[c-nsp] Juniper M20 to Cisco 2600 Multilink Frame Relay & FRF.16 issues
Jim Lucas
lists at cmsws.com
Mon Aug 23 14:09:48 EDT 2010
> Does it work with normal frame relay encapsulation.
Yes
> What are your DLCI statuses on the cisco?
Currently, they are in-active
> Also doesn't the IETF on the end of the frame relay dlci command change the lmi
> type for that DLCI? Is this intended?
Didn't catch that one. I removed the IETF from that line. Didn't seem to make
a difference.
Router#show interfaces summary
Interface IHQ IQD OHQ OQD RXBS RXPS TXBS TXPS TRTL
------------------------------------------------------------------------
Ethernet0/0 0 0 0 0 0 0 0 0 0
Serial0/0 0 0 0 0 0 0 0 0 0
Ethernet0/1 0 0 0 0 0 0 0 0 0
Serial0/1 0 0 0 0 0 0 0 0 0
Serial1/0 0 0 0 0 0 0 0 0 0
Serial1/1 0 0 0 0 0 0 0 0 0
MFR0 0 11 0 0 0 0 0 0 0
MFR0.16 - - - - - - - - -
Virtual-Access1 0 0 0 0 0 0 0 0 0
Thank you for your time spent on this issue!
Jim
>
> On Mon, Aug 23, 2010 at 1:22 PM, Jim Lucas <lists at cmsws.com> wrote:
>
>> Keegan,
>>
>> > I haven't looked at MLFR in a long time, but it looks like both sides are
>> > trying to be DCE. That may be a problem.
>>
>> Sorry, that was leftover from a previous config test. I have it running
>> without
>> the "frame-relay intf-type dce" on the Cisco. The Juniper side is DCE and
>> the
>> Cisco is not specified. My assumption has been that the default for Cisco
>> is
>> DTE.
>>
>> > Are they setup back to back or is there an actual frame network in the
>> middle?
>>
>> A network. They are in different buildings with a MUX or two between them.
>>
>> If I setup the connection with normal MLPPP it works and standard T1 setups
>> work
>> just fine. It shows a hardware level connection, but the protocol is down.
>> This makes me think it has something to do with my config and probably not
>> anything involving the equipment between the devices.
>>
>> Thanks!
>>
>> Jim
>>
>> >
>> >
>> >
>> > On Mon, Aug 23, 2010 at 12:06 PM, Jim Lucas <lists at cmsws.com> wrote:
>> >
>> >> Note: I initially sent this to the Juniper-NSP list. I was told by
>> Nilesh
>> >> Khambal (Juniper Engineer) that I have setup the Juniper side correctly.
>> >> So,
>> >> I'm hoping someone here might have a little more information on the
>> Cisco
>> >> side
>> >> of it all.
>> >>
>> >> TIA!
>> >>
>> >> First off, sorry for such a long email. But I figured I would give as
>> much
>> >> information as possible upfront to try and give a clear picture about
>> what
>> >> I
>> >> have and what I am currently running.
>> >>
>> >> Central Office Equipment:
>> >> Juniper M20 running v7.5R1.12
>> >> 1x Link Services module (ls-3/0/0)
>> >>
>> >> Customer Equipment:
>> >> Cisco 2611 running c2600-ipbase-mz.124-23
>> >> 2x Eth (e0/0, e0/1)
>> >> 4x T1 wic (s0/0, s0/1, s1/0, s1/1)
>> >>
>> >> The following is the important parts of the config of the Cisco router
>> >>
>> >> interface MFR0
>> >> description my interface
>> >> no ip address
>> >> frame-relay lmi-type ansi
>> >> frame-relay intf-type dce
>> >>
>> >> interface MFR0.16 point-to-point
>> >> ip address 66.39.177.130 255.255.255.252
>> >> no cdp enable
>> >> frame-relay interface-dlci 16 IETF
>> >>
>> >> interface Ethernet0/0
>> >> ip address 66.39.177.133 255.255.255.252
>> >> half-duplex
>> >>
>> >> interface Serial0/0
>> >> no ip address
>> >> encapsulation frame-relay MFR0
>> >> no arp frame-relay
>> >>
>> >> interface Serial0/1
>> >> no ip address
>> >> encapsulation frame-relay MFR0
>> >> no arp frame-relay
>> >>
>> >>
>> >> Here is my Juniper config:
>> >>
>> >> > show configuration chassis fpc 3 pic 0
>> >> mlfr-uni-nni-bundles 32;
>> >>
>> >> > show configuration interfaces t1-1/1/0:0
>> >> description "Bendtel Test leg #1";
>> >> encapsulation multilink-frame-relay-uni-nni;
>> >> lmi {
>> >> lmi-type ansi;
>> >> }
>> >> unit 0 {
>> >> family mlfr-uni-nni {
>> >> bundle ls-3/0/0:0;
>> >> }
>> >> }
>> >>
>> >> > show configuration interfaces t1-1/0/0:19
>> >> description "Bendtel Test leg #2";
>> >> encapsulation multilink-frame-relay-uni-nni;
>> >> lmi {
>> >> lmi-type ansi;
>> >> }
>> >> unit 0 {
>> >> family mlfr-uni-nni {
>> >> bundle ls-3/0/0:0;
>> >> }
>> >> }
>> >>
>> >> > show configuration interfaces ls-3/0/0:0
>> >> dce;
>> >> encapsulation multilink-frame-relay-uni-nni;
>> >> unit 16 {
>> >> dlci 16;
>> >> family inet {
>> >> address 66.39.177.129/30;
>> >> }
>> >> }
>> >> unit 17 {
>> >> dlci 17;
>> >> family inet {
>> >> address 10.100.100.1/30;
>> >> }
>> >> }
>> >>
>> >> Here is the current status of all these interfaces
>> >>
>> >> > show interfaces ls-3/0/0:0
>> >> Physical interface: ls-3/0/0:0, Enabled, Physical link is Down
>> >> Interface index: 349, SNMP ifIndex: 953
>> >> Link-level type: Multilink-FR-UNI-NNI, MTU: 1508
>> >> Device flags : Present Running
>> >> Interface flags: Hardware-Down Link-Layer-Down Point-To-Point
>> SNMP-Traps
>> >> Last flapped : 2010-08-13 19:39:56 GMT (6d 20:20 ago)
>> >> Multilink Frame Relay UNI NNI bundle options:
>> >> Device type DCE
>> >> MRRU 1508
>> >> Fragmentation threshold 0
>> >> Red differential delay limit 10
>> >> Yellow differential delay limit 6
>> >> Red differential delay action Remove link
>> >> Reassembly drop timer 0
>> >> Links needed to sustain bundle 1
>> >> LIP Hello timer 10
>> >> Acknowledgement timer 4
>> >> Acknowledgement retries 2
>> >> Bundle class A
>> >> LMI type ANSI
>> >> T391 LIV polling timer 10
>> >> T392 polling verification timer 15
>> >> N391 full status polling count 6
>> >> N392 error threshold 3
>> >> N393 monitored event count 4
>> >> Input rate : 0 bps (0 pps)
>> >> Output rate : 0 bps (0 pps)
>> >> Multilink Frame Relay UNI NNI bundle statistics:
>> >> Frames fps Bytes bps
>> >>
>> >> Fragments:
>> >> Input : 0 0 0 0
>> >> Output: 0 0 0 0
>> >> Packets:
>> >> Input : 0 0 0 0
>> >> Output: 0 0 0 0
>> >> Multilink Frame Relay UNI NNI bundle links information:
>> >> Active bundle links 0
>> >> Removed bundle links 2
>> >> Disabled bundle links 0
>> >> Multilink Frame Relay UNI NNI active bundle links statistics:
>> >> Frames fps Bytes bps
>> >> t1-1/0/0:19.0 <-- down
>> >> Input : 0 0 0 0
>> >> Output: 0 0 0 0
>> >> Current differential delay 0.0 ms
>> >> Recent high differential delay 0.0 ms
>> >> Times over red diff delay 0
>> >> Times over yellow diff delay 0
>> >> LIP:add_lnk lnk_ack lnk_rej hello hel_ack lnk_rem rem_ack
>> >> Rcv: 0 0 0 0 0 0 0
>> >> Xmt: 15 0 0 0 0 0 0
>> >> t1-1/1/0:0.0 <-- down
>> >> Input : 0 0 0 0
>> >> Output: 0 0 0 0
>> >> Current differential delay 0.0 ms
>> >> Recent high differential delay 0.0 ms
>> >> Times over red diff delay 0
>> >> Times over yellow diff delay 0
>> >> LIP:add_lnk lnk_ack lnk_rej hello hel_ack lnk_rem rem_ack
>> >> Rcv: 0 0 0 0 0 0 0
>> >> Xmt: 197 0 0 0 0 0 0
>> >>
>> >> Logical interface ls-3/0/0:0.16 (Index 230) (SNMP ifIndex 954)
>> >> Flags: Device-Down Point-To-Point SNMP-Traps Encapsulation:
>> >> Multilink-FR-UNI-NNI
>> >> Statistics Frames fps Bytes bps
>> >> Bundle:
>> >> Fragments:
>> >> Input : 0 0 0 0
>> >> Output: 0 0 0 0
>> >> Packets:
>> >> Input : 0 0 0 0
>> >> Output: 0 0 0 0
>> >> Protocol inet, MTU: 1500
>> >> Flags: None
>> >> Addresses, Flags: Dest-route-down Is-Preferred Is-Primary
>> >> Destination: 66.39.177.128/30, Local: 66.39.177.129
>> >>
>> >> Logical interface ls-3/0/0:0.17 (Index 305) (SNMP ifIndex 955)
>> >> Flags: Device-Down Point-To-Point SNMP-Traps Encapsulation:
>> >> Multilink-FR-UNI-NNI
>> >> Bandwidth: 625152kbps
>> >> Statistics Frames fps Bytes bps
>> >> Bundle:
>> >> Fragments:
>> >> Input : 0 0 0 0
>> >> Output: 0 0 0 0
>> >> Packets:
>> >> Input : 0 0 0 0
>> >> Output: 0 0 0 0
>> >> Protocol inet, MTU: 1500
>> >> Flags: None
>> >> Addresses, Flags: Dest-route-down Is-Preferred Is-Primary
>> >> Destination: 10.100.100.0/30, Local: 10.100.100.1
>> >>
>> >>
>> >> > show interfaces t1-1/1/0:0
>> >> Physical interface: t1-1/1/0:0, Enabled, Physical link is Up
>> >> Interface index: 444, SNMP ifIndex: 310
>> >> Description: Bendtel Test leg #1
>> >> Link-level type: Multilink-FR-UNI-NNI, MTU: 1518, Clocking: Internal,
>> >> Speed:
>> >> T1, Loopback: None, FCS: 16, Mode: C/Bit parity,
>> >> Framing: ESF
>> >> Device flags : Present Running
>> >> Interface flags: Point-To-Point SNMP-Traps Internal: 0x4000
>> >> Link flags : None
>> >> CoS queues : 4 supported, 4 in use
>> >> Last flapped : 2010-08-19 18:42:37 GMT (21:24:58 ago)
>> >> Input rate : 0 bps (0 pps)
>> >> Output rate : 0 bps (0 pps)
>> >> DS1 alarms : None
>> >> DS3 alarms : None
>> >> DS1 defects : None
>> >> DS3 defects : None
>> >>
>> >> Logical interface t1-1/1/0:0.0 (Index 214) (SNMP ifIndex 429)
>> >> Flags: Hardware-Down Point-To-Point SNMP-Traps Encapsulation:
>> >> Multilink-FR-UNI-NNI
>> >> Protocol mfr, Multilink bundle: ls-3/0/0:0, MTU: 0
>> >> Flags: None
>> >>
>> >> > show interfaces t1-1/0/0:19
>> >> Physical interface: t1-1/0/0:19, Enabled, Physical link is Up
>> >> Interface index: 501, SNMP ifIndex: 211
>> >> Description: Bendtel Test leg #2
>> >> Link-level type: Multilink-FR-UNI-NNI, MTU: 1518, Clocking: Internal,
>> >> Speed:
>> >> T1, Loopback: None, FCS: 16, Mode: C/Bit parity,
>> >> Framing: ESF
>> >> Device flags : Present Running
>> >> Interface flags: Point-To-Point SNMP-Traps Internal: 0x4000
>> >> Link flags : None
>> >> CoS queues : 4 supported, 4 in use
>> >> Last flapped : 2010-07-09 18:35:02 GMT (5w6d 21:32 ago)
>> >> Input rate : 0 bps (0 pps)
>> >> Output rate : 24 bps (0 pps)
>> >> DS1 alarms : None
>> >> DS3 alarms : None
>> >> DS1 defects : None
>> >> DS3 defects : None
>> >>
>> >> Logical interface t1-1/0/0:19.0 (Index 91) (SNMP ifIndex 625)
>> >> Flags: Hardware-Down Point-To-Point SNMP-Traps Encapsulation:
>> >> Multilink-FR-UNI-NNI
>> >> Protocol mfr, Multilink bundle: ls-3/0/0:0, MTU: 0
>> >> Flags: None
>> >>
>> >>
>> >> Here is the show chassis
>> >>
>> >> jim at b1-bend-re0> show chassis hardware
>> >> Hardware inventory:
>> >> Item Version Part number Serial number Description
>> >> Chassis 20934 M20
>> >> ...
>> >> FPC 3 REV 01 710-001292 AE7635 FPC
>> >> PIC 0 REV 01 750-007924 HM0123 1x Link
>> Service(32)
>> >> ...
>> >>
>> >>
>> >> For both t1s you can see that they show connected, but for some reason
>> >> (that
>> >> escapes me) the ls interface shows "Hardware-Down" Does this mean the
>> Link
>> >> services module is not turned up? To me it isn't clear.
>> >>
>> >> Any help would be great!
>> >>
>> >> Thanks
>> >>
>> >> --
>> >> Jim Lucas
>> >>
>> >>
>> >> _______________________________________________
>> >> cisco-nsp mailing list cisco-nsp at puck.nether.net
>> >> https://puck.nether.net/mailman/listinfo/cisco-nsp
>> >> archive at http://puck.nether.net/pipermail/cisco-nsp/
>> >>
>> >>
>> >>
>> >
>>
>>
>> --
>> Jim Lucas
>>
>>
>>
>>
>>
>
--
Jim Lucas
More information about the cisco-nsp
mailing list