• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 801
  • Last Modified:

Connect Cisco 4402 WLC WLAN VLAN to HP Procurve

hello all,

Not sure what I am doing incorrectly... Have a WLC with the app and management bound to port 1 untagged for vlan 1. This is connected to one  one switch using the 172.0.0.0/16 network. I also have a guest vlan 8 created and bound to port 2 using 172.16.0.0/16. This port is attached to a procurve gb managed switch with a matching vlan 8 and  an IP address acting as the gateway for the vlan 8.  

Issue: cannot ping the WLC interface from switch and vice Vera. Appreciate the help in advance.

Glen
0
GRGrayban
Asked:
GRGrayban
  • 4
  • 2
1 Solution
 
jburgaardCommented:
Is this a Q regarding L3 operation (routing) on a HP?
To route there must be a
IP ROUTING
statement

vlan1 network = 172.0.0.0/16 , a typo?

output from show run would be nice
0
 
GRGraybanAuthor Commented:
More about mapping vlans from a cisco to hp. The address is a supernet.

I can get a run posted. Maybe WLC will not accept supernet but that would be strange.  Too new to this hardware to know if that would be a limitation.  It does hand out dhcp addresses using that scope I think that the supernet is not the problem.
0
 
GRGraybanAuthor Commented:
I'll reset to a classfull c mask to check instead of the cidr.

Anyone else ever map cisco and hp vlans?

Thx for any help.
0
Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

 
Craig BeckCommented:
On the WLC set the management and guest interfaces VLAN to 0.  This means 'untagged'.

On the HP switch...

vlan 1
 untagged 1
vlan 8
 untagged 2

Open in new window

Try that and see how it goes.  If you're still stuck post the switch config.
0
 
GRGraybanAuthor Commented:
That worked. I was handling the WLC like another router and thought the guest interface needed to be configured to be on the same vlan as the procurve was set. In my case the vlan was 8 on the procurve, so i had set the wlc to 8 also. what did i miss here?
0
 
Craig BeckCommented:
You tagged on the WLC but untagged on the HP. That won't work.
0
 
GRGraybanAuthor Commented:
Knows his stuff! Thx craigbeck.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Improved Protection from Phishing Attacks

WatchGuard DNSWatch reduces malware infections by detecting and blocking malicious DNS requests, improving your ability to protect employees from phishing attacks. Learn more about our newest service included in Total Security Suite today!

  • 4
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now