[j-nsp] Frame-relay encapsulation across lt interfaces. still works (trio vs dpcr)?

Doug Hanks dhanks at juniper.net
Wed Jun 22 18:50:28 EDT 2011


You need to be on 11.1 for this feature on MX Trio.

root at P-network> show version
Hostname: P-network
Model: mx80-48t
JUNOS Base OS boot [11.1R2.3]
JUNOS Base OS Software Suite [11.1R2.3]
JUNOS Kernel Software Suite [11.1R2.3]
JUNOS Crypto Software Suite [11.1R2.3]
JUNOS Packet Forwarding Engine Support (MX80) [11.1R2.3]
JUNOS Online Documentation [11.1R2.3]
JUNOS Routing Software Suite [11.1R2.3]

root at P-network> show configuration logical-systems R1 interfaces lt-0/0/10 unit 0 {
    encapsulation frame-relay;
    dlci 100;
    peer-unit 1;
    family inet {
        address 1.1.1.1/30;
    }
    family inet6 {
        address 2006::1/64;
    }
}

root at P-network> show configuration logical-systems R2 interfaces lt-0/0/10 unit 1 {
    encapsulation frame-relay;
    dlci 100;
    peer-unit 0;
    family inet {
        address 1.1.1.2/30;
    }
    family inet6 {
        address 2006::2/64;
    }
}

root at P-network> ping 1.1.1.2 logical-system R1 PING 1.1.1.2 (1.1.1.2): 56 data bytes
64 bytes from 1.1.1.2: icmp_seq=0 ttl=64 time=0.388 ms
64 bytes from 1.1.1.2: icmp_seq=1 ttl=64 time=0.325 ms
64 bytes from 1.1.1.2: icmp_seq=2 ttl=64 time=0.337 ms ^C
--- 1.1.1.2 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss round-trip min/avg/max/stddev = 0.325/0.350/0.388/0.027 ms

root at P-network> ping 2006::2 logical-system R1
PING6(56=40+8+8 bytes) 2006::1 --> 2006::2
16 bytes from 2006::2, icmp_seq=0 hlim=64 time=0.452 ms
16 bytes from 2006::2, icmp_seq=1 hlim=64 time=0.332 ms
16 bytes from 2006::2, icmp_seq=2 hlim=64 time=0.386 ms
16 bytes from 2006::2, icmp_seq=3 hlim=64 time=0.379 ms ^C
--- 2006::2 ping6 statistics ---
4 packets transmitted, 4 packets received, 0% packet loss round-trip min/avg/max/std-dev = 0.332/0.387/0.452/0.043 ms

root at P-network>

Thank you,

....................................
Doug Hanks
Systems Engineer
JNCIP-M/T #1441



-----Original Message-----
From: juniper-nsp-bounces at puck.nether.net [mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of Joel Jaeggli
Sent: Wednesday, June 22, 2011 11:57 AM
To: juniper-nsp at puck.nether.net
Subject: [j-nsp] Frame-relay encapsulation across lt interfaces. still works (trio vs dpcr)?

I was previously using frame-relay encapsulation to carry ipv6 traffic across logical tunnel interfaces in an MX.

I was doing it again recently and it doesn't seem to work on trio, either that or my memory is foggy.

if someone has a better way to carry ipv6 across an lt-interface these days, I'm all ears.

this is related to this discussion some time ago:

http://www.gossamer-threads.com/lists/nsp/juniper/23524

so here's a frame relay lt interface on a 40x1Gbe dpc

root at svo-e2-mx480-re0# run show interfaces lt-4/3/10 
Physical interface: lt-4/3/10, Enabled, Physical link is Up
 Interface index: 282, SNMP ifIndex: 689
 Type: Logical-tunnel, Link-level type: Logical-tunnel, MTU: Unlimited,
 Speed: 1000mbps
 Device flags   : Present Running
 Interface flags: Point-To-Point SNMP-Traps
 Link flags     : None
 Physical info  : 13
 Current address: 80:71:1f:94:8e:28, Hardware address: 80:71:1f:94:8e:28
 Last flapped   : 2011-05-08 21:48:35 UTC (6w2d 20:58 ago)
 Input rate     : 0 bps (0 pps)
 Output rate    : 0 bps (0 pps)

 Logical interface lt-4/3/10.0 (Index 70) (SNMP ifIndex 0) 
   Flags: Point-To-Point SNMP-Traps 0x4000 DLCI 1 Encapsulation: FR-NLPID
   Input packets : 0 
   Output packets: 0
   Protocol inet, MTU: 4470
     Flags: Sendbcast-pkt-to-re
     Addresses, Flags: Is-Preferred Is-Primary
       Destination: 172.19.0.252/31, Local: 172.19.0.252

 Logical interface lt-4/3/10.1 (Index 82) (SNMP ifIndex 0) 
   Flags: Point-To-Point SNMP-Traps 0x4000 DLCI 1 Encapsulation: FR-NLPID
   Input packets : 0 
   Output packets: 0
   Protocol inet, MTU: 4470
     Flags: Sendbcast-pkt-to-re
     Addresses, Flags: Is-Preferred Is-Primary
       Destination: 172.19.0.252/31, Local: 172.19.0.253

root at svo-e2-mx480-re0# run ping 172.19.0.252 
PING 172.19.0.252 (172.19.0.252): 56 data bytes
64 bytes from 172.19.0.252: icmp_seq=0 ttl=64 time=0.069 ms
64 bytes from 172.19.0.252: icmp_seq=1 ttl=64 time=0.039 ms
^C
--- 172.19.0.252 ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.039/0.054/0.069/0.015 ms

{master}[edit]
root at svo-e2-mx480-re0# run ping 172.19.0.253    
PING 172.19.0.253 (172.19.0.253): 56 data bytes
64 bytes from 172.19.0.253: icmp_seq=0 ttl=64 time=0.353 ms
64 bytes from 172.19.0.253: icmp_seq=1 ttl=64 time=0.295 ms
64 bytes from 172.19.0.253: icmp_seq=2 ttl=64 time=0.303 ms

here it is on trio:

root at svo-e2-mx480-re0# run show interfaces lt-1/3/0 
Physical interface: lt-1/3/0, Enabled, Physical link is Up
  Interface index: 290, SNMP ifIndex: 699
  Type: Logical-tunnel, Link-level type: Logical-tunnel, MTU: Unlimited,
  Speed: 10000mbps
  Device flags   : Present Running
  Interface flags: Point-To-Point SNMP-Traps
  Link flags     : None
  Physical info  : 13
  Current address: 80:71:1f:94:8a:40, Hardware address: 80:71:1f:94:8a:40
  Last flapped   : 2011-06-22 19:00:22 UTC (00:00:33 ago)
  Input rate     : 0 bps (0 pps)
  Output rate    : 0 bps (0 pps)

  Logical interface lt-1/3/0.0 (Index 83) (SNMP ifIndex 701) 
    Flags: Point-To-Point SNMP-Traps 0x4000 DLCI 2 Encapsulation: FR-NLPID
    Input packets : 0 
    Output packets: 0
    Protocol inet, MTU: 4470
      Flags: Sendbcast-pkt-to-re
      Addresses, Flags: Is-Preferred Is-Primary
        Destination: 172.19.0.250/31, Local: 172.19.0.250

  Logical interface lt-1/3/0.1 (Index 84) (SNMP ifIndex 702) 
    Flags: Point-To-Point SNMP-Traps 0x4000 DLCI 2 Encapsulation: FR-NLPID
    Input packets : 0 
    Output packets: 0
    Protocol inet, MTU: 4470
      Flags: Sendbcast-pkt-to-re
      Addresses, Flags: Is-Preferred Is-Primary
        Destination: 172.19.0.250/31, Local: 172.19.0.251

root at svo-e2-mx480-re0# run ping 172.19.0.250  
PING 172.19.0.250 (172.19.0.250): 56 data bytes
64 bytes from 172.19.0.250: icmp_seq=0 ttl=64 time=0.068 ms
64 bytes from 172.19.0.250: icmp_seq=1 ttl=64 time=1.052 ms
64 bytes from 172.19.0.250: icmp_seq=2 ttl=64 time=0.040 ms
^C
--- 172.19.0.250 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.040/0.387/1.052/0.471 ms

{master}[edit]
root at svo-e2-mx480-re0# run ping 172.19.0.251    
PING 172.19.0.251 (172.19.0.251): 56 data bytes
 ^C
--- 172.19.0.251 ping statistics ---
363 packets transmitted, 0 packets received, 100% packet loss


root at svo-e2-mx480-re0# show logical-systems R2-RR interfaces 
lt-1/3/0 {
    unit 1 {
        encapsulation frame-relay;
        dlci 2;
        peer-unit 0;
        family inet {
            address 172.19.0.251/31;
        }
    }
}

lt-4/3/10 {
    unit 1 {
        encapsulation frame-relay;
        dlci 1;
        peer-unit 0;
        family inet {
            address 172.19.0.253/31;    
        }
    }
}

_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp



More information about the juniper-nsp mailing list