- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- J9001A wireless module problem
Switches, Hubs, and Modems
1748259
Members
3833
Online
108760
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-08-2006 03:26 AM
тАО10-08-2006 03:26 AM
Hi,
I've just installed a J9001A wireless module in my 5308xl Procurve switch, I can access the configuration via the procurve command line, but cannot get the module to respond to ping. The module requires its own address, but I'm not sure if this should be an entirely new subnet address, and what should the default gateway be ? I currently have configured several vlans on the 5308 using the 10.x.x.x address range, eg. 10.11.0.0, 10.12.0.0 etc. Can anyone explain where the J9001a fits into this scenario ?
Thanks,
Tony.
I've just installed a J9001A wireless module in my 5308xl Procurve switch, I can access the configuration via the procurve command line, but cannot get the module to respond to ping. The module requires its own address, but I'm not sure if this should be an entirely new subnet address, and what should the default gateway be ? I currently have configured several vlans on the 5308 using the 10.x.x.x address range, eg. 10.11.0.0, 10.12.0.0 etc. Can anyone explain where the J9001a fits into this scenario ?
Thanks,
Tony.
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-08-2006 03:45 PM
тАО10-08-2006 03:45 PM
Solution
Hi
By default, the wireless edge services module obtains an IP address from a DHCP server, and you can check the ip from CLI:
switch(config)# wireless-services c
switch(wireless-services-C)#show ip interface
and if you want to assign a static IP:
switch(wireless-services-C)(config)#interface vlan 1
switch(wireless-services-C)(config-if)#ip address a.b.c.d/xy
and for the Default gateway:
ProCurve(wireless-services-C)(config)# ip default-gateway a.b.c.d
Now for IP addressing, and since you have many subnets (Vlans), you can select the proper Vlan that must the wireless module works with,
Say you have 3 Vlans (subnest), and you've dedicated one of them for the Wireless so you configure the Wireless module within this Vlan interface and in its IP address range.
Anyway, after you assign an IP, then use the Web interface to login to the wireless module, you can see on the main screen the Management IP which is the IP for the 5300 switch.
In the menu bar on the left, select WLAN setup, and you will see the assigned Vlan for the Radio Ports.
You may have a different scenario like, using a dynamic Vlans along with the authentication,
and in this case you can assign an IP for the wireless module in the same subnet of the default-Vlan for management.
enough info. you can find here:
ftp://ftp.hp.com/pub/networking/software/5300xl-Wireless-Srvs-MgmtCfg-Aug2006-50135912.pdf
Good Luck !!!
By default, the wireless edge services module obtains an IP address from a DHCP server, and you can check the ip from CLI:
switch(config)# wireless-services c
switch(wireless-services-C)#show ip interface
and if you want to assign a static IP:
switch(wireless-services-C)(config)#interface vlan 1
switch(wireless-services-C)(config-if)#ip address a.b.c.d/xy
and for the Default gateway:
ProCurve(wireless-services-C)(config)# ip default-gateway a.b.c.d
Now for IP addressing, and since you have many subnets (Vlans), you can select the proper Vlan that must the wireless module works with,
Say you have 3 Vlans (subnest), and you've dedicated one of them for the Wireless so you configure the Wireless module within this Vlan interface and in its IP address range.
Anyway, after you assign an IP, then use the Web interface to login to the wireless module, you can see on the main screen the Management IP which is the IP for the 5300 switch.
In the menu bar on the left, select WLAN setup, and you will see the assigned Vlan for the Radio Ports.
You may have a different scenario like, using a dynamic Vlans along with the authentication,
and in this case you can assign an IP for the wireless module in the same subnet of the default-Vlan for management.
enough info. you can find here:
ftp://ftp.hp.com/pub/networking/software/5300xl-Wireless-Srvs-MgmtCfg-Aug2006-50135912.pdf
Good Luck !!!
Science for Everyone
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-09-2006 10:38 PM
тАО10-09-2006 10:38 PM
Re: J9001A wireless module problem
Thanks Mohieddin,
That points me in the right direction.
Tony
That points me in the right direction.
Tony
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP