Mailing List Archive: Problem with Cisco 4000 with CatOS 7.6

Problem with Cisco 4000 with CatOS 7.6

Sep 7, 2004, 10:34 PM

Post #1 of 3 (689 views)

Hi,

I have a Cisco 4000 which I recently upgraded to CatOS 7.6. after the
upgrade rancid stopped
working. The problem seems to be that it misses the "write term" command.

bash-2.05a$ cat5rancid -d cisco-4003
executing clogin -t 90 -c"show version;show boot;show flash;dir
bootflash:;dir slot0:;dir slot1:;dir sup-bootflash:;dir
sup-microcode:;show module;show port ifindex;write term all;write term"
cisco-4003-1-1709-1
PROMPT MATCH: cisco-4003-1-1709-1>
HIT COMMAND:cisco-4003-1-1709-1> (enable) show version
In ShowVersion: cisco-4003-1-1709-1> (enable) show version
...
HIT COMMAND:cisco-4003-1-1709-1> (enable) write term all
In WriteTerm: cisco-4003-1-1709-1> (enable) write term all
cisco-4003-1-1709-1: missed cmd(s): write term
cisco-4003-1-1709-1: missed cmd(s): write term

**** If I use clogin to issue the write term command it is often not
echoed on the console.

bash-2.05a$ clogin -c"write term" cisco-4003
cisco-4003
spawn telnet cisco-4003
Trying X.X.X.X...
Connected to cisco-4003
Escape character is '^]'.

Cisco Systems, Inc. Console

Unauthorised access is prohibited and will be prosecuted

User Access Verification

Username: rancid
Password:
cisco-4003> (enable)
cisco-4003> (enable) set length 0
Screen length for this session set to 0.
cisco-4003> (enable) set logging session disable
System logging messages will not be sent to the current login session.
cisco-4003> (enable)
cisco-4003> (enable)..............

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

begin

**** If I use clogin interactively ....

bash-2.05a$ clogin cisco-4003
cisco-4003
spawn telnet cisco-4003
Trying X.X.X.X...
Connected to cisco-4003.
Escape character is '^]'.

Cisco Systems, Inc. Console

Unauthorised access is prohibited and will be prosecuted

User Access Verification

Username: rancid
Password:
cisco-4003> (enable)
cisco-4003> (enable) write term
This command shows non-default configurations only.
Use 'write terminal all' to show both default and non-default
configurations.
...............

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

begin

**** It looks clogin is not recognising the output from write term
correctly, could this be so?

Thanks,
Peter.

--
_--_|\ Peter Yardley | petery at eng.uts.edu.au
/ \ Network & UNIX Systems Manager | Peter.Yardley at uts.edu.au
\_.--._* Faculty of Engineering, | Ph: +61 2 9514-2358
v University of Technology, Sydney.| Fax: +61 2 9514-2435

Problem with Cisco 4000 with CatOS 7.6 [ In reply to ]

lists at lowside

Sep 8, 2004, 7:19 AM

Post #2 of 3 (675 views)

Permalink

Cisco Cat OS 7.6 does not use write mem, all commands are written
immediately, you can see write mem isn't in the command reference guide
for that relase.

http://www.cisco.com/en/US/products/hw/switches/ps4324/products_command_reference_chapter09186a00801fd92d.html#wp999860

_L

Peter Yardley wrote:
> Hi,
>
> I have a Cisco 4000 which I recently upgraded to CatOS 7.6. after the
> upgrade rancid stopped
> working. The problem seems to be that it misses the "write term" command.
>
> bash-2.05a$ cat5rancid -d cisco-4003
> executing clogin -t 90 -c"show version;show boot;show flash;dir
> bootflash:;dir slot0:;dir slot1:;dir sup-bootflash:;dir
> sup-microcode:;show module;show port ifindex;write term all;write term"
> cisco-4003-1-1709-1
> PROMPT MATCH: cisco-4003-1-1709-1>
> HIT COMMAND:cisco-4003-1-1709-1> (enable) show version
> In ShowVersion: cisco-4003-1-1709-1> (enable) show version
> ...
> HIT COMMAND:cisco-4003-1-1709-1> (enable) write term all
> In WriteTerm: cisco-4003-1-1709-1> (enable) write term all
> cisco-4003-1-1709-1: missed cmd(s): write term
> cisco-4003-1-1709-1: missed cmd(s): write term
>
> **** If I use clogin to issue the write term command it is often not
> echoed on the console.
>
> bash-2.05a$ clogin -c"write term" cisco-4003
> cisco-4003
> spawn telnet cisco-4003
> Trying X.X.X.X...
> Connected to cisco-4003
> Escape character is '^]'.
>
> Cisco Systems, Inc. Console
>
> Unauthorised access is prohibited and will be prosecuted
>
> User Access Verification
>
> Username: rancid
> Password:
> cisco-4003> (enable)
> cisco-4003> (enable) set length 0
> Screen length for this session set to 0.
> cisco-4003> (enable) set logging session disable
> System logging messages will not be sent to the current login session.
> cisco-4003> (enable)
> cisco-4003> (enable)..............
>
> ..........................
> ..........................
> ..
>
> begin
>
> **** If I use clogin interactively ....
>
> bash-2.05a$ clogin cisco-4003
> cisco-4003
> spawn telnet cisco-4003
> Trying X.X.X.X...
> Connected to cisco-4003.
> Escape character is '^]'.
>
> Cisco Systems, Inc. Console
>
> Unauthorised access is prohibited and will be prosecuted
>
> User Access Verification
>
> Username: rancid
> Password:
> cisco-4003> (enable)
> cisco-4003> (enable) write term
> This command shows non-default configurations only.
> Use 'write terminal all' to show both default and non-default
> configurations.
> ...............
>
> ..........................
> ..........................
> ..
>
> begin
>
> **** It looks clogin is not recognising the output from write term
> correctly, could this be so?
>
> Thanks,
> Peter.
>

