Вы находитесь на странице: 1из 12

FTELS NEW METRO ACCESS

NETWORK
PILOT PHASE
TRAINING DOCUMENT

ISIS Configuration checklist

Plan ISO address


Plan ISIS zone
Set up ISO address on loopback interface
Enable family ISO on all interconnect interface
Configure loopback interface in ISIS
Configure ISIS interface with the correct level and connection type
Additional step: configure wide-metric-only

Useful command
//check neighboring state
Show isis adjacency
Show isis hostname
//check interface configuration
Show isis interface
//check isis route
Show isis route
Show route protocol isis

ISIS routing policy checklist

Advertise nothing from core to access zone


Advertise nothing from access to core zone

Useful command
//check policys impact by displaying isis route on L2 or L1 routers
Show isis route
Show route protocol isis

LDP configuration checklist

Enable family mpls on all interconnect interface


Configure loopback interface in LDP
Configure LDP interface
Additional step:
o Enable track-igp-metric
o Enable deaggregate
o Enable LDP-synchronization in ISIS

Useful command
//check ldp neighboring and interface state
Show ldp interface
Show ldp neighbor
Show ldp session
//check ldp label and path distribution
Show ldp database
Show ldp path
//check label distribution and forwarding action
Show route table mpls.0
//check ldp path on inet.3 table
Show route protocol ldp table inet.3
//traceroute/ping using MPLS label switched path
run ping mpls ldp remote-loopback-IP detail
run traceroute mpls ldp remote-loopback-IP detail

BGP configuration checklist

Plan BGP peering method


Plan cluster ID
Set up AS number
Configure BGP peer with the follow parameter
o Peering type: IBGP or EBGP
o Local-address
o Local-as (for EBGP)
o Authentication key
o Peer address (neighbor statement)
Additionally, configure cluster ID on routers that act as Route Reflector

Useful command
//check bgp neighboring state
Show bgp summary
Show bgp neighbor

Note: ESTABLISHED state only appear if MP-BGP is configuration (i.e more than one family support
is configuration inside protocol bgp {} stanza). If only normal BGP session is configured, the session
state will be display in the form x/x/x/x after established.
Otherwise IDLE or ACTIVE or CONNECT state indicate BGP session error.
juniper@vMX# run show bgp summary logical-system HN-UPE1
Groups: 1 Peers: 2 Down peers: 0
Table
Tot Paths Act Paths Suppressed
History Damp State
Pending
inet.0
2
1
0
0
0
0
inet.3
22
9
0
0
0
0
bgp.l2vpn.0
4
2
0
0
0
0
Peer
AS
InPkt
OutPkt
OutQ
Flaps Last Up/Dwn State|
#Active/Received/Accepted/Damped...
10.0.1.11
18403
103
68
0
1
29:01 Establ
inet.0: 1/1/1/0 > by default only these number are displayed
inet.3: 7/11/11/0 > Additional line for a neighbor only appear if MP-BGP is configured
bgp.l2vpn.0: 0/2/2/0
L2VPN-CUSTOMER1.l2vpn.0: 0/2/2/0
10.0.1.12
18403
77
66
0
0
28:15 Establ
inet.0: 0/1/1/0
inet.3: 2/11/11/0
bgp.l2vpn.0: 2/2/2/0
L2VPN-CUSTOMER1.l2vpn.0: 2/2/2/0

BGP policy

Perform next-hop self to


o Advertise BGP and LDP route in inet.3 route from access to core
o Advertise BGP and LDP route in inet.3 from core to access
Advertise summed loopback of access zone to core perform next-hop self

Useful command
//check bgp route on a router
Show route protocol bgp
Show route protocol bgp table inet.3
//check to see which route are being advertised to a bgp neighbor
Show route advertising-protocol bgp neighbor-IP
Show route advertising-protocol bgp neighbor-IP table <inet.3/ bgp.l3vpn.0/ bgp.l2vpn.0>
//check to see which route are being received from a bgp neighbor
Show route receive-protocol bgp neighbor-IP
Show route receive-protocol bgp neighbor-IP table <inet.3/ bgp.l3vpn.0/ bgp.l2vpn.0>

