Wireless Access

Reply
MVP Guru

Re: Controller doesn't seem to pass ip addresses from various vlans

 

That looks good , Now see if you can ping the IP address assigned to those VLANs from the controller ?

Thank you

Victor Fabian
Lead Mobility Architect @WEI
AMFX | ACMX | ACDX | ACCX | CWAP | CWDP | CWNA
Occasional Contributor II

Re: Controller doesn't seem to pass ip addresses from various vlans

MASTER


(3600_Master) #ping 10.12.20.1
Press 'q' to abort.
Sending 5, 100-byte ICMP Echos to 10.12.20.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1.631/2.8256/5.594 ms

(3600_Master) #ping 10.12.21.1
Press 'q' to abort.
Sending 5, 100-byte ICMP Echos to 10.12.21.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1.515/16.1898/61.164 ms

(3600_Master) #ping 10.12.22.1
Press 'q' to abort.
Sending 5, 100-byte ICMP Echos to 10.12.22.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1.181/5.1252/12.016 ms

(3600_Master) #ping 10.12.23.1
Press 'q' to abort.
Sending 5, 100-byte ICMP Echos to 10.12.23.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1.271/7.735/15.699 ms

 

LOCAL


(Aruba7210-US) #ping 10.12.20.1
Press 'q' to abort.
Sending 5, 100-byte ICMP Echos to 10.12.20.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1.009/1.4772/1.83 ms

(Aruba7210-US) #ping 10.12.21.1
Press 'q' to abort.
Sending 5, 100-byte ICMP Echos to 10.12.21.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1.048/5.0836/20.198 ms

(Aruba7210-US) #ping 10.12.22.1
Press 'q' to abort.
Sending 5, 100-byte ICMP Echos to 10.12.22.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 0.736/2.6836/7.683 ms

(Aruba7210-US) #ping 10.12.23.1
Press 'q' to abort.
Sending 5, 100-byte ICMP Echos to 10.12.23.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 0.894/3.7322/6.036 ms

 

all seem to ping just fine.

 

MVP Guru

Re: Controller doesn't seem to pass ip addresses from various vlans

 

And also if you can get an IP connecting your laptop to one of the ports on the controller using one of the VLANs that are not working

 

 

Thank you

Victor Fabian
Lead Mobility Architect @WEI
AMFX | ACMX | ACDX | ACCX | CWAP | CWDP | CWNA
MVP Guru

Re: Controller doesn't seem to pass ip addresses from various vlans

 

When you get a chance please share your VAP config ?

 

 

Thank you

Victor Fabian
Lead Mobility Architect @WEI
AMFX | ACMX | ACDX | ACCX | CWAP | CWDP | CWNA
MVP Guru

Re: Controller doesn't seem to pass ip addresses from various vlans

Do you get an IP if you just assign one VLAN to the VAP ?
Thank you

Victor Fabian
Lead Mobility Architect @WEI
AMFX | ACMX | ACDX | ACCX | CWAP | CWDP | CWNA
Highlighted
Occasional Contributor II

Re: Controller doesn't seem to pass ip addresses from various vlans

!
wlan virtual-ap "FortOsage-Mobile-vap_prof"
aaa-profile "FortOsage-Mobile-aaa_prof"
ssid-profile "FortOsage-Mobile-ssid_prof"
vlan 720-722
band-steering

 

!
wlan virtual-ap "FortOsage-Mobile-vap_prof"
aaa-profile "FortOsage-Mobile-aaa_prof"
ssid-profile "FortOsage-Mobile-ssid_prof"
vlan 720-722
band-steering

 

 

yes my laptop directly connected was able to recieve an address of 10.12.21.4 /24 

 

i did allow vlan 721 and 722 on the 0/1 port of my master controller.

Occasional Contributor II

Re: Controller doesn't seem to pass ip addresses from various vlans

yes.

Occasional Contributor II

Re: Controller doesn't seem to pass ip addresses from various vlans

its when i add more then one is when the problems start.

MVP Guru

Re: Controller doesn't seem to pass ip addresses from various vlans

I don't think you an issue but based on the way VLAN pooling algorithm works devices will be place in the same VLAN :


The hashing algorithm does not place users into the available pool of VLANs in a round-robin method. Ten clients that join a WLAN are not load balanced equally among the VLANs. Instead, the distribution is based on the output of the hash. One VLAN might have more users than the others. For example, consider 150 clients that join a WLAN with just two VLANs in the pool and with 80 addresses per VLAN available for clients. Based on the output of the hashing algorithm, 80 clients are placed in one VLAN and 70 in the other. When the 151st client joins, the output of the hash might place the client in the VLAN whose scope of 80 addresses has already exhausted. The result is that the client cannot obtain an IP. To avoid such a rare situation, the network administrator should design pools with sufficient number of user VLANs and DHCP scopes to accommodate the user density.


What exactly you are trying to accomplish ?
Thank you

Victor Fabian
Lead Mobility Architect @WEI
AMFX | ACMX | ACDX | ACCX | CWAP | CWDP | CWNA
Aruba Employee

Re: Controller doesn't seem to pass ip addresses from various vlans

can you provide us the output for 

 

show ap association client-mac <client-mac>

show user | in <mac>

Vinod Kumaar AVM ACMX, ACDX
Principal Network Engineer
Customer Advocacy | Aruba Networks Inc.

Did something you read in the Community solve a problem for you? If so, click "Accept as Solution" in the bottom right hand corner of the post.
Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: