LMS 3.2 on Solaris 10 - CatOS PVlan Mapping commands to MSFC not being saved by Ciscoworks

[josefribeiro]

Hi All,

We are doing some troubleshooting after the recovery of a Cat6500 Hybrid switch and we've encoutered something strange. It seems that Ciscoworks does not save the pvlan mapping statements applied to the MSFC (module 15 in this case). Below I have two excerpts. The first one is from an export of the latest saved config of a similar device. The other one is from the actual same switch.

Any ideas why this is happening?

Thanks

Jose Ribeiro

-----------------------------------------------------------------------------------------

-bash-3.00$ cat ctspitdcemsw303-172-raw.cfg | grep mapping
#Macro-Port mapping
#vlan mapping
set pvlan mapping 2100 2101 1/7
set pvlan mapping 2100 2103 1/7
set pvlan mapping 2100 2104 1/7
set pvlan mapping 2100 2106 1/7
set pvlan mapping 2100 2109 1/7
set pvlan mapping 2600 2603 5/11-12
set pvlan mapping 2600 2604 5/11-12
set pvlan mapping 2800 2801 5/4
set pvlan mapping 2800 2802 5/4
set pvlan mapping 2800 2803 5/4
set pvlan mapping 2800 2804 5/4
set pvlan mapping 2800 2805 5/4
set pvlan mapping 2800 2806 5/4
set pvlan mapping 2800 2807 5/4
set pvlan mapping 2800 2808 5/4
set pvlan mapping 2800 2809 5/4
set pvlan mapping 2300 2303 9/31
set pvlan mapping 2300 2304 9/31
set pvlan mapping 2600 2603 9/28
set pvlan mapping 2600 2604 9/28
-bash-3.00$

----------------------------------------------------------------------------------------

ctspitdcemsw303> (enable) sh runn | incl mapping
set pvlan mapping 2100 2101 1/7
set pvlan mapping 2100 2103 1/7
set pvlan mapping 2100 2104 1/7
set pvlan mapping 2100 2106 1/7
set pvlan mapping 2100 2109 1/7
set pvlan mapping 2600 2603 5/11-12
set pvlan mapping 2600 2604 5/11-12
set pvlan mapping 2800 2801 5/4
set pvlan mapping 2800 2802 5/4
set pvlan mapping 2800 2803 5/4
set pvlan mapping 2800 2804 5/4
set pvlan mapping 2800 2805 5/4
set pvlan mapping 2800 2806 5/4
set pvlan mapping 2800 2807 5/4
set pvlan mapping 2800 2808 5/4
set pvlan mapping 2800 2809 5/4
set pvlan mapping 2300 2303 9/31
set pvlan mapping 2300 2304 9/31
set pvlan mapping 2600 2603 9/28
set pvlan mapping 2600 2604 9/28
set pvlan mapping 2300 2303 10/35-36
set pvlan mapping 2300 2304 10/35-36
set pvlan mapping 2300 2305 10/35-36
set pvlan mapping 2300 2309 10/35-36
set pvlan mapping 2300 2303 11/34
set pvlan mapping 2300 2304 11/34
set pvlan mapping 2600 2603 11/12-13,11/38-39
set pvlan mapping 2600 2604 11/12-13,11/38-39
set pvlan mapping 2300 2303 12/45-46
set pvlan mapping 2300 2304 12/45-46
set pvlan mapping 2600 2603 12/41-44
set pvlan mapping 2600 2604 12/41-44
set pvlan mapping 2000 2001 15/1
set pvlan mapping 2000 2002 15/1
set pvlan mapping 2000 2003 15/1
set pvlan mapping 2000 2005 15/1
set pvlan mapping 2000 2009 15/1
set pvlan mapping 2200 2201 15/1
set pvlan mapping 2200 2202 15/1
set pvlan mapping 2200 2203 15/1
set pvlan mapping 2200 2208 15/1
set pvlan mapping 2300 2301 15/1
set pvlan mapping 2300 2302 15/1
set pvlan mapping 2300 2303 15/1
set pvlan mapping 2300 2304 15/1
set pvlan mapping 2300 2305 15/1
set pvlan mapping 2300 2306 15/1
set pvlan mapping 2300 2307 15/1
set pvlan mapping 2300 2309 15/1
set pvlan mapping 2300 2312 15/1
set pvlan mapping 2500 2501 15/1
set pvlan mapping 2500 2503 15/1
set pvlan mapping 2600 2602 15/1
ctspitdcemsw303> (enable)

----------------------------------------------------------------------------------------

[Joe Clarke]

RME will use the command "write term" to fetch the config from CatOS devices (via telnet or SSH).  With TFTP, RME will use the tftpGrp from the CISCO-STACK-MIB.  It's unclear what protocol you're using to fetch the config, but I would first verify that the protocol you're using shows the proper results using the methods described above.  I don't see how RME would be doing any filtering of those commands.

[josefribeiro]

Hi Joseph,

The method we are using to collect the configuration is SSH. RME will connect to the devices using a tacacs username that has enable privileges.

I'm checking our other switches and it seems the issue - missing parts of configuration - is across the board. I'll have more on that later today.

Could this be a time limit issue, where RME will leave the device after a while and not capturing the whole config?

Here's a message I got from our daily archive job.

ctspitdcemsw303:

CM0062 Polling ctspitdcemsw303 for changes to configuration.  CM0149 PRIMARY RUNNING config changed. RUNNING Primary Login Succeeded / Primary  Enable Succeeded CM0060 PRIMARY RUNNING Config fetch SUCCESS for  ctspitdcemsw303, version number 176 archived.

But after exporting the config to a text file I can see that portions of the switch config are missing.

Thanks,

Jose

[Joe Clarke]

Since you're using SSH, what do you see when you use "write term" on the switch?  I doubt this is a timeout problem as RME would likely throw an error trying to archive the config.

[josefribeiro]

Hi Joseph,

When I run a write term I can see the whole switch config, though in pages (I need to hit enter several time to go trhu the whole config).

ctspitdcemsw303> (enable) write terminal
This command shows non-default configurations only.
Use 'write terminal all' to show both default and non-default configurations.
.................
..................................

....................................
....................................
....................................
....................................
.....................................

....................................
.....................................
.....................................
.....................................

..............................

....................

begin
!
# ***** NON-DEFAULT CONFIGURATION *****
!      
!
#time: Mon May 9 2011, 09:08:46 EDT
!
#version 8.5(2)
!

Also a View Config Raw from Device Center shows configuration up to module 10, completely missing modules 11, 12 and 15 (pvlan mappings to the MSFC).

Thanks,

Jose

[Joe Clarke]

RME will send "set length 0" so the paging will not happen for RME.  Since you're using SSH, a sniffer will not help.  Instead, enable ArchiveMgmt Server debugging under RME > Admin > System Preferences > Application Loglevel Settings.  Run a new sync archive job for one failing switch, then post the dcmaservice.log.

[josefribeiro]

Hi Joseph,

Please find attached the compressed dcmaservice.log. As per your request I created an ArchiveMgmt job # 2760. It created configuration version 179 for device ctspitdcemsw303.

After the job I checked the stored config from the Device Manager > View Config option. There are several, hundreds I'd say, missing configuration lines.

It looks to me like the configuration is too big for a specific window of time. Ciscoworks then moves along without capturing the rest of the config.

Thanks for your help so far.This issue is affecting us big time. We have several CatOS switches in production.

Jose

[Joe Clarke]

It looks like the log rolled.  Can you post the dcmaservice.log.X files as well?