RSVP configuration checklist

Enable family mpls on all interconnect interface


Configure RSVP interface with link-protection
Setup RSVP signaled LSP manually with
o Ldp-tunnelling
o Link-protection

Useful command
//check rsvp neighboring and interface state
Show rsvp interface
Show rsvp neighbor
//check rsvp labeL-switched-path state
Show mpls lsp <ingress/ egress/ transist>
Show rsvp session
//check rsvp path on inet.3 table
Show route protocol rsvp table inet.3
//check label distribution and forwarding action
show route table mpls.0
//traceroute/ping using MPLS label switched path
run ping mpls lsp-end-point remote-loopback-IP detail
run traceroute mpls rsvp LSP-Name detail
//check LDP tunneling state
run traceroute mpls ldp remote-loopback-IP detail

L3VPN configuration checklist

Plan RT for customers service


Plan RD for customer on each site
Enable MP-BGP support for L3VPN
Configure L3VPN routing-instances RT (Instance-type vrf) with either
o Vrf-target statement
o Vrf-import and vrf-export statement
Configure L3VPN routing-instances RD
Ensure PE-CE link is advertised to remote PE router by either
o vrf-table-label
o Use static route to CE
o Use IGP peering with CE
Additional configuration: Create policy to advertise BGP route to CE with IGP peering.

Useful command
//check routing instances route
Show route table + Instance-name.inet.0
//check to see which route are being advertised to a bgp neighbor
Show route advertising-protocol bgp neighbor-IP table <inet.3/ bgp.l3vpn.0>
//check to see which route are being received from a bgp neighbor
Show route receive-protocol bgp neighbor-IP table <inet.3/ bgp.l3vpn.0>
//check table bgp.l3vpn.0 on transist/Route reflector router:
Show route table bgp.l3vpn.0 community + RT-vablue

L2VPN configuration checklist

Plan RT for customers service


Plan RD for customer on each site
Plan Site-identifier for customer on each site
Enable MP-BGP support for L2VPN
Enable the correct encapsulation-type (Ethernet-ccc or vlan-vpls) and family for
Configure L2VPN routing-instances RT with either method is L3VPN
Configure L2VPN routing-instances RD
Configure L2VPN routing-instance to run protocol l2vpn
o Set up protocol encapsulation-type with the same encapsulation-type as CE facing
interface
o Setup site-identifier
o Setup remote site-identifier inside CE facing interface
Additional step: perform vlan pop/push/swap to match two site

Useful command
//check L2VPN connection state Show l2vpn connection
//check to see which route are being advertised to a bgp neighbor
Show route advertising-protocol bgp neighbor-IP table <inet.3/ bgp.l3vpn.0>
//check to see which route are being received from a bgp neighbor
Show route receive-protocol bgp neighbor-IP table <inet.3/ bgp.l3vpn.0>
//check table bgp.l2vpn.0 on transist/Route reflector router:
Show route table bgp.l2vpn.0 community + RT-vablue

10

VPLS configuration checklist

Plan RT for customers service


Plan RD for customer on each site
Plan Site-identifier for customer on each site
Enable MP-BGP support for L2VPN signalling
Enable the correct encapsulation-type (Ethernet-vpls or vlan-vpls) and family for
Configure VPLS routing-instances RT with either method as L3VPN
Configure VPLS routing-instances RD
Configure VPLS routing-instance to run protocol l2vpn
o Setup site-identifier
o Setup site-range
o Setup CE facing interface
Additional step:
o perform vlan pop/push/swap to match between sites
o setup and vlan id/tags for VPLS instance to perform auto-normalization

Useful command
//check L2VPN connection state instances route
Show vpls connection
//check to see which route are being advertised to a bgp neighbor
Show route advertising-protocol bgp neighbor-IP table <inet.3/ bgp.l3vpn.0>
//check to see which route are being received from a bgp neighbor
Show route receive-protocol bgp neighbor-IP table <inet.3/ bgp.l3vpn.0>
//check table bgp.l2vpn.0 on transist/Route reflector router:
Show route table bgp.l2vpn.0 community + RT-vablue

11

12