Loading...
Loading...
Symptom: Vidmon NP flow table OOR triggers immediate P2MP traffic drop with NP drop cause "UNKNOWN_L2_ON_L3_DISCARD" at "show controller np counter ..." command. After a while, LC will reload due to complete drop of P2MP traffic. Conditions: On Trident LC, when Vidmon is configured on P2MP ingress. When vidmon flow count is over physical capacity, i.e., 1024 flows. This syslog output will indicate this OOR condition: "...%PLATFORM-AFMON_EA_OOR-4-NP_FLOWS_OOR_RED : Performance Traffic Monitoring: Maximum monitored flows (1024) reached..." Workaround: When using vidmon with P2MP, fine tune ACL scope so that the total number of flows per NP will not exceed the capacity (1024 flows). Here, ACL is the IPv4 ACL used in vidmon class map (with type "traffic"), which again is used in vidmon policy map (with type "performance traffic"). Recovery: Once this issue is encountered, LC reload is recommended to restore the NP to clean state.
Cisco Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.