Configure VLAN to route 2 subnets. Need to combine 2 class C subnets

HP ProCurve VLAN jargon:

Tagged ports = trunks between switches that carry vlan routing information
Untagged = ports connected to end devices (PC's, computers) and are essentially 'member' ports
Trunks = switch inter-connects that allow a vlan on one switch to communicate with an identical vlan on another, or other vlans on another, etc.

You're in luck - the 2848 is a layer 3 switch, so the choice is now yours to walk down one path or the other. For long term scalability and general network performance improvement, VLAN'ing would best suite, however as Mike has said supernetting your current range would be a little bit easier.

If you choose the VLAN method, let me know and I'll write you up a step-by-step for what you need to do (providing you can give me a better idea of your topology).

Changing the subnet would be hard due to the fact we have a mesh network and our gateways are mangaged by our ISP.  Plus we have alot of static IP's

I have a 2650 , 2824, and 2848;

I link both the 2650 and 2824 to the 2848 which is where i keep all my bandwidth intense servers etc.  

The 2824 has a vlan and trunk for our phone system.  They guy dint know HP and set it up on the cisco gateway to send between subnets as a router vs using the switch.  ( i dont really care bc the only time we go between subnets is to manage the phone system)

I think the trunk was done via CLI.  I can try and get that info from telnet.  here is a screenshot of the currrent vlan (which im not sure has anything to do with what I need to accomplish.)

At this time I dont really even care if the two subnets broadcast all traffic as if it was superneted  I am going to move my VPN appliance and all new servers to the new subnet.

We outgrew how I was doing it. we do not have a tun of users just alot of nodes and reservations. (ie i reserve 20 ips for coorporate visitors so they can get pop/smtp)

If i can get you more info just say so.

Thanks

Quori

you there?  not a huge rush just making sure you know im waiting for your step by step.

let me know if you need more info

thanks

Hi,

My apologies, I've not been well.

I shall do up a step by step today.

take your time.  hope your feeling better.

You said you have a VLAN for your phone system? Is this a VoIP system which you'll want to be plugging your handsets into the two access switches? Or...?

Are devices from both subnets going to be co-existing on each switch?

It is irrelivent I think.  the screenshot shows everying about it I think minus the trucking.

its just to keep broadcast traffic seperate. WE only do VOIP from office to office on a fully meshed MPLS network.  the only thing that plugs into that network is the avaya phone system.

Well, it isn't irrelivant as we need to know if the different VLAN's will exist on the other switches - so are trunks needed or can we just take the uplink port as a normal member, etc.

the voice vlan is onlly on one switch.

Voice Vlan:

Ports 1-2 are untagged / Ports 3-22, 24 are "no" / port 23 is "tagged"

Default Vlan:

Ports 1-2 are "no" / ports 3-24 are untagged

=======================

I dont know if that helps.  I dont fully get this stuff so it could be significant.  he explained it to me that to go from my main network and telnet to the phone system I hit my default gateway (main firewall cisco router that does our firewall/QOS and MPLS VPN).  the cisco router knows about the voice vlan and sends it back the same physical wire on the voice vlan and i connect. So the switch is not doing anything as far as routing.

I dont know the CLI well, but ill try and get some info out for you:

================================

switch0# show vlans
 Status and Counters - VLAN Information
  Maximum VLANs to support : 8
 Primary VLAN : DEFAULT_VLAN
 Management VLAN :
  802.1Q VLAN ID Name         Status     Voice Jumbo
 -------------- ------------ ---------- ----- -----
 1              DEFAULT_VLAN            No    No
 3              Voice                   No    No

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

switch0# show config (pasting information that may help only)

ip default-gateway 192.168.10.254

snmp-server community "public" Unrestricted
vlan 1
  name "DEFAULT_VLAN"
  untagged 3-24
  ip address dhcp-bootp
  no untagged 1-2
  exit
vlan 3
  name "Voice"
  untagged 1-2
  tagged 23
  exit

show trunk does not seem to produce anything... could have sworn he did something with trunking, but maybe not.

anything you want me to do from CLI just let me know

Forgot i visio'ed this

Im about to try this... here is my visio though to confirm you understand how its setup.

if you see anyhthing setup like a networking noob let me know :D

Also note I do not want to chagne the voice vlan to route on the switch. I dont want to mess with the cisco config since its hosted.

I just want to route the default vlan and a new vlan.

the first command is failing me.. Epic fail :(

copy of doing a help "?"  you can see enable is an option.  below is what happens

enable                Enter the Manager Exec context.
exit                  Return to the previous context or terminate current
                      console/telnet session if you are in the Operator
                      context level.
link-test             Test the connection to a MAC address on the LAN.
logout                Terminate this console/telnet session.
menu                  Change console user interface to menu system.
ping                  Send IP Ping requests to a device on the network.
show                  Display switch operation information.
traceroute            Send traceroute to a device on the network.

switch0(config)# enable
Invalid input: enable

how do you back this thing up anyway?

Once you're in config mode you can skip the 'enable' and 'conf t' commands - I just give commands from the moment of login.

So, you're happy for routing to actually take place on the cisco router but want to be able to talk across VLANs without going through the router?

For the voice Vlan that is fine.  once a month or so I connect to make a few second changeo n our phone system. Thats the only time the two vlans communicate.

For vlan1 and the new vlan I want it just to route directly at the switch.

Ahhh, I thought the voice VLAN was the new VLAN. Whoops! :)

Takes me back to an earlier question - will the new VLAN be used on all switches? IE will hosts from one VLAN be sharing a switch with hosts from another VLAN?

Yes.  Servers and VPN users will be on vlan2

there will be heavy traffic between the two.

Double check the port numbers. :) Was hard to make out from the drawing.

