Sei sulla pagina 1di 10

Gather info on ckt and topology of ingress/egress layer-2 interfaces.

RP/0/RSP0/CPU0:DLLFTXFQ9K002#sh int desc | i 44/KEFN/117489/TWCS


BE41.2700 up up 44/KEFN/117489/TWCS - DATA TECHNOLOGY SOLUTIONS # 288301 [SNLAN]
BE70.2700 up up 44/KEFN/117489/TWCS - DATA TECHNOLOGY SOLUTIONS # 288301 [SNLAN]

RP/0/RSP0/CPU0:DLLFTXFQ9K002#sh run int bundle-ether 41 | i descr


description to SHPTLA144A001
RP/0/RSP0/CPU0:DLLFTXFQ9K002#sh bundle bundle-ether 41 | i Te
Te0/0/0/23 Local Active 0x8000, 0x000e 10000000
Te0/7/0/23 Local Active 0x8000, 0x000d 10000000

RP/0/RSP0/CPU0:DLLFTXFQ9K002#sh run int bundle-ether 70 | i descr


description to DLLFTXFQC6003
RP/0/RSP0/CPU0:DLLFTXFQ9K002#sh bundle bundle-ether 70 | i Te
Te0/0/0/8 Local Active 0x8000, 0x000a 10000000
Te0/7/0/8 Local Active 0x8000, 0x000c 10000000
Gather info on the ingress/egress interface and corresponding BD:

- Note there are two ACs Be41.2700 and Be70.2700, and one VFI to the other 9k
- Note name of bridge-domain and VFI: '4323_303956'. The BD name is the key info to get from this output
- VFI neighbor IP 10.254.240.64 is the Lo0 interface of the other 9k DLLFTXFQ9K001 (other side of the PW)
- Note for simplicity the bridge group, bridge domain, vfi and route target are usually named the same
- For customer BDs, the first number (4323) is usually same as BGP AS #

RP/0/RSP0/CPU0:DLLFTXFQ9K002#sh l2vpn bridge-domain interface bundle-ether 41.2700 brief


Legend: pp = Partially Programmed.
Bridge Group:Bridge-Domain Name ID State Num ACs/up Num PWs/up
-------------------------------- ----- -------------- ------------ -------------
4323_303956:4323_303956 16 up 2/2 1/1

RP/0/RSP0/CPU0:DLLFTXFQ9K002#sh l2vpn bridge-domain interface bundle-ether 70.2700 brief


Legend: pp = Partially Programmed.
Bridge Group:Bridge-Domain Name ID State Num ACs/up Num PWs/up
-------------------------------- ----- -------------- ------------ -------------
4323_303956:4323_303956 16 up 2/2 1/1

- Take note all ACs in that BD and any Access PWs (ie: xconnects to ME-3600 in future)

RP/0/RSP0/CPU0:DLLFTXFQ9K002#sh l2vpn bridge-domain bd-name 4323_303956


Legend: pp = Partially Programmed.
Bridge group: 4323_303956, bridge-domain: 4323_303956, id: 16, state: up, ShgId: 0, MSTi: 0
Aging: 300 s, MAC limit: 4000, Action: none, Notification: syslog
Filter MAC addresses: 0
ACs: 2 (2 up), VFIs: 1, PWs: 1 (1 up), PBBs: 0 (0 up)
List of ACs:
BE41.2700, state: up, Static MAC addresses: 0
BE70.2700, state: up, Static MAC addresses: 0
List of Access PWs:
List of VFIs:
VFI 4323_303956 (up)
Neighbor 10.254.240.64 pw-id 4323:139, state: up, Static MAC addresses: 0
Check for incrementing traffic statistics on Ingress/Egress interfaces
for that bridge-domain and the PW

- Also check that PW is up and established


- Note that PW neighbor 10.254.240.64 is the other 9k -> DLLFTXFQ9K001

RP/0/RSP0/CPU0:DLLFTXFQ9K002#sh l2vpn bridge-domain bd-name 4323_303956 detail | i "state|VFI:|VLAN


ranges|received"
Bridge group: 4323_303956, bridge-domain: 4323_303956, id: 16, state: up, ShgId: 0, MSTi: 0
Coupled state: disabled
AC: Bundle-Ether41.2700, state is up
VLAN ranges: [2700, 2700]
packets: received 16153915, sent 45770455
bytes: received 1271296619, sent 8889907609
AC: Bundle-Ether70.2700, state is up
VLAN ranges: [2700, 2700]
packets: received 45770435, sent 16039060
bytes: received 8889905607, sent 1262535476
VPN-ID: 139, Auto Discovery: BGP, state is Provisioned (Service Connected)
PW: neighbor 10.254.240.64, PW ID 4323:139, state is up ( established )
packets: received 0, sent 61361238
bytes: received 0, sent 9710627809

