- If you need clarification, ask it in the comment box above.
- Better answers use proper spelling and grammar.
- Provide details, support with references or personal experience.
Tell us some more! Your answer needs to include more details to help people.You can't post answers that contain an email address.Please enter a valid email address.The email address entered is already associated to an account.Login to postPlease use English characters only.
Tip: The max point reward for answering a question is 15.
What do you need it configured to support? Multiple subnets? VoIP support? Here's an example to support 2 subnets, VLAN 1 Data and VLAN 2 Voice. This switch is the VLAN router for the site and it is also the default gateway for all the devices on the network.
show running-config
Running configuration:
; J4899A Configuration Editor; Created on release #H.10.50
hostname "HP 2650 dot 11 layer 3" snmp-server contact "Your contact info here" snmp-server location "Server Rack - Upper Switch" time timezone -5 time daylight-time-rule Continental-US-and-Canada interface 49 name "Uplink to HP2650 port 49 - 192.168.105.12" flow-control exit interface 50 name "Uplink to HP2650 port 49 - 192.168.105.13" flow-control exit ip routing timesync sntp snmp-server community "public" Unrestricted vlan 1 name "Data" untagged 1-46 ip address 192.168.105.11 255.255.255.0 ip helper-address 10.50.3.2 tagged 49-50 no untagged 47-48 exit vlan 2 name "Voice" untagged 47-48 ip address 10.50.3.11 255.255.255.0 ip helper-address 10.50.3.2 tagged 1-46,49-50 exit ip route 0.0.0.0 0.0.0.0 192.168.105.1 spanning-tree Always turn on Spanning Tree spanning-tree priority 0 This switch is the master Spanning Tree operator. password manager password operator
Create the same VLAN on all the switches that will need this VLAN. All ports that link to another switch should have ALL VLAN's set to tagged. This one VLAN should not have an IP address on any of your switches. This way it won't get routed by any of your users.
This switch will not function as a DHCP server itself. You will need to have a DHCP server on the VLAN with the access points to give out IP's to the wireless users.
HP has free design and configuration services http://www.procurve.com/customercare/services/design-center/index.htm
hostname "Switch1"
qos dscp-map 101110 priority 6
snmp-server community "public" Unrestricted
vlan 1 name "Data_Vlan" untagged 1-28 ip address 192.9.180.19 255.255.255.0 exit vlan 2 name "Voice_Vlan" ip address 10.9.180.5 255.255.255.0 qos dscp 101110 tagged 1-28 voice exit
Program the port that the PBX is in as a untagged port on Vlan 2
First, be sure to assign an ip address(in the proper subnet) to each VLAN.
Second, use the ip helper-address command in the context of each VLAN, the address used should be the address of the DHCP server
Third, Add a scope for each additional VLAN on the DHCP server.
The switch will route the DHCP request to the proper server based on the ip helper-address command parameter and based on the ip address of the VLAN that is passed tot he server, a DHCP address in the proper subnet is automatically configured.
The Procurve 1800 SWITCH series supports 802.1p, 802.1q VLANS, 802.3ad LACP, 802.3x Flow control, RFC1534 DHCP/BOOTP interoperation, the Cisco 2800 series is a ROUTER and dependant on its IOS version will support a multitude of routing/security features that the Procurve just isnt designed to do.
×