LMS & Archive Mgmt Issue - VLAN RUNNING Config fetch failed

Answered Question
Mar 14th, 2009
User Badges:

Hello, Joe


I've a problem with the Archive Mgmt.

I've several routers - 2821, 3845 and switches 3750.

With the 2821 archive management works fine.

both for the 3845 routers and 3750 switches I get the status 'Partially Successful'.


Error msg for the switch

*** Device Details for WAN_Switch ***

Protocol ==> TFTP

Selected Protocols with order ==> Telnet,TFTP,SSH

Execution Result:

RUNNING

TELNET: Failed to establish TELNET connection to 10.253.0.253 - Cause: Authentication failed on device 3 times.

CM0061 PRIMARY RUNNING Config fetch SUCCESS for WAN_Switch, no change in configuration.

VLAN

CM0151 VLAN RUNNING Config fetch failed for WAN_Switch Cause: TELNET: Failed to establish TELNET connection to 10.253.0.253 - Cause: Authentication failed on device 3 times.

VLAN Config fetch is not supported using TFTP.

Could not detect SSH protocols running on the device

Action: Check if protocol is supported by device and required device package is installed. Check device credentials. Increase timeout value, if required.


Error msg for the 3845 router

Device: 3845-1 Status: Partially Successful

*** Device Details for 3845-1 ***

Protocol ==> TFTP

Selected Protocols with order ==> Telnet,TFTP,SSH

Execution Result:

RUNNING

TELNET: Failed to establish TELNET connection to 10.253.0.120 - Cause: Authentication failed on device 3 times.

CM0061 PRIMARY RUNNING Config fetch SUCCESS for 3845-1, no change in configuration.

VLAN

CM0151 VLAN RUNNING Config fetch failed for 3845-1 Cause: TELNET: Failed to establish TELNET connection to 10.253.0.120 - Cause: Authentication failed on device 3 times.

VLAN Config fetch is not supported using TFTP.

Could not detect SSH protocols running on the device

Action: Check if protocol is supported by device and required device package is installed. Check device credentials. Increase timeout value, if required.

Telnet and snmp settings are the same for 28xx, 38xx and 3750.

The transport protocols are Telnet, Tftp and SSH.


What is wrong?

LMS version -3.1

RME version -4.2.0

Regards


Correct Answer by Joe Clarke about 8 years 4 months ago

The telnet credentials for these devices are most likely wrong in DCR. The reason the running config is fetched successfully is that RME falls back to TFTP/SNMP, and this works. However, the vlan.dat cannot be fetched in this way. RME MUST be able to login to the device using either telnet or SSH, and then copy the file back to the RME server using TFTP.


Make sure the DCR telnet and enable credentials are correct for these devices, and use a sniffer trace filtering on telnet traffic during a sync archive to see what's actually happening if you still see a problem.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (2 ratings)
Loading.
Correct Answer
Joe Clarke Sat, 03/14/2009 - 14:07
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

The telnet credentials for these devices are most likely wrong in DCR. The reason the running config is fetched successfully is that RME falls back to TFTP/SNMP, and this works. However, the vlan.dat cannot be fetched in this way. RME MUST be able to login to the device using either telnet or SSH, and then copy the file back to the RME server using TFTP.


Make sure the DCR telnet and enable credentials are correct for these devices, and use a sniffer trace filtering on telnet traffic during a sync archive to see what's actually happening if you still see a problem.

varnavsky Sat, 03/14/2009 - 23:25
User Badges:

Unfortunately, for now I can not use a sniffer trace.

Device credentials are the same for all equipment. It's very strange that from 28xx routers RME can fetch config/vlan.dat and from 38xx it can not... ((

I've solved this issue by deleting problem devices from the DCR, then discoverying and adding these routers and switches to DCR again. After this everything works fine.

Thanks!

Joe Clarke Sat, 03/14/2009 - 23:41
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

The 2800s don't have a vlan.dat, and RME doesn't try to fetch it. They must have been falling back to TFTP as well. Since there was no vlan.dat to fetch, RME was able to successfully fetch all supported configurations.

varnavsky Sun, 03/15/2009 - 23:45
User Badges:

jclarke,

2800s have a vlan.dat =)


2821_1#show flash:

-#- --length-- -----date/time------ path

1 51308320 Jan 23 2009 19:15:16 +10:00 c2800nm-advipservicesk9-mz.124-15.T8.bin

2 660 Feb 9 2009 18:35:34 +10:00 vlan.dat


76861440 bytes available (51314688 bytes used)

Joe Clarke Sun, 03/15/2009 - 23:51
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

Ah, this router has a switching module, I take it. While the 2800 may have a vlan.dat, RME will not try to fetch it. The instrumentation for 2800 series devices match that of a standard router where as the 3800 instrumentation matches that of an IOS switch.

Actions

This Discussion