We are getting failures on our archive management job for all of our Voice Gateway (VG) devices. Do we need to put some sort of config on the VGs or is it something on the CiscoWorks side?
Here is the job log detail.
Protocol ==> Unknown / Not Applicable
CM0056 Config fetch failed for 10.xx.xx.xx Cause: CM0204 Could not create DeviceContext for 806 Cause: CM0206 Could not get the config transport implementation for 10.xx.xx.xx Cause: UNKNOWN Action: Check if required device packages are available in RME. Action: Check if protocol is supported by device and required device package is installed.
I am new to CiscoWorks, so after doing some poking around I found that I may need to download a package update for our devices. The only package update that I see for VGs is VG224 (sysObjectID 220.127.116.11.18.104.22.168.558). Would this work for VG 202 and VG 204?
You can't. System config collection runs on all devices. You could, however, disable the system job, and create a Sync Archive job using the Group Selector (see the radio button above the Device Selector). When you do that, the job will run on all devices in the selected group(s) even if new devices are added.
We have 3 identical switches configured by someone else and would like to claim some of the Gigabit ports(G1/G2/G3/G4) for use on servers. When we try to change the wiring and configuration, we run in to connectivity issues. Attached is a des...
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...