Showing posts with label OSN 2500. Show all posts
Showing posts with label OSN 2500. Show all posts

Monday, January 23, 2017

The MSTP Configuration of stp md5-key

Function

The stp md5-key command is used to set the MD5 key for the MD5 encryption algorithm in an MST region. When you need to encrypt the region to ensure the device security, run this command. After the MD5 key for the MD5 encryption algorithm in the region is set, two devices cannot communicate with each other unless their MD5 keys are the same.
The undo stp md5-key command is used to restore the default MD5 key for the MD5 encryption algorithm in the region. The default MD5 key is recommended. After the MD5 key is modified, you can run this command to restore the default MD5 key. After the default MD5 key for the MD5 encryption algorithm in the region is restored, the MD5 key is 0x13AC06A62E47FD51F95D2BA243CD0346.

Format

stp md5-key number
undo stp md5-key

Parameters

Parameter Description Value
number Indicates the encryption parameter. The string must be hexadecimal and in length of multiples of 2. Character string type, a string of 1-32 characters.
Default: 0x13AC06A62E47FD51F95D2BA243CD0346
Recommended value: 0x13AC06A62E47FD51F95D2BA243CD0346.

Modes

Global config mode, OSN 1500, OSN 2500

Level

Operator level

Usage Guidelines

  • For the device security, two devices in a same region cannot communicate with each other unless their MD5 keys are the same. Thus, it is recommended to use the default MD5 key in the settings.
  • Two devices that belong to a same MST region must meet the following requirements:
    • The MST region names are the same.
    • The revision levels of the MST region are the same.
    • The configuration digest are the same. The configuration digest is calculated by using the MD5 encryption algorithm based on the VLAN mapping table of all configured spanning trees in the MST region and the MD5 key.

Example

To set the MD5 key for the MD5 encryption algorithm in an MST region to 00e0fc042958, do as follows:
huawei(config)#stp md5-key                                                      
{ string<S><Length 1-32> }:00e0fc042958                                                
                                                                                
  Command:                                                                      
          stp md5-key 00e0fc042958
To restore the default MD5 key for the MD5 encryption algorithm in an MST region, do as follows:
huawei(config)#undo stp md5-key   

Wednesday, January 4, 2017

The MSTP Configuration of revision-level

Function

The revision-level command is used to configure the multiple spanning tree protocol (MSTP) revision level of the device. The revision level, region name and configuration digest are three decision factors to check whether the devices are in the same multiple spanning tree (MST) region. After the revision level is set, only the devices with the same revision level are in the same MST region.
The undo revision-level command is used to restore the default MSTP revision level of the device. By default, the revision level of the device is 0.

Format

revision-level level
undo revision-level

Parameters

Parameter Description Value
level Indicates the MSTP revision level. Numeral type. Range: 0-65535.
Default: 0.

Modes

MST region mode, OSN 3500, OSN 2500

Level

Operator level

Usage Guidelines

  • Run the config command to enter global config mode, and then run the stp region-configuration command to enter MST region mode.
  • The MSTP revision level, region name and VLAN mapping table are used to check the MST which the device belongs to.
  • The user configure the related parameters of the MST region on the device to divide the device into a specified MST region.
  • Two devices that belong to a same MST region meet the following requirements:
    • The region names are the same.
    • The revision levels are the same.
    • The configuration digest are the same. The configuration digest is calculated by VLAN mapping table of all the spanning trees and MD5-KEY through MD5 encryption algorithm.
  • The modified device revision level takes effect only after the configuration is activated.

Example

To set the MSTP revision level of the device to 32768, do as follow:
huawei(stp-region-configuration)#revision-level                                 
{ integer<U><0,65535> }:32768                                                   
                                                                                
  Command:                                                                      
          revision-level 32768  
To restore the default MSTP level of the device, do as follows:
huawei(stp-region-configuration)#undo revision-level  

Friday, December 30, 2016

How to Logging In to the Web LCT?

