Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

Archive management failures

Hi There

I get quite a lot of failures with archiving, I get the following message:

*** Device Details for my hostname ***

Protocol ==> Unknown / Not Applicable

CM0062 Polling my hostname for changes to configuration. CM0065 No change in PRIMARY STARTUP config, config fetch not required CM0065 No change in PRIMARY RUNNING config, config fetch not required CM00 Polling not supported on VLAN RUNNING config, defaulting to fetch. CM0151 VLAN RUNNING Config fetch failed for my hostname Cause: Command failedCommand failedVLAN Config fetch is not supported using SCP. Action: Check if protocol is supported by device and required device package is installed. Check device credentials. Increase timeout value, if required.

I'm using ssh to manage the devices and LMS2.6 with RME 4.0.6.

Regards

Patrick

1 ACCEPTED SOLUTION

Accepted Solutions
Cisco Employee

Re: Archive management failures

In order for vlan.dat to be fetched, you must allow either SSH or telnet to your device (sounds like you have this with SSH). You must also allow the device to TFTP the vlan.dat file back to the RME server. This requires udp/69 to be open between device and server as well as all ephemeral UDP ports.

2 REPLIES
Cisco Employee

Re: Archive management failures

In order for vlan.dat to be fetched, you must allow either SSH or telnet to your device (sounds like you have this with SSH). You must also allow the device to TFTP the vlan.dat file back to the RME server. This requires udp/69 to be open between device and server as well as all ephemeral UDP ports.

New Member

Re: Archive management failures

Thanks your correct. Did a test from the switch to the server and the firewall is blocking it.

190
Views
0
Helpful
2
Replies