User's Manual

Booting from the SD cards
When being powered up, the control unit looks for a valid .bin binary file to load. It does this
using the possible source below in the order shown, skipping to the next source if the file is
not present or is not valid.
1. System SD card primary folder.
2. The control unit's own internal non-volatile memory. Once a system has been
installed, it uses its non-volatile memory to keep copies of the configuration and
system binary files it is using. These can be used to restore operation during a
system reboot. Note that though a system can boot from non-volatile memory, a
System SD card must still be present for correct system operation.
3. System SD card backup folder.
4. Optional SD card primary folder.
5. Optional SD card backup folder.
6. If no file is found, the control unit will fallback to making BOOTP requests to the
network. Manager can respond to the BOOTP request. See
About erasing the
operational firmware on page 247 for more information.
Once a valid .bin file is found, the control unit loads that firmware. The source from which the
control unit binary file was loaded is then used to load further files.
Configuration file loading
After the system firmware files are installed, a configuration file must be installed on the control
unit.
• If the control unit booted using binary files from an SD card location, it looks for a valid
configuration file in the same location.
• If a configuration file is present and valid, it is loaded.
If a configuration file is present but is not valid, load the configuration copy in its non-
volatile memory if present. Otherwise, the control unit will have a default
configuration.
• If a configuration file is not present, use the non-volatile memory copy unless the
reboot is as a result of a default system command.
• If the control unit booted using binary files from its non-volatile memory, it will also load
the configuration copy from that location.
• It will indicate a boot alarm (see Boot alarms below).
It will attempt to restore the firmware file in the System SD card /primary folder using
the copy in its non-volatile memory.
SD card management
256 Implementing the Avaya B5800 Branch Gateway November 2011
Comments? infodev@avaya.com