Cannot ping 3850 from 4500X core

[roger perkin]

I have a very strange but simple problem. 

I have a 4500X core with a 3850 stack connected. 

int vlan is configured on the core with 192.168.1.1 

int vlan is configured on the 3850 stack with 192.168.1.12 (Management Address) 

Vlans are both active on both switches

Spanning tree is forwarding for the vlan 

however I cannot ping the switch or manage it form the core?

I am running 03.06.01E 

Gateway of last resort is 192.168.1.1 to network 0.0.0.0

S*    0.0.0.0/0 [0/0] via 192.168.1.1
      192.168.1.0/24 is variably subnetted, 2 subnets, 2 masks

I cannot ping the Core from the switch or the switch from the core If I connect a PC into the VLAN I cannot ping the switch,

This has to be a config on the switch that I am missing. 

IP routing is off - (have tried it on)

Trunks are forwarding the vlan 

anyone any ideas I am scratching my head

[Madhukrishnan Gopinathan Nair]

Please share the configs for the vlan interfaces, associated trunks on both switches.

also below from both.

sh int <vlan> 

sh int <> trunk

sh vlan id 

Thanks,

M

[roger perkin]

The config has not changed and problem has resolved with IOS upgrade 

Core:

interface Vlan64
 description MANAGEMENT
 ip address 192.168.1.1 255.255.255.

Switch:

interface Vlan64
 ip address 192.168.1.16 255.255.255.0
 no ip route-cache

The vlan is allowed on the trunk. 

Pings are now working with 3.0.7E 

[roger perkin]

Turns out it was actually the reload that fixed the problem not the upgrade. 

I reloaded another stack and was able to ping successfully.

Problem solved

[Madhukrishnan Gopinathan Nair]

Yes thats whay my impression about this initially too.

[roger perkin]

UPDATE:

I have now upgraded the stack to 03.07.00E  and pings work as expected. 

Is this a bug?

If it is I have a lot of switches to upgrade!

[Madhukrishnan Gopinathan Nair]

Hi Roger,

I could not find a matching bug, and i believe it could have been resolved with a reload.

Could have been due some stuck process/interface/software etc would have caused it.

Could you please check if you see similar issue on another box too?

Thanks,

Madhu