[j-nsp] ppp problem between j2300 & Telindus 1030
Stacy W. Smith
stacy at acm.org
Tue May 17 13:38:55 EDT 2005
Looks like the Telindus converter is sending IPCP configuration options
0x81-0x84 (decimal 129-132) that the J2300 refuses to accept.
http://www.iana.org/assignments/ppp-numbers
129 Primary DNS Server Address [RFC1877]
130 Primary NBNS Server Address [RFC1877]
131 Secondary DNS Server Address [RFC1877]
132 Secondary NBNS Server Address [RFC1877]
--Stacy
On 17 May 2005, at 00:48, Le Hai Dang wrote:
> Hi all,
>
> I have problem with ppp connection between j2300 & Telindus 1030
> routers. NCP is not up & stops at inet "Conf-req-sent".
>
> j2300 ---v35----- Telindus_converter -----e1------- Telindus 1030.
>
> Just have a simple config on j2300:
> ==================================
> root> show configuration interfaces se-0/0/2
> encapsulation ppp;
> serial-options {
> clock-rate 2.0mhz;
> }
> unit 0 {
> family inet {
> address 192.168.3.1/30;
> }
> }
>
> Physical link & LCP is up:
> ==============================================
> root> show interfaces se-0/0/2 extensive
> Physical interface: se-0/0/2, Enabled, Physical link is Up
> Interface index: 139, SNMP ifIndex: 37, Generation: 20
> Type: Serial, Link-level type: PPP, MTU: 1504, Maximum speed: 8mbps
> Device flags : Present Running
> Interface flags: Point-To-Point 16384
> Link flags : Keepalives
> Hold-times : Up 0 ms, Down 0 ms
> Keepalive settings: Interval 10 seconds, Up-count 1, Down-count 3
> Keepalive statistics:
> Input : 112 (last seen 00:00:00 ago)
> Output: 183 (last sent 00:00:09 ago)
> LCP state: Opened
> NCP state: inet: Conf-req-sent, inet6: Not-configured, iso:
> Not-configured, mpls:
> Not-configured
> CHAP state: Not-configured
> CoS queues : 8 supported
> Last flapped : 2005-05-17 02:54:58 UTC (00:37:11 ago)
> Statistics last cleared: Never
> Traffic statistics:
> Input bytes : 6439006 15288 bps
> Output bytes : 5595590 13272 bps
> Input packets: 170182 50 pps
> Output packets: 170232 50 pps
> Input errors:
> Errors: 3, Drops: 0, Framing errors: 5, Runts: 0, Giants: 3,
> Policed discards: 0, Resource errors: 6
> Output errors:
> Carrier transitions: 3, Errors: 0, Drops: 0, MTU errors: 0,
> Resource errors: 0
> Serial media information:
> Line protocol: v.35
> Resync history:
> Sync loss count: 0
> Data signal:
> Rx Clock: OK
> Control signals:
> Local mode: DTE
> To DCE: DTR: up, RTS: up
> From DCE: CTS: up, DCD: up, DSR: up
> Clocking mode: loop-timed
> Clock rate: 2.0 MHz
> Loopback: none
> Tx clock: non-invert
> Line encoding: nrz
> Packet Forwarding Engine configuration:
> Destination slot: 0, PLP byte: 1 (0x00)
> CoS transmit queue Bandwidth Buffer
> Priority Limit
> % bps % bytes
> 0 best-effort 95 7600000 95 0
> low none
> 3 network-control 5 400000 5 0
> low none
>
> Logical interface se-0/0/2.0 (Index 66) (SNMP ifIndex 39)
> (Generation 5)
> Flags: Point-To-Point SNMP-Traps Encapsulation: PPP
> Protocol inet, MTU: 1500, Generation: 9, Route table: 0
> Flags: Protocol-Down, Is-Primary
> Addresses, Flags: Dest-route-down Is-Default Is-Preferred
> Is-Primary
> Destination: 192.168.3.0/30, Local: 192.168.3.1, Broadcast:
> 192.168.3.3,
> Generation: 15
>
> root>
>
>
> + Connecting the same e1 link from the converter to an M box shows no
> problem at all. And the point here is Telindous router works well with
> Cisco box in this case.
>
> + Traffic monitoring at serial link of j2300 shows:
>
> ========================
>
> root> monitor traffic interface se-0/0/2 extensive layer2-headers
> Listening on se-0/0/2, capture size 96 bytes
>
> 03:31:52.954149 In 38 03 IPCP: IPCP configure request (type
> 0x01 id 0x0b len 0x0022)
> IPCP OPTION: address (type 0x03 len 0x06)
> IPCP OPTION: UNKNOWN (type 0x81 len 0x06)
> IPCP OPTION: UNKNOWN (type 0x82 len 0x06)
> IPCP OPTION: UNKNOWN (type 0x83 len 0x06)
> IPCP OPTION: UNKNOWN (type 0x84 len 0x06)
> 03:31:52.954169 Out 32 03 IPCP: IPCP configure negative ack (type
> 0x03 id 0x0b len 0x001c)
> IPCP OPTION: UNKNOWN (type 0x81 len 0x06)
> IPCP OPTION: UNKNOWN (type 0x82 len 0x06)
> IPCP OPTION: UNKNOWN (type 0x83 len 0x06)
> IPCP OPTION: UNKNOWN (type 0x84 len 0x06)
> 03:31:52.964150 In 38 03 IPCP: IPCP configure request (type
> 0x01 id 0x0c len 0x0022)
> IPCP OPTION: address (type 0x03 len 0x06)
> IPCP OPTION: UNKNOWN (type 0x81 len 0x06)
> IPCP OPTION: UNKNOWN (type 0x82 len 0x06)
> IPCP OPTION: UNKNOWN (type 0x83 len 0x06)
> IPCP OPTION: UNKNOWN (type 0x84 len 0x06)
> 03:31:52.964167 Out 32 03 IPCP: IPCP configure negative ack (type
> 0x03 id 0x0c len 0x001c)
> IPCP OPTION: UNKNOWN (type 0x81 len 0x06)
> IPCP OPTION: UNKNOWN (type 0x82 len 0x06)
> IPCP OPTION: UNKNOWN (type 0x83 len 0x06^C
> 280 packets received by filter
> 0 packets dropped by kernel
>
> Any idea ?
>
> thks,
>
> Dang
>
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> http://puck.nether.net/mailman/listinfo/juniper-nsp
>
More information about the juniper-nsp
mailing list