Description: This object of type MasterState indicates the state of the Master Controller's system integration and should always be properlySet(7).

Immediately after the Master Controllers IP address has been assigned to the object aimosMasterAddress, the SNMP Agent tries to reach the Master Controller in order to query its GUID. Here, aimosMasterState has the value performGUIDRequest(2).

Afterwards, the network structure as well as all current information is queried. During this process aimosMasterState has the value performNetInfoRequest(5).

After the query the value changes to properlySet(7). Moreover, the tables aimosSubRackTable, aimosRemoteUnitTable, aimosGSMNSOTable and aimosUMTSNSOTable have one entry for each of the network elements found. Each of these tables (like the aimosMasterUnitTable) have one object referring to the hardware version specific tables (aimosMasterOID, aimosSubRackOID, aimosRemoteOID, etc.). These, too, have one entry for each of the network elements found after a successful query.

It is possible that one of the queries mentioned before fails:

. If the GUID query was not successful the value of aimosMasterState changes from performGUIDRequest(2) to missingGUID(3). For this, there may be various reasons: . One might be that the Master Controller cannot be reached under the IP address and Port Number given by aimosMasterAddress. In such a case, the A.I.M.O.S. SNMP Agent answers the allocation to aimosMasterAddress with SNMP ErrorStatus resourceUnavailable(13). The error will be corrected by correcting the IP address and/or Port in aimosMasterAddress.

. Another reason may be that the User in aimosMasterLoginUserName or the password in aimosMasterLoginPassword are wrong. Then, the A.I.M.O.S. SNMP Agent returns SNMP ErrorStatus noAccess(6). The error is corrected by assigning the correct Username to aimosMasterLoginUserName and/or the correct password to aimosMasterLoginPassword. Such an error may be prevented in advance by adjusting the pre-settings of these two objects. This can be done via the two objects aimosInitiallyMasterLoginUserName and aimosInitiallyMasterLoginPassword. Afterwards, a new GUID query must be made by setting aimosMasterState to requestGUID(1).

. It is also possible that the Master Controller is not ready. This error can be corrected by starting the Master Controller or by making it available in the network (Firewall ?). Afterwards, a new GUID query must be made by setting aimosMasterState to requestGUID(1).

. When a query of the network structure and/or status information failed, the value of aimosMasterState changes from performNetInfoRequest(5) to missingNetInfo(6). After correcting the cause of the failure another try to query the network structure must be made by setting aimosMasterState to requestNetInfo(4).

These steps must be repeated until aimosMasterState is set to properlySet(7). Sometimes it might help to delete Master Controller and create it anew.

This Leaf indicates, if the master unit is properly configured.

If the GUID is missing, this Leaf contains missingGUID(3). You can assign requestGUID(1) to aimosMasterState, in order to inquire the GUID at the CONTROLLER. During the inquiry aimosMasterState's value changes to performGUIDRequest(2). If the inquiry is done, the value changes to - missingGUID(3) if the request was not successful (that means, the GUID is still unknown) - missingNetInfo(6) if the master controllers network is unknown - missingCommParams(8) if aimosMasterCommunicationID is not set - properlySet(9) if the master controllers - GUID (aimosMasterGUID) is knownn - network is known - Communication ID (aimosMasterCommunicationID) is set

If the master controllers network is unknown (missingNetInfo(6)), set aimosMasterState to requestNetInfo(4). Until this command is recognized by the master controller aimosMasterState is performNetInfoRequest(5).

If the CommunicationID is unknown (missingCommParams(8)), set aimosMasterCommunicationID to an appropriate value. Until this command is recognized by the master controller aimosMasterState is performSetCommParams(7).

Each master controller should have the value properlySet(9) here.

Changes, which are made here, affect all organizations. That's why TelCo's are not allowed to make any changes here.