![]() ![]() This entry was posted in Networking and tagged alcatel lucent enterprise, alcatel-lucent, ale, aos, networking, omniswitch on Jby Patrick Terlisten. I will update this blog post with further information, as soon as I get them. ![]() I don’t know, if AOS 8 shows the same behaviour. I assume that this behaviour is caused by a bug. Make sure to leave the maintenance shell after the change, and don’t forget to restart the DHCP server. With higher privileges it’s no problem to edit the nf. Maintenance Shell commands should only be used by Alcatel-Lucent Enterprise personnel or under the direction of Alcatel-Lucent Enterprise.Įntering maintenance shell. In this case, the maintenance shell can help. In order to change the nf, we need an account with more privileges. So with your normal “admin” user, you don’t have the permission to write the file. “restart” is used to start or restart the DHCP server.īut how do you change the nf? Sure, simply use VI and edit it. Not quite… After starting the DHCP server, the owner of the nf changes from “admin” to “root”. The “enable” enables the DHCP server, but it’s not started. > cd /flash/switchĮdit the nf as necessary. Because you can run two or more switches as a virtual chassis, you can easily make the DHCP server role highly available. ![]() if you have no servers on premises, or you don’t want that a a non redundant firewall or router acts as DHCP server. But it’s pretty handy in some cases, e.g. The embedded DHCP server on AOS 7 and AOS 8 is a less known feature. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |