NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Setting up a Cisco Trunk Uplink to a GS105PE - Just configs - and How to
I purchased several GS105PE switches to utilize where I have no AC power, for several devices. The catch is I have to 802.1Q trunk vlans to this switch. I can configure a Cisco switch port to power i...
This is not exactly your PE but it is a Plus series and I hope this helps:
Hello,
After fiddling with this I got it going using Advanced VLAN 802.1q.
I think VLAN 1 has to exist but as I had been fiddling with this for hours I didn't want to risk removing it entirely.
Port 1 is my uplink.
Port 3, 4, 5 are links, each to different VLANs.
As using VLAN 1 is a no-no because it's usually the default everywhere I will give an example of mysetup using 11, 12, 13, and 14.
Cisco config real quickly:
usps#show run int gi 1/22
Building configuration...
Current configuration : 196 bytes
!
interface GigabitEthernet1/22
description wifi-uplink
switchport trunk encapsulation dot1q
switchport trunk native vlan 11
switchport trunk allowed vlan 11-14
switchport mode trunk
end
VLAN > 802.1q > Advanced > Port Configuration:
| VLAN ID | Port Members |
| 1 | 2 |
| 11 | 1 |
| 12 | 1 3 |
| 13 | 1 4 |
| 14 | 1 5 |
VLAN > 802.1q > Advanced > VLAN Membership:
VLAN ID 1: Port 2 (Untagged)
VLAN ID 11: Port 1 (Untagged)
VLAN ID 12: Port 1 (Tagged), Port 3 (Untagged)
VLAN ID 13: Port 1 (Tagged), Port 4 (Untagged)
VLAN ID 14: Port 1 (Tagged), Port 5 (Untagged)
VLAN > 802.1q > Advanced > Port PVID:
| Port | PVID |
| 1 | 11 |
| 2 | 1 |
| 3 | 12 |
| 4 | 13 |
| 5 | 14 |
Hope this helps anyone else going forward.
There is just one issue. The IP I gave it which is on VLAN 11 takes 6 to 7 times longer than the other VLANs. Ports 3, 4, 5 connect to devices. I'm using this like an edge switch. So I average about 0.25ms from my core switch to the devices on port 3, 4, and 5 respectively. But I'm at about 2ms from my core switch to the Netgear switch. It makes no sense, I probably have something messed up somewhere but not sure where.
Regardless as the edge devices have low latency and everything is just fine, no packet loss, loops or drops, I'm good as I got what I wanted. A Cisco trunk w/ 802.1q tagging and a native working.
devnull80s wrote:
I think VLAN 1 has to exist but as I had been fiddling with this for hours I didn't want to risk removing it entirely.
Port 1 is my uplink.
Port 3, 4, 5 are links, each to different VLANs.
As using VLAN 1 is a no-no because it's usually the default everywhere I will give an example of mysetup using 11, 12, 13, and 14.
Think again from where this theoretical logic is coming from: Cisco had a big problem with their old switch design and the native VLAN.
These switches don't care on over which VLAN you bring the untagged frames to the uC doing the ICMP Multicast and the simple IP stack with the Web UI...
devnull80s wrote:
There is just one issue. The IP I gave it which is on VLAN 11 takes 6 to 7 times longer than the other VLANs. Ports 3, 4, 5 connect to devices. I'm using this like an edge switch. So I average about 0.25ms from my core switch to the devices on port 3, 4, and 5 respectively. But I'm at about 2ms from my core switch to the Netgear switch. It makes no sense, I probably have something messed up somewhere but not sure where.
...as long as the frames are coming in with what can be interpreted as an IPv4 address. What does not work (or could cause some massive delays) is the attempt on bringing this management IP address over a trunked connection.
Can't see anything wrong with your config - except that you still fail to understand on how these Plus switches (at least those not implemented on a managed switch core, there are some...), their very simple IP stack is implemented.
devnull80s wrote:
Regardless as the edge devices have low latency and everything is just fine, no packet loss, loops or drops, I'm good as I got what I wanted. A Cisco trunk w/ 802.1q tagging and a native working.
Yes, this is what an unmanaged switch - this is what it is - (configured to some dot1q settings) can do nicely.
Feel free to remove the VLAN 1 from your unspecified Plus switch - as long as this is a classic Plus switch, not e.g. one of the more decent models with a managed core (where there is a config option for the management VLAN!).
Curious what you are "measuring" and what makes you think there must be some delay? The time to/from the uC where some famous engineers managed to implement a simple IP stack and ICMP Multicast handler for controlling the ports related to Multicast? This tiny uC does listen to -any- traffic flowing over this -unmanaged- switch most likely? And yes, the more traffic there is, the higher will the delay be. This is in no aspect something negative to these switches: It does not have an impact on the switching capabilities.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