You may also need to add some static routes for each subnet pointing to the IP of the respective VLAN.

IE: ip route 192.168.10.0 255.255.255.0 192.168.10.1
And the same for .11

Then you'd have a default-gateway set for everything else.

SO can i add these trunks to the existing uplink ports w/o effecthing current traffic?

Does each vlan have an IP or does each vlan on each switch have an IP

ie:

switch0(config)# show ip
 Internet (IP) Service
  IP Routing : Enabled

  Default TTL     : 64
 Arp Age         : 20
  VLAN         | IP Config  IP Address      Subnet Mask     Proxy ARP
 ------------ + ---------- --------------- --------------- ---------
 LAN1         | DHCP/Bootp 192.168.10.201  255.255.255.0
 LAN2         | Manual     192.168.11.201  255.255.255.0   No
 Voice        | Disabled

Would the ip on the other switches also be 10.201 and 11.201?

Only the VLANs on the distribution layer have an IP address. Let it handle the routing.

What is the distribution layer?

Trying to figure out what your telling me vs what Im seeing ik found something in the manual about "multinetting"

says you can put multiple subnets on a single vlan.

im not worried about broadcast domains.  woudl this be easier?

whats the difference?

Ill worry about bounding 2 links to dist layer later.

Maybe after I get a new switch as I dont have a tun of space. I keep my servers on the 2848.  so this will be the distribution switch with one uplink for now (for the sake of nodes and keeping this task one thing at a time.)  

ill create a second issue for the uplink later and link it here

You hit the nail on the head. With that sort of traffic, you'd suffer a major performance loss due to broadcasts.

Distribution layer is the 'core' switch. So only the VLANs added to the 2848 will have IP's.

SOrry I got bogged down with other things.

Im going to accept this. I spoke to hp support after locking myself out :p

I changed a few things.  I may need more help but you gave me a lot of guidence here. enough that I can figure it out i think.

If not ill post a link to a new question. I cant ask you to put more time into a single question!

So id appreciate if you monitor this for future posts with a link to a new question.

thanks for your help