Log in to the Web LCT before performing NE settings on the Web LCT.

Procedure

  1. Double-click the startweblct_https.bat file at "WebLCT\WebLCT\Tomcat" to launch the Web LCT application.
  2. In the browser, enter the default value admin for User Name and Changeme_123 for Password.
  3. Enter the Verification Code according to the picture that is displayed on the right side.
  4. Click Login to display the NE List window.

Postrequisite

After logging in to the Web LCT,pay attention to the following if you need to commission an NE on the Web LCT:
  • When no U2000 user logs in to an NE and an LCT user requests to log in to the NE, the NE does not refer to the LCT Access Control parameter and allows the LCT access directly
  • When a U2000 user has logged in to an NE and then an LCT user requests to log in to the NE, the NE determines whether to allow the LCT user to log in based on the LCT Access Control parameter.
  • When an LCT user has logged in to an NE and then a U2000 user requests to log in to the NE, the login of the LCT user does not affect the login of the U2000 user, and the successful login of the U2000 user does not affect the logged-in LCT user.
  • When the LCT user and the U2000 user log in to the NE at the same time, set LCT Access Control to Prohibit Access. This does not affect the LCT user that has already logged in.

Our company supply OSN 2500, OSN 3500 and transmission board.


More blog:

Wednesday, December 28, 2016

The MSTP Configuration on display stp region-configuration

Function

This command is used to query the configuration of the multiple spanning tree (MST) that is validated. In this case, you can judge what configuration needs to be activated manually.

Format

display stp region-configuration

Parameters

None

Modes

MST region mode, OSN1500, OSN 2500

Level

Operator level

Usage Guidelines

  • Run the config command to enter global config mode, and then run the stp region-configuration command to enter MST region mode.
  • When you query the validated configuration of the MST region, refer to the following description for details of the parameters.

Example

To query the configuration of the MST region, do as follows:
huawei(stp-region-configuration)#display stp region-configuration               
 Oper configuration                                                             
   Format selector    :0                                                        
   Region name        :00e0fc995050                                             
   Revision level     :0                                                        
                                                                                
   Instance   Vlans Mapped                                   
      0          1    to  4094 

System Response

  • The system displays the queried result when the command runs successfully.
  • The following table describes the parameters in response to the display stp region-configuration command.
    Parameter Description
    Format selector Indicates the selection factor specified by the MSTP protocol.
    Region name Indicates the MST region name.
    Revision level Indicates the revision level of the MST region.
    Instance Vlans Mapped Indicates the mapping relation between the spanning tree example of the MST region and the VLAN. 
More blog:

Tuesday, December 27, 2016

What's the MSTP Configuration on check region-configuration

Function

This command is used to check the configuration of the Multiple Spanning Tree (MST) region. The users can judge the MST region which the current switch belongs to based on the information or check whether the configuration of the MST region is correct.

Format

check region-configuration

Parameters

None

Modes

MST region mode, OSN 3500, OSN 2500

Level

Operator level

Usage Guidelines

  • Run the config command to enter global config mode, and then run the stp region-configurationcommand to enter MST region mode.
  • The deactivated region configuration includes the setting of MST region name, revision level and table of mapping between the MST region instances and VLANs. After the region configuration is activated, the active region configuration is displayed.
  • In multiple spanning tree protocol (MSTP) network, make sure that the region configuration is correct, especially the MST region instances and VLAN mapping table.
  • Only devices that have the same region name, VLAN mapping table, and revision level can be configured in the same region.

Example

To check the configuration information of the region, do as follows:
huawei(stp-region-configuration)#check region-configuration                     
 Admin configuration                                                            
   Format selector    :0                                                        
   Region name        :00e0fc995050                                             
   Revision level     :0                                                        
                                                                                
   Instance   Vlans Mapped                                                      
     0          1    to  4094   

