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

Re: (ASCEND) PANIC: Problems with 6.0.0

> > It appears that the Max suddenly stops routing packets
> > over established profiles that worked correct a second before. It
> > seems to be a highlevel issue: using wandsess I can see that the Max
> > stops sending out any packet on the session, completely ignoring that
> > I'm pinging to the other side like crazy. Hang up and redial of the
> > session and all works again, but we've seen this too often now to
> > call it spurious - it is a systematic problem. The routing table
> > doesn't show up any problems (Ok I didn't dive into whether the wanX
> > displayed there is indeed the one associated with the profile...).

Okay.  How is the profile being created?  Is it from a local profile,
the answer profile, or a RADIUS profile?  Are you using assigned IP
addresses, local address pools, or global address pools?  You say
you do not get response from the ping, what does traceroute show?
You say you cannot see the ping, but if the peer pings you do you see
the packet in the wadsess output?  Were you seeing the wadsess output
before the problem occured?

Check the output of the terminal server "show users" and "show ip routes"
commands.  Are there any duplicate addresses, overlapping network routes,
duplicate names?

Check the output of the "show ip stats" and "show icmp" commands.  Are
any of the error counters increasing when you try to ping the peer?

> Did you perchance notice is data was flowing OUT of the Max from the
> connection?  i.e. If they ping a host, can you see the icmp requests go out
> on the wire?

The first message said explicity "using wandsess I can see that the Max
stops sending out any packet on the session" so no data was flowing out
of the Max onto the connection.

> This is a long-standing issue I've never had sufficiently explained to me.
> The Max loses the route TO the host, but not FROM the host.  Go figure.

In addition, in traditional routing, there is no such thing as a route
"from [a] host".  Routes are based on destination address and contain
the "next hop" (who to send the packet to next).  [I added the qualifier
of "traditional routing" because some vendors are now doing policy routing
or flow routing or tag-based routing that look at the source address,
but this is not typically the case in the MAX].
++ 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: