How do I locate an OSPF fault

23

The debugging ospf event command can identify most of OSPF faults. If an OSPF fault cannot be located by this command, run the debugging ospf packet command to enable OSPF packet debugging and check whether OSPF packets are sent and received normally according to debugging information.

Other related questions:
Locate an OSPF fault on an S series switch
You can run the debugging ospf event command on S series switches supporting OSPF to locate most faults. If an OSPF fault cannot be located using this command, run the debugging ospf packet command to enable OSPF packet debugging and check whether OSPF packets are sent and received normally according to debugging information. Note: The debugging commands are used for fault location. Exercise caution when using the commands.

How do I locate VAP creation failures
To locate VAP creation failure on a WLAN device, perform the following steps: For an AC: V200R005 and earlier 1. Check whether the AP exists. 2. Check whether the VAPs of the AP are fully configured. 3. Check whether the radio interface is bound to a radio profile. 4. Check whether the service set is configured correctly and bound to the radio interface. 5. Check whether the configuration is committed. 6. Check whether the AP works properly and whether the configuration is delivered successfully. V200R006 and later 1. Check whether the AP exists. 2. Check whether the VAPs of the AP are fully configured. 3. Check whether the radio interface is bound to a radio profile. 4. Check whether the VAP profile is configured correctly and bound to the AP or an AP group. 5. Check whether the AP works properly and whether the configuration is delivered successfully. For a Fat AP: 1. Check whether the VAPs of the AP are fully configured. 2. Check whether the radio interface is bound to a radio profile. 3. Check whether the service set is configured correctly and bound to the radio interface. For an S series switch serving as the AC 1. Check whether the AP exists. 2. Check whether the VAPs of the AP are fully configured. 3. Check whether the radio interface is bound to a radio profile. 4. Check whether the service set is configured correctly and bound to the radio interface. 5. Check whether the configuration is committed. 6. Check whether the AP works properly and whether the configuration is delivered successfully.

Methods for locating MCA board faults
Question: The MCA board failed to scan the spectrum during a site deployment. MCA monitors 80 channels of four ports. All 320 channels reported the CHAN_LOS alarm. Analysis: 1. No input optical signal on all four ports of the MCA board. 2. The MCA board was faulty. Root cause: None Answer: 1. Detect the R01, R02, R03, and R04 ports of the MCA boards using a power meter and optical spectrum analyzer, and each port had optical power and normal waveforms were observed from the analyzer. 2. Use the following NE commands to check whether the configurations were correct: :cfg-set-monwave:bid,1,cband,1&&80,enable; (Channel 1 is used as an example, other channel can be used as well.) :cfg-get-monwave:bid,1,cband,0; :cfg-verify; (Verification must be performed.) :cfg-get-analydata:bid,1; MAC optical spectrum analysis data query :cfg-verify; Query results of ":cfg-get-analydata:bid,1; MAC optical spectrum analysis data query" for all channels were ?600, meaning that there were no optical signals on any ports. 3. According to previous steps, the MCA board was faulty. The board was unplugged for further analysis. a. Open the fireproof board. b. The module with five fibers at the front of the board is the optical switch. Among the five fibers, the white one is for input, which connects to the front panel; and the blue one is for output. Remove the end with the white fiber of the blue monolithic fiber adapter that is fixed on the board, input optical signals to any one of the R01 to R04 ports, and use the power meter to determine whether the blue fiber has output. When there is no output, confirmed whether the input is normal. If normal, then the optical switch or the fiber adapter is damaged. c. When there is output, confirm whether the OCM (optical spectrum analysis module) is faulty. Re-insert the end with the white fiber, and remove the end with the blue fiber. Connect the white fiber to the MON port of other boards, and make sure that the MON port has OTU wavelength and the fiber connection is correct. Reinsert the board to the subrack. After the board starts running, run the commands for optical port enabling, verifying, and wavelength analyzing. If the queried result of the MCA is still ?600, then the optical spectrum analysis module, the software, or the NE is faulty. For damaged optical switches or faulty optical spectrum analysis modules, replace the board. Suggestion and conclusion: To locate MCA faults, first confirm whether there are input optical signals, then confirm whether the data configurations are correct, and finally confirm whether the hardware is faulty.

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top