Monthly Archives: July 2016

How to Assemble an IMPI on the MA5620G?

Issue Description

Q:
When the MA5620G provisions an SIP voice service, terminal users are often registered

by shelf ID or by slot ID (such as sip:0/22/3/1/1/hw32303131EF0EC641@ims.zj.chinamobile.com).

How are series of symbols like this are assembled?

Alarm Information

Null

Handling Process

A:
The general format of “sip:0/22/3/1/1/hw32303131EF0EC641@ims.zj.chinamobile.com” is “sip:

Channel/Port/Slot/Shelf/Rack/AN-ID@domain”,
where Channel is fixed to 0, and Rack is fixed to 1. So variable parameters are only Shelf, Port, Slot,

AN-ID and domain. Port indicates the port ID of a subscriber. Slot indicates the slot ID. Shelf indicates

the shelf ID. AN-ID indicates the name of an access node and is set by running the raio-anid command.

domain indicates the domain name, that is IMS domain name, and is set in the basic attribute

home-domain of the SIP interface.
Note: In terms of MA5620G, for the versions earlier than V800R305C00B133SPH006, Port, Slot,

and Shelf do not indicate actual port ID, slot ID, and shelf ID, but the real ones plus 1; for the versions

later than V800R305C00B133SPH006, the actual port ID, slot ID, and shelf ID comprise the IMPI.

Root Cause

Null

Suggestions

After the SIP interface is enabled, the device, carrying IMS user private ID (IMPI) information,

registers to the IMS regularly. Users can view whether the IMPI assembled by the device meets

the requirement by using the DBwin tool. For details of configuration, refer to the MA5620G SIP

Voice Service Configuration Procedure.txt.

olt_1

olt_1

 

TwitterLinkedInGoogle+FacebookPinterestTumblrStumbleUponRedditShare

Why can not login S5700 after S5700 power on when the software version was upgraded to V200R005C00SPC500?

Issue Description

After a customer upgraded the software version to V200R005C00SPC500 and

the latest patch V200R005SPH011 from V200R005C00SPC200, he could login

S5700 by telnet. Then the S5700 was powered off due to power outage. After he

powered on S5700 again, he couldn’t login S5700 by telnet.

The topology is simple:

 

Here are the detail steps:

(1)   In the old software version V200R005C00SPC200, the customer can login

S5700 by telnet.

(2)   After a customer upgraded the software version to V200R005C00SPC500 and the latest patch

V200R005SPH011, he can login S5700 by telnet. When he checked the configuration, he found the

following configuration, which didn’t exist in the configuration of V200R005C00SPC200.

#

telnet server enable

#

user-interface vty 0 4

protocol inbound telnet

#

 

(3)   But then S5700 was powered off due to power outage. After S5700 was powered on again, the

customer couldn’t login S5700 by telnet. When he login S5700 by console interface, he found the

there was no above configuration.

Alarm Information

None

Handling Process

(1)   After the S5700 was power on, the customer login S5700 by console interface, then he added the

following configuration, he can login S5700 again by telnet.

#

telnet server enable

#

user-interface vty 0 4

protocol inbound telnet

#

Root Cause

(1)  In V200R005C00SPC200, the telnet server is enabled by default. So in the configuration of SPC200,

there is no such command “telnet server enable” by default, but you can login S5700 by telnet.

(2)    In V200R005C00SPC500, the telnet server is disabled by default.  So in the configuration of SPC500,

if there is no command “telnet server enable”, you can’t login S5700 by telnet.

(3)   During the upgrade of  S5700 from SPC200 to SPC500+patch V200R005SPH011,  S5700 will do

this configuration translation. (it found that the last software version is SPC200, but the new one is

SPC500, so it will do the configuration translation)

(4)   So when S5700 is running with SPC500 for the first time, in the current running configuration,

you can see “telnet server enable”, and you can login S5700 by telnet. But in the saved  configuration,

it’s still the  same configuration as SPC200 where there is no such command “telnet server enable”.

In this situation,

