Troubleshooting ospfv3 configuration, No ospfv3 neighbor relationship established, Symptom – H3C Technologies H3C S12500 Series Switches User Manual
Page 356: Analysis, Solution
340
[SwitchC-ipsec-policy-manual-policy002-10] sa string-key inbound esp gfedcba
[SwitchC-ipsec-policy-manual-policy002-10] quit
4.
Apply the IPsec policies in areas:
# Configure Switch A.
[SwitchA] ospfv3 1
[SwitchA-ospfv3-1] area 1
[SwitchA-ospfv3-1-area-0.0.0.1] enable ipsec-policy policy001
[SwitchA-ospfv3-1-area-0.0.0.1] quit
[SwitchA-ospfv3-1] quit
# Configure Switch B.
[SwitchB] ospfv3 1
[SwitchB-ospfv3-1] area 0
[SwitchB-ospfv3-1-area-0.0.0.0] enable ipsec-policy policy002
[SwitchB-ospfv3-1-area-0.0.0.0] quit
[SwitchB-ospfv3-1] area 1
[SwitchB-ospfv3-1-area-0.0.0.1] enable ipsec-policy policy001
[SwitchB-ospfv3-1-area-0.0.0.1] quit
[SwitchB-ospfv3-1] quit
# Configure Switch C.
[SwitchC] ospfv3 1
[SwitchC-ospfv3-1] area 0
[SwitchC-ospfv3-1-area-0.0.0.0] enable ipsec-policy policy002
[SwitchC-ospfv3-1-area-0.0.0.0] quit
[SwitchC-ospfv3-1] quit
5.
Verify the configuration:
OSPFv3 traffic between Switches A, B and C is protected by IPsec.
Troubleshooting OSPFv3 configuration
No OSPFv3 neighbor relationship established
Symptom
No OSPFv3 neighbor relationship can be established.
Analysis
If the physical link and lower protocol work well, check OSPFv3 parameters configured on interfaces.
The two neighboring interfaces must have the same parameters, such as the area ID, network segment
and mask, and network type. If the network type is broadcast, at least one interface must have a DR
priority higher than 0.
Solution
1.
Display neighbor information using the display ospfv3 peer command.
2.
Display OSPFv3 interface information using the display ospfv3 interface command.
3.
Ping the neighbor router's IP address to check connectivity.