Jump to content

Увидеть P-роутер в клиентской трассировке. Juniper l3vpn

2_alex
 Share

Recommended Posts

2_alex

2_alex

Posted
Posted

Схему прилагаю. Делаю traceroute с CE-A или с R1, не вижу P-роутера в трассировке, вместо него звёздочки(A7=CE-A, B8=CE-B):

 

# run traceroute 192.168.11.2 source 192.168.11.1 logical-system A7    
traceroute to 192.168.11.2 (192.168.11.2) from 192.168.11.1, 30 hops max, 40 byte packets
1  10.0.10.1 (10.0.10.1)  0.334 ms  0.337 ms  0.324 ms
2  * * *
3  172.22.212.1 (172.22.212.1)  0.616 ms  0.413 ms  0.423 ms
    MPLS Label=299888 CoS=0 TTL=1 S=1
4  192.168.11.2 (192.168.11.2)  0.548 ms  0.533 ms  0.538 ms

 

# run traceroute 192.168.11.2 routing-instance vpn-a logical-system R1  
traceroute to 192.168.11.2 (192.168.11.2), 30 hops max, 40 byte packets
1  * * *
2  172.22.212.1 (172.22.212.1)  0.611 ms  0.447 ms  0.413 ms
    MPLS Label=299888 CoS=0 TTL=1 S=1
3  192.168.11.2 (192.168.11.2)  0.545 ms  0.547 ms  0.541 ms

 

Помогите сделать так, чтобы P-роутер(R2) появился в трассировке.

 

Конфиги:

A7 {
   interfaces {
       lt-1/2/0 {
           unit 71 {
               encapsulation ethernet;
               peer-unit 17;
               family inet {
                   address 10.0.10.2/24;
               }
           }
       }
       lo0 {
           unit 7 {
               family inet {
                   address 192.168.11.1/32;
               }
           }
       }
   }
   protocols {
       bgp {
           group ext {
               export exp-lo;
               neighbor 10.0.10.1 {
                   peer-as 65512;
               }
           }
       }
   }
   policy-options {                    
       policy-statement exp-lo {
           from {
               route-filter 192.168.11.1/32 exact accept;
           }
       }
   }
   routing-options {
       autonomous-system 65101;
   }
}


B8 {
   interfaces {
       lt-1/2/0 {
           unit 83 {
               encapsulation ethernet;
               peer-unit 38;
               family inet {
                   address 10.0.11.2/24;
               }
           }
       }
       lo0 {
           unit 8 {
               family inet {
                   address 192.168.11.2/32;
               }
           }
       }
   }                                   
   protocols {
       bgp {
           inactive: traceoptions {
               file bgp-debug.log;
               flag all detail;
           }
           group ext {
               export exp-lo;
               neighbor 10.0.11.1 {
                   peer-as 65512;
               }
           }
       }
   }
   policy-options {
       policy-statement exp-lo {
           from {
               route-filter 192.168.11.2/32 exact accept;
           }
       }
   }
   routing-options {
       autonomous-system 65101 loops 2;
   }
}


