Controllerless Networks

Reply
Occasional Contributor I

Re: IAP 277 adding a mesh (point to point) to existing config

files showing below:

 

PtP drawing.jpg

Occasional Contributor I

Re: IAP 277 adding a mesh (point to point) to existing config

Hi VincentArriola. Thankyou for your update and help on this issue.

 

I had already completed the setup as outlined in your email with the exception of  

 

7.            On the mesh POINT set the Uplink values to VLAN X and BRIDGE ENABLED

 

When I attempt this I lose all connectivity with the planned mesh POINT so have to revert the changed via CLI and reload.

 

10.          On the POINT IAPs switch, set the PoE Profile “Upstream-TrunkPorts” to ENABLED(We use Aruba MAS switches, so this is more-or-less just setting the vlan to match the config on the IAP)

11.          On the POINT IAPs switch, set the port (0/0/0) to the “Upstream-TrunkPorts-Group” group (We use Aruba MAS switches, so this is more-or-less just setting the vlans to match the config on the IAP)

 

With points 10 & 11 I am using HP switches and trunking all with a native VLAN 4 on the switch ports the Aruba APs connect to.

 

VLAN 4 = Management (switches/APs and Clients) -- this is going into an existing site so I am unable to change this although I know it’s not ideal.

 

VLAN 5 = VOIP network.

 

The mesh network between Master Portal and Slave Point establishes OK and I can ping from the Master network switch to the Slave mesh point on VLAN 4. For the VOIP VLAN 5 I can ping through from Master switch to Slave network and back again.

 

From the Slave Mesh Point I can ping the Master Portal, VLAN 4 and 5 back on the Master switch and any clients connected on the Master switch.

 

My problems:

 

From the Master network switch I am unable to ping anything past the Slave Point on VLAN 4. Traceroute produces no results. We need the ability to connect to the remote Slave Point from the remote switch should it become ‘stranded’ as both Aruba’s will be installed on roof tops. We also need to be able to see the switch and clients connected on VLAN4 on the Slave site.

 

I know the problem is likely to be with eth0 bridging and/or switch port configuration. VLAN 5 connection is OK whereas VLAN 4 is not. As I said earlier I attempted to change the uplink VLAN to 4 on the Slave mesh Point but lost connection so this was changed back to VLAN 0.

 

Please find attached my redacted show tech-support from both Master (mesh portal) and Slave (mesh point), switch and a schematic showing the setup.

 

Thank you for any assistance you can provide.

 

 

Occasional Contributor I

Re: IAP 277 adding a mesh (point to point) to existing config

Hi VincentArriola. Thankyou for your update and help on this issue.

 

I had already completed the setup as outlined in your email with the exception of  

 

7.            On the mesh POINT set the Uplink values to VLAN X and BRIDGE ENABLED

When I attempt this I lose all connectivity with the planned mesh POINT so have to revert the changed via CLI and reload.

 

10.          On the POINT IAPs switch, set the PoE Profile “Upstream-TrunkPorts” to ENABLED(We use Aruba MAS switches, so this is more-or-less just setting the vlan to match the config on the IAP)

 

11.          On the POINT IAPs switch, set the port (0/0/0) to the “Upstream-TrunkPorts-Group” group (We use Aruba MAS switches, so this is more-or-less just setting the vlans to match the config on the IAP)

 

With points 10 & 11 I am using HP switches and trunking all with a native VLAN 4 on the switch ports the Aruba APs connect to.

 

VLAN 4 = Management (switches/APs and Clients) -- this is going into an existing site so I am unable to change this although I know it’s not ideal.

 

VLAN 5 = VOIP network.

 

The mesh network between Master Portal and Slave Point establishes OK and I can ping from the Master network switch to the Slave mesh point on VLAN 4. For the VOIP VLAN 5 I can ping through from Master switch to Slave network and back again.

 

From the Slave Mesh Point I can ping the Master Portal, VLAN 4 and 5 back on the Master switch and any clients connected on the Master switch.

 

My problems:

 

