Unable to connect to new VLAN IP Address

[JF7]

I have an HP E3500yl-24G that I have configured with VLAN 100 and an IP Address.

The steps I have completed are below:

• Configured like the other Procurve switches with a VLAN 100 for management access.
• I am trunking the receving port on the uplevel switch with VLAN 100 tagged.
• I have set the uplink port to tag VLAN 100 on this switch.
• I can ping the uplevel switch's VLAN 100 IP from my computer.
• I cannot ping the switch's VLAN 100 IP.
• I cannot ping from either switch's console to the other switch's VLAN IP.
• I connected a computer to a port that was set as untagged VLAN 100 with an IP Address in the switch's subnet and I could not ping it. I had to add an route, as below, to get a response to the computer with a ping.

  ip route 0.0.0.0 0.0.0.0 10.1.1.1

I have done multiple google searches and cannot find why I cannot get VLAN 100 to work.

I am adding the configuraton below, with IPs obfuscated, for review.

HP-E3500yl-24G(config)# sh run

Running configuration:

; J8692A Configuration Editor; Created on release #K.16.02.0021
; Ver #10:08.03.81.30.02.34.59.2c.6b.ff.f7.fc.7f.ff.3f.ef:26
hostname "HP-E3500yl-24G"
module 1 type j86xxa
trunk 24 trk10 trunk
port-security 12 learn-mode port-access
radius-server host 10.1.1.22 key "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
timesync sntp
sntp unicast
no telnet-server
time daylight-time-rule continental-us-and-canada
time timezone -300
ip authorized-managers 10.1.1.55 255.255.255.255 access manager
ip authorized-managers 10.1.1.56 255.255.255.255 access manager
ip authorized-managers 10.1.1.57 255.255.255.255 access manager
ip authorized-managers 10.1.1.58 255.255.255.255 access manager
ip authorized-managers 10.1.1.59 255.255.255.255 access manager
ip default-gateway 10.1.1.1
ip route 0.0.0.0 0.0.0.0 10.1.1.1
snmp-server community "public"
snmp-server community "private" unrestricted
snmp-server community "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" operator
snmp-server community "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" unrestricted
snmp-server host 10.1.1.98 community "public"
snmp-server host 10.1.1.99 community "public"
snmp-server contact "IT" location "IDF1"
aaa authentication port-access eap-radius
aaa port-access authenticator 12
aaa port-access authenticator 12 logoff-period 60
aaa port-access authenticator 12 client-limit 1
aaa port-access authenticator active
vlan 1
   name "DEFAULT_VLAN"
   no untagged 23
   untagged 1-22,Trk10
   no ip address
   exit
vlan 100
   name "Server VLAN"
   untagged 23
   tagged Trk10
   ip address 10.1.1.30 255.255.255.0
   exit
spanning-tree
spanning-tree Trk10 priority 4
no autorun
no dhcp config-file-update
no dhcp image-file-update
device-profile name "default-ap-profile"
   cos 0
   exit
password manager
password operator

It woudl be greatly appreciated if I could get some help as why this is happening because this software version isn't far behind and this issue may arise again for me as we replace older switches.

EDIT: Updated to add Private IPs rather than obfuscated Public IPs.

[parnassus]

Sanitizing private IP addresses doesn't really help reading what you could have done incorrectly (better if you hide other parametrs not useful to troubleshoot your issue)...who is responsible for routing? why you have an aggrgated (non protocol) trunk made of just one port (24)? can you share the outputs of show ip, show ip route and show vlan commands executed on both switches?

[JF7]

They are not Private IP Addresses thus the reason they are sanitized.

I can put in private IP Addresses that mimic my environment, but it can be discerned from my post.

Also, I have this exact same VLAN working on about 30 switches between Procurve and Comware OS versions. They are all in the same subnet and they can ping each other from inside the VLAN.

I am the one working on the routing, which isn't needed in the very simple environment I have. I only have them going up to a default gateway.

[JF7]

In Reponse to the need for the commands show ip, show ip route, and show vlan below are the output of those commands.

Problematic downlevel switch

HP-E3500yl-24G# sh ip

 Internet (IP) Service

  IP Routing : Disabled

  Default Gateway : 10.1.1.1
  Default TTL     : 64
  Arp Age         : 20
  Domain Suffix   :
  DNS server      :

                       |                                            Proxy ARP
  VLAN                 | IP Config  IP Address      Subnet Mask     Std  Local
  -------------------- + ---------- --------------- --------------- ----------
  DEFAULT_VLAN         | Disabled
  Server VLAN          | Manual     10.1.1.30       255.255.255.0    No    No