R1 {
   interfaces {
       lt-1/2/0 {
           unit 12 {                   
               encapsulation ethernet;
               peer-unit 21;
               family inet {
                   address 172.22.210.1/24;
               }
               family mpls;
           }
           unit 17 {
               encapsulation ethernet;
               peer-unit 71;
               family inet {
                   address 10.0.10.1/24;
               }
           }
       }
       lo0 {
           unit 1 {
               family inet {
                   address 192.168.1.1/32;
               }
           }
       }
   }
   protocols {
       rsvp {
           interface lt-1/2/0.12;
       }
       mpls {
           no-cspf;                    
           label-switched-path to-R3 {
               to 192.168.1.3;
           }
           interface lt-1/2/0.12;
       }
       bgp {
           group int {
               type internal;
               local-address 192.168.1.1;
               family inet {
                   unicast;
               }
               family inet-vpn {
                   unicast;
               }
               export nh-self;
               remove-private;
               neighbor 192.168.1.3;
           }
       }
       ospf {
           area 0.0.0.0 {
               interface lo0.1 {
                   passive;
               }
               interface lt-1/2/0.12 {
                   interface-type p2p;
               }
           }                           
       }
   }
   policy-options {
       policy-statement nh-self {
           then {
               next-hop self;
           }
       }
   }
   routing-instances {
       vpn-a {
           instance-type vrf;
           interface lt-1/2/0.17;
           route-distinguisher 192.168.1.1:1;
           vrf-target target:65512:101;
           protocols {
               bgp {
                   group ext {
                       remove-private;
                       neighbor 10.0.10.2 {
                           peer-as 65101;
                       }
                   }
               }
           }
       }
   }
   routing-options {
       autonomous-system 65512;        
   }
}


R2 {
   interfaces {
       lt-1/2/0 {
           unit 21 {
               encapsulation ethernet;
               peer-unit 12;
               family inet {
                   address 172.22.210.2/24;
               }
               family mpls;
           }
           unit 23 {
               encapsulation ethernet;
               peer-unit 32;
               family inet {
                   address 172.22.212.2/24;
               }
               family mpls;
           }
       }
       lo0 {
           unit 2 {
               family inet {
                   address 192.168.1.2/32;
               }
           }
       }                               
   }
   protocols {
       rsvp {
           interface lt-1/2/0.21;
           interface lt-1/2/0.23;
       }
       mpls {
           interface lt-1/2/0.21;
           interface lt-1/2/0.23;
       }
       ospf {
           area 0.0.0.0 {
               interface lo0.2 {
                   passive;
               }
               interface lt-1/2/0.21 {
                   interface-type p2p;
               }
               interface lt-1/2/0.23 {
                   interface-type p2p;
               }
           }
       }
   }
}


R3 {
   interfaces {
       lt-1/2/0 {
           unit 32 {                   
               encapsulation ethernet;
               peer-unit 23;
               family inet {
                   address 172.22.212.1/24;
               }
               family mpls;
           }
           unit 38 {
               encapsulation ethernet;
               peer-unit 83;
               family inet {
                   address 10.0.11.1/24;
               }
           }
       }
       lo0 {
           unit 3 {
               family inet {
                   address 192.168.1.3/32;
               }
           }
       }
   }
   protocols {
       rsvp {
           interface lt-1/2/0.32;
       }
       mpls {
           no-cspf;                    
           label-switched-path to-R1 {
               to 192.168.1.1;
           }
           interface lt-1/2/0.32;
       }
       bgp {
           group int {
               type internal;
               local-address 192.168.1.3;
               family inet {
                   unicast;
               }
               family inet-vpn {
                   unicast;
               }
               export nh-self;
               remove-private;
               neighbor 192.168.1.1;
           }
       }
       ospf {
           area 0.0.0.0 {
               interface lo0.3 {
                   passive;
               }
               interface lt-1/2/0.32 {
                   interface-type p2p;
               }
           }                           
       }
   }
   policy-options {
       policy-statement nh-self {
           then {
               next-hop self;
           }
       }
   }
   routing-instances {
       vpn-a {
           instance-type vrf;
           interface lt-1/2/0.38;
           route-distinguisher 192.168.1.2:1;
           vrf-target target:65512:101;
           protocols {
               bgp {
                   group ext {
                       remove-private;
                       neighbor 10.0.11.2 {
                           peer-as 65101;
                       }
                   }
               }
           }
       }
   }
   routing-options {
       autonomous-system 65512;        
   }
}

 

Заранее спасибо!

 

Не загрузилась схема. http://img13.imageshack.us/img13/1219/8j41.png

8j41.png

2_alex

2_alex

Posted
  • Author
Posted

icmp-tunneling ?

