Product Description

nanoBTS Product Description Software Specification

5.4.3 Reset Reason

If the BTS undergoes a fatal software reset of any sort, a byte indicating the "reset reason"

is stored in memory before the reset is initiated. During the reset procedure, this "reset

reason" byte is read out, and sent to the management system as a Failure Event Report.

5.5 Configuration

5.5.1 DHCP

The BTS supports the ip.access specific implementation of DHCP.

5.5.2 Fallback OML Link

The BTS supports a fallback link to its BSC, by configuring the "Primary OML Fallback

Address" and "Port" and the associated "Fallback Timeout". If the fallback address and

port are configured, then the BTS will behave as follows

• On startup, the primary, non-fallback address is repeatedly tried, until either

connection succeeds or the fallback timer expires

• If the fallback timer expires, then the fallback address is repeatedly tried, until either

connection succeeds or the fallback timer expires

• If the fallback timer expires, then the non-fallback address is tried again, and so on

If the fallback timer is zero (its default value) then the non-fallback and fallback addresses

are tried alternately.

If the fallback address and port are unconfigured, then the non-fallback address is tried

repeatedly for ever.

5.5.3 Management Model and Attributes

The management model is fully defined in [REF_110]. An example class tree for the

1800MHz EDGE/AMR BTS is given below.