Nexus Notes ~ Continued

DCNM - Data Center Network management

Configuration Rollback-

This feature enables you to take a snapshot or checkpoint of the current
running configuration and re-apply it at any point without the need to
reload.

3 Types of Configuration rollback

Atomic - Implement only if there are no errors

Best-Effort - Implement a roll back and skip any errors

Stop-at-first-failure - Implement a roll back and stop at the first error.

Limitations-

10 snapshots per VDC

You can not use one snapshot made in one VDC and apply it to the
configuration of another VDC

You can not apply a snapshot in a non-default VDC if there is a change to
the global configuration

Filename 75 characters or less

You can not start the file name with AUTO or SUMMARY

A write erase and reload destroys the snapshot

To change which VDC you are in

#switchto vdc

To create a snapshot

#checkpoint <snapshot-filename>

To rollback to a checkpoint

#rollback running-config checkpoint <snapshot-filename>

If you do not have dual supervisors in the N7k, you cant use the ISSU

VDCs cant be shut down and restarted.

Steps needed to create a VDC and assign resources to it:

Note: VDC(s) are always created from the default admin VDC context (VDC 1)

#vdc <name of VDC>

Allocate interfaces to a VDC

#vdc <name>

#allocate interface ethernet1/17

#show vdc membership

Connectivity Management Processor-

Supports remote management and troubleshooting of the complete system.
This provides complete out-of-band management that is completely
independent independent from the primary OS. It has its own processor,
memory and bootflash and even a separate ethernet management port.

#attach cmp