VLAN routing 4924

[organman]

I have 4924 switch and on port 12 I have VLAN 2056 and 2048 coming in to the switch.
VLAN 2056 should then be allowed to communicate with VLAN 1 on port 23, VLAN 2048 should be allowed to communicate with VLAN 133 on ports 1-11.

VLAN's 1 and 133 should never be allowed to communicate and same is true for VLAN's 2056 and 2048.

So I want VLAN routing to happen between VLAN 2056 and VLAN 1.

How do I configure this ?

I've read some manuals and found this:

Communication between different VLANs can only take place if they are all connected to a router or a Layer 3 Switch. Alternatively, if the Switch containing the VLANs is itself a Layer 3 Switch and is configured correctly,
it will be able to route the traffic from one VLAN to the other internally.
-----------------------------------------------------------
I also found this:

The “routing over bridging” scheme requires a VLAN-based IP Interface.
To create this kind of interface you must first configure a VLAN and then create a router interface over that VLAN.
---------------------------------------------------------

Seems to me that each VLAN must be assigned an IP address and then routing can take place.
This confuses me since I don't want to get into any IP routing conflicts with my existing IP adressing in the network.

I hope someone can clarify how this works and how to set up the routing between VLAN's.

Thanks
L-G Nihlman

 

[avilov]

It looks like that you already have some kind of router where you have all VLANS and routing betweeb them configured.

so now all yo need is to create a trunk port on the 4924 with all vlans configured (1, 133,2048 and 2056) connected to that router. that should do it.

 

[organman]

Well, the point here is that the 4924 shall be the router.
The examples from the manuals I referred to is from the 4924 manual.

My problem is that I don't understand what steps that are needed to be taken in the configuration of the 4924 switch in order for it to route between my VLAN's.

Any suggestions are welcome.

/L-G Nihlman

 

[bram4ict]

to organman:

i have the same problem,

i've a 3COM 4924 that will serve as router
and
i've a 3COM 3226 that will be the access-switch for pc's

there are 2 VLAN's

172.16.0.0 and 172.17.0.0

communication within the same VLAN is no problem, but VLAN1 cannot communicate with VLAN2 because of routing problems in the 4924 switch(router)

i already tried with static routes and Ripv1/Ripv2

-- if someone knows how to solve this problem, please contact me or respond to this thread --

 

[organman]

Actually I think I got it working in my environment, but I have not been able to verify this.

If you go to 3Com's website and support and then look for the 3Com knowledgebase and there search for this:

Solution ID:
2.0.98621725.3642778

It will tell you how to set up routing between VLAN's, however it does not mention the fact that you should enable "Ignore STP per VLAN".

In the manual for the 4924 this can be read:
3Com recommends that you use the Ignore STP per VLAN feature as this offers greater flexibility.

I set up the 4924 and two 4400 switches in a lab and followed the solution mentioned earlier.
I did get it work in the lab but when I put the 4924 in the production network it did not work anymore.

But I'm pretty sure that the reason for this was that I had
not enabled "Ignore STP per VLAN".

Hope this info will help you.

 

[bram4ict]

to organman:

thanks for the tip, i'll check it out monday first thing

i also fixed another problem with the 4500 series
--> the uplink ports (suppurted in all VLAN's) should have the VLAN-ID of the first VLAN (cfr: tagged & untagged ports in the 4900 series)

that already solved one problem

i'll tell you if it will work with "Ignore STP per VLAN"

thanks

 

[bram4ict]

it has been so busy, so i forgot to respond on this thread

the problem that i had a month ago, was due to a loop in the network

because of that loop, the stp (spanning tree protocol) blocked some traffic to prevent routing/switching loops

i had 2 uplinks to the same switch, without any link aggregation

kind regards