(1.1)    If the configuration was not “save”, after S5700 was rebooted( by manually, by power on-off button

or by power outage) again, the  S5700 will not do the configuration translation again, and will run with

that configuration which was used in SPC200, and for this configuration, there is no “telnet server

enable”. But for SPC500, if there is no “telnet server enable” in the running configuration, you can’t

login S5700 by telnet.

(1.2)    If the configuration was  “save”, the command “telnet server enable” will be saved to the saved

configuration.  After S5700 is rebooted again, in the running configuration, there is ““telnet server enable”,

so you can login S5700 by telnet.

Solution

(1)   After the software version of S5700 was upgraded to V200R005C00SPC500 and the latest patch

V200R005SPH011 from V200R005C00SPC200, you need “save” the current configuration.

(2) Or you need configure the following commands for telnet.

#

telnet server enable

#

user-interface vty 0 4

protocol inbound telnet

#

Suggestions

After the software version of S5700 was upgraded to V200R005C00SPC500 and the latest patch

V200R005SPH011 from V200R005C00SPC200, you need “save” the current configuration.

If not, after S5700 was rebooted or power on again, you can’t login S5700 by telnet.

 

Switch

Switch

When customized for North America unable to configure OSN1800.

Issue Description

The OSN 1800 can be acess and configured without using U2000 or

WebLCT on laptop, instead using the built-in tool , OSN1800 WebLCT for TL1.
Open Internet Explorer, type htp:// ‘ Ne ip address’
Login page appears ”OSN1800 Weblct For TL1”
Problem occur, once input username n password, 4seconds later we were pushed

out from the system with error display – Web Services Inhibited

Alarm Information

None

Handling Process

Upon failure to login in , we checked username and password is correct. Checked

Internet Explorer setting for ”off” proxy and security settings ”Low”. Checked to

make sure NE IP is correct with Navigator. And found out for OSN1800 customized

for North America, this feature/tool is disabled.

SO enable it by changing the pin setting on J51 on the SCC board.
Refer to attached PDF for step by step explanation to enable this tool on customized

OSN1800 for North America

 

Root Cause

Reason was the OSN1800 was customized for North America. This is determined by

the jumper pin on J51 on the SCC board.

Suggestions

This built in tool is important and useful to engineers on-site for commissioning

OSN 1800 in case U2000 failure or don’t have U2000/WebLCT .
Sometimes engineer laptop can have problem loading U2000 or slow and with the

customer pushing Huawei for fast commissioning, using this tool will be very helpful.

Hope this helps engineers to have better knowledge and complete commissioning fast.

 

Huawei OptiX OSN 1800

What is the command lines that we can use on the OLT to detect PRTE board status

Issue Description

Q:
MA5600T(  MA5600V800R005C32B138)  has 2 PRTE one of them is

damaged so how can we check it from command line

Alarm Information

ALARM 2849 FAULT MAJOR 0×15411026 ENVIRONMENTAL

2010-08-12 10:04:24 DST
ALARM NAME  : Fan power fault alarm
PARAMETERS  : FrameID: 0    EMU ID:  0    Digital ID:  0    EMU Type:  FAN
Name:  Power fault
Name:  Power fault
DESCRIPTION : Fan power fault alarm
CAUSE       : Power  fault
ADVICE      : Check power

Handling Process

A:
About the querying about the power board through command line please check below

commands :
If the two board boards is normal:
MA5600T(config)#interface emu 0
MA5600T(config-if-fan-0)#display fan
{ alarm<K>|environment<K>|system<K> }:alarm
Command:
display fan alarm
EMU ID: 0
—————————————————————————-
Alarm name                    Alarm state
—————————————————————————-
Read temperature fault       Normal
Fan block                            Normal
Temperature high              Normal
Power fault                         Normal
—————————————————————————-
If one of the power board is failure or does not exists
MA5600T(config-if-fan-0)#display fan alarm

EMU ID: 0
—————————————————————————-
Alarm name                    Alarm state
—————————————————————————-
Read temperature fault       Normal
Fan block                             Normal
Temperature high               Normal
Power fault                          Alarm
—————————————————————————-

