Re: (PM) Pipeline 75 dialing into PM3/CT1 (fwd)

Dan Machesky (dan@beesky.com)
Sat, 17 Apr 1999 10:03:17 +0000

> I think there is a fundamental communications gap here. Note that the PM
> keeps receiving the SAME request, over and over. We never once recieve an
> ACK or a NAK despite all of the requests we've sent. And, we've ACK'd the
> request each time, yet the Pipeline keeps making it.
>
> It seems that the Pipeline is not seeing anything from the PM. The PM
> is seeing it - but not the other way around. If you can I'd do a debug on
> the Pipeline to see what, if anything, it is receiving back.
>
> >Received LCP_CONFIGURE_REQUEST on port S35 of 17 bytes containing:
> >Received LCP_CONFIGURE_REQUEST on port S35 of 17 bytes containing:
> >Sending LCP_CONFIGURE_REQUEST to port S35 of 18 bytes containing:
> >Sending LCP_CONFIGURE_ACK to port S35 of 21 bytes containing:

Here is a debug from the Ascend pipeline.
-------------snip--------------
WANDATA: looking for session
profile 0, name pm3, ip 198.xx.xx.xx, ether<none>, outdial
<none>
startSession pm3 newSession pm3
WANDATA-0: profile 1, 'pm3' assigned WANDATA-0: >> RouteID 0, state
INACTIVE, event OPEN_OUT_REQ WANDATA-5: attempting to place call to
'920xxxx' WANDATA-5: << RouteID 0, state CALLING
WAN-16: wanOpenOriginate(callID 16)
WANDATA: Call state change, port 8, connected 1, carrier 0
WANDATA-5: WAN state change, route 16
WANDATA-5: >> RouteID 16, state CALLING, event CALL_CONNECTED
WANDATA: EVENT IGNORED
WANDATA-5: << RouteID 16, state CALLING
WANDATA: Call state change, port 8, connected 1, carrier 1
WANDATA-5: WAN state change, route 16
WANDATA-5: >> RouteID 16, state CALLING, event CARRIER_EST
WAN-16: wanRegisterData, I/F 5
WAN-16: wanRegisterData, I/F 5, clearing stats
PPP-OUT-5 (off 0x0):(task: 250290, time: 27041.86) 29 octets @ 2C525A
[0000]: FF 03 C0 21 01 02 00 19 00 04 00 00 01 04 05 F4
[0010]: 11 04 05 F4 13 09 03 00 C0 7B 72 D2 70
WANDATA-5: << RouteID 16, state OPENING

WAN-16: Bad CRC, frame ignored
WAN-16: Bad CRC, frame ignored
** message repeated 50 times **
** OUCH!! Is this a 3.8.2 problem?

----- data lost -----
WAN-16: Bad CRC, frame ignored
----- data lost -----
** message repeated 50 times **

WAN-16: Bad CRC, frame ignored
PPP-OUT-5 (off 0x0):(task: 250290, time: 27045.77) 29 octets @ 2C791A
[0000]: FF 03 C0 21 01 02 00 19 00 04 00 00 01 04 05 F4
[0010]: 11 04 05 F4 13 09 03 00 C0 7B 72 D2 70
PPP-OUT-5 (off 0x0):(task: 250290, time: 27049.81) 29 octets @ 2C809A
[0000]: FF 03 C0 21 01 02 00 19 00 04 00 00 01 04 05 F4
[0010]: 11 04 05 F4 13 09 03 00 C0 7B 72 D2 70
PPP-OUT-5 (off 0x0):(task: 250290, time: 27053.85) 29 octets @ 2C525A
[0000]: FF 03 C0 21 01 02 00 19 00 04 00 00 01 04 05 F4
[0010]: 11 04 05 F4 13 09 03 00 C0 7B 72 D2 70
WAN-16: wanCloseSession, I/F 5; hdlc 22C398; pend 0
WANDATA: Call state change, port 8, connected 0, carrier 0
WANDATA: Unable to add call block entry, 0 setting found
WANDATA-5: WAN state change, route 16
WANDATA-5: >> RouteID 16, state OPENING, event CALL_DISCONNECTED
WANDATA-5: closing encaps for 198.88.0.66
WANDATA-5: ENCAPS state change, route 16
WANDATA-5: << RouteID 16, state DOWN
WANDATA-5: WAN state change, route 16
WANDATA-5: >> RouteID 16, state DOWN, event ENCAPS_CLOSED
WANDATA-0: << RouteID 16, state DESTROYED
--------snip-----------

I am running 3.8.2 on the PM3, and have tried everything from 5.1 to
6.1.42 on 2 p75's and 1 p130, with the same results. The configs on
the pipelines work fine when dialing into a pm2. The only difference
being that I chaged the data srv to "voice", and changed the "rem
addr" and "rem name" to reflect calling into the pm3.

Sincerely,
Dan Machesky
dan@beesky.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/>