Filter
Top Products
2-69
Cisco ONS 15310-CL and Cisco ONS 15310-MA Troubleshooting Guide, R7.0
Chapter 2 Alarm Troubleshooting
2.7.103 HELLO
The GFP User Payload Mismatch is raised against Fibre Channel/FICON ports supporting GFP. It occurs
when the received frame user payload identifier (UPI) does not match the transmitted UPI and all frames
are dropped. The alarm is caused by a provisioning error, such as the port media type not matching the
remote port media type. For example, the local port media type could be set to Fibre Channel—1 Gbps
ISL or Fibre Channel—2 Gbps ISL and the remote port media type could be set to FICON—1 Gbps ISL
or FICON—2 Gbps ISL.
Note For more information about Ethernet cards, refer to the Cisco ONS 15310-CL and Cisco ONS 15310-MA
Ethernet Card Software Feature and Configuration Guide.
Clear the GFP-UP-MISMATCH Alarm
Step 1 Ensure that the transmit port and receive port are identically provisioned for distance extension by
completing the following steps:
a. Double-click the card to display the card view.
b. Click the Provisioning > Port > Distance Extension tabs.
c. Check the check box in the Enable Distance Extension column.
d. Click Apply.
Step 2 Ensure that both ports are set for the correct media type. For each port, complete the following steps:
a. Double-click the card to display the card view (if you are not already in card view).
b. Click the Provisioning > Port> General tabs.
c. Choose the correct media type (Fibre Channel - 1Gbps ISL, Fibre Channel - 2 Gbps ISL,
FICON - 1 Gbps ISL, or FICON - 2 Gbps ISL) from the drop-down list.
d. Click Apply.
Step 3 If the GFP-UP-MISMATCH alarm does not clear, log into the Technical Support Website at
http://www.cisco.com/techsupport for more information or call Cisco TAC (1-800-553-2447) to report
a Service-Affecting (SA) problem.
2.7.103 HELLO
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Object: OCN
The Open Shortest Path First (OSPF) Hello alarm is raised when the two end nodes cannot bring an
OSPF neighbor up to the full state. Typically, this problem is caused by an area ID mismatch, and/or an
OSPF HELLO packet loss over the DCC.
Clear the HELLO Alarm
Step 1 Ensure that the area ID is correct on the missing neighbor by completing the following steps:
a. In node view, click the Provisioning > Network > OSPF tabs.