Don't like ads? PRO users don't see any ads ;-)
Public Pastes
Guest

Untitled

By: a guest on Aug 1st, 2012  |  syntax: None  |  size: 2.17 KB  |  hits: 16  |  expires: Never
download  |  raw  |  embed  |  report abuse  |  print
Text below is selected. Please press Ctrl+C to copy to your clipboard. (⌘+C on Mac)
  1. ============================================================================
  2. Kompella
  3. ============================================================================
  4.  
  5. # Kompella uses MP-BGP to signal traffic.  Be sure to enable family l2vpn
  6. #  to the IBGP routers
  7. set protocols bgp <group> neighbor <ip> family l2vpn signaling
  8.  
  9. # Set the correct physical interface encap to vlan-ccc
  10. set interfaces <name> encapsulation vlan-ccc
  11.  
  12. # Set the logical interface/unit encap to vlan-ccc (that hands off to the CE)
  13. set interfaces <name>.<unit> encapsulation vlan-ccc
  14.  
  15. # Since kompella uses MP-BGP for signalling you need to create a
  16. #  routing-instance.  Remember you need to setup a BGP community for the
  17. #  RT.  The RTs must match between PEs.  The protocol l2vpn needs to be
  18. #  defined on each PE.  The site-identifier must be UNIQUE!!!
  19. #
  20. c1-c2-l2 {
  21.    instance-type l2vpn;
  22.    interface ge-1/2/8.600;                             (CE interface)
  23.    vrf-import c1-c2-import;
  24.    vrf-export c1-c2-export;
  25.    protocols {
  26.        l2vpn {
  27.            encapsulation-type ethernet-vlan;
  28.            site 2 {
  29.                site-identifier 2;                      (must be unique)
  30.                interface ge-1/2/8.600;                 (CE interface)
  31.            }
  32.        }
  33.    }
  34. }
  35.  
  36. # vrf-export
  37. policy-statement c1-c2-export {
  38.    then {
  39.        community add c1-c2-rt;
  40.        accept;
  41.    }
  42. }
  43.  
  44. # vrf-import
  45. policy-statement c1-c2-import {
  46.    term 1 {
  47.        from {
  48.            protocol bgp;
  49.            community c1-c2-rt;
  50.        }
  51.        then accept;
  52.    }
  53. }
  54.  
  55. set policy-options community c1-c2-rt members target:65412:7 (must match)
  56.  
  57. # If you want to map traffic to an LSP, you need to setup a policy and install
  58. #  the LSP.  A good method is to simply match on the BGP community used for
  59. #  the RT.  Don't forget to install the policy into the fowarding-table.
  60. policy-statement mapping {
  61.    term 1 {
  62.        from community c1-c2-rt;
  63.        then {
  64.            install-nexthop lsp r6-r4-prime;
  65.            accept;
  66.        }
  67.    }
  68.    term 2 {                    (default catch all for other traffic)
  69.        then accept;
  70.    }
  71. }
  72.  
  73. set routing-options forwarding-table export mapping
create a new version of this paste RAW Paste Data