Да. Работает с ним! Спасибо.

 

[edit logical-systems]
# set R1 protocols mpls icmp-tunneling 
# set R2 protocols mpls icmp-tunneling    
# set R3 protocols mpls icmp-tunneling
# commit

 

 

# run traceroute 192.168.11.2 source 192.168.11.1 logical-system A7       
traceroute to 192.168.11.2 (192.168.11.2) from 192.168.11.1, 30 hops max, 40 byte packets
1  10.0.10.1 (10.0.10.1)  0.472 ms  0.345 ms  0.348 ms
2  172.22.210.2 (172.22.210.2)  0.543 ms  0.419 ms  0.437 ms
    MPLS Label=299792 CoS=0 TTL=1 S=0
    MPLS Label=299888 CoS=0 TTL=1 S=1
3  172.22.212.1 (172.22.212.1)  0.557 ms  0.409 ms  0.420 ms
    MPLS Label=299888 CoS=0 TTL=1 S=1
4  192.168.11.2 (192.168.11.2)  0.408 ms  0.540 ms  0.535 ms

 

# run traceroute 192.168.11.2 routing-instance vpn-a logical-system R1    
traceroute to 192.168.11.2 (192.168.11.2), 30 hops max, 40 byte packets
1  172.22.210.2 (172.22.210.2)  0.674 ms  0.461 ms  0.449 ms
    MPLS Label=299792 CoS=0 TTL=1 S=0
    MPLS Label=299888 CoS=0 TTL=1 S=1
2  172.22.212.1 (172.22.212.1)  0.566 ms  0.422 ms  0.413 ms
    MPLS Label=299888 CoS=0 TTL=1 S=1
3  192.168.11.2 (192.168.11.2)  0.537 ms  0.544 ms  0.539 ms

  • 1 year later...
rdntw

rdntw

Posted
Posted

апну тему, но на предмет l2vpn в LS.

в LS должен работать L2VPN? или я где-то допустил ошибку..

может попробовать собрать через "martini"

 

собрал такой конфиг

admin@BR> show configuration logical-systems L2CE1
interfaces {
   lt-1/2/10 {
       unit 11 {
           encapsulation ethernet;
           peer-unit 12;
           family inet {
               address 192.168.255.1/30;
           }
       }
   }
}

admin@BR> show configuration logical-systems L2CE2
interfaces {
   lt-1/2/10 {
       unit 13 {
           encapsulation ethernet;
           peer-unit 14;
           family inet {
               address 192.168.255.2/30;
           }
       }
   }
}

admin@BR>



admin@BR>




admin@BR> show configuration logical-systems P3 protocols
rsvp {
   interface lt-1/2/10.5;
   interface lt-1/2/10.7;
}
mpls {
   icmp-tunneling;
   no-cspf;
   label-switched-path to-R1 {
       to 172.16.0.5;
   }
   interface lt-1/2/10.5;
   interface lt-1/2/10.7;
}
bgp {
   group VPN-s {
       type internal;
       local-address 172.16.0.3;
       family inet {
           unicast;
       }
       family inet-vpn {
           unicast;
       }
       family l2vpn {
           signaling;
       }
       neighbor 172.16.0.5;
   }
}
ospf {
   area 0.0.0.0 {
       interface lo0.3;
       interface lt-1/2/10.5 {
           interface-type p2p;
       }
       interface lt-1/2/10.7 {
           interface-type p2p;
       }
   }
}

admin@BR>



admin@BR> show configuration logical-systems P1 protocols
rsvp {
   interface lt-1/2/10.4;
   interface lt-1/2/10.8;
}
mpls {
   icmp-tunneling;
   no-cspf;
   label-switched-path to-R3 {
       to 172.16.0.3;
   }
   interface lt-1/2/10.4;
   interface lt-1/2/10.8;
}
bgp {
   group VPN-s {
       type internal;
       local-address 172.16.0.5;
       family inet {
           unicast;
       }
       family inet-vpn {
           unicast;
       }
       family l2vpn {
           signaling;
       }
       neighbor 172.16.0.3;
   }
}
ospf {
   area 0.0.0.0 {
       interface lo0.5;
       interface lt-1/2/10.4 {
           interface-type p2p;
       }
       interface lt-1/2/10.8 {
           interface-type p2p;
       }
   }
}

