Cisco PCMICIA Utility

2000-12-27 Thread Bowen, Shawn

Does anyone have or know where to get the Cisco software package for
formatting a PCMCIA Flash card in your PC and doing file manipulation with
it (Using the Cisco format so it's compatible when you stick it back in the
router or switch)???  I know it exists, but I have searched hi and low on
CCO to no avail.

Thanks,
Shawn

_
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



RE: CID test vs. CCIE written

2000-12-27 Thread Bowen, Shawn

It is similar in length, but it encompasses different items.  The "feel" is
similar, though you can go back through your answers on the written as many
times as you want.  I don't care what Cisco's www site says, it still has
TON's of Token Ring questions, you better know RIF's really well.  There is
ATM and LANE on it as well.  Also some very detailed circuit questions.  IPX
framing questions, basic DLSW, and STUN were on it as well.  I took both of
these last week, CID on Monday and CCIE on Tuesday, I was still amazed at
some of the abstract crap they through at me.

Good luck,
Shawn

P.S.

RIF = http://www.groupstudy.com/archives/cisco/199901/msg01626.html


-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
Dennis
Sent: Wednesday, December 27, 2000 1:58 PM
To: [EMAIL PROTECTED]
Subject: CID test vs. CCIE written

Just took and passed the CID test.  I have heard that this test is similar
in scope to the CCIE R/S qualification test.

Anybody have any feedback on that statement?

Also, does anyone know if there are command line type ins on the CCIE
written?

And can anyone recommend a good 'one-pager' on RIF's, Token Ring, bridging,
etc??

Thanks,
Dennis
CCNP, CCDP




_
FAQ, list archives, and subscription info:
http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

_
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



RE: IGRP Propagation???

2000-12-26 Thread Bowen, Shawn

That is weird, but if that's the case put the interface to the upstream in
passive mode and give it a try.  That way your providor won't see any
advertisements from you (Which they should ignore anyway).

Shawn

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
Timothy Metz
Sent: Tuesday, December 26, 2000 3:56 AM
To: [EMAIL PROTECTED]
Subject: IGRP Propagation???

Here's a strange one... maybe someone can shed some light...

My home setup:

Access Layer: 2505
Distro Layer: 2501
Core Layer: Netgear RT314 (DSL Router)

Workstations on 8 port hub (built into the 2505)
Access to Distro: Frame Relay
Distro to Core (LAN side): Ethernet
Core to Cloud (WAN side): Seimans DSL Modem

I don't know alot about the telecom side of DSL but my ISP knows who I am
based on my login, I do not get authenticated when checking mail or news.

If I enable IGRP on the Cisco routers (The netgear is RIP only) then I get a
message saying that I am not authorized to access the mail or news server on
the ISP side. When I disable IGRP all is fine.


Any thoughts?


Thanks,

Tim


_
FAQ, list archives, and subscription info:
http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

_
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



RE: Confused (was Re: is this statement true ??)

2000-12-26 Thread Bowen, Shawn

Yup, makes sense.  I can only speak for 3Com on this one, but I believe
Cisco implements similar features.  On a 3Com Corebuilder (as well as their
Workgroup Switches) they use fake collisions as a flow control mechanism.
In other words if there was contention at the server or switch and they
couldn't handle the load then a collision (a JAM) will be sent.  Now, that
said after we all just agreed that collisions can not happen on a full
duplex Ethernet segment:)  If you notice in Cisco texts that Collision
Detection is disabled on full duplex links, this is not true.  Collision
detection is still there, at least on a 5000 and can be simulated by loading
up a server at 10MB FD with a few 100MB FD clients on the other end of the
Cat, you will see this in action.  3Com does the same thing, I thought this
was kinda interesting.

Shawn


-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
Priscilla Oppenheimer
Sent: Tuesday, December 26, 2000 2:06 PM
To: Andy Walden; John lay
Cc: [EMAIL PROTECTED]
Subject: Re: Confused (was Re: is this statement true ??)

I think what John is getting at is that there is still contention. In his
example with two clients trying to reach one server, there's contention at
the switch, and at the server possibly. There's no contention on the medium
itself. There's only one device trying to send at any one time. The switch
has its transmit pair and the server has its own transmit pair. If the
switch has two frames to send to the server, the backup happens at the
switch. Does that make sense?