Root Cause

null

Suggestions

Null

OLT

OLT

How to check service board detail information?

Issue Description

Q:
How we can check detail information such as manufacture date, BOM code, board type,

etc… of service boards on MA5600T which have SCUB control board with V800R006C02 version…

Alarm Information

Null

Handling Process

A:
Detail information of service boards we can check by following steps:

1. Log in to device
2. enter in diagnose mode
huawei(config)#diagnose
huawei(diagnose)%%
3. Use command elable to check information
huawei(diagnose)%%display elable f/s
or      huawei(diagnose)%% display elable 0 for all boards in frame

Root Cause

Null

Suggestions

Null

PDH

How to Delete a Console Login Password?

Issue Description

How Can I Delete a Console Login Password?

Solution

Deleting the Console Login Password of a Fixed Switch Running

V100R002/V100R003

1.  Restart the switch. When the BootROM menu is displayed, choose option “5.

Enter filesystem submenu” to display the file system submenu.

2.  When the file system submenu is displayed, choose option “4.Rename file from

flash” to rename the default configuration file vrpcfg.zip. For example, change the

file name to vrptest.zip.

3.  Log in to the switch after the restart. The system uses the factory settings now.

4.  Decompress the vrptest file and name the decompressed file vrpcfg.bat.

<Quidway> unzip vrptest vrpcfg.bat

5.  Run the execute command to invoke the original configuration and delete the

console login password.

<Quidway> system-view
[Quidway] execute vrpcfg.bat
[Quidway] user-interface console 0
[Quidway-ui-console0] undo authentication-mode
[Quidway-ui-console0] quit
[Quidway] quit

6.   Save the configuration in the vrpcfg.zip file.

<Quidway> save
The current configuration will be written to the device. Continue? [Y/N]:y
Info: Please input the file name(*.cfg,*.zip)[vrpcfg.zip]:
Jun 25 2010 11:41:59 Quidway %%01CFM/4/SAVE(l): The user chose Y when

deciding whether to save the configuration to the device.    vrpcfg.zip   //Enter the

default configuration file name vrpcfg.zip.

7.  After the switch restarts, the console login password is deleted, and the original

service configurations are retained.

Deleting the Console Login Password of a Fixed Switch Running

V100R005/V200R001/V200R002/V200R003

During a startup process, a switch loads the BootROM program and the system software

in sequence. When the following information is displayed, press Ctrl+B within 2 seconds

to display the BootROM menu.

BIOS LOADING …
Copyright (c) 2008-2010 HUAWEI TECH CO., LTD.
CX22EFFE (Ver124, Jun  9 2010, 17:41:46)
Press Ctrl+B to enter BOOTROM menu … 0
password:    //Enter the BootROM password. The default password is Admin@huawei.com.

After you enter the correct BootROM password, the following BootROM menu is displayed:

BOOTROM  MENU

1. Boot with default mode
2. Enter serial submenu
3. Enter startup submenu
4. Enter ethernet submenu
5. Enter filesystem submenu
6. Modify BOOTROM password
7. Clear password for console user
8. Reboot
Enter your choice(1-8): 7
Note: Clear password for console user? Yes or No(Y/N): y
Clear password for console user successfully. Choose “1″ to boot, then set a new  password
Note: Do not choose “Reboot” or power off the device, otherwise this operation will not take effect

Choose option “7 .Clear password for console user” and then choose option “1. Boot with default mode.”

The console login password is then deleted.

NOTICE:
After clearing the console login password, choose option “1. Boot with default mode” in the BootROM

menu to restart the system. Do not choose option “8. Reboot” or power off the switch. Otherwise, the

configuration will be lost.

Deleting the Console Login Password of a Modular Switch Running

V100R001/V100R002/V100R003

1.  Restart the switch. When the BootROM menu is displayed, press CTRL+Z to display the hidden menu.

2.  Choose option “8-Rename file in CFCard” to rename the default configuration file vrpcfg.zip.

