Users Guide

Table 148. Configuring delay-restore orphan ports
Steps Command Description
1
OS10# configure terminal
Enters Configuration mode.
2
OS10(config)# interface
ethernet 1/1/1
Enters Interface configuration mode.
3
OS10(conf-if-eth1/1/1)# vlt
delay-restore orphan-port
enable
Enables delay-restore orphan port.
4
OS10(conf-if-eth1/1/1)# exit
Exits Interface configuration mode and
enters Configuration mode.
5
OS10(conf)# vlt-domain 1
Enters VLT domain mode.
6
OS10(conf-vlt-1)# delay-
restore 150
Configures VLT delay-restore timer to
150 seconds. This command enables the
VLT delay-restore timer to control the
orphan ports.
After you configure delay-restore orphan ports on both the VLT peers, the behavior of the port in different scenarios are
explained below:
Fresh VLT configuration
● If VLT is not configured earlier, the ethernet1/1/1 interface is up on both the nodes.
● When VLT is configured on both peers, VLT election occurs.
● In the primary VLT peer, ethernet1/1/1 remains up.
● In the secondary VLT peer, ethernet1/1/1 is brought down and delay-restore is started. A log indicating that the VLT
delay-restore has started is thrown on console.
● The ports are brought up after delay-restore timer expires. A syslog indicating that the VLT delay-restore timer has stopped
is thrown on the console.
NOTE:
A fresh VLT configuration is treated the same way as a reload case. All configured orphan ports irrespective of the
ignore vlti-failure configuration are brought down.
NOTE: If VLT and DROP are configured in a system for the first time (or being converted from DRP), DROP is configured
after the VLT election and after the initial delay-restore timer expires. This configuration must be applied if you do not want
the orphan ports to be brought down.
VLT peer reloads and joins as secondary (single VLT peer save and reload):
● During boot up, ethernet1/1/1 is kept down.
● After the VLT domain is created locally and the VLT peer joins the VLT fabric as the secondary node, the VLT delay-restore
timer is started. A syslog indicating that the VLT delay-restore has started is thrown on console.
● After expiry, the ports are brought up. A syslog indicating that the VLT delay-restore timer has stopped is thrown on the
console.
Reloading both Peers:
● During boot up, ethernet1/1/1 in both the nodes is kept down.
● VLT domain is created and election occurs.
● Ethernet1/1/1 is brought up immediately in the primary VLT peer.
● In the secondary VLT peer, ethernet1/1/1 remains down and delay-restore timer is started. A syslog indicating that the
delay-restore timer has started is thrown on the console.
● After the delay-restore timer expires, a syslog is thrown on the console and the port is brought up.
VLTi fail with heart-beat configured and up:
● If VLTi fails and the VLT heart-beat is up, ethernet1/1/1 is brought down (since ignore vlti-failure configuration is disabled)
immediately in the secondary VLT peer.
● When VLTi recovers, the delay-restore timer starts and a syslog is thrown indicating that the timer has started is thrown on
the console.
● After the delay-restore timer expires, ethernet1/1/1 is brought up and a syslog is thrown on the console.
● Ethernet1/1/1 is up in the primary VLT peer.
VLTi fail with heart-beat not configured or down:
1640
Virtual Link Trunking