- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- Re: DHCP across vlans not working
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
тАО05-12-2010 03:31 AM
тАО05-12-2010 03:31 AM
Re: DHCP across vlans not working
>>>
vlan 1
name "DEFAULT_VLAN"
untagged 41-48
ip address 172.16.45.1 255.255.255.0
no untagged 3-40,Trk1
<<<
my remark would be :
"no untagged 3-40,Trk1" is not he same as "tagged 3-40,Trk1"
As Trk1 seems like your uplink to another switch, I would expect all vlans "tagged Trk1"
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-12-2010 03:49 AM
тАО05-12-2010 03:49 AM
Re: DHCP across vlans not working
I overlooked some info.
You say the 3Com is "setup vlan25 only".
Do you mean the 3Com knows about vlan 25?
or do you mean the 3Com is setup default (all ports vlan-1) but connects to the procurve vlan-25?
Then you must set the PVID of Trk1 ports to 25.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-12-2010 04:34 PM
тАО05-12-2010 04:34 PM
Re: DHCP across vlans not working
module 1 type J9147A
ip default-gateway 172.16.45.1
ip routing
vlan 1
name "DEFAULT_VLAN"
untagged 41-48
ip address 172.16.45.1 255.255.255.0
no untagged 1-40
exit
vlan 25
name "lvl2"
untagged 1-2
ip helper-address 172.16.45.10
ip address 172.16.25.1 255.255.255.0
exit
vlan 15
name "lvl1"
untagged 3-40
ip helper-address 172.16.45.10
ip address 172.16.15.1 255.255.255.0
exit
ip route 0.0.0.0 0.0.0.0 172.16.45.254
snmp-server community "public" unrestricted
snmp-server contact "Jeff Powers Ext 237" location "Server Room Lvl 1"
no autorun
password manager
password operator
DHCP server is plugged into port 42 so untagged DEFAULT VLAN 1
DHCP server GW is 172.16.45.1
The uplink is plugged into Port 1 untagged VLAN 25 lvl2 the 3com switch is set to untagged VLAN 25 lvl2 all ports.
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-12-2010 09:34 PM
тАО05-12-2010 09:34 PM
Re: DHCP across vlans not working
Looking at the out put from wireshark this is from a successful ipconfig release / renew.
I would get a capture from a failed attempt from the host and the server, the idea is to see where the packet flow fails.
Just a quick one you don't need a 'ip default-gateway' command if you are running 'ip routing'
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-13-2010 12:15 AM
тАО05-13-2010 12:15 AM
Re: DHCP across vlans not working
I figured this out with watching the packet sniffer and seeing all these spaning tree packets which seemed to be every other packet on the wire.
Will report back tomorrow if this is indeed a solution. Thanks for your help I was going crazy is sometimes hard being a one man band.
Oh I have also turned off the default gateway and all seems happy so things are being fine tuned.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-14-2010 08:59 AM
тАО05-14-2010 08:59 AM
Re: DHCP across vlans not working
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-14-2010 03:05 PM
тАО05-14-2010 03:05 PM
Re: DHCP across vlans not working
Though you want to make sure STP on the same version for both switches. I suggest RSTP or MST as STP may be too slow and causing your issues.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-16-2010 04:33 PM
тАО05-16-2010 04:33 PM
Re: DHCP across vlans not working
If I renable LACP on 2 ports between the switches for 2GB connectino do I need spanning tree if one of the links drops out?
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-17-2010 03:46 AM
тАО05-17-2010 03:46 AM
Re: DHCP across vlans not working
May 17, 2010 00:33:28 GMT
If I renable LACP on 2 ports between the switches for 2GB connectino do I need spanning tree if one of the links drops out?
----
No. LACP makes the ports look like one, even for STP.
So, if one link of a LACP group drops and comes back, STP does not know anything occurred.
You see this as well when you create a LACP trunk group, the interfaces become a new interface type of "TRKx".
If you do a 'show span' you will see the interface TRKx at the bottom of the list.
hth...Jeff
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-17-2010 06:22 AM
тАО05-17-2010 06:22 AM
Re: DHCP across vlans not working
ip default-gateway 172.16.45.1
ip route 0.0.0.0 0.0.0.0 172.16.45.254
each command was pointing to another place, but i think both commands has the same result but pointing to diff. location.
Jeff mentioned that he removed the defualt gateway, that's why it works now.
Not sure if what i mentioned makes sence :D