HP VLAN Setup 2910Al

[jwc1972]

Hello

I Have Two Hp Switches 2910Ag. One switch in the office and another switch in the warehouse. The buildings are connected by Fibre
We are running windows server 2003 DC giving out Ip address of 192.168.1.*
Switch Office
Vlan1
Untagged 1-40
Tagged 48

Vlan 100
unatgged 41-47
tagged 48

I have the same setup for the warehouse switch. The question is I would like vlan1 to give out ip address of 192.168.1.* and the Vlan 100 to give out address 10.20.10.* Is this possiable? So when i connect a cable into port 42 it gives the client ip address 10.20.10.* is that correct?

[Mohammed Faiz · Accepted solution]

Hi,

Yes that is possible. You need to configure routing on one of your switches ("ip routing") and give it an IP address on both VLANs.
You can the configure an IP helper address on VLAN 100 to point to your DHCP server ("vlan 100 ip helper-address 192.168.1.x").
Then configure the new scope on your DHCP server.
Note that this setup will allow VLAN 1 clients to communicate with VLAN 100 clients (as the switch will route between the VLANs)

[jwc1972]

Cheers

I setup the Switch Office ip address is 192.168.1.220
Warehouse switch ip address is 192.168.1.221

What is ip address helper? is that the domain controller? How would i add ip routing in the config?

Switch Office

Vlan1
ip routing ?
ip address 192.168.1.* 255.255.255.0 ???
ip address helper ?
Untagged 1-40
Tagged 48

[Mohammed Faiz]

The command to enable routing is "ip routing". It's a global level command (i.e. not in the VLAN context)

The helper address is the address of your DC.

You need an IP address in both VLANs, i.e. on both address ranges.

e.g.

ip routing
vlan 1 ip address 192.168.1.1/24
vlan 100 ip address 10.20.10.1/24
vlan 100 ip helper address 192.168.1.DC_IP

[jwc1972]

Morning

Looks good before I crash the system!

Office Switch
VLAN 1
untagged 1-40
ip helper address (domain controller)
ip address 192.168.1.* 255.255.255.0
tagged 48

VLAN 100
untagged 41-47
ip helper address (domain controller)
ip address 10.20.10.* 255.255.255.0
tagged 48

Question how does port 41-47 give out ip address of 10.20.10.* ?

[Mohammed Faiz]

The way it works (roughly) is :

A PC connected to VLAN 100 sends a DHCP request which is a broadcast packet. As the switch has an IP on VLAN 100 it sees the broadcast and forwards it (from it's VLAN 100 ip address) to the IP helper address that is configured.
Your DC receives the DHCP request and returns a DHCP offer for the 10.20.10.* range because it can see that the DHCP request was forwarded from the 10.20.10.x address of the switch.

[jwc1972]

Thank very good answer, Last queston I promise, So on the Domain Controller I can create a New Scope of 10.20.20.* to sit along side the 192.168.1.* scope

[Mohammed Faiz]

Yes, you'll need that scope on your DC. Don't forget to add a router option and enable the scope once you've created it!

[jwc1972]

Hello Again

Networks!!! I been creating a new scope of 10.5.5.11 255.255.255.0 Is this a New scope or a Muplitecast scope. We have 192.168.1.0 as the default scope?

[Mohammed Faiz]

It's just a normal scope (not a multicast scope)

[jwc1972]

Not Working! Help

Hostname "officeswitch"
mirror-port 1
ip default-gatway 192.168.1.1
ip routing
Vlan 1
name computers
untagged 1-40
ipaddress 192.168.1.221 255.255.255.0
tagged 48
no tagged 41-47
exit
vlan 100
name servers
unatgged 41-47
ip helper-address 192.168.1.35(dc)
ip address 10.5.5.11 255.255.255.0
tagged 48
intface 40
monitoe
exit

On our Domain controller, I add a new scope of 10.5.5.0 starting addess 10.5.5.11 - 20
scopt options
router 003 192.168.1.1 degault gateway

When i plug any cat5 cable into 41-47 I get an private ip address. What i'm i missing?

[Mohammed Faiz]

Ok, there are a few issues there.

You've got 10.5.5.11 as the IP for VLAN 100 on your switch but you said you have "a new scope of 10.5.5.0 starting addess 10.5.5.11 - 20", there's obviously a conflict there with 10.5.5.11.

Also you've set the router option on your scope as "192.168.1.1". That needs to be an IP on VLAN 100.

But to check your DHCP helper address is working try this:

- Configure a static IP of 10.5.5.12 on a client and connect it to port 41.
- Can you ping the DC, 192.168.1.35?

If you can't then you most likely have a routing problem (first suspect is that 192.168.1.1 does not know how to route to the 10.5.5.0 network).

If you can ping the DC then there may just be a problem with the new scope (check that it's definitely enabled)

[jwc1972]

hello

I will check the ip helper, so the ipaddress should 10.5.5.0 255.255.255.0 it say it exist can i delete that line and start again?

[jwc1972]

Morning

I set the network card on the client machine to 10.5.5.12 can't ping the 192.168.1.1 or 192.168.1.35

I changed the scope of dchp server to 10.5.5.0 start at 10.5.5.1 to 254 is that correct?

On the scope option I don't understand why I need to add ip address on vlan 100?

I added 003 router 192.168.1.1 and 10.5.5.2?

Do I need to add anything on the Vlan Config ?
Do I need to take out ip address 192.168.1.221?

I have look at the web console on 192.168.1.221 in ip configuration I have

Vlan 1 is set to manual 192.168.1.221
Vlan 100 is set to manual 10.5.5.11

Should that be dchp/boot