Solved

AP460e/NX5500 Assistance

  • 12 February 2021
  • 8 replies
  • 58 views

I have a few questions related to the aP460e and NX5500.

 

1: How do I console in to the 460e / and or see the gui of it? I have a console cable and when I try to console in with putty this is what I see. 

Console Screen
  1. The reason I need to get in to it is because I need to tell it the IP address of the NX5500 I have because it is on a different broadcast domain. Would I need to do this manually on all of my APs that won’t be on the same network as the controller or is there a way to automate adding the controllers IP address? Also is that the only thing I need to do to get the controller to adopt it or do I need to mess around with IPSEC at all? I also do not have any clusters configured. 
  2. This question should be easy but I’m having a hard time with it at the moment. Is there a way to make it so access points in different RF Domains broadcast different SSIDs? All I’m seeing right now is the wireless lans under configuration and if they’re enabled or disabled. I can’t find a way to map certain SSIDs to an RF Domain or AP profile.
  3.  Finally what is the best way to get updated AP software onto the controller so it can update devices? I’m even fine using a USB device.

 

I understand if these take some time to answer. The answers I get from you guys are always really helpful so thank you again in advance for your time and any of the questions you’re able to answer for me.

icon

Best answer by Christoph S. 15 February 2021, 22:09

Hello Seth,

 

Layer 3 adoption is the way to go in this case; however, there are 3 methods for layer 3 adoption as such:

 

1 - Configure option 191 on your DHCP server. Once an AP is plugged in it will pull the necessary information for layer 3 adoption. This is an automated way of doing this

2 - Configuring the controller host command on APs, per instructions sent previously. This will have to be configured on APs once plugged in at remote site

3 - Prestage the APs, meaning adopt them locally by the controller and have them pull all the necessary information then install them remotely. They should know how to get back to the controller thereafter if all is properly configured. 

 

I hope this helps,

View original

8 replies

Userlevel 6

Hello Seth,

 

1 - If consoling in please use baud rate (speed) 115200

2 - Please elaborate on what you are trying to do

3 - check step 4 in this article: https://extremeportal.force.com/ExtrArticleDetail?an=000088793

4 - Here are some instructions on upgrading the controllers and APs at remote sites:

https://extremeportal.force.com/ExtrArticleDetail?an=000081743

https://extremeportal.force.com/ExtrArticleDetail?an=000082030

 

Regards,

Wow! Thank you @Christoph S. those articles are beyond helpful and gave me just the information I needed to get going.

 

So for question number 2 let me make a crude drawing and fake IP addresses to kind of show what I’m trying to do.

 

So I have two buildings both with WiNG access points that can be adopted by the NX5500. The buildings networks are connected together and can access devices between them but they’re on their own subnet. 

 

The building with the NX5500 can see the access points at that location and adopt them. However because the second building is on it’s own broadcast domain I don’t think I’ll be able to have the NX5500 adopt building 2’s access points unless I configure a setting on each access point with layer 3 adoption or telling it the IP address of the NX5500.

 

Is this the only way to achieve adoption for this scenario? 

https://extremeportal.force.com/ExtrArticleDetail?an=000081714&_ga=2.103946816.1775626189.1612883387-12488063.1609267507

 

 

@Christoph S. I guess thinking about this leads me to one last question. Both networks use vlan 1, is this going to be an issue? Currently at building 2 we have a virtual controller connected to the switch but we’d be changing that to the NX5500 at the other building on a different network. Is there a way to specify which DHCP server I want the RF Domain or Profile to use since I don’t want it to use the one it’s connected to?

Userlevel 6

Hello Seth,

 

Layer 3 adoption is the way to go in this case; however, there are 3 methods for layer 3 adoption as such:

 

1 - Configure option 191 on your DHCP server. Once an AP is plugged in it will pull the necessary information for layer 3 adoption. This is an automated way of doing this

2 - Configuring the controller host command on APs, per instructions sent previously. This will have to be configured on APs once plugged in at remote site

3 - Prestage the APs, meaning adopt them locally by the controller and have them pull all the necessary information then install them remotely. They should know how to get back to the controller thereafter if all is properly configured. 

 

I hope this helps,

I meant to put your other answer as the best and just like this new one but they both answered my questions. You are the best @Christoph S. Thank you so much for all your time you’ve spent answering my questions.

@Christoph S. This worked fine, the AP is adopted by the controller now.

The controller should just manage the AP settings even though it’s at a remote building, which it is doing that. I made a test SSID just to see how it would be handled. You may or may not know why but for some reason the ping or time it takes to ping google or elsewhere is very high. In this picture I’m adding its the test ssid vs what we have on our old system. I have everything configured the same as the old system so I’m not sure if it has something to do with the AP now being managed at a remote building now. 

    I’m also not sure if it’s because the AP460e I’m testing it on doesn’t have antennas yet, or if something weird is going on and I need to use different vlans.

Here are some of the errors I’m setting when consoled into the AP:

 

<4>CCB:10:BAD_PACKET:  Bcast/Mcast ICMP not allowed :

and

 <4>CCB:37:INVALID PADDING:  hop-by-hop extension header contains more than one pad1 option back to back

and

 <4>CCB:8:IP-MAC CONFLICT:  Conflict in ip-mac binding between packet and snoop table data : Vlan = 1, 

 

 

any ideas or suggestions to test out?

@Christoph S. I tested out if the reason was it being connected to the controller or not. It’s slow even when not adopted by the controller so I’m back to thinking maybe it’s because I’m using a 460e without antennas.

 

Something I did notice is even though I typed in the controller host command and saved the configuration, if I reboot the access point and check the adoption status it defaults to becoming it’s own controller still and I have to type in the controller host command again. Is there a way to get that to persist?

Userlevel 6

Hello Seth,

If you’re saving the settings (com wr) on the AP then they should persist a reboot. Something else is happening here. The easiest way to do this would be to follow these steps:

 

On the controller completely remove the AP, this will insure that no lingering settings are being pushed to the AP once it adopts:

1 - From GUI go to Configure > Devices > Device Configuration > Select AP > Click on the Delete button > Click on Commit and Save

2 - On the AP, reconfigure the controller host commands in ‘Self’ then save and have it adopt

3 - Once adopted, SSH into the AP again and run the following commands:

#self
#show context

4 - Verify that the controller host commands are still there. 

5 - On the Controller make sure you configure same commands in the AP profile and also confirm that the host command settings are also configured for this AP as overrides:

#config
#host <hostname>
#show context

 

I hope this helps,

 

Chris

Reply