Caught another one;
sh m44
Card Type: LU1674 Chipset
State: ACTIVE
Active Port: S44
Transmit Rate: 28000
Receive Rate: 19200
Connection Type: DIRECT/NONE
Chars Sent: 384633
Chars Received: 60949
Retrains: 1
Renegotiations: 2
Total Calls: 2
Modem Detects: 2
Good Connects: 2
results in;
Received CCP_RESET_REQUEST on port S44 of 0 bytes containing:
0e ec 00 04
Received CCP_RESET_REQUEST on port S44 of 0 bytes containing:
0e ed 00 04
Received CCP_RESET_REQUEST on port S44 of 0 bytes containing:
0e ee 00 04
Received CCP_RESET_REQUEST on port S44 of 0 bytes containing:
0e ef 00 04
Received CCP_RESET_REQUEST on port S44 of 0 bytes containing:
0e f0 00 04
Received CCP_RESET_REQUEST on port S44 of 0 bytes containing:
0e f1 00 04
just pounding out, about 5 times a second on the console during a set deb
0x51 session. The most obvious thing is the funky DIRECT protocol, and we're
going to call him and see what we can do, but I'm still curious about the
lack of response from the PM-3 to the request(or is it their modem that
refuses to acknowledge the request?).
Plus, it's ugly looking via the console. ;)
PM-3, 2 T-1, B8ZS ESF, ComOS 3.8.2c2, and the STAC card.
Thanks,
David Glynn
dglynn@mathware.com
-
To unsubscribe, email 'majordomo@livingston.com' with
'unsubscribe portmaster-users' in the body of the message.
Searchable list archive: <URL:http://www.livingston.com/Tech/archive/>