HP 5304Xl inter-vlans routing issue

[Mohieddin Kharnoub]

what i have done with you, is a scenario i done so many times without no issues ,

anyway, your network map that you attached before is not clear since no link between the main 2 switches, and its a simple , so hard to figure out what kind of setup you did.

good luck :)

[Matt Hobbs]

The reason that you can't ping VLAN 1 from other VLANs is because you have this line configured in your running-config:

management-vlan 1

When you set a management VLAN it disables routing functionality for that VLAN.

[Marius_rg]

Hello guys,

the problem was from arp, I think.

This morning I didn't do anything except for "show arp", and than boom, it works.
Still it's strange because I've runed this command before, but...now suddenly it worked.
Now I can really start to arrange vlans and to make shure that the VLAN_IT can manage the switches.

[Mohieddin Kharnoub · Accepted solution]

Congrats.

Assigning points is your thanks :)

[Marius_rg]

It seems that I still have problems.
It's from arp allright, but I don't understand whats happening.
In the same situation, with 2 clients with static ip's, ping fron one to each other doesn't work, and, after I run clear arp, it works.
After a while...the same problem appears.

What could be the issue?

[Matt Hobbs]

Can you attach a copy of:

1. Your current running-config from all procurve switches.
2. Detailed network map showing what ports are connected to what
3. ipconfig /all output of the clients you are testing with.

[Marius_rg]

Ok, I've attached a text file.

[Antonio Milanese]

Hello,

>vlan 1
> name "DEFAULT_VLAN"
> untagged A1-A24,B1-B11,B13-B17,B19-B23,C1-C4,D1-D4
> ip address 10.20.10.3 255.255.255.0
> ...
>vlan 20
> name "VLAN_VideoCA"
> untagged B18,B24
> ip address 10.20.10.33 255.255.255.240
>vlan 30
> name "VLAN_EXTRA"
> untagged B12
> ip address 10.20.10.49 255.255.255.240

maybe your problem is the subnetting:
the native VLAN has a wider netmask even if you have assigned the correct
addressing on the vlan interfaces i'll avoid this kind of "overlapping"
expecially if the assigned tagged ports are members of multiple vlans.

> vlan 20
> ip rip
> ip rip receive V1-only
> ip rip send V1-only
Rip v1 support only classfull netmask i.e. no VLSM is this your goal?
Maybe as suggested in a previuos replay you can skip RIP at all
and use only the static default gateway (ip route 0.0.0.0 0.0.0.0)
or turn on RIPv2.

Is this the "running-config" or the stored one? i'll double check that
proxy arp is not enabled anywhere in the network.

Can you post the "show ip route" and the arp entries on the PCs and
switches?

Best regards,

Antonio

p.s. as usual sorry for my broken english

[Mohieddin Kharnoub]

Hi

Antonio, since IP routing is enabled, then RIP is not used for InterValn Routing.

And i already told Marius than its not required unless he has his reasons for using RIP.

What Matt posted before, about Management Vlan is True because it disables routing to this VLAN 1, and it will not be included in the Routing Table.

For Professional Scenario:

1- Change your default Vlan to Someother Vlan (maybe Vlan2006) , and accordingly Change any native Vlan for any cisco devices to this vlan2006 , so your management Vlan is 2006 now.

2- Do whatever you want with Vlan1, if you want to still use it before you shift tio the System.

3- Be sure to check tagging and untagging for Vlan1 after you shift to new System.

4- Your configuration will be after i checked the 1st configuration you posted:
----------------------------------------------
ip default-gateway 10.20.10.1
sntp server 10.20.10.1
ip routing
timesync sntp
time timezone 120
time daylight-time-rule Middle-Europe-and-Portugal
sntp unicast
logging 10.20.10.34
snmp-server community "public" Unrestricted
snmp-server host 10.20.10.143 "public"
snmp-server host 10.20.10.36 "public"
vlan 1
name "VLAN_1"
untagged A1-A24,B1-B11,B13-B17,B19-B24,C1-C4,D1-D4
ip address 10.20.10.3 255.255.255.0
ip helper-address 10.20.10.246
no untagged B12,B18
exit
vlan 20
name "VLAN_VideoCA"
untagged B18
ip address 10.20.10.33 255.255.255.240
tagged C3
exit
vlan 30
name "VLAN_BONUS"
untagged B12
ip address 10.20.10.49 255.255.255.240
ip helper-address 10.20.10.34
tagged C3
exit
vlan 40
name "VLAN_QA"
ip address 10.20.10.65 255.255.255.192
ip helper-address 10.20.10.34
tagged C3
exit
vlan 60
name "VLAN_ProdOEM"
ip helper-address 10.20.10.34
exit
vlan 70
name "VLAN_HR_ACC"
no ip address
ip helper-address 10.20.10.34
exit
vlan 80
name "VLAN_SERVERS"
no ip address
ip helper-address 10.20.10.34
exit
vlan 2006
name "VLAN_Mngmt"
ip address a.b.c.d
ip helper-address 10.20.10.34
exit
fault-finder bad-driver sensitivity high
fault-finder bad-transceiver sensitivity high
fault-finder bad-cable sensitivity high
fault-finder too-long-cable sensitivity high
fault-finder over-bandwidth sensitivity high
fault-finder broadcast-storm sensitivity high
fault-finder loss-of-link sensitivity high
fault-finder duplex-mismatch-HDx sensitivity high
fault-finder duplex-mismatch-FDx sensitivity high
ip route 0.0.0.0 0.0.0.0 10.20.10.1
management-vlan 2006
password manager
----------------------------------------------

Now please check the configuration according to your requirements, some vlans in your first post removed from the last one, and check the Vlan1 tagginf and untagging.

If you want to keep Vlan1 as your default Vlan without changing to Vlan 2006, then remove the management-vlan command line from your configuration.

Good Luck !!!

[Matt Hobbs]

I think the reason you have to keep on doing a 'clear arp' is because you have an IP address conflict, both the 5300 and 2500 are using 10.20.10.33 on VLAN 20. You should remove this from the 2500.

I also agree with Antonio regading VLAN1, you should change it's subnet to not overlap. Change it to 255.255.255.240 or something else that fits in with your addressing scheme.

If you are planning for VLAN1 to also participate in routing, you will need to set 'no management-vlan 1'.