System Response

  • The system displays the result when the command runs successfully.
  • The following table describes the parameters in response to the check region-configuration command.
    Parameter Description
    Format selector Indicates the specified selector of the MSTP protocol.
    Region name Indicates the name of the MST region. It is used to identify the MST region.
    Revision level Indicates the revision level of the MST region.
    Range: 0-65535.
    Default value: 0.
    Instance Vlans Mapped Indicates the mapping between the spanning tree instance of the MST region and the VLAN.
More blog:

MSTP Configuration on active region-configuration

Function

This command is used to activate the configuration of the Multiple Spanning Tree (MST) region manually. When the MST region is re-configured and you need to validate the configuration, run this command. After that, the configuration of the MST region is available.
CAUTION:
Activating the configuration of the MST region interrupts ongoing services. Therefore, run this command with caution.

Format

active region-configuration

Parameters

None

Modes

MST region mode, OSN 3500, OSN 2500

Level

Operator level

Usage Guidelines

  • Run the config command to enter global config mode, and then run the stp region-configuration command to enter MST region mode.
  • When you configure the related parameters of the MST region, especially the mapping table for VLAN and examples, the topology may get unstable. To decrease the instability caused by the configuration, MSTP does not trigger recalculation of the spanning tree immediately, but activate the related parameters of the MST region or enable the MSTP protocol to validate the configuration.
  • Any change of a parameter of the MST region may cause the recalculation of the topology. Run this command to make configuration take effect.
  • By running this command, the configured parameters of the MST region are replaced by the current running parameters. MSTP recalculates the spanning tree.

Example

To activate the configuration of the MST region manually, do as follows:
huawei(stp-region-configuration)#active region-configuration             
  STP actives region configuration,it may take several minutes,are you sure to
active region configuration? [Y/N][N]y
  Command is being executed. Please wait: 100%

System Response

  • The command execution duration varies depending on other configurations in the system. If the duration is long, the system displays the progress.
  • The system does not display any message after the command is executed successfully.

More blog:

Friday, October 21, 2016

E1 Service Interruption Caused by Different Timeslot Numbering Schemes (ITU-T G.707 and ITU-T G.709)

When different devices or networks are interconnected with each other to provide services, part of the services are interrupted if different timeslot numbering schemes are adopted. After a timeslot numbering scheme is adopted, the fault is rectified.

Fault Type

  • Configuration problem
  • Device interconnection failure
  • Service interruption

Symptom

Two transmission devices from different vendors are interconnected with each other, and 20 timeslots of one STM-1 are adopted to transmit E1 services. When the services are configured, it is found that seven E1 services of timeslots 1, 4, 7, 10, 13, 16 and 19 are normal, and 13 E1 services of timeslots 2, 3, 5, 6, 8, 9, 11, 12, 14, 15, 17, 18 and 20 are interrupted.

Cause Analysis

Company A uses a Huawei device, which adopts the ITU-T G.707 timeslot numbering scheme. Company B uses the device of a competitor, which adopts the ITU-T G.709 timeslot numbering scheme.
 NOTE:
The sequences of timeslots 1, 4, 7, 10, 13, 16, and 19 in the two timeslot numbering schemes (ITU-T G.707 and ITU-T G.709) are the same, but the sequences of timeslots 2, 3, 5, 6, 8, 9, 11, 12, 14, 15, 17, 18 and 20 in the two timeslot numbering schemes are different, thus causing the service interruption.

Procedure

  1. According to the timeslot sequence from 1 to 20, configure the E1 services on the device of company A.
  2. Configure the services on the device of company B. Table 1 shows the mapping of timeslot numbers.
    Table 1Mapping of timeslot numbers between the devices of companies A and B
    Company
    Timeslot Number
    A
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    B
    1
    22
    43
    4
    25
    46
    7
    28
    49
    10
    31
    52
    13
    24
    55
    16
    37
    58
    19
    40
     NOTE:
    You can configure the E1 services on the device of company A, and then according to the timeslot mapping, configure the services for corresponding timeslots on the device of company B. For the corresponding timeslots, see Table 1.

