Switches, Hubs, and Modems
1753878 Members
7346 Online
108809 Solutions
New Discussion юеВ

Re: HP 5304Xl inter-vlans routing issue

 
SOLVED
Go to solution
Marius_rg
Advisor

HP 5304Xl inter-vlans routing issue

Hello,

I want to break my network into 8 vlans:
vlan10- 10.20.10.0/27
vlan20 -10,20,10,32/28
vlan30- 10,20,10,48/28
vlan40- 10,20,10,64/26
vlan50- 10,20,10,128/26
vlan60- 10,20,10,192/28
vlan70- 10,20,10,208/28
vlan80- 10,20,10,224/27

I have a layer 3 sw 5304XL and tree layer 2 sw 2524/2650.
On 5304xl I created those vlans. I will copy my running config to be more clear.
=======================
ip default-gateway 10.20.10.1
sntp server 10.20.10.1
ip routing
timesync sntp
sntp unicast
logging 10.20.10.34
snmp-server community "public" Unrestricted
vlan 1
name "DEFAULT_VLAN"
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
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 10.20.10.0 255.255.255.0 10.20.10.1
ip route 10.20.10.32 255.255.255.240 10.20.10.1
ip route 10.20.10.48 255.255.255.240 10.20.10.1
ip route 10.20.10.64 255.255.255.192 10.20.10.1
ip route 0.0.0.0 0.0.0.0 10.20.10.1
management-vlan 1
router rip
redistribute static
exit
vlan 20
ip rip
ip rip receive V1-only
ip rip send V1-only
exit
vlan 30
ip rip
ip rip receive V1-only
ip rip send V1-only
exit
vlan 40
ip rip
ip rip receive V1-only
ip rip send V1-only
exit
password manager
=================================

I have 2 client, one on vlan 20 and the other on vlan 30 with static ip.
Still they cannot se each other, but I can ping in 10.20.10.33/49/65....
What I'm missing in this picture ?

My goal is to have a DHCP servers with multiple scopes (one for each vlan), but until now I couldn't make anything becouse the clients cant see the server.

Can somebody help me in this problem.

Thanks.


30 REPLIES 30
Mohieddin Kharnoub
Honored Contributor

Re: HP 5304Xl inter-vlans routing issue

Hi

Except for vlan 20, all IP Helper-address in position and applied to guide vlan members to the DHCP server.

Now :

Create multiple Scopes on the DHCP server for each Vlan and its IP Address Range, now make the Router attribute for each Scope is its vlan IP address.

Example:

Vlan30 ip address is 10.20.10.49, so on the DHCP after you create the Scope for the 10.20.10.49 network, make thr router attribute is Vlan30 IP address (10.20.10.49).


One more thing:
On the default route which is 10.20.10.1, add a static route for every vlan and point it to the default-vlan ip address which is 10.20.10.3 ,

Example: add on your router these static routes:

IP route 10.20.10.33 255.255.255.240 10.20.10.3 ---- this is for vlan 20

IP route 10.20.10.49 255.255.255.240 10.20.10.3 ---- this is for vlan 30


and so on .....

so now you have 2 ways routing between the 5300 and the Main Router.

I hope this information are enough.

Don;t forget to assign points, this is our thanks :)

Good Luck !!!

Science for Everyone
Marius_rg
Advisor

Re: HP 5304Xl inter-vlans routing issue

When I try to add route it give me this error:

Switch1-4thFL-HP5304XL(config)# ip route 10.20.10.33 255.255.255.240 10.20.10.3

10.20.10.33/28: Inconsistent address and mask.

Indeed, on vlan 20 is not the helper address, I've must forgot'it when I reasign all ip's to vlans.

In DHCP I created scopes exactly how you said, but the problem is yet on the switch.

Thanks.
Mohieddin Kharnoub
Honored Contributor

Re: HP 5304Xl inter-vlans routing issue

Hi again,

You are trying to add a static route for your Vlans on the Switch and thats not correct so that you got the error message.

It should be on the router, and it seems you have RIP V1 enabled, but i have no idea if you enabled RIP v1 on your Router ? so that i told you to add a static routes on this router.

For the DHCP Scopes, please be specific when you create the scopes like the IP Address range , Mask , DNS , and the Router attribute which is the most important.

One more thing:
---------------

I have noticed that you have 2524/2650 switches in your network, please be sure to Tagg all the Vlans on each Port of these Switchs which connects them to the Core switch 5300 , otherwise it won;t get an IP Address from the DHCP because no Vlan traffci passed to the DHCP server throw switches Uplinks.
and i noticed that some vlans not tagged to some ports like C3, but no idea about the Edge switches.

Tagging should be on both sides and for all vlans.

Don;t forget points.

Good Luck !!!
Science for Everyone
Marius_rg
Advisor

Re: HP 5304Xl inter-vlans routing issue

I don't understand very well...
I don't have another router, the sw 5304XL is layer 3,so it has router functionality.

For DHCP scopes, i'll give u some examples:
Scope 20:
range:10.20.10.34/10.20.10.46
gw: 10.20.10.33
mask: 255.255.255.240
DNS:10.20.10.34

