Mediant 2000 Initialization & Configuration Files; Mediant 2000 Startup; Boot Firmware & Operational Firmware - AudioCodes Mediant 2000 User Manual

User's Manual
6 Mediant 2000 Initialization &
Configuration Files
This section describes the Configuration Options and Initialization Procedures for the
Mediant 2000. It includes:
Boot Firmware & Operational Firmware (refer to 'Boot Firmware & Operational
Firmware' below)
Startup Process (refer to 'Mediant 2000 Startup' below)
BootP/DHCP (refer to 'Using BootP/DHCP' on page 59)
Configuration Parameters and Files (refer to 'Configuration Parameters and Files'
on page 64)
Auxiliary Files (refer to the 'Appendix - Auxiliary Files' on page 385)
6.1

Mediant 2000 Startup

The Mediant 2000's startup process begins when the Mediant 2000 is reset. The
startup process ends when the operational firmware is running. The startup process
includes how the Mediant 2000 obtains its IP parameters, firmware and configuration
files.
The Mediant 2000 is reset when one of the following scenarios occurs:
1. The Mediant 2000 is manually reset.
2. acOpenRemoteBoard() is called with RemoteOpenBoardOperationMode set to
Full Configuration Mode (valid for VoPLib API users only).
3. acOpenBoard is called; VoPLib users who control the Mediant 2000 via PCI call
this API to initialize the Mediant 2000 (valid for VoPLib API users only).
4. acResetRemoteBoard() is called in the VoPLib API (valid for VoPLib API users
only).
5. There is a device irregularity.
6. Users perform a reset in the Embedded Web Server GUI or SNMP manager.
7. The flow chart in the figure below illustrates the process that occurs in scenarios
1-6.
6.2 Boot Firmware & Operational Firmware
The Mediant 2000 runs two distinct software programs: Boot firmware and operational
firmware.
Boot firmware - Boot firmware (also known as flash software) resides in the
Mediant 2000's non-volatile memory. When the Mediant 2000 is reset, Boot
firmware is initialized and the operational software is loaded into the SDRAM from
the PCI host, a TFTP server or integral non-volatile memory. Boot firmware is
also responsible for obtaining the Mediant 2000's IP parameters and ini file name
(used to obtain the Mediant 2000's configuration parameters) via integral BootP
or DHCP clients. The Boot firmware version can be viewed on the Embedded
Version 5.0
6. Mediant 2000 Initialization & Configuration Files
57 June 2006