06-14-2012 12:12 AM - edited 03-01-2019 10:27 AM
Helloo All,
One of our uplink ethernet FI-6120 connected to J*N*R switch..
1. when we set the J*N*R switch port to trunk mode, the uplink ethernet always down,(we test the connection using ping) how to solved this ? or any basic information?
2. right now the switch's port is in access mode. the strange is .. connections from the outside network is suddenly broken and we must ping from blade server to gateway to make the connection up again . every time the connection from outside network is broken we must ping from blade to gw,
this is not hapen to other ethernet uplink (connected to cisco switch)
Best regards
06-14-2012 04:25 AM
Hi Piston,
Can you check the following:
1) Are all VLANs on UCS loosing connectivity or is it just a particular VLAN which does when you enable trunk on the upstream switch. If its just one VLAN, it could be a native vlan miss-match on either side causing this issue.
2) If i understand it correctly, you have uplinks going to two different type of upstream switches one to the J switches and one to CISCO..correct? Is so did you could be in the l2-disjoint situation if you are not running version 2.0 and have not configured the l2-disjoint properly.
./Abhinav
06-14-2012 06:00 AM
Hi Abhinav, Thank u for your respon..
1. there is only one permitted vlan on the uplink. and on the J* switch we already configured to allow the vlan. is there any configuration added to J* switch ?
2. yes ... we have 3 ethernet uplink to cisco switch and 1 ehternet uplink to J* switch.
and we already implement L2-disjoint...
OS Blade: windows 2003 and RHEL 5.4
UCSM : 2.0(1s)
how to prove that this problem is not on FI-6120?
Best Regards
06-14-2012 06:35 AM
Make sure to map each of the VLANs to the proper ports on both FI, currently each of your VLANs is dedicated to only uplink on a single FI so you have no redundancy.
Make sure you are not using default VLAN 1on any interface. It is allowed on all uplinks so broadcasts will not work properly, even if you use hard pinning.
Did you globally set the J*n*r VLAN as native in UCSM? Have you tried to instead configure the VLAN as a trunk on the J*n*r's interfaces and UCS?
Did you enable hard pinning? It is unnecessary if each VLAN only has a single uplink per FI and woudl only add extra complexity.
Also, please keep in mind that since you have configured each of the Cisco and J*n*r switch uplinks to only carry a single VLAN, make sure that every single vnic on all blades each only have a single VLAN.
06-14-2012 06:42 AM
Hi Piston,
I am not very sure about the required config on the J switch but here is something which can help you. All uplinks on the FI are configured as trunk ports even though you allow only one vlan. Hence traffic comming out of the interfaces will be tagged (unless the vlan is native).
Make sure with the l2-disjoint config you have added the vlans correctly to the correct uplink interfaces. please rememebr vlan 1 will be allowed on all interfaces so do not used vlan 1.
Here is a command which you can use to check the DR for each vlan (DR is the interface which is going to recieve and frwd the broadcast and multicast traffic - e.g. arp brcst) :
(nxos)# show platform software enm internal info vlandb id x
(replace x with the vlan number)
Can you make sure the DR for the vlan where you are having issues is on the interface going to the correct switch (either J or cisco)
Abhinav
06-14-2012 08:50 AM
Thank u chaausti and Abhinav ....
For the problem no 1 its solved
We also configure hard pinning... and we will change to soft pinning..
for L2-disjoint, we already add the vlans correctly to the correct uplink interfaces...
on all vnic we only use one vlan and not using vlan 1
this is the out put for DR ( yes its correct).
--------------------------------------------------------------------------------------------------------
(nxos)# show platform software enm internal info vlandb id xx5
vlan_id xx5
-------------
Designated receiver: Eth1/4
Membership:
Eth1/4
--------------------------------------------------------------------------------------------------------
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide