From Wanos Wiki
(→Out of band management) |
|||
| Line 1: | Line 1: | ||
| + | <font size=5> Document migrated. An updated [http://wanos.co/docs/docs/wanos-admin-guide/optional-configuration/out-of-band-management/ Out of Band Management] can be found in the http://wanos.co/docs Wanos Documentation site] </font> | ||
| + | <font color=#dddddd> | ||
| + | |||
==Out of band management== | ==Out of band management== | ||
| Line 20: | Line 23: | ||
route add -net 192.0.0.0 netmask 255.0.0.0 gw 192.168.2.1 | route add -net 192.0.0.0 netmask 255.0.0.0 gw 192.168.2.1 | ||
</pre> | </pre> | ||
| + | |||
| + | </font> | ||
Revision as of 18:39, 10 February 2017
Document migrated. An updated Out of Band Management can be found in the http://wanos.co/docs Wanos Documentation site]
Out of band management
You can enable out of band management by adding the following information at the end of bootsync.sh
Open the bootsync.sh file by:
vi /opt/bootsync.sh
Add the following information to the of the script:
### Out of band management ifconfig eth2 192.168.2.200 netmask 255.255.255.0 broadcast 192.168.2.255 up
This gives, the third NIC in this example, the management address of 192.168.2.200.
A default route will clash with the in-path address, but a specific route can be added to enable the out of band management from the whole 192.0.0.0/8 network:
route add -net 192.0.0.0 netmask 255.0.0.0 gw 192.168.2.1