Solved

VLan with multiple subnets

Posted on 2014-02-11
5
33 Views
Last Modified: 2016-01-10
I have a network with voice and data vlans across several Cisco 3560G switches. I need to add a subnet to the data vlan and provide internet access to it. The subnets are completely separate class C; they are not contiguous Right now I can get internal network access but no internet. What is the best way to configure this?
0
Comment
Question by:kshing519
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
5 Comments
 
LVL 4

Expert Comment

by:colditzz
ID: 39851881
I would hazard a guess that you either need to add an outbound NAT rule to your edge device to deal with the new subnet that has been created, or that there are ACLs stopping the new (and previously unknown) subnet accessing the internet.  As your existing subnets are non-contiguous, I would guess that you have individual outbound rules configured per subnet.

Of course, this could be well off the mark, but without knowing more about your specific configuration, these are the most likely reasons I can come up with.

Hope this helps.
0
 

Author Comment

by:kshing519
ID: 39851987
The edge device is vendor owned. They provide the subnets (because we use a hosted app over a vpn), but I must specify a router. I currently have a Win2003 server with an IP in each subnet. It is assigned as the gateway for the devices in the new subnet. In their router, they route that traffic back to my server.

Sub1 - 192.168.148.0/24
Sub2 - 192.5.141.0/24

The switches have vlans assigned by port - some voice, some data, some cameras. It seemed like when I connected to a data port, the vlan assignment went missing.

I'm trying to establish whether my issue is with the switch config or the routing.
0
 
LVL 4

Accepted Solution

by:
colditzz earned 500 total points
ID: 39852015
It could be that the IP range you have used (192.5.141.0/24) is a public IP range, it is not part of RFC 1918 and this could be part of the problem, i.e. the vendor owned edge device is configured to only expect RFC 1918 ranges on it's inside.

Your server could be doing the NAT outbound.  But if you think the config looks correct, I would ask the vendor if they can see traffic between their device and the new subnet you have used.

Cheers
0

Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

There's a better way to communicate time sensitive or critical info.
How many times a day do you open, acknowledge, or close an IT incident? What’s your process? Do you have a process depending on the incident, systems involved, and other factors? New Relic Alerts gives you options for how you interact with notifica…
Are you ready to implement Active Directory best practices without reading 300+ pages? You're in luck. In this webinar hosted by Skyport Systems, you gain insight into Microsoft's latest comprehensive guide, with tips on the best and easiest way…

710 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question