The embedded DHCP server on AOS 7 and AOS 8 is a less known feature. But it’s pretty handy in some cases, e.g. if you have no servers on premises, or you don’t want that a a non redundant firewall or router acts as DHCP server. Because you can run two or more switches as a virtual chassis, you can easily make the DHCP server role highly available. Configuring the DHCP server

Manually assigning ports to VLANs can be a time consuming and error prone process. Depending on the size of the network, there is a point where it doesn’t make sense to do this manually. Especially in SMB networks, VLANs are assigned manually, because the effort of automating the VLAN assignment exceeds the effort for manually assigning VLANs. Those environments are often very static. I know many SMB networks where VLAN have not been addressed for a long time.

Today I saw an interesting behaviour of two Alcatel-Lucent Enterprise OmniSwitch 6450. Both switches has been configured as a stack, but one of the switches showed a flashing ID after the startup, and the stack was not formed. While I checked the logs and the status of the stack, I noticed that the slot number was incorrect. Furthermore the status showed “INC-LIC”. -> show stack topology Link A Link A Link B Link B NI Role State Saved Link A Remote Remote Link B Remote Remote Slot State NI Port State NI Port —-+———–+——–+——+——-+——-+——-+——-+——-+——- 1 PRIMARY RUNNING 1 UP 1001 StackB DOWN 0 0 1001 PASS-THRU INC-LIC 2 DOWN 0 0 UP 1 StackA