HP-E3500yl-24G# show ip route

                                IP Route Entries

  Destination        Gateway         VLAN Type      Sub-Type   Metric     Dist.
  ------------------ --------------- ---- --------- ---------- ---------- -----
  127.0.0.0/8        reject               static               0          0
  127.0.0.1/32       lo0                  connected            1          0

HP-E3500yl-24G# show vlan

 Status and Counters - VLAN Information

  Maximum VLANs to support : 256
  Primary VLAN : DEFAULT_VLAN
  Management VLAN :

  VLAN ID Name                             | Status     Voice Jumbo
  ------- -------------------------------- + ---------- ----- -----
  1       DEFAULT_VLAN                     | Port-based No    No
  100     Server VLAN                      | Port-based No    No

Uplevel working switch

ProCurve Switch 2848(config)# show ip

 Internet (IP) Service

  IP Routing : Disabled

  Default Gateway : 10.1.1.1
  Default TTL     : 64
  Arp Age         : 20

  VLAN         | IP Config  IP Address      Subnet Mask
  ------------ + ---------- --------------- ---------------
  DEFAULT_VLAN | Disabled
  Server VLAN  | Manual     10.1.1.31   255.255.255.0

ProCurve Switch 2848(config)# show ip route

                                IP Route Entries

  Destination        Gateway         VLAN Type      Sub-Type   Metric     Dist.
  ------------------ --------------- ---- --------- ---------- ---------- -----
  0.0.0.0/0          10.1.1.1        100  static               250        1
  127.0.0.0/8        reject               static               0          250
  127.0.0.1/32       lo0                  connected            0          0
  10.1.1.0/24        Server VLAN     100  connected            0          0


ProCurve Switch 2848(config)# sh vlan

 Status and Counters - VLAN Information

  Maximum VLANs to support : 8
  Primary VLAN : DEFAULT_VLAN
  Management VLAN :

  802.1Q VLAN ID Name         Status       Voice Jumbo
  -------------- ------------ ------------ ----- -----
  1              DEFAULT_VLAN Port-based   No    No
  100            Server VLAN  Port-based   No    No

I can see right away the routes are missing in the downlevel switch that isn't working. I have set an ip route to 10.1.1.1 for all traffic, but it isn't in the routes.

[parnassus · Accepted solution]

---

@JF7 wrote: I have set an ip route to 10.1.1.1 for all traffic, but it isn't in the routes.

---

It isn't the only thing that doesn't appear on the routes...the show ip route command doesn't list the directly connected route to 10.1.1.0/24 Subnet (to which the Servers's VLAN SVI belongs) as instead happens on the other switch; have you tried to re-create (remove and add) the VLAN 100 (10.1.1.30) on the  problematic downlevel switch? Which software version is the HP ProCurve E3500yl-24G Switch running on (just curious)?

[JF7]

@parnassus wrote: have you tried to re-create (remove and add) the VLAN 100 (10.1.1.30) on the  problematic downlevel switch?

I have tried to recreate a few times, this was after completely removing the VLAN and only having VLAN 1. I can try again to doublecheck I didn't do anything wrong in the process.

@parnassus wrote: Which software version is the HP ProCurve E3500yl-24G Switch running on (just curious)?

K.16.02.0021

[JF7]

@parnassus wrote: have you tried to re-create (remove and add) the VLAN 100 (10.1.1.30) on the  problematic downlevel switch?

So somehow this time it worked.

The steps I completed are:

1. Removed VLAN 100 with, no vlan 100.
2. Removed Spanning Tree with, no spanning-tree.
3. Enabled gvrp (I have been setting this up on the other switches).
4. Saved with, wr mem.
5. Exited configuration terminal.
6. Went back into configuation terminal.
7. Created VLAN 100.
   1. Tagged port 24.
   2. Set IP Address of 10.1.1.30
8. Could not ping 10.1.1.30.
9. Removed tagged port 24 from VLAN 100.
10. Checked to see if gvrp was working.
11. Ping was still running and after checking it was now responding.
12. The sh ip route command showed the correct routes.
13. Set port 24 to tagged on VLAN 100.
14. Ping was still responding and the routes were still correct.
15. Set VLAN name back to "Server VLAN".
16. Again ping was responding and routes were still correct.

Weird thing was that it was responding before tagging port 24, probably due to gvrp, but it is now working. I do not know how or why, as I had recreated once before.