HPE Aruba Networking & ProVision-based
1833355 Members
3165 Online
110051 Solutions
New Discussion

HP Procurve 2910al VLAN - can ping the other VLAN

 
MackyBalba
Occasional Contributor

HP Procurve 2910al VLAN - can ping the other VLAN

Hi,

 

I am certainly new to networking and I honestly do not know many things about VLAN. I have Procurve 2910al that act as my core switch and I have V1910. I am trying to setup 2 VLANS (1 for LAN and 1 for Wireless). 

 

hostname "MCN_CORE"
time timezone 480
module 1 type J9145A
ip routing
vlan 1
name "DEFAULT_VLAN"
untagged 1-24
ip address 10.1.0.1 255.255.252.0
exit
vlan 172
name "VLAN172"
ip address 172.100.1.1 255.255.254.0
tagged 19
exit
snmp-server community "public" unrestricted
no autorun
password manager

 

10.x.x.x ip cannot ping any hosts from 172.x.x.x range except 172.100.1.1.

 

My question is, is it normal that I can ping 172.100.1.1 even if my ip address is 10.x.x.x? When I am at 172.x.x.x ip, I cannot ping the 10.x.x.x. 

 

Is there a way that IP 10.x.x.x will not be able to ping 172.x.x.x?

 

Thank you in advance

 

 

3 REPLIES 3
Chrisd131313
Trusted Contributor

Re: HP Procurve 2910al VLAN - can ping the other VLAN

Hi MackyBalba,

 

To understand you config, I see that VLAN 172 is tagged on port 19, I assume that this is your uplink to the V1910 switch? Are you able to supply the config of that switch?

 

Also are you able to confirm that the Default Gateway on the 172 devices is set to 172.100.1.1 and the subnet is the same as stipulated on the switch?

 

 

-----------------------------------------------------

Don't forget to mark a post resolved if your question was answered.
MackyBalba
Occasional Contributor

Re: HP Procurve 2910al VLAN - can ping the other VLAN

Chrisd131313
Trusted Contributor

Re: HP Procurve 2910al VLAN - can ping the other VLAN

Hi,

 

If you are saying that you don't wanty the VLANs to be able to access each other then just setup a vlan ACL to deny access from one VLAN to the other, if you have to have routing enabled on the switch. You will always get a rsponse from the other VLANs DG because the switch sees it as a directly connected subnet, so the only way for this not to respond to pings is to setup a ACL to deny the traffic.

 

But from what you are saying it seems like you have managed to achieve what you were looking to do, so it's all good :)

-----------------------------------------------------

Don't forget to mark a post resolved if your question was answered.