Nilesh Khambal wrote: > Jim, > > What kind of Service PIC are you using for this purpose. Is it Link Services > PIC or Adaptive Service PIC configured in Layer-2 mode under [edit chassis]? > > You need either link services or adaptive service PIC (with L2 mode) to > create the ls- or lsq- interface. >
I found in one other PDF that suggested adding this. So, now I have this j...@x> show configuration chassis fpc 1 pic 2 adaptive-services { service-package layer-2; } mlfr-uni-nni-bundles 5; Didn't make a difference. Here is the current status of each T1 interface j...@x> 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: Test MLFR (1/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-06 21:09:54 GMT (1d 22:12 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 394) (SNMP ifIndex 429) Flags: Hardware-Down Point-To-Point SNMP-Traps Encapsulation: Multilink-FR-UNI-NNI Protocol mfr, Multilink bundle: lsq-1/2/0:0, MTU: 0 Flags: None j...@x> 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: Test MLFR (2/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-06 21:09:53 GMT (1d 22:12 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/0/0:19.0 (Index 389) (SNMP ifIndex 625) Flags: Hardware-Down Point-To-Point SNMP-Traps Encapsulation: Multilink-FR-UNI-NNI Protocol mfr, Multilink bundle: lsq-1/2/0:0, MTU: 0 Flags: None Thanks for the assistance Jim > Thanks, > Nilesh. > > > On 7/8/10 9:30 AM, "Jim Lucas" <li...@cmsws.com> wrote: > >> Equipment: >> 1 Juniper M20 running JunOS 7.5R1.12 >> 2 Cisco 2611 running 12.4.23 IOS >> Multiple T1 connections between the above devices >> >> Background: I have read the following literature. >> http://www.juniper.net/techpubs/software/junos/junos56/swconfig56-interfaces/h >> tml/interfaces-multilink-config25.html >> >> and I have downloaded all the PDFs available on the documentation site and >> read >> all the sections that talk about setting up MLFR >> >> Goal: I need to setup MLFR between the two devices listed above. At this >> point, >> I am simply trying to get the Juniper side configured so I can see the >> interfaces involved. >> >> What I have done so far: >> >> Here is an example config from the Juniper >> >> [edit] >> j...@x# show chassis fpc 1 pic 2 >> mlfr-uni-nni-bundles 5; >> >> [edit] >> j...@x# show interfaces ls-1/2/0:0 >> description "Test MLFR interface"; >> dce; >> encapsulation multilink-frame-relay-uni-nni; >> unit 16 { >> dlci 16; >> family inet { >> address 66.39.177.129/32 { >> destination 66.39.177.130; >> } >> } >> } >> unit 17 { >> dlci 17; >> family inet { >> address 10.100.100.1/32 { >> destination 10.100.100.2; >> } >> } >> } >> >> [edit] >> j...@x# show interfaces t1-1/1/0:0 >> description "Test MLFR leg (1/2)"; >> encapsulation multilink-frame-relay-uni-nni; >> unit 0 { >> family mlfr-uni-nni { >> bundle ls-1/2/0:0; >> } >> } >> >> [edit] >> j...@x# show interfaces t1-1/0/0:19 >> description "Test MLFR leg (2/2)"; >> encapsulation multilink-frame-relay-uni-nni; >> unit 0 { >> family mlfr-uni-nni { >> bundle ls-1/2/0:0; >> } >> } >> >> After issuing "commit" the first thing I notice when I exit edit mode is that >> I >> cannot see the device ls-1/2/0:0. Question: At this point, should I be able >> to >> see the status of the device? Even if nothing is connected I am guessing, >> just >> like other interfaces that are configured, I should be able to see the status >> of >> that interface. >> >> Also, I have seen two example of doing this. The first involving the >> ls-x/x/x:0 >> interface and the other using lsq-x/x/x:0. I have tried both. Didn't change >> anything. >> >> Any help would be great! >> >> TIA > -- Jim Lucas A: Maybe because some people are too annoyed by top-posting. Q: Why do I not get an answer to my question(s)? A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp