cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
646
Views
1
Helpful
2
Replies

Issue with routing protocol multicast packet transmission on SVI

stevesmith741
Level 1
Level 1

Originally posted in wrong discussion group (Nexus Developers)

Hi all,

I've run across an issue when trying to enable RIP and OSPF on SVI interfaces on my

nx-osv

instances. Getting this output from

debug l2fwder error
2023 Aug 12 02:04:20.571324 l2fwd: l2fwder_get_mac_lookup_fwd_info(784):l2fwder_get_mac_lookup_fwd_info: Unsupported frame [0100.5e00.0009] etype[2048
2023 Aug 12 02:04:21.020643 l2fwd: l2fwder_get_mac_lookup_fwd_info(784):l2fwder_get_mac_lookup_fwd_info: Unsupported frame [0100.5e00.0005] etype[2048

Not sure if that missing closing square bracket after

2048

is a clue. Probably just cosmetic. 

I also observe these drop counters in

show l2fwder statistics

output:

Switching stats:
Unicast 0
Flood 41
Multicast 0
Punt 140
Drop 26204

No issues with RIP or OSPF multicast packet transmission on routed interfaces or sub-interfaces, only with SVIs. No issues with unicast transmission on SVIs. Anyone aware if this is a limitation of

nx-osv

? I can't see any obvious limitations listed that would affect this functionality.

Running version is titanium

-d1-kickstart.7.3.0.D1.1. Running in EVE-NG

Any help greatly appreciated!

Steve

1 Accepted Solution

Accepted Solutions

Peter Paluch
Cisco Employee
Cisco Employee

Hi Steve,

What you're observing is definitely a bug (

CSCuz98156

sadly not publicly accessible) which was fixed internally for the

l2fwd

component. Unfortunately, the

NX-OSv

project itself is obsolete and to my best knowledge, we did not publicly release any newer versions of the

NX-OSv

(the virtual Nexus 7000 series). These images are deprecated and instead of them,

NX-OS 9000v 

should be used.

Sorry for disappointing you - I wish I had better news.

Best regards,
Peter

 

View solution in original post

2 Replies 2

Peter Paluch
Cisco Employee
Cisco Employee

Hi Steve,

What you're observing is definitely a bug (

CSCuz98156

sadly not publicly accessible) which was fixed internally for the

l2fwd

component. Unfortunately, the

NX-OSv

project itself is obsolete and to my best knowledge, we did not publicly release any newer versions of the

NX-OSv

(the virtual Nexus 7000 series). These images are deprecated and instead of them,

NX-OS 9000v 

should be used.

Sorry for disappointing you - I wish I had better news.

Best regards,
Peter

 

Thanks for taking the trouble to look into this Peter. I have indeed decided to work with the

9000v

instead of the Titanium image. It seems to come with its own bag of troubles as well (

VPC peer

keepalives not working, LACP not working), but hopefully I'll overcome with enough perserverance!