HP 7506 problem with static route

[ZewaZebra]

Dear Sir or Madam

 ,

I have the following problem: the swtich currrently has 2 Vlans, the default vlan (1) and Vlan 7 (dhcp test)created by me. On this Vlan 7 I created a extended pool for the dhcp function, which now works fine. 

Vlan 1: port 3/01 - 5/048

Vlan 7: port 5/0/1 - 5/0/16

here the dhcp pool settings:

network 192.168.2.0 mask 255.255.255.0

gateway-list 192.168.2.254

 dns-list 212.xx.xxx.xx 217.xx.xx.xxx

domain-name test

expired 1 0 0 0

____

Now I want to have access to the internet as soon as I connect the pc to the vlan (with Lan cable). The router ip is 192.168.1.1. (the router is plugged into 3/0/1) .Therefore I created a static route with these details:

Destination ip: 192.168.1.1

mask 255.255.255.0

next hop: 192.168.2.254

Unfortunately I can't access the internet. I hope somebody can help me. I think you already found out im relative new on this switch stuff and sorry for any grammatically faults (greets from germany )

Mit freundlichen Grüßen

ZewaZebra

[EricAtHP]

Your route only points to the 192.168.1.0 subnet and is not a default route. You need a default route: 0.0.0.0 0.0.0.0 192.168.1.1 on the switch. But then you need a static route on the router (192.168.1.1) pointing back to subnet 2: 192.168.2.0 255.255.255.0 192.168.1.X where X is the IP address of the switch in VLAN 1.

This will work assuming that the router (192.168.1.1) is doing NAT to the Inernet. Otherwise you have to add routes to upstream routers too.

Basically, for routing to work, the routing tables have to be correct every where along the path both to the Intenet and back to your network.

[ZewaZebra1]

I did evrything as said above, but I still can't connect to the internet. With the ping command (cmd) I see a 75% packet loss. This evenving I will send some pictures with my current configuration.

PS: I had to change my display name, don't knwo why.

[ZewaZebra1]

Update here:

The routes on the switch look like this:

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.169.13.0      255.255.255.0         Direct 0                      192.169.13.254 Vlan-interface20

192.169.13.254 255.255.255.255   Direct 0                       127.0.0.1 InLoopBack0

The static route on my router looks like this:

Destination LAN NET 192.168.13.0

Subnet Mask: 255.255.255.0

Gateway 192.169.13.254

when I connect to my Vlan20 the Switch will give my pc a ip based on my dhcp configuration which is correct, it also gives him the correct dns and gateway adress, but I can´t get an internet connection. How can I fix that? Or what am I missing here?  

[Vince-Whirlwind]

The static route on my router looks like this:

Destination LAN NET 192.168.13.0

Subnet Mask: 255.255.255.0

Gateway 192.169.13.254

For gateway, is that a typo, do you have 192.168.1.254?

[Vince-Whirlwind]

Show us the config on your router interface that's patched to the switch.

[ZewaZebra1]

Okay, I will give some detailed information about my current setup, because I have changed many things yesterday. 

I have two Vlans installed on my HP Switch. The first is the default Vlan1. It is connected to an router and has access to the internet. The next Vlan is called Vlan 20. It gets its IP from an DHCP Server installed on the switch, which works fine. My Problem is, whenever I connect a PC to a Port assigned to Vlan 20 I can´t connect to the Internet. If I connect him to Vlan 1, everything works fine. 

The Port on Vlan 1 where the Router is connected to has this configuration:

Port: GE3/0/1

Untagged Membership: 1

Tagged Membership: 20

Link Type: Trunk

PVID: 1

The Routing Table on the Switch looks like this:

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.169.13.0       255.255.255.0                  Direct 0     192.169.13.254 Vlan-interface20

192.169.13.254 255.255.255.255             Direct 0      127.0.0.1 InLoopBack0

The Route on the Router right now looks like this:

Destination LAN NET: 192.169.13.0

Subnet Mask: 255.255.255.0

Gateway: 192.168.1.254

It is possible to Ping VLAN 1 if I´m connected to VLAN 2. It is not possible to Ping the Router (192.168.1.1) So what I´m guessing is that VLAN 2 needs some kind of acces to the Port G 3/0/1 is that correct? And if yes, how can I do that?

[Vince-Whirlwind]

VLAN 2 does not need access to the router - VLAN2 ends at the VLAN2 interface on your switch. 

Your switch then consults its routing table which will tell it to route the packet via VLAN1 to 192.168.1.1

That all looks good.

If you're getting no reply from the router you should look closer at the router configuration.
 

Does the router respond to a ping from a host in VLAN1?

[ZewaZebra1]

Yes when I am connected to Vlan 1 with a cable I can ping 192.168.1.1 (router) without a problem.

Can you tell me some Keywords which I can look up at the router configuration? In order to solve the problem.

Another question: Is it normal that Vlan 2 can Ping Vlan 1, but Vlan 1 cannot ping Vlan2? If Vlan1 tries to ping vlan2 I can see with tracert that he goes to the router and then off to the internet...

[EricAtHP]

the behavior you describe can probably be understood after we see the routing tables on your devices. On the router, you should be able to find the route table somewhere, probably in the web UI. On the 7500, do a "display ip routing-table". Can you also share the routing table off of the hosts you are using to test? On windows for example, go to a command prompt and enter "route print".

[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.