Thank you for correcting this:
>> SNMP only access from Routers/Switches
>> 1) can modify Router/Switch Configs from Cisco Works
>> 2) Archive of Router/Switch Configs to Cisco Works.
If I had SNMP & TFTP from the routers & switches to Cisco Works, The Archive Config process will detect a config change via SNMP and if a config has changed then SNMP will TFTP the startup config to the shadow directory?
CSCOpx\files\rme\dcma\shadow\Switches_and_Hubs\PRIMARY
Thanks
This has been updated.
Telnet. The Server that Cisco Works is running on, now can only access the routers and switches via SNMP v2 only. Network Devices are sysloging to Cisco Works, but not SNMP Trapping to Cisco Works.
No TFTP from/to Cisco Works
I am trying to come up with a list of items that are useless now in Cisco Works:
No SSH/Telnet access to Routers/Switches
1) no Configuration Versioning - Running config to Startup config or to various versions.
2) no Copying of the VLAN.dat file for backup, uses TFTP
3) no Copying of the IOS from flash for backup, uses TFTP
No SNMP Traps to Cisco Works
1) disables notifications to Cisco Works when a configuration change has been made, causing the new config to be archived promptly instead of waiting on the collection job to run.
2) Renders the User Tracking Tool basically useless, could track dot1X switch ports status and other info.
SNMP only access from Routers/Switches
1) cannot modify Router/Switch Configs from Cisco Works
2) cannot Archive of Router/Switch Configs to Cisco Works.
3) Only IPM, Cisco View, and a tiny piece of Campus Manager functionalities will function.
