asked on

configure Cisco 1900 VLAN

For an engineering test setup, I need to create 4 VLANS on a Cisco 1900 EN that do not share traffic, but each can uplink to my primary LAN. This allows some equipment under development to broadcast without interfering with the other platforms (I have 4), but I need to pass traffic from each VLAN through another port. I have sucessfully configured the 4 VLANS, using the default 1 and three new ones. Each VLAN keeps its traffic local to itself, but i cannot seem to get an uplink working. I am trying to use one of the 100mb trunking ports. Is this correct? Or do I configure a new VLAN for this purpose. I'm a bit lost. i read that Access Control Lists would help but it's not clear to me how to set one up. I think this is a fairly simple config but I'm missing something. Thanks - Dale

Don Johnston

It's been a while since I saw a 1900xl, but if memory serves,

int fa0/26 (port A is 26 and B is 27)
trunk on

That's it. Keep in mind that the 1900xl can ONLY do the Cisco ISL trunking protocol.

What's the device at the other end of this trunk?

Les Moore

What are you trying to uplink/trunk it to? I believe the 1900 only supports ISL trunking and all of the newer switches only support dot1Q trunking.
Do you have Enterprise edition on the 1900?
Here's the config guide that has some other information
http://www.cisco.com/en/US/docs/switches/lan/catalyst2900xl_3500xl/catalyst1900_2820/version9.00.00/scg/1vlans.html#wp5001

dvanaken

ASKER

Thanks - to answer your questions, the "uplink" sits on an unmanaged LAN switch - I was under the impression that I don't really need to "trunk" per se, this is more of a routing type function - am I wrong? I am trying to use the menu interface, so any pointers in that direction will be helpful. --Dale

Don Johnston

Since the 1900 is a layer two switch, you're not going to be able to move any traffic between VLANs without a router. I was assuming that you were trunking to a Cisco router.

And the menu interface is really only for basic configuration. I'm not sure how detailed you can go using it. Most configuration has to be done through the command line interface. (K from the menu)

SOLUTION

Les Moore

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Les Moore

LOL! Posting at the same time... At least Don and I agree.....

dvanaken

ASKER

Thanks - glad you agree - just to be clear, I don;t need to route between VLANS, I just want to get each VLAN to talk to my other network resources, that's why I'm calling it (probably incorrectly) an uplink. So... one of you please confirm that I'm going down a dead-end and I'll split the points - thanks --Dale

Don Johnston

If the other end of the link is an unmanaged switch, then it will discard the ISL frames and any other device off that switch will never receive them.

So I guess the answer is yes, you're going down a dead end.

I'm still confused though. You have 4 VLANs. You want to send the traffic from all 4 VLANs out a single port to an unmanaged switch. What would you want the unmanaged switch to do with these frames?

dvanaken

ASKER

Well... the unmanaged switch is on the company LAN and will provide the interface to LAN and WAN resources (source control, exchange server, Internet) for the developers who have their development PC's on one of the VLANs. Point of detail - each VLAN is one developer with one piece of target hardware. Although we want to limit the pre-alpha software from blasting broadcasts all over (hence the use of the VLANs), they still need access to the company LAN, etc. (hence the uplink). Am I making any sense?

ASKER CERTIFIED SOLUTION

Don Johnston

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

dvanaken

ASKER

Ok I sounds like I cannot accomplish what I intended. Thanks for the great points, tho'. I will split point 60/40 to donjohnston and lrmoore. All the best... -Dale