RP/0/RSP0/CPU0:DLLFTXFQ9K002#sh l2vpn bridge-domain bd-name 4323_303956 detail | i "state|VFI:|VLAN


ranges|received"
Bridge group: 4323_303956, bridge-domain: 4323_303956, id: 16, state: up, ShgId: 0, MSTi: 0
Coupled state: disabled
AC: Bundle-Ether41.2700, state is up
VLAN ranges: [2700, 2700]
packets: received 16153926, sent 45770566
bytes: received 1271298565, sent 8889934962
AC: Bundle-Ether70.2700, state is up
VLAN ranges: [2700, 2700]
packets: received 45770555, sent 16039069
bytes: received 8889926772, sent 1262537074
VPN-ID: 139, Auto Discovery: BGP, state is Provisioned (Service Connected)
PW: neighbor 10.254.240.64, PW ID 4323:139, state is up ( established )
packets: received 0, sent 61361310
bytes: received 0, sent 9710640310

Can also check sub-int traffic stats:


sh int bundle-eth 41.2700 | i "line|packets"
sh int bundle-eth 70.2700 | i "line|packets"
Verify mac addresses are learned in the bridge-domain:

- For Location use same LC as previously found to be the physical for the BE (Ie: 0/0/CPU0 or 0/7/CPU0 here)

RP/0/RSP0/CPU0:DLLFTXFQ9K002#sh l2vpn forwarding bridge-domain 4323_303956:4323_303956 mac-address location


0/0/CPU0
Mac Address Type Learned from/Filtered on LC learned Resync Age Mapped to
--------------------------------------------------------------------------------
000f.24a7.3bc1 dynamic BE41.2700 0/0/CPU0 0d 0h 0m 3s N/A
fc99.471e.7708 dynamic BE41.2700 0/0/CPU0 0d 0h 0m 3s N/A
0000.0c07.ac01 dynamic BE70.2700 0/0/CPU0 0d 0h 0m 1s N/A
000f.23e3.5f01 dynamic BE70.2700 0/0/CPU0 0d 0h 0m 7s N/A
<snip>
If needed, check for MPLS label forwarding stats across the PW

Also can use ‘show mpls forwarding’ to see which labels (and corresponding BDs) have traffic forwarded via VPLS

RP/0/RSP0/CPU0:DLLFTXFQ9K002#show l2vpn bridge-domain bd-name 4323_303956 detail | i "MPLS|Label"


Encapsulation MPLS, Auto-discovered (BGP), protocol LDP
MPLS Local Remote
Label 16027 16024
(Ie: you should expect to see the opposite of the above on 9k1)

RP/0/RSP0/CPU0:DLLFTXFQ9K002#sh mpls forwarding labels 16027


Local Outgoing Prefix Outgoing Next Hop Bytes
Label Label or ID Interface Switched
------ ----------- ------------------ ------------ --------------- ------------
16027 Pop PW(10.254.240.64:10016005575081462272) \
BD=16 point2point 0

Above indicates no traffic over the PW. But if we check management BD, you will see MPLS traffic to other 9k1:
Example:

RP/0/RSP0/CPU0:DLLFTXFQ9K002#show l2vpn bridge-domain bd-name 512_management detail | i "MPLS|Label"


Encapsulation MPLS, Auto-discovered (BGP), protocol LDP
MPLS Local Remote
Label 16014 16011

RP/0/RSP0/CPU0:DLLFTXFQ9K002#sh mpls forwarding labels 16014


Local Outgoing Prefix Outgoing Next Hop Bytes
Label Label or ID Interface Switched
------ ----------- ------------------ ------------ --------------- ------------
16014 Pop PW(10.254.240.64:562953762900480) \
BD=3 point2point 2591660315

RP/0/RSP0/CPU0:DLLFTXFQ9K002#sh mpls forwarding labels 16014


Local Outgoing Prefix Outgoing Next Hop Bytes
Label Label or ID Interface Switched
------ ----------- ------------------ ------------ --------------- ------------
16014 Pop PW(10.254.240.64:562953762900480) \
BD=3 point2point 2591667825

