22.05.2017 Views

nx.os.and.cisco.nexus.switching.2nd.edition.1587143046

Nexus Switching 2nd Edition

Nexus Switching 2nd Edition

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Other supervisor (sup-5)<br />

------------------------<br />

Redundancy state: St<strong>and</strong>by<br />

Supervisor state:<br />

Internal state:<br />

HA st<strong>and</strong>by<br />

HA st<strong>and</strong>by<br />

System start time: Fri May 4 07:42:43 2012<br />

System uptime:<br />

128 days, 9 hours, 21 minutes,<br />

1 seconds<br />

Kernel uptime:<br />

128 days, 9 hours, 25 minutes,<br />

42 seconds<br />

Active supervisor uptime: 0 days, 0 hours, 7 minutes, 39<br />

seconds<br />

Nonstop Forwarding<br />

M<strong>os</strong>t modern protocols underst<strong>and</strong> that while a control plane switchover might be occurring<br />

on an adjacent node, the data plane can still forward traffic. The m<strong>os</strong>t common<br />

implementations of this functionality are with OSPF, EIGRP, <strong>and</strong> BGP. These mechanisms<br />

are sometimes referred to as a graceful restart. This should not be confused with a stateless<br />

restart; a stateful restart requires no interaction with peers, whereas a graceful restart<br />

involves notification of peers.<br />

If a stateful restart of the routing process fails, or is not p<strong>os</strong>sible, nonstop forwarding (NSF)<br />

specifies a mechanism to notify neighbors that the control plane is undergoing a restart, but<br />

the data plane can still forward traffic. All routing updates from this neighbor are held in<br />

their current states until the adjacency is restored or a hold timer expires. When the<br />

adjacency is reestablished, updates to the routing topology are then updated in the hardware<br />

forwarding tables. For NSF to work properly, the adjacent network devices must process<br />

the notification, in which case they are said to be NSF-Aware. M<strong>os</strong>t modern networking<br />

devices, including IOS <strong>and</strong> NX-OS, are NSF-Aware.<br />

In-Service Software Upgrades<br />

With the combination of the distributing forwarding nature of the Nexus platform <strong>and</strong> the<br />

high-availability features described within this chapter, one of the m<strong>os</strong>t immediate <strong>and</strong><br />

practical benefits of the approach is the capability to upgrade software without requiring a<br />

reload of the system or disruption to traffic flows through the system. This capability is<br />

referred to as In-Service Software Upgrades (ISSU), which is supported acr<strong>os</strong>s both minor<br />

<strong>and</strong> major NX-OS versions <strong>and</strong> enables customers to quickly take advantage of new<br />

features, protect their infrastructure against security vulnerabilities, <strong>and</strong> provide a more<br />

proactive software upgrade cycle, all while not having to wait for extended maintenance<br />

windows or c<strong>os</strong>tly downtime. Prior to initiating a software upgrade, an administrator should

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!