HP Procurve 1920 Trunk configuration with UBNT EdgeMax Lite

[abdomi]

Hi,

Last Friday, I bought a new HP Procurve 1920 24-port layer 3 switch for my large home network with multiple subnets for replacing my old Dell PowerConnect 2716 and connected to my Edgemax Lite router (eth2) but experiencing some issues with Trunk configuration between my UBNT EdgeMax and Procurve.

I already have another HP Procurve 1810 Layer 2 switch that I configured one of the ports as a trunk to my Edgemax router (eth1) and it works perfectly fine with my VLANs.

When it comes to configuration for eth1 and eth2 in my EdgeMax Lite, they are configured identically with obviously different subnets.

Interface    IP Address                        S/L  Description
---------    ----------                        ---  -----------
eth0         X.X.X.X/24                        u/u  Internet
eth1         -                                 u/u  DMZ
eth1.200     192.168.255.1/24                  u/u  DMZ Private IP
eth1.250     X.X.X.X/29                        u/u  DMZ Public IP
eth2         192.168.0.1/24                    u/u  Internal
             192.168.1.1/24
             192.168.254.1/27
eth2.300     192.168.254.33/28                 u/u  VMHost Network
lo           127.0.0.1/8                       u/u
             ::1/128

Side note, I'll transition 192.168.1.1/24 (VLAN 100) and 192.168.254.1/27 (VLAN 400) later to individual VLANs later since I want to make the Trunk work first between HP Procurve 1920 and my EdgeMax router. Also 192.168.0.0/24 will remain as default untagged network for my regular clients.

 In my Procurve 1920, I configured GE1/0/1 as a trunk:

PVID = 1

Untagged Membership = 1

Tagged Membership = 300

Other ports that are only tagged as VLAN 300 are GE1/0/3, 4, 5 and 6. The servers behind these ports are able to communicate with each other (already set VLAN tagging inside of the NIC) but nor Servers within this subnet can ping my EdgeMax or the EdgeMax can ping the servers.

Am I missing something in here?

Many thanks in advance!

[16again]

First take a look at the switch MAC address table, select addresses in  VLAN300. and review originating ports.

[abdomi]

Thanks for your reply 16again.

The switch shows correct MAC adresses for VLAN300, please refer to the screenshot.

As part of diagnostics, I've assigned an IP address to the switch within the same subnet and in VLAN300. The servers in VLAN300 are able to open Web Management interface and can ping the switch. 

When I tried to ping the router from the switch and the servers, got no response from the router but interestingly though, once I ping the router (the ip on eth2.300 interface), the RX Rate graph in the router's management interface indicating that the packets are coming and feels like somehow dropped. And the firewall is currently not active.  

[abdomi]

I just took a tcp dump in the router and as far as I can see, once I try to ping the router from one of the servers, I see ARP requests but no responses are sent back.

---

Ping from switch to router:

  PING 192.168.254.33: 56  data bytes
    Request time out
    Request time out
    Request time out
    Request time out
    Request time out

  --- 192.168.254.33 ping statistics ---
    5 packet(s) transmitted
    0 packet(s) received
    100.00% packet loss

---

TCP Dump from my router:

XXXX@XXXX:~$ sudo tcpdump -i eth2.300 -c 100
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth2.300, link-type EN10MB (Ethernet), capture size 262144 bytes
23:00:22.646772 IP 192.168.254.33.47428 > 255.255.255.255.10001: UDP, length 4
23:00:22.662774 IP 192.168.254.33.57898 > 255.255.255.255.47428: UDP, length 175
23:00:52.536864 ARP, Request who-has 192.168.254.33 tell 192.168.254.34, length 42
23:00:53.660154 IP 192.168.254.33.38873 > 255.255.255.255.10001: UDP, length 4
23:00:53.669316 IP 192.168.254.33.54465 > 255.255.255.255.38873: UDP, length 175
23:00:54.780621 ARP, Request who-has 192.168.254.33 tell 192.168.254.34, length 42
23:00:56.982239 ARP, Request who-has 192.168.254.33 tell 192.168.254.34, length 42
23:00:59.192240 ARP, Request who-has 192.168.254.33 tell 192.168.254.34, length 42
23:01:01.402253 ARP, Request who-has 192.168.254.33 tell 192.168.254.34, length 42
^C

[abdomi · Accepted solution]

Now it's solved after removing VLAN300 on eth2 in my UBNT EdgeMax Lite router, rebooting it and then adding back the VLAN.

Magic...