Note: Can also check ‘sh mpls forwarding labels’ to see all BD over VPLS
Verify MPLS OSPF, BGP neighbors:

RP/0/RSP0/CPU0:DLLFTXFQ9K002#sh mpls ldp neighbor


RP/0/RSP0/CPU0:DLLFTXFQ9K002#sh ospf nei

- Verify L2VPN Discovery and prefixes received via VPLS


- Number of prefixes received should match # of VFIs sent from the peer 9k(s).

RP/0/RSP0/CPU0:DLLFTXFQ9K002#sh bgp l2vpn vpls summary


BGP router identifier 10.254.240.65, local AS number 4323
BGP generic scan interval 60 secs
Non-stop routing is enabled
BGP table state: Active
Table ID: 0x0 RD version: 3911677
BGP main routing table version 83
BGP NSR Initial initsync version 39 (Reached)
BGP scan interval 60 secs

BGP is operating in STANDALONE mode.

Process RcvTblVer bRIB/RIB LabelVer ImportVer SendTblVer StandbyVer


Speaker 83 83 83 83 83 83

Neighbor Spk AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down St/PfxRcd


10.254.240.64 0 4323 45210 45210 83 0 0 4w3d 22

- Check for that BD, confirm you see two prefixes for local/remote ASR9k:

RP/0/RSP0/CPU0:DLLFTXFQ9K002#sh bgp l2vpn vpls bdomain 4323_303956:4323_303956


BGP router identifier 10.254.240.65, local AS number 4323
BGP generic scan interval 60 secs
Non-stop routing is enabled
BGP table state: Active
Table ID: 0x0 RD version: 3964894
BGP main routing table version 83
BGP NSR Initial initsync version 39 (Reached)
BGP scan interval 60 secs

Status codes: s suppressed, d damped, h history, * valid, > best


i - internal, r RIB-failure, S stale
Origin codes: i - IGP, e - EGP, ? - incomplete
Network Next Hop Rcvd Label Local Label
Route Distinguisher: 10.254.240.65:32784 (default for vrf 4323_303956:4323_303956)
*>i10.254.240.64/32 10.254.240.64 nolabel nolabel
*> 10.254.240.65/32 0.0.0.0 nolabel nolabel

Processed 2 prefixes, 2 paths


Verify Traffic-Eng Tunnel status

Hop 0 IP corresponds with BE physical IP of remote

RP/0/RSP0/CPU0:DLLFTXFQ9K002#sh mpls traffic-eng tunnels | i "Name|Admin|Hop"


Name: tunnel-te1 Destination: 10.254.240.64
Admin: up Oper: up Path: valid Signalling: connected
Hop-limit: disabled
Hop0: 10.254.240.37
Hop1: 10.254.240.64
Name: tunnel-te2 Destination: 10.254.240.64
Admin: up Oper: up Path: valid Signalling: connected
Hop-limit: disabled
Hop0: 10.254.240.37
Hop1: 10.254.240.64
Name: tunnel-te3 Destination: 10.254.240.64
Admin: up Oper: up Path: valid Signalling: connected
Hop-limit: disabled
Hop0: 10.254.240.37
Hop1: 10.254.240.64
Name: tunnel-te4 Destination: 10.254.240.64
Admin: up Oper: up Path: valid Signalling: connected
Hop-limit: disabled
Hop0: 10.254.240.33
Hop1: 10.254.240.64
Name: tunnel-te50000 Destination: 10.254.240.64 (auto-tunnel backup)
Admin: up Oper: up Path: valid Signalling: connected
Hop-limit: disabled
Hop0: 10.254.240.37
Hop1: 10.254.240.64
Name: tunnel-te50001 Destination: 10.254.240.64 (auto-tunnel backup)
Admin: up Oper: up Path: valid Signalling: connected
Hop-limit: disabled
Hop0: 10.254.240.33
Hop1: 10.254.240.64
Verify Traffic-Eng Tunnel status

RP/0/RSP0/CPU0:DLLFTXFQ9K002#sh mpls traffic-eng tunnels brief


