Re: Zyxel Switch Configuration Pdf Download
Sanora Ngueyn
To fill in some details: The switch is a GS1920-24HP with Boot Version V1.00 03/21/2014 and Firmware Version V4.50(AAOC.2) 02/27/2018. I think I have now tried everything I can think of to try and save the configuration. It makes no difference if I use config 1 or config 2. I have factory reset the device several times. Even just performing a reboot from the management console (using either config 1 or config 2 to boot to) makes the router lose the configuration completely.
I got this sorted out, finally! For reasons beyond my understanding, the switch only keeps configuration for "Config 1". If set to boot "Config 2", it always boots with factory default settings, despite having saved a modified "Config 2" (via the "Maintenance" page). I originally only upgraded "Config 2" to most recent ROM version, as my idea was to leave "Config 1" intact, using an older version. This was obviously not a good idea. I changed the router to boot "Config 1" instead and then reflashed it to most recent ROM. Both configs are now in the same version and "Config 1" is keeping the saved settings. All sorted out. Now it is time to start tinkering with the VLAN configs...
There is a configuration checking mechanism when the version gap between firmware image 1,2 is too big (For example: image 1 is 4.10 and image 2 is 4.50) and could lead to default setting to avoid mismatched configuration.
In cases that traffic should belimited or the connecting device to the switch requires a specialconfiguration, the default switch settings might not be enough. Due to these specificrequirements and also considering that different switches in your networktopology might have a different service purpose, the settings for switch portsare device-based and the admin needs to configure them aside from the switchsite-wide settings.
But hold on there, this is where Nebula comes in handy.Nebula is designed to ease management; multiple tools are in place to help manageyour switch ports in a more efficient way, such as tools that can configuremultiple switch ports all at once, or a mobile APP that makes the management ofthe essential port settings possible on the go.
Thepage lists all the switch ports from all the devices registered in the samesite, so you can simply select many ports, click on Edit button and configure them in an instant. Naturally,you can make use of the search filter options to quickly find and select thoseports that you could configure together.
Torestore, you only need to first select an existing backup from the table andthen select the switch(es) to apply the backup configuration. In the imagebelow, KC-2 is a new device that will replace the KC-1 (RMAed) and we want itto have exactly the same port settings.
Note that eachdevice can only have one backup point, so if your organization has 20 switches, you could have 20switch backups (one each). In the belowinstance you will find the second entry KC-1 has been greyed out since its backup already exists. In order to create anew backup for it, the old one has to be removed first.
The purpose of VLANs are to isolate one broadcast domain from another. If we would like hosts from different VLANs to communicate with each other, we have to set the switch to route traffic. The example shows how to configure the switch to route traffic across one VLAN to another.
Regarding the "default management" bit; it seems like it's used to decide where traffic like SNMP and other traffic originating from the switch itself should go (and unknown source). The first part of the description describes it a bit dependant on what you want to achieve.
I've tried multiple guides and various configurations, but I'm still unable to get VLAN "10" to function correctly. My current setup involves port 9 on my switch connected to an Ubuntu laptop configured to use DHCP. Strangely, it doesn't work when connected to VLAN "10," but it works perfectly when connected to another LAN switch port.
I suspect there might be an issue with either the DHCP server for VLAN "10" or a communication problem between the pfSense firewall and the switch. Despite my efforts, I haven't been able to resolve the problem.
I want to configure all ZyXEL switches with one port for administration only (port 48) with and SSH / HTTP access and the other ports just for switching. In other words the switch IP won't be accessible via ports 1-47 and to configure it I'll need to physically plug cable into port 48 (or via serial).
I started building this configuration by deleting default interface, changing device switch to switch only ports 1-8 (just for a test) and creating new interface for lan48 with static IP. I quickly realized that I can SSH / HTTP via port 48 but that switching ports don't work.
Thank you @_bernd , I can see in your configuration that you don't have an interface with protocol "none" (Unmanaged) so as Jow mentioned it makes sense that the netfid user is in your case an interface on a VLAN that has protocol DHCP / static.
Great idea since link-local is not routable. I was actually thinking about the same after I get comfortable with OpenWrt on a switch. But I was thinking about using unique local (fd00::/8) with a known "static" IPv6.
Is this just an OpenWrt configuration "thing" or does it mean that I can't use those VLANs inside the OS (for example with ip command)? I don't know... If those VLANs are really unusable then this is a more secure setup. If it's just an OpenWrt configuration "thing" then it doesn't matter...
Yes. Looking at =project/netifd.git;a=blob;f=bridge.c;hb=HEAD#l230 it seems the difference is whether netifd will add the vlan to the bridge itself in addition to the ports. Which is required if you want to use it for routing or anythng else in the OS. Otherwise it will only be switched within the bridge.
My ZyXEL (and you can test your D-Link DGS-1210-10) works OK for a single switch setup. Devices on access ports in different VLANs cannot speak to each other. But when I connect two switches via trunk, the VLAN isolation breaks and devices on VLAN 102 on my first switch can speak to devices on VLAN 103 on the second switch.
I'm not seeing this on my switches. Haven't actually tried to connect to of them directly, but I do use them to split VLAN trunks into both untagged access ports and trunk ports. I'm pretty sure I would notice any such failures immediately. But my switches are all RTL8380 based, like @_bernd 's DGS-1210-10. So I guess this could related to the RTL839x.
error you mentioned in the github issue. AFAIK, that shouldn't happen unless you send "a lot" of traffic to the CPU port. Not necessarily that much relative to what the switch ports can handle, but way more than normal switch management traffic.
A short time ago, I decided to install servers in a rack at my home. Although working very well, my 3Com managed was too much noisy for being at home. That is why I decided to change it for fanless switch. After some research, I finally chose a ZyXEL GS1910-24. It is a web-manageable gigabit switch. I chose the 24 ports version. This version has also 4 SFPs that replace 4 normal ports if enabled. I don't think I will ever need the SFPs, but it is nice to know that there are here if necessary. This switch has a lot of cool features, it supports IPV6, QoS, VLANs, filtering, RADIUS and so on.
The installation inside a rack is really easy. Each bracket is mounted with 4 screws onto the switch and then two screws are holding each bracket into place in the rack. Here is a picture of the rack:
The easiest way to configure the switch is to use the web configurator. By default, the switch IP is 192.168.1.1. As my router had the same IP, I had to disable it temporarily before changing the IP of the switch.
The web configuration is very complete, you can change absolutely everything from here. You have also access to a lot of monitoring tools from here. The most useful being of course the port monitoring interface:
I'm really impressed by this switch. The switch is highly configurable and seems to perfectly fit my need. I would totally recommend this switch for rack installation at home. You can also totally use it as a desktop switch if you needs for a big switch on your desktop too
The Zyxel Nebula NSW200-28P Cloud Managed PoE Switch is a 375-watt high-power-budget Layer-2 switch with 10 Gigabit uplinks designed to be managed completely from the Nebula cloud. The cloud-based management interface provides site-wide configuration and monitoring on all ports, which allows multiple switches to be configured at the same time with a single click over the Web.
The NSW200-28P brings many benefits of the cloud management systems, such as simplified configuration, easy management, site-wide visibility and real-time control for speedy branch network deployments into networks. Advanced settings such as user friendly ACL, VLAN-based QoS and PoE scheduling significantly improve the efficiency of network management.
The Zyxel Nebula Cloud Managed Switches support plug-and-play installation through remote provision with simple steps. The Zyxel Nebula NSW200-28P automatically downloads the current network configuration to the device and enables auto-provisioning without the need for on-site network professionals.
Rather than traditional management operations that require network administrators to configure each device separately with repetitive command lines, all Nebula Switches connected to the Nebula Control Center can be centrally managed with a single management interface. For better network management efficiency, switch settings made in the Nebula Control Center can automatically propagate to all connected Nebula switches.
User misspecifications are commonly seen in setting up ACL, reconfiguring VLAN/IP or other similar operations, and these may cause interruption to cloud connection. The Zyxel Nebula Cloud Managed Switches provide stable network environments by incorporating a mechanism that detects and prevents configuration that could potentially cause network disconnection between the switch and Nebula Control Center.
aa06259810