- Community Home
- >
- Networking
- >
- Switching and Routing
- >
- Aruba & ProVision-based
- >
- New DHCP Scope not assigning IP to VLAN
-
- Forums
-
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
- HPE Blog, Austria, Germany & Switzerland
- Blog HPE, France
- HPE Blog, Italy
- HPE Blog, Japan
- HPE Blog, Middle East
- HPE Blog, Russia
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
-
Blogs
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Blog, Latin America
- HPE Blog, Middle East
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
-
Information
- Community
- Welcome
- Getting Started
- FAQ
- Ranking Overview
- Rules of Participation
- Tips and Tricks
- Resources
- Announcements
- Email us
- Feedback
- Information Libraries
- Integrated Systems
- Networking
- Servers
- Storage
- Other HPE Sites
- Support Center
- Aruba Airheads Community
- Enterprise.nxt
- HPE Dev Community
- Cloud28+ Community
- Marketplace
-
Forums
-
Blogs
-
Information
-
English
- 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
- Email to a Friend
- 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
- Email to a Friend
- 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
- Email to a Friend
- 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
- Email to a Friend
- 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
Hewlett Packard Enterprise International
- Communities
- HPE Blogs and Forum
© Copyright 2021 Hewlett Packard Enterprise Development LP