TUNNEL NAME DESTINATION STATUS STATE
tunnel-te1 10.254.240.64 up up
tunnel-te2 10.254.240.64 up up
tunnel-te3 10.254.240.64 up up
tunnel-te4 10.254.240.64 up up
*tunnel-te50000 10.254.240.64 up up
*tunnel-te50001 10.254.240.64 up up
DLLFTXFQ9K001_t1 10.254.240.65 up up
DLLFTXFQ9K001_t2 10.254.240.65 up up
DLLFTXFQ9K001_t3 10.254.240.65 up up
DLLFTXFQ9K001_t4 10.254.240.65 up up
autob_DLLFTXFQ9K00 10.254.240.65 up up
autob_DLLFTXFQ9K00 10.254.240.65 up up
* = automatically created backup tunnel
Displayed 6 (of 6) heads, 0 (of 0) midpoints, 6 (of 6) tails
Displayed 6 up, 0 down, 0 recovering, 0 recovered heads

RP/0/RSP0/CPU0:DLLFTXFQ9K002#show mpls traffic-eng link-management admission-control


System Information::
Tunnels Count : 6
Tunnels Selected : 6

Bandwidth descriptor legend:


B0 = bw from pool 0, B1 = bw from pool 1, R = bw locked, H = bw held

TUNNEL ID UP IF DOWN IF PRI STATE BW (kbits/sec)


------------------------ ---------- ---------- --- ------------- ---------------
10.254.240.65 1_6 - BE2 7/7 Resv Admitted 5000000 RB0
10.254.240.65 2_6 - BE2 7/7 Resv Admitted 5000000 RB0
10.254.240.65 3_6 - BE2 7/7 Resv Admitted 5000000 RB0
10.254.240.65 4_8 - BE1 7/7 Resv Admitted 5000000 RB0
10.254.240.65 50000_2 - BE2 7/7 Resv Admitted 0 B0
10.254.240.65 50001_2 - BE1 7/7 Resv Admitted 0 B0
MISC

Check STP TCNs:


sh spanning-tree mstag DLLFTXFQC6001 topology-change flushes

Check MAC withdraw status and counters:


RP/0/RSP0/CPU0:DLLFTXFQ9K002# sh l2vpn bridge-domain bd-name 4323_303956 detail | i MAC withdraw
MAC withdraw: enabled
MAC withdraw for Access PW: enabled
MAC withdraw sent on bridge port down: enabled
MAC withdraw message: send 2146 receive 0

Summary of bridge domains and PWs


sh l2vpn bridge-domain brief

Summary of total macs, total bridge domains etc…


sh l2vpn forwarding summary location 0/0/CPU

=======================================================================================================
Storm Control Drop counters:
=======================================================================================================
RP/0/RSP0/CPU0:DLLFTXFQ9K002#sh l2vpn bridge-domain bd-name 512_management detail | i "AC:|control
drop|broadcast"
AC: BVI512, state is up
AC: Bundle-Ether10.512, state is down (Segment-down), standby in RG-ID 1
AC: Bundle-Ether11.512, state is down (Segment-down), standby in RG-ID 1
AC: Bundle-Ether20.512, state is up, active in RG-ID 1
Storm control drop counters:
packets: broadcast 0, multicast 0, unknown unicast 0
bytes: broadcast 0, multicast 0, unknown unicast 0
AC: Bundle-Ether41.512, state is up
Storm control drop counters:
packets: broadcast 0, multicast 0, unknown unicast 300
bytes: broadcast 0, multicast 0, unknown unicast 38296
AC: Bundle-Ether70.512, state is up
Storm control drop counters:
packets: broadcast 0, multicast 0, unknown unicast 14
bytes: broadcast 0, multicast 0, unknown unicast 914
Note connections between the 9ks:

RP/0/RSP0/CPU0:DLLFTXFQ9K002#sh bundle bundle-ether 1 | i Te


Te0/0/0/4 Local Active 0x8000, 0x0006 10000000
Te0/0/0/5 Local Active 0x8000, 0x0007 10000000
RP/0/RSP0/CPU0:DLLFTXFQ9K002#sh bundle bundle-ether 2 | i Te
Te0/7/0/4 Local Active 0x8000, 0x0001 10000000
Te0/7/0/5 Local Active 0x8000, 0x0002 10000000

RP/0/RSP0/CPU0:DLLFTXFQ9K002#sh cdp nei | i Te


DLLFTXFQ9K001.t Te0/0/0/4 167 R ASR9K Ser Te0/0/0/4
DLLFTXFQ9K001.t Te0/0/0/5 171 R ASR9K Ser Te0/0/0/5
DLLFTXFQ9K001.t Te0/7/0/4 124 R ASR9K Ser Te0/7/0/4
DLLFTXFQ9K001.t Te0/7/0/5 127 R ASR9K Ser Te0/7/0/5

Potrebbero piacerti anche