Problem with Cisco 4000 with CatOS 7.6 [ In reply to ]

heas at shrubbery

Sep 8, 2004, 10:21 AM

Post #3 of 3 (677 views)

Permalink

Wed, Sep 08, 2004 at 08:19:29AM -0700, Len:
> Cisco Cat OS 7.6 does not use write mem, all commands are written
> immediately, you can see write mem isn't in the command reference guide
> for that relase.
>
>
> http://www.cisco.com/en/US/products/hw/switches/ps4324/products_command_reference_chapter09186a00801fd92d.html#wp999860

Cisco has chosen to deprecate the 'write terminal' command in IOS, which has
been around since...oh 8.0. This is why rancid collects 'show running-config'
and write terminal (until we're sure everything has show running).

But, I wasn't aware it would also be deprecated in CatOS and the page above
does not indicate it has been (at least not for this release).

Anyway, note that cat5rancid runs both write terminal and write terminal all.
The problem Peter is having is that 'write terminal' is not echo'd, it just
starts writing the configuration. Also note that write terminal all _is_
echo'd. that is a cisco bug.

Peter, try a different TERM setting in rancid.conf, such as "dumb" (if your
termap/termios has that one).

> _L
>
> Peter Yardley wrote:
> >Hi,
> >
> >I have a Cisco 4000 which I recently upgraded to CatOS 7.6. after the
> >upgrade rancid stopped
> >working. The problem seems to be that it misses the "write term" command.
> >
> >bash-2.05a$ cat5rancid -d cisco-4003
> >executing clogin -t 90 -c"show version;show boot;show flash;dir
> >bootflash:;dir slot0:;dir slot1:;dir sup-bootflash:;dir
> >sup-microcode:;show module;show port ifindex;write term all;write term"
> >cisco-4003-1-1709-1
> >PROMPT MATCH: cisco-4003-1-1709-1>
> >HIT COMMAND:cisco-4003-1-1709-1> (enable) show version
> > In ShowVersion: cisco-4003-1-1709-1> (enable) show version
> >...
> >HIT COMMAND:cisco-4003-1-1709-1> (enable) write term all
> > In WriteTerm: cisco-4003-1-1709-1> (enable) write term all
> >cisco-4003-1-1709-1: missed cmd(s): write term
> >cisco-4003-1-1709-1: missed cmd(s): write term
> >
> >**** If I use clogin to issue the write term command it is often not
> >echoed on the console.
> >
> >bash-2.05a$ clogin -c"write term" cisco-4003
> >cisco-4003
> >spawn telnet cisco-4003
> >Trying X.X.X.X...
> >Connected to cisco-4003
> >Escape character is '^]'.
> >
> >Cisco Systems, Inc. Console
> >
> >Unauthorised access is prohibited and will be prosecuted
> >
> >User Access Verification
> >
> >Username: rancid
> >Password:
> >cisco-4003> (enable)
> >cisco-4003> (enable) set length 0
> >Screen length for this session set to 0.
> >cisco-4003> (enable) set logging session disable
> >System logging messages will not be sent to the current login session.
> >cisco-4003> (enable)
> >cisco-4003> (enable)..............
> >
> >..........................
> >..........................
> >..
> >
> >begin
> >
> >**** If I use clogin interactively ....
> >
> >bash-2.05a$ clogin cisco-4003
> >cisco-4003
> >spawn telnet cisco-4003
> >Trying X.X.X.X...
> >Connected to cisco-4003.
> >Escape character is '^]'.
> >
> >Cisco Systems, Inc. Console
> >
> >Unauthorised access is prohibited and will be prosecuted
> >
> >User Access Verification
> >
> >Username: rancid
> >Password:
> >cisco-4003> (enable)
> >cisco-4003> (enable) write term
> >This command shows non-default configurations only.
> >Use 'write terminal all' to show both default and non-default
> >configurations.
> >...............
> >
> >..........................
> >..........................
> >..
> >
> >begin
> >
> >**** It looks clogin is not recognising the output from write term
> >correctly, could this be so?
> >
> >Thanks,
> >Peter.
> >
>