[c-nsp] [ME6524] port based EoMPLS
Mateusz Błaszczyk
blahu77 at gmail.com
Mon Feb 25 07:59:56 EST 2008
List,
I would like to report a problem with ME6524s that I have in the testlab
network at the moment.
I am testing them since 4 weeks now and I hit a big show stopper.
At the moment I am concetrated on EoMPLS and checking the port-based (Type
5) EoMPLS cross-connects.
I am questioning their transparency.
Here is my simple topology.
[ME3400-A gi0/15] --- dot1q--- [gi1/5 ME6524-A gi1/32] ----mpls----[gi1/32
ME6524-B gi0/5] --dot1q trunk- [gi0/15 ME3400-B]
There is a VLAN505 stretched from ME3400-A to ME3400-B.
There are provisioned 2 SVIs on both these switches to check L3
connectivity.
Also the ME3400 switches are running spanning tree protocol - I have tested
PVST, PVST+ and MST alike (same final result)
I state that spanning tree BPDUs are not forwarded along the port-based
EoMPLS run on top of ME6524s.
On both sides there are only 140 packets received which 140 pings issued
from ME3400-A to ME3400-B.
ME6524-A:
ME6524-A#sh spanning-tree
No spanning tree instance exists.
ME6524-A#sh mpls l2transport vc 15 detail
Local interface: Gi1/5 up, line protocol up, Ethernet up
Destination address: 10.99.99.11, VC ID: 15, VC status: up
Output interface: Gi1/32, imposed label stack {16}
Preferred path: not configured
Default path: active
Next hop: 10.99.98.65
Create time: 00:16:27, last status change time: 00:02:57
Signaling protocol: LDP, peer 10.99.99.11:0 up
MPLS VC labels: local 16, remote 16
Group ID: local 0, remote 0
MTU: local 9216, remote 9216
Remote interface description:
Sequencing: receive disabled, send disabled
VC statistics:
packet totals: receive 140, send 163
byte totals: receive 17640, send 21306
packet drops: receive 0, send 0
ME6524-B#sh spanning-tree
No spanning tree instance exists.
ME6524-B#sh mpls l2transport vc 15 detail
Local interface: Gi1/5 up, line protocol up, Ethernet up
Destination address: 10.99.99.10, VC ID: 15, VC status: up
Output interface: Gi1/32, imposed label stack {16}
Preferred path: not configured
Default path: active
Next hop: 10.99.98.64
Create time: 00:08:20, last status change time: 00:02:53
Signaling protocol: LDP, peer 10.99.99.10:0 up
MPLS VC labels: local 16, remote 16
Group ID: local 0, remote 0
MTU: local 9216, remote 9216
Remote interface description:
Sequencing: receive disabled, send disabled
VC statistics:
packet totals: receive 140, send 158
byte totals: receive 17640, send 20371
packet drops: receive 0, send 0
Now let's ping Vl505 on ME3400-B from ME3400-A.
ME3400-A#ping 50.50.50.55 repeat 140
Type escape sequence to abort.
Sending 140, 100-byte ICMP Echos to 50.50.50.55, timeout is 2 seconds:
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Success rate is 100 percent (140/140), round-trip min/avg/max = 1/3/17 ms
ME3400-A#sh spanning-tree interface gi0/15 detail
Port 15 (GigabitEthernet0/15) of MST0 is designated forwarding
Port path cost 20000, Port priority 128, Port Identifier 128.15.
Designated root has priority 24576, address 001e.1415.e180
Designated bridge has priority 24576, address 001e.1415.e180
Designated port id is 128.15, designated path cost 0
Timers: message age 0, forward delay 0, hold 0
Number of transitions to forwarding state: 1
Link type is point-to-point by default, Internal
BPDU: sent 201, received 0
ME3400-A#sh spanning-tree
MST0
Spanning tree enabled protocol mstp
Root ID Priority 24576
Address 001e.1415.e180
This bridge is the root
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Bridge ID Priority 24576 (priority 24576 sys-id-ext 0)
Address 001e.1415.e180
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Interface Role Sts Cost Prio.Nbr Type
------------------- ---- --- --------- --------
--------------------------------
Gi0/15 Desg FWD 20000 128.15 P2p
ME3400-B#sh spanning-tree
MST0
Spanning tree enabled protocol mstp
Root ID Priority 32768
Address 001e.1415.da00
This bridge is the root
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Bridge ID Priority 32768 (priority 32768 sys-id-ext 0)
Address 001e.1415.da00
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Interface Role Sts Cost Prio.Nbr Type
------------------- ---- --- --------- --------
--------------------------------
Gi0/15 Desg FWD 20000 128.15 P2p
ME3400-B#sh spanning-tree interface gigabitEthernet 0/15 detail
Port 15 (GigabitEthernet0/15) of MST0 is designated forwarding
Port path cost 20000, Port priority 128, Port Identifier 128.15.
Designated root has priority 32768, address 001e.1415.da00
Designated bridge has priority 32768, address 001e.1415.da00
Designated port id is 128.15, designated path cost 0
Timers: message age 0, forward delay 0, hold 0
Number of transitions to forwarding state: 1
Link type is point-to-point by default, Internal
BPDU: sent 714, received 0
As you see the ME6524s are not running spanning tree - even for internal
vlans used for EoMPLS, so according with the documentation the received
BPDUs are to be forwarded into the xconnect and not to the switch CPU for
processing.
Furthermore both ME3400 are thinking they are roots in the spanning tree
topology.
As I said before I have tested the same setup with PVST, PVST+, MST
achieving the same results.
When I debug bpdu packets on ME3400 I see only transmit messages. When I
debug the BPDU on ME6524 (no spanning tree running) I see no messages coming
in.
I wonder if it is something wrong in my configuration (which follows) or I
hit some nasty bug.
I would appreciate any feedback.
Configurations:
ME6524-A#sh ver | i IOS
Cisco IOS Software, s3223_rp Software (s3223_rp-ADVIPSERVICESK9-VM), Version
12.2(33)SXH1, RELEASE SOFTWARE (fc3)
ME6524-A#sh run (fragments)
boot system disk0:/newsys/s6523/base/s6523-advipservicesk9-vm
boot system disk0:/newsys/lx10100/base/LCP_LX10100
boot system disk0:/newsys/s3223_rp/base/DRACO2_MP
vtp mode transparent
spanning-tree mode pvst
spanning-tree extend system-id
no spanning-tree vlan 1-4094
interface Loopback0
ip address 10.99.99.10 255.255.255.255
!
interface GigabitEthernet1/5
mtu 9216
no ip address
logging event link-status
logging event trunk-status
logging event spanning-tree status
logging event subif-link-status
load-interval 30
xconnect 10.99.99.11 15 encapsulation mpls
!
interface GigabitEthernet1/32
mtu 9216
ip address 10.99.98.64 255.255.255.254
logging event link-status
logging event trunk-status
logging event spanning-tree status
logging event subif-link-status
load-interval 30
mpls ip
!
router ospf 1
router-id 10.99.99.10
log-adjacency-changes
area 10 nssa
network 10.99.98.0 0.0.0.255 area 10
network 10.99.99.10 0.0.0.0 area 10
!
mpls ldp router-id Loopback0 force
ME6524-A#sh mpls forwarding-table detail
Local Outgoing Prefix Bytes Label Outgoing Next Hop
Label Label or Tunnel Id Switched interface
16 No Label l2ckt(15) 17640 none point2point
MAC/Encaps=0/0, MRU=0, Label Stack{}
No output feature configured
17 Pop Label 10.99.99.11/32 0 Gi1/32 10.99.98.65
MAC/Encaps=14/14, MRU=9220, Label Stack{}
00169D215DDE00169D21AD1C8847
No output feature configured
ME6524-B#sh ver | i IOS
Cisco IOS Software, s3223_rp Software (s3223_rp-ADVIPSERVICESK9-VM), Version
12.2(33)SXH1, RELEASE SOFTWARE (fc3)
ME6524-B#sh run
boot system disk0:/newsys/s6523/base/s6523-advipservicesk9-vm
boot system disk0:/newsys/lx10100/base/LCP_LX10100
boot system disk0:/newsys/s3223_rp/base/DRACO2_MP
vtp mode transparent
spanning-tree mode pvst
spanning-tree extend system-id
no spanning-tree vlan 1-4094
!
!
!
vlan internal allocation policy ascending
interface Loopback0
ip address 10.99.99.11 255.255.255.255
!
interface GigabitEthernet1/5
mtu 9216
no ip address
logging event link-status
logging event trunk-status
logging event spanning-tree status
logging event subif-link-status
load-interval 30
xconnect 10.99.99.10 15 encapsulation mpls
!
interface GigabitEthernet1/32
mtu 9216
ip address 10.99.98.65 255.255.255.254
logging event link-status
logging event trunk-status
logging event spanning-tree status
logging event subif-link-status
load-interval 30
mpls ip
!
router ospf 1
router-id 10.99.99.11
log-adjacency-changes
area 10 nssa
network 10.99.98.0 0.0.0.255 area 10
network 10.99.99.11 0.0.0.0 area 10
!
mpls ldp router-id Loopback0 force
!
ME6524-B#sh mpls forwarding-table detail
Local Outgoing Prefix Bytes Label Outgoing Next Hop
Label Label or Tunnel Id Switched interface
16 No Label l2ckt(15) 17640 none point2point
MAC/Encaps=0/0, MRU=0, Label Stack{}
No output feature configured
17 Pop Label 10.99.99.10/32 0 Gi1/32 10.99.98.64
MAC/Encaps=14/14, MRU=9220, Label Stack{}
00169D21AD1C00169D215DDE8847
No output feature configured
ME3400-A#sh ver | i IOS
Cisco IOS Software, ME340x Software (ME340x-METROIPACCESSK9-M),
Version 12.2(44)SE,
RELEASE SOFTWARE (fc1)
ME3400-A#sh run
spanning-tree mode mst
spanning-tree extend system-id
spanning-tree mst 0 priority 24576
!
vlan 505
name mat505
interface GigabitEthernet0/15
port-type nni
switchport trunk allowed vlan 505
switchport mode trunk
!
interface Vlan505
ip address 50.50.50.50 255.255.255.0
!
ME3400-B#sh ver | i IOS
Cisco IOS Software, ME340x Software (ME340x-METROIPACCESSK9-M),
Version 12.2(44)SE,
RELEASE SOFTWARE (fc1)
ME3400-B#sh run
spanning-tree mode mst
spanning-tree extend system-id
!
vlan 505
name mat505
!
interface GigabitEthernet0/15
port-type nni
switchport trunk allowed vlan 505
switchport mode trunk
!
interface Vlan505
ip address 50.50.50.55 255.255.255.0
!
--
-mat
More information about the cisco-nsp
mailing list