[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1034
  • Last Modified:

InterVLAN Routing on 3com 2900 Series

I've read a few other posts on this, and unfortunately none have been able to get me to where I need to be.

I need to implement VLANs for my development network, inter-office VOIP, and departments. For my test I've got VLAN1,2,11. I'm working with managed routers from AT&T, and it could be a little of what is causing my issues, as I'm trying to clean up some work that was left by a former admin. All switches are 3com 2900 series.

Current Layout
Ideally, I want to seperate the major components on my network with the VLANs. It's most important for us at the moment, because we need to apply QoS to the phones, and to do it I need them off on their own.

I've created VLAN1,2,11 on all of my switches. I've assigned the ports connecting those switches as tagged hybrids. I have two test machines plugged into the first switch, port 11 untagged as VLAN2 and port 9 untagged as VLAN11. Neither port 9 or 11 are members of VLAN1. I have created VLAN interfaces as follows:

VLAN1interface - 10.1.1.10/24
VLAN2interface - 10.1.2.1/24
VLAN11Interface - 10.1.11.1/24

VLAN2 & VLAN 11 Device:
CAN
Ping its gateway 10.1.2.1 for VLAN2 and 11.1 for VLAN11
Receive it's IP via DHCP from 10.1.0.104 DHCP server
CANNOT
Access or Ping anything beyond its VLAN - including the DHCP server it contacted for address

A VLAN1 device cannot ping anything on 2 or 11, including the interfaces with the DGW currently in place. A VLAN1 device with an address of 10.1.1.108/24 WILL Ping the interfaces of VLAN2 and 11 if the DGW is set to 10.1.1.10, but will not go any further. When I have tried to change the VLAN1 interface to 10.1.1.1, I lose connection to my server subnet of 10.1.0.0/24.

Advice is appreciated, as I have a second site that has the exact phone system connected via the PNT, and we need to do the same there. ATT is waiting to implement CoS across the WAN once we have the addressing and VLANs down.
0
jrobinsonvls
Asked:
jrobinsonvls
  • 6
  • 3
1 Solution
 
SouljaCommented:
Which switch in your diag is handling the vlan routing? You don't note that in the diag. Have you insured that you are trunking all of the vlans? Addionally, why are you running two different subnets in vlan 1?
0
 
jrobinsonvlsAuthor Commented:
The first switch is handling the vlan routing at the moment Soulja. At this point the trunking I don't THINK would be the issue, as I've got all of the devices in question on the same physical switch for testing.

As for the two subnets in VLAN1, up until two weeks ago we weren't using VLANs at all. The previous netadmin was running everything on PVID1. The ATT Router was being used to route between the 2 subnets, and as I'm reading it they've also put a route in there that allows it to route the entire /16 as well. In my head, it makes more sense to pull the routing off the ATT box and back onto the switches, but I'm not sure what effects it will have on the network as it is functioning now.
0
 
SouljaCommented:
Yes, I would pull the vlan routing off of the att router. The ATT router should just handle routing to/from the WAN.
0
[Video] Create a Disruption-Free Workspace

Open offices have their challenges. And Sometimes, it's even hard to work at work. It's time to reclaim your office and create a disruption-free workspace. With the MB 660, you can:

-Increase Concentration
-Improve well-being
-Boost Productivity

 
SouljaCommented:
If the router is still set up for routing, it could possibly be interferring with your routing on your L3 switch.
0
 
SouljaCommented:
I also noticed in your diag that the default gateways for the vlan 1 devices are not pointing to the vlan 1 interface on the switch. If they are still pointing to your att router, that is the issue. The att router doesn't know how to get to your new vlans.
0
 
jrobinsonvlsAuthor Commented:
Soulja

Are you saying that if I add another VLAN in to take the servers, add the interface, and THEN ask ATT to remove the routes from their router then I should start functioning normally?

Please understand my hesitation, because from the majority of my users prospective, the network "works" right now... if the change takes us down, there will be other issues that I'll have to deal with as well :)
0
 
SouljaCommented:
No, I am not saying add another vlan. You have already created the Vlan 1 interface on your L3 switch. You will need to point your vlan 1 devices to that vlan interface. To accommodate the two subnets in Vlan one, you can add a secondary ip address to the vlan 1 interface on the L3 switch. For example:

vlan 1 interface will have
ip address 10.1.1.10/24
ip address 10.1.0.252/24

and add a default route to the att router

ip route 0.0.0.0 0.0.0.0 10.1.1.1

On the ATT router all it needs it the routes to return traffic. Assuming the att router sits on vlan 1 with an ip address of 10.1.1.1

ip route 10.1.11.0 255.255.255.0 10.1.1.10
ip route 10.1.2.0 255.255.255.0 10.1.1.10
ip route 10.1.0.0 255.255.255.0 10.1.1.10

0
 
jrobinsonvlsAuthor Commented:
I see what you're saying, but what I was getting at with the other VLAN for the servers was to break them off on their own so that I'm conforming to a standard of 1 subnet per VLAN (sort of the OCD in me I guess.)

The ATT router does sit on VLAN1, so I'll submit the ticket for them to add the routes. And since ATT runs on their own time, it might be a day or so before they get them added... so standby while I set the cogs in motion.
0
 
SouljaCommented:
Yes, you are correct. You can set up another vlan. I would if I were you. Maybe vlan 3 or something. Then create a vlan interface for vlan 3 and point those devices to it.
0

Featured Post

 [eBook] Windows Nano Server

Download this FREE eBook and learn all you need to get started with Windows Nano Server, including deployment options, remote management
and troubleshooting tips and tricks

  • 6
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now