Reset Search
 

 

Article

WiNG APs not showing up on the dashboard when deploying them in a separate domain

« Go Back

Information

 
TitleWiNG APs not showing up on the dashboard when deploying them in a separate domain
Symptoms
When you check the APs from the NOC or adopting controllers, after you click on a separate domain, you just see one AP. Normally, when you refresh that domain, you will be able to see the hostname of different APs, each time you refresh it.
Environment
  • All Summit WM3000 Series Controllers
  • ExtremeWiNG Controllers
  • WirelessWiNG Controllers
  • ExtremeWiNG Access Points
  • WirelessWiNG Acess Points
  • WiNG v5.X Software
Cause
The control-vlan is not correctly propagated on the domain, or the adoption is not correctly set.
Resolution
  • Ensure the control-vlan is defined on the rf-domain, as this example:
rf-domain yourdomain
 timezone CET
 country-code xx
 control-vlan 133
  • Ensure that control-vlan is propagated correctly on the switches from that deployment, so the APs are able to see each other over layer 2.
  • Check on the rf-domain manager the MiNT links established between all the devices on that domain. These commands are done from the NOC controller, as an example: 
#show global domain managers
-----------------------------------------------------------------------------------------------------
                      RF-DOMAIN                              MANAGER          HOST-NAME  APS  CLIENTS
-----------------------------------------------------------------------------------------------------
                            NOC                    00-0C-29-A5-44-DC               VX       0        0
                        your-domain                00-15-70-81-81-CA    your-domain-manager 3        0

#show mint links details on your-domain-manager
2 mint links on 75.01.20.F8:
link vlan-133 at level 1, 3 adjacencies, DIS 4D.85.C5.94:
  cost 10, hello-interval 4, adj-hold-time 13
  created: for the control-vlan
  adjacency with 75.01.08.58, state UP (13 days), last hello 2 seconds ago
  adjacency with 75.01.08.FC, state UP (5 days), last hello 0 seconds ago
  adjacency with 75.01.09.40, state UP (13 days), last hello 2 seconds ago
link ip-10.15.1.26:24576 at level 2, 1 adjacencies, (used):
  local IP x.x.x.x
  cost 100, hello-interval 15, adj-hold-time 46
  created: by MLCP
  adjacency with 12.0F.01.1A, state UP (13 days), last hello 0 seconds ago
The correct output should have, level 2 MiNT link with the adopting controller and a link over the control vlan with different adjacencies, depending on the number of devices deployed on that domain. 
 
Additional notes
If you have everything configured as above, and the issue is still persistent, contact GTAC support (How to contact Extreme Networks Global Technical Assistance Center (GTAC))

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255