From the Master network switch I am unable to ping anything past the Slave Point on VLAN 4. Traceroute produces no results. We need the ability to connect to the remote Slave Point from the remote switch should it become ‘stranded’ as both Aruba’s will be installed on roof tops. We also need to be able to see the switch and clients connected on VLAN4 on the Slave site.

 

I know the problem is likely to be with eth0 bridging and/or switch port configuration. VLAN 5 connection is OK whereas VLAN 4 is not. As I said earlier I attempted to change the uplink VLAN to 4 on the Slave mesh Point but lost connection so this was changed back to VLAN 0.

 

Please find attached my redacted show tech-support from both Master (mesh portal) and Slave (mesh point), switch and a schematic showing the setup.

 

Thank you for any assistance you can provide.

Occasional Contributor I

Re: IAP 277 adding a mesh (point to point) to existing config

Hi VincentArriola. Thankyou for your update and help on this issue.

 

I had already completed the setup as outlined in your email with the exception of  

 

7.            On the mesh POINT set the Uplink values to VLAN X and BRIDGE ENABLED

When I attempt this I lose all connectivity with the planned mesh POINT so have to revert the changed via CLI and reload.

 

10.          On the POINT IAPs switch, set the PoE Profile “Upstream-TrunkPorts” to ENABLED(We use Aruba MAS switches, so this is more-or-less just setting the vlan to match the config on the IAP)

 

11.          On the POINT IAPs switch, set the port (0/0/0) to the “Upstream-TrunkPorts-Group” group (We use Aruba MAS switches, so this is more-or-less just setting the vlans to match the config on the IAP)

 

With points 10 & 11 I am using HP switches and trunking all with a native VLAN 4 on the switch ports the Aruba APs connect to.

 

VLAN 4 = Management (switches/APs and Clients) -- this is going into an existing site so I am unable to change this although I know it’s not ideal.

 

VLAN 5 = VOIP network.

 

The mesh network between Master Portal and Slave Point establishes OK and I can ping from the Master network switch to the Slave mesh point on VLAN 4. For the VOIP VLAN 5 I can ping through from Master switch to Slave network and back again.

 

From the Slave Mesh Point I can ping the Master Portal, VLAN 4 and 5 back on the Master switch and any clients connected on the Master switch.

 

My problems:

 

From the Master network switch I am unable to ping anything past the Slave Point on VLAN 4. Traceroute produces no results. We need the ability to connect to the remote Slave Point from the remote switch should it become ‘stranded’ as both Aruba’s will be installed on roof tops. We also need to be able to see the switch and clients connected on VLAN4 on the Slave site.

 

I know the problem is likely to be with eth0 bridging and/or switch port configuration. VLAN 5 connection is OK whereas VLAN 4 is not. As I said earlier I attempted to change the uplink VLAN to 4 on the Slave mesh Point but lost connection so this was changed back to VLAN 0.

 

Please find attached above my redacted show tech-support from both Master (mesh portal) and Slave (mesh point), switch and a schematic showing the setup.

 

Thank you for any assistance you can provide.

 

 

Aruba Employee

Re: IAP 277 adding a mesh (point to point) to existing config

net_sparrow
please double check if at your Mesh Point the admin state of your Eth0 port is up, as it goes to down per default as soon as you enable bridging on the Eth0 (please refer to point 1 in the second part of my previous post on how to do it).
Occasional Contributor I

Re: IAP 277 adding a mesh (point to point) to existing config

Hi Lukasz,

 

Thank you. I've confirmed the Slave Point Eth0 port is active. I can see the Slave Point MAC on the switch and protocol up.

 

Importantly I can pass traffic back across from the Slave switch VLAN 5 but not VLAN 4.

 

Untitled.jpg

Aruba Employee

Re: IAP 277 adding a mesh (point to point) to existing config

Hi net_sparrow,

ok, then the next place to do the check is in the very next Tab of your wired profile applied on the ETH0 port, namely under VLAN. Please double check, both native VLAN and allowed VLANs there, if it corresponds to what you wanted to set. You may also want to double check security settings in the third tab, too.

wired-profile-vlan.JPG

Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: