HP 7506 problem with static route

[ZewaZebra1]

Ok, so here is a full documentation of what I did in the past 3 days:

I use a HP7506 Switch and created two additional Vlans on him. Right now there are 3 Vlans on the Switch

Vlan1 = The Default VLAN, connected to the router, gets its IPs from the routers DHCP service. 

Interface: 192.168.1.254

Router Adress: 192.168.1.1

Vlan10 = Custom Vlan, I created an DHCP extended Pool for this one.

Interface: 192.168.2.254 /24

Vlan20 = Same as 10

Interface: 192.168.3.254

The goal is to have each Vlan get its IP adresses from a DHCP Service, be it on the router or on the switch. And every Vlan should be able to connect to the internet via the Default Vlan1.

So here are the routes of the router, the switch and the host:

Switch Routing Table:

Destination IP 	Mask		Protocol	Preference	Next Hop	Interface
0.0.0.0		0.0.0.0		Static		60		192.168.1.1	Vlan-interface1
127.0.0.0	255.0.0.0	Direct		0		127.0.0.1	InLoopBack0
127.0.0.1	255.255.255.255	Direct		0		127.0.0.1	InLoopBack0
192.168.1.0	255.255.255.0	Direct		0		192.168.1.254	Vlan-interface1
192.168.1.254	255.255.255.255	Direct		0		127.0.0.1	InLoopBack0
192.168.2.0	255.255.255.0	Direct		0		192.168.2.254	Vlan-interface10
192.168.2.254	255.255.255.255	Direct		0		127.0.0.1	InLoopBack0
192.168.3.0	255.255.255.0	Direct		0		192.168.3.254	Vlan-interface20
192.168.3.254	255.255.255.255	Direct		0		127.0.0.1	InLoopBack0

Host route:

Ethernet-Adapter Ethernet:

   Verbindungsspezifisches DNS-Suffix:
   Verbindungslokale IPv6-Adresse  . : fe80::d51a:a99f:3ce1:1768%4
   IPv4-Adresse  . . . . . . . . . . : 192.168.2.1
   Subnetzmaske  . . . . . . . . . . : 255.255.255.0
   Standardgateway . . . . . . . . . : 192.168.2.254

Tunneladapter Teredo Tunneling Pseudo-Interface:

   Medienstatus. . . . . . . . . . . : Medium getrennt
   Verbindungsspezifisches DNS-Suffix:

Tunneladapter isatap.{DA1E13BE-4E6F-4AD1-9E5B-4884638598A8}:

   Verbindungsspezifisches DNS-Suffix:
   Verbindungslokale IPv6-Adresse  . : fe80::5efe:192.168.2.1%21
   Standardgateway . . . . . . . . . :

C:\Users\tobias_gross>route print
===========================================================================
Schnittstellenliste
  4...14 fe b5 bb 51 d5 ......Controller der Familie Realtek PCIe GBE
  1...........................Software Loopback Interface 1
  7...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface
 21...00 00 00 00 00 00 00 e0 Microsoft-ISATAP-Adapter #3
===========================================================================

IPv4-Routentabelle
===========================================================================
Active routes:

Auf Verbindung = on connection

  Destination       Networkmask        Gateway          Next hop (Schnittstelle)   Metrik
  0.0.0.0                0.0.0.0      192.168.2.254       192.168.2.1                10
  127.0.0.0            255.0.0.0      Auf Verbindung      127.0.0.1                  306
  127.0.0.1            255.255.255.255   Auf Verbindung   127.0.0.1                  306
  127.255.255.255  255.255.255.255   Auf Verbindung       127.0.0.1                  306
  192.168.2.0        255.255.255.0        Auf Verbindung  192.168.2.1                266
  192.168.2.1        255.255.255.255   Auf Verbindung     192.168.2.1                266
  192.168.2.255    255.255.255.255   Auf Verbindung       192.168.2.1                266
  224.0.0.0            240.0.0.0      Auf Verbindung      127.0.0.1                  306
  224.0.0.0            240.0.0.0      Auf Verbindung      192.168.2.1                266
  255.255.255.255  255.255.255.255   Auf Verbindung       127.0.0.1                  306
  255.255.255.255  255.255.255.255   Auf Verbindung       192.168.2.1                266
===========================================================================
Ständige Routen:
  Netzwerkadresse          Netzmaske  Gatewayadresse  Metrik
          0.0.0.0          0.0.0.0      192.168.1.1  Standard
===========================================================================

and the router routing table:

Destination LAN NET Subnet Mask	        Gateway	             Interface
212.88.142.192	255.255.255.224	         0.0.0.0	      WAN
192.168.3.0	255.255.255.0	         0.0.0.0	      LAN & WLAN
192.168.3.0	255.255.255.0	         0.0.0.0	      vlan0
192.168.2.0	255.255.255.0	         0.0.0.0	      LAN & WLAN
192.168.2.0	255.255.255.0	         0.0.0.0	      vlan0
192.168.1.0	255.255.255.0	         0.0.0.0	      LAN & WLAN
169.254.0.0	255.255.0.0	         0.0.0.0	      LAN & WLAN
0.0.0.0	        0.0.0.0	                 212.88.142.193	      WAN

[Vince-Whirlwind]

192.168.3.0	255.255.255.0	         0.0.0.0	      LAN & WLAN
192.168.3.0	255.255.255.0	         0.0.0.0	      vlan0
192.168.2.0	255.255.255.0	         0.0.0.0	      LAN & WLAN
192.168.2.0	255.255.255.0	         0.0.0.0	      vlan0
 

You need a route on the router for each of these subnets, pointing at 192.168.1.254, which is the router's only path to the switch.

Have you configured 192.168.2.0 & 192.168.3.0 IP addresses on router interfaces? 

[ZewaZebra1]

Now it finally works :)

thank you very much.

The next problem we have is that we have another HP switch connected to the HP7506 via Optical Fiber. We want that the new small switch gets the same Vlans, DHCP configurations and so on. How can we do this? Does these switches have some sort of synchronization or do we have to configure it manually?

[Vince-Whirlwind]

Manually.

On the new switch, create the VLAN. Tag it on the uplink back to the 7506.

tag/untag it on the rest of the ports as necessary.

On the 7506, tag the VLAN on the interface the new switch is patched to.

I think dynamic VLAN assignment might make a comeback with SDN and the rise of the GUI-driven network, but on the whole it's a pretty bad idea.