Reference Information

  • The ITU-T G.707 timeslot numbering scheme adopts the sequential mode, which is also called Huawei mode, as shown in Figure 1. The numbering scheme is as follows: VC-12 number = TUG-3 number + (TUG-2 number - 1) x 3 + (TU-12 number - 1) x 21.
  • The ITU-T G.709 timeslot numbering scheme adopts the interleaved mode, which is also called Lucent mode, as shown in Figure 1. The numbering scheme is as follows: VC-12 number = (TUG-3 number - 1) x 21 + (TUG-2 number - 1) x 3 + TU-12 number.
Figure 1 ITU-T G.707 timeslot numbering



Thursday, October 20, 2016

Other Boards Could Not Be Detected Because the Auxiliary Board Was Faulty

When the auxiliary board EOW on the OptiX OSN 7500 was faulty, other boards could not be detected. After the EOW board was cold reset, other boards were detected. However, configuring NE services failed, and the NE reported the COMMUN_FAIL alarm. The fault was rectified by replacing the EOW board.

Fault Type

  • Fault in an auxiliary board
  • COMMUN_FAIL

Symptom

The indicators on some OptiX OSN 7500 boards turned red, and configuring NE services failed. After the EOW board was cold reset, the indicators on these boards were not red again. However, configuring NE services still failed, and the NE reported the COMMUN_FAIL alarm.

Cause Analysis

The auxiliary board EOW was faulty.

Procedure

  1. Found out the boards on which the indicators turned red. Assumed that one such board was in slot 26.
    NOTE:
    If the indicator on a board is red, it means that the board cannot be detected.
  2. Remove the board in slot 26 and installed the board in another slot. The indicator was not red again, and the board were detected. Therefore, the issue was not related to the board in slot 26 or the SCC board.
  3. Cold reset the EOW board. The indicator on the board in slot 26 was not red. However, configuring NE services still failed, and the NE reported the COMMUN_FAIL alarm.
  4. Replaced the EOW board. The COMMUN_FAIL alarm cleared, and configuring services for the board in slot 26 was successful.

Related Information

If some boards on the OptiX OSN equipment cannot be detected, determine the most possibly faulty board. For example, on the OptiX OSN 7500, the issue may be caused by an EOW board, and on the OptiX OSN 3500, the issue may be caused by an AUX board.


MORE BLOG:

How to Install SLQ4 board on slot 1 to slot 4 in OSN 3500?

An NE Became Unreachable to the NMS After Line Boards Were Cold Reset

Lower-rate multiport line boards preempted DCC resources of higher-rate line boards after line boards were cold reset during an NE upgrade or expansion. As a result, the NE became unreachable to the NMS. The fault was rectified by releasing DCC resources on lower-rate line boards.

Fault Type

  • DCN fault
  • DCC_CHAN_LACK

Symptom

Before an NE upgrade or expansion, the NE did not report any alarms, and DCC communication was normal. After an NE was upgraded or expanded, line boards reported the DCC_CHAN_LACK alarms, and the NE became unreachable to the NMS.

Cause Analysis

During an NE upgrade or expansion, line boards were cold reset, and DCC resources were re-allocated. The lower-rate line boards preempted DCC resources of the higher-rate line boards. As a result, the NE became unreachable to the NMS.

