Device stops working when moving from one switch to another, until both HP switches are rebooted.

[Chicagojsh]

This has be stumped.  I've reduced my confugration to the most basic possible config and the problem persists.

I have the following

Barracuda Firewall --Uplink--> HP-2915-8G-PoE(layer 3)  -Uplink-> HP-2530-48G-PoEP

Vlan 1 and 100(voice) configured on both swtiches.  The 2915 is acting as the layer 3 router for the vlans.

I can connect a Shoretel 400 series IP phone to either switch and it boots perfectly using LLDP for vlan assignment(I've also tested scenario using just vlan tagging).

If I take a phone that originally booted on the 2915, unplug it, connect it to the 2530 it will then boot, but fail to be able to access anything on the network, I can no longer ping it and it can no longer ping the rest of the world.

If I take that same phone and connect it back to the 2915, when it boots up it comes up perfectly and connects and pings everything.

I get the same behavior if I initially connect a phone to the 2530 then move it to the 2915.

I've tried factory resetting the phone post move to clear out anything wierd and it doesn't change, it continues to not work once moved from one HP switch to the other. 

If I reboot the HP swtiches, then the phones that were not working, begin to work, and then if I swap switches again, they stop responding on the network.

I'm totally stumped and baffled.

Here are the configs, please tell me what I've missed.  Again these configs have been stripped down to the bare minimum.  I was using LACP trunk originally, now I"m just using one uplink

Layer 3)

; J9562A Configuration Editor; Created on release #A.15.16.0006
; Ver #06:04.9c.63.ff.37.27:12
hostname "HP-2915-8G-PoE"
qos dscp-map 101110 priority 6
timesync sntp
sntp unicast
sntp server priority 1 192.168.1.9
time daylight-time-rule continental-us-and-canada
time timezone -360
ip route 0.0.0.0 0.0.0.0 192.168.1.1
ip routing
snmp-server community "public" unrestricted
vlan 1
   name "DEFAULT_VLAN"
   untagged 1-10
   ip address 192.168.1.250 255.255.255.0
   exit
vlan 100
   name "Shoretel"
   tagged 3-4,6-10

   ip address 192.168.100.250 255.255.255.0
   ip helper-address 192.168.1.10
   qos dscp ef
   voice
   exit

Running configuration:
; J9772A Configuration Editor; Created on release #YA.15.16.0006
; Ver #06:04.9c.63.ff.37.27:12
hostname "HP-2530-48G-PoEP"
timesync sntp
sntp unicast
sntp server priority 1 192.168.1.9
time daylight-time-rule continental-us-and-canada
time timezone -360
ip default-gateway 192.168.1.1
snmp-server community "public" unrestricted
vlan 1
   name "DEFAULT_VLAN"
   untagged 1-52
   ip address 192.168.1.251 255.255.255.0
   exit
vlan 100
   name "Shoretel"
   tagged 1-52
   ip address 192.168.100.251 255.255.255.0
   ip helper-address 192.168.1.9
  qos dscp ef
   voice
   exit

[Vince-Whirlwind]

I don't think these will be interesting, but can you show us:

--> Which switchports are the "uplink" ports on both switches?

--> IP config of the device when it is working, plus a show-mac-address table from the 2915 filtered to that device's MAC

--> IP config of the device when you have moved it and it is no longer working, plus as above but from the 2530 AND the 2915, plus a show ARP filtered to that device's IP address from the 2915

Just looking at your configs there are two things I would do differently:

1. Your Layer2-only 2530 switch has an IP address on VLAN100. You should get rid of this.

2. You have two Access subnets with inter-VLAN routing occurring on the 2915. I can't see a 3rd subnet, and this tells me that you have bridged your VLAN1 subnet (I'm guessing on switchport5) across the Layer3 switch and onto the router, which means you have 2 Layer3 devices on the same subnet. A device sending traffic to an external destination will (probably) receive a "redirect" from the core switch and start using .1 as its gateway. (If the 2915 doesn't do redirects, you will actually get asymmetric routing for external destinations, as the router will communicate directly with the host, whereas the host will not talk directly to the router.)
Best to avoid this by implementing a Layer3 segment dedicated to your Layer3 switch <---->< Router link. (The router will need routes added to it telling it to find the internal subnets via the Layer3 switch).