I have a 3005 Concentrator here at the office that I have in the pre-deployment phase. One of the things that I have been experiencing with this box is some sort of sleep mode that seems to kick in when the box has been inactive for some time...(a day or two). Now, when I access the Concentrator either thru a telnet session, or a HTTP session, it seems to wake it up, and no one has problems getting in. I have given it a lot of thought, and the only thing I can come up with is an ARP timeout coming from one of the Routers...Any Suggestions?
Can you better describe this “sleeping” state so I can try helping you out? If it’s not being used, sure the arp cache will clear in the surrounding routers but when it gets a packet destined for the 3005 is should re-arp and work transparently. I suppose you could set a static arp entry for the device but if it’s not broken is there anything to fix?
It just won't allow authentication onto the network... That's about all I can say. I can access it either thru a telnet session, or thru a http session, and as soon as I hit the interfaces, it will immediately allow traffic to pass.
Those are very odd symptoms, I’ve never heard of such a problem. Did you try the static arp j-block recommended? I’d suggest talking to Cisco on this one. Be sure to let us know what you come up with.
Weeks off and on, and they couldn't seem to solve the problem. However, now I believe it may have been a bug in the code, as I have recently upgraded to v3.0.3, and things seem to have calmed down.
Learn, share, save
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