Procedure

  1. Checked whether there were any bit errors in DCC byte transmission. The transmit end sent DCC bytes, but the receive end did not receive any. Therefore, this issue was not related to bit errors.
  2. Went to the site and checked the NE status.
    1. Connected a PC directly to the NE, and logged in to the NE.
    2. Checked the ECC protocol settings. The settings were correct. Therefore, this issue was not related to the ECC protocol settings.
    3. Performed a switchover from the active SCC board to the standby SCC board. The DCC_CHAN_LACK alarms persisted. Therefore, this issue was not related to an SCC board.
    4. Removed the lower-rate line boards. The higher-rate line boards immediately began to transmit data. The DCC_CHAN_LACK alarms cleared, and NEs communicated properly with each other. It was inferred that the lower-rate line boards preempted DCC resources of the higher-rate line boards, blocking the NMS from reaching the NE.
       NOTE:
      • Generally, an SCC board supports multiple DCC working modes, and some DCC working modes provide more DCC resources.
      • In the default DCC working mode for the N1GSCC board, the D1 to D3 bytes function as physical transmission channels and 10 optical ports are DCC-enabled.
      • Generally, a lower-rate line board has multiple optical ports. For example, an SLT1 board has 12 optical ports. After the line boards were cold reset, DCC resources were re-allocated. The lower-rate line boards preempted DCC resources of the higher-rate line boards. The higher-rate line boards failed to obtain DCC resources, blocking the NMS from reaching the NE.
    5. Re-installed the lower-rate line boards.
  3. Checked for the DCC_CHAN_LACK alarm on the NMS after the NE was running properly. The DCC_CHAN_LACK alarm persisted, and the NE became unreachable again.
  4. Released DCC resources from optical ports on the lower-rate line boards. The optical ports on the higher-rate line boards restored to transmit data. The DCC_CHAN_LACK alarm cleared, and the NE became reachable from the NMS. It was determined that the lower-rate line boards preempted DCC resources of the higher-rate line boards, blocking the NMS from reaching the NE.
     NOTICE:
    Before an NE upgrade or expansion, properly allocate DCC resources. Specifically, release some DCC resources from lower-rate multiport line boards so high-rate line boards can obtain sufficient DCC resources upon cold resetting.

Friday, October 7, 2016

Certain Ports on the N1SLQ4 Board Are Unavailable due to Bus Wiring Limitation of the Cross-Connect Board

Certain ports on the N1SLQ4 board are unavailable due to the bus wiring limitation of the cross-connect board. This problem is solved by reinstalling the N1SLQ4 board.

Fault Type

Cross-connect unit

Symptom

The OptiX OSN 3500 is configured with the N1SXCSA board. Two N1SLQ4 boards are installed in slots 4 and 15, but only the former two optical interfaces of the boards are available.

Cause Analysis

When planning the slots of boards, you need to consider the access capacity of slots, the bus wiring of the cross-connect board, and the bus rate of the board.
  1. The OptiX OSN 3500 is configured with the N1SXCSA board. The access capacities of slots 5 and 14 are 5 Gbit/s. The total rate of the ports on the N1SLQ4 board is 2.5 Gbit/s. Therefore, the problem is not caused by access capacity limitation.
  2. The N1SXCSA board can adapt to 622 Mbit/s buses and 2.5 Gbit/s buses.
  3. The bus rate of the N1SLQ4 board is 622 Mbit/s, so four 622 Mbit/s buses are required to support the four optical interfaces on the board. However, slots 4 and 15 provide only two buses respectively. Therefore, only the former two optical interfaces on the boards are available.

Procedure

  1. Reinstall the N1SLQ4 boards into slots 5 and 14. Slots 5, 6, 13, and 14 provide four buses. Then, all optical interfaces on the boards are available.

Related Information

On the OptiX OSN equipment, two types of backplane buses are available, namely, 622 Mbit/s and 2.5 Gbit/s. The bus specifications of the OptiX OSN equipment are as follows:
  • The OptiX OSN 1500 supports 622 Mbit/s buses only.
  • The OptiX OSN 2500 supports 622 Mbit/s buses only.
  • When configured with the GXCSA, EXCSA, or UXCSA/UXCSB, the OptiX OSN 3500 supports 622 Mbit/s buses only. When configured with the SXCSA/SXCSB, IXCSA/IXCSB, or FXCSA, the OptiX OSN 3500 can adapt to 622 Mbit/s buses and 2.5 Gbit/s buses.
  • The OptiX OSN 7500 can adapt to 622 Mbit/s buses and 2.5 Gbit/s buses.

MORE BLOG: