Showing posts with label OSN2500. Show all posts
Showing posts with label OSN2500. Show all posts

Thursday, September 1, 2016

Objects that Block the Fan Cause the Device to Report the FAN_FAIL Alarm

The device reports the FAN_FAIL alarm. After the fan is checked, it is found that some objects block the fan board. After the objects are removed, the fan works in the normal state.

Fault Type

Others

Symptom

When the OptiX OSN 1500 is being commissioned, it is found that the fan cannot work in the normal state. The device reports the FAN_FAIL alarm.

Cause Analysis

Fan Failure

Procedure

  1. Remove the fan from the subrack. It is found that some objects block the fan.
  2. Remove the objects and install the fan. The fan can work in the normal state.
  3. Query the NE alarms on the NMS. It is confirmed that no alarm is generated, and the FAN_FAIL alarm is cleared.

Reference Information

When the fan is faulty, check whether some objects block the fan.
If no object blocks the fan, replace the fan board.

MORE BLOG:

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

LCAS Negotiation Abnormal if Bound Paths Configured Prior to Cross-Connect Service

When the LCAS function is not enabled on either the source NE or the sink NE, LCAS negotiation faults arise and the LCAS configuration fails if the bound path is configured before the cross-connect service is configured. You can rectify the fault by deleting the existing configurations at both ends and enabling the LCAS function at both ends.

Products

Fault Type

  • LCAS
  • Ethernet fault

Symptom

For the point-to-point NE A and NE B, the LCAS function is enabled at NE A but disabled at NE B. After the bound paths are configured for the data processing boards at both ends and the cross-connect service is configured from the data processing board to the line board, LCAS negotiation at NE A becomes abnormal, that is, all the timeslots are deleted or only one timeslot remains.

Cause Analysis

The fault arises owning to the version and working principles of the LCAS function. Hence, the following situations should be prevented:
  • The LCAS function is disabled at one end.
  • The bound paths are configured before the cross-connection service is configured.

Procedure

  1. Query the status of the LCAS function at both ends, and ensure that the function is enabled at both ends.
  2. Query the paths bound at both ends, and delete the existing configurations.
  3. Query and delete the cross-connect service configured between the data processing board and the line board.
  4. Configure the cross-connect service between the data processing board and the line board, and then configure the bound paths. The alarm disappears, and the troubleshooting is complete.
MORE BLOG:

Friday, July 29, 2016

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

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.

Services Are Unavailable Due to Inappropriate Types of Optical Modules

Appropriate types of optical modules need to be selected to match transmission distances.

Fault Type

Unavailable services

Symptom

The OptiX OSN NEs at both ends of the link are configured with the SL4 boards. The SL4 boards are connected through fibers, but services are unavailable.

Cause Analysis

Possible causes of the fault are as follows:
  • The SL4 boards are faulty.
  • The fibers are faulty.
  • The optical distribution frame is faulty.
  • The optical modules are faulty.
  • The distance between the two NEs exceeds the maximum transmission distance supported by the optical modules.

Procedure

  1. Check the parameters associated with the SL4 boards. No exceptions are found. The boards, however, reported the R_LOS alarm, indicating the loss of signal.
  2. Use the optical time-domain reflectometer (OTDR) to test the fibers. The fibers are normal.
  3. Check the connections between the NEs and the optical distribution frame. The connections are normal.
  4. Check the optical modules on the SL4 boards. The optical modules are normal.
  5. Measure the distance between the two NEs. The distance is 26 km whereas the S-4.1 optical modules used on the SL4 boards support a maximum transmission distance of 15 km. Therefore, the services are unavailable due to inappropriate types of optical modules.
  6. Use the appropriate types of optical modules. Then, the fault is rectified.

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.

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.

Monday, July 25, 2016

The External Clock Source Is Unavailable After a Fiber Cut Because the Clock Configuration Is Incorrect

The priorities of the clock sources are set incorrectly, so the external clock source is unavailable after a fiber cut. After the priorities of the clock sources are re-set, the fault is rectified.

Fault Type

  • Bit errors
  • LTI

Symptom

The EOW board on NE A is connected to two clock sources from third-party equipment, the network clock tracing is normal. After a fiber cut occurs on the ring network, the external clock source becomes unvailable. In addition, NE D reports the LTI alarm, and a large amount of bit errors occur.
Cause Analysis
In normal cases, the working path of the clock tracing is external clock source->NE A->NE B->NE C->NE D->NE F; the protection path is external clock source->NE A->NE F->NE D->NE C->NE B. After a fiber cut occurs on the ring network, the clock source of NE D is lost. After the clock configuration of the network is checked, it is found that System Clock Source Priority Table on NE D is not configured.

Procedure

  1. Query the clock subnet configuration by using the NMS.
    1. In the NE Explorer of NE D, choose Configuration > Clock > Clock Subnet Configuration.
    2. Choose the Clock Quality tab, and Choose the Clock Source Quality. Click Query. The return shows that the system receives the G.811 primary reference clock (PRC) from the 11-SL64 board.
    3. Choose View > Clock View to obtain the clock tracing relationship of NE D. The west clock source (on NE C) next to NE D is unavailable, so NE C should trace its east clock source.
  2. In the NE Explorer of NE D, choose Configuration > Clock > Clock Source Priority. Then, select Priority Table for Phase-Locked Sources of 2nd External Clock Output, and click Create to add 8-SL64 and 11-SL64 as clock sources.
  3. In the Clock View, refresh the clock tracing relationship. Then, the alarm clears.

Communication Anomaly Occurs Between the Equipment and the NMS Due to the Setting of the Firewall

If the equipment and the NM server communicate unidirectionly, disable the firewall or antivirus software to restore the communication.

Product

Fault Type

  • DCN fault

Symptom

During the system commissioning, it is found that the NM server can communicate with the OptiX OSN equipment by using the ping command, but the PC used on the equipment side cannot communicate with the NMS.

Cause Analysis

The firewall or antivirus software is used on the NM server.

Procedure

  1. Replace the NM server with a PC, and use the ping command to test the DCN. The result shows that the communication is normal.
  2. Disable the firewall or antivirus software on the NM server. The equipment side can communicate with the NM server by using the ping command.

How to do when Failing to Connect the 155 Mbit/s Optical Port on the Router of Company C

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.

Monday, July 18, 2016

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.

Tuesday, July 12, 2016

Failing to Add IMA Boards into the DPS Protection Group

IMA boards fail to be added into the DPS protection group, hence failing to realize the DPS protection.

Fault Type

Configuration_Problem

Symptom

Boards fail to be added into the DPS protection group.
The configuration of the DPS protection fails to be performed. The boards fail to be added into the DPS protection group.

Cause Analysis

IMA boards that are added into the DPS protection group must be inserted in the paired slots.

Procedure

  1. Make sure that the IMA boards that are configured with DPS protection are set to the paired slots.

Friday, July 8, 2016

Mismatching Between MA Groups and Associated VCTRUNKs, Hence Causing the Binding Failure

IMA groups fail to be bound with associated VCTRUNKs. You need to configure IMA groups to match with associated VCTRUNKs.

Fault Type

Configuration_Problem

Symptom

The principle of binding VCTRUNKs is met, but VCTRUNKS fail to be bound.

Cause Analysis

Mutual check relation exists between IMA groups and associated VCTRUNKs.

Procedure

  1. If IMA groups are symmetrically configured, make sure that the mapping VCTRUNKs are symmetrical.
  2. If VCTRUNKs are nonsymmetrical, make sure that the mapping IMA groups are nonsymmetrical.

Thursday, June 30, 2016

Failing to Add ATM Connections into a Protection Group

After two connections are created, they cannot be added into a protection group. Hence, you need to configure the sink-source relation of the protection group.

Product

Fault Type

Equipment_Interconnection_Fault

Symptom

After creating two connections, you fail to add them into the protection group.

Cause Analysis

  • For 1+1 protection type:
    • In the case of source protection, the working and protection links must have the same sink but different sources.
    • In the case of sink protection, the working and protection links must have the same source but different sinks.
    • In the case of source + sink protection, the working and protection links must have different sinks and different sources.
  • For 1:1 protection, the working and protection links must have different sinks and different sources.

Procedure

  1. Determine the relation between the source and sink of the protection group. After changing the connections, add them into the protection group again.

Service Interruption After Enabling the Shaping Function of the N1EMS4 Board

After the shaping function of the N1EMS4 board is enabled for egress port queues, the services are interrupted.

Fault Type

  • RPR
  • Ethernet fault
Configuration problem

Symptom

Figure 1 shows the VCTRUNK-shared EVPL service between NE2 and NE3.
Figure 1 Configuration of the VCTRUNK-shared EVPL service
Two pairs of users (D and D', and E and E') share the 300 Mbit/s bandwidth of VCTRUNK1.
  1. Create a flow of the Port type for PORT1 and PORT2 separately.
  2. Create a CoS of the simpletype. Groom the port flow of PORT1 to queue 1 of VCTRUNK1, and groom the port flow of PORT2 to queue 3 of VCTRUNK1.
  3. Enable the traffic shaping function for queue 3 of VCTRUNK1. Set the CIR to 300 Mbit/s.
  4. Enable the traffic shaping function for queue 1 of VCTRUNK1. Use the default shaping parameter values.
Now if the traffic that enters PORT2 reaches a rate of 300 Mbit/s, the service of PORT1 is interrupted. Hence, although certain remaining bandwidth is available, it cannot allocated to queue 1.

Cause Analysis

This problem has the following possible causes.
  1. In this fault case, the priority of queue 3 is higher than the priority of queue 1. As a result, the packets of the higher priority queue 3 occupy the entire 300 Mbit/s bandwidth, and there is no remaining bandwidth for the lower priority queue 1. Consequently, the service between D and D' is interrupted.
  2. The shaping function is enabled for queue 1, but the shaping bandwidth is not set. As the default shaping bandwidth is 0, the service is interrupted.

Procedure

  1. Cause 1: The packets in queue 3 of higher priority occupy all the available bandwidth.
    1. Decrease the bandwidth of the higher priority queue 3.
      1. On the Main Topology, right-click the NE icon and choose NE Explorer from the shortcut menu.
      2. Select the relevant Ethernet board in the Object Tree. Choose Configuration > QoS Management > Port Shaping Management from the Function Tree.
      3. Set the committed information rate (CIR) and burst size (less than 300 Mbit/s).
  2. Cause 2: The shaping function is enabled for queue 1, but the committed bandwidth (CIR) of the shaping function is not set.
    1. Set the shaping bandwidth for queue 1.
      1. On the Main Topology, right-click the NE icon and choose NE Explorer from the shortcut menu.
      2. Select the relevant Ethernet board in the Object Tree. Choose Configuration > QoS Management > Port Shaping Management from the Function Tree.
      3. Select queue 1, and then set the relevant parameters for the queue.

Similar Problems

After a flow is bound with a CAR, the service is interrupted. The possible cause is that, although the CAR is enabled, the CIR and PIR (which are both 0 by default) are not set for the CAR.

Why Automatical configuration backup cannot work on S5700

Wednesday, June 29, 2016

LPT Switching Fails Due to Inconsistency of LPT Bearer Mode

If the LPT bearer modes of the ports at both ends are inconsistent, LPT switching may fail. Hence, ensure that the LPT bearer modes of the ports at both ends are consistent.

Product

Fault Type

  • LPT
  • Fault in the Ethernet

Symptom

In the case of R006 or earlier versions, LPT fails to work normally when the EFS board interconnects with the EMS4 board. After the service at the SDH layer is disconnected, automatic switching can be normally performed at both ends. After the network cable is removed from an Ethernet port, automatic switching at the opposite end fails.

Cause Analysis

In the case of version R006 or earlier than R006, the LPT function of the EFS board supports the MAC bearer mode only whereas the EMS4 board supports the GFP bearer mode only. Hence, the EFS and EMS4 boards fail to interconnect with each other due to different LPT bearer modes after the LPT function is enabled.

Procedure

  1. Modify the LPT bearer modes of the ports at both ends to be the same.

Reference Information

In the case of R006 or earlier versions, do not interconnect the EFGS boards with the EMS4 boards after the LPT function is enabled.


How to Change the Link Type of an Interface?