NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
exocomp
Jan 29, 2017Aspirant
M4100-26G changes VLAN membership after reboot
Hi there, hoping someone can help or confirm this is an issue. I recently got my first M4100-26G and updated to the latest firmware 10.0.2.20, the unit and features work as expected however when I s...
LaurentMa
Jan 29, 2017NETGEAR Expert
Hi exocomp
Welcome to the Community!
I can confirm we don't show outstanding issues with firmware 10.0.2.20.
It is normal the time resets back to the default when you reboot, only SNTP time servers and time zone configuration are kept in startup-config, not the latest time before reset. After reboot, SNTP sync will happen and your M4100-26G will show correct time again.
Ports VLAN configuration should be kept intact after a reboot, provided the configuration was saved. Are you sure you actually save the configuration (so basically write the running-config into startup-config)? Are you using Web interface (GUI) or the command line (CLI)?
- Web GUI: Please refer to the M4100 Web User Manual page 14, table 1. On each page, there is a button APPLY. This APPLY button sends the updated configuration to the switch. Configuration changes take effect immediately, but in fact you are writing into the running-config. Running-config is volatile until you SAVE it into startup-config. To do that, please refer to page 405 and select Maintenance -> Save Config -> Save Configuration.
- CLI: Please refer to the M4100 CLI Manual page 371. The command save will permanently write running-config into NVRAM, in fact into the startup-config file.
(M4100) >enable
(M4100) #save
Let us know if this helps!
Regards,
exocomp
Jan 29, 2017Aspirant
To add to my previous response. Here is an example:
Before Reboot
After Reboot
NOTE: See how VLAN 1 and 50 were added, why did this happen ?
Thanks,
J
- LaurentMaJan 30, 2017NETGEAR Expert
Hi exocomp
There must be conflicting configuration between Switching\VLAN\Advanced\VLAN Trunking Configuration you are showing in screenshots above, and Switching\VLAN\Advanced\VLAN Membership next page in the menu on the left. VLAN Membership data most likely took precedence when you save your configuration.
You can download your configuration file in Maintenance\Download to control the running-config: for interface 0/1, you should look at the switchport commands (Trunk or General) or the conflictual combination of both. In order to fix this, I would recommend you clear all configuration in Switching\VLAN\Advanced\VLAN Membership?
Please let me know. If you want, you can also copy and paste the VLAN/port information from your dowloaded configuation file in this thread?
Regards,
- exocompJan 30, 2017Aspirant
Hi Laurent,
>>You can download your configuration file in Maintenance\Download
In order for me to get the switch configuration file I have to go to the upload section not download, it is kind of confusing, so I guess you meant Configuration/Upload not download. Anyway, as far as I can tell VLAN membership is setup correctly, please review below and let me know.
Here is the config file:
!Current Configuration: ! !System Description "M4100-26G ProSafe 24-port Gigabit L2+ Intelligent Edge Managed Switch, 10.0.2.20, B1.0.1.1" !System Software Version "10.0.2.20" !System Up Time "0 days 0 hrs 17 mins 7 secs" !Additional Packages QOS,IPv6 Management,Routing !Current SNTP Synchronized Time: SNTP Client Mode Is Disabled ! vlan database vlan 50,100,200,300 vlan routing 1 1 vlan association subnet 10.0.0.0 255.255.255.0 300 vlan association subnet 172.16.0.0 255.255.255.0 100 vlan association subnet 172.16.1.0 255.255.255.0 200 exit configure no sntp client mode time-range line console exit line telnet exit line ssh exit ! interface 0/1 switchport mode trunk switchport trunk allowed vlan 1,50,100,200,300 vlan acceptframe vlanonly vlan ingressfilter exit interface 0/2 exit interface 0/3 switchport mode trunk switchport trunk allowed vlan 1,50,100,200,300 vlan acceptframe vlanonly vlan ingressfilter vlan participation auto 1 vlan participation include 100,200,300 vlan tagging 100,200,300 exit interface 0/4 exit interface 0/5 vlan participation auto 1 vlan participation include 100,200,300 vlan tagging 100,200,300 exit interface 0/6 exit interface 0/7 vlan pvid 50 vlan ingressfilter vlan participation auto 1 vlan participation include 50 vlan tagging 50 exit interface 0/8 exit interface 0/9 exit interface 0/10 exit interface 0/11 exit interface 0/12 exit interface 0/13 exit interface 0/14 exit interface 0/15 exit interface 0/16 exit interface 0/17 exit interface 0/18 exit interface 0/19 exit interface 0/20 exit interface 0/21 exit interface 0/22 exit interface 0/23 exit interface 0/24 exit interface 0/25 exit interface 0/26 exit interface lag 1 exit interface lag 2 exit interface lag 3 exit interface lag 4 exit interface lag 5 exit interface lag 6 exit interface lag 7 exit interface lag 8 exit interface lag 9 exit interface lag 10 exit interface lag 11 exit interface lag 12 exit interface vlan 1 routing ip address dhcp exit exit
I can't spot what I'm doing wrong so appreciate if you can take a look.
Thanks,
J
- LaurentMaJan 31, 2017NETGEAR Expert
Yes right, Maintenance\Upload\HTTP File Upload\Text Configuration in order to let you download the configuration file, from the switch standpoint.
Thank you for your patience here, and your screenshots alongside text configuration show the issue you're having: there is conflicting port VLAN configuration on some ports. To me this is due to the fact you used Switching\VLAN\Advanced\VLAN Trunking Configuration for some configuration, and Switching\VLAN\Advanced\VLAN Membership or Switching\VLAN\Advanced\Port PVID Configuration for some other configuration. For instance on your Port 1, you said earlier you were seeing VLAN1 and VLAN50 added to the Trunk Allowed VLANs in Switching\VLAN\Advanced\VLAN Trunking Configuration after reboot. I think VLAN1 was back because VLAN1 was still kept as (default) Native VLAN in Switching\VLAN\Advanced\VLAN Trunking Configuration. If the port Native VLAN for untagged traffic is VLAN1, VLAN1 got to be added to the trunk. For VLAN50, although I can't see it in your previous screenshots, this was likely because of conflicting configuration at that time in Switching\VLAN\Advanced\VLAN Membership. Other example, I see conflicting utilization of Port PVID and Port Tagging for your port 7 (interface 0/7) in your configuration file.
I would recommend we only configure port VLANs "Access Ports, Trunk Ports and Native VLANs" in:
- Switching\VLAN\Advanced\VLAN Trunking Configuration
or, alternatively, not simultaneously, we configure ports VLANs "Untag modes, Tag modes and PVIDs" in:
- Switching\VLAN\Advanced\VLAN Membership, and Switching\VLAN\Advanced\Port PVID Configuration
The configuration file above has mixed up configurations, so we should restart from a clean sheet. Maybe you can perform a factory-default in Maintenance\Reset\Factory Default for this. Then only use one of these methods. One think to keep in mind: VLAN1 is enabled by default on all ports (Access Ports, or untagged mode), so it must be removed from trunks and other access ports when necessary.
Based on my understanding of what you want to achieve (please keep me honest here):
- Ports 1, 5 and 7 in trunk mode with only tagged VLANs 100,200,300 allowed and no native VLAN for untagged traffic
- Ports 2, 3, 4 and 6 untouched (so in access mode with untagged VLAN 1)
- Port 7 in access mode with untagged VLAN 50
Here's the configuration for both modes. Of course, you can use local console (CLI) as well.
- Switching\VLAN\Advanced\VLAN Trunking Configuration
interface 0/1 switchport mode trunk switchport trunk allowed vlan 100,200,300 exit interface 0/2 exit interface 0/3 switchport mode trunk switchport trunk allowed vlan 100,200,300 exit interface 0/4 exit interface 0/5 switchport mode trunk switchport trunk allowed vlan 100,200,300 exit interface 0/6 exit interface 0/7 switchport mode access
switchport access vlan 50 exit- Switching\VLAN\Advanced\VLAN Membership, and Switching\VLAN\Advanced\Port PVID Configuration
interface 0/1 vlan participation exclude 1
vlan participation include 100,200,300 vlan tagging 100,200,300
vlan acceptframe vlanonly exit interface 0/2 exit interface 0/3 vlan participation exclude 1
vlan participation include 100,200,300
vlan tagging 100,200,300
vlan acceptframe vlanonly exit interface 0/4 exit interface 0/5 vlan participation exclude 1
vlan participation include 100,200,300
vlan tagging 100,200,300
vlan acceptframe vlanonly interface 0/6 exit interface 0/7 vlan pvid 50 vlan participation exclude 1
vlan participation include 50 exitRegards,
Related Content
NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!