H3C SOHO IE4300, Справочник по командам

Страница: 1264 / 3296

63
specified LSA on both ends (Interface: Vlan10, peer address:
10.1.1.1; LSA type: 5, LSID: 91.1.1.0, AdvRouter: 5.5.5.5).
•
The state of OSPF 1 peer 1.1.1.1 changed to EXSTART
because the LSA requested and then learned is older than that
in local. Please check the OSPF request queue and the
specified LSA on both ends (Interface: Vlan10, peer address:
10.1.1.1; LSA type: 5, LSID: 91.1.1.0, AdvRouter: 5.5.5.5).
•
The state of OSPF 1 peer 1.1.1.1 changed to EXSTART
because a SeqNumberMismatch event was triggered upon the
receipt of a non-retransmitted DD packet from the Loading or
Full peer during the DD retransmit interval. Please check the
OSPF peer state and LSDB on the remote end (Interface:
Vlan10, peer address: 10.1.1.1).
•
The state of OSPF 1 peer 1.1.1.1 changed to EXSTART
because a SeqNumberMismatch event was triggered by the
change of the OSPF peer’s capability to external attribute.
Please check the DD packets transmitted on both ends
(Interface: Vlan10, peer address: 10.1.1.1).
•
The state of OSPF 1 peer 1.1.1.1 changed to EXSTART
because a SeqNumberMismatch event was triggered by the
OSPF peer’s multi-topology attribute change. Please check
the multi-topology capability configuration on the remote end
(Interface: Vlan10, peer address: 10.1.1.1).
•
The state of OSPF 1 peer 1.1.1.1 changed to EXSTART
because a SeqNumberMismatch event was triggered upon the
receipt of a retransmitted DD packet from the Loading or Full
peer after the DD retransmit interval expired. Please check the
OSPF peer state and LSDB on the remote end (Interface:
Vlan10, peer address: 10.1.1.1).
•
The state of OSPF 1 peer 1.1.1.1 changed to EXSTART
because a SeqNumberMismatch event was triggered by the
change of the OSPF peer’s capability to receive AS external
LSA. Please check the area configuration (Interface: Vlan10,
peer address: 10.1.1.1).
•
The state of OSPF 1 peer 1.1.1.1 changed to EXSTART
because a SeqNumberMismatch event was triggered by the
master-slave relationship change. Please check the DD
packets transmitted on both ends (Interface: Vlan10, peer
address: 10.1.1.1).
•
The state of OSPF 1 peer 1.1.1.1 changed to EXSTART
because a SeqNumberMismatch event was triggered upon the
receipt of an unexpected initial DD packet after DD
transmission started. Please check the DD packets
transmitted on both ends (Interface: Vlan10, peer address:
10.1.1.1).
•
The state of OSPF 1 peer 1.1.1.1 changed to EXSTART
because a SeqNumberMismatch event was triggered upon the
receipt of a DD packet with a wrong sequence number from
the slave. Please check the DD packets transmitted on both
ends (Interface: Vlan10, peer address: 10.1.1.1).
•
The state of OSPF 1 peer 1.1.1.1 changed to EXSTART
because a SeqNumberMismatch event was triggered upon the
receipt of a DD packet with a wrong sequence number from
the master. Please check the DD packets transmitted on both
ends (Interface: Vlan10, peer address: 10.1.1.1).
•
The state of OSPF 1 peer 1.1.1.1 changed to EXSTART
because a SeqNumberMismatch event was triggered upon the
receipt of a DD packet containing local opaque LSA without
enabling the opaque capability. Please check the specified
LSA on the remote end and the opaque capability
configuration on both ends (Interface: Vlan10, peer address:
10.1.1.1).