Hi, I have bought an 9216i, but the password is lost. I found a recovery procedure which points out to press cntl-J to stop the boot and get a prompt. This does not work. Pressing CNTL-C when booting does work, it gets me in the BIOS of the switch. Can someone tell me what I am doing wrong?
MDS 9216i with only 14-2 module
Using a standard (networking) console cable from a catalist or such.
I did the upgrade btw from 2.0.3 to 3.0.1, but does that influence licensing? I seem to have "lost" the SAN_EXTN_OVER_IP_9216i entry in the license list. It was licensed in 2.0.3. Additionally, I read that the enterprise license is standard on these switches, but I seem to have a 120 day "grace" license? It is not totally clear to me what functionality my switch now does or does not have...
All of the columns show "Unused". This means you are not using any licensed features, so you dont need to buy any license. The Enterpise pkg has 119 days grace, so it looks like you must have enabled an Enterprise feature briefly and then disabled it. The grace should stay at 119D while it is 'unused'. Next time you enable an Enterprise feature the grace will resume countdown.
Enterpise license is not standard on 9216i. Also you do not need any license to do FCIP using the two built in GE ports of 9216i, or IVR over FCIP using the built-in ports.
Dear i have a problem with the password recovery for MDS 9140. I have used the procedure of break sequence Crtl+] with no sucsess. I have tried another compinations but with no sucsess also. According to the document attached
You must perform the password recovery procedure on the Supervisor Engine module that will become the active Supervisor Engine module after completion of the recovery procedure. In order to ensure that the other Supervisor Engine module does not become the active module, perform one of these two options:
Physically remove the other Supervisor Engine module from the chassis.
Change the console prompt of the other Supervisor Engine module to one of these two prompts until you complete the procedure:
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...