|
Home > Archive > CCNP > June 2001 > CAT 2924 Multi-VLANS
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
CAT 2924 Multi-VLANS
|
|
| marinos9 2001-06-21, 11:57 am |
| I believe RJohn was talking about this earlier but didnt' get the whole picture
anyhow
need help on CAT 2924
set up 2 vlans on one Switch and want to be able see devices on VLAN 1 from VLAN 2 and back again
example hosts
VLAN 1 host = 192.168.9.10
VLAN 2 host = 192.168.10.11
I've set up both VLANS and added ports to them with the "Switchport" command
I've even tried to make one of the ports to resolve on both VLANS. This wouldn't resolve it either
I do understand that this is probably a layer 3 issue but would like to know if there is another way around with VTP
Any suggestions? | |
| marinos9 2001-06-21, 11:59 am |
| ohh also, the VLAN remains in shutdown mode no matter what I try
no shutdown
add interface
???????? | |
| dmaftei 2001-06-21, 12:10 pm |
| quote:
Originally posted by marinos9
I do understand that this is probably a layer 3 issue but would like to know if there is another way around with VTP
Yes, it's a layer 3 issue, and there's no way around with VTP. You must route between VLANs, in your case with an external router, or on high-end switches with an RSP/MSFC/etc. (I don't remember the other acronyms).
Cheers! | |
| strikeattack 2001-06-21, 2:55 pm |
| Yep. In order to facilitate inter-VLAN traffic, you MUST ROUTE. This involves switching at layer 3, and not just at layer two. As Dmaftei said, you will need either a switch capable of switching at layer three, or two external routers (or maybe one external router with two FE interfaces).
Regarding this..
quote:
example hosts
VLAN 1 host = 192.168.9.10
VLAN 2 host = 192.168.10.11
Typically what is done, is the traffic is bridged up to a master switch (EX: CAT 6509) that does the layer three switching for the network. Hope this helps. | |
| dmaftei 2001-06-21, 3:29 pm |
| quote:
Originally posted by strikeattack
... or two external routers (or maybe one external router with two FE interfaces).
What about one link between your switch and your router? You put the port on the switch in trunk mode. Then, on your router:
(config)#interface fast 1.1
(config-if)#encapsulation isl 1
(config-if)#ip address 192.168.9.2 255.255.255.0
(config-if)#exit
(config)#interface fast 1.2
(config-if)#encapsulation isl 2
(config-if)#ip address 192.168.10.2 255.255.255.0
(config-if)#^Z
Cheers! | |
|
| marinos9,
Assuming you have one switch only (no trunking) you may perhaps use the multi-VLAN feature. I once considered this for a design but discarded the idea before trying. What follows is therefore from the books, not from practical experience.
Assign some ports to VLAN 1 and some to VLAN 2 as usual. The port you want to participate in both VLANs is configured like this:
SWITCHPORT MODE MULTI
SWITCHPORT MULTI VLAN 1,2
The device you connect to this port will now be able to see both VLANs. If you need every device on each VLAN to be able to speach to every device on the other VLAN, put a router on this port. The router interface should have IP addresses belonging to both subnets. If the router is a Windows NT or 2000 Server there is an "advanced" button to configure multiple IP addresses on an interface. In Ciscospeak you use the "SECONDARY" keyword on all but the first address.
If all this fails, you could always go back to the well-established practice with a router-on-a-stick that dmaftei described. Be aware that you need some minimum feature set in your router IOS to do that. Also, in that case you configure the switch port as a trunk port, not a multi-VLAN port. You can't have a trunk port and a multi-VLAN port on the same switch. If your router does not have a FastEthernet interface, the trunking protocol should be 802.1q.
If you actually get any of this to work, please let us know!
Terje | |
| marinos9 2001-06-22, 7:22 am |
| kewl,
just as I suspected, I didn't want to setup ISL as VLAN 1 is in use already and as we know this is the only VLAN capable of running ISL, also there wasn't a router with 2 nics to route the packets. As this was just a test the use of a hub and a little redesign resolved the problem.
Thanks for all your help
As being my first post on this board I must admit I'm impressed with the response.
I hope to be able to help as you all have
cheers! |
|
|
|
|