For example, change the file name to vrptest.zip.

3.  Log in to the switch after the restart. The system uses the factory settings now.

4.  Decompress the vrptest file and name the decompressed file vrpcfg.bat.

<Quidway> unzip vrptest vrpcfg.bat

5.  Run the execute command to invoke the original configuration and delete the console login password.

<Quidway> system-view
[Quidway] execute vrpcfg.bat
[Quidway] user-interface console 0
[Quidway-ui-console0] undo authentication-mode
[Quidway-ui-console0] quit
[Quidway] quit

6.  Save the configuration in the vrpcfg.zip file.

<Quidway> save
The current configuration will be written to the device. Continue? [Y/N]:y
Info: Please input the file name(*.cfg,*.zip)[vrpcfg.zip]:
Jun 25 2010 11:41:59 Quidway %%01CFM/4/SAVE(l): The user chose Y when deciding w
hether to save the configuration to the device.    vrpcfg.zip   //Enter the default configuration

file name vrpcfg.zip.

7.  After the switch restarts, the console login password is deleted, and the original service

configurations are retained.

Deleting the Console Login Password of a Fixed Switch Running

V100R006/V200R001/V200R002/V200R003

When you attempt to log in to a new switch through the console port for the first time, the

system prompts you to enter the console login password. You can also run the set authentication

password [ cipher password ] command in the console login user interface to set the console login

password. If you forget the Telnet or console login password, clear the console login password in

the BootROM menu. Perform the following steps:

During the startup process, press Ctrl+B as prompted and enter the password to enter the BootROM

menu. Choose option 8 in the BootROM menu to clear the console login password.

MAIN  MENU

1. Boot with default mode
2. Boot from Flash
3. Boot from CFCard
4. Enter serial submenu
5. Enter ethernet submenu
6. Modify Flash description area
7. Modify BootROM password
8. Clear password for console user
9. Reboot
Enter your choice(1-9):8
Note: Clear password for console user? Yes or No(Y/N): y
Clear password for console user successfully. Choose “1″ to boot, then set a new  password
Note: Do not choose “Reboot” or power off the device, otherwise this operation will not take effect

NOTICE:
After clearing the console login password, choose option “1. Boot with default mode” in the BootROM

menu to restart the system. Do not choose option “9. Reboot” or power off the switch. Otherwise, the

configuration will be lost.

How to Use the LDMD Board to Configure Intra-Board 1+1 Protection Fails?

Using the LDMD board to configure intra-board 1+1 protection fails due to the system limit.

The system displays a message “The optical port number exceeds the limit.”

Product

OptiX OSN 6800

OptiX OSN 3800

Fault Type

Protection

Optical Transponder Unit

Symptom

When the LDMD board is used to configure intra-board 1+1 protection on the OptiX iManager T2000

V200R007C01, the system displays a message “The optical port number exceeds the limit” and

configuring protection fails after the IN2/OUT2 optical interfaces are configured as the working

channel and the IN1/OUT1 optical interfaces are configured as the protection channel.

Cause Analysis

The OptiX OSN 6800 has a system specification, that is, only the IN1/OUT1 optical interface can

be selected as the working channel and the IN2/OUT2 optical interface can be selected as the

protection channel when an OTU board is used to configure intra-board 1+1 protection.

Procedure

  1. When you use the LDMD board to configure intra-board 1+1 protection on the
  2. OptiX OSN 6800, select the IN1/OUT1 optical interface as the working channel.
  3. Then, the protection configuration is successful.

Result

The problem is resolved.

Reference Information

None.

How to enable command log on S9300?

Issue Description

The device is not showing the command log, only interface up/down

S9300 V100R006C00SPC800

Alarm Information

none

Handling Process

By default, the command log is enabled with:

info-center source SHELL channel 4 log level notification

Where SHELL is the module name,  4 refers to logbuffer channel and Notification is the command log level.

To verify log status:

<Quidway> display logbuffer

The first line must be:

Logging buffer configuration and contents:enabled

Root Cause

none

Suggestions

none