VLANS between Netgear and Cisco

By troyreynolds ·
I am currently attempting to segment some of my network through the use of VLANs. I have several VLANs up and running for other purposes like webservers, public access, VoIP, and IP surveillance cams, but all of those go through either all cisco equipment ot a mix of cisco and 3com. This netgear is throwing me for a loop.

I am trying to build a trunk between the netgear (GSM7328FS) and the cisco (Catalyst 2960).

It seems that once I set the port on the 2960 to "switchport mode trunk" all traffic beyond the netgear stops. It works fine when it's just an access port, as it has been for over 6 months now. I have tried allowing VLAN 1, ALL VLANs, native VLAN 1, etc but I get nothing unless it's set to an access port.

Currently it's using a straight-through CAT5, but I did switch to a crossover with even worse results, as I couldn't even get to the netgear itself with trunking turned on in the cisco.

I could set up a port for access VLAN 1 and a separate port for access VLAN 10, and use 2 ports on each switch, but that just seems tedious, redundant, unnecessary, and a waste of ports.


This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Answers

Collapse -

Define VLANS Manually

by williamsad In reply to VLANS between Netgear and ...

To create a trunk port on Netgear switches the required vlan id's need to be created manually.

1. Enter the config menu and enter the vlan id's
vlan database
vlan 10

2. Configure the trunk port (e.g. port 24)
vlan participation include 10
vlan tagging 10

3. Configure the required device port (say port 2)
vlan participation include 10
vlan pvid 10

Use the regular port rather than one of the stacking ports as it can confuse!
Best of luck.

Collapse -

give it a shot

by troyreynolds In reply to Define VLANS Manually

I will have to try this when i have some time to get deeper into the netgear's CLI, i am far more familiar with the Cisco...

Collapse -

Trunking must be enabled on both ends, Netgear may not talk DTP

by robo_dev In reply to VLANS between Netgear and ...

Trunking is a function that must be enabled on both sides of a link. If two switches are connected together, for example, both switch ports must be configured for trunking, and they must both be configured with the same tagging mechanism (ISL or 802.1Q).

In an all-Cisco world, DTP (dynamic trunking protocol) would save the day. Netgear won't play with DTP, AFAIK.

I would guess you need to force both ends to be 802.1Q, but I never tried that.

Collapse -


by troyreynolds In reply to Trunking must be enabled ...

the cisco in a 48-port 2960 so it defaults all trunk ports to dot1q, and the neatgear only does 802.1Q AFAIK.

The IOS in the cisco doesn't even have the swichport encapsulation command to allow me to change it to anything but .1q

Collapse -

how many switches you got there that you need trunk lines?

by CG IT In reply to VLANS between Netgear and ...

inter-vlan routing is typically done by a router and not a trunk port. If you have 2 switches and there are the same vlans on each switch you use a trunk port to allow the vlans on each switch to pass data between them.

so if switch 1 has vlan 1, switchport membership of 1,2,3,4 switch 2 has vlan 1 switchports 1,2,3,4 you need a trunk line to allow traffic from hosts on switch one to pass data to hosts on switch 2.

if you want to pass data between vlan1 and vlan 10 that reside on switch 1 and switch 2, you need to configure the router for intervlan routing.

So that netgear should provide you with the ability to have intervlan routing [L3 device]

and also to provide trunking. it does run 802.1Q trunking.

Collapse -


by troyreynolds In reply to how many switches you got ...

that was really the purpose of us getting the layer 3 netgear. but we need the netgear to also pass multiple vlan traffic to a cisco that will continue to forward the vlan to our WAN connection in another building

Collapse -

yeah ok so....

by CG IT In reply to inter-vlan

there's nothing in the rule book that says that netgear managed layer 3 switch can't provide inter-vlan routing as well a trunking across switches.

Collapse -


by troyreynolds In reply to yeah ok so....

and that's not the problem... the problem is that it doesn't work and i don't know why the trunk isn't functioning properly. Both sides are 802.1q and should support trunking, the netgear works fine with our CE500 switches through the fiber ports, but we're running gigE copper to the 2960's gigE port and it works, until you set that port to trunk, and then the link stays up, but you cannot reach anything on the other side of that link.

Collapse -

have you tried the old method

by CG IT In reply to exactly

use a switch port on both switches as the trunk port and leave the uplink ports as the access port? Requires moving the cables aroud but heck.

Btw, what port is used to send traffic to the gateway or are you trying to send traffic to the gateway via the trunk port?

Collapse -

let my try to paint a picture

by troyreynolds In reply to have you tried the old me ...

the traffic path goes something like this:

PC => cisco CE500 => netgear L3/fiber => cisco 2960 => another cisco 2960 => gatetway

we are using fiber from the CE500 to the netgear, and the vlans are trunked, and working. I haven't actually set up any access ports yet because if the trunk isn't working, access is useless.

between the cisco 2960's the vlans are trunked, and working.

but from the 2960 to the netgear, through copper, both gigE ports (g0/1 on the cisco and 24T on the netgear) setting the ports to trunk screws everything up. I believe the problem is with the Cisco, because I can set the port on the netgear to trunk and traffic still flows (only to vlan1, obviously) but when I put the other vlan on the cisco and set it to trunk, all traffic stops

Related Discussions

Related Forums