admin@BR>
admin@BR> show configuration logical-systems P3 routing-instances L2VPN
instance-type l2vpn;
interface lt-1/2/10.14;
route-distinguisher 172.16.0.3:101;
vrf-target target:65501:101;
protocols {
   l2vpn {
       encapsulation-type ethernet;
       site PE_P3 {
           site-identifier 101;
           interface lt-1/2/10.14 {
               remote-site-id 102;
           }
       }
   }
}

admin@BR>

admin@BR> show configuration logical-systems P1 routing-instances L2VPN
instance-type l2vpn;
interface lt-1/2/10.12;
route-distinguisher 172.16.0.5:101;
vrf-target target:65501:101;
protocols {
   l2vpn {
       encapsulation-type ethernet;
       site PE_P1 {
           site-identifier 102;
           interface lt-1/2/10.12 {
               remote-site-id 101;
           }
       }
   }
}

admin@BR>




admin@BR> show l2vpn connections extensive logical-system P1
Layer-2 VPN connections:

Legend for connection status (St)
EI -- encapsulation invalid      NC -- interface encapsulation not CCC/TCC/VPLS
EM -- encapsulation mismatch     WE -- interface and instance encaps not same
VC-Dn -- Virtual circuit down    NP -- interface hardware not present
CM -- control-word mismatch      -> -- only outbound connection is up
CN -- circuit not provisioned    <- -- only inbound connection is up
OR -- out of range               Up -- operational
OL -- no outgoing label          Dn -- down
LD -- local site signaled down   CF -- call admission control failure
RD -- remote site signaled down  SC -- local and remote site ID collision
LN -- local site not designated  LM -- local site ID not minimum designated
RN -- remote site not designated RM -- remote site ID not minimum designated
XX -- unknown connection status  IL -- no incoming label
MM -- MTU mismatch               MI -- Mesh-Group ID not available
BK -- Backup connection          ST -- Standby connection
PF -- Profile parse failure      PB -- Profile busy
RS -- remote site standby        SN -- Static Neighbor
LB -- Local site not best-site   RB -- Remote site not best-site
VM -- VLAN ID mismatch

Legend for interface status
Up -- operational
Dn -- down

Instance: L2VPN
 Local site: PE_P1 (102)
   Number of local interfaces: 1
   Number of local interfaces up: 1
   lt-1/2/10.12        101
   Label-base        Offset     Size  Range     Preference
   800002            101        2      1         100
     status-vector:  0
   connection-site           Type  St     Time last up          # Up trans
   101                       rmt   Up     Sep 17 18:37:02 2014           1
     Remote PE: 172.16.0.3, Negotiated control-word: Yes (Null)
     Incoming label: 800002, Outgoing label: 800003
     Local interface: lt-1/2/10.12, Status: Up, Encapsulation: ETHERNET
   Connection History:
       Sep 17 18:37:02 2014  status update timer
       Sep 17 18:37:01 2014  PE route changed
       Sep 17 18:37:01 2014  Out lbl Update                    800003
       Sep 17 18:37:01 2014  In lbl Update                     800002
       Sep 17 18:37:01 2014  loc intf up                 lt-1/2/10.12

admin@BR> show l2vpn connections extensive logical-system P3
Layer-2 VPN connections:

Legend for connection status (St)
EI -- encapsulation invalid      NC -- interface encapsulation not CCC/TCC/VPLS
EM -- encapsulation mismatch     WE -- interface and instance encaps not same
VC-Dn -- Virtual circuit down    NP -- interface hardware not present
CM -- control-word mismatch      -> -- only outbound connection is up
CN -- circuit not provisioned    <- -- only inbound connection is up
OR -- out of range               Up -- operational
OL -- no outgoing label          Dn -- down
LD -- local site signaled down   CF -- call admission control failure
RD -- remote site signaled down  SC -- local and remote site ID collision
LN -- local site not designated  LM -- local site ID not minimum designated
RN -- remote site not designated RM -- remote site ID not minimum designated
XX -- unknown connection status  IL -- no incoming label
MM -- MTU mismatch               MI -- Mesh-Group ID not available
BK -- Backup connection          ST -- Standby connection
PF -- Profile parse failure      PB -- Profile busy
RS -- remote site standby        SN -- Static Neighbor
LB -- Local site not best-site   RB -- Remote site not best-site
VM -- VLAN ID mismatch

Legend for interface status
Up -- operational
Dn -- down

Instance: L2VPN
 Local site: PE_P3 (101)
   Number of local interfaces: 1
   Number of local interfaces up: 1
   lt-1/2/10.14        102
   Label-base        Offset     Size  Range     Preference
   800002            101        2      2         100
     status-vector:  0
   connection-site           Type  St     Time last up          # Up trans
   102                       rmt   Up     Sep 17 18:37:01 2014           1
     Remote PE: 172.16.0.5, Negotiated control-word: Yes (Null)
     Incoming label: 800003, Outgoing label: 800002
     Local interface: lt-1/2/10.14, Status: Up, Encapsulation: ETHERNET
   Connection History:
       Sep 17 18:37:01 2014  PE route changed
       Sep 17 18:37:01 2014  Out lbl Update                    800002
       Sep 17 18:37:01 2014  In lbl Update                     800003
       Sep 17 18:37:01 2014  loc intf up                 lt-1/2/10.14

admin@BR>



admin@BR> ping 192.168.255.2 logical-system L2CE1
PING 192.168.255.2 (192.168.255.2): 56 data bytes
^C
--- 192.168.255.2 ping statistics ---
5 packets transmitted, 0 packets received, 100% packet loss

admin@BR>

rdntw

rdntw

Posted
Posted

Видимо Вы правы, а пакетики бегают...эх

 

 

admin@BR:L2CE2> show interfaces lt-1/2/10.13
 Logical interface lt-1/2/10.13 (Index 973) (SNMP ifIndex 1221)
   Flags: Up SNMP-Traps 0x0 Encapsulation: ENET2
  MAC: 84:b5:9c:c1:90:b0
   Input packets : 43
   Output packets: 26
   Protocol inet, MTU: 1500
     Flags: Sendbcast-pkt-to-re, Is-Primary
     Addresses, Flags: Is-Default Is-Preferred Is-Primary
       Destination: 192.168.255.0/30, Local: 192.168.255.2, Broadcast: 192.168.255.3




admin@BR:L2CE1> show interfaces lt-1/2/10.11
 Logical interface lt-1/2/10.11 (Index 966) (SNMP ifIndex 1209)
   Flags: Up SNMP-Traps 0x0 Encapsulation: ENET2
   MAC: 84:b5:9c:c1:90:b0
   Input packets : 25
   Output packets: 46
   Protocol inet, MTU: 1500
     Flags: Sendbcast-pkt-to-re, Is-Primary
     Addresses, Flags: Is-Default Is-Preferred Is-Primary
       Destination: 192.168.255.0/30, Local: 192.168.255.1, Broadcast: 192.168.255.3

admin@BR:L2CE1>

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
 Share
Go to topic listing
×
×
  • Create New...
На сайте используются файлы cookie и сервисы аналитики для корректной работы форума и улучшения качества обслуживания. Продолжая использовать сайт, вы соглашаетесь с использованием файлов cookie и с Политикой конфиденциальности.