- Community Home
- >
- Networking
- >
- Switching and Routing
- >
- HPE Aruba Networking & ProVision-based
- >
- Re: 2920 DHCP pools not functional with routed upl...
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
Forums
Discussions
Discussions
Discussions
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
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
08-05-2015 01:39 PM
08-05-2015 01:39 PM
i just purchased 2 2920's. they didnt have dhcp functionality until i updated them to the latest software rev. after doing so all seemed well. i created 2 dhcp pools and configured them for 2 vlans. these were working as intended while on my bench.
as these units will go offsite i wanted to do as close to a real test as i could. i took it to our core switch and plugged in directly with a /30 network connecting to vlan 690. only one untagged port is used for 690 (port 48).
that worked, all subnets were pingable etc. However, now the dhcp server stopped providing addressing for ANY dhcp pools. if i disable port 48, i get dhcp again. its repeatable.
i completely disabled and wiped the DHCP server and re-created it with the same results.
Any suggestions are appreciated.
; J9729A Configuration Editor; Created on release #WB.15.17.0007
; Ver #07:eb.8f.fc.f3.ff.37.2d:89
hostname "ATL-2920"
module 1 type j9729a
qos dscp-map 011000 priority 5
no timesync
ip route 0.0.0.0 0.0.0.0 vlan 690
ip routing
interface 48
disable
rate-limit all out kbps 10000
exit
snmp-server community "" operator
snmp-server contact "" location "Atlanta"
oobm
ip address dhcp-bootp
exit
vlan 1
name "DEFAULT_VLAN"
no untagged 1-48
untagged A1-A2,B1-B2
ip address dhcp-bootp
exit
vlan 620
name "Data"
untagged 1-47
ip address 172.29.20.254 255.255.255.0
qos priority 3
dhcp-server
exit
vlan 650
name "Voice"
tagged 1-47
ip address 172.29.50.254 255.255.255.0
qos dscp 101110
voice
dhcp-server
exit
vlan 670
name "management"
ip address 172.29.70.254 255.255.255.0
exit
vlan 690
name "Uplink "
untagged 48
ip address 192.168.255.218 255.255.255.252
exit
primary-vlan 670
no tftp server
no autorun
no dhcp config-file-update
no dhcp image-file-update
dhcp-server pool "620"
authoritative
default-router "172.29.20.254"
dns-server "10.0.30.1,10.0.30.2"
domain-name "llsa.local"
network 172.29.20.0 255.255.255.0
range 172.29.20.10 172.29.20.200
exit
dhcp-server pool "650"
authoritative
default-router "172.29.50.254"
dns-server "10.0.30.1,10.0.30.2"
domain-name "llsa.local"
network 172.29.50.0 255.255.255.0
range 172.29.50.10 172.29.50.200
exit
dhcp-server enable
password manager
password operator
Solved! Go to Solution.
- Tags:
- DHCP
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-05-2015 05:10 PM
08-05-2015 05:10 PM
SolutionI have a solution,
if you follow this document.
it shows step by step how to create multipule dhcp scopes per vlan.
on my other switches, my default-router was always the vlan interface. in this instance, it HAS to be x.x.x.1
once that was configured, it is now working as intended.
i dont know why this would work while not connected to a default route, but hey, there it is.