Trying to perfect my PnP config's and have been added features. Got 8 devices in lab, 3 routers and 5 switches (including a 4 member switch stack). Had successfully able to deploy image upgrades and basic configuration templates. Moving on to assigning ip addresses' and non-vlan1 configurations + ether channel configurations.
Running into this error that have changed the switching configuration to include management vlan with basic default route. Got the pnp startup-vlan XX command on the upstream switch. One of the switches get configured correctly with the static management vlan and ip. The other ones come back with and error in APIC-EM controller about not being able to manage the device due to a time out (see error below). Found a bug ID with this error .
https://bst.cloudapps.cisco.com/bugsearch/bug/CSCuy57714/?referring_site=bugquickviewredir
Error message in the project page:
#######################################
Failed health check since device is stuck in non-terminal state PROVISIONING_CONFIG for more than threshold time: 0 hours, 16 minutes, 0 seconds
#######################################
After waiting for the configuration to deploy, if I log in the console I see this message and the job error's out in APIC-EM. If I enter no to the prompt I can see the configuration was delivered to the switch with the exception of enabling SSH.
#######################################
--- System Configuration Dialog ---
Enable secret warning
----------------------------------
In order to access the device manager, an enable secret is required
If you enter the initial configuration dialog, you will be prompted for the enable secret
If you choose not to enter the intial configuration dialog, or if you exit setup without setting the enable secret,
please set an enable secret using the following CLI in configuration mode-
enable secret 0 <cleartext password>
----------------------------------
Would you like to enter the initial configuration dialog? [yes/no]:
There are a couple of reasons this might occur. It depends on what model switch are you using and which version of code is it booting with.
Also, when doing testing, it is important that you "clean up" the device properly...
Here is a "full clean up" (as well as wr er) for a stack.
# remove the certificates on active and standby
delete /force nvram:*.cer
delete /force stby-nvram:*.cer
# remove vlan data based from active and standby
delete /force flash-1:vlan.dat
delete /force flash-2:vlan.dat
# remove certificates from memory. NOTE: you will not be able to SSH after this
conf t
crypto key zeroize
yes
end
you need to have "end" as the last line of the config file
this error message is an indication
000047: Nov 7 15:44:20 PST: %PARSER-4-BADCFG: Unexpected end of configuration file.
Check to have vlan 1 configured on this device. Are you using it as the logging source.
logging source-interface Vlan1
If pnp startup-vlan does the right thing, you should have vlan 1 shutdown, vlan 107 enabled, and any active interfaces in vlan 107.
Check if you can see vlan 107 being created in the pnp logs.
Or it could be like a config file issue. you should be able to ping the default gateway from the switch as it is in the same vlan. If not, need to check that the vlan is being trunked between the two switches.
Comments
0 comments
Please sign in to leave a comment.