Configuration switch EN2092 IBM flex system 7893 9655

Hello,I want help to configure the virtualization part of the administration interface switches.I created on my vms hypervisor but they do not communicate externally. i need help for configuring vlan. i want my hypervisor to communique externalthank you

1. Have you set the vlan on the external network switch ports? The internal ports will pass any vlan you set on them to the ex ports but the ex ports need a vlan. 2. Have you configured your vswitch to use one of the physical nics?

Thank you for your reply.I created 2 Vlan I assigned him ports (INTA1 to INTA9 and INTB1 to INTB9 and EXT1 to EXT5)in the network configuration of ESXi I assigned the VLAN 2 with the same IP address range and I activated the vmnic, but its not working.By cons, in ESXi when I leave the fields empty vlan. His works and I can connect me with vSphere.the vswitch is connected to the vmnics.I created my virtual machine, but I am unable to ping ip address but the Vm manages to ping my ip address.I do not understand, thank you for your help

i attached screenshot.with a single nic nothing changes.but in the network configuration of compute node ESXi when I chose the 4095 Vlan networks work.but the vlan 2 that I created in the administrator interface of the switch does not work.is there a precise configuration vlan for it to work?Thank you for help

If I were you I would set your chassis switches back to defaults. You should ONLY need VLANs to be set on your external ports, all internal ports will pass traffic through the external network switch ports without any configuration needed. From your picture it looks like you have it configured properly at least from the VMware side. VLAN 4095 is the local management VLAN. In our lab we had collapsed all preconfigured vlans and left a default of vlan 1 this allowed all vlans to pass to the core switch where traffic could be separated at the vlan layer there. Again you should never need to touch the internal ports unless your network architecture calls for the separating of data and management traffic on isolated VLANS.

So to recap, set your switches back to defaults if possible and try to ONLY set your VLAN on the external network port/ports.

Also as a sidenote, the networking piece is ALWAYS the biggest headache in these installs and while IBM has made massive strides in that department I fear for us engineers the networking nonsense will still exist for a little while longer.

Hello,Thank you for your answers.I applied what you told me I put default and I assigned to VLAN 1 ip address and gateway.I enabled the tagging option on the external ports.but in the network configuration of the blade, with the vlan 1 I still can not connect to it.thank you.

ok thank youI do not have FMS and my host is not clustered.now I created the vlan 2 on which I set some external ports.I assigned to compute node 9 the vlan 2on a PC with vSphere I created a VM under Windows 2008. my problem is that when I'm in the vm I do not always manage to ping an external ip address.and external as I am unable to ping the IP address of the Vms.Thank you for help

If you are able to connect to the esxi host via vsphere than the chassis switch is functioning properly and passing external traffic. If you are having an issue with the VMs then it sounds like the vSwitch has a configuration issue as it is not able to route traffic externally. I would focus our energies on your vSwitch and off of the chassis switches for now. Please send snapshots of all screens relating to the properties of you vSwitch NIC if possible and maybe some of what you are seeing from the VM side.

Hello,excuse me I was traveling.this is good. I'll just make a minimum configuration, all 4 switches will be on the same address range.So I think it is not worth creating a vlan??Thank you for your availability

Creating a VLAN should not be necessary EXCEPT on the external switch ports but again if you are able to ping and connect to your ESXi hosts then there could be a problem with you vSwitch and not with the chassis switches.

Are your vSwitches using an active/passive or active/active If active/active I would disable one NIC and try your ping tests again. If you can ping between your VMs and externally with only one active NIC then there is a misconfiguration of the active/active setup which COULD be a chassis configuration issue in which case my networking knowledge would have run its course and you should contact a network admin or try to open a ticket with IBM.

Please send me some snapshots of your vSwitch adapter settings so I can compare to our labs and report back if you get a chance.

Hello,I solved my problem with the switch configuration 1Gb.I use the default VLAN 1, I assigned an IP address and default gateway and some juggling with the config.everything works now.thank youI am currently on two 10Gb switch.I must create a vlan and make a trunk port EXT1 and EXT2 because it needs to connect to another switch via fiber optics.I try this config:I create a vlan 100 on the first 10Gb switch then I activate trunk group on EXT1 and EXT2.I validated but its still not working, worst I can no longer enter the Admin GUI of the switch but I can ping the address.Thank you for your help.