Multicast problem: Ingress vif not found
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
02-27-2015 08:18 AM
I found this warning on several switches:
Slot-1: exosmc: ip_mc_handle_msdp_data:2038: MC: Ingress vif not found
Does anyone know what this means?
We have software versions 15.3.1.4 patch1-7 and 15.5.2.9 patch1-5
Does anyone know what this means?
We have software versions 15.3.1.4 patch1-7 and 15.5.2.9 patch1-5
9 REPLIES 9
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
05-22-2015 11:12 AM
Funny I opened this case with those X650 switches. Well I will open new case. Still so far this looks like cosmetic issue.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
05-22-2015 11:12 AM
It looks like a fix is not currently scoped for 15.3. However, if you are running into this issue on an X650, I would suggest opening a case with GTAC or contacting your account team so we can request a patch in 15.3 as well.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
05-22-2015 11:12 AM
I hope that fix will be in 15.3 version.Several older x650 newest version what can be installed is 15.3
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
05-22-2015 11:02 AM
I think this might be CR xos0055945, fixed in 15.7.1.
If translation/network VLAN receives multicast packet with member/subscriber vlan tag, then switch throws error message "exosmc: ip_mc_handle_msdp_data:2038: MC: Ingress vif not found”.
Depending if you use vlan translation or private vlans this might be applicable.
If translation/network VLAN receives multicast packet with member/subscriber vlan tag, then switch throws error message "exosmc: ip_mc_handle_msdp_data:2038: MC: Ingress vif not found”.
Depending if you use vlan translation or private vlans this might be applicable.
