You may be able to de-stack the switches and try them seperately... may be able to, but you also may be in bad shape.
Never had one do that but my switch guy thinks it isn't a good situation.
You also may be able to get a good switch, make it the primary in the stack and attempt to update the...
So... you're in the 2511 just fine, you telnet from the 2511 to the 2600 via asynchronus port #14, get the prompts, actually log-in, and THEN you get garbled output?
Doesn't seem to me that the concern is with hyperterm settings when we're using telnet to hit a VTY port.
Are you also using...
It seems that disabling a static route is the most common cause. Sometimes, within a few moments of setting a static to inactive, the CPU will go 100%, and all connectivity is hosed. Can't reach the passport in any manner, even the console port. The OSPF neighbor states on connected routers...
Well...
172.16.0.2(client) resides on the 172.16.0.0/16 subnet which is the zero subnet for that mask.
In config mode enter: ip subnet-zero
Everything else looks ok.
In most cases where you can ping locally to an address but not off-net, the node you cannot ping off-net has either: a) mis-configured subnet mask or b) a mis-configured default gateway.
MULTICAST and BROADCAST storms wreak havoc on the 8600's CPU. Ours is generally caused by OSPF which uses multicast addressing to propagate information. Something in the OSPF process on these boxes isn't quite right and once it goes totally ballistic on you a re-boot is the only cure. I have...
This will cause the router to always take 1.1 unless the 1.1 interface is down, it will then "promote" 2.1 into the route table.
ip route 172.27.20.0 255.255.255.0 172.18.1.1
ip route 172.27.20.0 255.255.255.0 172.18.2.1 150
This will cause the router to place both entries into the route table...
What about this?
Some applications change port numbers within a session. They may initially transmit to a well-known port and then shift ports. This will not work with RACL's. Active FTP is an example of such an application. You'll need passive FTP if you plan on using reflexive access lists.
On the switch port the router is connected to issue sh int <switchport> and look for operational speed and duplex. My guess is they don't match the router!
You have a duplex mis-match most likely!
No particular code; I've seen it happen on 1600 routers, 6513's with SUP720's, and a 7513. All I can say is, never save a config with WR; use WR MEM or copy run start.
You haven't explained what you're using to pass data between VLAN's? You have said you connected a server to port 24 but you don't mention a router. Since each VLAN has to have a different IP subnet, how are you routing between them?
Also; how can your server talk on different VLANs unless he...
What I have seen is this:
Issuing the WR command instead of WR MEM does not necessarily write the config into NVRAM. I have changed a config, issued the WR command, booted the router, and the changes are gone! When I use WR MEM the config is saved every time.
When you eliminate the router how is the connectivity? Do you move the DSL to the inside VLAN on the switch so all PC's still have access?
When you conduct the test with the router removed are you generating the same amount of traffic as with the router in?
I expect you are but I don't like...
So really... what's going on here is:
1. Remote says send me SEQ 563 next
2. Local sends SEQ 563
3. Remote again asks for SEQ 563
4. Local sends SEQ 563
5. Remote again asks for SEQ 563
6. Local sends SEQ 563
7. Eventually the remote sends an RST.
Well, the remote is sending a RST because he...
1. If the host is on a different subnet the server responds to the IP address of the relay agent (router) which forwarded it the request and the router sends it to the requesting node.
2. If the host is on the same subnet the server responds to the source MAC of the requesting host.
3. Routers...
Once the DHCP server receives the DHCPDISCOVER packet from the client or relay agent he places an available address for the requested LAN in the packet and sends it back to either the client - if they're on the same LAN - or the relay agent (router) which sent it.
An RFC exists for this...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.