I followed the procedure but it looks like we did not wait long enough into the boot sequence. From past experience I am used to getting into ROMMON early on when the device begins to load. It seems on the Nexus that it is further along in the boot sequence, after POST, that your able to break into ROMMON. The maintenance window we had has closed so I'm waiting for the powers that be to schedule another outage.
I am having a hell of a time finding the right moment to press <CTL>-]
Here's an example. Can someone help me understand at what exact moment I press the key sequence? This is a new switch for me, yesterday I removed it from the box and entered the initial configuration dialog. I set my password ( I'm using: a5I*Wf+R*mq\At"| ) maybe that combination of characters is a part of the problem? PS: I will of course use a different password now!
GRUB Loading stage2 [ 0.000000] Fastboot Memory at 0c100000 of size 2013265922.U2.2.bin.... ÿUsage: init 0123POST INIT Starts at Tue Sep 9 16:51:24 UTC 2014 Starting Nexus 3000 Platform POST..... Executing Mod 1 1 SEEPROM Test:...done (0 seconds) Executing Mod 1 1 GigE Port Test:.done (8 seconds) Executing Mod 1 1 PCIE Test:.................done (0 seconds) Mod 1 1 Post Completed Successfully POST is completed .... done. Loading System Software Tue Sep 9 16:51:43 UTC 2014 ^] <---( I pressed ctl-] right at this moment ) System Software(/bootflash/n3000-uk22.214.171.124.U2.2.bin) Loaded Tue Sep 9 16:52:00 U TC 2014 ethernet switching mode INIT: Entering runlevel: 3 Mounting other filesystems: [ OK ]
Set name-type for VLAN subsystem. Should be visible in /proc/net/vlan/config Added VLAN with VID == 4042 to IF -:muxif:- 2014 Sep 9 16:52:07 BLM-80-A-2-41-CoreSwitch %$ VDC-1 %$ %USER-0-SYSTEM_MSG: FA ST REBOOT DISABLED - bcm_usd 2014 Sep 9 16:52:07 BLM-80-A-2-41-CoreSwitch %$ VDC-1 %$ %USER-2-SYSTEM_MSG: CL IS: loading cmd files begin - clis 2014 Sep 9 16:52:19 BLM-80-A-2-41-CoreSwitch %$ VDC-1 %$ %USER-2-SYSTEM_MSG: CL IS: loading cmd files end - clis 2014 Sep 9 16:52:19 BLM-80-A-2-41-CoreSwitch %$ VDC-1 %$ %USER-2-SYSTEM_MSG: CL IS: init begin - clis 2014 Sep 9 16:52:49 BLM-80-A-2-41-CoreSwitch %$ VDC-1 %$ %USER-0-SYSTEM_MSG: St arting bcm_attach - bcm_usd 2014 Sep 9 16:53:04 BLM-80-A-2-41-CoreSwitch %$ VDC-1 %$ %USER-0-SYSTEM_MSG: Fi nished bcm_attach... - bcm_usd 2014 Sep 9 16:53:18 BLM-80-A-2-41-CoreSwitch %$ VDC-1 %$ %VDC_MGR-2-VDC_ONLINE: vdc 1 has come online
User Access Verification BLM-80-A-2-41-CoreSwitch login:
Ok, problem solved on a 3064 switch. I used aggressive ctl-C before the GRUB prompt and I moved from a minicom based network terminal to a direct attach laptop at the same console port. Then it was just following the instructions already mentioned.
Topology & Design:
Two ACI fabrics
Stretching VLANs using OTV
Both fabrics are advertising BD subnets into same routing domain
Some BDs(or say VLANs) are stretched, but some are not.
Endpoints can move betwee...
VMware Trunk Port Group is supported from ACI version 2.1
VMM integration must be configured properly
ASA device package must be uploaded to APIC
ASAv version must be compatible with ACI and device package version
Topology &Design:Traffic flow within same fabric:Endpoint moves to Fabric-2Bounce Entry Times OutTraffic Black-holedSummarySolutionAppendix:
In the Previous articles of ACI Automation, we are using Postman/Newman a...