Re: (PM) Strange Frame Realy Connectivity Problem

Mike Sherman (msherman@svwh.net)
Mon, 01 Mar 1999 08:47:46 -0800

> That makes no sense. The only reason a switch should discard packets is
> if 1) incorrect DLCI, 2) CRC failure or 3) marked DE and congestion is
> present.
>
> You need a protocol analyzer on here to figure out why the packets are
> being discarded. There was a problem with the WAN card in the PM3 where
> it would send all frame relay data on an invalid DLCI, and the switch
> would discard accordingly. Though I've never seen this in the IRX or
> 2eR series. Is link management up? If it is, this would indicate the
> link management packets are making it through, but the data DLCI
> packets are not.

PacBell is going to _try_ and get a protocol analyzer out there today.
God knows if they'll make it.

Link management is up. We're using Annex-D with 10 second intervals.
Using debug 0x51 we see that the DLCI information is being passed along
-- the PM learns that it's using DLCI 16. What concerns me now is the
output from a "show arp frmW1":

show arp frmW1
0.0.0.0 at 04:01 (16)

That would not seem to be quite right to me... it shows the address at
the other end of the link as 0.0.0.0. We've done a lot of configuration
changes this last day, but restoring the configuration to the exact way
it was before we had trouble still show the address as 0.0.0.0.

The current status of the Frame port is thus:

--------------------- Current Status - Port W1 -------------------------
Status: ESTABLISHED
Input: 5184090 Abort Errors: 5747
Output: 12100374 CRC Errors: 4162
Pending: 0 Overrun Errors: 0
TX Errors: 2 Frame Errors: 0/3
Modem Status: DCD+ CTS+

Active Configuration Default Configuration
-------------------- ---------------------
Port Type: Netwrk Netwrk (Hardwired)
Line Speed: Ext 1536K Ext Clock
Modem Control: on on
Local Address: 10.0.2.2 10.0.2.2
Netmask: 255.255.255.0 255.255.255.0
Interface: frmW1 (FRM,Quiet) (FRM,Quiet)
Mtu: 1500 0
Pkt Filters: In:consoles Out:
Dial Group: 0
Annex-D Poll: 10 (seconds)
Old DLCI List:

With the configuration as it is now, the address of the router at the
other end is 10.0.2.1. As I said, packets are making it one direction
-- from Palo Alto to San Jose. This is still the case. They're just
getting discarded the other direction.

At this point PacBell is suggestion that both my Livingston routers are
bad and they both have the exact same problem. I don't quite by that
though...

> Alos the router polls the switch, not the other way around. The switch
> should be set to allow you 15 seconds to get your poll in. The router
> should be set to 10 seconds. These are configurable, so double check.

Checked and double checked. As I said, it is getting the DLCI info, but
that address the "show arp frmW1" shows me is not sitting quite right
with me.

> Be smart when troubleshooting, don't just throw crap at the wall and
> see what sticks.

lol, I like this!

Mike
msherman@svwh.net
-
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/>