Cisco 9K Switch - Reload timer - delay

[RG78874]

Hello All,

I have a test failover scenario. I want to reload a device and delay the time it takes to come back up.

So far the command I have is

reload timer 3600

I want to reload > wait 20 minutes > then the device will come back up.

Can anyone help with this please.

[Reza Sharifi]

Hi,

I am not sure if there is a command that can make the switch reboot, wait 20 minutes, and then come back up. Once the timer expires (3600 minutes in your case), the switch will reboot and comes backup after going through the boot sequance.

HTH

[MHM Cisco World]

This standalone or vPC ?

If it standalone then I think using EEM with kron will solve this issue.

https://yurisk.info/2011/06/22/cisco-how-to-schedule-an-unattended-reload-with-eem/

This example for Router but it same for SW.

MHM

[RG78874]

This Switch has vpc's on it, i just checked some port configs. But not every port has a vpc i don't think.

[RG78874]

I need to simulate a failed device for a test, the testers need around 20 mins downtime, but I cannot physically get to the device.

[MHM Cisco World]

If you have two vPC and you need to test down of one and failover to second NSK you can try shut peer-link and keepalive.

The secondary vPC will take rule and forward traffic.

If you test otherthing please can ypu more elaborate 

MHM

[RG78874]

So i've looked into this a little more, the scenario is to simulate one nexus access switch going down, and traffic should automatically flow through the other device. This has to be done remotely because no one is at the DC.

I'm not familiar with Nexus 9k setup so i am learning on the go as much as I can.

So shutting the peer link I am hoping will work, but knowing how to do this and finding this peer link, i've got my work cut out. I appreciate any help on this and commands if possible. Thank you. Planning on doing some sort of labs related to this if I can.

[MHM Cisco World]

Sure you need LAB and test all failure point 
this series LAB for you and for other read this post and need to learn about the NSK 
LAB1 
we will test 
shut the keepalive first 
shut the Peer-link 

this Keepalive and Peer-link is UP 

 Keepalive is shut in NXOS2 (it not matter if you shut it in NXOS2 or 3)

here we shut the peer-link 
we see that the role of secondary is change to be operational primary
this called split brain now each NSK assume it primary of vPC

NOW we no shut the peer-link and keepalive 
split brain is end but the OLD primary NSK not returning to it status it now work as secondary 

[MHM Cisco World]

Lab 2 
shut the Peer-link first then 
shut the keepalive 

here the difference between shut the keepalive first or shut the peer-link first 
when we shut the peer-link first the Secondary (operational not admin) is show down all SVI interface for vPC-VLAN, 
where in first example when we shut the keepalive this step not happened. 

Here both is shut the peer-link and keepalive

[liviu.gheorghe]

I think the feasible solution to solve this situation is to configure an EEM script on the remote Nexus to shut down the vPC peer link and maybe other links as well depending on your topology and bring them up again after 20 minutes.

You should test the EEM script in a lab before deploying it in the remote DC Nexus switch.

[RG78874]

thanks I'm going to have a look into this. Any commands or steps to shut down a vpc link so I know I am on the right path?

i've watched some youtube videos which have helped to find the vpc link.

[liviu.gheorghe]

You can use the show vpc command to identify the vPC Peer-links:

nx9000# show vpc
Legend:
(*) - local vPC is down, forwarding via vPC peer-link

vPC domain id : 1
Peer status : peer link is down
vPC keep-alive status : Suspended (Destination IP not reachable)
Configuration consistency status : failed
Per-vlan consistency status : success
Configuration inconsistency reason: Consistency Check Not Performed
Type-2 inconsistency reason : Consistency Check Not Performed
vPC role : none established
Number of vPCs configured : 2
Peer Gateway : Disabled
Dual-active excluded VLANs : -
Graceful Consistency Check : Disabled (due to peer configuration)
Auto-recovery status : Disabled
Delay-restore status : Timer is off.(timeout = 30s)
Delay-restore SVI status : Timer is off.(timeout = 10s)
Delay-restore Orphan-port status : Timer is off.(timeout = 0s)
Operational Layer3 Peer-router : Disabled
Virtual-peerlink mode : Disabled

vPC Peer-link status
---------------------------------------------------------------------
id Port Status Active vlans
-- ---- ------ -------------------------------------------------
1 Po1 up -

vPC status
----------------------------------------------------------------------------
Id Port Status Consistency Reason Active vlans
-- ------------ ------ ----------- ------ ---------------
2 Po2 down failed Peer-link is down -

3 Po3 down failed Peer-link is down -

Please check "show vpc consistency-parameters vpc <vpc-num>" for the
consistency reason of down vpc and for type-2 consistency reasons for
any vpc.

You can see in this example the vPC Peer-link is interface Po1.

[RG78874]

Thank you all for your help, I will try this out and then update back, hopefully at some point this week.