This is currently how the OE for the acod node is configured
eth0 192.168.224.111
eth0.217 192.168.217.2
The interface MAC is the same for both eth0 and eth0.217.
The NAS is configured with 192.168.211.10
A netstat -rn of acod node
Destination Gateway Genmask Int
0.0.0.0 192.168.224.254 0.0.0.0 eth0
192.168.217.0 0.0.0.0 255.255.255.0 eth0.217
192.168.224.0 0.0.0.0 255.255.255.0 eth0
192.168.122.0 0.0.0.0 255.255.255.0 virbr0
From the aocd node, we cannot ping the 192.168.217.254 gateway.
From the aocd node, we cannot ping the 192.168.224.254 gateway.
From the NAS node, we can ping the 192.168.217.254 gateway.
From the NAS node, we can ping the 192.168.224.254 gateway.
From the NAS node, we cannot ping the 192.168.217.2
From the NAS node, we can ping the 192.168.224.111
This is what was done:
Step 1. Create Segments in NSX:
Segment 1
Name: nsx-tipc-trunk
Connected Gateway: None
Transport Zone: nsx-vlan-transportzone (or custom-defined VLAN transport zone)
Subnets (Gateway CIDR): Leave Blank
Uplink Teaming Policy: Leave Blank if not defined in Transport Zone (only required if configuring traffic pinning to specific Top of Rack)
VLAN: 217,224
Segment 2
Name: nsx-tipc-vlan-217
Connected Gateway: None
Transport Zone: nsx-vlan-transportzone (or custom-defined VLAN transport zone)
Subnets (Gateway CIDR): Leave Blank
Uplink Teaming Policy: Leave Blank if not defined in Transport Zone (only required if configuring traffic pinning to specific Top of Rack)
VLAN: 217
Segment 3
Name: nsx-tipc-vlan-224
Connected Gateway: None
Transport Zone: nsx-vlan-transportzone (or custom-defined VLAN transport zone)
Subnets (Gateway CIDR): Leave Blank
Uplink Teaming Policy: Leave Blank if not defined in Transport Zone (only required if configuring traffic pinning to specific Top of Rack)
VLAN: 224
Step 2. Create Service Interfaces on Tier0 or Tier1 SERVICES ROUTER (Edge Cluster required)
Create or Edit Tier0 or 1 SR
Expand SERVICE INTERFACES
Select "Set"
Select "ADD INTERFACE"
Name: tipc-vlan-217-gw
IP Address/Mask: 192.168.217.254/24 (or appropriate address on subnet)
Connected To(Segment): Select the 'nsx-tipc-vlan-217' segment created in previous step
Save
Select "ADD INTERFACE"
Name: tipc-vlan-224-gw
IP Address/Mask: 192.168.224.254/24 (or appropriate address on subnet)
Connected To(Segment): Select the 'nsx-tipc-vlan-224' segment created in previous step
Save
If configured on Tier1 SR, ensure "All Connected Segments & Service Ports" is selected to advertise routes to Tier0
Step 3. Edit TIPC VM Network Adapter Settings
Modify Network Adapter and select "nsx-tipc-trunk" segment that was configured in Step 1 as the attached VM network port group
These steps will configure NSX to host the gateways for the specified VLANs, and also configure an NSX segment as a trunk to attach to the VM and pass multiple VLANs across.
Hi all,
We are trying to have our aocd VM which has a native vlan 0f 224 and a tagged vlan of 217 have connectivity to our NAS on vlan 211.
This is currently how the OE for the acod node is configured
eth0 192.168.224.111
eth0.217 192.168.217.2
The interface MAC is the same for both eth0 and eth0.217.
The NAS is configured with 192.168.211.10
A netstat -rn of acod node
Destination Gateway Genmask Int
0.0.0.0 192.168.224.254 0.0.0.0 eth0
192.168.217.0 0.0.0.0 255.255.255.0 eth0.217
192.168.224.0 0.0.0.0 255.255.255.0 eth0
192.168.122.0 0.0.0.0 255.255.255.0 virbr0
From the aocd node, we cannot ping the 192.168.217.254 gateway.
From the aocd node, we cannot ping the 192.168.224.254 gateway.
From the NAS node, we can ping the 192.168.217.254 gateway.
From the NAS node, we can ping the 192.168.224.254 gateway.
From the NAS node, we cannot ping the 192.168.217.2
From the NAS node, we can ping the 192.168.224.111
In vCenter, under edit settings, attached nsx-tipc-trunk to the vVM interface and make sure it was connected.
Thank you very much!