Aruba & ProVision-based

Re: configuration issues (more like user issues) on Hp5400 procurve

 
out_of_depth
Occasional Contributor

configuration issues (more like user issues) on Hp5400 procurve

Okay i will admit that i have buggered this up and now i need some help un-buggering it.

 

I am trying to do the following

have two vlan

vlan 1 to have 2 subnets on it 192.168.1.0/24 and 192.168.90.0/24

 

vlan 4 no ip address, traffic will just flow through it

 

I want the traffic on either the 90 or the 1 subnet to route and talk to each other ie if i am on ip address of 192.168.1.30 and ping 192.168.90.10 that it can connect etc

 

all of the ports and trunks i have pretty good handle on.

 

Now my current config has got itself into a bit of knot

 

so at the top  i have managed to get this

 

; J8697A Configuration Editor; Created on release #K.15.12.0012
; Ver #05:08.41.ff.3f.ef:63
hostname "HP-5406zl"
module 1 type j9538a
module 2 type j9538a
module 3 type j9550a
module 4 type j8702a
module 5 type j8702a
module 6 type j8702a
trunk A1-A4 trk1 lacp
trunk A5-A8 trk2 lacp
trunk B1-B4 trk3 lacp
trunk B5-B8 trk4 lacp

 

##### these are wrong and probably should not be here. cant work how to remove
ip route 192.168.1.0 255.255.255.0 192.168.90.1       
ip route 192.168.10.0 255.255.255.0 192.168.1.1

###### end of wrong bit


ip routing

.... There are a load of port defs here which i have not included

 

vlan 1
   name "Internal_Traffic"
   no untagged C13-C24
   untagged C1-C12,D1-D24,E1-E24,F1-F24
   tagged Trk1-Trk4
   ip address 192.168.1.1 255.255.255.0
   exit
vlan 4
   name "External_Traffic"
   untagged C13-C24
   tagged Trk1-Trk4
   no ip address
   exit

management-vlan 1
spanning-tree
spanning-tree Trk1 admin-edge-port
spanning-tree Trk1 priority 4
spanning-tree Trk2 admin-edge-port
spanning-tree Trk2 priority 4
spanning-tree Trk3 admin-edge-port
spanning-tree Trk3 priority 4
spanning-tree Trk4 admin-edge-port
spanning-tree Trk4 priority 4
spanning-tree instance ist Trk1 path-cost 2000
spanning-tree instance ist Trk2 path-cost 2000
spanning-tree instance ist Trk3 path-cost 2000
spanning-tree instance ist Trk4 path-cost 2000
spanning-tree force-version rstp-operation
no tftp server
no autorun
no dhcp config-file-update
no dhcp image-file-update

 

so how do i go about fixing this to do what i want to do.

I ideally would also like to give the switch the ip of 192.168.1.48. at the moment it is .1.1.  all of the machines are using .1.1 as the gateway and anything on the 90 subnet are using 90.1 as gateway

 

Hope that makes sense.

 

some simple commands to get what i want would be good.

This switch has virtual connect 10 connecting to which is what the 10gb trunks are that are mentioned in the config

 

 

P.S. This thread has been moved from Switches, Hubs, Modems (Legacy ITRC forum) to ProCurve / ProVision-Based. -HP Forum Moderator

 

 

3 REPLIES 3
Pete W
Valued Contributor

Re: configuration issues (more like user issues) on Hp5400 procurve

What's the reason for using 2 x subnets within the same VLAN?

 

Pete

out_of_depth
Occasional Contributor

Re: configuration issues (more like user issues) on Hp5400 procurve

Hi Pete

 

There are numerous reasons for wanting to have different subnets on the vlans.

 

Most of these reasons originate away from this switch and at the virtual connect 10 layer to the blades and also with the virtualiasation layer etc.

 

We are using shared uplink sets within the virtual connect and trying to avoid doing vlan tunneling through virtual connect.

 

As i understand it a vlan can have multiple subnets attached to it.

correct me if i am wrong

Pete W
Valued Contributor

Re: configuration issues (more like user issues) on Hp5400 procurve

You are correect, you can have multiple subnets on a VLAN, so the following should work.

 

conf ter

ip routing

vlan 1

 ip address 192.168.1.0/24

 ip address 192.168.90.0/24

 exit

vlan 4

 no ip address

 exit

 

# Remove IP ROUTE commands

no ip route 192.168.1.0 255.255.255.0 192.168.90.1       
no ip route 192.168.10.0 255.255.255.0 192.168.1.1

 

end

 

Personally, I only use multiple IP ranges in the same VLAN in cases of emergency or as an interim measure when doing re-IP addressing projects. Without going into detail here - I would simply advise to put in the leg-work and get those VLANs working through VC. Remember, just because you can, doesn't mean that you should (Google "multiple subnets on one vlan" to get other opinions).

 

Regards,

 

Pete