[c-nsp] me-3600 docs and drops

[Jason Lixfeld]

First and foremost, get on to the latest 15.3 code.  Everything south of that, good luck.  Anything north of that, well, based on the history of the platform, I wouldn’t trust it.
Second, the one EFP in the bridge-domain caveat might be simply describing an unsupported topology where you have two similarly configured EFPs on the same interface with the same encapsulation match trying to access the same BD.  If that’s the case, it’s probably just a confusing reference to this:

http://www.cisco.com/c/en/us/td/docs/switches/metro/me3600x_3800x/software/release/12-2_52_ey/configuration/guide/3800x3600xscg/swevc.html#wp1051106

I don’t see why it wouldn’t work if there were two EFPs on different interfaces trying to access the same SVI.  I have that working no problem:

!
ip dhcp pool DYNAMIC
 utilization mark high 90 log
 network 1.1.1.0 255.255.255.0
 default-router 1.1.1.1
!
interface Vlan4000
 ip address 1.1.1.1 255.255.255.0
 no logging event link-status
 no snmp trap link-status
!
interface GigabitEthernet0/2
 switchport trunk allowed vlan none
 switchport mode trunk
 dampening
 ip dhcp limit lease 1
 logging event link-status
 carrier-delay msec 0
 speed 10
 no cdp enable
 service instance 4000 ethernet
  encapsulation untagged
  bridge-domain 4000 split-horizon group 1
 !
interface GigabitEthernet0/3
 switchport trunk allowed vlan none
 switchport mode trunk
 dampening
 ip dhcp limit lease 1
 logging event link-status
 carrier-delay msec 0
 speed 10
 no cdp enable
 service instance 4000 ethernet
  encapsulation untagged
  bridge-domain 4000 split-horizon group 1
 !
!
interface GigabitEthernet0/5
 switchport trunk allowed vlan none
 switchport mode trunk
 dampening
 ip dhcp limit lease 1
 logging event link-status
 carrier-delay msec 0
 speed 10
 no cdp enable
 service instance 4000 ethernet
  encapsulation untagged
  bridge-domain 4000 split-horizon group 1
 !
!
interface GigabitEthernet0/15
 switchport trunk allowed vlan none
 switchport mode trunk
 dampening
 ip dhcp limit lease 1
 logging event link-status
 carrier-delay msec 0
 speed 100
 no cdp enable
 service instance 4000 ethernet
  encapsulation untagged
  bridge-domain 4000 split-horizon group 1
 !

Internet  1.1.1.1         -   2c36.f8b2.7340  ARPA   Vlan4000
Internet  1.1.1.2         0   c8d7.1985.e9ea  ARPA   Vlan4000
Internet  1.1.1.3         0   1803.73c0.b5de  ARPA   Vlan4000
Internet  1.1.1.4         0   204e.7fc5.e02c  ARPA   Vlan4000
Internet  1.1.1.5         1   001e.5832.332a  ARPA   Vlan4000

4000    001e.5832.332a    DYNAMIC     Gi0/2+Efp4000
4000    1803.73c0.b5de    DYNAMIC     Gi0/3+Efp4000
4000    204e.7fc5.e02c    DYNAMIC     Gi0/15+Efp4000
4000    c8d7.1985.e9ea    DYNAMIC     Gi0/5+Efp4000

> On Dec 23, 2014, at 2:39 PM, Christopher Hunt <dharmachris at gmail.com> wrote:
> 
> I'm reading the docs on my shiny new ME-3600X [1]  and i see this:
> 
> The switch supports IP routing and multicast routing for bridge domains,
> including Layer 3 and Layer 2 VPNs, using the SVI model. There are the
> limitations:...
> 
>   - You must configure SVIs for bridge-domain routing.
>   - The bridge domain must be in the range of 1 to 4094 to match the
>   supported VLAN range.
>   - There can be only one EFP in the bridge domain.
> 
> 
> This last bit seems like a pretty serious limitation to me, so off to the
> lab:
> ########################################
> System image file is
> "flash:/me360x-universal-mz.152-2.S1/me360x-universal-mz.152-2.S1.bin"
> License Level: AdvancedMetroIPAccess
> 
> interface GigabitEthernet0/2
> description direct to customer
> switchport trunk allowed vlan none
> switchport mode trunk
> service instance 6 ethernet
>  encapsulation untagged etype ipv4
>  bridge-domain 44
> !
> !
> interface GigabitEthernet0/3
> description direct to customer
> switchport trunk allowed vlan none
> switchport mode trunk
> no keepalive
> service instance 6 ethernet
>  encapsulation untagged etype ipv4
>  bridge-domain 44
> !
> !
> interface Vlan44
> ip vrf forwarding TestCo
> ip address 192.168.1.254 255.255.255.0
> end
> ########################################
> 
> Sure enough, I am unable to ping the SVI or across the switchports.  Then I
> remove the "etype ipv4" restriction (leaving simply "encapsulation untagged
> ") and it works fine.  I couldn't find any bug directly related  So I have
> two questions:
> 1) exactly what do they mean by "There can be only one EFP in the bridge
> domain."
> 2) why would "etype ipv4" drop packets that clearly are ipv4?  (icmp echo
> request,  TCP3389  etc.)
> 
> 
> Cheers,
> Chris
> 
> 
> 
> 
> [1]
> http://www.cisco.com/c/en/us/td/docs/switches/metro/me3600x_3800x/software/release/12-2_52_ey/configuration/guide/3800x3600xscg/swevc.html
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/