topic Re: VX9000 VLAN configuration and VMware in ExtremeWireless (WiNG)

VX9000 VLAN configuration and VMware

Andrej_N — Thu, 13 Jul 2023 06:03:24 GMT

We have installed VX9000 (7.9.1.0-022R) on ESXi (7.0.3). Everything work till adding some more VLANs and put IP 10.0.4.254 in VLAN40 and created new VLAN1 and set 10.0.9.254 IP. After that we were unable to access the controller. We put Ge1 to trunk mode, allowed VLANs on that port are 1, 40,...

Are there any reccomendations for ESXi, vswitch to work properly with VX9000?

Re: VX9000 VLAN configuration and VMware

Christoph_S — Thu, 13 Jul 2023 12:44:14 GMT

Hello Andrej ,

1 - Why did you assign an IP address to VLAN 40 and VLAN 1, which one is the management and native VLAN?

2 - Are you trying to access the controller remotely (behind the default gateway) or locally?

3 - If you set VLANs 40 and 1 to DHCP clients do they pull an IP address?

4 - Is the VX the DHCP server?

5 - Before assigning static IP addresses, you said that everything worked, what IP address and which VLAN were you accessing the controller through?

Please provide us with the VX profile and overrides outputs when in this state for analysis (from ESXI console)

BR,

Re: VX9000 VLAN configuration and VMware

Andrej_N — Mon, 17 Jul 2023 05:35:48 GMT

Hello Christoph,

1. Management VLAN is VLAN40 (IP 10.0.4.252 (not 254 as mentioned above). VLAN1 IP should be 10.0.9.253. There is DHCP server for 10.0.9.0 network for IPs for AP310-1 APs.

2. We are trying to access the controller locally trough VLAN40.

3. If 10.0.4.254 is in VLAN1, we can access, APs are adopting. We want to make similar configuration as it is on RFS4000 which will be replaced by VX. When we put 10.0.4.252 into VLAN40 (the same subnet as RFS) we can not access VX9k anymore.

4. Yes, it works as DHCP server. We use small pool for testing, but not the same scope as on RFS which is actually DHCP server. We won't use boath of them.

5. Static address for VX9k was assigned from the start. There will be 4 VLANs with static IPs. Other 2 are not important in this moment.

VX9000 profile:

profile vx9000 default-vx9000
no autoinstall configuration
no autoinstall firmware
no device-upgrade auto
crypto ikev1 policy ikev1-default
isakmp-proposal default encryption aes-256 group 2 hash sha
crypto ikev2 policy ikev2-default
isakmp-proposal default encryption aes-256 group 2 hash sha
crypto ipsec transform-set default esp-aes-256 esp-sha-hmac
crypto ikev1 remote-vpn
crypto ikev2 remote-vpn
crypto auto-ipsec-secure
crypto load-management
crypto remote-vpn-client
interface xge1
interface xge2
interface xge3
interface xge4
interface ge1
interface ge2
use firewall-policy default
logging on
service pm sys-restart
router bgp
adoption-mode controller

VX9k self context:
! vx9000 00-50-56-81-A2-F9
use profile default-vx9000
use rf-domain default
hostname vx9000-xyz
license AAP xyz
license ADSEC DEFAULT-ADV-SEC-LICENSE
license VX xyz
no adoption-site
no lci-config
ip default-gateway 10.0.4.1
interface vlan1
ip address 10.0.4.253/24
use dhcp-server-policy default

RFS4000 self context:
rfs4000 xyz
use profile default-rfs4000
use rf-domain default
hostname rfs4000-xyz
license AP DEFAULT-6AP-LICENSE
license AAP xyz
license ADSEC DEFAULT-ADV-SEC-LICENSE
no channel-list dynamic
no mint level 1 area-id
ip name-server 8.8.8.8
ip default-gateway 10.0.4.1
no device-upgrade auto
interface ge1
switchport mode trunk
switchport trunk native vlan 150
no switchport trunk native tagged
switchport trunk allowed vlan 1,40,150
interface ge2
switchport mode access
switchport access vlan 40
interface ge4
switchport mode trunk
switchport trunk native vlan 1
no switchport trunk native tagged
switchport trunk allowed vlan 1,10,19,40
interface vlan1
ip address 10.0.8.253/24
ip address 192.168.0.1/24 secondary
ip dhcp client request options all
interface vlan10
ip address 192.168.17.249/24
interface vlan19
ip address 10.0.12.2/22
interface vlan40
ip address 10.0.4.253/22
use dhcp-server-policy default
use auto-provisioning-policy default
logging on
logging console warnings
logging buffered warnings

There is only GE4 port active on RFS.

We need to use same VLANs as on RFS. Difference is on VLAN40, RFS uses 10.0.8.0, VX will use 10.0.9.0 network.

Re: VX9000 VLAN configuration and VMware

Andrej_N — Mon, 17 Jul 2023 06:10:09 GMT

To be shorter... the main problem is that when we put IP 10.0.4.252 to VLAN40, the VX is not manageble anymore.

If we have 10.0.4.252 in VLAN1, everything works ok.

VLAN1 is for APs.

VLAN40 for managing VX.

Re: VX9000 VLAN configuration and VMware

Christoph_S — Mon, 17 Jul 2023 12:38:37 GMT

Hello Andrej,

I don't see these settings configured on the VX:

interface ge1
switchport mode trunk
switchport trunk native <native VLAN ID>
switchport trunk allowed vlan <list of allowed vlans>

Also please make sure that vlan 40 is also allowed through the switchport.

BR,

Re: VX9000 VLAN configuration and VMware

ckelly — Mon, 17 Jul 2023 13:58:07 GMT

Andrej, looking at your config, I'm seeing this:

interface vlan40 ip address 10.0.4.253/22

You seem to be saying elsewhere though that VLAN-40 should be on .4.252 (not .4.253) Can you confirm which address is correct?

Re: VX9000 VLAN configuration and VMware

Christoph_S — Tue, 18 Jul 2023 12:36:13 GMT

Hello Anrej,

I can't see the following configured on you VX9000:

Please configure vlan 40 and add the following:

interface ge1
switchport mode trunk
switchport trunk native <vlan id>
no switchport trunk native tagged
switchport trunk allowed vlan 1,40 (include any other vlans that need access if you have others)

Also make sure that same are allowed out of your switchport.

BR,