Problem and solution when the USG2000 and USG5000 series can properly work only after the undo shutdown command is executed on the interface

18

The interface has been manually disabled.

Other related questions:
After the shutdown and undo shutdown commands are used on a trunk member interface of an S6700, traffic is interrupted. Why
When the shutdown and undo shutdown commands are used on a trunk member interface of an S6700, the trunk bandwidth changes. The ifnet sends a port rate change event. MSTP responds to the event and delivers the Block flag to the outbound port. As a result, the outbound port cannot forward traffic. After 15s, MSTP delivers the forward flag to the port. Traffic can be forwarded. When the shutdown and undo shutdown commands are used on a trunk member interface of an S6700, traffic is interrupted for 15s.

Whether the USG2000 series can map ports after the nat server command is executed
USG2000 series cannot map ports after the nat server command is executed.

Problem and solution when the forward and reverse paths of sessions are inconsistent on the USG2000 and USG5000
Configure sticky load balancing on the device.

After the shutdown command is executed on an interface of an S series switch, an LSA sent by the switch still exists in the peer LSDB. Why
Question: Two devices are connected using a link. After the shutdown command is executed on an interface on one end of the link, an LSA sent by the interface still exists in the peer LSDB. Why? Answer: An LSA can be flooded only by the S series switch supporting OSPF that generates the LSA. When the peer switch has no reachable path to the local switch, new LSAs generated by the local switch will not be flooded to the peer. Therefore, the old LSA exists in the peer LSDB. It is not used in SPF calculation and ages with time.

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