NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
M4300
9 TopicsM4300 (GSM4352PS V1) : can't get kernel image
Hi Netgear Users and Administrators, I have a little problem with my M4300 GSM4352PS V1. There's possibility that image2 is broken. Device is actually booting from image2. On the console I see that can't boot from image and i see "ERROR: can't get kernel image". I supose that the image1 is a good conditional. Best Redgards Pawel2.7KViews0likes1CommentGlobal L2 Loop Protection question on M4300-52G-PoE+
I was testing the L2 Loop Protection capability of my M4300-52G-PoE+ stack by connecting ports 4/0/1 and 4/0/5 together, and the protection seemed to work great, putting port 4/0/1 in a D-Disable state. My question is, after correcting such a state by disconnecting the loop, how do I go about taking the port out of a D-Disable state and putting it back into an Enable state? I see no option to reenable the port via the browser GUI under Switching -> L2 Loop Protection and I'd like to know if the only way to renable the port is to completely reboot the entire stack? Thanks, TedWSolved7.8KViews0likes2CommentsDual DHCP helper-address in startup-config
I'm replacing my M5300 stack with a new M4300 stack and I had a question about a routing command in each of the VLANs on my old M5300 stack. My M5300 was configured by Netgear contracted support when we first purchased it, and as I scroll through the startup-config file from the M5300 I see a few commands for each of the VLANs that I have questions about: Question 1: In the "interface vlan" commands listed in the M5300's startup-config (see example below) I see the command ip helper-address 10.1.0.20 dhcp and I was wondering how I add this option via the browser interface on my new M4300 stack, or can it only be done by modifying and uploading a new startup-config to my M4300 stack? interface vlan 2 routing ip address 10.1.1.1 255.255.255.0 ip helper-address 10.1.0.20 dhcp exit interface vlan 3 routing ip address 10.1.2.1 255.255.255.0 ip helper-address 10.1.0.20 dhcp exit interface vlan 4 routing ip address 10.1.11.1 255.255.255.0 ip helper-address 10.1.0.20 dhcp exit Question 2: I also noticed that the M5300 stack's startup-config had individual interfaces that were configured to include and exclude (see below). Every interface that was untagged for the default VLAN 1 did not have these "include" and "exclude" statements, but All of the ports configured for untagged VLAN 3 and VLAN 4 did. Can someone clue me in on what these commands might be for, and if they can also be added through the browser interface on my new M4300 stack? Computers on VLAN 3 and VLAN 4 can still access servers on VLAN 1, so I'm not sure what the vlan participation exclude 1 is doing. interface 1/0/19 voice vlan 2 auto-voip protocol-based auto-voip oui-based vlan pvid 3 vlan participation exclude 1 vlan participation include 3 exit interface 3/0/47 voice vlan 2 auto-voip protocol-based auto-voip oui-based vlan pvid 4 vlan participation exclude 1 vlan participation include 4 exit Any help with my above questions would be greatly appreciated. Thanks, TedWSolved6KViews0likes3CommentsM4300-28G-POE+: LAG + Port Mirroring results in high number of Transmit Packet Discards
Hello, I have an issue with a M4300-28G-POE+ model. The setup I have is quite simple: * 2x1 Gbit links are used which are batched into a LAG * The LAG is mirrored to a probe port. * Jumbo packets are configured. When I generate network traffic on the two links, the 10Gbit uplink receives each of the packets of the LAG of course, but when I am listening on the probe port, ~40% of the packets are dropped. In the Detailed Port Statistics I can see the following: Total Packets Transmitted Successfully: 161364755 Transmit Packets Discarded: 73094691 This example was taken from a scenario when the overall network traffic on the LAG was ~170Mbit/s and on the probe port I measured ~100Mbit/s I've tried to change the configuration based on hints in the Netgear Community threads (like this, since the observation is quite similar: https://community.netgear.com/t5/Smart-Plus-Click-Switches/GS724T-High-number-of-Transmit-Packet-Errors/m-p/393029#M257). When I am not using Jumbo packets but LAG, I observe the same issue. I've updated the firmware to 12.0.2.15 but the issue still occurs on my test environment. Are there any suggestions how to deal with this problem? Best, I.5.7KViews0likes5CommentsTransceiver sonnet SFP+ SR compatible M4300
Hi, i want to know if this SFP+ Short-Range transceiver: Sonnet G10E-SFP-SR https://www.sonnetstore.com/collections/network-adapters/products/sfpmodule-shortrange is compatible with the Switch: Netgear M4300-12x12F I would like to connect the sfp+ transceiver directly in 10GBase-X SFP+ ports of netgear switch replacing AXM761 Does anyone knows if it is compatible and reliable? some other better module? thank u! regards to community7.9KViews0likes5CommentsM4300-24X24F VLAN's, ACL and separation
Good day all, I have found an article, but as soon as I try to set the rules according to the article I lose all connection to the switch and need to undo the ACL using the console cable... https://kb.netgear.com/30818/How-to-configure-routing-VLANs-on-a-NETGEAR-managed-switch-with-shared-internet-access I have a stack of 2x M4300-24X24F, which contains several VLAN's: 1, 20, 90, 91 and 101 Now all theses VLAN,s should not be able to route to eachother, except for VLAN 20 to a few hosts in VLAN 1, and theses few hosts in VLAN 1 to all of VLAN 20. So what is the best way to configure this? Or did I really make a big mistake and should I have gone for HP instead?? (At least on our old HP switch routing is opt-IN instead of opt-OUT?) Sorry to say, but even budget TP-LINK has a more intuitive interface...7.2KViews0likes8CommentsM4300-28G ip management port fails after restart in a stacked configuration.
Hello, we have a stacked configuration from 6 times a M4300-28G switch (firmware version 12.0.2.9), the stack up and running. The ip management port (IP4) is set to vlan 1 and via the web interface all settings en configurations can be seen. After a restart of the stack (all the swithes go down) the web interface fails and de ip address of the ip management port can't be accessed any more. After setting the ip address from the ip management port again (via CLI command line interface port) the ip management port is available again. What can be the reason that the ip management port isn't available after a restart? best regards, Jos LaanSolved7.9KViews0likes14Comments