Re: possible quirk in cisco IOS [7:37628]
No , I have never had problem with 2 or 3 IOS. as long as I have enough space.. - Original Message - From: "mike rose" To: Sent: Thursday, March 07, 2002 10:39 PM Subject: possible quirk in cisco IOS [7:37628] > All, > > I recently uploaded a new IOS to a flash card on a cisco device and did not > reboot it, I just left it up there so I could relod it al a later time. I > set the boot prompt to boot from the new IOS though. For some reason a dumb > ass colegue at work thinks there might be a bug in the IOS (ver 12.6) that > makes the router go into stall mode when 2 IOS images reside in the IOS. I > was wondering, has any one else experienced this ? > > Thanks > > Mike Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=37643&t=37628 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: throttles and input drops [7:46406]
Check to see if you are doing process switching on this router. or Check the buffers on your router, This error comes out normally when you are doing process switching for debug and buffer is full. jin jung CCNP, CCDP,, - Original Message - From: "rmart." To: Sent: Wednesday, June 12, 2002 10:36 PM Subject: throttles and input drops [7:46406] > Hi, > > My router, cisco 7000 series having problem with a number of throttles and > input drops on one of the FastEth interface. > cpu utilization seems ok (below 5%). > > below is the output of sh int : > > FastEthernet0/1 is up, line protocol is up > Hardware is i82543 (Livengood), address is 0004.9b6e.c406 (bia > 0004.9b6e.c406) > Description: used by sub-interfaces > Internet address is 212.194.2.3/23 > MTU 1500 bytes, BW 10 Kbit, DLY 100 usec, rely 255/255, load 5/255 > Encapsulation ARPA, loopback not set > Keepalive set (10 sec) > Full-duplex, 100Mb/s, 100BaseTX/FX > ARP type: ARPA, ARP Timeout 04:00:00 > Last input 00:00:00, output 00:00:00, output hang never > Last clearing of "show interface" counters 23:03:59 > Queueing strategy: fifo > Output queue 0/40, 0 drops; input queue 0/75, 869280 drops > 30 second input rate 3313000 bits/sec, 738 packets/sec > 30 second output rate 226 bits/sec, 744 packets/sec > 42338355 packets input, 3700449939 bytes > Received 0 broadcasts, 0 runts, 0 giants, 1307541 throttles > 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored > 0 watchdog, 0 multicast > 0 input packets with dribble condition detected > 43216540 packets output, 1919733782 bytes, 0 underruns > 0 output errors, 0 collisions, 0 interface resets > 0 babbles, 0 late collision, 0 deferred > 0 lost carrier, 0 no carrier > 0 output buffer failures, 0 output buffers swapped out > > any ideas? > Thanks. > > Rey Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=46413&t=46406 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: ISDN Problem [7:47411]
I vould be wrong but you may need to configure "dialer map" statements for each subnets.. - Original Message - From: "George Sherman" To: Sent: Tuesday, June 25, 2002 2:40 PM Subject: ISDN Problem [7:47411] > I have two routers connect throgh an ISDN switch. > System image file is "flash:c2500-js56i-l.121-12.bin > > When I change the address to 135.11.35.0 /24 I can not ping. I verified > that the call went through > 11R3#ping 135.11.35.2 > > Type escape sequence to abort. > Sending 5, 100-byte ICMP Echos to 135.11.35.2, timeout is 2 seconds: > . > Success rate is 0 percent (0/5) > R11R3#sh isdn act > > > ISDN ACTIVE CALLS > > > CallCalling Called Remote Seconds Seconds Seconds > Charges > TypeNumber Number NameUsedLeftIdle > Units/Currency > > > In 8995101 899520136 114 5 > > > > If I change the address to 135.11.35.0 /27 it works well and if I change > to 135.110.35.0 /24 it works. I am puzzled any ideas? > > > R11R3#sh run int bri0 > Building configuration... > > Current configuration : 182 byte > ! > interface BRI0 > ip address 135.11.35.1 255.255.255.0 > dialer string 8995101 > dialer-group 1 > isdn switch-type basic-ni > isdn spid1 8995201 8995201 > isdn spid2 8995202 8995202 > end > > > R11R4#sh run int bri0 > Building configuration... > > Current configuration : 182 bytes > ! > interface BRI0 > ip address 135.11.35.2 255.255.255.0 > dialer string 8995201 > dialer-group 1 > isdn switch-type basic-ni > isdn spid1 8995101 8995101 > isdn spid2 8995102 8995102 > end > > > > HERE IS THE COMPLETE CONFIGURATION: > R11R3#sh run > Building configuration... > > Current configuration : 1967 bytes > ! > version 12.1 > service timestamps debug uptime > service timestamps log uptime > no service password-encryption > ! > hostname R11R3 > ! > enable secret 5 $1$LX3.$7TGAHxWdu5Zw8iWCkIHhf1 > enable password lab > ! > username r4 password 0 r4 > ! > ! > ! > ! > ip subnet-zero > ip tcp synwait-time 5 > no ip domain-lookup > ip host R11R1 135.11.1.1 > ip host R11R3 135.11.3.3 > ip host R11R4 135.11.4.4 > ip host R11R6 135.11.6.6 > ip host R11R7 135.11.7.7 > ip host R11R8 135.11.8.8 > ip host R11R16 135.11.16.16 > ! > isdn switch-type basic-5ess > ! > ! > crypto isakmp policy 10 > hash md5 > authentication pre-share > crypto isakmp key cisco address 135.11.34.5 > ! > ! > crypto ipsec transform-set tor7 esp-des > ! > crypto map toR7 10 ipsec-isakmp > set peer 135.11.34.5 > set transform-set tor7 > match address 101 > ! > ! > ! > ! > interface Loopback0 > ip address 135.11.3.3 255.255.255.0 > ! > interface Loopback2 > no ip address > ! > interface Ethernet0 > ip address 135.11.56.3 255.255.255.0 > crypto map toR7 > ! > interface Serial0 > no ip address > shutdown > no fair-queue > ! > interface Serial1 > no ip address > shutdown > ! > interface Serial2 > no ip address > shutdown > ! > interface Serial3 > no ip address > shutdown > ! > interface BRI0 > ip address 135.11.35.1 255.255.255.0 > dialer string 8995101 > dialer-group 1 > isdn switch-type basic-ni > isdn spid1 8995201 8995201 > isdn spid2 8995202 8995202 > ! > router igrp 10 > network 135.11.0.0 > ! > ip classless > ip http server > ! > access-list 101 permit ip host 135.11.3.3 host 135.11.7.7 > dialer-list 1 protocol ip permit > ! > alias exec ct config t > alias exec sc show controllers serial > alias exec sci show cdp interface > alias exec scn sh cdp neighbor > alias exec sip show ip route > alias exec sipx show ipx route > alias exec cip clear ip route * > alias exec cib clear ip bgp * > alias exec sib show ip bgp > ! > line con 0 > exec-timeout 0 0 > password lab > logging synchronous > login > line aux 0 > exec-timeout 0 0 > password lab > logging synchronous > login > line vty 0 4 > exec-timeout 0 0 > password lab > logging synchronous > login > ! > end > > R11R3# > > R11R4#sh run > Building configuration... > > Current configuration : 2781 bytes > ! > version 12.1 > service timestamps debug uptime > service timestamps log uptime > no service password-encryption > ! > hostname R11R4 > ! > enable secret 5 $1$wnCW$4qHyuNAOZk3Z2FYnq7IUG0 > enable password lab > ! > username cisco password 0 cisco > username r3 password 0 cisco > ! > ! > ! > ! > ip subnet-zero > ip tcp synwait-time 5 > no ip domain-lookup > ip host R11R1 135.11.1.1 > ip host R11R3 135.11.3.3 > ip host R11R6 135.11.6.6 > ip host R11R7 135.11.7.7 > ip host R11R8 135.11.8.8 > ip host R11R16 135.11.16.16 > ip host R11R4 135.11.4.4 > ! > isdn switch-type basic-5ess > ! > ! > ! > ! > ! > interfa
Re: Cisco Works 2000 problem [7:56601]
Busy flag is normally set, but clears away in while, What other problems do you have? also, make sure you set the swap file to double your memory. jin jung - Original Message - From: "Tim Champion" To: Sent: Thursday, October 31, 2002 11:31 AM Subject: Cisco Works 2000 problem [7:56601] > I have a problem with Cisco Works 2000 whereby the ANI server has the busy > flag set. This is effecting many of the services. I have tried all of the > suggestions on CCO but it has made no difference. Has anyone else seen this > before? > > Cheers > > Tim Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=56738&t=56601 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: Collision Detecting [7:48830]
You can run at 10/FULL// - Original Message - From: "Dan Penn" To: Sent: Monday, July 15, 2002 11:04 PM Subject: RE: Collision Detecting [7:48830] > You are wrong =) That is OLD stuff that won't do 10/full > > Dan > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of > Kohli, Jaspreet > Sent: Monday, July 15, 2002 2:45 PM > To: [EMAIL PROTECTED] > Subject: RE: Collision Detecting [7:48830] > > Just confirming that when we say full duplex we are referring to > switched > networks over 100Mb. 10 Mb networks cannot run on full duplex. Please > correct me if I am wrong. > > Jaspreet Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=48884&t=48830 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
