× NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Orbi WiFi 7 RBE973
Reply

NetGear GSM7328Sv2 VLANs in the CISCO World

Nizax
Follower

NetGear GSM7328Sv2 VLANs in the CISCO World

Hello Guys,

 

I am having a pretty hard time figuring out the equivalent VLAN configurations of the netGear.

I am totally new to netgear's switching and its approche regarding VLANs since I worked almost my whole life with CISCO switchs.

I did my researches and understood the PVID, TAG and UNTAG concepts in Netgear. But I still hit a wall when analysing a configuration and trying to convert it into the CISCO world.

I have a project with a client that wants to replace its core netgear switch by a CISCO one. To do so, I need to be able to understand the configuration present in each port in order to translate iT on the new CISCO core.

My question is straightforward :

Analysing the configuration, I can see those kind of configs :

 

interface 1/0/15
vlan participation include 10,20,22,30,56-57,60,62,72,82-83,100,156
vlan tagging 13,20,22,30,56-57,60,62,72,82-83,86-87,100,156
exit

 

I belive this stand for :

Interface 1/0/15

Switchport mode trunk

Switchport trunk allowed vlan 13,20,22,30,56-57,60,62,72,82-83,86-87,100,156

 

I'm I right ? If so, why does the VLANs in participation are different from those who are tagged ? What's the matter with VLAN10 ?

 

Another configuration is this one :

 

interface 1/0/14
vlan pvid 32

exit

I also belive this stand for :

interface 1/0/14

switchport mode access

switchport access vlan 32

 

Then I saw this configuration :

 

interface 4/0/1
vlan pvid 14
vlan participation auto 1
vlan participation include 14,31-32
vlan tagging 31-32
exit

 

Then I saw this configuration and now I am totally confused

Model: GSM7328Sv2|ProSafe 24 ports managed L3 gigabit stackable switch
Message 1 of 2
msi
Luminary
Luminary

Re: NetGear GSM7328Sv2 VLANs in the CISCO World

I've run 10.x based firmware M4100 and moreso the 12.x based M4300. The client could have used "switchport mode trunk" or "switchport mode access" where the CLI syntax and behavior would have been pretty close if not (almost) identical to classic IOS. - I personally prefer to use access and trunk mode on our M4300's to be honest.

 

Now onto your first example: It looks right to me.

 

> If so, why does the VLANs in participation are different from those who are tagged ?

From the M4300 CLI reference on "vlan tagging": "If tagging is enabled, traffic is transmitted as tagged frames". It could mean that frames leaving the port (egress) might not be tagged. To be honest, usually I'd have added a "pvid" statement to make it clear as when untagged frames enter this port (ingress) the switch would know what tag it should add.

 

> interface 1/0/14
> vlan pvid 32

> exit

> I also belive this stand for :

> interface 1/0/14

> switchport mode access

> switchport access vlan 32

 

Mostly, I'd likely have  added a vlan participation include 32 to make it more understandable on the Netgear side. It only tells the switch to tag incoming untagged frames with ID 32.

 

> Then I saw this configuration and now I am totally confused

I'll try to explain things inline

 

> interface 4/0/1
> vlan pvid 14

If untagged frames enter the switchport, tag them with VLAN ID 14
> vlan participation auto 1

The port will transmit and accept frames with VLAN ID 1, this is the default behavior.


> vlan participation include 14,31-32

Accept frames with IDs 14 and 31-32


> vlan tagging 31-32

Accept tagged frames with IDs 31-32.

 

It could be translated to like:

switchport mode trunk

switchport trunk allowed vlan 14,31-32

switchport trunk native vlan 14

 

The M4300 software administration manual (simply that the model line I'm currently most familiar with) has a section "VLAN Access Ports and Trunk Ports" where they explain the operational behavior between Access, Trunk and General mode. General mode is the default and is what your client is currently using.

 

Message 2 of 2
Discussion stats
  • 1 reply
  • 1106 views
  • 0 kudos
  • 2 in conversation
Announcements