Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: (ASCEND) PANIC: Problems with 6.0.0

OK, here's the setup:
MAX running OSPF.  Nothing fancy, just one area with no authentication.
Radius is running.  This happens on more than one machine.  Three of them
have "monolithic" address pools, i.e. they all fit in a subnet, but they
aren't broadcast that way(yet). One of them has two pools.

The Max still claims to have a route to the interface.

Here's the radius entry:
DEFAULT Password = "UNIX", NAS-Port-Type = Async,
        User-Service = Framed-User,
        Framed-Protocol = PPP,
        Framed-Address = 255.255.255.254,
        Framed-Netmask = 255.255.255.255,
        Framed-Routing = None,
        Ascend-Idle-Limit = 1200

Last time I talked to Ascend, someone suggested it was a problem with
firmware on the remote modem, and that the incoming(to the max) data stream
was locked up.  It's happened enough times that I don't think that's it.

I'll look at the iproutedebug output for a while.
--
Neal Rigney, PERnet Communications, (409)729-4638
neal@mail.pernet.net
"I've seen better bandwidth between two gorillas with flash cards!"
-----Original Message-----
From: Tim Basher <basher@alpha.CES.cwru.edu>
To: ascend-users@max.bungi.com <ascend-users@max.bungi.com>
Date: Tuesday, March 03, 1998 5:17 PM
Subject: Re: (ASCEND) PANIC: Problems with 6.0.0


>> I didn't speak clearly enough.  When the problem I relate happens, a ping
>> will go through all the way to the max(shown by a tcpdump) from the
>> network(i.e. my machine in the office), but never shows up on the
wandsess.
>> On the other hand, the connection in question can SEND packets to the
>> network.  If they run a ping, wandsess shows packets coming from them and
>> tcpdump shows packets going on the wire.
>
>Okay, then that would match with the MAX losing its local route to the
>WAN (but it also matches a couple of other possible problems).  As long
>as the physical and link-layer connection exists, the remote system can
>send packets in and the MAX will be about to route them based on the
>destination address.
>
>Depending upon how the WAN route was advertised (is it a network route,
>is it a host route, is it part of a network route for an address pool?)
>packets might be able to get back to the MAX, but not out the WAN.
>
>When this problem occurs you need to gather the information to see why
>the network layer on the MAX is not able to deliver the packets to the
>correct WAN interface.
>
>[That is what the questions I proposed were trying to address.]
>
>Another tool you might try to use in 6.0.0 is the Diagnostic command
>"ip-routeDebug 10".  This will show the routes coming and going
>(it produces a lot information so be careful and disable it when you
>are done with "ip-routeDebug 0").
>++ Ascend Users Mailing List ++
>To unsubscribe: send unsubscribe to ascend-users-request@bungi.com
>To get FAQ'd: <http://www.nealis.net/ascend/faq>
>

++ Ascend Users Mailing List ++
To unsubscribe:	send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd:	<http://www.nealis.net/ascend/faq>
Follow-Ups: