On Sun, Jun 19, 2011 at 13:10, <[email protected]> wrote: > I am trying to get a vlan working between a Procurve 2810 and my Cisco core > switch (4510). > > On the Cisco side: > > Show ip route: > > Gateway of last resort is 192.168.100.9 to network 0.0.0.0 > > C 172.30.0.0/16 is directly connected, Vlan15 > S* 0.0.0.0/0 [1/0] via 192.168.100.9 > C 192.168.0.0/16 is directly connected, Vlan1 > > Show int vlan15: > > Vlan15 is up, line protocol is up > Hardware is Ethernet SVI, address is c47d.4fe6.e97f (bia c47d.4fe6.e97f) > Internet address is 172.30.1.1/16 > > > On the Procurve side: > > Procurve gateway is IP of my core switch. > I have Vlan15 with ip of 172.30.1.1. > > Port 5 is Tagged and member of Vlan15. > > Assume device in port 5 is a laptop with IP of 172.30.1.10. > > From the laptop I can ping the Procurve switch but anything on the 4510 side > (native vlan) > The Procurve can ping the laptop and also ping core switch and anything on > native vlan. > > The 4510 ping to the laptop fails. > > If this was just Cisco, I would guess it to be a trunking problem but I > understand Procurve trunking is like Cisco's etherchannel. > > However, it seems to be a routing issue but I'm at a loss where to go from > here. > Any help would be greatly appreciated!
Do all VLANs match for IP subnet across the two switches? Is the same VLAN configured on the Cisco and HP as primary/native? Is the management VLAN the same on both, and have the same subnet and DG? When you say for the HP that "Port 5 is Tagged and member of Vlan15", what exactly does 'sho conf' reveal for that VLAN? Ditto on the Cisco. Kurt ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin
