Introduction   What is WAN-PHY mode? The purpose of WAN-PHY is to render 10 Gigabit Ethernet compatible with the SONET STS-192c format and data rate, as defined by ANSI, as well as the SDH VC-4-64c container specified by ITU. When the controller is in WAN-PHY mode the WIS sublayer transports 10 Gigabit Ethernet frames in an OC-192c SONET payload which can interoperate with SONET section or line level repeaters. This effectively bridges the asynchronous world of Ethernet data with synchronous SONET/SDH transport allowing 10 Gigabit Ethernet to be transparently carried over current DWDM networks without having to directly map the Ethernet frames into SONET/SDH. PHY device maps 10GE LAN streams to STS-192c SPE and this limits the data-rate to 9.584 Gbps. WAN PHY provides rich SONET OAM capabilities for link management. It is to be noted that WAN PHY line-rate is lower than 10GE LAN rate (10.3125 Gbps).     Topology   WAN-PHY InterOP between Cisco & Juniper Topology         Cisco Configuration & show commands   Cisco Configuration:   This example shows how to configure the interface for WAN PHY mode: RP/0/RSP0/CPU0:LSR# config RP/0/RSP0/CPU0:LSR(config)# interface interface TenGigE0/1/0/27                                                                                                   RP/0/RSP0/CPU0:LSR(config-if)# transport-mode wan RP/0/RSP0/CPU0:LSR(config-if)# commit The following configuration is needed to operate in WAN PHY mode: RP/0/RSP0/CPU0:LSR# config RP/0/RSP0/CPU0:LSR(config)# controller wanphy 0/1/0/27                                                                                                   RP/0/RSP0/CPU0:LSR(config)# wanmode on RP/0/RSP0/CPU0:LSR(config)# commit      Cisco show commands:   This cli displays registers, alarms, and module information for the specified 10-Gigabit Ethernet WAN PHY controller.   RP/0/RP0/CPU0:LSR2#sh controllers wanphy 0/1/0/27 all Fri Jul 15 15:59:32.574 PDT Interface: wanphy0/1/0/27 Configuration Mode: WAN Mode SECTION   LOF = 1, LOS = 0, BIP(B1) = 0 LINE   AIS = 0, RDI = 1, FEBE = 0, BIP(B2) = 0 PATH   AIS = 0, RDI = 0, FEBE = 47903, BIP(B3) = 0   LOP = 0, NEWPTR = 0, PSE = 0, NSE = 0 WIS ALARMS   SEF = 1, FEPLMP = 0, FEAISP = 1   WLOS = 0, PLCD = 0   LFEBIP = 0, PBEC = 0, PLMP = 0   Active Alarms[All defects]: Active Alarms[Highest Alarms]:   Rx(K1/K2): N/A, Tx(K1/K2): N/A   S1S0 = N/A, C2 = N/A PATH TRACE BUFFER Remote IP addr: BER thresholds: SF = E-3 SD = E-6 TCA thresholds: N/A Alarm reporting enabled for:los, lof, path lop, REGISTERS P_FEBE  : 47903 L_FE_BIP: 0 L_BIP   : 0 P_BEC   : 0 S_BIP   : 0 J1-Rx0  : 0x   0 J1-Rx1  : 0x   0 J1-Rx2  : 0x2f30 J1-Rx3  : 0x2f30 J1-Rx4  : 0x2d30 J1-Rx5  : 0x7865 J1-Rx6  : 0x  e8 J1-Rx7  : 0x   0 Internal Information Operational Mode: WAN Mode Current Alarms: 0x0                                                                                                           This cli displays information about any alarms that are detected by the specified 10-Gigabit Ethernet WAN PHY controller.   RP/0/RP0/CPU0:LSR2#sh controllers wanphy 0/1/0/27 alarms Fri Jul 15 15:59:38.839 PDT Interface: wanphy0/1/0/27 Configuration Mode: WAN Mode SECTION   LOF = 1, LOS = 0, BIP(B1) = 0 LINE   AIS = 0, RDI = 1, FEBE = 0, BIP(B2) = 0 PATH   AIS = 0, RDI = 0, FEBE = 47903, BIP(B3) = 0   LOP = 0, NEWPTR = 0, PSE = 0, NSE = 0 WIS ALARMS   SEF = 1, FEPLMP = 0, FEAISP = 1   WLOS = 0, PLCD = 0   LFEBIP = 0, PBEC = 0, PLMP = 0   Active Alarms[All defects]: Active Alarms[Highest Alarms]:   Rx(K1/K2): N/A, Tx(K1/K2): N/A   S1S0 = N/A, C2 = N/A PATH TRACE BUFFER Remote IP addr: BER thresholds: SF = E-3 SD = E-6 TCA thresholds: N/A Alarm reporting enabled for:los, lof, path lop,     This cli displays registers for the specified 10-Gigabit Ethernet WAN PHY controller.   RP/0/RP0/CPU0:LSR2#sh controllers wanphy 0/1/0/27 registers Fri Jul 15 15:59:44.562 PDT Interface: wanphy0/1/0/27 Configuration Mode: WAN Mode REGISTERS P_FEBE  : 47903 L_FE_BIP: 0 L_BIP   : 0 P_BEC   : 0 S_BIP   : 0 J1-Rx0  : 0x   0 J1-Rx1  : 0x   0 J1-Rx2  : 0x2f30 J1-Rx3  : 0x2f30 J1-Rx4  : 0x2d30 J1-Rx5  : 0x7865 J1-Rx6  : 0x  e8 J1-Rx7  : 0x   0 Internal Information Operational Mode: WAN Mode Current Alarms: 0x0                                                                                                           Cisco Configuration of Signal Failure(SF) and Signal Degrade(SD)   SD/SF BER threshold is configurable using ‘threshold’ command. Software monitors B2 BIP errors and asserts SD/SF BER alarms whenever the error-rate exceeds the threshold. Port link will go down once BIP error-rate exceeds SF BER threshold.     RP/0/RSP0/CPU0:ios#sh controllers wanphy 0/6/0/0 alarms | inc SD BER thresholds: SF = 10e-3 SD = 10e-6   Threshold configuration: RP/0/RSP0/CPU0:ios#conf t RP/0/RSP0/CPU0:ios(config)#controller wanphy 0/6/0/0 RP/0/RSP0/CPU0:ios(config-wanphy)#threshold ? sd-ber Set Signal Degrade BER threshold sf-ber Set Signal Fail BER threshold   CISCO Troubleshooting Do the following steps before debugging L2/L3 layer:   1. Check Fiber or optics when B1/B2/B3 counters are incrementing   2. Check for SD_BER or SF_BER alarms in show controller wanphy <> alarms   3. Show controller tengig <> internal RP/0/RP0/CPU0:LSR2#sh controllers tenGigE0/1/0/27 internal Tue Jul 19 17:02:45.829 PDT Internal data for interface: TenGigE0/1/0/27 Port Number         : 27 Bay Number          : 0 Ifinst              : 0 Ifinst Subport      : 27 Board Type          : 0x00380261 Port Type           : 10GE Transport mode      : WAN BIA MAC addr        : 6c9c.ed6f.214b Oper. MAC addr      : e0ac.f167.259b Egress MAC addr     : e0ac.f167.259b Port Available      : true Status polling is   : enabled Status events are   : enabled I/F Handle          : 0x06000780 Cfg Link Enabled    : tx/rx enabled H/W Tx Enable       : yes MTU                 : 2000 H/W Speed           : 10 Gbps H/W Duplex          : Full H/W Loopback Type   : None FEC                 : Disable H/W FlowCtrl Type   : None H/W AutoNeg Enable  : Off H/W Link Defects    : (0x00100000)  WANPHY_SD_SF_BER H/W Raw Link Defects : (0x00100000)  WANPHY_SD_SF_BER Link Up             : yes Link Led Status     : Link up   -- Green/Amber Serdes hw version   : 0.3 Serdes sw version   : 8.0 Pluggable Present   : yes Pluggable Type      : SFP-10G-SR Pluggable PID       : SFP-10G-SR Pluggable Compl.    : Compliant Pluggable Type Supp.: Supported Pluggable PID Supp. : Supported   Juniper Configuration & Show commands   Juniper Configuration:   To set a WAN-PHY on Juniper 10G interface use the following cli: set interfaces <interface id> framing wan-phy   Configuring the wan-phy framing mode on the 10-Gigabit Ethernet ports allows the interface to accept SONET or SDH frames without further configuration. If you configure the WAN PHY mode on an aggregated Ethernet interface, you must set the aggregated Ethernet link speed to OC192.       root@JNPR-2-LER5# show interfaces Jul 15 15:14:11 xe-0/0/0 {     description "connected to LSR2 ten0/1/0/28 ";     framing {         wan-phy;     }     gigether-options {         802.3ad ae2;     } } xe-0/1/0 {     description "connected to LSR2 ten0/1/0/27 ";     framing {         wan-phy;     }     gigether-options {         802.3ad ae2;     } }   Juniper show command:   To display interface information, use the operational mode command show interfaces xe-fpc/pic/port extensive .     root@JNPR-2-LER5# run show interfaces xe-0/0/0 extensive Jul 15 15:19:59 Physical interface: xe-0/0/0, Enabled, Physical link is Up   Interface index: 646, SNMP ifIndex: 524, Generation: 649   Description: connected to LSR2 ten0/1/0/28   Link-level type: Ethernet, MTU: 2000, MRU: 2008, Clocking: Internal, WAN-PHY mode, Speed: OC192, BPDU Error: None, MAC-REWRITE Error: None, Loopback: None, Source filtering: Disabled, Flow control: Disabled   Pad to minimum frame size: Disabled   Device flags   : Present Running   Interface flags: SNMP-Traps Internal: 0x4000   Link flags     : None   CoS queues     : 8 supported, 8 maximum usable queues   Hold-times     : Up 0 ms, Down 0 ms   Current address: 00:19:e2:bc:17:c2, Hardware address: 00:19:e2:bc:10:00   Last flapped   : 2016-07-11 18:44:03 PDT (3d 20:35 ago)   Statistics last cleared: Never   Traffic statistics:    Input  bytes  :         149780058791               582416 bps    Output bytes  :          10938000701                    0 bps    Input  packets:            904262884                  442 pps    Output packets:             54140655                    0 pps    IPv6 transit statistics:     Input  bytes  :                   0     Output bytes  :                   0     Input  packets:                   0     Output packets:                   0   Label-switched interface (LSI) traffic statistics:    Input  bytes  :                    0                    0 bps    Input  packets:                    0                    0 pps   Dropped traffic statistics due to STP State:    Input  bytes  :                    0    Output bytes  :                    0    Input  packets:                    0    Output packets:                    0    …..   ……   ……….   Cisco Supported Hardware:   List of Linecards & MPA’s with WAN-PHY support on ASR9K.  1.        A9K-MPA-2x10GE  2.        A9K-MPA-4x10GE  3.        A9K-MPA-8x10GE  4.        A9K-MPA-20x10GE  5.        A9K-MPA-20x10GECM  6.        A9K-MPA-2x100GE(10x10 breakout)  7.        A9K-MPA-2x100GECM(10x10 breakout)  8.        A9K-MPA-1x100GE(10x10 breakout)  9.        A9K-24x10GE-SE/TR 10.       A9K-36x10GE-SE/TR 11.       A9K-8x100GE-SE/TR, A99K-8x100GE-SE/TR 12.      A9K-4x100GE-SE/TR, A99K-4x100GE-SE/TR   References: Cisco & Juniper Documentation   Related Information: Sheetal Bhogale , Sr. Software Engineer, ASR9K Sivakumar Munagapati, Technical Leader , ASR9K Dinesh Pullat, Sr. Technical Leader, ASR9K Sadananda Phadke, Sr. Technical Leader, ASR9K ... View more

  Why Top Label Hash? Traffic is running across the bundle with multiple member-links. If all the member-links are up but traffic is not getting forwarded currently there is no way to know if there is traffic black holing happening. This feature allows us to monitor all the member links and ensure they are up and running thereby avoids any traffic black holing. Why Normal Hashing won’t help here? With Normal Hashing we hash based on the bottom label (eos =1) and router-id. This is not predictable at every hop. Top label hash does the hashing based on the topmost label. With top label hash user can predict the hash and the member-link through which traffic is going to get forwarded giving user full control over defined LSP’s. Introduction: MPLS Top Label Hash MPLS Top label hash allows Label switch routers (LSRs) to switch MPLS OAM packets based on the top label hashing mechanism. LSRs generate a hash of the label stack to discriminate flows and use this discriminator to distribute the flows over equal cost multipaths (ECMPs) that exists. Topology  Refer to top-label-topo.png attachment Overview: Top label hash provides us the capability of hashing based on the Top Label. MPLS static LSP is used on all the routers, connected via bundle-ether with multiple member links, in the forwarding path. At each hop top-label is popped and the packet is forwarded via the chosen bundle-member link to the next hop. The sequence of labels should be defined in such a way that each label uses a different bundle-member to load-balance amongst the member-links How MPLS static OAM works? When a router receives a labeled packet the topmost label is looked up. LSR sees the 20-bit field in the top label, which carries the actual value of the label. Hash is calculated on this value and corresponding bundle-member link is chosen. Based on the value of the label, corresponding label operation such as swap, push or pop is performed and packet is forwarded to the next hop via the chosen member-link. Basic configuration steps LER1: mpls static   interface Bundle-Ether21 interface Bundle-Ether31 address-family ipv4 unicast top-label-hash                                 - > Enables Top label hash                              local-label 14000 allocate              -- > specifies the incoming label as 14000    forward      path 1 nexthop Bundle-Ether21 14.0.4.2 out-label pop     -- > label operation pop   LSR2: mpls static interface Bundle-Ether21 interface Bundle-Ether22 address-family ipv4 unicast top-label-hash local-label 14001 allocate                 -- > specifies the incoming label as 14001    forward      path 1 nexthop Bundle-Ether22 14.0.5.1 out-label pop -- > label operation pop   LER2: mpls static interface Bundle-Ether22 interface Bundle-Ether32 address-family ipv4 unicast top-label-hash local-label 14002 allocate               -- > specifies the incoming label as 14002    forward      path 1 nexthop Bundle-Ether32 32.0.1.1 out-label pop -- > label operation pop   Packet- flow OAM Packet with static label stack is being sent from traffic generator IXIA. Packet enters LER1 with stack of 3 labels (14000,14001,14002). LFIB lookup happens on the LER1 router and it learns what the nexthop is and what label operation (push,pop or swap) is to be performed on the LER1. 1) Since LER1 has a pop operation defined for the nexthop, label 14000 is popped from LER1 and the packet is sent to LSR1 with 2 labels. Based on the output of the command “show bundle load-balancing bundle-ether21 location 0/0/CPU0” the nexthop member-link with LON value of 0 is chosen. This value is calculated by doing a MOD on the last byte of the topmost label value with the total number of member-links ( eg: i) hex of 14000 = 36B0;  ii) last 2 bytes is B0 iii) convert this hex value back to decimal : decimal(B0) = 176 iv) 176 mod 3 = 2 so member link with LON value of 2 is chosen) 2) Then the LFIB table on LSR1 is looked up and packet is forwarded to LER2, which is the nexthop by popping label 14001. Next hop member link is chosen using the following (eg: mod 14001 % 3 = 0; so member link with LON value of 0 is chosen) 3) Finally the packet reaches LER2 and the label 14002 is popped and the final IP packet is sent to the traffic generator IXIA-2.Next hop member link is chosen using the following (eg: mod 14002 % 3 = 1; so member link with LON value of 1 is chosen)   RP/0/RSP0/CPU0:LER3#sh bundle load-balancing bundle-ether 21 location 0/0/CPU0 Wed Jan 13 14:52:53.829 PST   Bundle-Ether21 Type:                 Ether (L3) Members <current/max>: 3/64 Total Weighting:       3 Load balance:         Default Locality threshold:   65 Avoid rebalancing?     False Sub-interfaces:       0   Member Information:    Port:                 LON ULID BW    -------------------- --- ---- --    Hu0/0/0/2               2     2   1    Hu0/0/0/3               0     0   1    Hu0/0/0/4             1     1   1   Platform Information: =====================                    * Bundle Summary Information *                    --------------------------   Interface             : Bundle-Ether21       Ifhandle           : 0x0203eaa0 Lag ID                : 2                     Virtual Port       : 255 Number of Members     : 3                     Local to LC       : Yes Hash Modulo Index     : 3 MGSCP Operational Mode : No   Member Information: LON     Interface         ifhandle   Base         SFP   port slot remote/                                      Transport                     rack_id -----   -------------     ---------- ----------   ---   ---- ---- ------- 0       Hu0/0/0/3         0x00000100 0x00000100   120   116   0     0/0 1      Hu0/0/0/4         0x00000180 0x00000180   132   117   0     0/0 2       Hu0/0/0/2         0x00000200 0x00000200   108   117   0     0/0   Preroute Member Information: LON       Interface       ifhandle     SFP   port   slot remote/rack_id -----   ---------------   ----------   ---   ----   ---- -------------- 0       Hu0/0/0/3         0x00000100   120   116     0       0/0                      * Bundle Table Information *                      ------------------------   [NP 0]: ----------------------------------------------------------------------    Unicast (Global) LAG table     |     Unicast (Rack) LAG table ---------------------------------------------------------------------- idx local   VQI   port   VQI-LB | idx local   VQI   port   VQI-LB ---------------------------------------------------------------------- 1     0   120   116     0       1     0   120   116     0 2     0   132   117     0       2     0   132   117     0 3     0   108   117     0       3     0   108   117     0   [NP 1]: -------------------------------------------------------------------------------------------------------------    Unicast (Global) LAG table     |   Multicast (Local) LAG table   |   Unicast (Rack) LAG table ------------------------------------------------------------------------------------------------------------- idx local   VQI   port   VQI-LB | idx local   VQI   port   VQI-LB | idx local   VQI   port   VQI-LB -------------------------------------------------------------------------------------------------------------    1     1   120   116     0       1     1   120   116     0       1     1   120   116     0    2     0   132   117     0       2     1   108   117     0       2     0   132   117     0    3     1   108   117     0       3     0     0     0     0       3     1   108   117     0   [NP 2]: -------------------------------------------------------------------------------------------------------------    Unicast (Global) LAG table     |   Multicast (Local) LAG table   |   Unicast (Rack) LAG table ------------------------------------------------------------------------------------------------------------- idx local   VQI   port   VQI-LB | idx local   VQI   port   VQI-LB | idx local   VQI   port   VQI-LB -------------------------------------------------------------------------------------------------------------    1     0   120   116     0       1     1   132   117     0       1     0   120   116     0    2     1   132   117     0       2     0     0     0     0       2     1   132   117     0    3     0   108   117     0       3     0     0     0     0       3     0   108   117     0   [NP 3]: ----------------------------------------------------------------------    Unicast (Global) LAG table     |     Unicast (Rack) LAG table ---------------------------------------------------------------------- idx local   VQI   port   VQI-LB | idx local   VQI   port   VQI-LB ---------------------------------------------------------------------- 1     0   120   116     0       1     0   120   116     0 2     0   132   117     0       2     0   132   117     0 3     0   108   117     0       3     0   108   117      0                      * SW LAG Table Information *                      ------------------------   --------------------------------------------------------------------------------------          Global/Rack LAG table         |             Local LAG table -------------------------------------------------------------------------------------- idx local   LON   VQI   port   VQI-LB | idx local   LON   VQI   port   VQI-LB --------------------------------------------------------------------------------------    1     1     0   120   116     0     1     1     0   120   116     0    2     1     1   132   117     0     2     1     1   132   117     0    3     1     2   108   117     0     3     1     2   108   117     0   ===============================================================================     sh mpls forwarding private detail location 0/0/CPU0 14000 Pop         No ID             BE21         14.0.4.2       805122162624      Updated: Jan 13 11:08:07.710      Version: 16, Priority: 4      Label Stack (Top -> Bottom): { Imp-Null }      NHID: 0x0, Path idx: 0, Backup path idx: 0, Weight: 0      MAC/Encaps: 14/14, MTU: 1500      Packets Switched: 10322079008 Caveats CSCus77690 Top Label Hash is not indexing to correct intf with mixed bundle speeds Example Use-case:Top label hash behavior for Bundle with mixed bandwidth For mixed bandwidth member bundles, it is based on the credit. For example, if there is a bundle with one 100Gig member and 1 10Gig member, then first 10 hash values point to 1st member and 11th will point to 10Gig member.  Here is hashing is based on the assumption that there are 11 members (module 11 = 10+1). Show commands output: show bundle load-balancing bundle-ether 21 location 0/1/CPU0   Bundle-Ether21   Type:                  Ether (L3)   Members <current/max>: 4/64   Total Weighting:       22   <===   because there are 2 100gig members and 2 10Gig members   Load balance:          Default   Locality threshold:    65   Avoid rebalancing?     False   Sub-interfaces:        0     Member Information:     Port:                 LON  ULID  BW     --------------------  ---  ----  --     Hu0/1/0/3               0     0  10  <===      Hu0/2/0/0               1     1  10  <===     Te0/0/0/8               2     3   1     Te0/0/0/9               3     2   1     Platform Information:   =====================                     * Bundle Summary Information *                     --------------------------   Interface: Bundle-Ether21       Ifhandle: 0x02002d60   Lag ID: 4                        Virtual Port: 255        Number of Members:4                                           Local to LC        : Yes        Hash Modulo Index: 22           <======================          MGSCP Operational Mode: No                      Member Information: LON     Interface         ifhandle    Base         SFP   port  slot remote/                                       Transport                     rack_id -----   -------------     ----------  ----------   ---   ----  ---- ------- 0       Hu0/1/0/3         0x06000140  0x06000140   234    116    3     0/0   <=== VOQ used for the member 1       Hu0/2/0/0         0x080000c0  0x080000c0   324     10    4     0/0  <=== VOQ used for the member 3       Te0/0/0/9         0x04000300  0x04000300    90      6    2     0/0  <=== VOQ used for the member 2       Te0/0/0/8         0x040002c0  0x040002c0    95      4    2     0/0  <=== VOQ used for the member   Preroute Member Information: LON        Interface       ifhandle     SFP   port   slot remote/rack_id -----   ---------------   ----------    ---   ----   ---- -------------- 0       Hu0/1/0/3         0x06000140    234    116      3       0/0                      * Bundle Table Information *                      ------------------------   [NP 0]: ----------------------------------------------------------------------     Unicast (Global) LAG table     |    Unicast  (Rack) LAG table    ----------------------------------------------------------------------  idx  local    VQI   port   VQI-LB | idx  local   VQI   port   VQI-LB  ----------------------------------------------------------------------   1      0    234    116      0       1      0    234    116      0  <=== All in blue are hash values for member 234 (Hun0/1/0/3)   2      0    234    116      0       2      0    234    116      0   3      0    234    116      0       3      0    234    116      0   4      0    234    116      0       4      0    234    116      0   5      0    234    116      0       5      0    234    116      0   6      0    234    116      0       6      0    234    116      0   7      0    234    116      0       7      0    234    116      0   8      0    234    116      0       8      0    234    116      0   9      0    234    116      0       9      0    234    116      0  10      0    234    116      0      10      0    234    116      0   11      0    324     10     12      11      0    324     10     12  <== 10 of these are hash values for member 324 (Hun0/2/0/0)   12      0    324     10     12      12      0    324     10     12  13      0    324     10     12      13      0    324     10     12  14      0    324     10     12      14      0    324     10     12  15      0    324     10     12      15      0    324     10     12  16      0    324     10     12      16      0    324     10     12  17      0    324     10     12      17      0    324     10     12  18      0    324     10     12      18      0    324     10     12  19      0    324     10     12      19      0    324     10     12  20      0    324     10     12      20      0    324     10     12  21      0     95      4      0      21      0     95      4      0  22      0     90      6      0      22      0     90      6      0 <== hash values of 10g Member links ten0/0/0/8 and ten0/0/0/9 with 95 and 90 as hash values respectively. IOS-XR Release Feature is supported starting IOS-XR release 5.3.2 References: N/A Related Information: Sheetal Bhogale, Sr. Software Engineer, CSG Xander Thuijs, Principal Engineer, CSG Sadananda Phadke, Sr. Technical Lead, CSG   ... View more

  This document summarizes CGNAT/CGv6 on VSM as implemented in Release 5.1.1     ... View more

Introduction Topology Test Scenarios 1) Import from default-vrf           i) Matching prefix           ii) Matching Community attribute                        iii) Matching as-path; prefix           iv) Matching as-path;prefix and community 2) Export to default-vrf           i) Matching prefix           ii) Matching community attribute           iii) Matching as-path; prefix           iv) Matching as-path; prefix;community 3) Common prefixes imported to multiple vrf's Traffic Scenarios 4 a) CISCO vrf ----> Junos global    b) Junos Global ----> Cisco vrf 5 a) Cisco global ----> Junos vrf    b) Junos vrf ----> Cisco global 6 a) CISCO vrf -----> Junos vrf    b) Junos vrf ----> Cisco vrf References Related Information     Introduction Virtual Routing and Forwarding (VRF) tables are logically isolated entities that enable multiple VPN’s to share a common core such as Internet while keeping private networks traffic segregated from the Internet traffic.In some cases, we will need to allow global prefixes to be installed in vrf table and vice-versa. Currently this can be done by adding a static route, etc.Customers want a way to dynamically leak routes between global and vrf table. This is accomplished through the new feature BGP Dynamic Route-leaking that provides a flexibility of leaking multiple prefixes using route-policy for import and export. Dynamic Route leaking feature is introduced to import routes from global/default vrf to non-default vrf and vice-versa.       Topology       Basic Configuration CLI   To import from default-VRF to non-default-VRF import, the following configuration is needed:          vrf <VRF_NAME>          address-family <ADDRESS_FAMILY>          import from default-vrf route-policy <POLICY_NAME>   To import from non-default-VRF to default VRF, the following configuration is needed:         vrf <VRF_NAME>        address-family <ADDRESS_FAMILY>        export to default-vrf route-policy <POLICY_NAME>   Policy is mandatory in both the cases.       Test Scenarios 1) Import from default-vrf           i) Matching prefix     Configuration on Cisco router route-policy dyna-route-leak-8-x   if destination in (8.0.0.0/24) then     pass   endif end-policy  vrf vrf1 address-family ipv4 unicast import from default-vrf route-policy dyna-route-leak-8-x   import route-target    1:1   !       Existing Global entry for the route:   RP/0/RSP0/CPU0:vc#sh bgp 8.0.0.0/24                       Wed Jan 16 10:48:52.515 PST BGP routing table entry for 8.0.0.0/24 Versions:   Process           bRIB/RIB  SendTblVer   Speaker             272161      272161 Last Modified: Jan 16 10:38:15.025 for 00:10:37 Paths: (1 available, best #1)   Not advertised to any peer   Path #1: Received by speaker 0   Not advertised to any peer   65008     192.200.1.2 (metric 2) from 6.6.6.6 (6.6.6.6)       Origin incomplete, localpref 100, valid, internal, best, group- best, import-candidate       Received Path ID 0, Local Path ID 1, version 272161 RP/0/RSP0/CPU0:vc#   Show command to see imported route in vrf1   RP/0/RSP0/CPU0:vc#sh bgp vrf vrf1 8.0.0.0/24              Wed Jan 16 10:49:10.665 PST BGP routing table entry for 8.0.0.0/24, Route Distinguisher: 3.3.3.3:0 Versions:   Process           bRIB/RIB  SendTblVer   Speaker             258011      258011 Last Modified: Jan 16 10:38:15.025 for 00:10:55 Paths: (1 available, best #1)   Advertised to CE update-groups (with more than one peer):     0.2   Path #1: Received by speaker 0   Advertised to CE update-groups (with more than one peer):     0.2   65008     192.200.1.2 (metric 2) from 6.6.6.6 (6.6.6.6)       Origin incomplete, localpref 100, valid, internal, best, group-best, import-candidate, imported- This tag gets added for the imported route       Received Path ID 0, Local Path ID 1, version 258011       Source VRF: default, Source Route Distinguisher: 0:0 RP/0/RSP0/CPU0:vc# RP/0/RSP0/CPU0:vc#sh cef vrf vrf1 8.0.0.0/24 Wed Jan 16 10:50:08.130 PST 8.0.0.0/24, version 110154, internal 0x14000001 (ptr 0x75714894) [1], 0x0 (0x0), 0x0 (0x0) Updated Jan 16 10:38:15.502 Prefix Len 24, traffic index 0, precedence n/a, priority 3    via 192.200.1.2, 7 dependencies, recursive [flags 0x6010]     path-idx 0 [0x72d9f6e0 0x0]     next hop VRF - 'default', table - 0xe0000000---- next hop would still point to the default vrf for a route imported in vrf table     next hop 192.200.1.2 via 192.200.1.0/24 RP/0/RSP0/CPU0:vc#             ii) Matching Community attribute                 Configuration on Cisco router route-policy dyna-route-leak-comm-9-x   if community matches-every (65008:9) then     pass   endif end-policy vrf vrf2 address-family ipv4 unicast   import from default-vrf route-policy dyna-route-leak-comm-9-x   import route-target    1:2   Global Entry for route:   RP/0/RSP0/CPU0:vc#sh bgp 9.0.0.0/24 Fri Jan  4 16:27:10.080 PST BGP routing table entry for 9.0.0.0/24 ….. ……… ……… Not advertised to any peer   65008     1.1.1.1 (metric 9) from 1.1.1.1 (1.1.1.1)       Origin IGP, localpref 100, valid, internal, best, group-best, import-candidate       Received Path ID 0, Local Path ID 1, version 739583       Community: 65008:9   Show command to see imported route in vrf2   RP/0/RSP0/CPU0:vc#sh bgp vrf vrf2 9.0.0.0   Wed Jan 16 11:07:39.941 PST BGP routing table entry for 9.0.0.0/24, Route Distinguisher: 1:2 ..... .... 192.200.1.2 (metric 2) from 6.6.6.6 (6.6.6.6)       Origin incomplete, localpref 100, valid, internal, best, group-best, import-candidate, imported ......               iii) Matching as-path; prefix   Configuration on Cisco router route-policy dyna-route-leak-aspath-prefix-10-x   if as-path originates-from '65008'  and destination in (10.0.0.0/24) then     pass   endif end-policy ! vrf vrf3 address-family ipv4 unicast   import from default-vrf route-policy dyna-route-leak-aspath-prefix-10-x   import route-target    1:3   Global entry for the route:   RP/0/RSP0/CPU0:vc#sh bgp 10.0.0.0/24 Wed Jan 16 11:13:46.446 PST BGP routing table entry for 10.0.0.0/24 …… …….   Show command to see imported route in vrf3   RP/0/RSP0/CPU0:vc#sh bgp vrf vrf3 10.0.0.0/24 Wed Jan 16 11:14:10.537 PST BGP routing table entry for 10.0.0.0/24, Route Distinguisher: 1:3 ….. ….. Origin incomplete, localpref 100, valid, internal, best, group-best, import-candidate, imported …….   RP/0/RSP0/CPU0:vc#sh cef vrf vrf3 10.0.0.0 Wed Jan 16 11:14:21.743 PST 10.0.0.0/24, version 58508, internal 0x14000001 (ptr 0x75b37d34) [1], 0x0 (0x0), 0x0 (0x0) …….    next hop VRF - 'default', table - 0xe0000000    next hop 192.200.1.2 via 192.200.1.0/24 RP/0/RSP0/CPU0:vc#               iv) Matching as-path;prefix and community   Configuration on Cisco router route-policy dyna-route-leak-aspath-prefix-comm-11-x   if as-path originates-from '65008'  and destination in (11.0.0.0/24) and community matches-every (65008:11) then     pass   endif end-policy   vrf vrf4 address-family ipv4 unicast   import from default-vrf route-policy dyna-route-leak-aspath-prefix-comm-11-x   import route-target    1:4   Global entry for the route:   RP/0/RSP0/CPU0:vc#sh bgp 11.0.0.0/24 Wed Jan 16 11:20:59.420 PST BGP routing table entry for 11.0.0.0/24 ….. …..   Show command to see imported route in vrf4   RP/0/RSP0/CPU0:vc#sh bgp vrf vrf4 11.0.0.0                                   Wed Jan 16 11:22:48.438 PST BGP routing table entry for 11.0.0.0/24, Route Distinguisher: 1:4 …… …… Origin incomplete, localpref 100, valid, internal, best, group-best, import-candidate, imported ……..   RP/0/RSP0/CPU0:vc#sh cef vrf vrf4 11.0.0.0 Wed Jan 16 11:23:27.457 PST 11.0.0.0/24, version 39030, internal 0x14000001 (ptr 0x75b37da4) [1], 0x0 (0x0), 0x0 (0x0) Updated Jan 16 11:22:50.079 .......    next hop VRF - 'default', table - 0xe0000000    next hop 192.200.1.2 via 192.200.1.0/24 RP/0/RSP0/CPU0:vc#         2) Export to default-vrf             i) Matching prefix Cisco configuration on the router route-policy dyna-route-leak-26-x   if destination in (26.0.0.0/30) then     pass   endif end-policy vrf vrf1 address-family ipv4 unicast export to default-vrf route-policy dyna-route-leak-26-x   export route-target    1:1   VRF entry for the route:   RP/0/RSP0/CPU0:vc#sh bgp vrf vrf1 26.0.0.0                 Wed Jan 16 11:34:20.369 PST BGP routing table entry for 26.0.0.0/30, Route Distinguisher: 3.3.3.3:0 ……. ……   Show command to see exported route in the global table   RP/0/RSP0/CPU0:vc#sh bgp 26.0.0.0                         Wed Jan 16 11:34:46.949 PST BGP routing table entry for 26.0.0.0/30 …….. ……. Advertised to update-groups (with more than one peer):    0.7 0.8 65002    192.172.1.2 from 192.172.1.2 (192.172.1.2)      Origin incomplete, localpref 100, valid, external, best, group-best, import-candidate, imported -••à This tag gets added for the imported route      Received Path ID 0, Local Path ID 1, version 372157      Extended community: RT:1:1      Origin-AS validity: not-found      Source VRF: vrf1, Source Route Distinguisher: 3.3.3.3:0   RP/0/RSP0/CPU0:vc#sh cef 26.0.0.0 Wed Jan 16 11:34:54.832 PST 26.0.0.0/30, version 2038985, internal 0x14004001 (ptr 0x759afa7c) [1], 0x0 (0x72fee3d8), 0x400 (0x74714080) ……… next hop VRF - 'vrf1', table - 0xe0000042••à next hop would still point to the vrf table for a route imported in global table ……….             ii) Matching community attribute Cisco Configuration on the router route-policy dyna-route-leak-comm-27-x   if community matches-every (65004:27) then     pass   endif end-policy ! vrf vrf2 address-family ipv4 unicast export to default-vrf route-policy dyna-route-leak-comm-27-x   export route-target    1:2   !   VRF Entry for route:   RP/0/RSP0/CPU0:vc#sh bgp vrf vrf2 27.0.0.0                     Wed Jan 16 11:42:48.873 PST BGP routing table entry for 27.0.0.0/30, Route Distinguisher: 1:2 …… ……   Show command to see exported route in the global table RP/0/RSP0/CPU0:vc#sh bgp 27.0.0.0 Wed Jan 16 11:44:26.564 PST BGP routing table entry for 27.0.0.0/30 …… ……..    192.172.2.2 from 192.172.2.2 (192.172.2.2)      Origin EGP, localpref 100, valid, external, best, group-best, import-candidate, imported ………       RP/0/RSP0/CPU0:vc#sh cef 27.0.0.0 Wed Jan 16 11:44:33.638 PST 27.0.0.0/30, version 2038990, internal 0x14004001 (ptr 0x759afbc0) [1], 0x0 (0x72fee360), 0x400 (0x74b8c278) ………    next hop VRF - 'vrf2', table - 0xe0000043    …….               iii) Matching as-path; prefix Cisco configuration on the router route-policy dyna-route-leak-aspath-prefix-28-x   if as-path originates-from '65006'  and destination in (28.0.0.0/30) then     pass   endif end-policy   vrf vrf3 address-family ipv4 unicast export to default-vrf route-policy dyna-route-leak-aspath-prefix-28-x   export route-target    1:3   Vrf entry for the route:   RP/0/RSP0/CPU0:vc#sh bgp vrf vrf3 28.0.0.0 Wed Jan 16 11:47:04.085 PST BGP routing table entry for 28.0.0.0/30, Route Distinguisher: 1:3 ……… ……   Show command to see exported route in the global table   RP/0/RSP0/CPU0:vc#sh bgp 28.0.0.0 Wed Jan 16 11:48:31.484 PST BGP routing table entry for 28.0.0.0/30 …….. …….. Origin incomplete, localpref 100, valid, external, best, group-best, import-candidate, imported ……   RP/0/RSP0/CPU0:vc#sh cef 28.0.0.0 Wed Jan 16 11:47:53.249 PST 28.0.0.0/30, version 2059119, internal 0x14000001 (ptr 0x759af9a4) [1], 0x0 (0x72fee400), 0x400 (0x754ea778) …….. ………    next hop VRF - 'vrf3', table - 0xe0000044    ……               iv) Matching as-path; prefix;community Cisco configuration on the router route-policy dyna-route-leak-aspath-prefix-comm-29-x   if as-path originates-from '65008'  and destination in (29.0.0.0/30) and community matches-every (65008:29) then     pass   endif end-policy   vrf vrf4 address-family ipv4 unicast export to default-vrf route-policy dyna-route-leak-aspath-prefix-comm-29-x   export route-target    1:4   Vrf entry for the route:   RP/0/RSP0/CPU0:vc#sh bgp vrf vrf4 29.0.0.0 Wed Jan 16 11:54:34.259 PST BGP routing table entry for 29.0.0.0/30, Route Distinguisher: 1:4 …… ……….   Show command to see exported route in the global table     RP/0/RSP0/CPU0:vc#sh bgp 29.0.0.0 Wed Jan 16 11:54:51.833 PST BGP routing table entry for 29.0.0.0/30 …….. ……..        Origin incomplete, localpref 100, valid, external, best, group-best, import-candidate, imported ……   RP/0/RSP0/CPU0:vc#sh cef 29.0.0.0 Wed Jan 16 11:54:56.327 PST 29.0.0.0/30, version 2059125, internal 0x14004001 (ptr 0x72d4c304) [1], 0x0 (0x75554448), 0x400 (0x754fa470) …….. next hop VRF - 'vrf4', table - 0xe0000045 …….     3) Common prefixes imported to multiple vrf's   Cisco Configuration on the router route-policy dyna-route-leak-8-x if destination in (12.0.0.0/24) then     pass   endif end-policy   vrf vrf1 address-family ipv4 unicast import from default-vrf route-policy dyna-route-leak-8-x     Similarly this route-policy can be imported under multiple vrf to import this prefix.   Global entry for the route   RP/0/RSP0/CPU0:vc#sh bgp 12.0.0.0/24 Wed Jan 16 12:05:11.712 PST BGP routing table entry for 12.0.0.0/24 ……. ……….   Show command to see route imported in multiple vrf’s     VRF1:   RP/0/RSP0/CPU0:vc#sh bgp vrf vrf1 12.0.0.0/24 Wed Jan 16 12:05:30.630 PST BGP routing table entry for 12.0.0.0/24, Route Distinguisher: 3.3.3.3:0   VRF2:   RP/0/RSP0/CPU0:vc#sh bgp vrf vrf2 12.0.0.0/24 Wed Jan 16 12:07:08.524 PST BGP routing table entry for 12.0.0.0/24, Route Distinguisher: 1:2   VRF3:   RP/0/RSP0/CPU0:vc#sh bgp vrf vrf3 12.0.0.0/24 Wed Jan 16 12:07:12.441 PST BGP routing table entry for 12.0.0.0/24, Route Distinguisher: 1:3   VRF4:   RP/0/RSP0/CPU0:vc#sh bgp vrf vrf4 12.0.0.0/24 Wed Jan 16 12:07:17.185 PST BGP routing table entry for 12.0.0.0/24, Route Distinguisher: 1:4     Vrf entry in all the vrf’s:   RP/0/RSP0/CPU0:vc#sh bgp vrf vrf1 12.0.0.0/24 Wed Jan 16 12:05:30.630 PST BGP routing table entry for 12.0.0.0/24, Route Distinguisher: 3.3.3.3:0 ……. ……….      Origin incomplete, localpref 100, valid, internal, best, group-best, import-candidate, imported      ……….   RP/0/RSP0/CPU0:vc#sh bgp vrf vrf2 12.0.0.0/24 Wed Jan 16 12:07:08.524 PST BGP routing table entry for 12.0.0.0/24, Route Distinguisher: 1:2 …… ……… Origin incomplete, localpref 100, valid, internal, best, group-best, import-candidate, imported ……   RP/0/RSP0/CPU0:vc#sh bgp vrf vrf3 12.0.0.0/24 Wed Jan 16 12:07:12.441 PST BGP routing table entry for 12.0.0.0/24, Route Distinguisher: 1:3 …….. ……..      Origin incomplete, localpref 100, valid, internal, best, group-best, import-candidate, imported ……   RP/0/RSP0/CPU0:vc#sh bgp vrf vrf4 12.0.0.0/24 Wed Jan 16 12:07:17.185 PST BGP routing table entry for 12.0.0.0/24, Route Distinguisher: 1:4 ……. ……      Origin incomplete, localpref 100, valid, internal, best, group-best, import-candidate, imported ….......   Traffic Scenarios 4 a) CISCO vrf ----> Junos global Traffic direction: Cisco ----> Junos 27.0.0.0(vrf2) ----> 9.0.0.0   Dynamic route-leaking based on Community on Cisco ASR9K: -Import from default-vrf   Cisco configuration on the router route-policy dyna-route-leak-comm-9-x   if community matches-every (65008:9) then     pass   endif end-policy   vrf vrf2 address-family ipv4 unicast   import from default-vrf route-policy dyna-route-leak-comm-9-x   Global entry for 9.0.0.0 on Cisco ASR9K:   RP/0/RSP0/CPU0:vc#sh bgp 9.0.0.0 Wed Feb 13 00:33:04.007 PST BGP routing table entry for 9.0.0.0/24 …… …….   Route as seen in CISCO vrf table after route-leaking   RP/0/RSP0/CPU0:vc#sh bgp vrf vrf2 9.0.0.0 Wed Feb 13 00:33:56.913 PST BGP routing table entry for 9.0.0.0/24, Route Distinguisher: 1:2 ……. ………. Origin incomplete, localpref 100, valid, internal, best, group-best, import- candidate, imported ……..   Cef entry for the route:   RP/0/RSP0/CPU0:vc#sh cef vrf vrf2 9.0.0.0 Wed Feb 13 00:37:02.628 PST 9.0.0.0/24, version 150018, internal 0x14000001 (ptr 0x74e1ef84) [1], 0x0 (0x0), 0x0 (0x0) …… ……    next hop VRF - 'default', table - 0xe0000000 ……..        b) Junos Global ----> Cisco vrf Traffic direction : Junos --> Cisco 9.0.0.0 --> 27.0.0.0(vrf2)   Dynamic route-leaking based on Community on Cisco ASR9K: -Export to default vrf: Cisco configuration on the router route-policy dyna-route-leak-comm-27-x   if community matches-every (65004:27) then     pass   endif end-policy ! vrf vrf2 address-family ipv4 unicast export to default-vrf route-policy dyna-route-leak-comm-27-x   Vrf entry for the route: RP/0/RSP0/CPU0:vc#sh bgp vrf vrf2 27.0.0.0                     Wed Feb 13 00:20:02.109 PST BGP routing table entry for 27.0.0.0/30, Route Distinguisher: 1:2 …… ……   Route as seen in CISCO Global table after route-leaking   RP/0/RSP0/CPU0:vc#sh bgp 27.0.0.0 Wed Feb 13 00:23:13.598 PST BGP routing table entry for 27.0.0.0/30 …… ……      Origin EGP, localpref 100, valid, external, best, group-best, import-candidate, imported …….   CEF entry for the route: RP/0/RSP0/CPU0:vc#sh cef 27.0.0.0 Wed Feb 13 00:22:19.199 PST 27.0.0.0/30, version 357462, internal 0x14000001 (ptr 0x71cedfe0) [1], 0x0 (0x73a9a798), 0x400 (0x74690070) …… ……    next hop VRF - 'vrf2', table - 0xe0000012 ……..   5 a) Cisco global ----> Junos vrf Traffic direction: cisco ----->  junos 16.0.0.0---- 15.0.0.0(vrf1)   Route-leaking on Juniper ----- vrf to global:   Juniper configuration on the node root@MX960# show routing-instances vrf1 instance-type vrf; interface xe-5/1/0.101; route-distinguisher 1:1; vrf-import vrf1-import; vrf-export vrf1-export{ routing-options {     auto-export; } protocols {     bgp {         family inet {             unicast;         }         group ROUTE-LEAK {             type external;             family inet {                 unicast {                     rib-group vrf1-to-global;                 }             }             neighbor 192.7.1.2 {                 peer-as 65002;             }         }                                   } }     Route as seen in Juniper Global table after route-leaking   root@MX960# run show route 15.0.0.0 inet.0: 70048 destinations, 70054 routes (70048 active, 0 holddown, 0 hidden) @ = Routing Use Only, # = Forwarding Use Only + = Active Route, - = Last Active, * = Both 15.0.0.0/24       *[BGP/170] 00:14:03, localpref 100                     AS path: 65002 ?                    > to 192.7.1.2 via xe-5/1/0.101 vrf1.inet.0: 20038 destinations, 20038 routes (20038 active, 0 holddown, 0 hidden) + = Active Route, - = Last Active, * = Both 15.0.0.0/24       *[BGP/170] 18:34:44, localpref 100                      AS path: 65002 ?                    > to 192.7.1.2 via xe-5/1/0.101          b) Junos vrf ----> Cisco global Traffic direction: Junos ----->CISCO 15.0.0.0(vrf1)---- 16.0.0.0   Route-leaking on Juniper global--- to----vrf:   Juniper configuration on the node root@MX960# show protocols bgp group ROUTE-LEAK-internal type internal; family inet {     unicast {         rib-group global-to-vrf1;     } } local-as 65000; neighbor 3.3.3.3 {     local-address 6.6.6.6     peer-as 65000; }     Route as seen in Juniper vrf table after route-leaking     root@MX960# run show route 16.0.0.0 inet.0: 70048 destinations, 70054 routes (70048 active, 0 holddown, 0 hidden) @ = Routing Use Only, # = Forwarding Use Only + = Active Route, - = Last Active, * = Both 16.0.0.0/24       *[BGP/170] 00:58:02, localpref 100, from 3.3.3.3                      AS path: 65010 ?                    > to 12.1.1.2 via xe-5/2/0.0 vrf1.inet.0: 20038 destinations, 20038 routes (20038 active, 0 holddown, 0 hidden) + = Active Route, - = Last Active, * = Both 16.0.0.0/24       *[BGP/170] 00:05:43, localpref 100, from 3.3.3.3                      AS path: 65010 ?                    > to 12.1.1.2 via xe-5/2/0.0   6 a) CISCO vrf -----> Junos vrf Traffic direction: CISCO (26.0.0.0) VRF1------- JUNOS (15.0.0.0) VRF1   Dynamic route-leaking configuration on CISCO ASR9K route-policy dyna-route-leak-15-x   if destination in (15.0.0.0/24) then     pass   endif end-policy   vrf vrf1 address-family ipv4 unicast   import from default-vrf route-policy dyna-route-leak-15     Route as seen in CISCO vrf table after route-leaking   RP/0/RSP0/CPU0:vc#sh bgp vrf vrf1 15.0.0.0 Thu Feb 7 10:44:05.506 PST BGP routing table entry for 15.0.0.0/24, Route Distinguisher: 1:1 ……. ……. Not advertised to any peer 65002    6.6.6.6 (metric 1) from 6.6.6.6 (6.6.6.6)      Origin incomplete, localpref 100, valid, internal, best, group-best, import-candidate, imported      Received Path ID 0, Local Path ID 1, version 128819      Extended community: RT:1:1      Source VRF: default, Source Route Distinguisher: 0:0        b) Junos vrf ----> Cisco vrf Traffic direction: JUNOS (15.0.0.0) VRF1------- CISCO (26.0.0.0) VRF1     Header 1 route-policy dyna-route-leak-26-x   if destination in (26.0.0.0/30) then     pass endif end-policy !   vrf vrf1 address-family ipv4 unicast export to default-vrf route-policy dyna-route-leak-26-x   Route as seen in Juniper vrf table after route-leaking   root@MX960# run show route 26.0.0.0   inet.0: 60028 destinations, 60034 routes (60028 active, 0 holddown, 0 hidden) @ = Routing Use Only, # = Forwarding Use Only + = Active Route, - = Last Active, * = Both 26.0.0.0/30       *[BGP/170] 00:00:03, localpref 100, from 3.3.3.3                      AS path: 65002 ?                    > to 12.1.1.2 via xe-5/2/0.0 vrf1.inet.0: 10018 destinations, 10018 routes (10018 active, 0 holddown, 0 hidden) + = Active Route, - = Last Active, * = Both 26.0.0.0/30       *[BGP/170] 00:00:03, localpref 100, from 3.3.3.3                      AS path: 65002 ?                    > to 12.1.1.2 via xe-5/2/0.0     References N/A   Related Information   Sheetal Bhogale Software Engineer, ASR9K SIT Team ... View more