Networkwide Conflict of MAC Addresses Caused by Incorrect Configuration of Protocol Converters from Other Vendors

The MAC addresses of the protocol converters from other vendors are set to the same value. As a result, the networkwide conflict of MAC addresses occurs after the devices from Huawei are interconnected with the devices from other vendors. This problem is solved by changing the MAC addresses of the protocol converters to different values.

Product

• OptiX OSN 1500A/1500B
• OptiX OSN 2500
• OptiX OSN 3500
• OptiX OSN 3500 II
• OptiX OSN 7500

Fault Type

Equipment interconnection failure

Symptom

A chain consists of the OptiX OSN equipment and the Ethernet boards configured on the NEs are the N4EFS0 and N1ETF8 boards. EPLAN services are configured on the chain because all other sites can communicate with the central site. After the OptiX OSN equipment is interconnected with the protocol converters from other vendors, the interconnected interface on the OptiX OSN equipment does not report any alarm, but the monitoring systems of other vendors detect frequent service interruptions.

Cause Analysis

Possible causes of the problem are as follows:

1. Service configuration is incorrect.
2. Protocol converters are faulty.

Procedure

1. Cause 1: Service configuration is incorrect.
   1. Check the service configuration and confirm that the service configuration is correct.
2. Cause 2: Protocol converters are faulty.
   1. On the NMS, perform RMON performance tests and find that the reception of packets at the receive port is interrupted frequently.
   2. Check the original data of the protocol converters and find that all protocol converters have the same MAC address.
   3. Change the MAC addresses of the protocol converters to different values. Then, the problem is solved.

Related Information

When configuring Ethernet services, you need to analyze the information about the interconnected equipment. Configure different Ethernet services based on different equipment information and service requirements.

MORE BLOG:

Prewarning for ARP Entry Aging Failures on MxU

When Users on Base Stations of Different Vendors Attempt to Get Online Through an ATN Device.

Warning of an ARP Entry Dually-Transmitting Failure

Different Definitions of Serial Bytes Cause Failure of Interconnection Between OptiX OSN Equipment and OptiX Metro Equipment

When the OptiX OSN equipment and OptiX Metro equipment are interconnected, broadcast data services are available only if broadcast data ports are interconnected correctly.

Product

• OptiX OSN 1500A/1500B
• OptiX OSN 2500
• OptiX OSN 3500
• OptiX OSN 3500 II
• OptiX OSN 7500

Fault Type

Equipment interconnection failure

Symptom

The S1 port on the OptiX OSN equipment is interconnected with the S1 port on the OptiX Metro 1000 to transmit a broadcast data service. The broadcast data service is however unavailable.

Cause Analysis

The OptiX equipment uses four unused overhead bytes to transmit broadcast data services.

The broadcast data ports on the OptiX OSN equipment are defined as follows:

• For the OptiX OSN equipment, the Serial 1 byte is defined as the first unused byte following the D3 byte in the SDH RS overhead bytes. Generally, the Serial 1 byte corresponds to the S1 port.
• For the OptiX OSN equipment, the Serial 2 byte is defined as the second unused byte following the D3 byte in the SDH RS overhead bytes. Generally, the Serial 2 byte corresponds to the S2 port.
• For the OptiX OSN equipment, the Serial 3 byte is defined as the second unused byte following the D12 byte in the SDH MS overhead bytes. Generally, the Serial 3 byte corresponds to the S3 port.
• For the OptiX OSN equipment, the Serial 4 byte is defined as the first unused byte following the D4 byte in the SDH MS overhead bytes. Generally, the Serial 4 port corresponds to the S4 port.

The broadcast data ports on the OptiX OSN equipment are defined as follows:

• For the OptiX Metro equipment, the Serial 1 byte corresponds to the F2 byte and is defined as the second unused byte following the D12 byte in the SDH MS overhead bytes. Generally, the Serial 1 byte corresponds to the F2 port.
• For the OptiX Metro equipment, the Serial 2 byte corresponds to the X1 byte and is defined as the first unused byte following the D4 byte in the SDH MS overhead bytes. Generally, the Serial 2 byte corresponds to the COM2 port.
• For the OptiX Metro equipment, the Serial 3 byte corresponds to the X2 byte and is defined as the first unused byte following the D3 byte in the SDH RS overhead bytes. Generally, the Serial 3 byte corresponds to the COM3 port.
• For the OptiX Metro equipment, the Serial 4 byte corresponds to the X3 byte and is defined as the second unused byte following the D3 byte in the SDH RS overhead bytes. Generally, the Serial 4 byte corresponds to the COM4 port.

The correspondence relationships between the serial ports on the OptiX OSN equipment and the OptiX Metro equipment are as follows:

• The Serial 1 byte on the OptiX Metro equipment corresponds to the Serial 3 byte on the OptiX OSN equipment.
• The Serial 2 byte on the OptiX Metro equipment corresponds to the Serial 4 byte on the OptiX OSN equipment.
• The Serial 3 byte on the OptiX Metro equipment corresponds to the Serial 1 byte on the OptiX OSN equipment.
• The Serial 4 byte on the OptiX Metro equipment corresponds to the Serial 2 byte on the OptiX OSN equipment.

The analysis shows that the broadcast data service is unavailable due to incorrect interconnection between the broadcast data ports on the OptiX OSN and OptiX Metro equipment.

Procedure

1. Re-configure the broadcast data service according to the correspondence relationships between the broadcast data ports on the OptiX OSN equipment and OptiX SDH equipment.

Related Information

None.

How to enable command log on S9300?

Why Automatical configuration backup cannot work on S5700

How to Change the Link Type of an Interface?

Boards Cannot Be Added on the NMS Due to Mismatch Between the NE Software Version and the NMS Version

The PL3A board cannot be added on the NMS because the NE software version does not match the NMS version. This fault is rectified by upgrading the NMS.

Product

OptiX OSN 1500B, 

Huawei OptiX OSN2500

Fault Type

Others

Symptom

The PL3A board is installed in slot 11 of the OptiX OSN 1500B. This board, however, cannot be added on the NMS. The NMS version is T2000 V200R004 and the NE software version is 5.21.17.13.

Cause Analysis

Possible causes of the fault are as follows:

• The NE software is incorrect.
• The NMS is faulty.

Procedure

1. Add the PL3A board in slot 11 by running commands. The board is added successfully, indicating that the NE software is normal.
2. Query the version mapping table. It is found that the NE software version does not match the NMS version.
3. Upgrade the NMS to T2000 V200R006. Then, the fault is rectified.

Related Information

None.

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

When customized for North America unable to configure OSN1800.

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

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.

Product

• OptiX OSN 1500A/1500B
• OptiX OSN 2500
• OptiX OSN 3500
• OptiX OSN 3500 II
• OptiX OSN 7500

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.

10G Card Issue in Quidway S5300

In S5700 when configuring voice vlan there is an error says “no enough resources”

When OptiX OSN 1800 Database Recovery Failures

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.

Product

OptiX OSN 3500, OSN1500B, OSN2500

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.

How to check service board detail information?

How to Delete a Console Login Password?

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