NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
managed switches
63 Topics"Advanced Engineering Certification - Wired Module 14": Multiple VLAN untagged???
Hello, in Netgear Academy, "Advanced Engineering Certification - Wired", Module 14, ports are untagged in VLAN 1; at 06:20, some ports are added untagged to VLAN 10, too. I could only replicate this when the port is in General Mode, not in Trunked or Access mode. I am sorry if this is a newbie question. From what I understand, * every port can sensefully only have one VLAN untagged, the rest has to be tagged, as untagged denotes the direct VLAN untagged packets can be sent to. Please correct me if I am wrong here. * "General" mode is kind of an "Auto" mode where the port itself decides whether it should act "Access" or "Trunked", so if I configure a port, I understand it that this configuration should work either in "Access" or in "Trunked, whichever is the actual mode I am working in? So, this behaviour opens a lot of questions, namely which is the "real" untagged VLAN, and how it could be configured as "untagged" in multiple VLAN. Note: As I am using devices I have at work that could be spared, I am using a M4250-10G2XF-PoE++, not the Netgear M4350-36X4V the learning video uses. However, regardless, I could replicate the behaviour of the switch in the tutorial video; and to me, there still is no sense in multiple VLAN being "untagged" for a single port. Could perhaps somebody point me to sources where I can research this, or help out here? Thanks, and greetings from the Franco-German borderlands, Yours Ralf77Views0likes2CommentsMost wanted: Friendly Port Names everywhere
On every management page, we want to see friendly port names aka port descriptions. so we dont have to remember on VLAN pages or other pages, which port number is important, instead we look for server1 or routerA or printer123.. Also for vlans the same.. always show a friendlich name instead of numbers only. very easy to include.. but nobody cares from netgear..59Views1like1CommentM4300 stack-port RX discarded packets, high mgmt latency
Hello, I have 4 M4300-28G-PoE+ (IP 192.168.101.4, fw version 12.0.19.23) in a stack ring, and one M4350-48G4XF (IP 192.168.101.5, fw 14.0.6.9), which is connected to the stack via 4 port LAG, each cord connected to one switch from the stack. The asic switching seems fine, I have <1ms latency on every device in the network, except for the stack management IP. Counters show RX discards on all but one stack cord (which is logically disconnected to prevent loop). The discards bleed steadily and more heavily if there are more devices in the network, though the data rate shows around 90Mb/s on each stack interface, which is nothing, when the stack interfaces show 10Gbit links. There are no errors, just RX discards (show stack-port counters all) as if the CPU buffer can't handle it. The stack management IP also has higher ping, 1-2ms with up to 80ms peaks. Those peaks are probably correlated with CPU usage spikes, normally sitting around 15 % on the Mgmt Sw, going well over 50% and even up to 80% (with agentMain, tRpcsrv.01000 and syncdb eating up the most at those peaks). There is VuWall AV system populating most of the switch ports. I have igmp-plus set up and igmpsnooping, with querier being the switch 192.168.101.4 (snoopTask eats almost nothing). The secondary switch 101.5 has set igmp mrouter 101 on the LAG and querier set to 101.4. Therefore IGMP should be correctly configured. I tried: Set all recommended settings for Netgear by VuWall. Upgraded FW from 12.0.19.21 to 12.0.19.23. Different presets in switch GUI. Disconnecting 3 out of 4 LAG ports. port-channel load-balance 3 and 6 and I have port-channel local-preference on that LAG, on both stack and M4350 I guess discarding rx packets on stack interfaces isn't a feature. Only the stack interface is having this high latency and sometimes our video streams freeze (this can be totally unrelated to the switch issue though) Disconnecting almost all devices, problems weren't as severe but persisted, which seems to me more like a broadcast storm/topology problem, rather than low bandwith problem. Any ideas of what could have been wrong?61Views0likes0CommentsGS108Ev3 refuses to connect
I have 4 GS108Ev3 switches. As they are all configured and working well I don't need to administer them often. Today I wanted to login to them - and can't. All 4 refuse to connect when I access the admin screen (http://192.168.0.XXX). I can ping them all. Netgear Discovery Tool v2.0.7 finds them all, shows the firmware is v2.06.24 but when I click Admin Page, a new tab opens followed by: This site can’t be reached 192.168.0.231 refused to connect. Try: Checking the connection Checking the proxy and the firewall ERR_CONNECTION_REFUSED When I try the ProSafe Discovery Tool and ProSafe Plus Utility v2.7.8, they also discover the switches but report that the admin feature is disabled on the switches. I have factory reset the switches. They pick up an IP address from the DHCP server after the reset, and respond to pings but still refuse admin web connection. I've seen some threads about MTU length required to be 1500 and it is. I tried changing that - it didn't work so I changed it back and it still didn't work! This is on a flat network (no VLANs etc), from Windows 11 and Chrome. I have a lot of web-managed devices that all work but these switches don't and I can't figure out why! How do I get access to the admin screen for these switches, please?SolvedThe SNMP service is occasionally unavailable
Hi all, My customer is currently facing occasional SNMP unavailability. I have checked uptime ot the switch and found that CPU and memory are normal. After reset snmp, the snmp service resumed. However, after a period of time, this issue will occur again, and it is still unclear about the time interval and trggering conditions, which may be a software bug. May I ask if anyone else has encountered the same problem and has a solution? Thank you. Below information is the switch parameters: [Product Name] NETGEAR 48-Port Gigabit PoE+ Smart Managed Pro Switch with 4 SFP Ports (GS752TPv2) [Model Name] GS752TPv2 [Boot Version] 1.0.0.5 [Software Version] 6.0.3.3M4300 Switch Stack Upgrade Path
Hi, I have inherited a M4300 stack cluster of 3 24 port switches, which are having issues where one of the stack seems to crash/latchup & is unresponsive They are running old software 12.9.0.3 Now whilst i would love to upgrade the firmware to latest 12.0.19.21 im finding conflicting information, if we can go from 12.9.0.3 -> 12.0.19.21 or if we need to stagger with something like this: [v12.0.9.3] ──> [v12.0.11.16] ──> [v12.0.17.6] ──> [v12.0.19.21 (Latest)] Reasons i see for stagger is 17.6X breaks admin passwords & possible 15.8+ fixes that looking for clarification from support or other users, the correct upgrade path. currently have no access to usb console, & fully remote from these devices..55Views0likes0CommentsMemory leak M4300 12.0.19.21
Hello We upgraded to 12.0.19.21 in hope that if fixes random crashes of our M4300 stacks, we now observer memory leak in SCRIPT process. We took output of "show process memory" in hourly intervals on friday and extra output on Monday morning Time SCRIPT CurrentAllocated Δ from baseline 11:15 4,527,712 baseline 12:15 4,539,920 +12,208 13:15 4,553,808 +26,096 14:30 4,571,840 +44,128 15:20 4,582,144 +54,432 3 days later 10:15 5,480,944 +953,232 There is slow leak and no memory is Freed. Is there a way to restart/disable this single process to stop switches from crashing eventually? Regards246Views0likes1Comment