Scope30:
range: 10.20.10.50/10.20.10.62
gw: 10.20.10.49
mask: 255.255.255.240
dns: 10.20.10.34

Scope40:
range: 10.20.10.66/10.20.10.126
gw: 10.20.10.65
mask: 255.255.255.192
dns: 10.20.10.34

etc.

Yes, the link between switches is tagged, and the reason that not all vlans have C3 tagged is becouse I've made a test only on vlan20/30/40...to see if it works.
Mohieddin Kharnoub
Honored Contributor

Re: HP 5304Xl inter-vlans routing issue

First,

Scopes seem fine to me, and it should work, but it won't.

Second:

Your Main router is the one you included in the 5304 Core switch, just look to the configuration and you will see:
ip route 0.0.0.0 0.0.0.0 10.20.10.1

And this is your defaulr route, or your exit for internet.

Now routing between Vlans is enabled, and ip helper-address command excuted i neach Vlan, so if any Client sent a DHCP request, the Vlan will direct him to the DHCP Server,

And in the DHCP server you have configured DNS to point to your Main Router , the 10.20.10.1

BUT , still your clients in Vlan1 can get an IP from the DHCP because they are in the Same network of the Main Router.

Vlan1 IP is : 10.20.10.3
Router IP is: 10.20.10.1

Summary:
--------

Just look for the Router which connects you to the Internet, and there you should add the static Routes i told you about before , for each Vlan.

Note:
-----

Some Home users ADSL Modem/Routers doesn't support NAT for multiple subnets, so clients in Vlan1 can get internet but not clients on other Vlans.

Good Luck !!!
Science for Everyone
Marius_rg
Advisor

Re: HP 5304Xl inter-vlans routing issue

I think we've started on wrong foot.
My routes on the running-config
(ip route 10.20.10.0 255.255.255.0 10.20.10.1
ip route 10.20.10.32 255.255.255.240 10.20.10.1
ip route 10.20.10.48 255.255.255.240 10.20.10.1
ip route 10.20.10.64 255.255.255.192 10.20.10.1
ip route 0.0.0.0 0.0.0.0 10.20.10.1)
wore added a couple of days before, but they have no effect on our network enviroment.Now they are removed and everyting is Ok, except my test vlans.
Second, the 10.20.10.1 is a linux server, our gateway,firewall and proxy.

Let's forghet for now that we need internet on these vlans, and focus on routing between them and on DHCP.

This I don't understand "And in the DHCP server you have configured DNS to point to your Main Router , the 10.20.10.1 " ???

My clients don't have a chance to receive a DHCP response from the server ( 10.20.10.34) becouse they can't see it.

I've told you that I can't ping from one into another, but I can ping in all vlan interfaces. ( .33 / .49 / . 65 ), but not 10.20.10.1 becouse in Vlan1 ( default vlan) a don't have a tagged port (Here I can't do enything without affecting all my running netowork enviroment)

thank you.

Marius_rg
Advisor

Re: HP 5304Xl inter-vlans routing issue

Why ip routing isn't enough to route between vlans? What else do I have to do ?
Mohieddin Kharnoub
Honored Contributor

Re: HP 5304Xl inter-vlans routing issue

Hi

Sorry for not replying back, kinda busy.

I noticed that you have enabled RIP on your Switches, and for what ? i have no idea !!!

I think you have configured RIP to redistribute the connected Vlans Routing Table to the Routers, anyway , You still don't need this RIP enabled.

Disable RIP on the Vlans (anyway its not enabled for all of them), and check the routing between the Vlans.

The command:
ip route 0.0.0.0 0.0.0.0 10.20.10.1
is needed as a default Route.

Now, i want you to do 2 tests for me.

1- Plug your PC in Vlan1 port, and see if you can get an IP address.

2- Plug your PC in Vlan20 port, but before doing that, assign a static IP address for you which is 10.20.10.35 255.255.255.240 and Gatwaway 10.20.10.33 ,

- and try to ping 10.20.10.33
- and ping the DHCP server 10.20.10.34
- and try to ping 10.20.10.1
- and try to ping 10.20.10.3

Give me the results !!!

Points are the way to say thanks :)
Science for Everyone
Marius_rg
Advisor

Re: HP 5304Xl inter-vlans routing issue

No problem,
I enabled Rip from HP examples
http://www.hp.com/rnd/support/config_examples/5300xl_portbase.pdf

And YES rip is configured to redistribute the connected vlans.

Now,
the vlan 1 is fully operational, in this vlan is the entire firm.
I've created those vlans for test, to prepare for transition.
So, all the computers are connected to vlan1.
In vlan20 is working, I'm getting ip from DHCP and I cand ping in DHCP,in all interfaces (.33/.49/.65). In 10.20.10.1 i can't ping. Perhaps is because I don't have a tagged port (C3 who is present in all the others) in this vlan.

So, how I can route to something that I can't reach.
Port C3 is the link to another switch, on withc are all servers, so I can't play with this port on vlan1.