Priscilla

At 08:33 AM 12/26/00, Andy Walden wrote:

This is correct. You don't use full duplex if you are competing for
bandwidth, ie, plugged into a hub. But if you are plugged into a switch,
there is only one bandwidth domain between the device and switch and
with nothing competing for the bandwidth on that link so you can go full
duplex.

andy

On Tue, 26 Dec 2000, John lay wrote:

  Priscilla, everybody,
 
  I am confused. Ethernet and FastEthernet uses the CSMA/CD as a channel
  allocation techinque in a shared media access envoiroment.
  Here it comes the confusion, when you are saying that the Full-duplex
does
  not support CSMA/CD because the transmit and receive are on different
 wires.
  This implies that in this case there is no shared media, how come if
you
  have two clients competing to talk to the  same server
simultaneously!!
 
  Thanx
 
 
  On Mon, 25 Dec 2000 16:36:11 -0800, Priscilla Oppenheimer wrote:
 
It's true for Ethernet because Ethernet's CSMA/CD media access
control
method has strict timing requirements, which result in strict length
restrictions. Half-duplex uses CSMA/CD. Full-duplex does not.
  
I wouldn't say it's true in general, however.
  
Priscilla
  
At 05:32 PM 12/25/00, Li Song wrote:
"full-duplex can be used over longer distance than
half-duplex" ??
what 's your opinion ??


_
FAQ, list archives, and subscription info:
http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to
[EMAIL PROTECTED]
  
  

  
Priscilla Oppenheimer
http://www.priscilla.com
  
_
FAQ, list archives, and subscription info:
  http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to
[EMAIL PROTECTED]
 
 
 
 
 
  ___
  Send a cool gift with your E-Card
  http://www.bluemountain.com/giftcenter/
 
 
  _
  FAQ, list archives, and subscription info:
 http://www.groupstudy.com/list/cisco.html
  Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
 




Priscilla Oppenheimer
http://www.priscilla.com

_
FAQ, list archives, and subscription info:
http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

_
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



RE: Confused (was Re: is this statement true ??)

2000-12-26 Thread Bowen, Shawn

I believe we are saying mostly the same thing.  Your "* Extended carrier to
indicate busy (assert carrier beyond the length of the packet)." Is an
Ethernet JAM signal.  That's the same thing I was saying, though I was
putting it in more layman's terms, it's also what is immediately transmitted
onto the segment after a collision is detected to start the back off
routine.  Cat's will see collisions in this configuration.  I wasn't trying
to start a huge issue over this, merely pointing out to someone something
that I found interesting.
The only reason I took it to any depth was the fact that other than duplex
mismatches a lot of people getting into this field (reading these posts)
haven't ever been exposed to such nuances.  And I also guess I wanted to
point out that the Cisco documentation is not "always" 100% accurate in the
real world. 

Shawn

-Original Message-
From: Jeff Kell [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, December 27, 2000 12:16 AM
To: Bowen, Shawn
Cc: Priscilla Oppenheimer; Andy Walden; John lay; [EMAIL PROTECTED]
Subject: Re: Confused (was Re: is this statement true ??)

"Bowen, Shawn" wrote:

 Yup, makes sense.  I can only speak for 3Com on this one, but I believe
 Cisco implements similar features.  On a 3Com Corebuilder (as well as
their
 Workgroup Switches) they use fake collisions as a flow control mechanism.
 In other words if there was contention at the server or switch and they
 couldn't handle the load then a collision (a JAM) will be sent.  Now, that
 said after we all just agreed that collisions can not happen on a full
 duplex Ethernet segment:)  If you notice in Cisco texts that Collision
 Detection is disabled on full duplex links, this is not true.  Collision
 detection is still there, at least on a 5000 and can be simulated by
loading
 up a server at 10MB FD with a few 100MB FD clients on the other end of the
 Cat, you will see this in action.  3Com does the same thing, I thought
this
 was kinda interesting.

If collisions are reported on the Cisco 5000 then forget my following
diatribe as I don't have time to simulate it (and no testbed 5000, it
would be the production switch).

You stated (let me repeat it for emphasis)...

 Collision detection is still there, at least on a 5000 and can be
 simulated by loading up a server at 10MB FD with a few 100MB FD
  ^^^
 clients on the other end of the Cat, you will see this in action.

