Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: (ASCEND) Q: wdDialout not working ?
> Got a Max4000 running 5.0Ap38. Yesterday, some user had a ping going
> which kept one of the lines up all the time. Easy to find the offender,
> I thought, and enabled the wdDialout debug command. After a forced
> hangup the line came right up again, as expected. But, NO debug output.
> What did I do wrong ?
Were you calling the offender or was the offender calling you?
The wdDialout debug command displays the packet that causes the unit to
dial out. If the problem is a customer is dialing you and keeping the
line up, then wdDialout will not display anything because you did not
"Dialout".
Instead of using the "WAN Display Dialout" (wddialout), you want to use
the wanDSess ("WAN Display Session") debug command. Wandsess allows you
to see the packets that are part of a single session. The output in in
the same format as the wddialout information.
To use wandsess command, you must first get the User Name of the offender
is using. You can do this using the terminal server "show users" command
(or in 5.0Aix or 6.0.0, you can use "finger", if enabled). Then go into
Diagnostics mode and enter the "wandsess username 64", where username is
the "User Name" of the offender, to see the first 64 bytes of every packet
for their session.
Example:
wandsess baduser 64
When you are done, don't forget to disable the display before you quit
Diagnostic mode using "wandsess username 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>