From srau at rauhaus.org  Mon Dec  5 19:07:58 2005
From: srau at rauhaus.org (Stafford A. Rau)
Date: Mon, 5 Dec 2005 11:07:58 -0800
Subject: Resolved! Re: Missing "Image: Software:" for some platforms
In-Reply-To: <20051115172753.GA15129@rauhaus.org>
References: <20051115172753.GA15129@rauhaus.org>
Message-ID: <20051205190758.GB23923@rauhaus.org>

* Stafford A. Rau <srau at rauhaus.org> [051115 09:28]:
> I'd like to be able to extract the running IOS version for all of our
> Cisco platforms from the rancid configs, but we're missing the '!Image:
> Software:' lines from some of them.
> 
> Specifically, I don't see it for our 7609s, or 6509s (running native IOS)

Here's the problem, and an easy fix that I'm requesting to be
incorporated in future releases of rancid.

The "IOS" line from show version output on a 7609:

IOS (tm) s72033_rp Software (s72033_rp-ADVIPSERVICESK9_WAN-M), Version 12.2(18)SXE4, RELEASE SOFTWARE (fc2)

Note the underscores in (s72033_rp-ADVIPSERVICESK9_WAN-M).

Here's the regex in Sub ShowVersion in bin/rancid:

        /^(Cisco )?IOS .* Software,? \(([A-Za-z-0-9]*)\), .*Version\s+(.*)$/ &&
            ProcessHistory("COMMENTS","keysort","F1",

Just need to add an underscore to the character set match:

        /^(Cisco )?IOS .* Software,? \(([A-Za-z-0-9_]*)\), .*Version\s+(.*)$/ &&
            ProcessHistory("COMMENTS","keysort","F1",

Now I get the correct Image: line in our 6500 and 7600 rancid configs:

!Image: Software: s72033_rp-ADVIPSERVICESK9_WAN-M, 12.2(18)SXE4, RELEASE SOFTWARE (fc2)

Thanks,
--Stafford


From eravin at panix.com  Wed Dec  7 18:49:20 2005
From: eravin at panix.com (Ed Ravin)
Date: Wed, 7 Dec 2005 13:49:20 -0500
Subject: S/Key patches for RANCID
Message-ID: <20051207184920.GA12361@panix.com>

A while back I mentioned that I had gotten S/Key logins working for RANCID,
and was looking for a beta tester.  Someone finally took the bait a few
weeks ago, and after fixing a few things and updating the docs, I think
the code is ready for public consumption.

The enclosed tar file contains patches for clogin, a couple of other misc
patches for various helper files, and the "otphelper" Perl script that 
generates the one-time passwords.  If anyone needs S/Key for devices other
than Cisco and can't figure out how to port the clogin patch, let me know.

See the README in the tar file for the installation instructions.

	-- Ed
-------------- next part --------------
A non-text attachment was scrubbed...
Name: rancid.skey.r2.tar.gz
Type: application/x-tar-gz
Size: 11178 bytes
Desc: not available
Url : http://www.shrubbery.net/pipermail/rancid-discuss/attachments/20051207/aa93ebb9/attachment.bin 

From eravin at panix.com  Wed Dec  7 19:04:49 2005
From: eravin at panix.com (Ed Ravin)
Date: Wed, 7 Dec 2005 14:04:49 -0500
Subject: How *rancid programs can read cloginrc
Message-ID: <20051207190449.GB12361@panix.com>

As part of adding S/Key support into RANCID, I wrote code that lets
a Perl script like rancid/hrancid/jrancid etc. read cloginrc.  It
works by having a Perl module call an Expect script that parses cloginrc,
and then adds the post-parsed contents into a Perl structure.  Since
all the parsing is done by an Expect program, it's the same results
as if clogin had read the data.

What's the point?  One of the architectural problems in RANCID is that
we have no way of specifying options to the *rancid programs.
For example, I once posted that rancid dumps the config twice on
most routers, by sending both "show running" and "write term".
With this feature, you could put router-specific directives for the
*rancid programs into cloginrc.  If rancid accepted options from
cloginrc, perhaps I could specify this:

 add rancid_no_command * {write term} # don't do this command

to tell rancid to not send that command.

Anyway, I thought this opens up some interesting possibilities for
making RANCID more flexible.  To see how the parsing works, open
up the tar file I just sent with the S/Key patches, and read through
the "Rancid/ParseConfig.pm" module and the "otphelper" script that
calls it.

	-- Ed


From jeekay at gmail.com  Mon Dec 12 16:10:43 2005
From: jeekay at gmail.com (Jee Kay)
Date: Mon, 12 Dec 2005 16:10:43 +0000
Subject: RANCID on Redline E|X's (now Juniper D|Xs)
Message-ID: <aad9e1ca0512120810h4a6c8f07r@mail.gmail.com>

Is there any support for Redline E|X (now Juniper D|X) server load
balancers? I can't find them mentioned anywhere in 2.3.2a3.

If there isn't, what is the easiest way to add support for them? Any
hints/tips on knocking up a new login/rancid pair?

Thanks,
GK


From cmgist at gmail.com  Wed Dec 14 15:33:12 2005
From: cmgist at gmail.com (Chad Gist)
Date: Wed, 14 Dec 2005 10:33:12 -0500
Subject: Big Band Login
Message-ID: <d773cbde0512140733r6007fd6br5d8083837f26f7eb@mail.gmail.com>

Greetings ~ I am new to rancid, so please forgive the question.  I
have successfully installed rancid and am attempting to use it to
login to a Big Band CMTS.  The auth to the CLI requires the command
"enable username" followed by password.  The issue seems to be the
space between enable and username.  I have tried putting enable root
in "  "  and  '   ' without any success.  My clogin config follows and
the results from the login attempt.
Thanks in advance...

chad

# customer x
# these routers ask for a username and password.  we automatically get
# enable access after successful authentication.
add user *                      'enable root'
add password *                  xxxxxx
add method *                    telnet


[rancid at localhost ~]$ bin/clogin 10.0.0.5
10.0.0.5
spawn telnet 10.0.0.5
Trying 10.0.0.5...
Connected to 10.0.0.5.
Escape character is '^]'.

Management Module

Starting CLI...

cli:cmts0.localnet.net:root> enable
Incomplete command line.
expecting one of the following parameters:
      <word>
cli:cmts0.localnet.net:root>
Error: TIMEOUT reached


From faron.hopper at capgemini.com  Wed Dec 14 17:33:03 2005
From: faron.hopper at capgemini.com (Hopper, Faron  W.)
Date: Wed, 14 Dec 2005 12:33:03 -0500
Subject: cisco 9509 fiber switch not working
Message-ID: <0D9EF3454D8EFC4B8BFFD2B862941681D091C5@caonmastxm03.na.capgemini.com>


Hello all,
     I have a cisco 9509 fiber switch that I can't get rancid to
recognize.  I can clogin -c "show version" to it and it provides the
show version command and then exits.  When I try to run a rancid-run -r
device to it, it produces the following log file

==============================================================
starting: Wed Dec 14 10:55:06 CST 2005

Trying to get all of the configs.
cod-cisco-9509-1: End of run not found

=====================================
Getting missed routers: round 1.
cod-cisco-9509-1: End of run not found

=====================================
Getting missed routers: round 2.
cod-cisco-9509-1: End of run not found

=====================================
Getting missed routers: round 3.
cod-cisco-9509-1: End of run not found

=====================================
Getting missed routers: round 4.
cod-cisco-9509-1: End of run not found


cvs diff: Diffing .
cvs diff: Diffing configs
cvs commit: Examining .
cvs commit: Examining configs

ending: Wed Dec 14 10:56:40 CST 2005
==============================================================

My router.db file has this entry in it
    Cisco-9509-1:cisco:up
I have tried cat5 and also css just trying to get it to recognize it.

I have attached to .new file and the .raw file for added information.
The .raw file makes me think that it can't parse the error from the
write term command (which is not supported on this device).  Can anyone
point me in the right direction?  I am not sure what to do next.

Thanks,
Faron



netcfgbak at ckcus0002-cfgbak01$ more cod-cisco-9509-1.new




















!RANCID-CONTENT-TYPE: cisco
!
!
!
!
!
!
!
!
!
!BootFlash: sup-1
!BootFlash: kickstart variable =
bootflash:/m9500-sf1ek9-kickstart-mz.2.0.2b.bin
!BootFlash: system variable = bootflash:/m9500-sf1ek9-mz.2.0.2b.bin
!BootFlash: sup-2
!BootFlash: kickstart variable =
bootflash:/m9500-sf1ek9-kickstart-mz.2.0.2b.bin
!BootFlash: system variable = bootflash:/m9500-sf1ek9-mz.2.0.2b.bin
!BootFlash: No module boot variable set
!
!
!Slot 1: type 1/2 Gbps FC Module, 16 ports
!Slot 1: part DS-X9016, serial ok
!
!Slot 2: type 1/2 Gbps FC Module, 32 ports
!Slot 2: part DS-X9032, serial ok
!
!Slot 3: type 1/2 Gbps FC Module, 32 ports
!Slot 3: part DS-X9032, serial ok
!
!Slot 4: type 1/2 Gbps FC Module, 32 ports
!Slot 4: part DS-X9032, serial ok
!
!Slot 5: type Supervisor/Fabric-1              DS-X9530-SF1-K9, 0 ports
!Slot 5: part active, serial *
!
!Slot 6: type Supervisor/Fabric-1, 0 ports
!Slot 6: part DS-X9530-SF1-K9, serial ha-standby
!
version 2.0(2b)
fcid-allocation area company-id 0x001125
fcid-allocation area company-id 0x005076
fcdomain fcid persistent vsan 1
fcdomain fcid database
  vsan 1 wwn 50:05:07:68:01:40:1a:51 fcid 0x390000 area dynamic
  vsan 1 wwn 50:05:07:68:01:10:1a:51 fcid 0x390100 area dynamic
  vsan 1 wwn 50:05:07:68:01:40:1a:0d fcid 0x390200 area dynamic
  vsan 1 wwn 50:05:07:68:01:10:1a:0d fcid 0x390300 area dynamic
  vsan 1 wwn 20:08:00:a0:b8:18:67:03 fcid 0x390400 area dynamic
  vsan 1 wwn 20:09:00:a0:b8:18:67:03 fcid 0x390500 area dynamic
  vsan 1 wwn 20:06:00:a0:b8:18:75:9d fcid 0x390600 area dynamic
  vsan 1 wwn 20:07:00:a0:b8:18:75:9d fcid 0x390700 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:52 fcid 0x390800 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:1e fcid 0x390900 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:3c fcid 0x390a00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:46 fcid 0x390b00 area dynamic
  vsan 1 wwn 50:05:07:68:01:30:1a:51 fcid 0x390c00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:82 fcid 0x390d00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:19 fcid 0x390e00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:94:85 fcid 0x390f00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:4b fcid 0x391000 area dynamic
  vsan 1 wwn 50:05:07:68:01:20:1a:51 fcid 0x391100 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:97:39 fcid 0x391200 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:96:40 fcid 0x391300 area dynamic
  vsan 1 wwn 50:05:07:68:01:30:1a:0d fcid 0x391400 area dynamic
  vsan 1 wwn 50:05:07:68:01:20:1a:0d fcid 0x391500 area dynamic
  vsan 1 wwn 20:08:00:a0:b8:18:67:04 fcid 0x391600 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:3d fcid 0x391700 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:53 fcid 0x391800 area dynamic
  vsan 1 wwn 20:09:00:a0:b8:18:67:04 fcid 0x391900 area dynamic
  vsan 1 wwn 20:06:00:a0:b8:18:75:9e fcid 0x391a00 area dynamic
  vsan 1 wwn 20:07:00:a0:b8:18:75:9e fcid 0x391b00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:96:3a fcid 0x391c00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:aa:94 fcid 0x391d00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:26 fcid 0x391e00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:ac fcid 0x391f00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:ba fcid 0x392000 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:97:4a fcid 0x392100 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:6c fcid 0x392200 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:b6 fcid 0x392300 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:8a fcid 0x392400 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:5a fcid 0x392500 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:84 fcid 0x392600 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:9e fcid 0x392700 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:6e fcid 0x392800 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:94:30 fcid 0x392900 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:ae fcid 0x392a00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:9c fcid 0x392b00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:aa:ac fcid 0x392c00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:80 fcid 0x392d00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:96:8a fcid 0x392e00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:96:3b fcid 0x392f00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:4a fcid 0x393000 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:97:38 fcid 0x393100 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:94:84 fcid 0x393200 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:18 fcid 0x393300 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:96:66 fcid 0x393400 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:0e fcid 0x393500 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:96:67 fcid 0x393600 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:b4 fcid 0x393700 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:0f fcid 0x393800 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:b5 fcid 0x393900 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:6a fcid 0x393a00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:6b fcid 0x393b00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:10 fcid 0x393c00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:96:98 fcid 0x393d00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:11 fcid 0x393e00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:96:99 fcid 0x393f00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:32 fcid 0x394000 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:aa:70 fcid 0x394100 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:33 fcid 0x394200 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:96:14 fcid 0x394300 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:aa:71 fcid 0x394400 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:96:15 fcid 0x394500 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:95:9a fcid 0x394600 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:95:9b fcid 0x394700 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:58 fcid 0x394800 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:59 fcid 0x394900 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:16 fcid 0x394a00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:17 fcid 0x394b00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:7f fcid 0x394c00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:ad fcid 0x394d00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:bb fcid 0x394e00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:b7 fcid 0x394f00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:6d fcid 0x395000 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:97:4b fcid 0x395100 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:8b fcid 0x395200 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:af fcid 0x395300 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:5b fcid 0x395400 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:85 fcid 0x395500 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:9f fcid 0x395600 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:6f fcid 0x395700 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:94:31 fcid 0x395800 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:9d fcid 0x395900 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:aa:ad fcid 0x395a00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:96:41 fcid 0x395b00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:1f fcid 0x395c00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:47 fcid 0x395d00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:83 fcid 0x395e00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:27 fcid 0x395f00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:aa:95 fcid 0x396000 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:96:8b fcid 0x396100 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:81 fcid 0x396200 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:7e fcid 0x396300 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:9c fcid 0x396400 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:9d fcid 0x396500 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:94:30 fcid 0x396600 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:94:31 fcid 0x396700 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:84 fcid 0x396800 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:85 fcid 0x396900 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:97:38 fcid 0x396a00 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:97:39 fcid 0x396b00 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:94:84 fcid 0x396c00 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:4a fcid 0x396d00 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:82 fcid 0x396e00 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:46 fcid 0x396f00 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:aa:94 fcid 0x397000 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:1e fcid 0x397100 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:96:8a fcid 0x397200 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:94:85 fcid 0x397300 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:4b fcid 0x397400 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:52 fcid 0x397500 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:83 fcid 0x397600 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:47 fcid 0x397700 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:96:40 fcid 0x397800 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:aa:95 fcid 0x397900 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:1f fcid 0x397a00 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:3c fcid 0x397b00 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:96:8b fcid 0x397c00 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:26 fcid 0x397d00 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:53 fcid 0x397e00 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:96:41 fcid 0x397f00 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:3d fcid 0x398000 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:27 fcid 0x398100 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:ba fcid 0x398200 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:bb fcid 0x398300 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:8a fcid 0x398400 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:b6 fcid 0x398500 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:ae fcid 0x398600 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:ac fcid 0x398700 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:8b fcid 0x398800 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:af fcid 0x398900 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:5a fcid 0x398a00 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:aa:ac fcid 0x398b00 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:b7 fcid 0x398c00 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:97:4a fcid 0x398d00 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:9e fcid 0x398e00 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:6e fcid 0x398f00 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:ad fcid 0x399000 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:5b fcid 0x399100 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:aa:ad fcid 0x399200 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:6f fcid 0x399300 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:97:4b fcid 0x399400 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:9f fcid 0x399500 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:6c fcid 0x399600 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:6d fcid 0x399700 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:96:66 fcid 0x399800 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:96:67 fcid 0x399900 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:96:3a fcid 0x399a00 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:96:3b fcid 0x399b00 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:aa:71 fcid 0x399c00 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:0e fcid 0x399d00 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:0f fcid 0x399e00 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:6a fcid 0x399f00 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:6b fcid 0x39a000 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:b4 fcid 0x39a100 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:b5 fcid 0x39a200 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:10 fcid 0x39a300 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:11 fcid 0x39a400 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:58 fcid 0x39a500 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:16 fcid 0x39a600 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:59 fcid 0x39a700 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:17 fcid 0x39a800 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:32 fcid 0x39a900 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:33 fcid 0x39aa00 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:96:98 fcid 0x39ab00 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:96:99 fcid 0x39ac00 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:96:15 fcid 0x39ad00 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:95:9b fcid 0x39ae00 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:7f fcid 0x39af00 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:18 fcid 0x39b000 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:19 fcid 0x39b100 area dynamic
switchname CoD-Cisco-9509-1
boot kickstart bootflash:/m9500-sf1ek9-kickstart-mz.2.0.2b.bin sup-1
boot system bootflash:/m9500-sf1ek9-mz.2.0.2b.bin sup-1
boot kickstart bootflash:/m9500-sf1ek9-kickstart-mz.2.0.2b.bin sup-2
boot system bootflash:/m9500-sf1ek9-mz.2.0.2b.bin sup-2
ip default-gateway 206.245.27.1
role name default-role
  description This is a system defined role and applies to all users
  rule 1 permit show feature system
  rule 2 permit show feature snmp
  rule 3 permit show feature module
  rule 4 permit show feature interface
  rule 5 permit show feature hardware
  rule 6 permit show feature environment
kernel core target 0.0.0.0
kernel core limit 1

snmp-server user
snmp-server user
 localizedkey
snmp-server host
username
username
ssh key dsa 1024 force


callhome
  switch-priority 7


snmp-server enable traps license



fcalias name SVC-N1-H1-P1 vsan 1
    member pwwn 50:05:07:68:01:40:1a:51

fcalias name SVC-N1-H1-P2 vsan 1
    member pwwn 50:05:07:68:01:30:1a:51

fcalias name SVC-N1-H2-P1 vsan 1
    member pwwn 50:05:07:68:01:10:1a:51

fcalias name SVC-N2-H1-P1 vsan 1
    member pwwn 50:05:07:68:01:40:1a:0d

fcalias name SVC-N2-H2-P1 vsan 1
    member pwwn 50:05:07:68:01:10:1a:0d

fcalias name DS43-CA-P1 vsan 1
    member pwwn 20:08:00:a0:b8:18:67:03

fcalias name DS43-CB-P1 vsan 1
    member pwwn 20:09:00:a0:b8:18:67:03

fcalias name DS41-CA-P1 vsan 1
    member pwwn 20:06:00:a0:b8:18:75:9d

fcalias name DS41-CB-P1 vsan 1
    member pwwn 20:07:00:a0:b8:18:75:9d

fcalias name SVC-N1-H2-P2 vsan 1
    member pwwn 50:05:07:68:01:20:1a:51

fcalias name SVC-N2-H1-P2 vsan 1
    member pwwn 50:05:07:68:01:30:1a:0d

fcalias name SVC-N2-H2-P2 vsan 1
    member pwwn 50:05:07:68:01:20:1a:0d

fcalias name DS43-CA-P2 vsan 1
    member pwwn 20:08:00:a0:b8:18:67:04

fcalias name DS43-CB-P2 vsan 1
    member pwwn 20:09:00:a0:b8:18:67:04

fcalias name DS41-CA-P2 vsan 1
    member pwwn 20:06:00:a0:b8:18:75:9e

fcalias name DS41-CB-P2 vsan 1
    member pwwn 20:07:00:a0:b8:18:75:9e

fcalias name codibm01 vsan 1
    member pwwn 21:00:00:11:25:12:93:18
    member pwwn 21:00:00:11:25:12:93:19

fcalias name codibm01-os vsan 1
    member pwwn 21:00:00:11:25:12:93:18

fcalias name codibm02 vsan 1
    member pwwn 21:00:00:11:25:12:94:84
    member pwwn 21:00:00:11:25:12:94:85

fcalias name codibm29 vsan 1
    member pwwn 21:00:00:11:25:92:96:3a
    member pwwn 21:00:00:11:25:92:96:3b

fcalias name codibm03 vsan 1
    member pwwn 21:00:00:11:25:12:97:39
    member pwwn 21:00:00:11:25:12:97:38

fcalias name codibm04 vsan 1
    member pwwn 21:00:00:11:25:12:93:4a
    member pwwn 21:00:00:11:25:12:93:4b

fcalias name codibm05 vsan 1
    member pwwn 21:00:00:11:25:92:93:80
    member pwwn 21:00:00:11:25:92:93:81

fcalias name codibm15 vsan 1
    member pwwn 21:00:00:11:25:12:93:ac
    member pwwn 21:00:00:11:25:12:93:ad

fcalias name codibm16 vsan 1
    member pwwn 21:00:00:11:25:12:93:ba
    member pwwn 21:00:00:11:25:12:93:bb

fcalias name codibm17 vsan 1
    member pwwn 21:00:00:11:25:12:93:6c
    member pwwn 21:00:00:11:25:12:93:6d

fcalias name codibm18 vsan 1
    member pwwn 21:00:00:11:25:12:93:b6
    member pwwn 21:00:00:11:25:12:93:b7

fcalias name codibm19 vsan 1
    member pwwn 21:00:00:11:25:12:97:4a
    member pwwn 21:00:00:11:25:12:97:4b

fcalias name codibm06 vsan 1
    member pwwn 21:00:00:11:25:12:96:8b

fcalias name codibm31 vsan 1
    member pwwn 21:00:00:11:25:12:93:0e
    member pwwn 21:00:00:11:25:12:93:0f

fcalias name codibm03-os vsan 1
    member pwwn 21:00:00:11:25:12:97:38

fcalias name codibm30 vsan 1
    member pwwn 21:00:00:11:25:12:96:66
    member pwwn 21:00:00:11:25:12:96:67

fcalias name codibm32 vsan 1
    member pwwn 21:00:00:11:25:12:93:b4
    member pwwn 21:00:00:11:25:12:93:b5

fcalias name codibm39 vsan 1
    member pwwn 21:00:00:11:25:12:93:7f

fcalias name codibm33 vsan 1
    member pwwn 21:00:00:11:25:12:93:6a
    member pwwn 21:00:00:11:25:12:93:6b

fcalias name codibm34 vsan 1
    member pwwn 21:00:00:11:25:12:93:10
    member pwwn 21:00:00:11:25:12:93:11

fcalias name codibm35 vsan 1
    member pwwn 21:00:00:11:25:12:96:98
    member pwwn 21:00:00:11:25:12:96:99

fcalias name codibm37 vsan 1

fcalias name codibm38 vsan 1
    member pwwn 21:00:00:11:25:12:96:15

fcalias name codibm40 vsan 1
    member pwwn 21:00:00:11:25:12:95:9b

fcalias name codibm41 vsan 1
    member pwwn 21:00:00:11:25:12:93:58
    member pwwn 21:00:00:11:25:12:93:59

fcalias name codibm42 vsan 1
    member pwwn 21:00:00:11:25:12:93:16

fcalias name codibm26 vsan 1
    member pwwn 21:00:00:11:25:12:94:30
    member pwwn 21:00:00:11:25:12:94:31

fcalias name codibm23 vsan 1
    member pwwn 21:00:00:11:25:12:93:84
    member pwwn 21:00:00:11:25:12:93:85

fcalias name codibm27 vsan 1
    member pwwn 21:00:00:11:25:12:93:9c
    member pwwn 21:00:00:11:25:12:93:9d

fcalias name codibm20 vsan 1
    member pwwn 21:00:00:11:25:12:93:8a
    member pwwn 21:00:00:11:25:12:93:8b

fcalias name codibm21 vsan 1
    member pwwn 21:00:00:11:25:12:93:ae
    member pwwn 21:00:00:11:25:12:93:af

fcalias name codibm22 vsan 1
    member pwwn 21:00:00:11:25:12:93:5a
    member pwwn 21:00:00:11:25:12:93:5b

fcalias name codibm24 vsan 1
    member pwwn 21:00:00:11:25:12:93:9e
    member pwwn 21:00:00:11:25:12:93:9f

fcalias name codibm25 vsan 1
    member pwwn 21:00:00:11:25:12:93:6e
    member pwwn 21:00:00:11:25:12:93:6f

fcalias name codibm28 vsan 1
    member pwwn 21:00:00:11:25:12:aa:ac
    member pwwn 21:00:00:11:25:12:aa:ad

zone broadcast enable vsan 1



zone name SVC-disk vsan 1
    member fcalias SVC-N1-H1-P1
    member fcalias SVC-N1-H2-P1
    member fcalias SVC-N2-H1-P1
    member fcalias SVC-N2-H2-P1
    member fcalias DS43-CA-P1
    member fcalias DS43-CB-P1
    member fcalias DS41-CA-P1
    member fcalias DS41-CB-P1
    member fcalias DS43-CA-P2
    member fcalias DS43-CB-P2
    member fcalias DS41-CA-P2
    member fcalias DS41-CB-P2

zone name SVC-winOS vsan 1
    member pwwn 21:00:00:11:25:12:93:ad
    member fcalias SVC-N2-H1-P2
    member fcalias codibm01-os
    member fcalias codibm02
    member fcalias codibm16
    member fcalias codibm06

zone name SVC-win vsan 1
    member pwwn 21:00:00:11:25:12:93:bb
    member pwwn 21:00:00:11:25:12:93:ba
    member pwwn 21:00:00:11:25:92:93:19
    member pwwn 21:00:00:11:25:92:93:18
    member pwwn 21:00:00:11:25:12:94:85
    member pwwn 21:00:00:11:25:12:94:84
    member fcalias SVC-N1-H1-P2
    member fcalias SVC-N1-H2-P2
    member fcalias SVC-N2-H1-P2
    member fcalias SVC-N2-H2-P2
    member fcalias codibm02

zone name SVC-linux vsan 1
    member pwwn 21:00:00:11:25:12:93:85
    member pwwn 21:00:00:11:25:12:93:84
    member pwwn 21:00:00:11:25:12:94:31
    member pwwn 21:00:00:11:25:12:94:30
    member pwwn 21:00:00:11:25:12:93:9d
    member pwwn 21:00:00:11:25:12:93:9c
    member pwwn 21:00:00:11:25:12:96:3b
    member pwwn 21:00:00:11:25:12:96:3a
    member pwwn 21:00:00:11:25:12:93:7f
    member pwwn 21:00:00:11:25:12:aa:95
    member pwwn 21:00:00:11:25:12:96:67
    member pwwn 21:00:00:11:25:12:96:66
    member pwwn 21:00:00:11:25:12:93:0f
    member pwwn 21:00:00:11:25:12:93:0e
    member pwwn 21:00:00:11:25:12:93:b5
    member pwwn 21:00:00:11:25:12:93:b4
    member pwwn 21:00:00:11:25:12:93:6b
    member pwwn 21:00:00:11:25:12:93:6a
    member pwwn 21:00:00:11:25:12:93:11
    member pwwn 21:00:00:11:25:12:93:10
    member pwwn 21:00:00:11:25:12:96:99
    member pwwn 21:00:00:11:25:12:96:98
    member pwwn 21:00:00:11:25:12:aa:94
    member pwwn 21:00:00:11:25:12:93:27
    member pwwn 21:00:00:11:25:12:aa:71
    member pwwn 21:00:00:11:25:12:93:26
    member pwwn 21:00:00:11:25:12:96:15
    member pwwn 21:00:00:11:25:12:93:83
    member pwwn 21:00:00:11:25:12:95:9b
    member pwwn 21:00:00:11:25:12:93:82
    member pwwn 21:00:00:11:25:12:93:59
    member pwwn 21:00:00:11:25:12:93:58
    member pwwn 21:00:00:11:25:12:93:47
    member pwwn 21:00:00:11:25:12:93:16
    member pwwn 21:00:00:11:25:12:93:46
    member pwwn 21:00:00:11:25:12:93:1f
    member pwwn 21:00:00:11:25:12:93:1e
    member pwwn 21:00:00:11:25:12:96:41
    member pwwn 21:00:00:11:25:12:93:6d
    member pwwn 21:00:00:11:25:12:93:6c
    member pwwn 21:00:00:11:25:12:93:b7
    member pwwn 21:00:00:11:25:12:93:b6
    member pwwn 21:00:00:11:25:12:97:4b
    member pwwn 21:00:00:11:25:12:97:4a
    member pwwn 21:00:00:11:25:12:93:8b
    member pwwn 21:00:00:11:25:12:93:8a
    member pwwn 21:00:00:11:25:12:93:af
    member pwwn 21:00:00:11:25:12:93:ae
    member pwwn 21:00:00:11:25:12:93:5b
    member pwwn 21:00:00:11:25:12:93:5a
    member pwwn 21:00:00:11:25:12:93:9f
    member pwwn 21:00:00:11:25:12:93:9e
    member pwwn 21:00:00:11:25:12:93:6f
    member pwwn 21:00:00:11:25:12:93:6e
    member pwwn 21:00:00:11:25:12:aa:ad
    member pwwn 21:00:00:11:25:12:aa:ac
    member pwwn 21:00:00:11:25:12:96:40
    member pwwn 21:00:00:11:25:12:93:3d
    member pwwn 21:00:00:11:25:12:93:3c
    member pwwn 21:00:00:11:25:12:93:53
    member pwwn 21:00:00:11:25:12:93:52
    member fcalias SVC-N1-H1-P2
    member fcalias SVC-N1-H2-P2
    member fcalias SVC-N2-H1-P2
    member fcalias SVC-N2-H2-P2

zone name SVC-linuxOS vsan 1
    member pwwn 21:00:00:11:25:92:93:80
    member pwwn 21:00:00:11:25:12:93:4a
    member pwwn 21:00:00:11:25:12:97:4a
    member pwwn 21:00:00:11:25:12:93:b6
    member fcalias SVC-N1-H1-P2
    member fcalias codibm03-os

zoneset name CoD_1 vsan 1
    member SVC-disk
    member SVC-winOS
    member SVC-win
    member SVC-linux
    member SVC-linuxOS

zoneset activate name CoD_1 vsan 1


interface mgmt0
  ip address 206.245.27.43 255.255.255.128

interface fc1/1
  switchport description SVC-N1-H1-P1
  no shutdown

interface fc1/2
  switchport description SVC-N1-H2-P1
  no shutdown

interface fc1/3
  switchport description SVC-N2-H1-P1
  no shutdown

interface fc1/4
  switchport description SVC-N2-H2-P1
  no shutdown

interface fc1/5
  switchport description DS43-CA-P1
  no shutdown

interface fc1/6
  switchport description DS43-CB-P1
  no shutdown

interface fc1/7
  switchport description DS41-CA-P1
  no shutdown

interface fc1/8
  switchport description DS41-CB-P1
  no shutdown

interface fc1/9

interface fc1/10

interface fc1/11
  no shutdown

interface fc1/12
  no shutdown

interface fc1/13
  no shutdown

interface fc1/14
  no shutdown

interface fc1/15
  no shutdown

interface fc1/16
  no shutdown

interface fc2/1
  switchport description SVC-N1-H1-P2
  no shutdown

interface fc2/2
  no shutdown

interface fc2/3
  no shutdown

interface fc2/4
  no shutdown

interface fc2/5
  switchport description SVC-N1-H2-P2
  no shutdown

interface fc2/6
  no shutdown

interface fc2/7
  no shutdown

interface fc2/8
  no shutdown

interface fc2/9
  switchport description SVC-N2-H1-P2
  no shutdown

interface fc2/10
  no shutdown

interface fc2/11
  no shutdown

interface fc2/12
  no shutdown

interface fc2/13
  switchport description SVC-N2-H2-P2
  no shutdown

interface fc2/14
  no shutdown

interface fc2/15
  no shutdown

interface fc2/16
  no shutdown

interface fc2/17
  switchport description DS43-CA-P2
  no shutdown

interface fc2/18
  no shutdown

interface fc2/19
  no shutdown

interface fc2/20

interface fc2/21
  switchport description DS43-CB-P2
  no shutdown

interface fc2/22

interface fc2/23

interface fc2/24

interface fc2/25
  switchport description DS41-CA-P2
  no shutdown

interface fc2/26

interface fc2/27

interface fc2/28

interface fc2/29
  switchport description DS41-CB-P2
  no shutdown

interface fc2/30

interface fc2/31

interface fc2/32

interface fc3/1
  no shutdown

interface fc3/2
  no shutdown

interface fc3/3
  no shutdown

interface fc3/4
  no shutdown

interface fc3/5
  no shutdown

interface fc3/6
  no shutdown

interface fc3/7
  no shutdown

interface fc3/8
  no shutdown

interface fc3/9
  no shutdown

interface fc3/10
  no shutdown

interface fc3/11
  no shutdown

interface fc3/12
  no shutdown

interface fc3/13
  no shutdown

interface fc3/14
  no shutdown

interface fc3/15
  no shutdown

interface fc3/16
  no shutdown

interface fc3/17
  no shutdown

interface fc3/18
  no shutdown

interface fc3/19
  no shutdown

interface fc3/20
  no shutdown

interface fc3/21
  no shutdown

interface fc3/22
  no shutdown

interface fc3/23
  no shutdown

interface fc3/24
  no shutdown

interface fc3/25
  no shutdown

interface fc3/26
  no shutdown

interface fc3/27
  no shutdown

interface fc3/28
  no shutdown

interface fc3/29
  no shutdown

interface fc3/30
  no shutdown

interface fc3/31
  no shutdown

interface fc3/32
  no shutdown

interface fc4/1
  no shutdown

interface fc4/2
  no shutdown

interface fc4/3
  no shutdown

interface fc4/4
  no shutdown

interface fc4/5
  no shutdown

interface fc4/6
  no shutdown

interface fc4/7
  no shutdown

interface fc4/8
  no shutdown

interface fc4/9
  no shutdown

interface fc4/10
  no shutdown

interface fc4/11
  no shutdown

interface fc4/12
  no shutdown

interface fc4/13
  no shutdown

interface fc4/14
  no shutdown

interface fc4/15
  no shutdown

interface fc4/16
  no shutdown

interface fc4/17
  no shutdown

interface fc4/18
  no shutdown

interface fc4/19
  no shutdown

interface fc4/20
  no shutdown

interface fc4/21
  no shutdown

interface fc4/22
  no shutdown

interface fc4/23
  no shutdown

interface fc4/24
  no shutdown

interface fc4/25
  no shutdown

interface fc4/26
  no shutdown

interface fc4/27
  no shutdown

interface fc4/28
  no shutdown

interface fc4/29
  no shutdown

interface fc4/30
  no shutdown

interface fc4/31
  no shutdown

interface fc4/32
  no shutdown

                        ^
% invalid command detected at '^' marker.


Here is the raw file
netcfgbak at ckcus0002-cfgbak01$ more cod-cisco-9509-1.raw
cod-cisco-9509-1
spawn telnet cod-cisco-9509-1
Trying 206.245.27.43...
Connected to CoD-Cisco-9509-1.
Escape character is '^]'.
Password:
Login incorrect

CoD-Cisco-9509-1 login: admin
Password:
Cisco Storage Area Networking Operating System (SAN-OS) Software
TAC support: http://www.cisco.com/tac
Copyright (c) 2002-2004, Cisco Systems, Inc. All rights reserved.
The copyrights to certain works contained herein are owned by
other third parties and are used and distributed under license.
Some parts of this software are covered under the GNU Public
License. A copy of the license is available at
http://www.gnu.org/licenses/gpl.html.
^MCoD-Cisco-9509-1# ^M
^MCoD-Cisco-9509-1# term length 0^M
^MCoD-Cisco-9509-1#  show version^M
Cisco Storage Area Networking Operating System (SAN-OS) Software
TAC support: http://www.cisco.com/tac
Copyright (c) 2002-2004, Cisco Systems, Inc. All rights reserved.
The copyrights to certain works contained herein are owned by
other third parties and are used and distributed under license.
Some parts of this software are covered under the GNU Public
License. A copy of the license is available at
http://www.gnu.org/licenses/gpl.html.

Software
  BIOS:      version 1.1.0
  loader:    version 1.2(2)
  kickstart: version 2.0(2b)
  system:    version 2.0(2b)

  BIOS compile time:       10/24/03
  kickstart image file is:
bootflash:///m9500-sf1ek9-kickstart-mz.2.0.2b.bin
  kickstart compile time:  12/3/2004 17:00:00 [12/07/2004 02:04:10]
  system image file is:    bootflash:/m9500-sf1ek9-mz.2.0.2b.bin
  system compile time:     12/3/2004 17:00:00 [12/07/2004 02:24:05]


Hardware
  RAM 1028776 kB

  bootflash: 500736 blocks (block size 512b)
  slot0:          0 blocks (block size 512b)

CoD-Cisco-9509-1   uptime is 106 days 17 hours 3 minute(s) 4 second(s)

  Last reset at 392033 usecs after Sun Mar  2 00:41:42 1980
    Reason: Reset Requested by CLI command reload
    System version: 2.0(2b)
    Service:


^MCoD-Cisco-9509-1# show redundancy secondary^M
                       ^
% invalid command detected at '^' marker.

^MCoD-Cisco-9509-1# show idprom backplane^M
                       ^
% invalid command detected at '^' marker.

^MCoD-Cisco-9509-1# show install active^M
                               ^
% invalid command detected at '^' marker.

^MCoD-Cisco-9509-1# show env all^M
                           ^
% invalid command detected at '^' marker.

^MCoD-Cisco-9509-1# show rsp chassis-info^M
                       ^
% invalid command detected at '^' marker.

^MCoD-Cisco-9509-1# show gsr chassis^M
                       ^
% invalid command detected at '^' marker.

^MCoD-Cisco-9509-1# show boot^M
sup-1
kickstart variable = bootflash:/m9500-sf1ek9-kickstart-mz.2.0.2b.bin
system variable = bootflash:/m9500-sf1ek9-mz.2.0.2b.bin
sup-2
kickstart variable = bootflash:/m9500-sf1ek9-kickstart-mz.2.0.2b.bin
system variable = bootflash:/m9500-sf1ek9-mz.2.0.2b.bin
No module boot variable set
^MCoD-Cisco-9509-1# show bootvar^M
                       ^
% invalid command detected at '^' marker.

^MCoD-Cisco-9509-1# show variables boot^M
                       ^
% invalid command detected at '^' marker.

^MCoD-Cisco-9509-1# show flash^M
                       ^
% invalid command detected at '^' marker.

^MCoD-Cisco-9509-1# dir /all nvram:^M
                           ^
% long command detected at '^' marker.

^MCoD-Cisco-9509-1# dir /all bootflash:^M
                           ^
% long command detected at '^' marker.

^MCoD-Cisco-9509-1# dir /all slot0:^M
                           ^
% long command detected at '^' marker.

^MCoD-Cisco-9509-1# dir /all disk0:^M
                           ^
% long command detected at '^' marker.

^MCoD-Cisco-9509-1# dir /all slot1:^M
                           ^
% long command detected at '^' marker.

^MCoD-Cisco-9509-1# dir /all disk1:^M
                           ^
% long command detected at '^' marker.

^MCoD-Cisco-9509-1# dir /all slot2:^M
                           ^
% long command detected at '^' marker.

^MCoD-Cisco-9509-1# dir /all disk2:^M
                           ^
% long command detected at '^' marker.

^MCoD-Cisco-9509-1# dir /all harddisk:^M
                           ^
% long command detected at '^' marker.

^MCoD-Cisco-9509-1# dir /all harddiska:^M
                           ^
% long command detected at '^' marker.

^MCoD-Cisco-9509-1# dir /all harddiskb:^M
                           ^
% long command detected at '^' marker.

^MCoD-Cisco-9509-1# dir /all sup-bootflash:^M
                           ^
% long command detected at '^' marker.

^MCoD-Cisco-9509-1# dir /all sup-microcode:^M
                           ^
% long command detected at '^' marker.

^MCoD-Cisco-9509-1# dir /all slavenvram:^M
                           ^
% long command detected at '^' marker.

^MCoD-Cisco-9509-1# dir /all slavebootflash:^M
                           ^
% long command detected at '^' marker.

^MCoD-Cisco-9509-1# dir /all slaveslot0:^M
                           ^
% long command detected at '^' marker.

^MCoD-Cisco-9509-1# dir /all slavedisk0:^M
                           ^
% long command detected at '^' marker.

^MCoD-Cisco-9509-1# dir /all slaveslot1:^M
                           ^
% long command detected at '^' marker.

^MCoD-Cisco-9509-1# dir /all slavedisk1:^M
                           ^
% long command detected at '^' marker.

^MCoD-Cisco-9509-1# dir /all slaveslot2:^M
                           ^
% long command detected at '^' marker.

^MCoD-Cisco-9509-1# dir /all slavedisk2:^M
                           ^
% long command detected at '^' marker.

^MCoD-Cisco-9509-1# dir /all slavesup-bootflash:^M
                           ^
% long command detected at '^' marker.

^MCoD-Cisco-9509-1# dir /all sec-nvram:^M
                           ^
% long command detected at '^' marker.

^MCoD-Cisco-9509-1# dir /all sec-bootflash:^M
                           ^
% long command detected at '^' marker.

^MCoD-Cisco-9509-1# dir /all sec-slot0:^M
                           ^
% long command detected at '^' marker.

^MCoD-Cisco-9509-1# dir /all sec-disk0:^M
                           ^
% long command detected at '^' marker.

^MCoD-Cisco-9509-1# dir /all sec-slot1:^M
                           ^
% long command detected at '^' marker.

^MCoD-Cisco-9509-1# dir /all sec-disk1:^M
                           ^
% long command detected at '^' marker.

^MCoD-Cisco-9509-1# dir /all sec-slot2:^M
                           ^
% long command detected at '^' marker.

^MCoD-Cisco-9509-1# dir /all sec-disk2:^M
                           ^
% long command detected at '^' marker.

^MCoD-Cisco-9509-1# show controllers^M
                       ^
% invalid command detected at '^' marker.

^MCoD-Cisco-9509-1# show controllers cbus^M
                       ^
% invalid command detected at '^' marker.

^MCoD-Cisco-9509-1# show diagbus^M
                       ^
% invalid command detected at '^' marker.

^MCoD-Cisco-9509-1# show diag^M
                       ^
% invalid command detected at '^' marker.

^MCoD-Cisco-9509-1# show module^M
Mod  Ports  Module-Type                      Model              Status
---  -----  -------------------------------- ------------------
------------
1    16     1/2 Gbps FC Module               DS-X9016           ok
2    32     1/2 Gbps FC Module               DS-X9032           ok
3    32     1/2 Gbps FC Module               DS-X9032           ok
4    32     1/2 Gbps FC Module               DS-X9032           ok
5    0      Supervisor/Fabric-1              DS-X9530-SF1-K9    active *
6    0      Supervisor/Fabric-1              DS-X9530-SF1-K9
ha-standby

Mod  Sw           Hw      World-Wide-Name(s) (WWN)
---  -----------  ------
--------------------------------------------------
1    2.0(2b)      5.2     20:01:00:0d:ec:1f:fb:00 to
20:10:00:0d:ec:1f:fb:00
2    2.0(2b)      3.2     20:41:00:0d:ec:1f:fb:00 to
20:60:00:0d:ec:1f:fb:00
3    2.0(2b)      3.2     20:81:00:0d:ec:1f:fb:00 to
20:a0:00:0d:ec:1f:fb:00
4    2.0(2b)      3.2     20:c1:00:0d:ec:1f:fb:00 to
20:e0:00:0d:ec:1f:fb:00
5    2.0(2b)      5.3     --
6    2.0(2b)      5.3     --


Mod  MAC-Address(es)                         Serial-Num
---  --------------------------------------  ----------
1    00-13-19-57-80-56 to 00-13-19-57-80-5a  JAB092106DA
2    00-13-19-57-57-6e to 00-13-19-57-57-72  JAB091906PM
3    00-13-1a-e5-ec-80 to 00-13-1a-e5-ec-84  JAB091906MU
4    00-13-19-57-69-12 to 00-13-19-57-69-16  JAB092005R8
5    00-13-19-57-5a-02 to 00-13-19-57-5a-06  JAB092000CZ
6    00-13-19-57-5d-96 to 00-13-19-57-5d-9a  JAB092000F1

* this terminal session
^MCoD-Cisco-9509-1# show spe version^M
                       ^
% invalid command detected at '^' marker.

^MCoD-Cisco-9509-1# show c7200^M
                       ^
% invalid command detected at '^' marker.

^MCoD-Cisco-9509-1# show vtp status^M
                       ^
% invalid command detected at '^' marker.

^MCoD-Cisco-9509-1# show vlan^M
                       ^
% invalid command detected at '^' marker.

^MCoD-Cisco-9509-1# show running-config^M
version 2.0(2b)
fcid-allocation area company-id 0x001125
fcid-allocation area company-id 0x005076
fcdomain fcid persistent vsan 1
fcdomain fcid database
  vsan 1 wwn 50:05:07:68:01:40:1a:51 fcid 0x390000 area dynamic
  vsan 1 wwn 50:05:07:68:01:10:1a:51 fcid 0x390100 area dynamic
  vsan 1 wwn 50:05:07:68:01:40:1a:0d fcid 0x390200 area dynamic
  vsan 1 wwn 50:05:07:68:01:10:1a:0d fcid 0x390300 area dynamic
  vsan 1 wwn 20:08:00:a0:b8:18:67:03 fcid 0x390400 area dynamic
  vsan 1 wwn 20:09:00:a0:b8:18:67:03 fcid 0x390500 area dynamic
  vsan 1 wwn 20:06:00:a0:b8:18:75:9d fcid 0x390600 area dynamic
  vsan 1 wwn 20:07:00:a0:b8:18:75:9d fcid 0x390700 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:52 fcid 0x390800 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:1e fcid 0x390900 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:3c fcid 0x390a00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:46 fcid 0x390b00 area dynamic
  vsan 1 wwn 50:05:07:68:01:30:1a:51 fcid 0x390c00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:82 fcid 0x390d00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:19 fcid 0x390e00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:94:85 fcid 0x390f00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:4b fcid 0x391000 area dynamic
  vsan 1 wwn 50:05:07:68:01:20:1a:51 fcid 0x391100 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:97:39 fcid 0x391200 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:96:40 fcid 0x391300 area dynamic
  vsan 1 wwn 50:05:07:68:01:30:1a:0d fcid 0x391400 area dynamic
  vsan 1 wwn 50:05:07:68:01:20:1a:0d fcid 0x391500 area dynamic
  vsan 1 wwn 20:08:00:a0:b8:18:67:04 fcid 0x391600 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:3d fcid 0x391700 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:53 fcid 0x391800 area dynamic
  vsan 1 wwn 20:09:00:a0:b8:18:67:04 fcid 0x391900 area dynamic
  vsan 1 wwn 20:06:00:a0:b8:18:75:9e fcid 0x391a00 area dynamic
  vsan 1 wwn 20:07:00:a0:b8:18:75:9e fcid 0x391b00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:96:3a fcid 0x391c00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:aa:94 fcid 0x391d00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:26 fcid 0x391e00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:ac fcid 0x391f00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:ba fcid 0x392000 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:97:4a fcid 0x392100 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:6c fcid 0x392200 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:b6 fcid 0x392300 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:8a fcid 0x392400 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:5a fcid 0x392500 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:84 fcid 0x392600 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:9e fcid 0x392700 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:6e fcid 0x392800 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:94:30 fcid 0x392900 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:ae fcid 0x392a00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:9c fcid 0x392b00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:aa:ac fcid 0x392c00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:80 fcid 0x392d00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:96:8a fcid 0x392e00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:96:3b fcid 0x392f00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:4a fcid 0x393000 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:97:38 fcid 0x393100 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:94:84 fcid 0x393200 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:18 fcid 0x393300 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:96:66 fcid 0x393400 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:0e fcid 0x393500 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:96:67 fcid 0x393600 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:b4 fcid 0x393700 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:0f fcid 0x393800 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:b5 fcid 0x393900 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:6a fcid 0x393a00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:6b fcid 0x393b00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:10 fcid 0x393c00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:96:98 fcid 0x393d00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:11 fcid 0x393e00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:96:99 fcid 0x393f00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:32 fcid 0x394000 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:aa:70 fcid 0x394100 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:33 fcid 0x394200 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:96:14 fcid 0x394300 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:aa:71 fcid 0x394400 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:96:15 fcid 0x394500 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:95:9a fcid 0x394600 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:95:9b fcid 0x394700 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:58 fcid 0x394800 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:59 fcid 0x394900 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:16 fcid 0x394a00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:17 fcid 0x394b00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:7f fcid 0x394c00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:ad fcid 0x394d00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:bb fcid 0x394e00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:b7 fcid 0x394f00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:6d fcid 0x395000 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:97:4b fcid 0x395100 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:8b fcid 0x395200 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:af fcid 0x395300 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:5b fcid 0x395400 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:85 fcid 0x395500 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:9f fcid 0x395600 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:6f fcid 0x395700 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:94:31 fcid 0x395800 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:9d fcid 0x395900 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:aa:ad fcid 0x395a00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:96:41 fcid 0x395b00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:1f fcid 0x395c00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:47 fcid 0x395d00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:83 fcid 0x395e00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:27 fcid 0x395f00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:aa:95 fcid 0x396000 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:96:8b fcid 0x396100 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:81 fcid 0x396200 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:7e fcid 0x396300 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:9c fcid 0x396400 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:9d fcid 0x396500 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:94:30 fcid 0x396600 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:94:31 fcid 0x396700 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:84 fcid 0x396800 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:85 fcid 0x396900 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:97:38 fcid 0x396a00 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:97:39 fcid 0x396b00 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:94:84 fcid 0x396c00 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:4a fcid 0x396d00 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:82 fcid 0x396e00 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:46 fcid 0x396f00 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:aa:94 fcid 0x397000 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:1e fcid 0x397100 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:96:8a fcid 0x397200 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:94:85 fcid 0x397300 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:4b fcid 0x397400 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:52 fcid 0x397500 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:83 fcid 0x397600 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:47 fcid 0x397700 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:96:40 fcid 0x397800 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:aa:95 fcid 0x397900 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:1f fcid 0x397a00 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:3c fcid 0x397b00 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:96:8b fcid 0x397c00 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:26 fcid 0x397d00 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:53 fcid 0x397e00 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:96:41 fcid 0x397f00 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:3d fcid 0x398000 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:27 fcid 0x398100 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:ba fcid 0x398200 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:bb fcid 0x398300 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:8a fcid 0x398400 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:b6 fcid 0x398500 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:ae fcid 0x398600 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:ac fcid 0x398700 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:8b fcid 0x398800 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:af fcid 0x398900 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:5a fcid 0x398a00 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:aa:ac fcid 0x398b00 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:b7 fcid 0x398c00 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:97:4a fcid 0x398d00 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:9e fcid 0x398e00 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:6e fcid 0x398f00 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:ad fcid 0x399000 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:5b fcid 0x399100 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:aa:ad fcid 0x399200 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:6f fcid 0x399300 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:97:4b fcid 0x399400 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:9f fcid 0x399500 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:6c fcid 0x399600 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:6d fcid 0x399700 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:96:66 fcid 0x399800 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:96:67 fcid 0x399900 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:96:3a fcid 0x399a00 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:96:3b fcid 0x399b00 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:aa:71 fcid 0x399c00 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:0e fcid 0x399d00 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:0f fcid 0x399e00 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:6a fcid 0x399f00 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:6b fcid 0x39a000 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:b4 fcid 0x39a100 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:b5 fcid 0x39a200 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:10 fcid 0x39a300 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:11 fcid 0x39a400 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:58 fcid 0x39a500 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:16 fcid 0x39a600 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:59 fcid 0x39a700 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:17 fcid 0x39a800 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:32 fcid 0x39a900 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:33 fcid 0x39aa00 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:96:98 fcid 0x39ab00 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:96:99 fcid 0x39ac00 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:96:15 fcid 0x39ad00 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:95:9b fcid 0x39ae00 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:7f fcid 0x39af00 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:18 fcid 0x39b000 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:19 fcid 0x39b100 area dynamic
switchname CoD-Cisco-9509-1
boot kickstart bootflash:/m9500-sf1ek9-kickstart-mz.2.0.2b.bin sup-1
boot system bootflash:/m9500-sf1ek9-mz.2.0.2b.bin sup-1
boot kickstart bootflash:/m9500-sf1ek9-kickstart-mz.2.0.2b.bin sup-2
boot system bootflash:/m9500-sf1ek9-mz.2.0.2b.bin sup-2
ip default-gateway 206.245.27.1
role name default-role
  description This is a system defined role and applies to all users
  rule 1 permit show feature system
  rule 2 permit show feature snmp
  rule 3 permit show feature module
  rule 4 permit show feature interface
  rule 5 permit show feature hardware
  rule 6 permit show feature environment
kernel core target 0.0.0.0
kernel core limit 1





snmp-server user
 localizedkey
snmp-server user admin
localizedkey
snmp-server host
username
username
ssh key dsa 1024 force


callhome
  switch-priority 7


snmp-server enable traps license



fcalias name SVC-N1-H1-P1 vsan 1
    member pwwn 50:05:07:68:01:40:1a:51

fcalias name SVC-N1-H1-P2 vsan 1
    member pwwn 50:05:07:68:01:30:1a:51

fcalias name SVC-N1-H2-P1 vsan 1
    member pwwn 50:05:07:68:01:10:1a:51

fcalias name SVC-N2-H1-P1 vsan 1
    member pwwn 50:05:07:68:01:40:1a:0d

fcalias name SVC-N2-H2-P1 vsan 1
    member pwwn 50:05:07:68:01:10:1a:0d

fcalias name DS43-CA-P1 vsan 1
    member pwwn 20:08:00:a0:b8:18:67:03

fcalias name DS43-CB-P1 vsan 1
    member pwwn 20:09:00:a0:b8:18:67:03

fcalias name DS41-CA-P1 vsan 1
    member pwwn 20:06:00:a0:b8:18:75:9d

fcalias name DS41-CB-P1 vsan 1
    member pwwn 20:07:00:a0:b8:18:75:9d

fcalias name SVC-N1-H2-P2 vsan 1
    member pwwn 50:05:07:68:01:20:1a:51

fcalias name SVC-N2-H1-P2 vsan 1
    member pwwn 50:05:07:68:01:30:1a:0d

fcalias name SVC-N2-H2-P2 vsan 1
    member pwwn 50:05:07:68:01:20:1a:0d

fcalias name DS43-CA-P2 vsan 1
    member pwwn 20:08:00:a0:b8:18:67:04

fcalias name DS43-CB-P2 vsan 1
    member pwwn 20:09:00:a0:b8:18:67:04

fcalias name DS41-CA-P2 vsan 1
    member pwwn 20:06:00:a0:b8:18:75:9e

fcalias name DS41-CB-P2 vsan 1
    member pwwn 20:07:00:a0:b8:18:75:9e

fcalias name codibm01 vsan 1
    member pwwn 21:00:00:11:25:12:93:18
    member pwwn 21:00:00:11:25:12:93:19

fcalias name codibm01-os vsan 1
    member pwwn 21:00:00:11:25:12:93:18

fcalias name codibm02 vsan 1
    member pwwn 21:00:00:11:25:12:94:84
    member pwwn 21:00:00:11:25:12:94:85

fcalias name codibm29 vsan 1
    member pwwn 21:00:00:11:25:92:96:3a
    member pwwn 21:00:00:11:25:92:96:3b

fcalias name codibm03 vsan 1
    member pwwn 21:00:00:11:25:12:97:39
    member pwwn 21:00:00:11:25:12:97:38

fcalias name codibm04 vsan 1
    member pwwn 21:00:00:11:25:12:93:4a
    member pwwn 21:00:00:11:25:12:93:4b

fcalias name codibm05 vsan 1
    member pwwn 21:00:00:11:25:92:93:80
    member pwwn 21:00:00:11:25:92:93:81

fcalias name codibm15 vsan 1
    member pwwn 21:00:00:11:25:12:93:ac
    member pwwn 21:00:00:11:25:12:93:ad

fcalias name codibm16 vsan 1
    member pwwn 21:00:00:11:25:12:93:ba
    member pwwn 21:00:00:11:25:12:93:bb

fcalias name codibm17 vsan 1
    member pwwn 21:00:00:11:25:12:93:6c
    member pwwn 21:00:00:11:25:12:93:6d

fcalias name codibm18 vsan 1
    member pwwn 21:00:00:11:25:12:93:b6
    member pwwn 21:00:00:11:25:12:93:b7

fcalias name codibm19 vsan 1
    member pwwn 21:00:00:11:25:12:97:4a
    member pwwn 21:00:00:11:25:12:97:4b

fcalias name codibm06 vsan 1
    member pwwn 21:00:00:11:25:12:96:8b

fcalias name codibm31 vsan 1
    member pwwn 21:00:00:11:25:12:93:0e
    member pwwn 21:00:00:11:25:12:93:0f

fcalias name codibm03-os vsan 1
    member pwwn 21:00:00:11:25:12:97:38

fcalias name codibm30 vsan 1
    member pwwn 21:00:00:11:25:12:96:66
    member pwwn 21:00:00:11:25:12:96:67

fcalias name codibm32 vsan 1
    member pwwn 21:00:00:11:25:12:93:b4
    member pwwn 21:00:00:11:25:12:93:b5

fcalias name codibm39 vsan 1
    member pwwn 21:00:00:11:25:12:93:7f

fcalias name codibm33 vsan 1
    member pwwn 21:00:00:11:25:12:93:6a
    member pwwn 21:00:00:11:25:12:93:6b

fcalias name codibm34 vsan 1
    member pwwn 21:00:00:11:25:12:93:10
    member pwwn 21:00:00:11:25:12:93:11

fcalias name codibm35 vsan 1
    member pwwn 21:00:00:11:25:12:96:98
    member pwwn 21:00:00:11:25:12:96:99

fcalias name codibm37 vsan 1

fcalias name codibm38 vsan 1
    member pwwn 21:00:00:11:25:12:96:15

fcalias name codibm40 vsan 1
    member pwwn 21:00:00:11:25:12:95:9b

fcalias name codibm41 vsan 1
    member pwwn 21:00:00:11:25:12:93:58
    member pwwn 21:00:00:11:25:12:93:59

fcalias name codibm42 vsan 1
    member pwwn 21:00:00:11:25:12:93:16

fcalias name codibm26 vsan 1
    member pwwn 21:00:00:11:25:12:94:30
    member pwwn 21:00:00:11:25:12:94:31

fcalias name codibm23 vsan 1
    member pwwn 21:00:00:11:25:12:93:84
    member pwwn 21:00:00:11:25:12:93:85

fcalias name codibm27 vsan 1
    member pwwn 21:00:00:11:25:12:93:9c
    member pwwn 21:00:00:11:25:12:93:9d

fcalias name codibm20 vsan 1
    member pwwn 21:00:00:11:25:12:93:8a
    member pwwn 21:00:00:11:25:12:93:8b

fcalias name codibm21 vsan 1
    member pwwn 21:00:00:11:25:12:93:ae
    member pwwn 21:00:00:11:25:12:93:af

fcalias name codibm22 vsan 1
    member pwwn 21:00:00:11:25:12:93:5a
    member pwwn 21:00:00:11:25:12:93:5b

fcalias name codibm24 vsan 1
    member pwwn 21:00:00:11:25:12:93:9e
    member pwwn 21:00:00:11:25:12:93:9f

fcalias name codibm25 vsan 1
    member pwwn 21:00:00:11:25:12:93:6e
    member pwwn 21:00:00:11:25:12:93:6f

fcalias name codibm28 vsan 1
    member pwwn 21:00:00:11:25:12:aa:ac
    member pwwn 21:00:00:11:25:12:aa:ad

zone broadcast enable vsan 1



zone name SVC-disk vsan 1
    member fcalias SVC-N1-H1-P1
    member fcalias SVC-N1-H2-P1
    member fcalias SVC-N2-H1-P1
    member fcalias SVC-N2-H2-P1
    member fcalias DS43-CA-P1
    member fcalias DS43-CB-P1
    member fcalias DS41-CA-P1
    member fcalias DS41-CB-P1
    member fcalias DS43-CA-P2
    member fcalias DS43-CB-P2
    member fcalias DS41-CA-P2
    member fcalias DS41-CB-P2

zone name SVC-winOS vsan 1
    member pwwn 21:00:00:11:25:12:93:ad
    member fcalias SVC-N2-H1-P2
    member fcalias codibm01-os
    member fcalias codibm02
    member fcalias codibm16
    member fcalias codibm06

zone name SVC-win vsan 1
    member pwwn 21:00:00:11:25:12:93:bb
    member pwwn 21:00:00:11:25:12:93:ba
    member pwwn 21:00:00:11:25:92:93:19
    member pwwn 21:00:00:11:25:92:93:18
    member pwwn 21:00:00:11:25:12:94:85
    member pwwn 21:00:00:11:25:12:94:84
    member fcalias SVC-N1-H1-P2
    member fcalias SVC-N1-H2-P2
    member fcalias SVC-N2-H1-P2
    member fcalias SVC-N2-H2-P2
    member fcalias codibm02

zone name SVC-linux vsan 1
    member pwwn 21:00:00:11:25:12:93:85
    member pwwn 21:00:00:11:25:12:93:84
    member pwwn 21:00:00:11:25:12:94:31
    member pwwn 21:00:00:11:25:12:94:30
    member pwwn 21:00:00:11:25:12:93:9d
    member pwwn 21:00:00:11:25:12:93:9c
    member pwwn 21:00:00:11:25:12:96:3b
    member pwwn 21:00:00:11:25:12:96:3a
    member pwwn 21:00:00:11:25:12:93:7f
    member pwwn 21:00:00:11:25:12:aa:95
    member pwwn 21:00:00:11:25:12:96:67
    member pwwn 21:00:00:11:25:12:96:66
    member pwwn 21:00:00:11:25:12:93:0f
    member pwwn 21:00:00:11:25:12:93:0e
    member pwwn 21:00:00:11:25:12:93:b5
    member pwwn 21:00:00:11:25:12:93:b4
    member pwwn 21:00:00:11:25:12:93:6b
    member pwwn 21:00:00:11:25:12:93:6a
    member pwwn 21:00:00:11:25:12:93:11
    member pwwn 21:00:00:11:25:12:93:10
    member pwwn 21:00:00:11:25:12:96:99
    member pwwn 21:00:00:11:25:12:96:98
    member pwwn 21:00:00:11:25:12:aa:94
    member pwwn 21:00:00:11:25:12:93:27
    member pwwn 21:00:00:11:25:12:aa:71
    member pwwn 21:00:00:11:25:12:93:26
    member pwwn 21:00:00:11:25:12:96:15
    member pwwn 21:00:00:11:25:12:93:83
    member pwwn 21:00:00:11:25:12:95:9b
    member pwwn 21:00:00:11:25:12:93:82
    member pwwn 21:00:00:11:25:12:93:59
    member pwwn 21:00:00:11:25:12:93:58
    member pwwn 21:00:00:11:25:12:93:47
    member pwwn 21:00:00:11:25:12:93:16
    member pwwn 21:00:00:11:25:12:93:46
    member pwwn 21:00:00:11:25:12:93:1f
    member pwwn 21:00:00:11:25:12:93:1e
    member pwwn 21:00:00:11:25:12:96:41
    member pwwn 21:00:00:11:25:12:93:6d
    member pwwn 21:00:00:11:25:12:93:6c
    member pwwn 21:00:00:11:25:12:93:b7
    member pwwn 21:00:00:11:25:12:93:b6
    member pwwn 21:00:00:11:25:12:97:4b
    member pwwn 21:00:00:11:25:12:97:4a
    member pwwn 21:00:00:11:25:12:93:8b
    member pwwn 21:00:00:11:25:12:93:8a
    member pwwn 21:00:00:11:25:12:93:af
    member pwwn 21:00:00:11:25:12:93:ae
    member pwwn 21:00:00:11:25:12:93:5b
    member pwwn 21:00:00:11:25:12:93:5a
    member pwwn 21:00:00:11:25:12:93:9f
    member pwwn 21:00:00:11:25:12:93:9e
    member pwwn 21:00:00:11:25:12:93:6f
    member pwwn 21:00:00:11:25:12:93:6e
    member pwwn 21:00:00:11:25:12:aa:ad
    member pwwn 21:00:00:11:25:12:aa:ac
    member pwwn 21:00:00:11:25:12:96:40
    member pwwn 21:00:00:11:25:12:93:3d
    member pwwn 21:00:00:11:25:12:93:3c
    member pwwn 21:00:00:11:25:12:93:53
    member pwwn 21:00:00:11:25:12:93:52
    member fcalias SVC-N1-H1-P2
    member fcalias SVC-N1-H2-P2
    member fcalias SVC-N2-H1-P2
    member fcalias SVC-N2-H2-P2

zone name SVC-linuxOS vsan 1
    member pwwn 21:00:00:11:25:92:93:80
    member pwwn 21:00:00:11:25:12:93:4a
    member pwwn 21:00:00:11:25:12:97:4a
    member pwwn 21:00:00:11:25:12:93:b6
    member fcalias SVC-N1-H1-P2
    member fcalias codibm03-os

zoneset name CoD_1 vsan 1
    member SVC-disk
    member SVC-winOS
    member SVC-win
    member SVC-linux
    member SVC-linuxOS

zoneset activate name CoD_1 vsan 1


interface mgmt0
  ip address 206.245.27.43 255.255.255.128

interface fc1/1
  switchport description SVC-N1-H1-P1
  no shutdown

interface fc1/2
  switchport description SVC-N1-H2-P1
  no shutdown

interface fc1/3
  switchport description SVC-N2-H1-P1
  no shutdown

interface fc1/4
  switchport description SVC-N2-H2-P1
  no shutdown

interface fc1/5
  switchport description DS43-CA-P1
  no shutdown

interface fc1/6
  switchport description DS43-CB-P1
  no shutdown

interface fc1/7
  switchport description DS41-CA-P1
  no shutdown

interface fc1/8
  switchport description DS41-CB-P1
  no shutdown

interface fc1/9

interface fc1/10

interface fc1/11
  no shutdown

interface fc1/12
  no shutdown

interface fc1/13
  no shutdown

interface fc1/14
  no shutdown

interface fc1/15
  no shutdown

interface fc1/16
  no shutdown

interface fc2/1
  switchport description SVC-N1-H1-P2
  no shutdown

interface fc2/2
  no shutdown

interface fc2/3
  no shutdown

interface fc2/4
  no shutdown

interface fc2/5
  switchport description SVC-N1-H2-P2
  no shutdown

interface fc2/6
  no shutdown

interface fc2/7
  no shutdown

interface fc2/8
  no shutdown

interface fc2/9
  switchport description SVC-N2-H1-P2
  no shutdown

interface fc2/10
  no shutdown

interface fc2/11
  no shutdown

interface fc2/12
  no shutdown

interface fc2/13
  switchport description SVC-N2-H2-P2
  no shutdown

interface fc2/14
  no shutdown

interface fc2/15
  no shutdown

interface fc2/16
  no shutdown

interface fc2/17
  switchport description DS43-CA-P2
  no shutdown

interface fc2/18
  no shutdown

interface fc2/19
  no shutdown

interface fc2/20

interface fc2/21
  switchport description DS43-CB-P2
  no shutdown

interface fc2/22

interface fc2/23

interface fc2/24

interface fc2/25
  switchport description DS41-CA-P2
  no shutdown

interface fc2/26

interface fc2/27

interface fc2/28

interface fc2/29
  switchport description DS41-CB-P2
  no shutdown

interface fc2/30

interface fc2/31

interface fc2/32

interface fc3/1
  no shutdown

interface fc3/2
  no shutdown

interface fc3/3
  no shutdown

interface fc3/4
  no shutdown

interface fc3/5
  no shutdown

interface fc3/6
  no shutdown

interface fc3/7
  no shutdown

interface fc3/8
  no shutdown

interface fc3/9
  no shutdown

interface fc3/10
  no shutdown

interface fc3/11
  no shutdown

interface fc3/12
  no shutdown

interface fc3/13
  no shutdown

interface fc3/14
  no shutdown

interface fc3/15
  no shutdown

interface fc3/16
  no shutdown

interface fc3/17
  no shutdown

interface fc3/18
  no shutdown

interface fc3/19
  no shutdown

interface fc3/20
  no shutdown

interface fc3/21
  no shutdown

interface fc3/22
  no shutdown

interface fc3/23
  no shutdown

interface fc3/24
  no shutdown

interface fc3/25
  no shutdown

interface fc3/26
  no shutdown

interface fc3/27
  no shutdown

interface fc3/28
  no shutdown

interface fc3/29
  no shutdown

interface fc3/30
  no shutdown

interface fc3/31
  no shutdown

interface fc3/32
  no shutdown

interface fc4/1
  no shutdown

interface fc4/2
  no shutdown

interface fc4/3
  no shutdown

interface fc4/4
  no shutdown

interface fc4/5
  no shutdown

interface fc4/6
  no shutdown

interface fc4/7
  no shutdown

interface fc4/8
  no shutdown

interface fc4/9
  no shutdown

interface fc4/10
  no shutdown

interface fc4/11
  no shutdown

interface fc4/12
  no shutdown

interface fc4/13
  no shutdown

interface fc4/14
  no shutdown

interface fc4/15
  no shutdown

interface fc4/16
  no shutdown

interface fc4/17
  no shutdown

interface fc4/18
  no shutdown

interface fc4/19
  no shutdown

interface fc4/20
  no shutdown

interface fc4/21
  no shutdown

interface fc4/22
  no shutdown

interface fc4/23
  no shutdown

interface fc4/24
  no shutdown

interface fc4/25
  no shutdown

interface fc4/26
  no shutdown

interface fc4/27
  no shutdown

interface fc4/28
  no shutdown

interface fc4/29
  no shutdown

interface fc4/30
  no shutdown

interface fc4/31
  no shutdown

interface fc4/32
  no shutdown

^MCoD-Cisco-9509-1# write term^M
                        ^
% invalid command detected at '^' marker.

^MCoD-Cisco-9509-1#exit^M
Connection closed by foreign host.




From eravin at panix.com  Wed Dec 14 17:55:40 2005
From: eravin at panix.com (Ed Ravin)
Date: Wed, 14 Dec 2005 12:55:40 -0500
Subject: cisco 9509 fiber switch not working
In-Reply-To: <0D9EF3454D8EFC4B8BFFD2B862941681D091C5@caonmastxm03.na.capgemini.com>
References: <0D9EF3454D8EFC4B8BFFD2B862941681D091C5@caonmastxm03.na.capgemini.com>
Message-ID: <20051214175540.GA10724@panix.com>

On Wed, Dec 14, 2005 at 12:33:03PM -0500, Hopper, Faron  W. wrote:
> 
> Hello all,
>      I have a cisco 9509 fiber switch that I can't get rancid to
> recognize.  I can clogin -c "show version" to it and it provides the
> show version command and then exits.  When I try to run a rancid-run -r
> device to it, it produces the following log file
> 
> ==============================================================
> starting: Wed Dec 14 10:55:06 CST 2005
> 
> Trying to get all of the configs.
> cod-cisco-9509-1: End of run not found

[...]

What platform are you using, and what version of RANCID?  Also, read the
release notes in RANCID about how some versions of Expect need to be patched.

Have you tried "rancid -d" to get debug output?

Sometimes this error means rancid didn't find the last command ("exit"), but
in your case, it's there at the end of the output:

  ^MCoD-Cisco-9509-1#exit^M
  Connection closed by foreign host.

> The .raw file makes me think that it can't parse the error from the
> write term command (which is not supported on this device).

That's not the problem - you'll note that "show running-config" was
also sent and recognized.  rancid is smart enough to use whichever one
worked.


From heas at shrubbery.net  Wed Dec 14 19:33:38 2005
From: heas at shrubbery.net (john heasley)
Date: Wed, 14 Dec 2005 11:33:38 -0800
Subject: cisco 9509 fiber switch not working
In-Reply-To: <0D9EF3454D8EFC4B8BFFD2B862941681D091C5@caonmastxm03.na.capgemini.com>
References: <0D9EF3454D8EFC4B8BFFD2B862941681D091C5@caonmastxm03.na.capgemini.com>
Message-ID: <20051214193338.GD26511@shrubbery.net>

Please try this box as device type :cat5k:.  I am not positive that will work,
as this looks like some really perverse mix of catos and ios.  but, the real
issue here is that it does not tag the end of the config (show running) as
ios does and thus type :cisco: looks for.

Wed, Dec 14, 2005 at 12:33:03PM -0500, Hopper, Faron  W.:
> 
> Hello all,
>      I have a cisco 9509 fiber switch that I can't get rancid to
> recognize.  I can clogin -c "show version" to it and it provides the
> show version command and then exits.  When I try to run a rancid-run -r
> device to it, it produces the following log file
> 
> ==============================================================
> starting: Wed Dec 14 10:55:06 CST 2005
> 
> Trying to get all of the configs.
> cod-cisco-9509-1: End of run not found
> 
> =====================================
> Getting missed routers: round 1.
> cod-cisco-9509-1: End of run not found
> 
> =====================================
> Getting missed routers: round 2.
> cod-cisco-9509-1: End of run not found
> 
> =====================================
> Getting missed routers: round 3.
> cod-cisco-9509-1: End of run not found
> 
> =====================================
> Getting missed routers: round 4.
> cod-cisco-9509-1: End of run not found
> 
> 
> cvs diff: Diffing .
> cvs diff: Diffing configs
> cvs commit: Examining .
> cvs commit: Examining configs
> 
> ending: Wed Dec 14 10:56:40 CST 2005
> ==============================================================
> 
> My router.db file has this entry in it
>     Cisco-9509-1:cisco:up
> I have tried cat5 and also css just trying to get it to recognize it.
> 
> I have attached to .new file and the .raw file for added information.
> The .raw file makes me think that it can't parse the error from the
> write term command (which is not supported on this device).  Can anyone
> point me in the right direction?  I am not sure what to do next.


From faron.hopper at capgemini.com  Wed Dec 14 20:13:05 2005
From: faron.hopper at capgemini.com (Hopper, Faron  W.)
Date: Wed, 14 Dec 2005 15:13:05 -0500
Subject: cisco 9509 fiber switch not working
Message-ID: <0D9EF3454D8EFC4B8BFFD2B862941681D09251@caonmastxm03.na.capgemini.com>


Ed,
	Platform = freebsd 5.4
	Rancid ver = rancid-2.3.1_1
	Expect ver = expect-5.43.0

>> Have you tried "rancid -d" to get debug output?

Yes, that is how I attached the .raw and .new files.  I attached them
and the info from the log file.  Is there anything else that would give
me more information?

Another user on the list, Mark Scheuber, responded with

"I wound up hacking the script with 'show running-config'   =>
"WriteTerm", and changing the text of the actual command in the array
below that..  Very dirty, I know, but it works.  I think I also might
have done a few more tweaks that stripped off the error correction.  If
I remember correctly there was some white space at the end, and a prompt
issue that was throwing the scripts.  Also, the snmp server settings
change hourly depending on if the people configuring the SAN use that
little java applet.  Just an FYI as it threw me while I was working on
it.  
        The major problem I had was setting up the escalated privileges
in ACS as we have an EMC branded box, but after locating the actual
documentation on Cisco's site versus EMC I was set.  Let me know if you
want the script I hacked together, but again, it's not pretty. ..."

He is willing to send me the script, and I will try to pursue that
avenue next, unless you have another idea.

Thanks,
Faron


-----Original Message-----
From: Ed Ravin [mailto:eravin at panix.com]
Sent: Wednesday, December 14, 2005 11:56 AM
To: Hopper, Faron W.
Cc: rancid-discuss at shrubbery.net
Subject: Re: cisco 9509 fiber switch not working

On Wed, Dec 14, 2005 at 12:33:03PM -0500, Hopper, Faron  W. wrote:
>
> Hello all,
>      I have a cisco 9509 fiber switch that I can't get rancid to
> recognize.  I can clogin -c "show version" to it and it provides the
> show version command and then exits.  When I try to run a rancid-run
-r
> device to it, it produces the following log file
>
> ==============================================================
> starting: Wed Dec 14 10:55:06 CST 2005
>
> Trying to get all of the configs.
> cod-cisco-9509-1: End of run not found

[...]

What platform are you using, and what version of RANCID?  Also, read the
release notes in RANCID about how some versions of Expect need to be
patched.

Have you tried "rancid -d" to get debug output?

Sometimes this error means rancid didn't find the last command ("exit"),
but
in your case, it's there at the end of the output:

  ^MCoD-Cisco-9509-1#exit^M
  Connection closed by foreign host.

> The .raw file makes me think that it can't parse the error from the
> write term command (which is not supported on this device).

That's not the problem - you'll note that "show running-config" was
also sent and recognized.  rancid is smart enough to use whichever one
worked.




From faron.hopper at capgemini.com  Thu Dec 15 19:00:10 2005
From: faron.hopper at capgemini.com (Hopper, Faron  W.)
Date: Thu, 15 Dec 2005 14:00:10 -0500
Subject: cisco 9509 fiber switch not working
Message-ID: <0D9EF3454D8EFC4B8BFFD2B862941681D093FC@caonmastxm03.na.capgemini.com>


John,
	When I do a find for rancid.in, I don't find it on my system.
What file do you want me to apply the patch to?

find / rancid.in | grep -i rancid.in
/usr/local/man/man1/rancid_intro.1.gz
/usr/local/share/rancid/index.html
find: rancid.in: No such file or directory
ckcus0002-cfgbak01#


Thanks,
Faron
-----Original Message-----
From: john heasley [mailto:heas at shrubbery.net]
Sent: Wednesday, December 14, 2005 5:52 PM
To: Hopper, Faron W.; heas at ni.shrubbery.net
Subject: Re: cisco 9509 fiber switch not working

Wed, Dec 14, 2005 at 03:00:06PM -0500, Hopper, Faron  W.:
>
>
> I did try that, and the css as well.  I received the same results.

think I see the problem.  try this patch; you'll probably have to apply
it by hand.

can you tell me what version of rancid you are using?  your .raw file is
missing some commands.

Index: rancid.in
===================================================================
RCS file: /home/rancid/.CVS/rancid/bin/rancid.in,v
retrieving revision 1.198
diff -d -u -1 -0 -r1.198 rancid.in
--- rancid.in	5 Dec 2005 21:13:07 -0000	1.198
+++ rancid.in	14 Dec 2005 23:48:31 -0000
@@ -1325,23 +1338,23 @@
     return(0);
 }

 # This routine processes a "write term"
 sub WriteTerm {
     print STDERR "    In WriteTerm: $_" if ($debug);
     my($lineauto,$comment,$linecnt) = (0,0,0);

     while (<INPUT>) {
 	tr/\015//d;
-	last if(/^$prompt/);
+	last if (/^$prompt/);
 	return(1) if /Line has invalid autocommand /;
-	return(1) if /(Invalid input detected|Type help or )/;
+	return(1) if /(invalid input detected|type help or )/i;
 	return(-1) if (/command authorization failed/i);
 	# the pager can not be disabled per-session on the PIX
 	if (/^(<-+ More -+>)/) {
 	    my($len) = length($1);
 	    s/^$1\s{$len}//;
 	}

 	/Non-Volatile memory is in use/  && return(-1); # NvRAM is
locked
 	return(0) if ($found_end);		# Only do this routine
once
 	$linecnt++;





From faron.hopper at capgemini.com  Thu Dec 15 21:44:05 2005
From: faron.hopper at capgemini.com (Hopper, Faron  W.)
Date: Thu, 15 Dec 2005 16:44:05 -0500
Subject: cisco 9509 fiber switch not working
Message-ID: <0D9EF3454D8EFC4B8BFFD2B862941681D0947F@caonmastxm03.na.capgemini.com>


John,
	Here are my results for the patch.


-----Original Message-----
From: john heasley [mailto:heas at shrubbery.net]
Sent: Thursday, December 15, 2005 1:21 PM
To: Hopper, Faron W.
Subject: Re: cisco 9509 fiber switch not working

Thu, Dec 15, 2005 at 02:00:10PM -0500, Hopper, Faron  W.:
>
> John,
> 	When I do a find for rancid.in, I don't find it on my system.
> What file do you want me to apply the patch to?
>
> find / rancid.in | grep -i rancid.in
> /usr/local/man/man1/rancid_intro.1.gz
> /usr/local/share/rancid/index.html
> find: rancid.in: No such file or directory
> ckcus0002-cfgbak01#

rancid.in is dist. w/ the source and is converted to rancid in the make
process.  just look for rancid, prob. /usr/local/bin/rancid.

>
> Thanks,
> Faron
> -----Original Message-----
> From: john heasley [mailto:heas at shrubbery.net]
> Sent: Wednesday, December 14, 2005 5:52 PM
> To: Hopper, Faron W.; heas at ni.shrubbery.net
> Subject: Re: cisco 9509 fiber switch not working
>
> Wed, Dec 14, 2005 at 03:00:06PM -0500, Hopper, Faron  W.:
> >
> >
> > I did try that, and the css as well.  I received the same results.
>
> think I see the problem.  try this patch; you'll probably have to
apply
> it by hand.
>
> can you tell me what version of rancid you are using?  your .raw file
is
> missing some commands.
>
> Index: rancid.in
> ===================================================================
> RCS file: /home/rancid/.CVS/rancid/bin/rancid.in,v
> retrieving revision 1.198
> diff -d -u -1 -0 -r1.198 rancid.in
> --- rancid.in	5 Dec 2005 21:13:07 -0000	1.198
> +++ rancid.in	14 Dec 2005 23:48:31 -0000
> @@ -1325,23 +1338,23 @@
>      return(0);
>  }
>
>  # This routine processes a "write term"
>  sub WriteTerm {
>      print STDERR "    In WriteTerm: $_" if ($debug);
>      my($lineauto,$comment,$linecnt) = (0,0,0);
>
>      while (<INPUT>) {
>  	tr/\015//d;
> -	last if(/^$prompt/);
> +	last if (/^$prompt/);
>  	return(1) if /Line has invalid autocommand /;
> -	return(1) if /(Invalid input detected|Type help or )/;
> +	return(1) if /(invalid input detected|type help or )/i;
>  	return(-1) if (/command authorization failed/i);
>  	# the pager can not be disabled per-session on the PIX
>  	if (/^(<-+ More -+>)/) {
>  	    my($len) = length($1);
>  	    s/^$1\s{$len}//;
>  	}
>
>  	/Non-Volatile memory is in use/  && return(-1); # NvRAM is
> locked
>  	return(0) if ($found_end);		# Only do this routine
> once
>  	$linecnt++;
>
>
>
>



From faron.hopper at capgemini.com  Thu Dec 15 23:39:25 2005
From: faron.hopper at capgemini.com (Hopper, Faron  W.)
Date: Thu, 15 Dec 2005 18:39:25 -0500
Subject: cisco 9509 fiber switch not working
Message-ID: <0D9EF3454D8EFC4B8BFFD2B862941681D094AC@caonmastxm03.na.capgemini.com>


John,
    I change the lines by hand.  I edited the lines that had a - symbol
beside them and change them to what the line looked like with the +
symbol.  Here is the diff

ckcus0002-cfgbak01# diff rancid rancid.bak
1132c1132
<       last if (/^$prompt/);
---
>       last if(/^$prompt/);
1134c1134
<       return(1) if /(invalid input detected|iype help or )/i;
---
>       return(1) if /(Invalid input detected|Type help or )/;

If I did that right, then I ran the rancid -d cod-cisco-9509-1 command
and received the same results (listed below).  Thanks, Faron

netcfgbak at ckcus0002-cfgbak01$ rancid -d cod-cisco-9509-1
executing clogin -t 90 -c"show version;show redundancy secondary;show
idprom backplane;show install active;show env all;show rsp
chassis-info;show gsr chassis;show boot;show bootvar;show variables
boot;show flash;dir /all nvram:;dir /all bootflash:;dir /all slot0:;dir
/all disk0:;dir /all slot1:;dir /all disk1:;dir /all slot2:;dir /all
disk2:;dir /all harddisk:;dir /all harddiska:;dir /all harddiskb:;dir
/all sup-bootflash:;dir /all sup-microcode:;dir /all slavenvram:;dir
/all slavebootflash:;dir /all slaveslot0:;dir /all slavedisk0:;dir /all
slaveslot1:;dir /all slavedisk1:;dir /all slaveslot2:;dir /all
slavedisk2:;dir /all slavesup-bootflash:;dir /all sec-nvram:;dir /all
sec-bootflash:;dir /all sec-slot0:;dir /all sec-disk0:;dir /all
sec-slot1:;dir /all sec-disk1:;dir /all sec-slot2:;dir /all
sec-disk2:;show controllers;show controllers cbus;show diagbus;show
diag;show module;show spe version;show c7200;show vtp status;show
vlan;show running-config;write term" cod-cisco-9509-1
PROMPT MATCH: CoD-Cisco-9509-1#
HIT COMMAND:CoD-Cisco-9509-1#  show version
    In ShowVersion: CoD-Cisco-9509-1#  show version
HIT COMMAND:CoD-Cisco-9509-1# show redundancy secondary
    In ShowRedundancy: CoD-Cisco-9509-1# show redundancy secondary
HIT COMMAND:CoD-Cisco-9509-1# show idprom backplane
    In ShowIDprom: CoD-Cisco-9509-1# show idprom backplane
HIT COMMAND:CoD-Cisco-9509-1# show install active
    In ShowInstallActive: CoD-Cisco-9509-1# show install active
HIT COMMAND:CoD-Cisco-9509-1# show env all
    In ShowEnv: CoD-Cisco-9509-1# show env all
HIT COMMAND:CoD-Cisco-9509-1# show rsp chassis-info
    In ShowRSP: CoD-Cisco-9509-1# show rsp chassis-info
HIT COMMAND:CoD-Cisco-9509-1# show gsr chassis
    In ShowGSR: CoD-Cisco-9509-1# show gsr chassis
HIT COMMAND:CoD-Cisco-9509-1# show boot
    In ShowBoot: CoD-Cisco-9509-1# show boot
HIT COMMAND:CoD-Cisco-9509-1# show bootvar
    In ShowBoot: CoD-Cisco-9509-1# show bootvar
HIT COMMAND:CoD-Cisco-9509-1# show variables boot
    In ShowBoot: CoD-Cisco-9509-1# show variables boot
HIT COMMAND:CoD-Cisco-9509-1# show flash
    In ShowFlash: CoD-Cisco-9509-1# show flash
HIT COMMAND:CoD-Cisco-9509-1# dir /all nvram:
    In DirSlotN: CoD-Cisco-9509-1# dir /all nvram:
HIT COMMAND:CoD-Cisco-9509-1# dir /all bootflash:
    In DirSlotN: CoD-Cisco-9509-1# dir /all bootflash:
HIT COMMAND:CoD-Cisco-9509-1# dir /all slot0:
    In DirSlotN: CoD-Cisco-9509-1# dir /all slot0:
HIT COMMAND:CoD-Cisco-9509-1# dir /all disk0:
    In DirSlotN: CoD-Cisco-9509-1# dir /all disk0:
HIT COMMAND:CoD-Cisco-9509-1# dir /all slot1:
    In DirSlotN: CoD-Cisco-9509-1# dir /all slot1:
HIT COMMAND:CoD-Cisco-9509-1# dir /all disk1:
    In DirSlotN: CoD-Cisco-9509-1# dir /all disk1:
HIT COMMAND:CoD-Cisco-9509-1# dir /all slot2:
    In DirSlotN: CoD-Cisco-9509-1# dir /all slot2:
HIT COMMAND:CoD-Cisco-9509-1# dir /all disk2:
    In DirSlotN: CoD-Cisco-9509-1# dir /all disk2:
HIT COMMAND:CoD-Cisco-9509-1# dir /all harddisk:
    In DirSlotN: CoD-Cisco-9509-1# dir /all harddisk:
HIT COMMAND:CoD-Cisco-9509-1# dir /all harddiska:
    In DirSlotN: CoD-Cisco-9509-1# dir /all harddiska:
HIT COMMAND:CoD-Cisco-9509-1# dir /all harddiskb:
    In DirSlotN: CoD-Cisco-9509-1# dir /all harddiskb:
HIT COMMAND:CoD-Cisco-9509-1# dir /all sup-bootflash:
    In DirSlotN: CoD-Cisco-9509-1# dir /all sup-bootflash:
HIT COMMAND:CoD-Cisco-9509-1# dir /all sup-microcode:
    In DirSlotN: CoD-Cisco-9509-1# dir /all sup-microcode:
HIT COMMAND:CoD-Cisco-9509-1# dir /all slavenvram:
    In DirSlotN: CoD-Cisco-9509-1# dir /all slavenvram:
HIT COMMAND:CoD-Cisco-9509-1# dir /all slavebootflash:
    In DirSlotN: CoD-Cisco-9509-1# dir /all slavebootflash:
HIT COMMAND:CoD-Cisco-9509-1# dir /all slaveslot0:
    In DirSlotN: CoD-Cisco-9509-1# dir /all slaveslot0:
HIT COMMAND:CoD-Cisco-9509-1# dir /all slavedisk0:
    In DirSlotN: CoD-Cisco-9509-1# dir /all slavedisk0:
HIT COMMAND:CoD-Cisco-9509-1# dir /all slaveslot1:
    In DirSlotN: CoD-Cisco-9509-1# dir /all slaveslot1:
HIT COMMAND:CoD-Cisco-9509-1# dir /all slavedisk1:
    In DirSlotN: CoD-Cisco-9509-1# dir /all slavedisk1:
HIT COMMAND:CoD-Cisco-9509-1# dir /all slaveslot2:
    In DirSlotN: CoD-Cisco-9509-1# dir /all slaveslot2:
HIT COMMAND:CoD-Cisco-9509-1# dir /all slavedisk2:
    In DirSlotN: CoD-Cisco-9509-1# dir /all slavedisk2:
HIT COMMAND:CoD-Cisco-9509-1# dir /all slavesup-bootflash:
    In DirSlotN: CoD-Cisco-9509-1# dir /all slavesup-bootflash:
HIT COMMAND:CoD-Cisco-9509-1# dir /all sec-nvram:
    In DirSlotN: CoD-Cisco-9509-1# dir /all sec-nvram:
HIT COMMAND:CoD-Cisco-9509-1# dir /all sec-bootflash:
    In DirSlotN: CoD-Cisco-9509-1# dir /all sec-bootflash:
HIT COMMAND:CoD-Cisco-9509-1# dir /all sec-slot0:
    In DirSlotN: CoD-Cisco-9509-1# dir /all sec-slot0:
HIT COMMAND:CoD-Cisco-9509-1# dir /all sec-disk0:
    In DirSlotN: CoD-Cisco-9509-1# dir /all sec-disk0:
HIT COMMAND:CoD-Cisco-9509-1# dir /all sec-slot1:
    In DirSlotN: CoD-Cisco-9509-1# dir /all sec-slot1:
HIT COMMAND:CoD-Cisco-9509-1# dir /all sec-disk1:
    In DirSlotN: CoD-Cisco-9509-1# dir /all sec-disk1:
HIT COMMAND:CoD-Cisco-9509-1# dir /all sec-slot2:
    In DirSlotN: CoD-Cisco-9509-1# dir /all sec-slot2:
HIT COMMAND:CoD-Cisco-9509-1# dir /all sec-disk2:
    In DirSlotN: CoD-Cisco-9509-1# dir /all sec-disk2:
HIT COMMAND:CoD-Cisco-9509-1# show controllers
    In ShowContAll: CoD-Cisco-9509-1# show controllers
HIT COMMAND:CoD-Cisco-9509-1# show controllers cbus
    In ShowContCbus: CoD-Cisco-9509-1# show controllers cbus
HIT COMMAND:CoD-Cisco-9509-1# show diagbus
    In ShowDiagbus: CoD-Cisco-9509-1# show diagbus
HIT COMMAND:CoD-Cisco-9509-1# show diag
    In ShowDiag: CoD-Cisco-9509-1# show diag
HIT COMMAND:CoD-Cisco-9509-1# show module
    In ShowModule: CoD-Cisco-9509-1# show module
HIT COMMAND:CoD-Cisco-9509-1# show spe version
    In ShowSpeVersion: CoD-Cisco-9509-1# show spe version
HIT COMMAND:CoD-Cisco-9509-1# show c7200
    In ShowC7200: CoD-Cisco-9509-1# show c7200
HIT COMMAND:CoD-Cisco-9509-1# show vtp status
    In ShowVTP: CoD-Cisco-9509-1# show vtp status
HIT COMMAND:CoD-Cisco-9509-1# show vlan
    In ShowVLAN: CoD-Cisco-9509-1# show vlan
HIT COMMAND:CoD-Cisco-9509-1# show running-config
    In WriteTerm: CoD-Cisco-9509-1# show running-config
HIT COMMAND:CoD-Cisco-9509-1# write term
    In WriteTerm: CoD-Cisco-9509-1# write term
cod-cisco-9509-1: End of run not found
cod-cisco-9509-1: End of run not found



and the .new files is as follows

netcfgbak at ckcus0002-cfgbak01$ cat cod-cisco-9509-1.new
!RANCID-CONTENT-TYPE: cisco
!
!
!
!
!
!
!
!
!
!BootFlash: sup-1
!BootFlash: kickstart variable =
bootflash:/m9500-sf1ek9-kickstart-mz.2.0.2b.bin
!BootFlash: system variable = bootflash:/m9500-sf1ek9-mz.2.0.2b.bin
!BootFlash: sup-2
!BootFlash: kickstart variable =
bootflash:/m9500-sf1ek9-kickstart-mz.2.0.2b.bin
!BootFlash: system variable = bootflash:/m9500-sf1ek9-mz.2.0.2b.bin
!BootFlash: No module boot variable set
!
!
!Slot 1: type 1/2 Gbps FC Module, 16 ports
!Slot 1: part DS-X9016, serial ok
!
!Slot 2: type 1/2 Gbps FC Module, 32 ports
!Slot 2: part DS-X9032, serial ok
!
!Slot 3: type 1/2 Gbps FC Module, 32 ports
!Slot 3: part DS-X9032, serial ok
!
!Slot 4: type 1/2 Gbps FC Module, 32 ports
!Slot 4: part DS-X9032, serial ok
!
!Slot 5: type Supervisor/Fabric-1              DS-X9530-SF1-K9, 0 ports
!Slot 5: part active, serial *
!
!Slot 6: type Supervisor/Fabric-1, 0 ports
!Slot 6: part DS-X9530-SF1-K9, serial ha-standby
!
version 2.0(2b)
fcid-allocation area company-id 0x001125
fcid-allocation area company-id 0x005076
fcdomain fcid persistent vsan 1
fcdomain fcid database
  vsan 1 wwn 50:05:07:68:01:40:1a:51 fcid 0x390000 area dynamic
  vsan 1 wwn 50:05:07:68:01:10:1a:51 fcid 0x390100 area dynamic
  vsan 1 wwn 50:05:07:68:01:40:1a:0d fcid 0x390200 area dynamic
  vsan 1 wwn 50:05:07:68:01:10:1a:0d fcid 0x390300 area dynamic
  vsan 1 wwn 20:08:00:a0:b8:18:67:03 fcid 0x390400 area dynamic
  vsan 1 wwn 20:09:00:a0:b8:18:67:03 fcid 0x390500 area dynamic
  vsan 1 wwn 20:06:00:a0:b8:18:75:9d fcid 0x390600 area dynamic
  vsan 1 wwn 20:07:00:a0:b8:18:75:9d fcid 0x390700 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:52 fcid 0x390800 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:1e fcid 0x390900 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:3c fcid 0x390a00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:46 fcid 0x390b00 area dynamic
  vsan 1 wwn 50:05:07:68:01:30:1a:51 fcid 0x390c00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:82 fcid 0x390d00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:19 fcid 0x390e00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:94:85 fcid 0x390f00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:4b fcid 0x391000 area dynamic
  vsan 1 wwn 50:05:07:68:01:20:1a:51 fcid 0x391100 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:97:39 fcid 0x391200 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:96:40 fcid 0x391300 area dynamic
  vsan 1 wwn 50:05:07:68:01:30:1a:0d fcid 0x391400 area dynamic
  vsan 1 wwn 50:05:07:68:01:20:1a:0d fcid 0x391500 area dynamic
  vsan 1 wwn 20:08:00:a0:b8:18:67:04 fcid 0x391600 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:3d fcid 0x391700 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:53 fcid 0x391800 area dynamic
  vsan 1 wwn 20:09:00:a0:b8:18:67:04 fcid 0x391900 area dynamic
  vsan 1 wwn 20:06:00:a0:b8:18:75:9e fcid 0x391a00 area dynamic
  vsan 1 wwn 20:07:00:a0:b8:18:75:9e fcid 0x391b00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:96:3a fcid 0x391c00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:aa:94 fcid 0x391d00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:26 fcid 0x391e00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:ac fcid 0x391f00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:ba fcid 0x392000 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:97:4a fcid 0x392100 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:6c fcid 0x392200 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:b6 fcid 0x392300 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:8a fcid 0x392400 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:5a fcid 0x392500 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:84 fcid 0x392600 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:9e fcid 0x392700 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:6e fcid 0x392800 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:94:30 fcid 0x392900 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:ae fcid 0x392a00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:9c fcid 0x392b00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:aa:ac fcid 0x392c00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:80 fcid 0x392d00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:96:8a fcid 0x392e00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:96:3b fcid 0x392f00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:4a fcid 0x393000 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:97:38 fcid 0x393100 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:94:84 fcid 0x393200 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:18 fcid 0x393300 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:96:66 fcid 0x393400 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:0e fcid 0x393500 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:96:67 fcid 0x393600 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:b4 fcid 0x393700 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:0f fcid 0x393800 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:b5 fcid 0x393900 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:6a fcid 0x393a00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:6b fcid 0x393b00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:10 fcid 0x393c00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:96:98 fcid 0x393d00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:11 fcid 0x393e00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:96:99 fcid 0x393f00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:32 fcid 0x394000 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:aa:70 fcid 0x394100 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:33 fcid 0x394200 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:96:14 fcid 0x394300 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:aa:71 fcid 0x394400 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:96:15 fcid 0x394500 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:95:9a fcid 0x394600 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:95:9b fcid 0x394700 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:58 fcid 0x394800 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:59 fcid 0x394900 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:16 fcid 0x394a00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:17 fcid 0x394b00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:7f fcid 0x394c00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:ad fcid 0x394d00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:bb fcid 0x394e00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:b7 fcid 0x394f00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:6d fcid 0x395000 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:97:4b fcid 0x395100 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:8b fcid 0x395200 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:af fcid 0x395300 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:5b fcid 0x395400 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:85 fcid 0x395500 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:9f fcid 0x395600 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:6f fcid 0x395700 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:94:31 fcid 0x395800 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:9d fcid 0x395900 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:aa:ad fcid 0x395a00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:96:41 fcid 0x395b00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:1f fcid 0x395c00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:47 fcid 0x395d00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:83 fcid 0x395e00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:27 fcid 0x395f00 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:aa:95 fcid 0x396000 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:96:8b fcid 0x396100 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:81 fcid 0x396200 area dynamic
  vsan 1 wwn 21:00:00:11:25:92:93:7e fcid 0x396300 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:9c fcid 0x396400 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:9d fcid 0x396500 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:94:30 fcid 0x396600 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:94:31 fcid 0x396700 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:84 fcid 0x396800 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:85 fcid 0x396900 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:97:38 fcid 0x396a00 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:97:39 fcid 0x396b00 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:94:84 fcid 0x396c00 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:4a fcid 0x396d00 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:82 fcid 0x396e00 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:46 fcid 0x396f00 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:aa:94 fcid 0x397000 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:1e fcid 0x397100 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:96:8a fcid 0x397200 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:94:85 fcid 0x397300 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:4b fcid 0x397400 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:52 fcid 0x397500 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:83 fcid 0x397600 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:47 fcid 0x397700 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:96:40 fcid 0x397800 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:aa:95 fcid 0x397900 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:1f fcid 0x397a00 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:3c fcid 0x397b00 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:96:8b fcid 0x397c00 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:26 fcid 0x397d00 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:53 fcid 0x397e00 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:96:41 fcid 0x397f00 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:3d fcid 0x398000 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:27 fcid 0x398100 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:ba fcid 0x398200 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:bb fcid 0x398300 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:8a fcid 0x398400 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:b6 fcid 0x398500 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:ae fcid 0x398600 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:ac fcid 0x398700 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:8b fcid 0x398800 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:af fcid 0x398900 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:5a fcid 0x398a00 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:aa:ac fcid 0x398b00 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:b7 fcid 0x398c00 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:97:4a fcid 0x398d00 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:9e fcid 0x398e00 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:6e fcid 0x398f00 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:ad fcid 0x399000 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:5b fcid 0x399100 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:aa:ad fcid 0x399200 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:6f fcid 0x399300 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:97:4b fcid 0x399400 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:9f fcid 0x399500 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:6c fcid 0x399600 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:6d fcid 0x399700 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:96:66 fcid 0x399800 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:96:67 fcid 0x399900 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:96:3a fcid 0x399a00 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:96:3b fcid 0x399b00 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:aa:71 fcid 0x399c00 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:0e fcid 0x399d00 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:0f fcid 0x399e00 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:6a fcid 0x399f00 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:6b fcid 0x39a000 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:b4 fcid 0x39a100 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:b5 fcid 0x39a200 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:10 fcid 0x39a300 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:11 fcid 0x39a400 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:58 fcid 0x39a500 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:16 fcid 0x39a600 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:59 fcid 0x39a700 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:17 fcid 0x39a800 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:32 fcid 0x39a900 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:33 fcid 0x39aa00 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:96:98 fcid 0x39ab00 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:96:99 fcid 0x39ac00 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:96:15 fcid 0x39ad00 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:95:9b fcid 0x39ae00 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:7f fcid 0x39af00 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:18 fcid 0x39b000 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:93:19 fcid 0x39b100 area dynamic
  vsan 1 wwn 21:00:00:11:25:12:aa:70 fcid 0x39b200 area dynamic
switchname CoD-Cisco-9509-1
boot kickstart bootflash:/m9500-sf1ek9-kickstart-mz.2.0.2b.bin sup-1
boot system bootflash:/m9500-sf1ek9-mz.2.0.2b.bin sup-1
boot kickstart bootflash:/m9500-sf1ek9-kickstart-mz.2.0.2b.bin sup-2
boot system bootflash:/m9500-sf1ek9-mz.2.0.2b.bin sup-2
ip default-gateway 206.245.27.1
role name default-role
  description This is a system defined role and applies to all users
  rule 1 permit show feature system
  rule 2 permit show feature snmp
  rule 3 permit show feature module
  rule 4 permit show feature interface
  rule 5 permit show feature hardware
  rule 6 permit show feature environment
kernel core target 0.0.0.0
kernel core limit 1

snmp-server user localizedkey
snmp-server user localizedkey
username
username
ssh key dsa 1024 force


callhome
  switch-priority 7


snmp-server enable traps license



fcalias name SVC-N1-H1-P1 vsan 1
    member pwwn 50:05:07:68:01:40:1a:51

fcalias name SVC-N1-H1-P2 vsan 1
    member pwwn 50:05:07:68:01:30:1a:51

fcalias name SVC-N1-H2-P1 vsan 1
    member pwwn 50:05:07:68:01:10:1a:51

fcalias name SVC-N2-H1-P1 vsan 1
    member pwwn 50:05:07:68:01:40:1a:0d

fcalias name SVC-N2-H2-P1 vsan 1
    member pwwn 50:05:07:68:01:10:1a:0d

fcalias name DS43-CA-P1 vsan 1
    member pwwn 20:08:00:a0:b8:18:67:03

fcalias name DS43-CB-P1 vsan 1
    member pwwn 20:09:00:a0:b8:18:67:03

fcalias name DS41-CA-P1 vsan 1
    member pwwn 20:06:00:a0:b8:18:75:9d

fcalias name DS41-CB-P1 vsan 1
    member pwwn 20:07:00:a0:b8:18:75:9d

fcalias name SVC-N1-H2-P2 vsan 1
    member pwwn 50:05:07:68:01:20:1a:51

fcalias name SVC-N2-H1-P2 vsan 1
    member pwwn 50:05:07:68:01:30:1a:0d

fcalias name SVC-N2-H2-P2 vsan 1
    member pwwn 50:05:07:68:01:20:1a:0d

fcalias name DS43-CA-P2 vsan 1
    member pwwn 20:08:00:a0:b8:18:67:04

fcalias name DS43-CB-P2 vsan 1
    member pwwn 20:09:00:a0:b8:18:67:04

fcalias name DS41-CA-P2 vsan 1
    member pwwn 20:06:00:a0:b8:18:75:9e

fcalias name DS41-CB-P2 vsan 1
    member pwwn 20:07:00:a0:b8:18:75:9e

fcalias name codibm01 vsan 1
    member pwwn 21:00:00:11:25:12:93:18
    member pwwn 21:00:00:11:25:12:93:19

fcalias name codibm01-os vsan 1
    member pwwn 21:00:00:11:25:12:93:18

fcalias name codibm02 vsan 1
    member pwwn 21:00:00:11:25:12:94:84
    member pwwn 21:00:00:11:25:12:94:85

fcalias name codibm29 vsan 1
    member pwwn 21:00:00:11:25:92:96:3a
    member pwwn 21:00:00:11:25:92:96:3b

fcalias name codibm03 vsan 1
    member pwwn 21:00:00:11:25:12:97:39
    member pwwn 21:00:00:11:25:12:97:38

fcalias name codibm04 vsan 1
    member pwwn 21:00:00:11:25:12:93:4a
    member pwwn 21:00:00:11:25:12:93:4b

fcalias name codibm05 vsan 1
    member pwwn 21:00:00:11:25:92:93:80
    member pwwn 21:00:00:11:25:92:93:81

fcalias name codibm15 vsan 1
    member pwwn 21:00:00:11:25:12:93:ac
    member pwwn 21:00:00:11:25:12:93:ad

fcalias name codibm16 vsan 1
    member pwwn 21:00:00:11:25:12:93:ba
    member pwwn 21:00:00:11:25:12:93:bb

fcalias name codibm17 vsan 1
    member pwwn 21:00:00:11:25:12:93:6c
    member pwwn 21:00:00:11:25:12:93:6d

fcalias name codibm18 vsan 1
    member pwwn 21:00:00:11:25:12:93:b6
    member pwwn 21:00:00:11:25:12:93:b7

fcalias name codibm19 vsan 1
    member pwwn 21:00:00:11:25:12:97:4a
    member pwwn 21:00:00:11:25:12:97:4b

fcalias name codibm06 vsan 1
    member pwwn 21:00:00:11:25:12:96:8b

fcalias name codibm31 vsan 1
    member pwwn 21:00:00:11:25:12:93:0e
    member pwwn 21:00:00:11:25:12:93:0f

fcalias name codibm03-os vsan 1
    member pwwn 21:00:00:11:25:12:97:38

fcalias name codibm30 vsan 1
    member pwwn 21:00:00:11:25:12:96:66
    member pwwn 21:00:00:11:25:12:96:67

fcalias name codibm32 vsan 1
    member pwwn 21:00:00:11:25:12:93:b4
    member pwwn 21:00:00:11:25:12:93:b5

fcalias name codibm39 vsan 1
    member pwwn 21:00:00:11:25:12:93:7f

fcalias name codibm33 vsan 1
    member pwwn 21:00:00:11:25:12:93:6a
    member pwwn 21:00:00:11:25:12:93:6b

fcalias name codibm34 vsan 1
    member pwwn 21:00:00:11:25:12:93:10
    member pwwn 21:00:00:11:25:12:93:11

fcalias name codibm35 vsan 1
    member pwwn 21:00:00:11:25:12:96:98
    member pwwn 21:00:00:11:25:12:96:99

fcalias name codibm37 vsan 1

fcalias name codibm38 vsan 1
    member pwwn 21:00:00:11:25:12:96:15

fcalias name codibm40 vsan 1
    member pwwn 21:00:00:11:25:12:95:9b

fcalias name codibm41 vsan 1
    member pwwn 21:00:00:11:25:12:93:58
    member pwwn 21:00:00:11:25:12:93:59

fcalias name codibm42 vsan 1
    member pwwn 21:00:00:11:25:12:93:16

fcalias name codibm26 vsan 1
    member pwwn 21:00:00:11:25:12:94:30
    member pwwn 21:00:00:11:25:12:94:31

fcalias name codibm23 vsan 1
    member pwwn 21:00:00:11:25:12:93:84
    member pwwn 21:00:00:11:25:12:93:85

fcalias name codibm27 vsan 1
    member pwwn 21:00:00:11:25:12:93:9c
    member pwwn 21:00:00:11:25:12:93:9d

fcalias name codibm20 vsan 1
    member pwwn 21:00:00:11:25:12:93:8a
    member pwwn 21:00:00:11:25:12:93:8b

fcalias name codibm21 vsan 1
    member pwwn 21:00:00:11:25:12:93:ae
    member pwwn 21:00:00:11:25:12:93:af

fcalias name codibm22 vsan 1
    member pwwn 21:00:00:11:25:12:93:5a
    member pwwn 21:00:00:11:25:12:93:5b

fcalias name codibm24 vsan 1
    member pwwn 21:00:00:11:25:12:93:9e
    member pwwn 21:00:00:11:25:12:93:9f

fcalias name codibm25 vsan 1
    member pwwn 21:00:00:11:25:12:93:6e
    member pwwn 21:00:00:11:25:12:93:6f

fcalias name codibm28 vsan 1
    member pwwn 21:00:00:11:25:12:aa:ac
    member pwwn 21:00:00:11:25:12:aa:ad

zone broadcast enable vsan 1



zone name SVC-disk vsan 1
    member fcalias SVC-N1-H1-P1
    member fcalias SVC-N1-H2-P1
    member fcalias SVC-N2-H1-P1
    member fcalias SVC-N2-H2-P1
    member fcalias DS43-CA-P1
    member fcalias DS43-CB-P1
    member fcalias DS41-CA-P1
    member fcalias DS41-CB-P1
    member fcalias DS43-CA-P2
    member fcalias DS43-CB-P2
    member fcalias DS41-CA-P2
    member fcalias DS41-CB-P2

zone name SVC-winOS vsan 1
    member pwwn 21:00:00:11:25:12:93:ad
    member fcalias SVC-N2-H1-P2
    member fcalias codibm01-os
    member fcalias codibm02
    member fcalias codibm16
    member fcalias codibm06

zone name SVC-win vsan 1
    member pwwn 21:00:00:11:25:12:93:bb
    member pwwn 21:00:00:11:25:12:93:ba
    member pwwn 21:00:00:11:25:92:93:19
    member pwwn 21:00:00:11:25:92:93:18
    member pwwn 21:00:00:11:25:12:94:85
    member pwwn 21:00:00:11:25:12:94:84
    member fcalias SVC-N1-H1-P2
    member fcalias SVC-N1-H2-P2
    member fcalias SVC-N2-H1-P2
    member fcalias SVC-N2-H2-P2
    member fcalias codibm02

zone name SVC-linux vsan 1
    member pwwn 21:00:00:11:25:12:93:85
    member pwwn 21:00:00:11:25:12:93:84
    member pwwn 21:00:00:11:25:12:94:31
    member pwwn 21:00:00:11:25:12:94:30
    member pwwn 21:00:00:11:25:12:93:9d
    member pwwn 21:00:00:11:25:12:93:9c
    member pwwn 21:00:00:11:25:12:96:3b
    member pwwn 21:00:00:11:25:12:96:3a
    member pwwn 21:00:00:11:25:12:93:7f
    member pwwn 21:00:00:11:25:12:aa:95
    member pwwn 21:00:00:11:25:12:96:67
    member pwwn 21:00:00:11:25:12:96:66
    member pwwn 21:00:00:11:25:12:93:0f
    member pwwn 21:00:00:11:25:12:93:0e
    member pwwn 21:00:00:11:25:12:93:b5
    member pwwn 21:00:00:11:25:12:93:b4
    member pwwn 21:00:00:11:25:12:93:6b
    member pwwn 21:00:00:11:25:12:93:6a
    member pwwn 21:00:00:11:25:12:93:11
    member pwwn 21:00:00:11:25:12:93:10
    member pwwn 21:00:00:11:25:12:96:99
    member pwwn 21:00:00:11:25:12:96:98
    member pwwn 21:00:00:11:25:12:aa:94
    member pwwn 21:00:00:11:25:12:93:27
    member pwwn 21:00:00:11:25:12:aa:71
    member pwwn 21:00:00:11:25:12:93:26
    member pwwn 21:00:00:11:25:12:96:15
    member pwwn 21:00:00:11:25:12:93:83
    member pwwn 21:00:00:11:25:12:95:9b
    member pwwn 21:00:00:11:25:12:93:82
    member pwwn 21:00:00:11:25:12:93:59
    member pwwn 21:00:00:11:25:12:93:58
    member pwwn 21:00:00:11:25:12:93:47
    member pwwn 21:00:00:11:25:12:93:16
    member pwwn 21:00:00:11:25:12:93:46
    member pwwn 21:00:00:11:25:12:93:1f
    member pwwn 21:00:00:11:25:12:93:1e
    member pwwn 21:00:00:11:25:12:96:41
    member pwwn 21:00:00:11:25:12:93:6d
    member pwwn 21:00:00:11:25:12:93:6c
    member pwwn 21:00:00:11:25:12:93:b7
    member pwwn 21:00:00:11:25:12:93:b6
    member pwwn 21:00:00:11:25:12:97:4b
    member pwwn 21:00:00:11:25:12:97:4a
    member pwwn 21:00:00:11:25:12:93:8b
    member pwwn 21:00:00:11:25:12:93:8a
    member pwwn 21:00:00:11:25:12:93:af
    member pwwn 21:00:00:11:25:12:93:ae
    member pwwn 21:00:00:11:25:12:93:5b
    member pwwn 21:00:00:11:25:12:93:5a
    member pwwn 21:00:00:11:25:12:93:9f
    member pwwn 21:00:00:11:25:12:93:9e
    member pwwn 21:00:00:11:25:12:93:6f
    member pwwn 21:00:00:11:25:12:93:6e
    member pwwn 21:00:00:11:25:12:aa:ad
    member pwwn 21:00:00:11:25:12:aa:ac
    member pwwn 21:00:00:11:25:12:96:40
    member pwwn 21:00:00:11:25:12:93:3d
    member pwwn 21:00:00:11:25:12:93:3c
    member pwwn 21:00:00:11:25:12:93:53
    member pwwn 21:00:00:11:25:12:93:52
    member fcalias SVC-N1-H1-P2
    member fcalias SVC-N1-H2-P2
    member fcalias SVC-N2-H1-P2
    member fcalias SVC-N2-H2-P2

zone name SVC-linuxOS vsan 1
    member pwwn 21:00:00:11:25:92:93:80
    member pwwn 21:00:00:11:25:12:93:4a
    member pwwn 21:00:00:11:25:12:97:4a
    member pwwn 21:00:00:11:25:12:93:b6
    member fcalias SVC-N1-H1-P2
    member fcalias codibm03-os

zoneset name CoD_1 vsan 1
    member SVC-disk
    member SVC-winOS
    member SVC-win
    member SVC-linux
    member SVC-linuxOS

zoneset activate name CoD_1 vsan 1


interface mgmt0
  ip address 206.245.27.43 255.255.255.128

interface fc1/1
  switchport description SVC-N1-H1-P1
  no shutdown

interface fc1/2
  switchport description SVC-N1-H2-P1
  no shutdown

interface fc1/3
  switchport description SVC-N2-H1-P1
  no shutdown

interface fc1/4
  switchport description SVC-N2-H2-P1
  no shutdown

interface fc1/5
  switchport description DS43-CA-P1
  no shutdown

interface fc1/6
  switchport description DS43-CB-P1
  no shutdown

interface fc1/7
  switchport description DS41-CA-P1
  no shutdown

interface fc1/8
  switchport description DS41-CB-P1
  no shutdown

interface fc1/9

interface fc1/10

interface fc1/11
  no shutdown

interface fc1/12
  no shutdown

interface fc1/13
  no shutdown

interface fc1/14
  no shutdown

interface fc1/15
  no shutdown

interface fc1/16
  no shutdown

interface fc2/1
  switchport description SVC-N1-H1-P2
  no shutdown

interface fc2/2
  no shutdown

interface fc2/3
  no shutdown

interface fc2/4
  no shutdown

interface fc2/5
  switchport description SVC-N1-H2-P2
  no shutdown

interface fc2/6
  no shutdown

interface fc2/7
  no shutdown

interface fc2/8
  no shutdown

interface fc2/9
  switchport description SVC-N2-H1-P2
  no shutdown

interface fc2/10
  no shutdown

interface fc2/11
  no shutdown

interface fc2/12
  no shutdown

interface fc2/13
  switchport description SVC-N2-H2-P2
  no shutdown

interface fc2/14
  no shutdown

interface fc2/15
  no shutdown

interface fc2/16
  no shutdown

interface fc2/17
  switchport description DS43-CA-P2
  no shutdown

interface fc2/18
  no shutdown

interface fc2/19
  no shutdown

interface fc2/20

interface fc2/21
  switchport description DS43-CB-P2
  no shutdown

interface fc2/22

interface fc2/23

interface fc2/24

interface fc2/25
  switchport description DS41-CA-P2
  no shutdown

interface fc2/26

interface fc2/27

interface fc2/28

interface fc2/29
  switchport description DS41-CB-P2
  no shutdown

interface fc2/30

interface fc2/31

interface fc2/32

interface fc3/1
  no shutdown

interface fc3/2
  no shutdown

interface fc3/3
  no shutdown

interface fc3/4
  no shutdown

interface fc3/5
  no shutdown

interface fc3/6
  no shutdown

interface fc3/7
  no shutdown

interface fc3/8
  no shutdown

interface fc3/9
  no shutdown

interface fc3/10
  no shutdown

interface fc3/11
  no shutdown

interface fc3/12
  no shutdown

interface fc3/13
  no shutdown

interface fc3/14
  no shutdown

interface fc3/15
  no shutdown

interface fc3/16
  no shutdown

interface fc3/17
  no shutdown

interface fc3/18
  no shutdown

interface fc3/19
  no shutdown

interface fc3/20
  no shutdown

interface fc3/21
  no shutdown

interface fc3/22
  no shutdown

interface fc3/23
  no shutdown

interface fc3/24
  no shutdown

interface fc3/25
  no shutdown

interface fc3/26
  no shutdown

interface fc3/27
  no shutdown

interface fc3/28
  no shutdown

interface fc3/29
  no shutdown

interface fc3/30
  no shutdown

interface fc3/31
  no shutdown

interface fc3/32
  no shutdown

interface fc4/1
  no shutdown

interface fc4/2
  no shutdown

interface fc4/3
  no shutdown

interface fc4/4
  no shutdown

interface fc4/5
  no shutdown

interface fc4/6
  no shutdown

interface fc4/7
  no shutdown

interface fc4/8
  no shutdown

interface fc4/9
  no shutdown

interface fc4/10
  no shutdown

interface fc4/11
  no shutdown

interface fc4/12
  no shutdown

interface fc4/13
  no shutdown

interface fc4/14
  no shutdown

interface fc4/15
  no shutdown

interface fc4/16
  no shutdown

interface fc4/17
  no shutdown

interface fc4/18
  no shutdown

interface fc4/19
  no shutdown

interface fc4/20
  no shutdown

interface fc4/21
  no shutdown

interface fc4/22
  no shutdown

interface fc4/23
  no shutdown

interface fc4/24
  no shutdown

interface fc4/25
  no shutdown

interface fc4/26
  no shutdown

interface fc4/27
  no shutdown

interface fc4/28
  no shutdown

interface fc4/29
  no shutdown

interface fc4/30
  no shutdown

interface fc4/31
  no shutdown

interface fc4/32
  no shutdown

                        ^
% invalid command detected at '^' marker.

netcfgbak at ckcus0002-cfgbak01$


-----Original Message-----
From: john heasley [mailto:heas at shrubbery.net]
Sent: Thursday, December 15, 2005 3:55 PM
To: Hopper, Faron W.
Subject: Re: cisco 9509 fiber switch not working

Thu, Dec 15, 2005 at 04:50:02PM -0500, Hopper, Faron  W.:
>
> John,
> 	Sorry about the last post, I hit a wrong key.  Anyway, here are
> the results of the patch.  It looks to me like it failed.  Did I do
the
> patch command wrong?

nope.  i'd just pull it up in your editor, find the line and manually
cut-n-paste it.

> ckcus0002-cfgbak01# patch -p0 </root/rancid/rancid.in
> Hmm...  Looks like a unified diff to me...
> The text leading up to this was:
> --------------------------
> |RCS file: /home/rancid/.CVS/rancid/bin/rancid.in,v
> |retrieving revision 1.198
> |diff -d -u -1 -0 -r1.198 rancid.in
> |--- rancid.in  5 Dec 2005 21:13:07 -0000       1.198
> |+++ rancid.in  14 Dec 2005 23:48:31 -0000
> --------------------------
> File to patch: /usr/local/libexec/rancid/rancid
> Patching file /usr/local/libexec/rancid/rancid using Plan A...
> Hunk #1 failed at 1338.
> 1 out of 1 hunks failed--saving rejects to
> /usr/local/libexec/rancid/rancid.rej
> done
> ckcus0002-cfgbak01# cat rancid.rej
> ***************
> *** 1325,1347 ****
>       return(0);
>   }
>
>   # This routine processes a "write term"
>   sub WriteTerm {
>       print STDERR "    In WriteTerm: $_" if ($debug);
>       my($lineauto,$comment,$linecnt) = (0,0,0);
>
>       while (<INPUT>) {
>         tr/\015//d;
> -       last if(/^$prompt/);
>         return(1) if /Line has invalid autocommand /;
> -       return(1) if /(Invalid input detected|Type help or )/;
>         return(-1) if (/command authorization failed/i);
>         # the pager can not be disabled per-session on the PIX
>         if (/^(<-+ More -+>)/) {
>             my($len) = length($1);
>             s/^$1\s{$len}//;
>         }
>
>         /Non-Volatile memory is in use/  && return(-1); # NvRAM is
> locked
>         return(0) if ($found_end);              # Only do this routine
> once
>         $linecnt++;
> --- 1338,1360 ----
>       return(0);
>   }
>
>   # This routine processes a "write term"
>   sub WriteTerm {
>       print STDERR "    In WriteTerm: $_" if ($debug);
>       my($lineauto,$comment,$linecnt) = (0,0,0);
>
>       while (<INPUT>) {
>         tr/\015//d;
> +       last if (/^$prompt/);
>         return(1) if /Line has invalid autocommand /;
> +       return(1) if /(invalid input detected|type help or )/i;
>         return(-1) if (/command authorization failed/i);
>         # the pager can not be disabled per-session on the PIX
>         if (/^(<-+ More -+>)/) {
>             my($len) = length($1);
>             s/^$1\s{$len}//;
>         }
>
>         /Non-Volatile memory is in use/  && return(-1); # NvRAM is
> locked
>         return(0) if ($found_end);              # Only do this routine
> once
>         $linecnt++;
>
>
>
>
> -----Original Message-----
> From: john heasley [mailto:heas at shrubbery.net]
> Sent: Thursday, December 15, 2005 1:21 PM
> To: Hopper, Faron W.
> Subject: Re: cisco 9509 fiber switch not working
>
> Thu, Dec 15, 2005 at 02:00:10PM -0500, Hopper, Faron  W.:
> >
> > John,
> > 	When I do a find for rancid.in, I don't find it on my system.
> > What file do you want me to apply the patch to?
> >
> > find / rancid.in | grep -i rancid.in
> > /usr/local/man/man1/rancid_intro.1.gz
> > /usr/local/share/rancid/index.html
> > find: rancid.in: No such file or directory
> > ckcus0002-cfgbak01#
>
> rancid.in is dist. w/ the source and is converted to rancid in the
make
> process.  just look for rancid, prob. /usr/local/bin/rancid.
>
> >
> > Thanks,
> > Faron
> > -----Original Message-----
> > From: john heasley [mailto:heas at shrubbery.net]
> > Sent: Wednesday, December 14, 2005 5:52 PM
> > To: Hopper, Faron W.; heas at ni.shrubbery.net
> > Subject: Re: cisco 9509 fiber switch not working
> >
> > Wed, Dec 14, 2005 at 03:00:06PM -0500, Hopper, Faron  W.:
> > >
> > >
> > > I did try that, and the css as well.  I received the same results.
> >
> > think I see the problem.  try this patch; you'll probably have to
> apply
> > it by hand.
> >
> > can you tell me what version of rancid you are using?  your .raw
file
> is
> > missing some commands.
> >
> > Index: rancid.in
> > ===================================================================
> > RCS file: /home/rancid/.CVS/rancid/bin/rancid.in,v
> > retrieving revision 1.198
> > diff -d -u -1 -0 -r1.198 rancid.in
> > --- rancid.in	5 Dec 2005 21:13:07 -0000	1.198
> > +++ rancid.in	14 Dec 2005 23:48:31 -0000
> > @@ -1325,23 +1338,23 @@
> >      return(0);
> >  }
> >
> >  # This routine processes a "write term"
> >  sub WriteTerm {
> >      print STDERR "    In WriteTerm: $_" if ($debug);
> >      my($lineauto,$comment,$linecnt) = (0,0,0);
> >
> >      while (<INPUT>) {
> >  	tr/\015//d;
> > -	last if(/^$prompt/);
> > +	last if (/^$prompt/);
> >  	return(1) if /Line has invalid autocommand /;
> > -	return(1) if /(Invalid input detected|Type help or )/;
> > +	return(1) if /(invalid input detected|type help or )/i;
> >  	return(-1) if (/command authorization failed/i);
> >  	# the pager can not be disabled per-session on the PIX
> >  	if (/^(<-+ More -+>)/) {
> >  	    my($len) = length($1);
> >  	    s/^$1\s{$len}//;
> >  	}
> >
> >  	/Non-Volatile memory is in use/  && return(-1); # NvRAM is
> > locked
> >  	return(0) if ($found_end);		# Only do this routine
> > once
> >  	$linecnt++;
> >



From faron.hopper at capgemini.com  Fri Dec 16 14:58:48 2005
From: faron.hopper at capgemini.com (Hopper, Faron  W.)
Date: Fri, 16 Dec 2005 09:58:48 -0500
Subject: cisco 9509 fiber switch not working
Message-ID: <0D9EF3454D8EFC4B8BFFD2B862941681D094E9@caonmastxm03.na.capgemini.com>


Okay John that seemed to get me more information.  I hope this one
contains what you are looking for.

netcfgbak at ckcus0002-cfgbak01$
netcfgbak at ckcus0002-cfgbak01$ diff -c -20 rancid rancid.bak
*** rancid      Thu Dec 15 17:25:17 2005
--- rancid.bak  Thu Dec 15 15:38:53 2005
***************
*** 1112,1154 ****
        # newer releases (~12.1(9)) place the vlan config in the normal
        # configuration (write term).
        return(1) if ($type =~ /^(3550|4500|7600)$/);
        #return(1) if ($type !~ /^(2900XL|3500XL|6000)$/);
        return(-1) if (/command authorization failed/i);
        # the pager can not be disabled per-session on the PIX
        s/^<-+ More -+>\s*//;
        ProcessHistory("COMMENTS","keysort","IO","!VLAN: $_");
      }
      ProcessHistory("COMMENTS","keysort","IO","!\n");
      return(0);
  }

  # This routine processes a "write term"
  sub WriteTerm {
      print STDERR "    In WriteTerm: $_" if ($debug);
      my($lineauto,$comment,$linecnt) = (0,0,0);

      while (<INPUT>) {
        tr/\015//d;
!       last if (/^$prompt/);
        return(-1) if (/command authorization failed/i);
!       return(1) if /(invalid input detected|iype help or )/i;
        # the pager can not be disabled per-session on the PIX
        s/^<-+ More -+>\s*//;
        /Non-Volatile memory is in use/  && return(-1); # NvRAM is
locked
        return(0) if ($found_end);              # Only do this routine
once
        $linecnt++;
        $lineauto = 0 if (/^[^ ]/);
        # skip the crap
        if (/^(##+$|(Building|Current) configuration)/i) {
            while (<INPUT>) {
                next if (/^Current configuration\s*:/i);
                next if (/^:/);
                next if (/^([%!].*|\s*)$/);
                next if (/^ip add.*ipv4:/);     # band-aid for 3620
12.0S
                last;
            }
            if (defined($config_register)) {
                ProcessHistory("","","","!\nconfig-register
$config_register\n");
            }
            tr/\015//d;
        }
--- 1112,1154 ----
        # newer releases (~12.1(9)) place the vlan config in the normal
        # configuration (write term).
        return(1) if ($type =~ /^(3550|4500|7600)$/);
        #return(1) if ($type !~ /^(2900XL|3500XL|6000)$/);
        return(-1) if (/command authorization failed/i);
        # the pager can not be disabled per-session on the PIX
        s/^<-+ More -+>\s*//;
        ProcessHistory("COMMENTS","keysort","IO","!VLAN: $_");
      }
      ProcessHistory("COMMENTS","keysort","IO","!\n");
      return(0);
  }

  # This routine processes a "write term"
  sub WriteTerm {

      print STDERR "    In WriteTerm: $_" if ($debug);
      my($lineauto,$comment,$linecnt) = (0,0,0);

      while (<INPUT>) {
        tr/\015//d;
!       last if(/^$prompt/);
        return(-1) if (/command authorization failed/i);
!       return(1) if /(Invalid input detected|Type help or )/;
        # the pager can not be disabled per-session on the PIX
        s/^<-+ More -+>\s*//;
        /Non-Volatile memory is in use/  && return(-1); # NvRAM is
locked
        return(0) if ($found_end);              # Only do this routine
once
        $linecnt++;
        $lineauto = 0 if (/^[^ ]/);
        # skip the crap
        if (/^(##+$|(Building|Current) configuration)/i) {
            while (<INPUT>) {
                next if (/^Current configuration\s*:/i);
                next if (/^:/);
                next if (/^([%!].*|\s*)$/);
                next if (/^ip add.*ipv4:/);     # band-aid for 3620
12.0S
                last;
            }
            if (defined($config_register)) {
                ProcessHistory("","","","!\nconfig-register
$config_register\n");
            }
            tr/\015//d;
        }

Faron

-----Original Message-----
From: john heasley [mailto:heas at shrubbery.net]
Sent: Thursday, December 15, 2005 7:59 PM
To: Hopper, Faron W.
Subject: Re: cisco 9509 fiber switch not working

Thu, Dec 15, 2005 at 08:51:06PM -0500, Hopper, Faron  W.:
>
> John,
> 	Here is the diff -20.

your diff stinks.  -20 is supposed to add context on either side of the
change(s).  try diff -c -20

> netcfgbak at ckcus0002-cfgbak01$ diff -20 rancid rancid.bak
> 1132c1132
> <       last if (/^$prompt/);
> ---
> >       last if(/^$prompt/);
> 1134c1134
> <       return(1) if /(invalid input detected|iype help or )/i;
> ---
> >       return(1) if /(Invalid input detected|Type help or )/;
> netcfgbak at ckcus0002-cfgbak01$
>
>
>
> Thanks,
> Faron
>
> -----Original Message-----
> From: john heasley [mailto:heas at shrubbery.net]
> Sent: Thursday, December 15, 2005 6:29 PM
> To: Hopper, Faron W.
> Subject: Re: cisco 9509 fiber switch not working
>
> Thu, Dec 15, 2005 at 06:39:25PM -0500, Hopper, Faron  W.:
> >
> > John,
> >     I change the lines by hand.  I edited the lines that had a -
> symbol
> > beside them and change them to what the line looked like with the +
> > symbol.  Here is the diff
> >
> > ckcus0002-cfgbak01# diff rancid rancid.bak
> > 1132c1132
> > <       last if (/^$prompt/);
> > ---
> > >       last if(/^$prompt/);
> > 1134c1134
> > <       return(1) if /(invalid input detected|iype help or )/i;
> > ---
> > >       return(1) if /(Invalid input detected|Type help or )/;
> >
> > If I did that right, then I ran the rancid -d cod-cisco-9509-1
command
> > and received the same results (listed below).  Thanks, Faron
>
> that looks right, but please send a diff to me with the option -20



From patrick.topping at hypermediasystems.com  Tue Dec 20 01:06:28 2005
From: patrick.topping at hypermediasystems.com (Patrick Topping)
Date: Mon, 19 Dec 2005 17:06:28 -0800
Subject: Foundry Serviron load balancers
Message-ID: <1135040788.3392.13.camel@turtle>

I just installed RANCID for the very first time a week ago.  It is
working great so far except for my Foundry ServerIron load balancers.
RANCID is reporting changes in them every hour when it runs.  It reports
changes in them even when there has not been a change.  Has any one seen
anything similar to this with Foundry load balancers?  Any one have any
idea where I should start looking for this issue?  Any help would be
greatly appreciated.  Thanks in advance.

-Patrick

From justin at grote.name  Tue Dec 20 01:24:08 2005
From: justin at grote.name (Justin Grote)
Date: Mon, 19 Dec 2005 18:24:08 -0700
Subject: Foundry Serviron load balancers
In-Reply-To: <1135040788.3392.13.camel@turtle>
References: <1135040788.3392.13.camel@turtle>
Message-ID: <43A75D38.3040300@grote.name>

Patrick Topping wrote:

> I just installed RANCID for the very first time a week ago.  It is 
> working great so far except for my Foundry ServerIron load balancers.  
> RANCID is reporting changes in them every hour when it runs.  It 
> reports changes in them even when there has not been a change.  Has 
> any one seen anything similar to this with Foundry load balancers?  
> Any one have any idea where I should start looking for this issue?  
> Any help would be greatly appreciated.  Thanks in advance.

Is it reporting the *exact* same diffs every time? If so, your CVS or 
Subversion is likely messed up somehow and is uncommitable, which is 
what is causing RANCID to do that.


-- 
Justin Grote
Network Architect
JWG Networks



From patrick.topping at hypermediasystems.com  Tue Dec 20 22:18:04 2005
From: patrick.topping at hypermediasystems.com (Patrick Topping)
Date: Tue, 20 Dec 2005 14:18:04 -0800
Subject: Foundry Serviron load balancers
In-Reply-To: <43A75D38.3040300@grote.name>
References: <1135040788.3392.13.camel@turtle>  <43A75D38.3040300@grote.name>
Message-ID: <1135117084.3326.21.camel@turtle>

Justin,

Below is a snapshot of what was seen at 6:00 and then again at 7:00 a.m.
The diffs are identical.  What is the best way to clean this up?  Any
ideas?  Thanks.

-Patrick

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

6:00 a.m.

Index: configs/lax06fsi450-001.dtiserv2.com
===================================================================
retrieving revision 1.482
diff -U4 -r1.482 lax06fsi450-001.dtiserv2.com
@@ -693,8 +693,10 @@
   port http keepalive
   port http url "HEAD / HTTP/1.1\nHost: web055-dsr.ecp.dtiserv2.com"
  !
  server real web056.ecp 204.1.155.140
+ server real web056.ecp 204.1.155.140
+ server real web056.ecp 204.1.155.140
   port http
   port http keepalive
   port http url "HEAD / HTTP/1.1\nHost: web056-dsr.ecp.dtiserv2.com"
  !
@@ -748,10 +750,8 @@
   port http no-http-downgrade
   bind http web212.dl http web213.dl http web211.dl http
  !
  server virtual dl04.1pondo.tv 38.118.199.88
- server virtual dl04.1pondo.tv 38.118.199.88
- server virtual dl04.1pondo.tv 38.118.199.88
   sym-priority 110
   port http
   port http dsr
   port http no-http-downgrade
@@ -937,17 +937,17 @@
   port ssl dsr
   bind http koisuru http
   bind ssl koisuru ssl

7:00 a.m.

Index: configs/lax06fsi450-001.dtiserv2.com
===================================================================
retrieving revision 1.483
diff -U4 -r1.483 lax06fsi450-001.dtiserv2.com
@@ -693,10 +693,8 @@
   port http keepalive
   port http url "HEAD / HTTP/1.1\nHost: web055-dsr.ecp.dtiserv2.com"
  !
  server real web056.ecp 204.1.155.140
- server real web056.ecp 204.1.155.140
- server real web056.ecp 204.1.155.140
   port http
   port http keepalive
   port http url "HEAD / HTTP/1.1\nHost: web056-dsr.ecp.dtiserv2.com"
  !
@@ -750,8 +748,10 @@
   port http no-http-downgrade
   bind http web212.dl http web213.dl http web211.dl http
  !
  server virtual dl04.1pondo.tv 38.118.199.88
+ server virtual dl04.1pondo.tv 38.118.199.88
+ server virtual dl04.1pondo.tv 38.118.199.88
   sym-priority 110
   port http
   port http dsr
   port http no-http-downgrade
@@ -880,8 +880,10 @@
  server virtual blog.dtiblog.com 204.1.155.22
   sym-priority 120
   port http
   port http dsr
+  port http dsr
+  port http dsr
   port http no-http-downgrade
   port ssl sticky
   port ssl dsr
   bind http blog003.aff http
@@ -937,10 +939,8 @@
   port ssl dsr
   bind http koisuru http
   bind ssl koisuru ssl

On Mon, 2005-12-19 at 18:24 -0700, Justin Grote wrote:

> Patrick Topping wrote:
> 
> > I just installed RANCID for the very first time a week ago.  It is 
> > working great so far except for my Foundry ServerIron load balancers.  
> > RANCID is reporting changes in them every hour when it runs.  It 
> > reports changes in them even when there has not been a change.  Has 
> > any one seen anything similar to this with Foundry load balancers?  
> > Any one have any idea where I should start looking for this issue?  
> > Any help would be greatly appreciated.  Thanks in advance.
> 
> Is it reporting the *exact* same diffs every time? If so, your CVS or 
> Subversion is likely messed up somehow and is uncommitable, which is 
> what is causing RANCID to do that.
> 
> 

From justin at grote.name  Tue Dec 20 22:21:53 2005
From: justin at grote.name (Justin Grote)
Date: Tue, 20 Dec 2005 15:21:53 -0700
Subject: Foundry Serviron load balancers
In-Reply-To: <1135117084.3326.21.camel@turtle>
References: <1135040788.3392.13.camel@turtle>  <43A75D38.3040300@grote.name> <1135117084.3326.21.camel@turtle>
Message-ID: <43A88401.4000808@grote.name>

Patrick Topping wrote:

> Justin,
>
> Below is a snapshot of what was seen at 6:00 and then again at 7:00 
> a.m.  The diffs are identical.  What is the best way to clean this 
> up?  Any ideas?  Thanks.

 From the FAQ (http://www.shrubbery.net/rancid/FAQ)

Q. I keep receiving the same diff for a (or set of) devices, but I know the
   data is not changing repeatedly.  Why?
A. This is probably a CVS or filesystem permissions problem.  Check the log
   file from the last run for that group for clues first; it may provide the
   exact cause.

   Note: It is very important the following be done as the user who normally
         runs the rancid collection from cron.

   Check the cvs status of the device's file.  example:

   guelah [2704] cvs status rtr.shrubbery.net
   ===================================================================
   File: yogi.shrubbery.net        Status: Up-to-date

      Working revision:    1.197   Tue Jul 10 15:41:16 2001
      Repository revision: 1.197   /user/local/rancid/CVS/shrubbery/configs/rtr.shrubbery.net,v
      Sticky Tag:          (none)
      Sticky Date:         (none)
      Sticky Options:      (none)

   The Status: should be Up-to-date.  If the status is "Unknown", then somehow
   the file has been created without being cvs add'ed.  This should be
   corrected by removing that device's entry from the group's router.db file,
   run do-diffs, replace the entry in router.db, and run do-diffs again.

   If the Status is anything else, someone has most likely been touching the
   files manually.  Sane state can be achieved by removing the file and running
   cvs update <file> to get a fresh copy from the repository.

   Check the ownership and permissions of the file and directory and the
   directory and file in the cvs repository (/usr/local/rancid/CVS/).  They
   should be owned by the user who runs do-diffs from cron.  At the very least,
   the directory and files should be writable by the rancid user.  Group and
   world permissions will determined by the umask (default 027), which is set
   in /usr/local/rancid/bin/env.  Likely the easiest way to fix the ownership
   on the cvs repository is chown -R <rancid user> /usr/local/rancid/CVS



-- 
Justin Grote
Network Architect
JWG Networks



From rmordasiewicz at samuelmanutech.com  Wed Dec 21 22:57:13 2005
From: rmordasiewicz at samuelmanutech.com (Robin Mordasiewicz)
Date: Wed, 21 Dec 2005 17:57:13 -0500 (EST)
Subject: using subversion instead of cvs
Message-ID: <Pine.LNX.4.64.0512211756260.14752@smtcorms02.samuelmanutech.com>

Is it possible to use subversion instead of cvs ?




From justin at grote.name  Wed Dec 21 23:15:45 2005
From: justin at grote.name (Justin Grote)
Date: Wed, 21 Dec 2005 16:15:45 -0700
Subject: using subversion instead of cvs
In-Reply-To: <Pine.LNX.4.64.0512211756260.14752@smtcorms02.samuelmanutech.com>
References: <Pine.LNX.4.64.0512211756260.14752@smtcorms02.samuelmanutech.com>
Message-ID: <43A9E221.30707@grote.name>

Robin Mordasiewicz wrote:

> Is it possible to use subversion instead of cvs ?

Yep. I wrote a patch that was incorporated into RANCID. Get 2.3.2a, and 
use the --enable-svn flag when compiling, i.e.

./configure --enable-svn

you can also compile it normally, and then change the RCSYS variable in 
rancid.conf from cvs to svn. DO NOT MAKE THIS CHANGE IF YUOU HAVE AN 
EXISTING CVS REPOSITORY without running cvs2svn first though.

-- 
Justin Grote
Network Architect
JWG Networks



From rmordasiewicz at samuelmanutech.com  Wed Dec 21 23:25:48 2005
From: rmordasiewicz at samuelmanutech.com (Robin Mordasiewicz)
Date: Wed, 21 Dec 2005 18:25:48 -0500 (EST)
Subject: using subversion instead of cvs
In-Reply-To: <43A9E221.30707@grote.name>
References: <Pine.LNX.4.64.0512211756260.14752@smtcorms02.samuelmanutech.com>
 <43A9E221.30707@grote.name>
Message-ID: <Pine.LNX.4.64.0512211824570.14752@smtcorms02.samuelmanutech.com>

On Wed, 21 Dec 2005, Justin Grote wrote:

> Robin Mordasiewicz wrote:
>
>> Is it possible to use subversion instead of cvs ?
>
> Yep. I wrote a patch that was incorporated into RANCID. Get 2.3.2a, and use 
> the --enable-svn flag when compiling, i.e.
>
> ./configure --enable-svn
>
> you can also compile it normally, and then change the RCSYS variable in 
> rancid.conf from cvs to svn. DO NOT MAKE THIS CHANGE IF YUOU HAVE AN EXISTING 
> CVS REPOSITORY without running cvs2svn first though.


excellent. Thanks alot.
Now I need to figure out how to integrate this into trac.


From rmordasiewicz at samuelmanutech.com  Thu Dec 22 00:34:29 2005
From: rmordasiewicz at samuelmanutech.com (Robin Mordasiewicz)
Date: Wed, 21 Dec 2005 19:34:29 -0500 (EST)
Subject: using subversion instead of cvs
In-Reply-To: <Pine.LNX.4.64.0512211824570.14752@smtcorms02.samuelmanutech.com>
References: <Pine.LNX.4.64.0512211756260.14752@smtcorms02.samuelmanutech.com>
 <43A9E221.30707@grote.name> <Pine.LNX.4.64.0512211824570.14752@smtcorms02.samuelmanutech.com>
Message-ID: <Pine.LNX.4.64.0512211932230.14752@smtcorms02.samuelmanutech.com>

On Wed, 21 Dec 2005, Robin Mordasiewicz wrote:

> On Wed, 21 Dec 2005, Justin Grote wrote:
>
>> Robin Mordasiewicz wrote:
>> 
>>> Is it possible to use subversion instead of cvs ?
>> 
>> Yep. I wrote a patch that was incorporated into RANCID. Get 2.3.2a, and use 
>> the --enable-svn flag when compiling, i.e.
>> 
>> ./configure --enable-svn
>> 
>> you can also compile it normally, and then change the RCSYS variable in 
>> rancid.conf from cvs to svn. DO NOT MAKE THIS CHANGE IF YUOU HAVE AN 
>> EXISTING CVS REPOSITORY without running cvs2svn first though.
>
> excellent. Thanks alot.
> Now I need to figure out how to integrate this into trac.

ok everything is working, except my repository seems to have a structure 
of

root/root/configs

       ^
       |

Is there any way to tell rancid to import to a specifc directory name ???

forgive me I am a cvs noob.


From rmordasiewicz at samuelmanutech.com  Thu Dec 22 18:29:26 2005
From: rmordasiewicz at samuelmanutech.com (Robin Mordasiewicz)
Date: Thu, 22 Dec 2005 13:29:26 -0500 (EST)
Subject: filename options
Message-ID: <Pine.LNX.4.64.0512221321080.14752@smtcorms02.samuelmanutech.com>

Is it possible that my filenames are configurable ?

I have ip addresses, but no DNS, and so my filenames are all by ip 
address. I would like to see the filenames slightly more descriptive.






From helmwork at ruraltel.net  Thu Dec 22 19:17:29 2005
From: helmwork at ruraltel.net (Eric Helm)
Date: Thu, 22 Dec 2005 13:17:29 -0600
Subject: filename options
In-Reply-To: <Pine.LNX.4.64.0512221321080.14752@smtcorms02.samuelmanutech.com>
References: <Pine.LNX.4.64.0512221321080.14752@smtcorms02.samuelmanutech.com>
Message-ID: <43AAFBC9.10200@ruraltel.net>



Robin Mordasiewicz wrote:
> Is it possible that my filenames are configurable ?
> 
> I have ip addresses, but no DNS, and so my filenames are all by ip
> address. I would like to see the filenames slightly more descriptive.
> 
Robin,
I just use the hosts file on the RANCID server in this situation.
I'm not aware of any better way to do it.

/Eric


From asp at partan.com  Thu Dec 22 19:34:04 2005
From: asp at partan.com (Andrew Partan)
Date: Thu, 22 Dec 2005 14:34:04 -0500
Subject: filename options
In-Reply-To: <Pine.LNX.4.64.0512221321080.14752@smtcorms02.samuelmanutech.com>
References: <Pine.LNX.4.64.0512221321080.14752@smtcorms02.samuelmanutech.com>
Message-ID: <20051222193404.GA58428@partan.com>

On Thu, Dec 22, 2005 at 01:29:26PM -0500, Robin Mordasiewicz wrote:
> Is it possible that my filenames are configurable ?
> 
> I have ip addresses, but no DNS, and so my filenames are all by ip 
> address. I would like to see the filenames slightly more descriptive.

So long as you can telnet or ssh to the name, you can use whatever you want.
I'd put them into the DNS, or /etc/hosts.
	--asp


From wcgallar at iupui.edu  Wed Dec 28 16:54:59 2005
From: wcgallar at iupui.edu (Chris Gallardo)
Date: Wed, 28 Dec 2005 11:54:59 -0500 (EST)
Subject: HP 4100 switch not being collected
In-Reply-To: <e05f39290512280331y184319f4j23a4a9b3e4f8736e@mail.gmail.com>
References: <e05f39290512280331y184319f4j23a4a9b3e4f8736e@mail.gmail.com>
Message-ID: <Pine.LNX.4.62.0512281150480.14736@brutus.noc.iu.edu>

I'm using rancid to collect the configs of hp 4100 on the Indinaa
univeristy campus.  Most of the configs are being collected except a few
and I have used hlogin as well as hrancid -dl to test as to why these
switches are not being collected both came up fine and i was able to
generate a .new file when using hrancid.  I do get this error though


10.166.195.1: End of run not found
10.166.195.1: End of run not found
/usr/bin/tail: `-1' option is obsolete; use `-n 1' since this will be
removed in the future


which doesn't come up when i use hrancid -dl on a switch that is being
collected correctly.


--

Chris Gallardo
Network Services
278-9067



From karim.adel at gmail.com  Wed Dec 28 11:31:13 2005
From: karim.adel at gmail.com (Kim Onnel)
Date: Wed, 28 Dec 2005 13:31:13 +0200
Subject: Rancid crashing routers/remove commands
Message-ID: <e05f39290512280331y184319f4j23a4a9b3e4f8736e@mail.gmail.com>

Hello,

 We're using RANCID,  its a great tool,.


I wonder if people has reported that it crashs routers sometimes ?


I also would like to reduce the number of the commands it issues, how is
that possible ?


Regards



From rspeed at gmail.com  Thu Dec 29 01:34:30 2005
From: rspeed at gmail.com (Ryan Speed)
Date: Wed, 28 Dec 2005 17:34:30 -0800
Subject: expect (alternatives?) on embedded linux machine
Message-ID: <a6e20ec60512281734u3cf951a3w61665dfc625cb3e2@mail.gmail.com>

I realize this might fall into the off topic category but I'm
wondering if anyone's had any luck compiling expect on nslu2
(http://www.nslu2-linux.org/) box, any mention I found in the expect
archives leads nowhere.  Alternative to this would be to try a python
implementation of expect, has anyone gone down this road to get rancid
running on one of these boxes or something similar?

see below for the roadblock, im not a coder so it's got me scratching my head.

thanks in advance,
ryan

configuring Expect 5.43.0
checking for autoconf... yes
checking configure up to date... yes
checking host system type... Invalid configuration
`armv5b-unknown-linux-gnu': machine `armv5b-unknown' not recognized

checking target system type... Invalid configuration
`armv5b-unknown-linux-gnu': machine `armv5b-unknown' not recognized

checking build system type... Invalid configuration
`armv5b-unknown-linux-gnu': machine `armv5b-unknown' not recognized

checking shell to use within Make...
checking for gcc... gcc
checking whether the C compiler (gcc  ) works... yes
checking whether the C compiler (gcc  ) is a cross-compiler... no
checking whether we are using GNU C... yes
checking whether gcc accepts -g... yes
checking for building with threads... no (default)
checking for Tcl configuration... configure: warning: Can't find Tcl
configuration definitions .: #: not found
checking Tcl build library...
checking for Tcl_CreateCommand... no
checking if Tcl library build specification is valid... no
checking for Tk configuration... configure: warning: Can't find Tk
configuration definitions
checking for Tk_Init... no
checking if Tk library build specification is valid... no
checking whether the compiler () actually works... configure: error:
the native compiler is broken and won't compile.


From babydr at baby-dragons.com  Thu Dec 29 02:45:51 2005
From: babydr at baby-dragons.com (Mr. James W. Laferriere)
Date: Wed, 28 Dec 2005 19:45:51 -0700 (MST)
Subject: expect (alternatives?) on embedded linux machine
In-Reply-To: <a6e20ec60512281734u3cf951a3w61665dfc625cb3e2@mail.gmail.com>
References: <a6e20ec60512281734u3cf951a3w61665dfc625cb3e2@mail.gmail.com>
Message-ID: <Pine.LNX.4.64.0512281944130.20945@filesrv1.baby-dragons.com>

 	Hello Ryan ,  There is a mini expect called 'Jim' .  I have no idea if
 	it will drive rancid properly or not .  I only mentioning that it
 	exists .  Hth ,  JimL

On Wed, 28 Dec 2005, Ryan Speed wrote:
> I realize this might fall into the off topic category but I'm
> wondering if anyone's had any luck compiling expect on nslu2
> (http://www.nslu2-linux.org/) box, any mention I found in the expect
> archives leads nowhere.  Alternative to this would be to try a python
> implementation of expect, has anyone gone down this road to get rancid
> running on one of these boxes or something similar?
>
> see below for the roadblock, im not a coder so it's got me scratching my head.
>
> thanks in advance,
> ryan
>
> configuring Expect 5.43.0
> checking for autoconf... yes
> checking configure up to date... yes
> checking host system type... Invalid configuration
> `armv5b-unknown-linux-gnu': machine `armv5b-unknown' not recognized
>
> checking target system type... Invalid configuration
> `armv5b-unknown-linux-gnu': machine `armv5b-unknown' not recognized
>
> checking build system type... Invalid configuration
> `armv5b-unknown-linux-gnu': machine `armv5b-unknown' not recognized
>
> checking shell to use within Make...
> checking for gcc... gcc
> checking whether the C compiler (gcc  ) works... yes
> checking whether the C compiler (gcc  ) is a cross-compiler... no
> checking whether we are using GNU C... yes
> checking whether gcc accepts -g... yes
> checking for building with threads... no (default)
> checking for Tcl configuration... configure: warning: Can't find Tcl
> configuration definitions .: #: not found
> checking Tcl build library...
> checking for Tcl_CreateCommand... no
> checking if Tcl library build specification is valid... no
> checking for Tk configuration... configure: warning: Can't find Tk
> configuration definitions
> checking for Tk_Init... no
> checking if Tk library build specification is valid... no
> checking whether the compiler () actually works... configure: error:
> the native compiler is broken and won't compile.
>

-- 
+------------------------------------------------------------------+
| James   W.   Laferriere | System    Techniques | Give me VMS     |
| Network        Engineer | 3542 Broken Yoke Dr. |  Give me Linux  |
| babydr at baby-dragons.com | Billings , MT. 59105 |   only  on  AXP |
+------------------------------------------------------------------+


From heas at shrubbery.net  Thu Dec 29 04:11:00 2005
From: heas at shrubbery.net (john heasley)
Date: Wed, 28 Dec 2005 20:11:00 -0800
Subject: expect (alternatives?) on embedded linux machine
In-Reply-To: <a6e20ec60512281734u3cf951a3w61665dfc625cb3e2@mail.gmail.com>
References: <a6e20ec60512281734u3cf951a3w61665dfc625cb3e2@mail.gmail.com>
Message-ID: <20051229041100.GA23170@shrubbery.net>

Wed, Dec 28, 2005 at 05:34:30PM -0800, Ryan Speed:
> I realize this might fall into the off topic category but I'm
> wondering if anyone's had any luck compiling expect on nslu2
> (http://www.nslu2-linux.org/) box, any mention I found in the expect
> archives leads nowhere.  Alternative to this would be to try a python
> implementation of expect, has anyone gone down this road to get rancid
> running on one of these boxes or something similar?
> 
> see below for the roadblock, im not a coder so it's got me scratching my head.
> 
> thanks in advance,
> ryan
> 
> configuring Expect 5.43.0
> checking for autoconf... yes
> checking configure up to date... yes
> checking host system type... Invalid configuration
> `armv5b-unknown-linux-gnu': machine `armv5b-unknown' not recognized

presumably the autoconf script just doesn't know about this platofrm.  grep
it for armv5b.  presumably this is actually just like any other arm based
linux distro; so just figure out which arm<whatever> it does support and
whack it w/ --host & --target



From heas at shrubbery.net  Thu Dec 29 04:17:58 2005
From: heas at shrubbery.net (john heasley)
Date: Wed, 28 Dec 2005 20:17:58 -0800
Subject: HP 4100 switch not being collected
In-Reply-To: <Pine.LNX.4.62.0512281150480.14736@brutus.noc.iu.edu>
References: <e05f39290512280331y184319f4j23a4a9b3e4f8736e@mail.gmail.com> <Pine.LNX.4.62.0512281150480.14736@brutus.noc.iu.edu>
Message-ID: <20051229041758.GB23170@shrubbery.net>

Wed, Dec 28, 2005 at 11:54:59AM -0500, Chris Gallardo:
> I'm using rancid to collect the configs of hp 4100 on the Indinaa
> univeristy campus.  Most of the configs are being collected except a few
> and I have used hlogin as well as hrancid -dl to test as to why these
> switches are not being collected both came up fine and i was able to
> generate a .new file when using hrancid.  I do get this error though
> 
> 
> 10.166.195.1: End of run not found
> 10.166.195.1: End of run not found

the scripts try to make sure that the config was actually collected, vs.
an empty config that happens when devices can't produce a config.

so its either truncating the config or it produces a config whose ending
is different from what the script expects.

> /usr/bin/tail: `-1' option is obsolete; use `-n 1' since this will be
> removed in the future

lovely.  which craptacular linux distro is this?

> 
> which doesn't come up when i use hrancid -dl on a switch that is being
> collected correctly.
> 
> 
> --
> 
> Chris Gallardo
> Network Services
> 278-9067


From heas at shrubbery.net  Thu Dec 29 04:18:56 2005
From: heas at shrubbery.net (john heasley)
Date: Wed, 28 Dec 2005 20:18:56 -0800
Subject: Rancid crashing routers/remove commands
In-Reply-To: <e05f39290512280331y184319f4j23a4a9b3e4f8736e@mail.gmail.com>
References: <e05f39290512280331y184319f4j23a4a9b3e4f8736e@mail.gmail.com>
Message-ID: <20051229041856.GC23170@shrubbery.net>

Wed, Dec 28, 2005 at 01:31:13PM +0200, Kim Onnel:
> Hello,
> 
>  We're using RANCID,  its a great tool,.
> 
> 
> I wonder if people has reported that it crashs routers sometimes ?

if using the UI crashes the router, i suggest that you find another
router vendor.


From karim.adel at gmail.com  Thu Dec 29 07:48:01 2005
From: karim.adel at gmail.com (Kim Onnel)
Date: Thu, 29 Dec 2005 09:48:01 +0200
Subject: Rancid crashing routers/remove commands
In-Reply-To: <20051229041856.GC23170@shrubbery.net>
References: <e05f39290512280331y184319f4j23a4a9b3e4f8736e@mail.gmail.com>
	 <20051229041856.GC23170@shrubbery.net>
Message-ID: <e05f39290512282348q3851a136ka6cd2e8b09fbfc24@mail.gmail.com>

I mean could it be that because of term length 0 and than alot of commands
will for example increase the VTY proecss and causes router crash

On 12/29/05, john heasley <heas at shrubbery.net> wrote:
>
> Wed, Dec 28, 2005 at 01:31:13PM +0200, Kim Onnel:
> > Hello,
> >
> >  We're using RANCID,  its a great tool,.
> >
> >
> > I wonder if people has reported that it crashs routers sometimes ?
>
> if using the UI crashes the router, i suggest that you find another
> router vendor.
>



From asp at partan.com  Thu Dec 29 20:30:16 2005
From: asp at partan.com (Andrew Partan)
Date: Thu, 29 Dec 2005 15:30:16 -0500
Subject: Rancid crashing routers/remove commands
In-Reply-To: <e05f39290512282348q3851a136ka6cd2e8b09fbfc24@mail.gmail.com>
References: <e05f39290512280331y184319f4j23a4a9b3e4f8736e@mail.gmail.com> <20051229041856.GC23170@shrubbery.net> <e05f39290512282348q3851a136ka6cd2e8b09fbfc24@mail.gmail.com>
Message-ID: <20051229203016.GC53946@partan.com>

On Thu, Dec 29, 2005 at 09:48:01AM +0200, Kim Onnel wrote:
> I mean could it be that because of term length 0 and than alot of commands
> will for example increase the VTY proecss and causes router crash

The only time I've ever seen rancid crash a router is when the
router was having serious s/w problems & running some command (by
rancid or anyone) was enough to trigger the bug.

If you are having router crashes, the problem is with the router,
not with rancid.  All rancid does is run commands like any ordinary
user.  And if an ordinary user can crash the router, you hare having
problems with the router.

I would suspect 'term len 30' to cause a router more problems than
'term len 0' as the router has to buffer or stall the output of the
commands.
	--asp


From tex at off.org  Thu Dec 29 20:38:28 2005
From: tex at off.org (Austin Schutz)
Date: Thu, 29 Dec 2005 12:38:28 -0800
Subject: Rancid crashing routers/remove commands
In-Reply-To: <20051229203016.GC53946@partan.com>
References: <e05f39290512280331y184319f4j23a4a9b3e4f8736e@mail.gmail.com> <20051229041856.GC23170@shrubbery.net> <e05f39290512282348q3851a136ka6cd2e8b09fbfc24@mail.gmail.com> <20051229203016.GC53946@partan.com>
Message-ID: <20051229203827.GB9941@gblx.net>

On Thu, Dec 29, 2005 at 03:30:16PM -0500, Andrew Partan wrote:
> On Thu, Dec 29, 2005 at 09:48:01AM +0200, Kim Onnel wrote:
> > I mean could it be that because of term length 0 and than alot of commands
> > will for example increase the VTY proecss and causes router crash
> 
> The only time I've ever seen rancid crash a router is when the
> router was having serious s/w problems & running some command (by
> rancid or anyone) was enough to trigger the bug.
> 
> If you are having router crashes, the problem is with the router,
> not with rancid.  All rancid does is run commands like any ordinary
> user.  And if an ordinary user can crash the router, you hare having
> problems with the router.
> 
> I would suspect 'term len 30' to cause a router more problems than
> 'term len 0' as the router has to buffer or stall the output of the
> commands.

	We've had problems here which the vendor "suspects" is due to
rancid rapid firing off commands during polling. I've done some ugly hack
work here to have rancid skip some commands for given platforms depending
on environment variable settings.
	What might be slightly less ugly would be to have an option to clogin
to set a delay between execution of commands. That might give the garbage
collection (referring to mem mgmt, not the overall OS here) a chance to
catch up between commands.

	Austin


From asp at partan.com  Thu Dec 29 20:48:36 2005
From: asp at partan.com (Andrew Partan)
Date: Thu, 29 Dec 2005 15:48:36 -0500
Subject: Rancid crashing routers/remove commands
In-Reply-To: <20051229203827.GB9941@gblx.net>
References: <e05f39290512280331y184319f4j23a4a9b3e4f8736e@mail.gmail.com> <20051229041856.GC23170@shrubbery.net> <e05f39290512282348q3851a136ka6cd2e8b09fbfc24@mail.gmail.com> <20051229203016.GC53946@partan.com> <20051229203827.GB9941@gblx.net>
Message-ID: <20051229204835.GE53946@partan.com>

On Thu, Dec 29, 2005 at 12:38:28PM -0800, Austin Schutz wrote:
> 	We've had problems here which the vendor "suspects" is due to
> rancid rapid firing off commands during polling.

What vendor is feeding you that line of bull?

Say you are trying to do some debugging & want to catch the output
of some command as often as possible; is the vendor telling you
that you should not be doing this?  Bogus...

> 	What might be slightly less ugly would be to have an option to clogin
> to set a delay between execution of commands.

There is a for loop in run_commands; that would be the place to put
a sleep.
	--asp


From faron.hopper at capgemini.com  Thu Dec 29 21:01:33 2005
From: faron.hopper at capgemini.com (Hopper, Faron  W.)
Date: Thu, 29 Dec 2005 16:01:33 -0500
Subject: Rancid crashing routers/remove commands
Message-ID: <0D9EF3454D8EFC4B8BFFD2B862941681D407E1@caonmastxm03.na.capgemini.com>


Just my .02, any vendor who sells a product that cannot keep up with a
telnet session should be re-evaluated and phased out.  I have been using
rancid for 6 months to a year on all types of equipment and have not had
any problems.

Faron

-----Original Message-----
From: owner-rancid-discuss at shrubbery.net
[mailto:owner-rancid-discuss at shrubbery.net] On Behalf Of Andrew Partan
Sent: Thursday, December 29, 2005 2:49 PM
To: Austin Schutz
Cc: rancid-discuss at shrubbery.net
Subject: Re: Rancid crashing routers/remove commands

On Thu, Dec 29, 2005 at 12:38:28PM -0800, Austin Schutz wrote:
> 	We've had problems here which the vendor "suspects" is due to
> rancid rapid firing off commands during polling.

What vendor is feeding you that line of bull?

Say you are trying to do some debugging & want to catch the output
of some command as often as possible; is the vendor telling you
that you should not be doing this?  Bogus...

> 	What might be slightly less ugly would be to have an option to
clogin
> to set a delay between execution of commands.

There is a for loop in run_commands; that would be the place to put
a sleep.
	--asp




From tex at off.org  Fri Dec 30 09:26:55 2005
From: tex at off.org (Austin Schutz)
Date: Fri, 30 Dec 2005 01:26:55 -0800
Subject: Rancid crashing routers/remove commands
In-Reply-To: <20051229204835.GE53946@partan.com>
References: <e05f39290512280331y184319f4j23a4a9b3e4f8736e@mail.gmail.com> <20051229041856.GC23170@shrubbery.net> <e05f39290512282348q3851a136ka6cd2e8b09fbfc24@mail.gmail.com> <20051229203016.GC53946@partan.com> <20051229203827.GB9941@gblx.net> <20051229204835.GE53946@partan.com>
Message-ID: <20051230092655.GD9941@gblx.net>

On Thu, Dec 29, 2005 at 03:48:36PM -0500, Andrew Partan wrote:
> On Thu, Dec 29, 2005 at 12:38:28PM -0800, Austin Schutz wrote:
> > 	We've had problems here which the vendor "suspects" is due to
> > rancid rapid firing off commands during polling.
> 
> What vendor is feeding you that line of bull?
> 

	Well the bull is second hand from one of our engineers, so I'll skip
the public flogging for now.
	It sounds pretty far fetched to me as well, but I'm not part of the
team responsible for maintaining these albatrosses - excepting the rancid
polling. It's far easier in my case to just add the kludge rather than try to
prove the polling isn't causing side effects.

	Austin


From Roderick.Greening at bell.ca  Fri Dec 30 13:32:46 2005
From: Roderick.Greening at bell.ca (Roderick B. Greening)
Date: Fri, 30 Dec 2005 05:32:46 -0800
Subject: Rancid crashing routers/remove commands
Message-ID: <BD7CBE5FC8A9B5428F74E78191E453FE02888690@storexmb04.gt.ca>

If it's a Cisco router (like a Cat 5500 RSM) it's possible that the router
could be crashing upon multiple executions of "sh running" and "write term".


There is a memory issue in certain IOS's that when examining the running
memory config causes a memory leak.

I have personally watched this happen via a SNMP poll to my RSM. The memory
will leak over a few hours or sometimes days, and then start having
problems. This is a bug with the Cisco IOS. I would expect that same with
whatever hardware/software you are using. It's not really a RANCID problem
as such.

However, one possible work around would be to not have RANCID execute a "sh
running" or "write term", and instead use "sh start" or "sh config". The
only issue doing this is that you do not capture any changes if they haven't
been written to memory (via "write memory" or "copy running start"). Of
course, you could write a rule/patch to detect the RSM, and if it is issue a
"write mem" first and then do a "sh config". This gets around the memory
leak issue. Although, now this forces the change to be committed to memory,
and perhaps it shouldn't, at the time RANCID is polling.

Anyway, some food for thought.

-----Original Message-----
From: owner-rancid-discuss at shrubbery.net
[mailto:owner-rancid-discuss at shrubbery.net] On Behalf Of Austin Schutz
Sent: Friday, December 30, 2005 5:57 AM
To: Andrew Partan
Cc: Austin Schutz; rancid-discuss at shrubbery.net
Subject: Re: Rancid crashing routers/remove commands

On Thu, Dec 29, 2005 at 03:48:36PM -0500, Andrew Partan wrote:
> On Thu, Dec 29, 2005 at 12:38:28PM -0800, Austin Schutz wrote:
> > 	We've had problems here which the vendor "suspects" is due to
> > rancid rapid firing off commands during polling.
> 
> What vendor is feeding you that line of bull?
> 

	Well the bull is second hand from one of our engineers, so I'll skip
the public flogging for now.
	It sounds pretty far fetched to me as well, but I'm not part of the
team responsible for maintaining these albatrosses - excepting the rancid
polling. It's far easier in my case to just add the kludge rather than try
to
prove the polling isn't causing side effects.

	Austin