Question : What to look for when IAP Mesh trunk is unable to carry tagged vlan traffic?
Environment Information : Instant Version 6.2.1.0-3.3 and later versions.
Symptoms :
Resolution:
Ensure Eth0 bridging is enabled
Tried below scenarios and has issues and the tagged vlan is not passing traffic. Scenario 1: Had a client ( IP address 192.168.10.3, Mac address b4:b5:2f:73:0c:1f ) connected on vlan 10 on the Point end switch. Able to ping Point end switch's vlan 10 interface IP address. Tried to ping the vlan 10 interface IP of the Portal end switch (192.168.10.254). Unable to ping it. Scenario 2: Had a client ( IP address 192.168.10.3, Mac address b4:b5:2f:73:0c:1f ) connected on vlan 10 on the portal end switch. Able to ping Portal end switch's vlan interface IP address. Tried to ping the vlan 10 interface IP of the Point end switch (192.168.10.253). Unable to ping it. We would have this issue, if we have the configuration of vlan 10 with the same subnet as Magic vlan 3333 in IAP which is 192.168.10.x. DHCP Information ================== listen-address=127.0.0.1 addn-hosts=/etc/ld_eth_hosts addn-hosts=/etc/ld_ppp_hosts dhcp-src=192.168.10.1 dhcp-leasefile=/tmp/dnsmasq.leases dhcp-authoritative filterwin2k #magic-vlan { vlan-id=3333 dhcp-range=192.168.10.3,192.168.11.254,255.255.254.0,12h dhcp-option=1,255.255.254.0 dhcp-option=3,192.168.10.1 dhcp-option=6,8.8.8.8 dhcp-option=54,192.168.10.1 } DHCP VLAN Id: 3333 DHCP Server Id: 192.168.10.1 DHCP Server Mask: 255.255.254.0 946730914 00:02:3f:eb:5d:e5 192.168.10.4 10 magic-1 00:02:3f:eb:5d:e5 946732488 e0:f8:47:cf:bc:b3 192.168.11.30 3333 iPhone 01:e0:f8:47:cf:bc:b3 Hence we should change the 'Magic vlan's 3333' subnet to a different one for instance 192.168.100.0/24 To change the Magic vlan's subnet, Please navigate to System > 'Show Advanced Options' > Dhcp.
© Copyright 2024 Hewlett Packard Enterprise Development LPAll Rights Reserved.