nxos

Nexus Virtual Device Contexts (VDCs) vitualize physical hardware (like contexts in ASA) also vitualize control plane protocols. Separate control plane per VDC (vlan 10 in VDC 1 is not vlan 10 in VDC 2) Each VDC has its own: Management plane Control plane Data plane Why use VDC: multiple logical roles (Core & Distribution on the same box) VDCs as a managed service to customers lab enviroment for later production use some features can not co-exist in the same VDC (OTV and SVIs) VDC limitations:...

NX-OS supports aliases “cli alias name <name of alias> <command>” conf t cli alias name wr copy run star** => can use “wr” to save config NX-OS also supports multiple commands aliases. Use “;” as separator: conf t cli alias name commit end ; copy run start ; copy running-config bootflash:///$(SWITCHNAME).$(TIMESTAMP.cfg IOS range command CTRL+0 => clear the screen Tab to complete the command Admins of efault VDC can verify or save config in all VDCs: show run vdc-all copy run start vdc-all NX-OS has checkpoints - save well known working config before the maintenance window start....