RE: [USR-TC] disconnect after 30 seconds??
Very wierd. No idea at all. -----Original Message----- From: Mike Greene [mailto:mikeg@rockisland.com] Sent: Monday, February 24, 2003 11:02 AM To: usr-tc@mailman.xmission.com Subject: RE: [USR-TC] disconnect after 30 seconds?? At 10:34 AM 2/24/2003 -0600, you wrote:
Is this on a Hiper ARC? If so, do this:
Dialup to the chassis and start your ping going to keep it connected.
telnet to the ARC.
enter the command SHOW SESSION <your_username>
This will show you the Idle timeout. If it's 30, which I suspect it will be, then you need to find where it's getting that from. You can do a MON RAD, then dialup and monitor for the user to see whether or not it's coming from the radius server during authentication.
Just a couple suggestions.
Thanks Joel, Unfortunately that didn't reveal a smoking gun... The first session was without the idle timer specified in radius (notice the idle timeout is not shown in the first session). INFORMATION FOR SESSION mikeg Service Type: Framed Framed Protocol: PPP Session Timeout: 28800 Speed of Connection: Auto NAS IP Address: x.x.x.72 Login Service: Telnet Interface Name: slot:1/mod:22 Active Session ID: 18688388 Traffic Threshold: 0 Keep Alive Interval: 0 Framed IP Netmask: 255.255.255.0 MLPPP Fragmentation Threshold: 0 Framed Routing: None Framed Callback Identifier: 0 Framed MTU: 1500 Compression Algorithm: None Compression Reset Mode: Auto Receive Acc Map: 0 Transmit Acc Map: 0 Here is the 2nd session with the idle timer enabled in Radius, still get disconnected after 30 seconds though. INFORMATION FOR SESSION mikeg Service Type: Framed Framed Protocol: PPP Session Timeout: 28800 Idle Timeout: 1800 Speed of Connection: Auto NAS IP Address: x.x.x.72 Login Service: Telnet Interface Name: slot:1/mod:23 Active Session ID: 18756472 Traffic Threshold: 0 Keep Alive Interval: 0 Framed IP Netmask: 255.255.255.0 MLPPP Fragmentation Threshold: 0 Framed Routing: None Framed Callback Identifier: 0 Framed MTU: 1500 Compression Algorithm: None Compression Reset Mode: Auto Receive Acc Map: 0 Transmit Acc Map: 0 HiPer>> Very strange indeed! I think I'll reboot the chassis and see what happens. - Mike ------------------------------------------------ Rock Island Communications, Inc. (360)-378-5884 http://www.rockisland.com/ San Juan Islands, WA ------------------------------------------------ _______________________________________________ USR-TC mailing list USR-TC@mailman.xmission.com http://mailman.xmission.com/cgi-bin/mailman/listinfo/usr-tc
Thank you all for your suggestions, the final fix was to reset the DSP card. I don't know if this was a bug tickled by someone trying to do MultiLink over a PRI fed DSP (we don't support MultiLink) but that is the only thing I can see that may have contributed to this issue. We had signed up a new customer for this POP and they were the only ones trying to do a multilink session, never saw that attempted before in the radius detail logs. Oh, well... add that to our KB of quirky issues with 3COM gear! (to be fair, we have had great success with our TC chassis's) - Mike ------------------------------------------------ Rock Island Communications, Inc. (360)-378-5884 http://www.rockisland.com/ San Juan Islands, WA ------------------------------------------------
participants (2)
-
Joel - Fox Computers -
Mike Greene