ExtremeWireless (WiNG)

  • 1.  MiNT and MCX

    Posted 11-08-2018 08:14
    Hello,

    A site has some AP7562s. Some are no mesh, others are mesh points root and non root. They are adopted to a VX9000 with layer 3 level 2 links.

    Are they all supposed to see each other via level 1 vlan links?

    No mesh AP:

    - has level 1 vlan links to all other APs except the non root ones
    - can't ping non root APs
    - can mint ping non roots APs
    - mint route table shows all APs

    Non root mesh AP:

    - has level 1 vlan link only as self
    - has level 1 mesh link and it's root AP as neighbour
    - can't ping any other AP (but can ping everything else)
    - can mint ping other APs
    - mint route table shows all APs

    Relevant config:

    rf-domain GNC
    timezone Europe/Prague
    country-code hr
    use smart-rf-policy GNC-SMART-RF
    channel-list dynamic
    control-vlan 113

    meshpoint GNC-Mesh-Point
    meshid GNC-Mesh-ID
    beacon-format mesh-point
    control-vlan 113
    allowed-vlans 112-113
    security-mode psk
    wpa2 psk 0 xxx
    no root

    profile ap7562 GNC-AP7562-MCX
    interface radio2
    placement outdoor
    meshpoint GNC-Mesh-Point bss 1
    interface ge1
    switchport mode trunk
    switchport trunk allowed vlan 112-113
    switchport trunk native vlan 113
    interface vlan113
    ip address dhcp
    ip dhcp client request options all
    meshpoint-device GNC-Mesh-Point
    preferred interface 5GHz

    ap7562 XX-XX-XX-XX-XX-XX
    use profile GNC-AP7562-MCX
    use rf-domain GNC
    hostname GNC-RAP06
    meshpoint-device GNC-Mesh-Point
    root

    ap7562 XX-XX-XX-XX-XX-XX
    use profile GNC-AP7562-MCX
    use rf-domain GNC
    hostname GNC-AP07
    no rf-domain-manager capable

    Thanks.

    Best regards.



  • 2.  RE: MiNT and MCX

    Posted 11-08-2018 13:02
    Non root MCX AP will only see root as neighbor.
    Non Mesh APs will not see non-root as neighbor.
    Devices should be able to ping each other via L3 or Mint.

    Config provided is not sufficient to address ping query, advise opening up a support ticket with GTAC for further troubleshooting.


  • 3.  RE: MiNT and MCX

    Posted 11-08-2018 13:02
    Thanks for replying.

    Did some additional testing, results below:

    MPR can't resolve MAC of MP (ping doesn't work)
    MP can resolve MAC of MPR (ping doesn't work)

    Wired PC can't resolve MAC of MP (ping doesn't work)
    MP can resolve MAC of same wired PC (ping works | wired PC can now ping MP as well)



  • 4.  RE: MiNT and MCX

    Posted 11-08-2018 17:00
    Hello, Please, clarify following - all APs adopted on VX - APs and VX are on different RFD - wireless clients talking to MP can ping hosts on backbone and vice versa Misha


  • 5.  RE: MiNT and MCX

    Posted 11-08-2018 17:00
    Hi Misha,

    - all APs adopted on VX - yes
    - APs and VX are on different RFD - yes
    - wireless clients talking to MP can ping hosts on backbone and vice versa - remote site for guests, can't really check



  • 6.  RE: MiNT and MCX

    Posted 11-08-2018 17:00
    MCX designed to provide wireless (and wired) client connectivity to backbone resources while handling wireless client roaming. Root APs is also taking additional care to eliminate possible loops. From this perspective bidirectional pinging infrastructure can not deliver representative results, as by default AP is tuned for wireless client handling. Internal and wired clients may require additional bridge conf. As soon you have all APs adopted and wireless clients can ping backbone - I see no reasons to worry except they also have wired clients connected to MPs Ethernet. Misha