Reset Search
 

 

Article

Why when VDX hardware-profile tcam is configured on I2-ipv4-acl, does PIM Multicast not work?

« Go Back

Information

 
TitleWhy when VDX hardware-profile tcam is configured on I2-ipv4-acl, does PIM Multicast not work?
Question
VDX 6.01a and other releases . VDX 6740

Multicast traffic was confirmed to be sent but was not delivered.
Environment
Answer
PIM Multicast is not working. Even though we have multicast traffic coming from source on the first hop router it is not creating (s,g) entries. PIM Sparse mode is configured properly on VE 394 of VDX 6740 where the traffic is coming and also RP(10.1.1.251) is reachable via "VE 499". On further debugging identified that the "tcam profile" hardware-profile tcam l2-ipv4-acl" is being usedto allowmore ACL's.More than 900 ACL's are needed and using theabove mentioned profile allocates 0 tcam entries for Multicast.

ACL shows that traffic is coming to the box and PIM is configured on VE394.

VCS5_RB11# show access-list interface vlan 394 in
mac access-list MCAST_SRC on Vlan 394 at Ingress (From User)
seq 10 permit host 88ae.1daa.417f host 0100.5e09.0a0b count (Active)
seq 20 permit any any (Active)

VCS5_RB11# show statistics access-list mac MCAST_SRC in
mac access-list MCAST_SRC on Vlan 394 at Ingress (From User)
seq 10 permit host 88ae.1daa.417f host 0100.5e09.0a0b count (5160 frames)
seq 20 permit any any

VCS5_RB11# show statistics access-list mac MCAST_SRC in
mac access-list MCAST_SRC on Vlan 394 at Ingress (From User)
seq 10 permit host 88ae.1daa.417f host 0100.5e09.0a0b count (5176 frames)
seq 20 permit any any

VCS5_RB11# show ip pim mcache 239.9.10.11
IP Multicast Mcache Table
Entry Flags : sm - Sparse Mode, ssm - Source Specific Multicast
RPT - RPT Bit, SPT - SPT Bit, LSrc - Local Source
LRcv - Local Receiver, RegProbe - Register In Progress
RegSupp - Register Suppression Timer, Reg - Register Complete
needRte - Route Required for Src/RP
Interface Flags: IM - Immediate, IH - Inherited, WA - Won Assert
MJ - Membership Join, BR - Blocked RPT, BA - Blocked Assert
BF - Blocked Filter
Total entries in mcache: 31

VCS5_RB11# show running-config rb int ve 394
rbridge-id 10
interface Ve 394
ip access-group 194 in routed
ip ospf area 0
ip ospf active
ip dhcp relay address 10.128.128.9
ip dhcp relay address 10.128.128.23
ip dhcp relay address 10.132.112.27
ip directed-broadcast
ip proxy-arp
ip address 10.128.220.2/22
ip pim-sparse
vrrp-extended-group 1
virtual-ip 10.128.220.1
advertisement-interval 1
enable
no preempt-mode
!
no shutdown
!
!

sw0(config-rbridge-id-159)# hardware-profile tcam l2-ipv4-acl

With hardware-profile tcam l2-ipv4-acl profilewe canhave 1536ingress entries and 128 egress entries butzerotcam allocated for multicast.

sw0(config-rbridge-id-159)# do show hardware-profile tcam l2-ipv4-acl
rbridge-id: 159 switch type: VDX6740T-1G

TCAM profile: L2-IPV4-ACL
________________________________________________________________

L2 Path Select FCoE: 512
MAC ACL Based QoS Policy Entries (Ingress): 512
L2 Path Select FCoE Zones: 0
MAC Security ACL Entries (Ingress): 1024
MAC Policy Based forwarding entries: 0
L2 Multicast No Flood Entries (Ingress): 0
L2 OpenFlow (Ingress): 0
IPV4 ACL Based QoS Policy Entries (Ingress): 512
IPV4 Multicast Entries (Ingress): 0
IPV4 Policy Based Routing Entries (Ingress): 512
IPV4 Security ACL Entries (Ingress): 1536
L3 Path Select FCoE: 512
IPV6 Policy Based Routing Entries (Ingress): 0
IPV6 ACL Based QoS Policy Entries (Ingress): 0
IPV6 Multicast Entries (Ingress): 0
IPV6 Security ACL Entries (Ingress): 0
IPV4 OpenFlow (Ingress): 0
IPV4 MINI Path Select Mcast: 0
L3 ACL MINI FCOE: 0
L2 Forward FCoE: 2048
MAC Security ACL Entries (Egress): 128
MAC ACL Based QoS Policy Entries (Egress): 128
IPV4 Security ACL Entries (Egress): 128
IPV4 ACL Based QoS Policy Entries (Egress): 128
IPV6 Security ACL Entries (Egress): 128
IPV6 ACL Based QoS Policy Entries (Egress): 0
FCoE Egress ACL: 0
L2 MAC Classifier: 256
L2 MAC Classifier Prio: 0
VLN Classifier: 4096
Policy Classifier: 0


Changeeither of the following two tcam profiles for Multicast to work.The following two profiles defaultor ipv4-v6-mcastwill support TCAM for L3 PIM (L3 multicast):

hardware-profile tcam ?
Possible completions:

[default]

default basic support for all applications
dyn-arp-insp optimized for dynamic Arp Inspection
ipv4-v6-mcast optimized for multicast
ipv4-v6-pbr optimized for IPv4 and IPv6 ACL, PBR
ipv4-v6-qos optimized for IPv4 and IPv6 ACL, QOS
l2-acl-qos optimized for L2 ACL, QOS
l2-ipv4-acl optimized for L2 and IPv4 ACL
openflow optimized for openflow support

# do show hardware-profile tcam ipv4-v6-mcast

TCAM profile: IPV4-V6-MCAST
________________________________________________________________

L2 Path Select FCoE: 512
MAC ACL Based QoS Policy Entries (Ingress): 512
L2 Path Select FCoE Zones: 0
MAC Security ACL Entries (Ingress): 0
MAC Policy Based forwarding entries: 0
L2 Multicast No Flood Entries (Ingress): 512
L2 OpenFlow (Ingress): 0
IPV4 ACL Based QoS Policy Entries (Ingress): 0
IPV4 Multicast Entries (Ingress): 1024
IPV4 Policy Based Routing Entries (Ingress): 0
IPV4 Security ACL Entries (Ingress): 512
L3 Path Select FCoE: 512
IPV6 Policy Based Routing Entries (Ingress): 0
IPV6 ACL Based QoS Policy Entries (Ingress): 0
IPV6 Multicast Entries (Ingress): 512
IPV6 Security ACL Entries (Ingress): 512
IPV4 OpenFlow (Ingress): 0
IPV4 MINI Path Select Mcast: 0
L3 ACL MINI FCOE: 0
L2 Forward FCoE: 2048
MAC Security ACL Entries (Egress): 0
MAC ACL Based QoS Policy Entries (Egress): 128
IPV4 Security ACL Entries (Egress): 128
IPV4 ACL Based QoS Policy Entries (Egress): 128
IPV6 Security ACL Entries (Egress): 128
IPV6 ACL Based QoS Policy Entries (Egress): 128
FCoE Egress ACL: 0
L2 MAC Classifier: 256
L2 MAC Classifier Prio: 0
VLN Classifier: 4096
Policy Classifier: 0
__

VDX6740# show hardware-profile tcam default
rbridge-id: 1 switch type: BR-VDX6740

TCAM profile: DEFAULT
________________________________________________________________

L2 Path Select FCoE: 512
MAC ACL Based QoS Policy Entries (Ingress): 512
L2 Path Select FCoE Zones: 0
MAC Security ACL Entries (Ingress): 512
MAC Policy Based forwarding entries: 0
L2 Multicast No Flood Entries (Ingress): 0
L2 OpenFlow (Ingress): 0
IPV4 ACL Based QoS Policy Entries (Ingress): 512
IPV4 Multicast Entries (Ingress): 1024
IPV4 Policy Based Routing Entries (Ingress): 512
IPV4 Security ACL Entries (Ingress): 512
L3 Path Select FCoE: 512
IPV6 Policy Based Routing Entries (Ingress): 0
IPV6 ACL Based QoS Policy Entries (Ingress): 0
IPV6 Multicast Entries (Ingress): 0
IPV6 Security ACL Entries (Ingress): 512
IPV4 OpenFlow (Ingress): 0
IPV4 MINI Path Select Mcast: 0
L3 ACL MINI FCOE: 0
L2 Forward FCoE: 2048
MAC Security ACL Entries (Egress): 128
MAC ACL Based QoS Policy Entries (Egress): 128
IPV4 Security ACL Entries (Egress): 128
IPV4 ACL Based QoS Policy Entries (Egress): 0
IPV6 Security ACL Entries (Egress): 128
IPV6 ACL Based QoS Policy Entries (Egress): 0
FCoE Egress ACL: 128
L2 MAC Classifier: 256
L2 MAC Classifier Prio: 0
VLN Classifier: 4096
Policy Classifier: 0

Note: With the defaultor ipv4-v6-multicastprofile the usercan configure 1024 (S,G) Multicast entries but the number of ACL entries that can be created areonly 512.

Please refer to the attached document for6.01a Release Notes forthe scalability ofhardware tcam with different profiles.

Additional notes

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255