Wednesday, July 20, 2016

Incorrect Mode Setting Causes the Extended ECC Communication Failure

When different networks communicate with each other through the interconnected routers, the extended ECC is not available after the extended ECC mode is set to automatic. When the extended ECC mode is set to the specified mode, the fault is rectified.

Fault Type

ECC fault

Symptom

The two networks are connected to each other through Ethernet cables, but they cannot communicate with each other.

Cause Analysis

The possible causes are as follows:
  • The IP address is configured incorrectly.
  • The extended ECC mode is set incorrectly.

Procedure

  1. Query the IP addresses of the two NEs and the IP addresses of the routers connected to the two NEs.
    • NE A:
      IP address: 129.9.1.1
      Subnet mask: 255.255.255.0
      Gateway: 129.9.1.111
    • Router A:
      IP address: 129.9.1.111
      Subnet mask: 255.255.255.0
    • Router B: IP address:
      129.9.0.111
      Subnet mask: 255.255.255.0
    • NE B:
      IP address: 129.9.0.1
      Subnet mask: 255.255.255.0
      Gateway: 129.9.0.111
    The IP addresses are configured correctly, but the extended ECC is still unavailable.
  2. Query the ECC extended mode. It is found that ECC Extended Mode is set to Auto mode.
  3. Set ECC Extended Mode to Specified mode.
    NOTE:
    Select NE A as the server and NE B as the client. Input the IP addresses and port IDs of NE A and NE B in Set Server and Set Client respectively.
  4. After the preceding operations are complete, the extended ECC communication is restored.

Reference Information

  • Auto mode: In this mode, the extended ECC connection is established automatically. The configuration of the automatic mode is easy, but extra connections are established. Hence, the resource utilization ratio is low. It is recommended that the automatic mode be used only when there are less than nine NEs. In addition, two NEs can automatically establish an extended ECC for communication only after the ECC extended modes of the two NEs are set to Auto mode.
  • Specified mode: In this mode, the extended ECC is established between specified servers and clients. The extended ECC is of high reliability and the bandwidth is effectively used. Generally, the specified mode is adopted to establish the extended ECC connection.

Tuesday, July 19, 2016

what's the terminal unlock ip-address command?

Function

This command is used to unlock the locked IP address. After the command is successfully executed, the specified IP address is unlocked. You can log in to the device from the terminal or NMS using this IP address. For the terminal and NMS having the same IP address, both the terminal and NMS have been unlocked after you run this command once.

Format

terminal unlock ip-address ip-address

Parameters

Parameter Description Value
ip-address Indicates the terminal IP address to be unlocked. Dotted decimal notation.

Modes

Global config mode

Level

Administrator level

Usage Guidelines

The running process of the command is shown as follows:
  1. Enter the IP address of the terminal to be unlocked.
  2. The system searches the IP address of the terminal to be unlocked in the locked IP address list:
    • If the search fails, the system prompts the IP address is not locked.
    • If the search succeeds, the system delete the IP address from the locked IP address list and has no any prompt.

Example

To unlock the terminal IP address of 10.10.10.10, do as follows:
huawei(config)#terminal unlock ip-address
{ ip-address<I><X.X.X.X> }:10.10.10.10

  Command:
          terminal unlock ip-address 10.10.10.10

System Response

  • The system does not display any message after the IP address is unlocked successfully.
  • The system displays the message "Failure: IP address is not locked" when the IP address that you unlock is not locked.
  • For more information about the error message that the system displays against a command entered with incorrect syntax, see the "Syntax Check" in Parameter.

This take MA5608T as example.




Monday, July 18, 2016

When Interconnection Fails Due to Inconsistent Timeslot Numbering Modes

The services in certain timeslots are intermittently available during the equipment interconnection. During the problem investigation, it is found that the timeslot numbering modes are not consistent.

Fault Type

  • Equipment interconnection failure

Symptom

The OptiX OSN devices form a chain network that connects to an optical interface switch. The user configures VC-12 pass-through services in timeslots 1-38 on the OptiX OSN device. The services in timeslots 1-2, 4-5, and 7-8 are intermittently available on the switch. If the user configures VC-12 pass-through services in timeslots 1-63, this problem does not occur.

Cause Analysis

The timeslot numbering modes are not consistent. Currently, timeslot numbering modes are classified into sequential mode and interleaved mode, and Huawei equipment adopts the sequential mode by default. According to the user, the services are intermittently available. Thus, it can be inferred that the service configurations are correct, and the problem may be caused by the inconsistent timeslot numbering modes between the switch and the transmission device.

Procedure

  1. Through investigation, the switch of the user adopts the interleaved mode, which is inconsistent with the default timeslot numbering mode of Huawei equipment.
  2. The T2000 V100R002 that is used by the user can directly use the line numbers (Lucent mode) to create services in timeslots 1-38. After being reconfigured, the services on the switch become normal.

Splicing of a G.652 Fiber with a G.655 or G.656 Fiber

The splicing of a G.652 fiber with a G.655 or G.656 fiber.

Product

OptiX BWS 1600G,OSN6800,OSN8800

Fault Type

Fiber

Symptom

A network adopts the OptiX BWS 1600G and with an RPC board as a Raman amplifier board. The customer uses G.656 fibers and the ODF interfaces are of the LC/PC type. By default, the RPC board of the OptiX BWS 1600G matches the G.652 fiber whose interface is of the FC/UPC type. The LC/PC interface of the fiber provided by the customer does not satisfy the requirements of high power. In addition, the FC/PC interface of a fiber is not available temporarily. After negotiation with the customer, direct splicing is adopted.

Cause Analysis

The effective sections of the G.652 fiber and the G.655 or G.656 fiber, technical specifications for manufacturers, and mode field diameters of the 1500 nm wavelength (the G.652 fiber is of a bigger diameter) are different.
When two G.652 fibers are spliced, a loss is produced. The average loss is 0.02 dB.
In the case of splicing of a G.652 fiber with a G.656 fiber, the loss is 0.38 dB due to different cross-sectional areas of fibers. In this case, the splicing loss is within the permitted range for an RPC board. In the case of splicing of a G.652 fiber and a G.656 fiber, the average loss is 0.5 dB. In the case of splicing of a G.652 fiber with a G.655 or G.656 fiber whose effective section is small, a great loss is produced (as great as 2 dB). In this case, the splicing loss is out of the permitted range.

Procedure

  1. None.

Result

The problem is resolved.

The Lower Order Service Fails to Be Created Because the Cross-Connect Resources Are Insufficient

When service expansion is required on the existing network, check and ensure that the cross-connect resources are sufficient.

Fault Type

  • Others

Symptom

The customer needs to add several VC-12 services to the OptiX OSN 3500 in service on the existing network. After the service configuration is delivered, the NMS returns a message indicating that the lower order cross-connect board cannot provide sufficient higher order paths for the lower order service. The error code is 38882. As a result, the added services are in inactive state.

Cause Analysis

The possible causes are as follows:
  • Cause 1: The software version of the cross-connect board does not match with the version specified in the mapping table.
  • Cause 2: The cross-connect matrix is incorrect.
  • Cause 3: The configuration is incorrect.
  • Cause 4: The cross-connect capacity is limited.

Procedure

  1. Check and ensure that the software version of the cross-connect board matches with the version specified in the mapping table. Thus, cause 1 can be excluded.
  2. Switch the active and standby cross-connect boards, and the fault persists. Thus, cause 2 can be excluded.
  3. Check the cross-connect configuration of the NE, and find the following phenomenon: VC-12 services can be created on an existing VC-4 server trail, rather than on a new VC-4 server trail. Thus, cause 3 can be excluded.
  4. The most probable cause of the fault is as follows: The cross-connect board reserves 63 VC-12 resources for the existing VC-4 server trails. After new VC-4 server trails are added, lower order resources are insufficient for use.
  5. Optimize the service configuration and reduce the number of VC-4 server trails, to make optimal use of cross-connect resources.

Friday, July 15, 2016

How to do if Incorrect Mode Setting Causes the Extended ECC Communication Failure

When different networks communicate with each other through the interconnected routers, the extended ECC is not available after the extended ECC mode is set to automatic. When the extended ECC mode is set to the specified mode, the fault is rectified.

Fault Type

ECC fault

Symptom

The two networks are connected to each other through Ethernet cables, but they cannot communicate with each other.

Cause Analysis

The possible causes are as follows:
  • The IP address is configured incorrectly.
  • The extended ECC mode is set incorrectly.

Procedure

  1. Query the IP addresses of the two NEs and the IP addresses of the routers connected to the two NEs.
    • NE A:
      IP address: 129.9.1.1
      Subnet mask: 255.255.255.0
      Gateway: 129.9.1.111
    • Router A:
      IP address: 129.9.1.111
      Subnet mask: 255.255.255.0
    • Router B: IP address:
      129.9.0.111
      Subnet mask: 255.255.255.0
    • NE B:
      IP address: 129.9.0.1
      Subnet mask: 255.255.255.0
      Gateway: 129.9.0.111
    The IP addresses are configured correctly, but the extended ECC is still unavailable.
  2. Query the ECC extended mode. It is found that ECC Extended Mode is set to Auto mode.
  3. Set ECC Extended Mode to Specified mode.
     NOTE:
    Select NE A as the server and NE B as the client. Input the IP addresses and port IDs of NE A and NE B in Set Server and Set Client respectively.
  4. After the preceding operations are complete, the extended ECC communication is restored.

Reference Information

  • Auto mode: In this mode, the extended ECC connection is established automatically. The configuration of the automatic mode is easy, but extra connections are established. Hence, the resource utilization ratio is low. It is recommended that the automatic mode be used only when there are less than nine NEs. In addition, two NEs can automatically establish an extended ECC for communication only after the ECC extended modes of the two NEs are set to Auto mode.
  • Specified mode: In this mode, the extended ECC is established between specified servers and clients. The extended ECC is of high reliability and the bandwidth is effectively used. Generally, the specified mode is adopted to establish the extended ECC connection.

How to Repeated Clock ID Causes the Free-Run of the NE Clock?

The ID of the internal clock source is the same as the ID of the external clock source, which results in the free-fun of the NE clock. When the setting of the internal clock source ID is cancelled, the fault is rectified.

Product

Fault Type

  • Time synchronization
  • S1_SYN_CHANGE
  • LTI

Symptom

The SL64 board is installed in both slot 8 and slot 11 of the OptiX OSN 3500. The OptiX OSN 3500 and the OptiX OSN 7500 are interconnected. The cross-connect board of each device reports the S1_SYN_CHANGE and LTI alarms.
  • The clock configuration of the OptiX OSN 3500 is as follows:
    • The clock source traced by the line board is obtained from another device, and the priority of the external clock source is higher than the priority of the internal clock source.
    • The reversion mode of the high-priority clock source is set to automatic reversion.
    • The clock quality is set to Automatic Extraction.
    • Protection Status is set to Star Extended SSM Protocol.
    • The clock ID of the line board is not set.
    • The ID of the internal clock source is set to 6.
    • All the clock sources are in the normal state.
  • The clock configuration of the Optix OSN 7500 is as follows:
    • The external clock source exists.
    • No clock ID for either the external clock source or the internal clock source is set.
    • The clock synchronization source is provided by the clock source of the line board with a higher priority.

Cause Analysis

The OptiX OSN 3500 and the OptiX OSN 7500 are located on the same network, and the clocks of the entire network are synchronized with the external clock source of the device outside the network. The ID of the external clock source is 6, which conflicts with the ID of the internal clock source of the Optix OSN 3500. In this case, when the OptiX OSN 3500 detects the signals of the external clock source, after checking the ID of the external source, the OptiX OSN 3500 regards the signals as the internal clock signals. Therefore, to prevent the clock tracing loop, the clock of the OptiX OSN 3500 enters the free-run mode.

Procedure

  1. In the T2000 main topology, right-click the NE icon of the OptiX OSN 3500, and then choose NE Explorer.
  2. Choose Configuration > Clock > Clock Subnet Configuration from the Function tree.
  3. Click the Clock Subnet tab.
  4. Set Internal Clock Source.
     NOTE:
    If the device does not have an external clock source, set Internal Clock Source to (None). If the ID of the internal clock source is required to be set, make sure that the ID is different from the clock IDs of other devices.
  5. Click Apply. In the Operation Result dialog box, click Close.