Older switches implement flow control in one of two ways:
* Simulated collisions (not terribly efficient), or
* Extended carrier to indicate busy (assert carrier beyond the length
  of the packet).

With 100Mbps we have varying implementations of the 802.something
method of the "pause" indicator in the header, and/or the "throttle"
mechanism (in Cisco terminology).  But your example specifically
indicates 10Mb, which has another variable.

In 10Mb ethernet, many NICs are setup to detect "jabber" -- asserting
carrier longer than the max packet length.  If this is detected, the
transmit circuit is turned off (ref Siefert, _Gigabit Ethernet_). 

All of the flow controls, as well as the "jabber" detection, can
result in a variety of line errors.  Only in the "throttle" case does
a Cisco switch continue without logging errors other than throttle
packet counts.  Throttling or pausing is undefined for 10Mb which may
be the corner case you are presenting, depending upon the intelligence
of the NIC in the server.

In a normal case, I would expect discards if you were throwing many
100Mb clients at a 10Mb server connection, after all flow control and
switch store-and-forward buffers had been exhausted.  You can overload
some of the older Catalyst switches (2926 for example) which has 24
ports at 100Mb and 2 uplinks at 100Mb but only 1.2Gb backplane.  If we
ignore the potential overloading of the uplink(s), the switch cannot
handle the potential load.  The newer 2924XL/3524XLs are more in line
with a 3Gbps backplane and could handle a full (distributed) load, but
still suffer from uplink congestion which is dependent on the buffer
space.  This is less of an issue with a 1000xX uplink but you can
still, in theory, overload the bandwidth of the switch.  But this is
true of any vendor's switch, if you oversubscribe the uplink, you can
overload the switch, regardless of flow control, buffer size, etc.

Bottom line, in southern terminology, there ain't no collisions on a
full-duplex link :-)

Jeff Kell [EMAIL PROTECTED]
Systems/Network Administrator
University of Tennessee at Chattanooga

_
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



RE: Confused (was Re: is this statement true ??)

2000-12-26 Thread Bowen, Shawn

I might also add I'm a southern fella myself.  But I must argue that you
"can" see collisions and late collisions on a full duplex link.  Before I
get thrashed, I understand FULLY that full duplex is TX to RX so it "should"
be impossible but I was just answering for a fellow earlier about this.  On
10MB links the Collision mechanism and it's corresponding JAM signal are
used as rudimentary flow control mechanisms, and can be seen on FD switches.
Another thing is you CAN see them from is crosstalk, cable attenuation
issues, Floresant lights, (and sun spots j/k), power cables trashing your
signal, and many other weird ones.  Telnet to a production switch with a lot
of traffic going through it and take a peak sometime, then clear the
counters and let it roll on.

And heck who knows, I'm wrong on occasion, if I am now I just need to lay
off the crack:)  j/k

Shawn

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Jeff
Kell
Sent: Wednesday, December 27, 2000 12:16 AM
To: Bowen, Shawn
Cc: Priscilla Oppenheimer; Andy Walden; John lay; [EMAIL PROTECTED]
Subject: Re: Confused (was Re: is this statement true ??)

"Bowen, Shawn" wrote:

 Yup, makes sense.  I can only speak for 3Com on this one, but I believe
 Cisco implements similar features.  On a 3Com Corebuilder (as well as
their
 Workgroup Switches) they use fake collisions as a flow control mechanism.
 In other words if there was contention at the server or switch and they
 couldn't handle the load then a collision (a JAM) will be sent.  Now, that
 said after we all just agreed that collisions can not happen on a full
 duplex Ethernet segment:)  If you notice in Cisco texts that Collision
 Detection is disabled on full duplex links, this is not true.  Collision
 detection is still there, at least on a 5000 and can be simulated by
loading
 up a server at 10MB FD with a few 100MB FD clients on the other end of the
 Cat, you will see this in action.  3Com does the same thing, I thought
this
 was kinda interesting.

If collisions are reported on the Cisco 5000 then forget my following
diatribe as I don't have time to simulate it (and no testbed 5000, it
would be the production switch).

You stated (let me repeat it for emphasis)...

 Collision detection is still there, at least on a 5000 and can be
 simulated by loading up a server at 10MB FD with a few 100MB FD
  ^^^
 clients on the other end of the Cat, you will see this in action.

Older switches implement flow control in one of two ways:
* Simulated collisions (not terribly efficient), or
* Extended carrier to indicate busy (assert carrier beyond the length
  of the packet).

With 100Mbps we have varying implementations of the 802.something
method of the "pause" indicator in the header, and/or the "throttle"
mechanism (in Cisco terminology).  But your example specifically
indicates 10Mb, which has another variable.

In 10Mb ethernet, many NICs are setup to detect "jabber" -- asserting
carrier longer than the max packet length.  If this is detected, the
transmit circuit is turned off (ref Siefert, _Gigabit Ethernet_). 

All of the flow controls, as well as the "jabber" detection, can
result in a variety of line errors.  Only in the "throttle" case does
a Cisco switch continue without logging errors other than throttle
packet counts.  Throttling or pausing is undefined for 10Mb which may
be the corner case you are presenting, depending upon the intelligence
of the NIC in the server.

In a normal case, I would expect discards if you were throwing many
100Mb clients at a 10Mb server connection, after all flow control and
switch store-and-forward buffers had been exhausted.  You can overload
some of the older Catalyst switches (2926 for example) which has 24
ports at 100Mb and 2 uplinks at 100Mb but only 1.2Gb backplane.  If we
ignore the potential overloading of the uplink(s), the switch cannot
handle the potential load.  The newer 2924XL/3524XLs are more in line
with a 3Gbps backplane and could handle a full (distributed) load, but
still suffer from uplink congestion which is dependent on the buffer
space.  This is less of an issue with a 1000xX uplink but you can
still, in theory, overload the bandwidth of the switch.  But this is
true of any vendor's switch, if you oversubscribe the uplink, you can
overload the switch, regardless of flow control, buffer size, etc.

Bottom line, in southern terminology, there ain't no collisions on a
full-duplex link :-)

Jeff Kell [EMAIL PROTECTED]
Systems/Network Administrator
University of Tennessee at Chattanooga

_
FAQ, list archives, and subscription info:
http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

_
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



RE: is this statement true ??

2000-12-25 Thread Bowen, Shawn

Very well said Priscilla, more or less what I was trying to say from memory.
Also included in this is that when a collision is detected a jam is sent on
the wire and the back off mechanism comes into play, should another
collision occur, then another back off of a longer period takes place, and
so on.  After 4 (If I remember correctly) back offs the packet is dropped
and left to a higher layer protocol to retransmit.  You are correct that a
late collision indicates a collision that is past the preamble and should
never happen in a properly designed and specified Ethernet segment, however
when they do occur it is most likely a cable that is beyond length in spec.

While we are on the topic I am often asked what a runt is, simply
put it is the fragments that result in collisions on an Ethernet segment, a
somewhat normal condition.  With Store and Forward switching runts will be
eliminated from the wire while with cut-through switching they can be
propagated.  This being said, even though Cut-Through can be faster on a
lightly loaded network store and forward can provide for higher throughput
on a more saturated network due to this fact.

Also I am asked what giants are.  They are the result of an Ethernet
frame being larger than the IEEE limit of 1524 (Or 1518 depending on who
your talking to) Bytes.  This can be from a few things, the most important
being VLAN tagging.  Other sources are mis-configured stations on the wire
or NIC's that are spewing garbage on the wire.

For anyone really interested in a GREAT sight covering these items
the original writer of the CNX certification has an excellent web site with
all these goodies on it.  It is www.optimized.com go there and check out the
Technical Compendium link.

Merry Christmas to all,
Shawn

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
Priscilla Oppenheimer
Sent: Monday, December 25, 2000 7:47 PM
To: Bowen, Shawn; Li Song; [EMAIL PROTECTED]
Subject: RE: is this statement true ??

At 01:07 PM 12/25/00, Bowen, Shawn wrote:
According to IEEE NO, 100 Meters is the max cable distance for Half or Full
100MB Ethernet over TP.  In reality, Yes it will extend the range, The
reason why is that at full duplex you can not have collisions, and
collisions are the main reason for the distance limitation (Cross Talk
comes
into play as well).  The reason behind this is that in the original IEEE
spec the distance limitation was set so that a single 64Byte packet (the
smallest) could be transmitted down the line and would collide with another
packet before the 64Byte packet header had been completely transmitted,
when

Minor correction: The distance limitation is defined so that if a station
is transmitting a minimum-size frame (64 bytes) and a collision occurs at
the other end of the network, the collision will reflect back to the sender
while the sender is still sending. If this didn't happen, the sender would
have stopped monitoring for a collision with its transmission, and would
not automatically retry. An upper layer would have to retransmit, which
takes a lot longer.

this does not happen properly you see late collisions, these indicate a
collision past the preamble header of the packet and indicate a cable
length
that is to long.

A late collision is one that happens past the preamble and past the first
64 bytes of the frame. A collision within the first 64 bytes is legal,
normal, and not late.

Priscilla

If you need to even go close to the 100 Meter mark you
should consider 100BaseFX or similar.

Shawn

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Li
Song
Sent: Monday, December 25, 2000 4:33 AM
To: [EMAIL PROTECTED]
Subject: is this statement true ??

"full-duplex can be used over longer distance than
half-duplex" ??
what 's your opinion ??


_
FAQ, list archives, and subscription info:
http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

_
FAQ, list archives, and subscription info:
http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]




Priscilla Oppenheimer
http://www.priscilla.com

_
FAQ, list archives, and subscription info:
http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

_
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



RE: CSU

2000-12-24 Thread Bowen, Shawn

CSU is a channel service unit.  A CSU/DSU is similar to a modem in that it
converts analog signals to digital, as well as providing a mechanism for
breaking down individual DS0's in a DS1 so that they can be bundled or muxed
out.  This would be the piece of equipment between you and the Telco, a
typical configuration would be Router to CSU/DSU to Telco SmartJack or local
DAX to local loop to long haul to remote local loop to smart jack / local
DAX to CSU/DSU to Router.  Several flavors of routers have CSU/DSU's built
into them so that the external box is no longer necessary in some cases.

Shawn

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Hunt
Sent: Saturday, December 23, 2000 5:12 PM
To: [EMAIL PROTECTED]
Subject: CSU

Can anyone please tell me what is a CSU?  And what is it used for?

Hunt   =^o^=

_
FAQ, list archives, and subscription info:
http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

_
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



RE: can u route in boot mode?

2000-12-23 Thread Bowen, Shawn

Had this issue last night.  7505 wit 2 VIPS's.  Came up in boot mode and
wouldn't fire up any Ethernet ports, all were UP/DOWN indicating a physical
connection problem, I to wanted to drop new code on it with a directly
connected TFTP laptop (I used the right cables).  I ended up resolving it by
going to ROMMON  Changing confreg to boot without the config, blowing the
config away, resetting the config registers and bouncing the router.  It
came up fine, added the config back to the router and worked AOK from then
on.

Happy Holidays,
Shawn

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Kane,
Christopher A.
Sent: Friday, December 22, 2000 3:09 PM
To: 'Manny Akintayo'; [EMAIL PROTECTED]
Subject: RE: can u route in boot mode?

My experience has been that you can't route packets, so it couldn't be
"production". But, you could setup a default gateway. This way you could
telnet to the router and setup to get IOS via TFTP.

-Original Message-
From: Manny Akintayo [mailto:[EMAIL PROTECTED]]
Sent: Friday, December 22, 2000 9:46 AM
To: [EMAIL PROTECTED]
Subject: Re: can u route in boot mode?


no you can not route.Your router is in a coma-like state.

a wrote:

 I have recently read that you can not route while in boot mode (0x101). I
 have a 7000 router and am able to route in boot mode just fine? what
gives?
 thx a bunch.

 _
 FAQ, list archives, and subscription info:
http://www.groupstudy.com/list/cisco.html
 Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

_
FAQ, list archives, and subscription info:
http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

_
FAQ, list archives, and subscription info:
http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

_
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



RE: 7505 Reboots randomly Please HELP

2000-12-21 Thread Bowen, Shawn

This is an issue with 12.07T, I have seen it a lot with AS5800's running
this code.  Boot without a config let it get FULLY booted, then copy start
to run.  This works for us, as it seems the router does not fully get
initialized before certain configurations get loaded.  Also, it seems that
console logging on the 5800 is what kills it when it runs out of memory
after initializing all the modems on the 5800's(1400 of em!).  Like I said,
I know why this happens on 5800s, I'm assuming the issue is following to the
7505's.  One other note, if you have the back plane oversubscribed with
certain cards it will do this as well.

Shawn

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
Desai, Inamul
Sent: Thursday, December 21, 2000 3:03 PM
To: [EMAIL PROTECTED]
Subject: 7505 Reboots randomly Please HELP


We got 7505 router reboots randomly twice a week or
when you write to config file. We gone thru changing
VIP card, resetting all cards, resetting mem modules, swapping
mem modules on VIP card, powering up and down and talked to Cisco.
It's running IOS 12.0(7)T with RSM, VIP2 and one PRI module.
No matter how many times you cold boot it, it brings all
enable LEDs except one on fastEthenet card. It does help
some time when I reset FLASH cards.
D u think it's flash cards ?

here is startup info:
System Bootstrap, Version 5.3.2(3.2) [kmac 3.2], MAINTENANCE INTERIM
SOFTWARE
Copyright (c) 1994 by cisco Systems, Inc.
RSP processor with 131072 Kbytes of main memory


Creading the file into memory...
Self decompressing the image :
#


### [OK]
%DBUS-3-SW_NOTRDY: DBUS software not ready after HARD RESET, elapsed 12032,
stat
us 0x0
-Traceback= 60192B5C 60195A84 60195B3C 6015444C 601546C8 60128990 600109B0
%DBUS-3-SW_NOTRDY: DBUS software not ready after HARD_RESET, elapsed 12032,
stat
us 0x0
-Traceback= 60192B5C 60194BA0 60195008 6019845C 600F4E64 600F4ECC 600E9090
600E9
298 600EA3B0 600EA39C
%DBUS-3-SW_NOTRDY: DBUS software not ready after RESET, elapsed 12032,
status 0x
40
-Traceback= 60192B5C 60194EC0 60191AF4 60195054 6019845C 600F4E64 600F4ECC
600E9
090 600E9298 600EA3B0 600EA39C
System Bootstrap, Version 5.3.2(3.2) [kmac 3.2], MAINTENANCE INTERIM
SOFTWARE
Copyright (c) 1994 by cisco Systems, Inc.
RSP processor with 131072 Kbytes of main memory


Creading the file into memory...
Self decompressing the image :
#


### [OK]
%CBUS-3-CCBPTIMEOUT: CCB handover timed out, CCB 0x5800FF50, slot 3
-Traceback= 601A5348 601A398C 601A3E3C 6019D4F0 600EE70C 600F4EFC 600E9090
600E9
298 600EA3B0 600EA39C
%LINK-4-NOMAC: A random default MAC address of .0c9a.31e7 has
been chosen. Ensure that this address is unique, or specify MAC
addresses for commands (such as 'novell routing') that allow the
use of this address as a default.
%SYS-4-CONFIG_NEWER: Configurations from version 12.0 may not be correctly
under
stood.CC

CC
%CBUS-3-MIPSTAT: Out of buffers--losing status information for the MIP
cardC


CC

_
FAQ, list archives, and subscription info:
http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

_
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



RE: [re - A silly question - modified]

2000-12-21 Thread Bowen, Shawn

Ctrl-shift-6 let go then X

Shawn

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
Charles Nunie
Sent: Thursday, December 21, 2000 12:13 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: [re - A silly question - modified]

Thanx. 

For years I've tried to figure that one out.

Dzilo


[EMAIL PROTECTED] wrote:
I believe it is ctrl+shift+6  al at the same time.

Gene

While I try to ping a remote ip address from the router CLI, I am asked to
 type escape sequence to abort.
 
 I know I would sound silly asking this question, But to be honest, I
don't
 know the answer for this. Can anyone tell me what is the escape sequence
to
 abort pinging from the CLI.
 
 
 *** I am pinging from within a telnet session to the Router ***
 
 Thanks in Advance,
 S.Kalidasan

_
FAQ, list archives, and subscription info:
http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



Get free email and a permanent address at http://www.netaddress.com/?N=1

_
FAQ, list archives, and subscription info:
http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

_
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]