- Community Home
- >
- Networking
- >
- Switching and Routing
- >
- Aruba & ProVision-based
- >
- New DHCP Scope not assigning IP to VLAN
Categories
Company
Local Language
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
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
Community
Resources
Forums
Blogs
- 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
тАО12-17-2015 02:23 PM
тАО12-17-2015 02:23 PM
Hi
We have 7 HP Procurve Switches around the building, and 1 DHCP windows server 2008.
On server 2008, there are already 8 dhcp scopes. On Switches, there are 8 VLANs pointing back to DHCP server with ip helper-address 10.89.31.6.
Problem is:
On the server 2008 DHCP, I created a new scope:
NEW-WIFI
IP Scope: 10.89.41.5 to 10.89.41.250
subnet mask: 255.255.255.0
Gateway: 10.89.41.1
On the core switch, I created vlan 70:
VLAN 70
name тАЬNEW-WIFIтАЭ
ip helper-address 10.89.31.6
ip address 10.89.41.1 255.255.255.0
tagged 44-48
exit
On one of hub switches, I created vlan 70 also:
VLAN 70
name тАЬNEW-WIFIтАЭ
untagged 40
tagged 45-48
no ip address
exit
Then I plugged a device in, itтАЩs not getting ip address from dhcp.
Where did I do wrong?
Many thanks in advance!
Ji
Solved! Go to Solution.
- Tags:
- DHCP
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-17-2015 11:30 PM
тАО12-17-2015 11:30 PM
Re: New DHCP Scope not assigning IP to VLAN
1st step is checking routing
Can server2008 ping the new VLAN interface 10.89.31.6 ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-18-2015 12:20 AM
тАО12-18-2015 12:20 AM
Re: New DHCP Scope not assigning IP to VLAN
10.89.31.6 is the windows dc server itself.
From the server, I can ping 10.89.41.1 which is the gateway of the new scope and ip address for new vlan.
But my laptop or WAP just not getting any IP assigned.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-18-2015 04:39 AM
тАО12-18-2015 04:39 AM
SolutionFound the problem.
The switch I tested with was not connected to core switch directly. But via another switch in a different hub room.
New VLAN was not setup on that switch, although no port was used.
Had to create vlan on all switches and it is working now.
Cheers
Ji