NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
S3300
5 Topics
DHCP not traversing switch Part 2
Hi, Unfortunatly I have a follow up issue to my last issue here. This time however only the Netgear is involved. I have performed various tests already and it boild down to that the S3300 does not seem to pass on DHCP traffic at all at the moment. Test setup: I have a box A on Port 12 and a box B on Port 13. On B there is a dhcp server active and tcpdump on 67/68 udp. I start a dhcp request on box a connected via Netgear switch - I don't see any requests. On Box A I can see the requests being sent out with wireshark, but o/c no replies. A static IP on Box A results ins perfectly fine communication, no issues. Now I used another switch (cheap 8 port) and attached box A and B to it and with that switch DHCP is working fine, tcpdump listing everything. Both boxes are on VLAN 1, no security features active, no helper, relay or anything. S3300 (stack of 2) is on latest FW (6.6.4.7) but I think the issue was present before. I noticed weird behaviour for about 2 weeks but can't really tell what I could have changed to cause this :( Lost again :(Solved17KViews0likes17Comments
S3300 inter-VLAN Routing Issue
I have just purchase an S3300-28X and S3300-52X and am getting to grips with all the features. Most features seem pretty straight forward so far, but I'm having real issues setting up inter-VLAN routing. I've been unsuccessfully banging my head against the wall for a few days now, so hopefully someone here will be able to shine some light on where I'm going wrong. I've factory-reset the S3300-28X and setup a simple configuration for testing: VLAN10 Interface IP: 10.0.10.1 Subnet Mask: 255.255.255.0 VLAN20 Interface IP: 10.0.20.1 Subnet Mask: 255.255.255.0 Port 1/g14 PVID: 10 VLAN Member: 10 VLAN Tag: None Port 1/g16 PVID: 20 VLAN Member: 20 VLAN Tag: None I initially setup the VLANs with the routing wizard, selecting the appropriate tags as untagged. After checking the PVID configuration I connected a workstation to each port with the following manual IP settings: Workstation (1/g14) IP Address: 10.0.10.123 Subnet Mask: 255.255.255.0 Default Gateway: 10.0.10.1 Workstation (1/g16) IP Address: 10.0.20.123 Subnet Mask: 255.255.255.0 Default Gateway: 10.0.20.1 Each workstation can ping default gateways on either VLAN, but the workstations cannot ping one-another. I feel like I've tried every possible setting in the PVID Configuration sections but nothing seems to work. So, could someone please suggest where I've gone wrong or what I should try next? Thanks!Solved4.9KViews0likes3CommentsStacking on S3300
I've been reading as much documentation as I can find, but I just can seem to get stacking to work. The Hardware Installation document states that stacking will automatically configure itself, but it doesn't seem to be working for me. I have two S3300 switches connected to each other over two 10Gbase-T connections. Both connections are up and stable showing no errors and traffic can pass across the switches. However, I can never see the other switch when I'm looking at the stack configuration. Can someone point me in a direction as to where I need to look?SolvedSame VLAN on two switches (S3300's) will not communicate
Hi, probably its just a stupidity issue on my side but I can't get this to work. I am trying to get two boxes to communicate over two switches using a particular vlan. This is actually the simplified solution attempt for a more complex issue but can't even get this to work:( I've been following https://kb.netgear.com/11673/How-do-I-setup-a-VLAN-trunk-link-between-two-NETGEAR-switches this guide. Test Setup : 2x S3300 (one on 6.6.14, one one .17) connected via Trunk 1x ESX box with a vSwitch with multiple vmknics, one of these on the relvant vlan (6) 1x Windows Box (no VLAN setup on nic) Switch A (stacked with another S3300) Interface PVID VLAN Member VLAN Tag Acceptable Frame Untagged VLANs Tagged VLANs Comment 2/g14 6 6 None Admit All 6 None TestPort Local Switch 2/xg25 1 1,6 6 Admit All 1 6 Trunk Link 2/xg28 1 1,5-9,18,19 5-9,18,19 Admit All 1 5-9,18,19 ESX Box ESX box with a vmknic on VLAN 6 on Switch A, Trunk configured on 25 according to KB. 14 is a testport - if I connect the Windows box to this port the connection works (- - > Intra Switch VLAN is fine) Switch B Interface PVID VLAN Member VLAN Tag Acceptable Frame Untagged VLANs Tagged VLANs Comment 1/g22 6 6 None Admit All 6 None Windows Box 1/g23 1 1,6 6 Admit All 1 6 Trunk Link If the Windows Box is connected to B/22 I can't communicate with it and I can't see why not I have tried a lot of things already, setting up VLAN IPs for example on both switches to check whether its a port issue or not. But its always the same pattern - everything local is working fine but as soon as the traffic has to flow to the other switch its not. Everything on VLAN 1 is working fine o/c, just not on another VLAN. Looking for any kind of clue, totally lost :( Thanks for reading.SolvedNMS300 and S3300
Dear Community, I have installed NMS300 (latest) and discovered some devices, also created new device credentials. It is working so far except one issue, maybe it is config related. My S3300-52X-PoE+ is detected in Device Discovery but not added to inventory. Current device status is "Some stack member is empty" stated in NMS Device Discovery Results. Device name, IP address and model is displayed also. Is it possible to add devices only in "clean" state? It is not mentioned in the manual. Thanks in advance, RaphaelSolved