Skip to main content

New to Cisco VLAN configuration couple of questions

More
19 years 12 hours ago #11585 by haselnut
First of all let me say I have no experience working with Cisco equipment or VLAN’s for that matter so please be patient. :wink: Vlan’s are easy enough to understand but I think my problem right now is actually the configuration steps to get it all working. I’ve read the articles on this site and some other information around the web, but I’m still having problems getting all this to work.

This is the hardware:
1 Cisco 3560G
6 Cisco 2950’s
These are the vlans:
Vlan: 100 Name: STATIC – Static IP machines – all plugged into the 3560 (mostly servers and printers)
Vlan: 200 Name: DHCP – 98% of the addresses here will be DHCP. (mostly clients)

Clients need to access all resources on vlan 100

3560G
Configured as VTP Server
Port 1 – Connected to watchguard firewall appliance (do I need to configure this port at all?)
Ports 2-42 configured as static access vlan 100
Ports 43-48 configured as 802.1Q Trunk Links – one port will be used for each of the 2950’s

2950’s
The uplink ports on the 2950’s will be configured as trunk links in order to communicate with the 3560.

Now when I configure ports 2-42 on the 3560 I lose all communication with the switch unless I plug into a port that hasn’t been configured. Then of course I can see it and the other 2950 I am using to test. Why can’t I ping the switch when I’m plugged into a port that has been assigned a static access vlan? Is this a routing issue even though the laptop I’m using is plugged directly into the switch?


I’ll stop there for now, once I figure out how to get these guys talking to each other I’ll have more questions.

Thanks
More
19 years 12 hours ago #11586 by susetechie
Hi There,

I still consider myself a newbie honestly, but just a question. I am not extremely familiar with these two devices but does either of these have layer three capability? do you have a routing configuration(ie. static, rip)? are you assigning ip's to these vlan interfaces?

My take on vlans is that for inter-vlan communication, you need a layer three device. also, what is your management vlan? its usually 1 by default and my understanding is that your switch ip needs to be in this vlan for communication.

Maybe these will get you started...hopefully i have provided correct info, if not...someone please point it out.

Good Luck,
M

"Go away or I will replace you with a very small shell script"
More
19 years 12 hours ago #11588 by haselnut
The 3560G is a layer 3 switch and the 2950's are layer 2. The managment vlan is 1 (default). I haven't configured any routing on the 3560 yet, I thought I needed to configure the vlan stuff first.

The IP address of the switch (3560) is 192.168.1.100 and the laptop I have plugged into it is 192.168.1.199. I can ping that address as long as i'm not plugged into a port that has been configured as a static access vlan.
More
19 years 11 hours ago #11589 by susetechie
I would think you would need a routing config to get access to those other vlans. either a static route to these others or a routing protocol like rip.

In essence your laptop when plugged into a port configured as vlan 100, when your switch is in vlan 1 may not be able to communicate. these are to the switch totally different ip "subnets". you will need a address scheme for these different ones such as:

Vlan 100: 192.168.2.0
Vlan 200: 192.168.3.0

Again....correct me if i am wrong.

"Go away or I will replace you with a very small shell script"
More
19 years 2 hours ago #11595 by reaper
You need a default gateway that will route the VLAN's, either the Cisco or another router. Please check this document on how to configer inter-VLAN routing. Good luck.

www.cisco.com/en/US/products/hw/switches...186a00801cc828.shtml
Time to create page: 0.194 seconds