Here's a Partially Successful device in Config Archive:
70. rtr1 PRIMARY STARTUP Feb 11 2009 07:06:15 Successful
71. rtr1 PRIMARY RUNNING Feb 11 2009 07:06:44 Couldnot enter ENABLE Mode from USER Mode on Device. Failed to fetch config using SCP.Administratively disabled. Verify SCP is enabled or not. TFTP: Failed to fetch config using TFTP.
72. rtr1 VLAN RUNNING Feb 11 2009 07:06:59 Couldnot enter ENABLE Mode from USER Mode on Device. VLAN Config fetch is not supported using SCP. VLAN Config fetch is not supported using TFTP.
I see the device is currently oddly asking for the username again when entering enable mode. I've been told it's a "new" feature in the particular IOS it's running. Is this why RME is thrown off unable to get the running and VLAN configs? Should it be able to deal with that?
User Access Verification
Also, how come RME does appear to retry after Feb 11?
It's bizarre, because if RME can't handle this. My transport methods are SSH, SCP, and TFTP only, in that order. I ran a Sync Archive against this device a couple of time. The first time it ended up the same as Feb. 11: Startup successful; Running "cannot get into ENABLE mode". The second time, it got the Running Config, and the device disappeared from the Failed list. So somehow RME was able to get the Running configs, but not consistently. Is it trying TFTP and failing most of the times?
I'd think ConfigMgmtServer is working correctly, if it's collecting fine for most of the devices.
This is actually a pretty cool feature, i didn't even know it existed until I was looking for a solution to advertise a subnet (prefix in BGP talk), only if a certain condition existed. This is exactly what conditional advertisements does
j ai une question j ai achete un routeur cisco 887VA-k9 , je le configuré avec la configuration ci- dessous
si je le lier avec mon pc portable sur l un de ses ports directement ça marche toute est bien ( la connexion internet + m...
Attached policy provides CLI access to the Cisco 4G router over text messaging. Two files are in the attached .tar file:
2. PDF with instructions on how to load and use the .tcl file.