VC FlexFabric 10/24 gb with Shared Uplink Set With Multiple Networks/Vlans

[Gopan]

We have a setup of new C7000 enclosure with VC 10/24gb FlexFabric .Configured Shared Uplink Set with Multiple VLAN's with port X4 in Virtual connect switch which is of 10gb.Once configured the SUS and assigned the server profile ,its not getting connected to the LAN.If we configure SUS with single VLAN,then yes its working (connected to domain network).If we select all multiple VLAN's and configure Untag on the VLAN of the IP address which is assigned to the particular server ,then also yes its working,but need to check it from Hyper-V.

Please somebody can explain/advice what is the issue when its not getting connected?

Attached is the snapshot where we configured the Untagged Network.Kindly somebody explain the nature/use/behaviour of Untagged Network configuration on VC

[Hongjun Ma]

sorry but I'm still not clear the question after looking at word document.

For untagged network, under SUS, you can check "native" box for the particular vnet. This is the connection between VC and network access switch.  Under server profile, if you are using "multiple networks" for the port, you can check "untagged" for the particular vnet(like the one in your word document).

can you send a screen capture of SUS and server profile config where it doesn't work and where it does work so we can see the comparison.

which vlan is configured as native under network access switch port connecting with VC?

[Psychonaut]

How are the switch ports configured - are the VLANs you want to connect to trunked to the port?

[Gopan]

Attached word document is somewhat more clear ..believe so ...No Vlan configured as native but from SUS set ,we have configured untagged network

[Gopan]

The switch port is trunked and individual seperate V;an's are pssing the traffic.I mean to say that Vlan say 203,204,206,208,209 etc ,if we configure individual direct one vlan ,then all fine ,but with multiple networks ,there is the problem .Attached (in above reply)more snapshots of the current environment

[Hongjun Ma · Accepted solution]

from word document, it looks like with SUS(multiple vnets under) config, if you choose a vnet as "untagged" under "Multiple Networks", then the server in that vnet will work. If you don't choose a vnet as "untagged" under "Multiple Networks", the server will not connect to the network even with the same SUS config.

If that's the case, very likely the config problem is not at VC SUS side, you need to check your server OS NIC configuration to see if it can accepted tagged traffic coming in from VC. It looks like a tagging configuration mismatch between VC downlink and server side.

[Gopan]

Thanks for the Hint and Thanks for the explanation to Untagged network.Yes believe it was a configuration mismatch/missing configuration from server NIC side.Once we configure NIC of the server(teamed) with Vlan ID(configuration advanced tab) .its ok now.