cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements

200
Views
40
Helpful
7
Replies
alex210
Beginner

UCS B SERIES BLADES DONT TALK TO EACH OTHER

Hi Folks,

 

I have the following setup:

- fabric interconnect connected to one upstream switch.

- mac address of the OS's Blades are learned by the switch but the blades can't communicate to each others.

- it s baremetal installation.

 

7 REPLIES 7
Kirk J
Cisco Employee

Are these all in the same vlan and subnet?

Are you tagging the vlans in the OS, or using native-vlan designation at the vnic level?

Is the FI nxos level, showing the macs learned in the vlan you expect them in?

 

Kirk...

 

Hi ,

below my answers.

 

Are these all in the same vlan and subnet?

yes , they are in the same vlan and subnet. linux is installed as baremetal on blades with diffrents vNIC. I configure one interface from each blade in same VLAN/subnet and try ping.

Are you tagging the vlans in the OS, or using native-vlan designation at the vnic level?

i am not tagging vlan in OS. native vlan is the default vlan 1. I didn't change it.

Is the FI nxos level, showing the macs learned in the vlan you expect them in?

Could you please share with me the command.

hi ,

 

Is the FI nxos level, showing the macs learned in the vlan you expect them in?

 

no mac is of vNIC is learned by the FI. mac are learned only by the upstream switch.

connect nxos a|b

show mac address-table

 

using vlan 1 is never a good idea.

If you aren't going to tag the vlans at OS level, then you should designate the vlan you want traffic on, as 'native' at vnic, vlan config level.

 

Kirk...

 

hi ,

 

I designated my vlan as native vlan on vNIC but still no ping.

fabric interconnect doesn't learn any mac address of my vNIC.

 

regards

Please check your vnic assigned mac address from service profile, and confirm the mac address you get at the OS level.

Almost sounds like the vnic and the expected eth interface at the OS level aren't matching up, or we don't have correct enic driver, etc.

 

Kirk...

Hi ,

 

sorry, I didn't apply the change well for the first time.

when I designate native vlan on the vNIC , the node ping each other.

so , this native vlan doesn't impact other vlan if i try to reach them. as each vNIC is affacted on different vlan ?

vlan 220 is designate as native? if i configure another ip on vNIC2 (other subnet /vlan) , can I ping each server , as the native vlan is only on vNIC1.

 

vNIC 1 subnet 1 vlan 220

vNIC 2 subnet 2 vlan201

 

regards

 

 

Content for Community-Ad