AIMOS: View SNMP OID List / Download MIB

A textual description of the entity. This value should include the full name and version identification of the system's hardware type, software operating-system, and networking software.

The vendor's authoritative identification of the network management subsystem contained in the entity. This value is allocated within the SMI enterprises subtree (1.3.6.1.4.1) and provides an easy and unambiguous means for determining `what kind of box' is being managed. For example, if vendor `Flintstones, Inc.' was assigned the subtree 1.3.6.1.4.1.4242, it could assign the identifier 1.3.6.1.4.1.4242.1.1 to its `Fred Router'.

The time (in hundredths of a second) since the network management portion of the system was last re-initialized.

The textual identification of the contact person for this managed node, together with information on how to contact this person. If no contact information is known, the value is the zero-length string.

An administratively-assigned name for this managed node. By convention, this is the node's fully-qualified domain name. If the name is unknown, the value is the zero-length string.

The physical location of this node (e.g., `telephone closet, 3rd floor'). If the location is unknown, the value is the zero-length string.

Root of Andrew Wireless Systems GmbH

The MIB is divided into ranges with different rights of access, in order not to grant any person access to the entire data. The protected main part of the information is located in the branch aimosObjects and can be accessed only after an authorising of the user, called login. The areas are accessible as follows: . The public area aimosPublic is accessible without any restrictions.It serves mainly to prepare the login procedure. . aimosLogin can be accessed only with special community names generated by the A.I.M.O.S. SNMP Agent. Here the login takes place. This authorising takes place via username and password. A valid user/password combination combined with a community name generated by the agent is called a session after the login has take place. The main part of the MIB (off aimosObjects downward) is permitted only within a valid session. . aimosObjects contains the objects of the managed network elements. This area is accessible only after a successful login (that is within a valid session) . aimosNotifications contains objects, which concern the alarm notifications. . aimosGroups and aimosCompliances satisfies SNMP requirements.

Before an user is able to login to the A.I.M.O.S. SNMP Agent, some preconditions must be fulfilled, which are located beneath aimosPublic and explained below. This branch is accessible with SNMP community set to public.

aimosSystemAvailability of type SystemAvailability gives information about system login possibility. The required value to be able to login is accessible(1). The first version of the A.I.M.O.S. SNMP Agent will report this value only. If the agent itself is not reachable by the SNMP protocol, then the manager will get a timeout error.

aimosCommunity of type Community issues a Community-Name required for the communication with the A.I.M.O.S. SNMP Agent. The Community public only allows access to the aimosPublic area. The validity of a Community-Name expires, when . it has no longer been used for a certain time (s. aimosSessionTimeout) . the logoff followed the login (s. aimosLoginState) . the A.I.M.O.S. SNMP Agent Windows NT service is closed. Accessing the aimosCommunity object with the Community public (or an invalid Community-Name) returns a Community-Name with a random combination of characters. The object aimosCommunityLength determines the length of this character chain. Only Community-Names created in this way are accepted by the A.I.M.O.S. SNMP Agent. An access to aimosCommunity using a valid generated Community-Name (instead of public) provides no new name but the Community-Name used in the query.

aimosCommunityLength is an Unsigned32 value in the range of 1 to 40 which states the length of community names being generated on reading of aimosCommunity. The provider is allowed to adjust this value, in order to manipulate the foreseeableness of the community names and therefore increase or decrease the security level. Although this value is in the public area (and could be read from everyone), a modification can take place only in a valid Session, i.e., with a community name, to which a valid login took place.

aimosMinPasswordLength is an Unsigned32 value in the range of 5 to 40 which states the requirement for the length of passwords. The provider is allowed to adjust this value, in order to manipulate the password security level. Although this value is in the public area (and could be read from everyone), a modification can take place only in a valid Session, i.e., with a community name, to which a valid login took place.

The aimosLogin branch carries the leafs for logging in as a specific user. As above-mentioned access to the branch aimosLogin is only permitted with SNMP community set to a value published by aimosCommunity. Login process is performed by the following actions: . Get SNMP community string from aimosCommunity using public as community name. Use this community name in further SNMP requests. . Set the user name in aimosLoginUserName (use the new community name!) . Set the corresponding password in aimosLoginPassword expect in the case of the first login after software installation. In that case a text in the following format has to be used as password: nnnnnn xxxx xxxx xxxx xxxx xxxx aaaaaaa where n is the OrgID x is the license key a is the license extra data (may be omitted) . Set aimosLoginState to connected(1). . Check the current aimosLoginState. . If login was successful, then it is set to connected(1) state. . If the password is wrong, then it is set to refused(2) state. . If passwordExpired(4) is returned, the password has expired. Password expiration =================== All passwords are valid for an amount of days. This period of time is specified in aimosPasswordExpirationPeriod. If a password was unchanged for more than the specified number of days, then the password expires. Existing Sessions are not affected by the password expiration. When a password has expired, no login can be made for the corresponding user account, until the user has defined a new password. The new password has to be assigned to aimosLoginPassword in order to complete the login process. If the new password is permissible then . this password is stored in aimosUserPassword and has to be used in the future . and aimosLoginState gets connected(1). The default password (start) is expired by default. I.e., if the default password is used for login, the user needs to advise a new password as mentioned above. Due to the . minimum password length requirements (aimosMinPasswordLength) . or the reusability of passwords (aimosPasswordReuseCounter) . as well as the requirements on password security (aimosPasswordStandard) it may be possible, that the new password is not acceptable by the A.I.M.O.S. SNMP Agent. In that case, the password remains expired and the user is required to . devise another password and repeat this procedure until aimosLoginState gets connected(1) . or cancel the login process by setting aimosLoginState to disconnected(0) Logout ====== Set aimosLoginState to disconnected(0) in order to log out. After log out the community name is invalid and therefore aimosLoginState gets canceled(3). If you need to log in again, then you have to request for a new community name by the steps described above.

aimosLoginUserName of type UserName is provided to record the username for login purposes. The username is a predefined user account or a user account created by the provider. When setting the Username the following SNMP ErrorStatus-values may be returned: . noAccess(6) either the Organisation to which the Username belongs is deactivated (via aimosOrgActive) or the user account itself is deactivated (via aimosUserActive) . wrongLength(8) the TextualConvention of this object specifies, that Usernames must be 1 to 40 characters long. If this condition is not fulfilled, the Username assignment is answered by this SNMP ErrorStatus. . wrongValue(10) the Username is unknown . authorizationError(16) an invalid Community-Name was used . notWritable(17) after a successful login the aimosLoginUserName can no longer be changed

aimosLoginPassword of type PasswordString serves to record the password of the user. Here, the user must enter the password assigned to the user account by one of the following three processes: . A password can be assigned when a user account is created. . If no password was explicitly assigned during the creation of the user account, the implicitly assigned default password is start. In such a case this password must uniquely be used for the first login. . Passwords expire after a certain interval (see aimosPasswordExpirationPeriod). If a password is expired, the user has to define a new one. A password assignment may result in one of the following SNMP ErrorStatus values: . wrongLength(8) the TextualConvention of this object specifies the length of a password to range from 5 to 40 characters. The Provider may specify a higher minimum length via the object aimosMinPasswordLength. If one of the two length requirements is not kept, the password assignment will be denied with this SNMP ErrorStatus. . wrongEncoding(9) the object aimosPasswordStandard specifies which characters may be used for a password. If this requirement is not kept, the password assignment will be denied with this SNMP ErrorStatus. . wrongValue(10) this SNMP ErrorStatus message follows either after a trial to assign the standard password start as new password or when the password for the first login after software installation is an invalid OrgID . authorizationError(16) an invalid Community-Name was used . notWritable(17) after a successful login the aimosLoginPassword can no longer be changed

The aimosLoginState of type LoginState is used in order to accomplish the login process, as its value is set to connected(1). If its value is set to disconnected(0), then the user logs off and the community name is invalidated. Therefore it cannot be reused. In addition it serves to indicate the status of login success. To any time this object may emit one of the following values: . disconnected(0) if access to the MIB (except the branches aimosPublic and aimosLogin) is not allowed with the community name currently used . connected(1) if login was successful and access is permitted to the entire MIB . refused(2) if the password is wrong. Enter the correct password in aimosLoginPassword and try to set aimosLoginState to connected(1) again . canceled(3) if the community name is invalidated by setting aimosLoginState to disconnected(0) or due to missing traffic for a certain period of time . passwordExpired(4) if password is expired. Setting the LoginState may result in one of the following SNMP ErrorStatus-values . noAccess(6) This SNMP ErrorStatus will be returned by the A.I.M.O.S. SNMP Agent if a login failed more than three times in a row due to a wrong password. When such 'hacking' is discovered, the account will be locked for a period of 30 minutes. . wrongValue(10) Only the two values disconnected(0) and connected(1) may be assigned. All other values are only important for read access. . inconsistentValue(12) This SNMP ErrorStatus will be returned by the A.I.M.O.S. SNMP Agent if an expired password is used to try and set the aimosLoginState to connected(1). In such a case, however, the A.I.M.O.S. SNMP Agent expects that either the new password is assigned by aimosLoginPassword or a logout by assigning aimosLoginState disconnected(0). . authorizationError(16) An invalid Community-Name was used.

aimosLoginOrgID of type OrgID contains the organisation ID of the organisation of the user after successful login.

After a successful login the AIMOS SNMP Agent attempts to recognize the SNMP Managers aimosLoginPhonebookID by means of its IP Address. In case the aimosPhoneBookTable contains a unique representation if this IP Address the aimosLoginPhoneBookID of type Unsigned32 contains the appropriate aimosPhoneBookID. If not this value is 0, In any case this value can be set to (overridden with) a valid aimosLoginPhoneBookID. The value here is used in two cases: 1. starting an Alarm List Resync (see description to aimosAlarmListResync) 2. walking the aimosAlarmListTable (see its description for further details)

The branch aimosObjects is accessible only after a successful login.

In this section, system-wide parameters are described. Only the provider is responsible for and allowed to change most of the contents of the listed MIB branch. Changes, which are made here may have sometimes crucial influence on the behaviour of the A.I.M.O.S. SNMP Agent. Thus be careful with changes in this section.

This object is a read-only value of type Version representing the version of the MIB file.

This object is a read-only value of type Version showing the software version of the A.I.M.O.S. SNMP Agent.

This object is a read-only value of type Version displaying the software version of the OMC Connector.

This object of type OBJECT IDENTIFIER references the OID of the corresponding trap type listed in aimosNotifications, if aimosPhoneBookInterfaceType is set to ifAimosObsolete(4). The entry is accessible in notifications only. If aimosPhoneBookInterfaceType is not set to ifAimosObsolete(4), then the object snmpTrapOID is used in the notifications instead.

This object of type SDN is the system distinguished name of the OMC which is designated to uniquely identify this OMC within an organisation. E.g.: The third OMC in the network supervision may have an SDN of OMC=3. Changing the class name (preceding the equality mark) affect only the current organisation, while changing the instance number (after the equality mark) will affect each organisation. That's the reason, why TelCo's must not change the instance number.

This object of type Text with up to 40 characters is provided to assign a free definable name for the OMC, e.g. 'A.I.M.O.S. OMC - North'. It makes only sense if you have more than one A.I.M.O.S. OMC. Changes, which are made here, affect all organisations. That's why TelCo's are not allowed to make any changes here.

This object of type TimeFormat determines of how date and time values of type VariableTime (e.g. aimosAlarmListEventTime) will be published by the SNMP Agent. This would be either UTCTime or LocalTime. The latter one is the default setting. Changes made here affect only the current organisation.

This object of type Unsigned32 within a range from 0 to 365 days decides the period of days after that passwords will expire. A value of 0 indicates, that the password will never expire; use this value in order to disable the password expiration facility. If a password is expired, then login is prevented by the A.I.M.O.S. SNMP Agent until a new password is assigned to aimosLoginPassword. Changes, which are made here, affect all organisations. That's why TelCo's are not allowed to make any changes here.

This object of type Unsigned32 with a range from 1 to 255 denotes the number of distinguished passwords, that must be used, before a specific one can be repeatedly used. A value of 3 indicates, that the 3 recent used passwords must be different to the new one. I.e., the user may have a list of 4 passwords used in circulation. Changes, which are made here, affect all organisations. That's why TelCo's are not allowed to make any changes here.

This object of type PasswordStandard determines if any numeric or special character is required in valid password creation. Existing passwords are not affected by changes made here. Changes, which are made here, affect all organisations. That's why TelCo's are not allowed to make any changes here.

A Session is rejected after a certain time of inactivity. This object provides the means to adjust this period in minutes. Set this object to zero in order to disable the idle timeout facility. Changes, which are made here, affect all organisations. That's why TelCo's are not allowed to make any changes here.

This object contains the IP address and the port that serves to access the OMC Connector. This information is required for creating Master Controllers. The value of this object is pre-set with the IP address determined by the A.I.M.O.S. SNMP Agent and the port set via the OMC Connector Setup. If the PC on which the A.I.M.O.S. SNMP Agent and the OMC Connector are running has several IP addresses, the selection made by the A.I.M.O.S. SNMP Agent might be wrong. In such a case the IP address can be changed. Since the port number is derived from the OMC Connector Setup, it cannot be changed, here. It should be left out when the IP address is changed.

This object of type VariableTime is used in heartbeat notifications and states the heartbeat notifications event time. This object also states the current time of the A.I.M.O.S. SNMP Agent.

The user management contains all access authorisation related data of organisations and its user accounts. Each organisation may have user accounts. An user account is required in order to get access to the A.I.M.O.S. SNMP Agent. An user account having the required rights can be used in order to create further user accounts with similar or less access rights. Read and write access rights are defined per area and are combined in 'roles'. The access rights of a user account are determined by assigning it to a certain role. The system is shipped with predefined organisations, user accounts, roles and its right assignments. Nevertheless the provider is responsible for the user management.

Informations about organizations. A organization is a company having a relationship with A.I.M.O.S.. Relationship can be one of the following: - manufacturer - provider - telco There is always exact one manufacturer and one provider. It's up to the provider to complete this table with one entry for each mobile network provider (telco) using his A.I.M.O.S. service. Users with aimosOrgLevel=telco are not allowed to modify contents of this table except of aimosOrgText and aimosOrgActiveWorkShiftID Insert rows: set aimosOrgName. to the organisation's name Delete rows: set aimosOrgName. to 'delete' (without quotation marks). TelCo's are not allowed to insert or delete rows.

see description for table entry...

This object is a Mikom provided world-wide unique identification number of an organisation of type OrgID.

This object offers the possibility to designate the organisation mentioned in aimosOrgID. Set this value to 'delete' (without quotation marks) in order to delete this table entry.

This object gives each organisation the possibility to configure a piece of text.

This object of type OrgLevel denotes the role of the organisation. Possible values are manufacturer(0), provider(1) and telco(2).

This object of type MCC is the mobile country code of a TelCo organisation. Manufacturer and provider have the MCC of its country.

This object of type MNC is the mobile network code of a TelCo organisation. Manufacturer and provider have a MNC of 0 (zero).

This object sets the activity state of an organisation. An organisation account is activated by writing true and deactivated by writing false to this object. Users of a deactivated organisations are not allowed to login. Existing Sessions are not affected by organisation deactivation.

This object of type DistinguishedNameSeparator separates the Distinguished Names into object type and object instance. E.g.: . 3GPP recommends equality mark (RU=17) . Nokia NetAct recommends hyphen (RU-17) Factory setting is an equality mark (=).

This object of type DistinguishedNameHierarchySymbol divides System Distinguished Names in its parts, the Relative Distinguished Names. E.g.: . 3GPP recommends comma (OMC=1,MC=4,SRMU=17) . Nokia NetAct recommends slash mark (OMC-1/MC-4/SRMU-17) Factory setting is a comma (,).

This object of type CableCodeConcatenator is used in aimosAlarmListCustomerCableInfo for concatenation of Cable Codes. Mikom default is a comma.

This object denotes the active work shift for delegation of alarms. The description for aimosWorkShiftTable contains more about work shifts.

Provides the aimosUserID to be used in creating a new user account (aimosUserTable).

Provides the aimosWorkShiftID to be used in creating a new work shift (aimosWorkShiftTable).

Provides the aimosAlarmRecipientListID to be used in creating a new alarm recipient list (aimosAlarmRecipientListTable).

Provides the aimosPhoneBookID to be used in creating a new phone book entry (aimosPhoneBookTable).

This table holds user related data. A user is a employee of a organization having an login account. This table is indexed by aimosOrgID and aimosUserID. Nevertheless aimosUserID is a unique number within one OMC aimosOrgID is included in indexing because of access rights. Insert rows: set aimosUserName.. to user's name Delete rows: set aimosUserName.. to 'delete' (without quotation marks)

see description for table entry...

This object is numbered consecutively. aimosOrgNextUserID tells you the value to be used in row/user creation.

This object of type UserName hosts the users name. A user name can be used once in the OMC. Therefore it is advisable to prefix the user name with an organisation sign (e.g. 'D1 - Meier'). Changing the user name will reset the aimosUserPassword to the default password (start). Setting this value to delete deletes this table entry (the user account).

This object of type PasswordString is the password for an user account required in order to login into the OMC. The default password is start. During the first login attempt using the default password the user needs to change the password. Each user is allowed to change its own password by means of . set aimosLoginPassword (if aimosLoginState is refused) or . set this object (if aimosLoginState is connected) to the new password. The user does not need to have readWrite(2) access to the RightArea administrationOMCAccounts(500) in order to change its own password. This access right is required in order to set the password of any user account.

This object of type Text gives the possibility to configure a piece of text.

With this object a certain role is assigned to a user account. Thus, via the table aimosRoleRightTable the User is granted the rights that are assigned to this role. The default value (0) is an illegal role ID, thus the user is by default not assigned to any role and couldn't access the MIB except the public and login area.

This object activates and deactivates an user account. If set to true the account is active and the user is able to log in, otherwise (false) no log in is possible. Existing Sessions are not affected by user deactivation.

This object states the time when the password was most recently changed.

This object is used in order to produce new roles within the aimosRoleTable. Its value has to be used as the identifier (aimosRoleID) of the new role.

Access control is made using roles. A role is a synonym for a certain combination of read and write access rights (AccessRight) to certain areas (RightArea). A role could be called e.g. 'admin' or 'alarm manager'. This table, indexed by aimosRoleID, contains a list of that roles. By assigning a role to a User via aimosUserRoleID, the read and write access rights connected to this role will be granted to the user account. Insert rows: set aimosRoleOwner. to the aimosOrgID of the role's owner Delete rows: set aimosRoleName. to 'delete' (without quotation marks) TelCo's are not allowed to insert or delete rows.

see description for table entry...

This object is numbered consecutively. Zero value is not allowed. aimosNextRoleID tells you the ID to be used in row creation.

This object contains a name for the role with up to 40 characters. The table entry is deleted by setting this value to delete.

Access control is made using roles. A role is a synonym for a certain combination of read and write access rights (AccessRight) to certain areas (RightArea). A role could be called e.g. 'admin' or 'alarm manager'. In this table, indexed by aimosRoleID and aimosRoleRightArea, the RightArea's of the Controller are assigned to the roles listed in the aimosRoleTable. Insert rows: set aimosRoleRightAccess.. to readOnly/ readWrite Delete rows: set aimosRoleRightAccess.. to noAccess TelCo's are not allowed to insert or delete rows.

see description for table entry...

This object of type RightArea determines the right area arised from the controller software to be attached to a particular role identified by the index object aimosRoleID.

This object of type AccessRight determines whether read, write or no access to a specific RightArea has to be assigned to the affected role. Write access includes read access. Setting this value to noAccess deletes this entry.

When a new Master Controller is created by making a new entry into the table aimosMasterUnitTable, the A.I.M.O.S. SNMP Agent requires a pre-setting for the object aimosMasterLoginUserName. This pre-setting is provided by this object. It is of the UserName type and must consist at least of one character and 20 characters at the most. The pre-setting is Owner. Changing the aimosInitiallyMasterLoginUserName has no effect on already existing user accounts on the Master Units.

When a new Master Controller is created by making a new entry into the table aimosMasterUnitTable, the A.I.M.O.S. SNMP Agent requires a pre-setting for the object aimosMasterLoginPassword. This pre-setting is provided by this object. It is of the ControllerPassword type and must consist of small and capital letters (a-z) as well as numbers. Other characters are not allowed. The password can be read, but the A.I.M.O.S. SNMP Agent only displays star marks (*) instead of the actual password. The pre-setting is Apwd4own. Changing the aimosInitiallyMasterLoginPassword has no effect on already existing user accounts on the Master Units.

Band Management is provided for allocation of radio frequencies to mobile network companies (TelCo's).

This table, indexed by aimosBandID, configures the characteristics of each RF band. This set up is done by Mikom. Insert rows: must only be done by Mikom Delete rows: must only be done by Mikom

see description for table entry...

This object of type NetworkStandard determines the network standard of the band to which this entry belongs to.

This object of type FrequencyRange is the lowest DL frequency (kHz) possible in a specific band.

This object of type FrequencyRange is the highest DL frequency (kHz) possible in a specific band.

This object of type Unsigned32 with a range from 10000 to 95000 represents the frequency gap in kHz between UL and DL. Uplink frequency = downlink frequency - gap.

This object of type ARFCN represents the ARFCN gap between UL and DL. Uplink ARFCN = downlink ARFCN - gap.

Frequency calculation for any ARFCN can be done by the following formula: fDL(ARFCN) = fStart + fBandWidth * (ARFCN-aOffset) This table contains the information required to calculate the frequency for any ARFCN for any network band. E.g.: the formula for Extended GSM900 is fDL(ARFCN) = 935000 + 200 * (ARFCN - 1024) Determination of frequency for ARFCN 1023 in E-GSM900 is realised by the following formula: fDL(1023) = 935.000 + 200 * (1023 - 1024) = 934.800 kHz Insert rows: must only be done by Mikom Delete rows: must only be done by Mikom

see description for table entry...

Enumerated consecutively.

First ARFCN for wich the aimosBandCalculationFormula-leafs are valid.

Last ARFCN for wich the aimosBandCalculationFormula-leafs are valid.

You can calculate the frequency for any ARFCN with the following formula: fDL(ARFCN) = aimosBandCalculationFormulaStart + aimosBandCalculationFormulaGap * (ARFCN-aimosBandCalculationFormulaOffset) Example: formula for Extended GSM 900 is 935000 + 200 * (ARFCN - 1024) Determine frequency of ARFCN 1023 in E-GSM900: fDL(1023) = 935.000 + 200 * (1023 - 1024) = 934.800 kHz In this example aimosBandCalculationFormulaStart must have the value 935000.

You can calculate the frequency for any ARFCN with the following formula: fDL(ARFCN) = aimosBandCalculationFormulaStart + aimosBandCalculationFormulaGap * (ARFCN-aimosBandCalculationFormulaOffset) Example: formula for Extended GSM 900 is 935000 + 200 * (ARFCN - 1024) Determine frequency of ARFCN 1023 in E-GSM900: fDL(1023) = 935.000 + 200 * (1023 - 1024) = 934.800 kHz In this example aimosBandCalculationFormulaGap must have the value 200.

You can calculate the frequency for any ARFCN with the following formula: fDL(ARFCN) = aimosBandCalculationFormulaStart + aimosBandCalculationFormulaGap * (ARFCN-aimosBandCalculationFormulaOffset) Example: formula for Extended GSM 900 is 935000 + 200 * (ARFCN - 1024) Determine frequency of ARFCN 1023 in E-GSM900: fDL(1023) = 935.000 + 200 * (1023 - 1024) = 934.800 kHz In this example aimosBandCalculationFormulaOffset must have the value 1024.

This table is indexed by aimosOrgID, aimosBandID and aimosLicenseeFirstARFCN and shows information about frequencies licensed by Mobile Network Providers. Insert rows: set aimosLicenseeARFCNCount... to the number of channels in band aimosBandID starting with aimosLicenseeFirstARFCN used by aimosOrgID Delete rows: set aimosLicenseeARFCNCount... to zero TelCo's are not allowed to insert or delete rows.

see description for table entry...

This object of type ARFCN is the first ARFCN of an licensed interval. The size of an ARFCN interval is specified by aimosLicenseeARFCNCount.

this object of type ARFCN represents the size of each ARFCN interval. The last ARFCN of an ARFCN interval is calculated by the following formula: last ARFCN = aimosLicenseeFirstARFCN+aimosLicenseeARFCNCount-1. Set this value to 0 (zero) to delete this table entry.

This table is indexed by aimosBandID and aimosFrequencyARFCN and tells you per radio frequency channel number its radio frequency and licensee (identified by its aimosOrgID). Insert rows: not applicable (calculated by contents of aimosBandCalculationTable) Delete rows: not applicable (calculated by contents of aimosBandCalculationTable)

see description for table entry...

This object of type ARFCN is the index of this table.

This object of type FrequencyRange returns the frequency in kHz for aimosFrequencyARFCN.

This object of type OrgID returns the organisation ID of the TelCo owning the license for this frequency/ARFCN.

This table is indexed by aimosBandID and aimosARFCNFrequency and tells you per radio frequency its radio frequency channel number and licensee (identified by its aimosOrgID). Insert rows: not applicable (calculated by contents of aimosBandCalculationTable) Delete rows: not applicable (calculated by contents of aimosBandCalculationTable)

see description for table entry...

This object of type FrequencyRange is the index (kHz) of this table.

This object of type ARFCN returns the ARFCN that corresponds to aimosARFCNFrequency.

This object of type OrgID returns the organisation ID of the TelCo owning the license for this ARFCN/frequency.

This is a short introduction in order to help you understand how the A.I.M.O.S. SNMP Agent realises SNMP alarm forwarding. When the A.I.M.O.S. SNMP Agent is informed about a failure in the monitored system, it must find out which SNMP Managers will have to get an alarm message. Each SNMP Manager who is to get the alarm message, requires an entry in the aimosPhoneBookTable. This entry contains the IP address used for alarm forwarding. Prior to the explanation on how the A.I.M.O.S. SNMP Agent determines the list of phone book entries which have to be informed about an active alarm, the three aspects with a decisive influence on this determination will be explained in the following: . Alarms with similar characteristics will be put together in alarm groups. The alarm groups defined in the system are listed in the table aimosAlarmGroupTable. Via aimosAlarmAlarmGroupID each alarm is assigned to exactly one alarm group. . The Provider can create work shifts and determine various alarm distribution rules in dependence of each work shift. The work shifts defined in the system are listed in the table aimosWorkShiftTable. The currently active work shift is set by each Organisation itself using the object aimosOrgActiveWorkShiftID in the aimosOrgTable. . The third point of influence are the alarm recipient lists. Each Organisation defines its own alarm recipient lists by adding the according entries to the table aimosAlarmRecipientListTable. For each alarm recipient list the phone book entries assigned to it are listed in the aimosAlarmRecipientListMemberTable. One phone book entry (i.e. one SNMP Manager) can be assigned to several alarm recipient lists simultaneously. In order to get the list of SNMP Managers that have to be informed, the A.I.M.O.S. SNMP Agent proceeds as follows: . The A.I.M.O.S. SNMP Agent checks the aimosAlarmConfigTable, and uses the object aimosAlarmAlarmGroupID in order to find out to which alarm group the alarm belongs. . Next, it determines which Organisations are authorised to receive alarms of this alarm group. This information is laid down in the table aimosAlarmGroupAllowedOrgTable. . The A.I.M.O.S. SNMP Agent checks the value of aimosAlarmForwardingType of each affected organisation in order to determine the organisations having alarm forwarding enabled as well as the kind of alarm forwarding to be used (SNMPv1 trap or SNMPv2c notification). . For each Organisation that is allowed (allowed org) and enabled (alarm forwarding enabled) to receive alarms, the current work shift is identified via the object aimosOrgActiveWorkShiftID. . The table aimosAlarmDistributionPlanTable now shows which alarm recipient lists have to be used. The table provides one alarm recipient list per Organisation, AlarmGroup and work shift. If there is no entry for a certain combination, no alarm will be sent. If there is an entry, each member of the alarm recipient list (aimosAlarmRecipientListMemberTable) will receive an alarm notification, unless a phone book entry was deactivated via aimosPhoneBookActive. After the alarm recipients have been identified, the various counters required for sending traps must be identified: . The aimosAlarmListAlarmEventID identifies the cause leading to the dispatch of a aimosAlarmNew or a aimosAlarmChanged notification to one or more SNMP Managers. Here, the counter will be increased by one for each cause. If the cause leads to sending a aimosAlarmCleared notification, the counter will not be increased. Instead, the count of the according aimosAlarmNew or (if present) the latest aimosAlarmChanged notification will be used. . The aimosAlarmListID is identical to the aimosAlarmListAlarmEventID, as long as the aimosAlarmChanged alarm has not been implemented. . The aimosAlarmTrapID uniquely identifies each notification that was not sent to an SNMP Manager. . Each SNMP Manager can rely on the aimosAlarmTrapNotificationID to have a continuous numeration. If not, one notification got lost. At long last the A.I.M.O.S. SNMP Agent have to collect some information required to provide the notifications: . The A.I.M.O.S. SNMP Agent have to inspect the aimosAlarmConfigTable (and in a future version of the A.I.M.O.S. SNMP Agent the aimosAlarmSeverityRangeTable) to determine the alarms severity (in the future version for each organisation). . The A.I.M.O.S. SNMP Agent collects the organisation specific customer device information to be provided with the notification by means of the values of aimosMasterTrapInfo, aimosSubRackTrapInfo, aimosRemoteTrapInfo and aimosCableTrapInfo. Now the A.I.M.O.S. SNMP Agent has collected all information required for SNMP alarm forwarding. The A.I.M.O.S. SNMP Agent will now perform the following actions: . Create one entry per organisation in the alarm list (aimosAlarmListTable) using the organisations ID (aimosOrgID) and the alarm List ID (aimosAlarmListID) as index. . Send one SNMP notification to each manager discovered by the steps mentioned above and create for each notification one entry in the trap list (aimosAlarmTrapTable) using the organisations ID (aimosOrgID), the alarm List ID (aimosAlarmListID) and the trap ID (aimosAlarmTrapID) as index. Each manager have to acknowledge the received notifications by means of setting aimosAlarmTrapAcknowledgementState using its organisation ID (aimosOrgID), the alarm list ID (aimosAlarmListID) and the alarm trap ID (aimosAlarmTrapID) to acknowledged(2). After having emitted the alarm notification, the A.I.M.O.S. SNMP Agent expects an acknowledgement within a certain interval, that can be specified (in seconds) in aimosAlarmAckExpectInterval. If there is no such acknowledgement, the A.I.M.O.S. SNMP Agent will continue to emit the alarm until the acknowledgement is received. The notification remains in the alarm list . as long as the based alarm event is active or . if at least one notification related to the alarm event is not yet acknowledged by at least one of the involved SNMP Managers. The entries in the trap table (aimosAlarmTrapTable) are earlier removed: If a manager has performed the required acknowledgements, its entries in the trap table are removed. After remove from the trap and alarm list table, the removed entries are available in the alarm log (aimosAlarmLogTable). The specific alarm event ID will not be used again unless an alarm list rebuild resets the counter to zero or the wrap value (2^32-1) is reached. If a similar or even the same alarm event occurs again (after the old one gets cleared), than the notification will not contain the formerly used alarm event ID but a new one.

This object is needed in addition of alarm groups to the aimosAlarmGroupTable. Its value has to be used as the identifier (aimosAlarmGroupID) of the new alarm group.

This table is indexed by aimosAlarmGroupID and lists the alarm groups available in the system. Alarm groups provides the means to collect alarms with similar characteristics. Insert rows: set aimosAlarmGroupName. to any text Delete rows: set aimosAlarmGroupName. to 'delete' (without quotation marks) TelCo's are not allowed to insert or delete rows.

see description for table entry...

This object is numbered consecutively. aimosNextAlarmGroupID tells you the ID to be used in row creation.

This object contains a name for the alarm group with up to 50 characters. Set this value to 'delete' (without quotation marks) in order to delete this table entry/alarm group. Changes, which are made here, affect all organizations. That's why TelCo's are not allowed to make any changes here.

This table serves to specify the organisations that will be authorised to receive alarms of a certain alarm group. Organisations not listed in this table cannot have entries in the table aimosAlarmDistributionPlanTable, which excludes them from alarm distribution. Only the provider is allowed to modify the contents of this table. Insert rows: set aimosAlarmGroupAllowedOrgActive.. to true Delete rows: set aimosAlarmGroupAllowedOrgActive.. to false TelCo's are not allowed to insert or delete rows.

see description for table entry...

This object is used for row creation and deletion. An existing table entry denotes, that the corresponding organisation is allowed to receive alarms collected in a specific alarm group. Due to the way of row deletion there will never be a table entry with a value of false in aimosAlarmGroupAllowedOrgActive. TelCo's are not allowed to make any changes.

With this table, indexed by aimosAlarmID, alarms can be configured. E.g. the Severity or the assignment to a certain alarm group can be specified here. Insert rows: must only be done by Mikom Delete rows: must only be done by Mikom

see description for table entry...

The aimosAlarmID of type AlarmID uniquely identifies the type of alarm.

This object holds a short explanation of the type of alarm.

The aimosAlarmEventType of type EventType categorises the alarm.

This object of type Severity denotes the default severity of an alarm. Use the value indeterminate(0) in order to disable the alarm forwarding for this kind of alarms. Default severity is used, if organisation specific alarm severity configuration is not defined by aimosAlarmSeverityRangeTable. Changes, which are made here, affect all organizations. That's why TelCo's are not allowed to make any changes here.

This object of type Severity determines the at least allowed configurable severity in aimosAlarmDefaultSeverity and aimosAlarmSeverityRangeTable.

This object holds the Alarm Group assignment (aimosAlarmGroupID). Changes, which are made here, affect all organizations. That's why TelCo's are not allowed to make any changes here.

This object of type ClearMode informs you of how an alarm gets cleared. Changes, which are made here, affect all organizations. That's why TelCo's are not allowed to make any changes here.

This table holds organisation specific data of alarm severity configuration. Insert rows: set aimosAlarmSeverityRangeSeverity... . to any severity value but indeterminate Delete rows: set aimosAlarmSeverityRangeSeverity... . to severity indeterminate This table is not yet supported !

see description for table entry...

Low value causing a defined severity.

High value causing a defined severity.

aimosAlarmSeverityRangeSeverity of type Severity holds the severity to be used in alarm notifications if the alarm value is within the range from aimosAlarmSeverityRangeMinValue to aimosAlarmSeverityRangeMaxValue, both of type AlarmValue. Use the value indeterminate(0) in order to delete the table entry. If there is no appropriate entry for a specific Alarm ID, then aimosAlarmDefaultSeverity determines the severity of the alarm.

Alarm distribution depends on work shifts: . This table holds the available work shift ID's and names. . aimosOrgActiveWorkShiftID determines the active work shift per each organisation. . The table aimosAlarmDistributionPlanTable is indexed by aimosWorkShiftID and therefore it holds one alarm recipient list per work shift. In this way it is possible to activate another alarm distribution list via simply switching the current work shift. Insert rows: set aimosWorkShiftName.. to any text Delete rows: set aimosWorkShiftName.. to 'delete' (without quotation marks)

see description for table entry...

This object is numbered consecutively. aimosOrgNextWorkShiftID tells you the ID to be used in row creation.

This object contains a name for the work shift with up to 40 characters. Set this value to 'delete' (without quotation marks) in order to delete this table entry/work shift.

This object is intended to specify the interval in minutes, after that the A.I.M.O.S. SNMP Agent will emit a heartbeat notification to one or more SNMP Manager. Use aimosWorkShiftHeartbeatRecipientList in order to define that SNMP Managers. This interval is only used, if the affected work shift is activated (i.e. the value of aimosOrgActiveWorkShiftID is set to the affected aimosWorkShiftID). If either aimosWorkShiftHeartbeatInterval or aimosWorkShiftHeartbeatRecipientList is set to 0, no heartbeat notification will be emitted.

This object is intended to specify the Alarm Recipient List which has to be used if the A.I.M.O.S. SNMP Agent emits heartbeat notifications. Each member of the specified Alarm Recipient List (specified via aimosAlarmRecipientListMemberTable) will receive a heartbeat notification every [aimosWorkShiftHeartbeatInterval] minutes. This Recipient List is only used, if the affected work shift is activated (i.e. the value of aimosOrgActiveWorkShiftID is set to the affected aimosWorkShiftID). If either aimosWorkShiftHeartbeatInterval or aimosWorkShiftHeartbeatRecipientList is set to 0, no heartbeat notification will be emitted.

This table, indexed by aimosOrgID, aimosAlarmGroupID and aimosWorkShiftID, holds the alarm recipient list to be used for sending alarms of a certain Alarm Group if a certain work shift is active. Each organisation may have different settings. Each member of the discovered alarm recipient lists will get the notification. The organization must be allowed to receive alarms of the specific Alarm Group, thus there must be an appropriate entry in the aimosAlarmGroupAllowedOrgTable. Insert rows: set aimosAlarmDistributionPlanRecipientListID.. . to a valid aimosAlarmRecipientListID Delete rows: set aimosAlarmDistributionPlanRecipientListID.. . to zero Example: ======== An organisation with OrgID 262299 wants . recipient list 1 to be used for alarms of alarm group 2 during work shift 1 . recipient list 4 to be used for alarms of alarm group 2 during work shift 2 Two entries are needed in this table: . aimosAlarmDistributionPlanRecipientListID.262299.2.1 set to 1 . aimosAlarmDistributionPlanRecipientListID.262299.2.2 set to 4

see description for table entry...

This objects value is the recipient lists ID (aimosAlarmRecipientListID) that will be bound up with the aimosAlarmGroupID and aimosWorkShiftID for aimosOrgID. The corresponding organisation must be allowed to receive alarms of the specified Alarm Group, thus there must be an appropriate entry in the aimosAlarmGroupAllowedOrgTable. Set the value to 0 (zero) in order to delete this table entry.

This table holds the names and IDs of available alarm recipient lists for each organization. It is indexed by aimosOrgID and aimosAlarmRecipientListID. Insert rows: set aimosAlarmRecipientListName.. to the recipient list's name Delete rows: set aimosAlarmRecipientListName.. to 'delete' (without quotation marks)

see description for table entry...

This object is numbered consecutively within one organisation. aimosOrgNextAlarmRecipientListID tells you the value to be used in alarm recipient list creation. The value of 0 (zero) must not be used here.

This object is just a name with a maximum length of 50 characters for the alarm recipient list. Set this value to 'delete' (without quotation marks) in order to delete this table entry.

This table gives IP addresses and IP ports of alarm recipients (SNMP Manager) a name and classifies its communication type. Insert rows: set aimosPhoneBookAddress.. to any IP address and port Delete rows: set aimosPhoneBookAddress.. to 'delete' (without quotation marks)

see description for table entry...

This object is numbered consecutively within one organisation. aimosOrgNextPhoneBookID tells you the value to be used in phone book entry creation.

This object of type PhoneBookEntry is a name for the phone book entry helping to disclose its identity. This name should be unique.

This object of type IPAddressAndPort hold the IP address and IP port number. The port number may be omitted in set requests, if the port number is the default port number for SNMP traps (162). Set this value to 'delete' (without quotation marks) in order to delete the phone book entry. Phone book entries currently used in the alarm list/log cannot be removed.

This object is used in order to deactivate a phone book entry for a short period of time. Inactive phone book entries are excluded from alarm distribution even if they have entries in the aimosAlarmDistributionPlanTable.

This object denotes the notification ID used in the most recent trap for the specific SNMP Manager. The NotificationID of the next trap that is generated will be 1 higher. The wrap value is 2^32-1.

This object of type OperationMode is provided to give each SNMP Manager the ability to synchronise its alarm table. Setting this value to start(5) will start the alarm list synchronisation process.

This object of type InterfaceType is provided in order to define the kind of alarm forwarding. Leave this object on its default value unless you want to force the SNMP Agent to use an older type of alarm forwarding for compatibility reasons. The aimos interface was adapted in order to remain conformal with SNMP. The differences between ifAimosObsolete(4) and ifAimos(5) are as follows: -------------------------------------------------------------------------------- topic ifAimosObsolete ifAimos ================================================================================ trap object (second 1.3.6.1.4.1.6408.201.3.1.4 1.3.6.1.6.3.1.1.4.1.0 object in alarm AIMOS.aimosTrapOID SNMPV2-MIB.snmpTrapOID.0 notifications) -------------------------------------------------------------------------------- enterprise object 1.3.6.1.4.1.6408.201.4.3.0 1.3.6.1.6.3.1.1.4.3.0 (the last object in AIMOS.aimosTrapEnterprise SNMPV2-MIB.snmpTrapEnterprise.0 alarm notifications) -------------------------------------------------------------------------------- enterprise name (the 1.3.6.1.4.1.6408 1.3.6.1.4.1.6408.201.4 alarm notifications mikom AIMOS.aimosNotifications last objects value) -------------------------------------------------------------------------------- instance identifiers each objects instance each object has its real in alarm except aimosTrapOID is 0 instance identifier notifications objects -------------------------------------------------------------------------------- The ifOMC3... interfaces are implemented only for compatibility reasons to the Mikom OMC Version 3. They are described in the documentation to that OMC. The Nokia interface is described in documents available from Nokia.

This object is provided in order to state the SNMP Managers ability to perform an acknowledgement. . If this object is set to true (default), then the SNMP Agent expects an acknowledgement for each trap sent out. Each trap will be periodically re-send until achnowledgement is detected. . This object has to be set to false in the case of the inability of the SNMP Manager to maintain the acknowledgement process. In that case the SNMP Agent doesn't expect an acknowledgement. Therefore each trap is sent out nonrecurring and - since SNMP is based on UDP - traps may be lost!

This object of type TimeDisplayFormat is provided in order to define ofhow date and time values (in objects of type VariableTime) inquired by an GET request or shipped within alarm notifications have to be encoded by the SNMP agent. Each SNMP manager may make its own setting if system default is not acceptable. The system default is default(0). It is treated as . osiBinary(1) unless aimosPhoneBookInterfaceType is set to ifAimosObsolete(4) . osiText(2) if aimosPhoneBookInterfaceType is set to ifAimosObsolete(4)

This object defines the format to be used for objects with textual convention GPSPosition. These are as follows: . aimosAlarmListRaiseLatitude . aimosAlarmListRaiseLongitude . aimosAlarmListClearLatitude . aimosAlarmListClearLongitude . aimosAlarmLogRaiseLatitude . aimosAlarmLogRaiseLongitude . aimosAlarmLogClearLatitude . aimosAlarmLogClearLongitude

This object provides means to state whether or not the SNMP Manager desires the SNMP Agent to sent a aimosAlarmRecognized trap in case an alarms recognition state changes from unrecognized(1) to recognized(2). Please see also the description to aimosAlarmListRecognitionState.

This table determines the members of a certain alarm recipient list. All active members of an Alarm Recipient List receive the alarm notifications assigned to this list via the table aimosAlarmDistributionPlanTable. Insert rows: set aimosAlarmRecipientListMemberActive.. . to true Delete rows: set aimosAlarmRecipientListMemberActive.. . to false

see description for table entry...

This object is used for row creation and deletion. Due to the way of row deletion there will never be an object in this table having a value of false. An existing table entry denotes, that the corresponding phone book entry is assigned to the specific alarm recipient list. Thus it become a member of the alarm recipient list and with it a recipient of the alarms assigned to the alarm recipient list. If the phone book entry is deactivated via aimosPhoneBookActive, no traps will be sent to this recipient. Set this value to false in order to delete a table entry.

This table is indexed by aimosOrgID, aimosAlarmTrapID and aimosAlarmListID and contains a list of all traps sent out by the agent to a specific SNMP Manager identified by its phone book entry. Insert rows: must only be done by system Delete rows: must only be done by system

see description for table entry...

This object is an unique identifier for a trap on SNMP Agent side and is used in alarm acknowledgement. Even if its value is consecutive numbered on agent side, it could seem to the SNMP Manager in such a way as if the values may be gappy. This will be regularly the case if more than one alarm receiver is present. This value is reset to 0 on alarm list rebuild. The wrap value is 2^32-1.

This object is incremented consecutively for each notification sent out to a particular SNMP Manager. Thus every SNMP Manager (identified by its phone book entry) will have consecutively numbered values in all received notifications and therefore its value can be used in order to recognise missing notifications. The wrap value is 2^32-1. An Alarm List Resync will reset the current SNMP Managers notification ID, whereas an alarm list rebuild will reset the corresponding notification ID of each SNMP Manager.

This object is the SNMP Managers aimosPhoneBookID to which the notification was directed to.

This object of type AcknowledgementState states whether or not the alarm was acknowledged. It is the only writeable value in this table. Acknowledgement will be done by setting this value to acknowledged(2). The term acknowledgement is pertaining to the SNMP protocol: it provides means for the SNMP manager to acknowledge trap receipt. On the other hand the similar sounding term 'recognition' is used to indicate an 'I have seen the alarm and will take care about it'. The latter one is also available via the AIMOS_Visu's Supervision page.

This object holds the user who has acknowledged the alarm. This object is empty if the alarm is not yet acknowledged.

This object of type VariableTime holds the time of acknowledgement. This object is empty if the alarm is not yet acknowledged.

This table contains a list of active alarms. This table is indexed by aimosOrgID and aimosAlarmListID; i.e. the table is organisation specific and, thus has entries for each concerned organisation. Each aimosAlarmNew and aimosAlarmChanged notification generates a new entry for each Organisation receiving the alarm. aimosAlarmCleared notifications forwarded by the agent to any manager do not create another entry, but make an amendment to existing ones. The entries remain in the list . as long as the corresponding alarm situation still exists or . if any manager of a specific organisation has not yet acknowledged required notifications related to the specific alarm situation. Insert rows: must only be done by system Delete rows: must only be done by system The value stored in aimosLoginPhoneBookID affects this table in the following way: - if aimosLoginPhoneBookID is a valid aimosPhoneBookID, then only alarms forwarded to the corresponding SNMP Manager are listed in aimosAlarmListTable - if aimosLoginPhoneBookID is an invalid aimosPhoneBookID, this table is empty - if aimosLoginPhoneBookID is 0 this table is complete / not filtered

see description for table entry...

This object is the consecutive numbering of all alarm notifications of the A.I.M.O.S. SNMP Agent forwarded to any manager. A notification forwarded to more than one SNMP Manager will contain identical aimosAlarmListID's. When an alarm list rebuild is initiated by a SNMP Manager then the alarm list ID is reset. The alarm list ID is not reset, if a SNMP Manager starts an Alarm List Resync. The wrap value is 2^32-1.

This object's Unsigned32 value is incremented by one for each alarm notification except aimosAlarmChanged and aimosAlarmCleared. Alarm changed notifications and alarm clear notifications are correlated with alarm new notifications by the aimosAlarmListAlarmEventID. When an alarm list rebuild is initiated by a SNMP Manager then the alarm event ID is reset. The alarm event ID is not reset, if a SNMP Manager starts an Alarm List Resync. The wrap value is 2^32-1.

This object of type AlarmID designates the alarm kind.

The Event Type categorises the alarm.

This object of type VariableTime states when the alarm condition appeared or (in the case of an aimosAlarmCleared notification) when the alarm condition is gone.

This object of type ProbableCause defines further qualification of an alarm than aimosAlarmListEventType.

This object of type SpecificProblem is a fault specific value used in order to classify the fault situation. It provides further qualification of the alarm than probable cause and is defined in accordance with definitions given in ITU-T Recommendation X.733 clause 8.1.2.2.

This object of type Severity defines severity levels, which provide an indication of how it is perceived that the capability of the managed object has been affected.

This object of type TrendIndication specifies the current severity trend of the managed object.

This object allows a free form text description to be reported. It contains a formatted description of the alarm and, should the occasion arise, includes alarm values.

The System Distinguished Name uniquely identifies the unit within the system controlled by the OMC.

This OID contains the Network Elements's TrapInfo

This OID contains the Network Elements's Component Name

This OID contains the Network Elements's Location

This OID contains the Network Elements's Unique System ID

This OID gives information weather the alarm was cleared or not. If an alarm does not become automatically cleared (aimosAlarmClearMode is set to manualClear), manualCleared is the only writeable value (besides aimosAlarmListRecognitionState).

this object of type VariableTime states the time of the event specified in aimosAlarmListClearReason.

this object was introduced in V 2.6.0 and states the Network Elements Latitude to the time the alarm was raised.

this object was introduced in V 2.6.0 and states the Network Elements Longitude to the time the alarm was raised.

this object was introduced in V 2.6.0 and states the Network Elements Latitude to the time the alarm was cleared.

this object was introduced in V 2.6.0 and states the Network Elements Longitude to the time the alarm was cleared.

This object of type RecognitionState states whether or not the alarm has been recognized. Together with aimosAlarmListClearReason these objects are the only writeable values of this table. Recognition is used to indicate an 'I have seen the alarm and will take care about it'. It is available via SNMP as well as via the AIMOS_Visu's Supervision page. Recognition by means of SNMP will be done by setting this value to recognized(2). Due to the fact that alarms are moved from aimosAlarmListTable to aimosAlarmLogTable as soon as they are both cleared and acknowledged aimosAlarmLogRecognitionState provides means to recognize cleared alarms; it is the only writeable alarm log object. A SET request with unrecognized(1) (i.e. 'Unrecognition') is an invalid operation and will be rejected by the SNMP Agent. For each alarm recognition the SNMP Agent sends a aimosAlarmRecognized trap to SNMP Managers having aimosPhoneBookRecognitionTraps set to true. On the other hand the similar sounding term 'acknowledgement' is pertaining to the SNMP protocol: it provides means for the SNMP manager to acknowledge trap receipt. Please note: in case both the acknowledgement feature and the recognition-traps-feature are active, even the recognition traps have to be acknowledged.

This object indicates the user who has recognized the alarm. This object is empty if the alarm is not recognized at all.

This object of type VariableTime holds the time of recognition. This object is empty if the alarm is not recognized at all.

This table is indexed by aimosOrgID, aimosAlarmTrapID and aimosAlarmListID and contains the list of cleared and acknowledged alarms. The data is the content of the alarm list related to a specific SNMP Manager and the corresponding contents of the trap list. Insert rows: must only be done by system Delete rows: must only be done by system

see description for table entry...

See corresponding description in aimosAlarmTrapTable.

See corresponding description in aimosAlarmTrapTable.

See corresponding description in aimosAlarmListTable.

See corresponding description in aimosAlarmListTable.

See corresponding description in aimosAlarmListTable.

See corresponding description in aimosAlarmListTable.

See corresponding description in aimosAlarmListTable.

See corresponding description in aimosAlarmListTable.

See corresponding description in aimosAlarmListTable.

See corresponding description in aimosAlarmListTable.

See corresponding description in aimosAlarmListTable.

See corresponding description in aimosAlarmListTable.

See corresponding description in aimosAlarmListTable.

See corresponding description in aimosAlarmListTable.

See corresponding description in aimosAlarmListTable.

See corresponding description in aimosAlarmListTable.

See corresponding description in aimosAlarmTrapTable.

See corresponding description in aimosAlarmTrapTable.

See corresponding description in aimosAlarmListTable.

See corresponding description in aimosAlarmListTable.

See corresponding description in aimosAlarmTrapTable.

See corresponding description in aimosAlarmTrapTable.

See corresponding description in aimosAlarmTrapTable.

See corresponding description in aimosAlarmTrapTable.

See corresponding description in aimosAlarmListTable.

See corresponding description in aimosAlarmListTable.

See corresponding description in aimosAlarmListTable.

See corresponding description in aimosAlarmListTable.

See corresponding description in aimosAlarmListTable.

See corresponding description in aimosAlarmListTable.

See corresponding description in aimosAlarmListTable.

This object of type AlarmForwardingType specifies if and in what way, alarm forwarding is to be carried out: . If this object is set to disabled(0), there is no alarm forwarding even if the tables for the configuration of the alarm recipients have correct entries. . If TRAP-TYPE construct from SNMPv1 is to be used for alarm forwarding, the parameter snmpV1(1) has to be set. . The default setting of snmpV2c(2) specifies that NOTIFICATION-TYPE construct from SNMPv2, will be used for alarm forwarding. This setting refers to an organisation, not to an individual SNMP Manager. In order to exclude an individual SNMP Manager temporarily from SNMP alarm forwarding, set aimosPhoneBookActive to false. To exclude an SNMP Manager completely, delete the corresponding phone book entry from the according distribution lists (aimosAlarmRecipientListMemberTable).

After having emitted an alarm notification, the SNMP Agent expects an acknowledgement within a certain interval. This period of time is adjustable by means of this object within the range from 10 to 600 second. If there is no such acknowledgement the SNMP Agent will continue to emit the alarm until the acknowledgement is received, except in the case, that the SNMP Manager has stated its inability for acknowledgement by setting aimosPhoneBookAckCapability to false. Changes, which are made here, affect all organizations. That's why TelCo's are not allowed to make any changes here.

ATTENTION: Setting this objects value to start(5) will initiate an Alarm List Rebuild process. During this process ALL ALARM INFORMATION WILL BE DELETED ! The Alarm List Rebuild process ============================== When an employee discovers that the internal alarm table of the A.I.M.O.S. SNMP Agent is flawed, an alarm list rebuild can be triggered. Such a process may also be necessary if productive operation is to start after a test phase with an empty alarm list. The Alarm List Rebuild consists of the following steps: . A SNMP Manager sets aimosAlarmListRebuild to start(5). The logged in user must belong the Provider. . The A.I.M.O.S. SNMP Agent drops the contents of the internal alarm tables. The table is completely deleted; each alarm list entry for each organisation is removed ! . The A.I.M.O.S. SNMP Agent resets each alarm notification related counter to zero. These counters are aimosAlarmListID, aimosAlarmListAlarmEventID, aimosAlarmTrapID and each managers aimosAlarmTrapNotificationID. The values of these counters are increased by one with each new alarm, i.e. with the first alarms the value is 1. A counter of 0 is only possible after the maximum value (2^32-1) has been reached; which is, however, highly unlikely. . The aimosAlarmListRebuildInitiated notification is forwarded to all SNMP Managers configured to receive this alarm. This will result in . one new alarm list entry per affected organisation (with aimosAlarmListID and aimosAlarmListAlarmEventID each set to 1) and . one trap list entry per affected manager (with aimosAlarmTrapNotificationID set to 1 and per SNMP Manager consecutive numbered values beginning with 1 in aimosAlarmTrapID) . The A.I.M.O.S. devices are informed about the rebuild in order to reset its internal alarm tables, too. The devices will report still existing alarms as new alarms immediately. . Suppress forwarding of further notifications to a specific manager until the manager acknowledges the aimosAlarmListRebuildInitiated notification. If the acknowledgement is missing for a specific period of time, the agent obviously emits the aimosAlarmListRebuildInitiated notification again On receipt of the aimosAlarmListRebuildInitiated notification, the SNMP Manager shall clean the internal alarm table prior to acknowledge this notification. There is no aimosAlarmCleared notification for this alarm. The alarm gets cleared on acknowledgement. Alarm notifications received after that acknowledgement needs to get acknowledged by the manager as usual; the manager is neither required nor able to distinguish if a notification is a result of the alarm list rebuild or a new (never received before) one. Changes, which are made here, affect all organizations. That's why TelCo's are not allowed to initiate an Alarm List Rebuild Process by setting this value to start(5).

This object of type OperationMode is provided to give each SNMP Manager the ability to synchronise its alarm table. Setting this value to start(5) will start the alarm list synchronisation process. If the current SNMP Manager has more than one IP address or if his phonebook entry is 127.0.0.1, the SNMP Agent cannot determine for which phonebook entry the Alarm List Resync is to be done. In such a case - either aimosPhoneBookAlarmListResync must be used - or the aimosLoginPhoneBookID should be set manually (recommended) in order to start the Alarm List Resync Process. The Alarm List Resync process ============================= When an employee discovers that the internal alarm table of the SNMP Manager is flawed, a resynchronisation of the alarm list can be initiated, which is e.g. the case when the trap count (aimosAlarmTrapNotificationID), which is continuous for each SNMP Manager, is interrupted. Each SNMP Manager receiving alarms is allowed to start a synchronisation of the alarm list. In order to do that the SNMP Manager shall first clean the internal alarm table and then request for an alarm list rebuild by setting aimosAlarmListResync to start(5). This request does not cause the agent to send a notification like the alarm list rebuild process will do, but the A.I.M.O.S. SNMP Agent will perform the following steps: . Set the value of aimosAlarmListResync to running(3) . It resets the managers aimosAlarmTrapNotificationID to zero . All alarms in the alarm list related to the specific manager will be emit with unchanged aimosAlarmListID, aimosAlarmListAlarmEventID and aimosAlarmTrapID values. The aimosAlarmTrapNotificationID is a new generated consecutive numbered value. The agent doesn't wait for acknowledgement before emitting the next notification. . If the last notification is sent to the manager, aimosAlarmListResync is set to idle(0) The manager is required to acknowledge all notifications as usual. An alarm list synchronisation neither effect the contents from the A.I.M.O.S. SNMP Agent's nor from other SNMP Manager's alarm lists except of the affected SNMP Manager's notification ID.

This area comprises all objects dealing with unit management. This introduction provides an explanation of its basic structures. For each unit type there is one general table and one table per hardware version. E.g. there is the aimosRemoteUnitTable with objects that are valid for each Remote Unit, and the aimosRemoteUnitV1Table with objects of the Remote Unit Version 1. The general table contains one OID referring to the unit-specific table. Unit Reference ============== The Index of the general tables is composed of the topological arrangement of the units, i.e. depending on the arrangement it might contain several objects. The Index of a general Remote Unit table entry (aimosRemoteUnitTable) is e.g. composed of the Index of the Master Unit (aimosMasterID of type MasterID), the Index of the SubRack Master Unit (aimosSubRackID of type SubRackID) and the Index of the Remote Unit itself (aimosRemoteID of type RemoteID), since they are arranged in this order, whereas the Master Unit itself only has one Index (aimosMasterID), because there are no higher level units. All unit-specific tables, however, are always identified by two objects, one of the UnitReference type and the other of type ValueSource. Here, it does not matter whether it is a Master Unit or a Remote Unit. Value Source ============ The unit-specific tables have three entries per unit: . one entry specifies the desired values . one entry serves to read the current values and to buffer them for subsequent access . and the third entry contains the buffered values Which one of these three entries is to be accessed is specified with the second Index of the unit-specific tables of type ValueSource. To avoid that a GET BULK results in endless hardware accesses, the A.I.M.O.S. SNMP Agent normally provides only the buffered values. Also, in case of a GET NEXT only the table entry corresponding to ValueSource cachedValue(2) is returned. Read accesses with cachedValue(2), however, are treated like accesses with actualValue(1), if no buffered values are available or if the time stamp belonging to these values was deleted. ValueSource desiredValue(3) is to be used for write access. However, the A.I.M.O.S. SNMP Agent also accepts write access to table entries with ValueSource cachedValue(2). This is treated as if the write access was made with desiredValue(3). Values ====== The unit specific tables comprise objects containing various types of status information. Due to performance reasons, values of the same 'topic' are put together on a logic basis. Such logical object groups can be recognised by the name. E.g. the aimosSubRackV1Table comprises the following objects regarding attenuation: . aimosSubRackV1AttenuationAge . aimosSubRackV1AttenuationAmp1DL . aimosSubRackV1AttenuationAmp1UL . aimosSubRackV1AttenuationAmp2DL . aimosSubRackV1AttenuationAmp2UL . aimosSubRackV1AttenuationAmp3DL . aimosSubRackV1AttenuationAmp3UL These values are always dealt with together, i.e. if one of these values is to be read directly by the Master Controller, all the other values will be read, too. The time of this access is recorded in the age-object belonging to each status group. Time objects can be set to 0. This serves to prompt the A.I.M.O.S. SNMP Agent to get the current values with the next access to a cachedValue(2)-instance.

This object of type MasterID is used in order to create new Master Unit table entries. Its value has to be used as the identifier (aimosMasterID) of the new Master Unit.

This table contains hardware revision independent information's about Master Units including its Master Controller. A Master Unit consists of up to 127 Remote Units. Insert rows: set aimosMasterAddress. to the master units ip address and port Delete rows: set aimosMasterAddress. to 'delete' (without quotation marks) TelCo's are not allowed to insert or delete rows respective Master Units.

see description for table entry...

This object of type MasterID uniquely identifies the Master Controller within the OMC. aimosNextMasterID tells you the value to be used in row creation.

This object of type RDN shows the Relative Distinguished Name which consists of the object type and an object instance divided by the Distinguished Name Separator defined in aimosOrgDNSeparator. (e.g. RDN: MC=11)

This object of type SDN shows the System Distinguished Name which consists of a chaining of all RDN's all the way down from the OMC point of view to the desired unit. The RDN's are divided by the Distinguished Name Concatenator defined in aimosOrgDNConcatenator. (e.g. SDN for MC=11: OMC=1,MC=11)

This object of type IdentNo carries the Mikom Identification Number of the Master Controller.

This object of type SerialNo represents the Mikom Serial Number of the Master Controller.

This object of type Text lays down additional information to be provided with each notification sent to any SNMP Manager. The SNMP Agent makes this information available in the object aimosAlarmListCustomerMasterInfo of messages, which concern these Master Controller or subordinated devices like Sub Rack Master Units and Remote Units.

This object of type Text is a textual description of the place, where the Master Unit is located.

This object of type Text gives the ability to store any unit related text.

This object of type Coordinates carries co-ordinates of Master Unit location.

This object of type RowPointer provides the OID where to find hardware specific information. In the first release of A.I.M.O.S. this object will point to the appropriate instance of the columnar object aimosMasterV1UnitReference. That object contains the Master Unit's UnitReference.

This object of type IPAddressAndPort provides the Master Controllers IP address and port number. When a new Master Controller was integrated into the network by the provider, it can be integrated into the MIB, in a way that the A.I.M.O.S. SNMP Agent can answer the corresponding requests and forward alarms. The only required information is the IP address of the Master Controller and the port number where the controller software waits for incoming connections. The default is 7420. Only users of the provider are entitled to integrate Master Controllers into the MIB. In order to create a new Master Controller in the table aimosMasterUnitTable the following steps are required: . aimosInitiallyMasterLoginUserName and aimosInitiallyMasterLoginPassword should correspond to the User name and password set at the Master Controller. . aimosOMCConnectorAddress should contain the IP address and the IP Port under which the OMC Connector can be reached. . aimosNextMasterID must be queried, in order to identify the Index to be used for creating the table entry. . The returned ID is used to set aimosMasterAddress to the IP address and Port of the Master Controller. IP address and Port have to be separated by colons. If the Standard-Port 7420 is used, the port number information (and the colon) is dispensable. aimosMasterState states the success of the Master Controller integration. The desired value is properlySet(7). If not please refer to the DESCRIPTION clause for the next object (aimosMasterState). It describes, how the success of the MIB integration can be examined. Set this value to 'delete' (without quotation marks) in order to delete a Master Controller's table entry. Changes, which are made here, affect all organizations. That's why TelCo's are not allowed to make any changes here.

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.

This object of type GUID is a globally unambiguous name for the Master Controller. This is not redundant with regard to the aimosMasterID, for if a Master Controller is to be exchanged one day, the new one will certainly have another GUID while the aimosMasterID remains the same.

This object of type UserName is the user name (max. length is 20 characters) used by the OMC for establishing a login with the Master Controller. When a new table entry is made, the user name is determined by the contents of aimosInitiallyMasterLoginUserName.

This object of type ControllerPassword contains the password for establishing a login with the Master Controller. The password can be read but the A.I.M.O.S. SNMP Agent only displays stars ('*') instead of the actual password. When a new table entry is made, the password is determined by the contents of aimosInitiallyMasterLoginPassword.

This table contains hardware revision independent information's about the SubRack Master Unit. Insert rows: must only be done by system Delete rows: must only be done by system

see description for table entry...

This object of type SubRackID uniquely identifies the Sub Rack Master Unit within its parent, a Master Unit.

This object of type RDN shows the Relative Distinguished Name which consists of the object type and an object instance divided by the Distinguished Name Separator defined in aimosOrgDNSeparator. (e.g. RDN: SRMU=19)

This object of type SDN shows the System Distinguished Name which consists of a chaining of all RDN's all the way down from the OMC point of view to the desired unit. The RDN's are divided by Distinguished Name Concatenator defined in aimosOrgDNConcatenator. (e.g. SDN for SRMU=19 of MC 11: OMC=1,MC=11,SRMU=19)

This object of type IdentNo carries the Mikom Identification Number of the Sub Rack Master Unit.

This object of type SerialNo represents the Mikom Serial Number of the Sub Rack Mater Unit.

This object of type Text lays down additional information to be provided with each notification sent to any SNMP Manager. The SNMP Agent makes this information available in the object aimosAlarmListCustomerSubRackInfo of messages, which concern these Sub Rack Master Unit or subordinated devices like Remote Units.

This object of type Text is a textual description of the place, where the Sub Rack Master Unit is located.

This object of type Text gives the ability to store any unit related text.

This object of type Coordinates carries co-ordinates of Sub Rack Master Unit location.

This object of type RowPointer provides the OID where to find hardware specific information. In the first release of A.I.M.O.S. this object will point to the appropriate instance of the columnar object aimosSubRackV1UnitReference. That object contains the Sub Rack Master Unit's UnitReference.

This table contains hardware revision independent information's about Remote Units. Insert rows: must only be done by system Delete rows: must only be done by system

see description for table entry...

This object of type RemoteID uniquely identifies the Remote Unit within the connected Sub Rack Master Unit.

This object of type RDN shows the Relative Distinguished Name which consists of the object type and an object instance divided by the Distinguished Name Separator defined in aimosOrgDNSeparator. (e.g. RDN: RU=1)

This object of type SDN shows the System Distinguished Name which consists of a chaining of all RDN's all the way down from the OMC point of view to the desired unit. The RDN's are divided by Distinguished Name Concatenator defined in aimosOrgDNConcatenator. (e.g. SDN for a single RU connected to SRMU 23 of MC 11: OMC=1,MC=11,SRMU=23,RU=1)

This object of type IdentNo carries the Mikom Identification Number of the Remote Unit.

This object of type SerialNo represents the Mikom Serial Number of the Remote Unit.

This object of type Text lays down additional information to be provided with each notification sent to any SNMP Manager. The SNMP Agent makes this information available in the object aimosAlarmListCustomerRemoteInfo of messages, which concern these Remote Unit or subordinated devices like GSM NSO's and UMTS NSO's.

This object of type Text is a textual description of the place, where the Remote Unit is located.

This object of type Text gives the ability to store any unit related text.

This object of type Coordinates carries co-ordinates of Remote Unit location.

This object of type RowPointer provides the OID where to find hardware specific information. In the first release of A.I.M.O.S. this object will point to the appropriate instance of the columnar object aimosRemoteV1UnitReference. That object contains the Remote Unit's UnitReference.

This table contains hardware revision independent information's about GSM NSO's. Insert rows: must only be done by system Delete rows: must only be done by system

see description for table entry...

This object of type NSOID uniquely identifies the GSM NSO within the connected Remote Unit.

This object of type RDN shows the Relative Distinguished Name which consists of the object type and an object instance divided by the Distinguished Name Separator defined in aimosOrgDNSeparator. (e.g. RDN: NSOG=1)

This object of type SDN shows the System Distinguished Name which consists of a chaining of all RDN's all the way down from the OMC point of view to the desired unit. The RDN's are divided by Distinguished Name Concatenator defined in aimosOrgDNConcatenator. (e.g. SDN for the GSM NSO at a single RU connected to SRMU 23 of MC 11: OMC=1,MC=11,SRMU=23,RU=1,NSOG=1)

This object of type IdentNo carries the Mikom Identification Number of the GSM NSO.

This object of type SerialNo represents the Mikom Serial Number of the GSM NSO.

This object of type Text lays down additional information to be provided with each notification sent to any SNMP Manager. Since the GSM NSO is located in the Remote Unit, this objects value is identical to the aimosRemoteTrapInfo's value.

This object of type Text is a textual description of the place, where the GSM NSO is located. Since the GSM NSO is located in the Remote Unit, this object's value is identical to aimosRemoteLocation's value.

This object of type Text gives the ability to store any unit related text.

This object of type Coordinates carries co-ordinates of GSM NSO location.

This object of type RowPointer provides the OID where to find hardware specific information. In the first release of A.I.M.O.S. this object will point to the appropriate instance of the columnar object aimosGSMNSOV1UnitReference. That object contains the GSM NSO's UnitReference.

This object of type RowPointer shows the OID, which provides measurement data of GSM NSO. In the first release of A.I.M.O.S. this object will point to directly preceding the first appropriate instance of the columnar object aimosGSMNSODataV1ID.

This table contains hardware revision independent information's about UMTS NSO's. Insert rows: must only be done by system Delete rows: must only be done by system

see description for table entry...

This object of type NSOID uniquely identifies the UMTS NSO within the connected Remote Unit.

This object of type RDN shows the Relative Distinguished Name which consists of the object type and an object instance divided by the Distinguished Name Separator defined in aimosOrgDNSeparator. (e.g. RDN: NSOU=1)

This object of type SDN shows the System Distinguished Name which consists of a chaining of all RDN's all the way down from the OMC point of view to the desired unit. The RDN's are divided by Distinguished Name Concatenator defined in aimosOrgDNConcatenator. (e.g. SDN for the UMTS NSO at a single RU connected to SRMU 23 of MC 11: OMC=1,MC=11,SRMU=23,RU=1,NSOU=1)

This object of type IdentNo carries the Mikom Identification Number of the UMTS NSO.

This object of type SerialNo represents the Mikom Serial Number of the UMTS NSO.

This object of type Text lays down additional information to be provided with each notification sent to any SNMP Manager. Since the UMTS NSO is located in the Remote Unit, this objects value is identical to the aimosRemoteTrapInfo's value.

This object of type Text is a textual description of the place, where the UMTS NSO is located. Since the UMTS NSO is located in the Remote Unit, this object's value is identical to aimosRemoteLocation's value.

This object of type Text gives the ability to store any unit related text.

This object of type Coordinates carries co-ordinates of UMTS NSO location.

This object of type RowPointer provides the OID where to find hardware specific information. In the first release of A.I.M.O.S. this object will point to the appropriate instance of the columnar object aimosUMTSNSOV1UnitReference. That object contains the UMTS NSO's UnitReference.

This object of type RowPointer shows the OID, which provides measurement data of UMTS NSO. In the first release of A.I.M.O.S. this object will point to directly preceding the first appropriate instance of the columnar object aimosUMTSNSODataV1ID.

This object of type CableID has to be used in order to create new entries in aimosCableTable. The value has to be used as the identifier for new entries.

This table contains information's about fibre-optic cables used in interconnection between Remote Units and SubRack Master Units. This information is transmitted as part of traps and, thus offers the possibility to recognise a cable damage in case several Remote Units that all use the same cable show a failure. If this information is not necessary this table may be left empty. Insert rows: set aimosCableCode. to the cable's code Delete rows: set aimosCableCode. to 'delete' (without quotation marks) TelCo's are not allowed to insert or delete rows.

see description for table entry...

This object of type CableID is an unique identifier for cable table entries. aimosNextCableID tells you the value to be used in cable table entry creation.

This value of type CableCode holds the textual identification / representation of a specific cable. Set this value to 'delete' (without quotation marks) in order to delete this entry. Changes, which are made here, affect all organizations. That's why TelCo's are not allowed to make any changes here.

In aimosCableTrapInfo of type Text a freely definable identification can be entered, by which the cable can be identified. This identifier is transmitted with the alarm notifications referring to A.I.M.O.S. units (aimosAlarmNew, aimosAlarmChanged and aimosAlarmCleared) in the object aimosAlarmListCustomerCableInfo. In this text, the wildcard character %s can be used. It has the effect that at the according position in the traps the contents of the object aimosCableUsageFibreCode are inserted. In this way, the cable identification can be extended by the corresponding core identifier. Attention: If aimosCableUsageAlternativeTrapInfo contains text, that text will be used for the creation of the aimosAlarmListCustomerCableInfo, thus; aimosCableTrapInfo will then be without meaning.

This object of type Text is a textual description of the place, where the cable is located. Changes, which are made here, affect all organizations. That's why TelCo's are not allowed to make any changes here.

This object of type Text gives the ability to store any unit related text. Changes, which are made here, affect all organizations. That's why TelCo's are not allowed to make any changes here.

This table contains information as to which cable or even which cores of a cable were used to connect a certain Sub Rack Master Unit to a certain Remote Unit. This information is transmitted with the traps and is designed to indicate a cable damage in case several Remote Units that all use the same cable show a failure at the same time. If this information is not required, the table can be ignored. Insert rows: set aimosCableUsageCableID.. to the aimosCableID of the used cable Delete rows: set aimosCableUsageCableID.. to zero TelCo's are not allowed to insert or delete rows.

see description for table entry...

This object is of type UnitReference and identifies the Remote Unit to which the current table entry does refer.

This object determines the sequence of cables used in order to connect the Sub Rack Master Unit with a specific Remote Unit. The cable directly connected to the Sub Rack Master Unit get number one. The numbers increase by one with the distance from the Sub Rack Master Unit.

This object of type CableID shows which cable was used to connect the Remote Unit identified by aimosCableUsageRemoteUnitReference with the SubRack Master Unit. Setting this value to 0 deletes the table entry.

This object of type CableCode can be used to identify the cores used in the cable. This identification can be taken over into the object aimosAlarmListCustomerCableInfo of several alarm traps by entering the wildcard character %s in aimosCableTrapInfo.

In aimosCableUsageAlternativeTrapInfo of type Text a freely definable identification for identifying cable and used core can be entered. This identification is transmitted with the alarm notifications referring to A.I.M.O.S. units (aimosAlarmNew, aimosAlarmChanged and aimosAlarmCleared), in the object aimosAlarmListCustomerCableInfo. If this object is used, object aimosCableTrapInfo remains without meaning.

This table contains information's about Master Units with hardware revision 1. Insert rows: must only be done by system Delete rows: must only be done by system

see description for table entry...

This object of type UnitReference is the first index of this table. It unambiguously identifies the unit, independent of its kind (Master Unit, Sub Rack Master Unit, Remote Unit,...).

This object of type ValueSource is the second index in this table. It indicates, which value is to be addressed (actual, cached or desired value): . actual : An access to the hardware takes place in order to query the current values. These values are stored in the SNMP Agents local database. Actual values are read only. . cached : The values stored with the last hardware access are indicated. This is the default in order to shorten the period of reply. If the associated age value is missing, then the access is treated in such a way, as if actual one would have indicated. Cached values are read only (see remark below). . desired: Has to be used, if values on the hardware are to be changed. Remark: Although write accesses on cached values do not make a sense, are they permitted in order to facilitate handling with the MIB. Write accesses on cached values are treated in such a way, as if desired one would have indicated.

Alternatively to a regular polling of the Master Controllers by an SNMP Manager, the Master Controller is capable of sending a regular 'I'm-alive-message' to the A.I.M.O.S. SNMP Agent. In this way, the A.I.M.O.S. SNMP Agent will recognise a failure of the Master Controller when the message is no longer sent and can consequently generate and send out a aimosAlarmNew notification with the objects aimosAlarmListAlarmID set to alarmHeartbeatMissing(63) and aimosAlarmListSpecificProblem set to 8888. aimosMasterV1HeartbeatInterval is an object of type WeekMinutes, by which the interval at which the Master Controller is to send this 'life sign' can be set. Values from 0 up to 10.080 are allowed. Setting 0 deactivates the Heartbeat feature, the highest setting 10.080 sets the interval to one week.

This object of type WeekMinutes offers the possibility to set a certain waiting time. This is required to compensate the differing latency periods of the Master Controller and the A.I.M.O.S. SNMP Agent. The default value of 1 minute should generally be sufficient. Only in case of a very slow connection establishment or if the Master Controller / A.I.M.O.S. SNMP Agent is very busy, this value should be increased to avoid false alarms.

This object of type VariableTime provides the time when the Master Controller sent the last life sign. It does not make sense to read this value to an instance with aimosMasterV1ValueSource of actualValue(1); there is only one value for the instance cachedValue(2).

This table contains information's about SubRack Master Units with hardware revision 1. Insert rows: must only be done by system Delete rows: must only be done by system

see description for table entry...

This object of type UnitReference is the first index of this table. It unambiguously identifies the unit, independent of its kind (Master Unit, Sub Rack Master Unit, Remote Unit,...).

This object of type ValueSource is the second index in this table. It indicates, which value is to be addressed (actual, cached or desired value): . actual : An access to the hardware takes place in order to query the current values. These values are stored in the SNMP Agents local database. Actual values are read only. . cached : The values stored with the last hardware access are indicated. This is the default in order to shorten the period of reply. If the associated age value is missing, then the access is treated in such a way, as if actual one would have indicated. Cached values are read only (see remark below). . desired: Has to be used, if values on the hardware are to be changed. Remark: Although write accesses on cached values do not make a sense, are they permitted in order to facilitate handling with the MIB. Write accesses on cached values are treated in such a way, as if desired one would have indicated.

In both the uplink (UL) and the downlink (DL) path for each of the three bands supported by the three amplifiers (1 to 3), the attenuation of the corresponding attenuator (located in the optical device) responsible for Autolevelling can be read-off or (only in case of a provider) be changed. For this purpose, the MIB contains the following six objects: . aimosSubRackV1AttenuationAmp1DL . aimosSubRackV1AttenuationAmp1UL . aimosSubRackV1AttenuationAmp2DL . aimosSubRackV1AttenuationAmp2UL . aimosSubRackV1AttenuationAmp3DL . aimosSubRackV1AttenuationAmp3UL. These objects are of the Attenuation type and contain the attenuation value in dB. The time when the values were last read is recorded in the object aimosSubRackV1AttenuationAge of the VariableTime type. This value can be set to empty text in order to prompt the Controller to query the values anew with the next request to a cachedValue(2)-instance directly at the Master Controller.

Attenuation on amplifier 1 downlink. The object aimosSubRackV1AttenuationAge indicates the age of this information. Changes, which are made here, affect the hardware. That's why TelCo's are not allowed to make any changes here.

Attenuation on amplifier 1 uplink. The object aimosSubRackV1AttenuationAge indicates the age of this information. Changes, which are made here, affect the hardware. That's why TelCo's are not allowed to make any changes here.

Attenuation on amplifier 2 downlink. The object aimosSubRackV1AttenuationAge indicates the age of this information. Changes, which are made here, affect the hardware. That's why TelCo's are not allowed to make any changes here.

Attenuation on amplifier 2 uplink. The object aimosSubRackV1AttenuationAge indicates the age of this information. Changes, which are made here, affect the hardware. That's why TelCo's are not allowed to make any changes here.

Attenuation on amplifier 3 downlink. The object aimosSubRackV1AttenuationAge indicates the age of this information. Changes, which are made here, affect the hardware. That's why TelCo's are not allowed to make any changes here.

Attenuation on amplifier 3 uplink. The object aimosSubRackV1AttenuationAge indicates the age of this information. Changes, which are made here, affect the hardware. That's why TelCo's are not allowed to make any changes here.

In both the uplink (UL) and the downlink (DL) path for each of the three bands provided by the three amplifiers (1 to 3), the gain offset can be read-off and is adjustable by the provider. For this the MIB contains the following six objects: . aimosSubRackV1GainOffsetAmp1DL . aimosSubRackV1GainOffsetAmp1UL . aimosSubRackV1GainOffsetAmp2DL . aimosSubRackV1GainOffsetAmp2UL . aimosSubRackV1GainOffsetAmp3DL . aimosSubRackV1GainOffsetAmp3UL. These objects are of the GainOffset type and contain the gain offset values. The time when the values were last read is recorded in the object aimosSubRackV1GainOffsetAge of the VariableTime type. This value can be set to empty text in order to prompt the Controller to query the values anew with the next request to a cachedValue(2)-instance directly at the Master Controller.

Gain offset on amplifier 1 downlink. The object aimosSubRackV1GainOffsetAge indicates the age of this information. Changes, which are made here, affect the hardware. That's why TelCo's are not allowed to make any changes here.

Gain offset on amplifier 1 uplink. The object aimosSubRackV1GainOffsetAge indicates the age of this information. Changes, which are made here, affect the hardware. That's why TelCo's are not allowed to make any changes here.

Gain offset on amplifier 2 downlink. The object aimosSubRackV1GainOffsetAge indicates the age of this information. Changes, which are made here, affect the hardware. That's why TelCo's are not allowed to make any changes here.

Gain offset on amplifier 2 uplink. The object aimosSubRackV1GainOffsetAge indicates the age of this information. Changes, which are made here, affect the hardware. That's why TelCo's are not allowed to make any changes here.

Gain offset on amplifier 3 downlink. The object aimosSubRackV1GainOffsetAge indicates the age of this information. Changes, which are made here, affect the hardware. That's why TelCo's are not allowed to make any changes here.

Gain offset on amplifier 3 uplink. The object aimosSubRackV1GainOffsetAge indicates the age of this information. Changes, which are made here, affect the hardware. That's why TelCo's are not allowed to make any changes here.

aimosSubRackV1TemperatureBoard is an object of the TemperatureStatus type and contains the temperature measured at the SubRack Master Unit, in degrees Celsius. The time when the value was last read is recorded in the object aimosSubRackV1TemperatureAge of the VariableTime type. This value can be set to empty text in order to prompt the Controller to query the temperature anew with the next request to a cachedValue(2)-instance directly at the Master Controller.

Temperature in degrees centigrade measured at the Sub Rack Master Unit. The object aimosSubRackV1TemperatureAge indicates the age of this information.

Both Sub Rack Master Unit and each of its connected Remote Units have up to three amplifiers. The objects . aimosSubRackV1Amplifier1BandName . aimosSubRackV1Amplifier2BandName . aimosSubRackV1Amplifier3BandName contain the frequency band names, which are strengthened by the Sub Rack Master Units and its connected Remote Units amplifiers. Each of the object is of type Text with up to 10 characters. The time when the values were last read is recorded in the object aimosSubRackV1AmplifierBandNamesAge of the VariableTime type. This value can be set to empty text in order to prompt the Controller to query the names anew with the next request to a cachedValue(2)-instance directly at the Master Controller.

States which frequency band (UMTS, GSM1800, GSM900, or any else) is assigned to amplifier 1. The object aimosSubRackV1AmplifierBandNamesAge indicates the age of this information.

States which frequency band (UMTS, GSM1800, GSM900, or any else) is assigned to amplifier 2. The object aimosSubRackV1AmplifierBandNamesAge indicates the age of this information.

States which frequency band (UMTS, GSM1800, GSM900, or any else) is assigned to amplifier 3. The object aimosSubRackV1AmplifierBandNamesAge indicates the age of this information.

This table contains information's about Remote Units with hardware revision 1. Insert rows: must only be done by system Delete rows: must only be done by system

see description for table entry...

This object of type UnitReference is the first index of this table. It unambiguously identifies the unit, independent of its kind (Master Unit, Sub Rack Master Unit, Remote Unit,...).

This object of type ValueSource is the second index in this table. It indicates, which value is to be addressed (actual, cached or desired value): . actual : An access to the hardware takes place in order to query the current values. These values are stored in the SNMP Agents local database. Actual values are read only. . cached : The values stored with the last hardware access are indicated. This is the default in order to shorten the period of reply. If the associated age value is missing, then the access is treated in such a way, as if actual one would have indicated. Cached values are read only (see remark below). . desired: Has to be used, if values on the hardware are to be changed. Remark: Although write accesses on cached values do not make a sense, are they permitted in order to facilitate handling with the MIB. Write accesses on cached values are treated in such a way, as if desired one would have indicated.

aimosRemoteUnitV1NominalTemperature is an object of type NominalTemperature, where the temperature to be obtained by fan control is entered in degrees centigrade. The time when the value was last read is recorded in the object aimosRemoteUnitV1NominalTemperatureAge of the VariableTime type. This value can be set to empty text in order to prompt the Controller to query the nominal temperature anew with the next request to a cachedValue(2)-instance directly at the Master Controller.

Temperature to be obtained by fan control in degrees centigrade. The object aimosRemoteV1NominalTemperatureAge indicates the age of this information. Changes, which are made here, affect the hardware. That's why TelCo's are not allowed to make any changes here.

The Remote Unit has five temperature probes. For this, the MIB contains the following objects: . aimosRemoteV1TemperatureAmp1 . aimosRemoteV1TemperatureAmp2 . aimosRemoteV1TemperatureAmp3 . aimosRemoteV1TemperatureBoard . aimosRemoteV1TemperaturePowerSupply These objects are of type TemperatureStatus and contain the temperatures measured at the according probe in degrees centigrade. The time when the values were last read is recorded in the object aimosRemoteV1TemperatureAge of type VariableTime. This value can be set to empty text in order to prompt the Controller to query the temperatures anew with the next request to a cachedValue(2)-instance directly at the Master Controller.

Amplifier 1 temperature in degrees centigrade. The object aimosRemoteV1TemperatureAge indicates the age of this information.

Amplifier 2 temperature in degrees centigrade. The object aimosRemoteV1TemperatureAge indicates the age of this information.

Amplifier 3 temperature in degrees centigrade. The object aimosRemoteV1TemperatureAge indicates the age of this information.

Board temperature in degrees centigrade. The object aimosRemoteV1TemperatureAge indicates the age of this information.

Power supply temperature in degrees centigrade. The object aimosRemoteV1TemperatureAge indicates the age of this information.

The downlink amplifiers for each one of the three frequency bands supported by the Remote Unit can be switched individually. For this, the MIB contains the following three objects: . aimosRemoteV1Amplifier1State . aimosRemoteV1Amplifier2State . aimosRemoteV1Amplifier3State These objects are of the Boolean type and show whether the corresponding amplifier is active or not. The time when the value was last read is recorded in the object aimosRemoteV1AmplifierStateAge of the type VariableTime. This value can be set to empty text in order to prompt the Controller to query the values anew with the next request to a cachedValue(2)-instance directly at the Master Controller.

Denotes if the amplifier 1 is active or not. The object aimosRemoteV1AmplifierStateAge indicates the age of this information. Changes, which are made here, affect the hardware. That's why TelCo's are not allowed to make any changes here.

Denotes if the amplifier 2 is active or not. The object aimosRemoteV1AmplifierStateAge indicates the age of this information. Changes, which are made here, affect the hardware. That's why TelCo's are not allowed to make any changes here.

Denotes if the amplifier 3 is active or not. The object aimosRemoteV1AmplifierStateAge indicates the age of this information. Changes, which are made here, affect the hardware. That's why TelCo's are not allowed to make any changes here.

The output power at the downlink amplifiers for each one of the three frequency bands supported by the Remote Unit can be read off individually. For this, the MIB contains the following three objects: . aimosRemoteV1Amplifier1Power . aimosRemoteV1Amplifier2Power . aimosRemoteV1Amplifier3Power These objects are of the AmplifierPower type and show the output power of the corresponding amplifier in one tenth of dB. The time when the value was last read is recorded in the object aimosRemoteV1AmplifierPowerAge of type VariableTime. This value can be set to empty text in order to prompt the Controller to query the values anew with the next request to a cachedValue(2)-instance directly at the Master Controller.

Power of amplifier 1 in dB. The object aimosRemoteV1AmplifierPowerAge indicates the age of this information.

Power of amplifier 2 in dB. The object aimosRemoteV1AmplifierPowerAge indicates the age of this information.

Power of amplifier 3 in dB. The object aimosRemoteV1AmplifierPowerAge indicates the age of this information.

For both the uplink (UL) and downlink (DL) paths the attenuation of the corresponding attenuator (located at the optical unit) required for Autolevelling for each one of the three frequency bands can be read off individually or may be changed (only by the provider). For this, the MIB contains the following six objects: . aimosRemoteV1AttenuationAmp1DL . aimosRemoteV1AttenuationAmp1UL . aimosRemoteV1AttenuationAmp2DL . aimosRemoteV1AttenuationAmp2UL . aimosRemoteV1AttenuationAmp3DL . aimosRemoteV1AttenuationAmp3UL. These objects are of the Attenuation type and contain the attenuation value in dB. The time when the value was last read is recorded in the object aimosRemoteV1AttenuationAge of type VariableTime. This value can be set to empty text in order to prompt the Controller to query the values anew with the next request to a cachedValue(2)-instance directly at the Master Controller.

Attenuation on amplifier 1 downlink. The object aimosRemoteV1AttenuationAge indicates the age of this information. Changes, which are made here, affect the hardware. That's why TelCo's are not allowed to make any changes here.

Attenuation on amplifier 1 uplink. The object aimosRemoteV1AttenuationAge indicates the age of this information. Changes, which are made here, affect the hardware. That's why TelCo's are not allowed to make any changes here.

Attenuation on amplifier 2 downlink. The object aimosRemoteV1AttenuationAge indicates the age of this information. Changes, which are made here, affect the hardware. That's why TelCo's are not allowed to make any changes here.

Attenuation on amplifier 2 uplink. The object aimosRemoteV1AttenuationAge indicates the age of this information. Changes, which are made here, affect the hardware. That's why TelCo's are not allowed to make any changes here.

Attenuation on amplifier 3 downlink. The object aimosRemoteV1AttenuationAge indicates the age of this information. Changes, which are made here, affect the hardware. That's why TelCo's are not allowed to make any changes here.

Attenuation on amplifier 3 uplink. The object aimosRemoteV1AttenuationAge indicates the age of this information. Changes, which are made here, affect the hardware. That's why TelCo's are not allowed to make any changes here.

For both the uplink (UL) and downlink (DL) paths the gain offset for each one of the three frequency bands can be read off individually or may be changed (only by the provider). For this, the MIB contains the following six objects: . aimosRemoteV1GainOffsetAmp1DL . aimosRemoteV1GainOffsetAmp1UL . aimosRemoteV1GainOffsetAmp2DL . aimosRemoteV1GainOffsetAmp2UL . aimosRemoteV1GainOffsetAmp3DL . aimosRemoteV1GainOffsetAmp3UL. These objects are of the GainOffset type and show the gain offset values. The time when the value was last read is recorded in the object aimosRemoteV1GainOffsetAge of type VariableTime This value can be set to empty text in order to prompt the Controller to query the values anew with the next request to a cachedValue(2)-instance directly at the Master Controller.

Gain offset on amplifier 1 downlink. The object aimosRemoteV1GainOffsetAge indicates the age of this information. Changes, which are made here, affect the hardware. That's why it's not allowed to make any changes here.

Gain offset on amplifier 1 uplink. The object aimosRemoteV1GainOffsetAge indicates the age of this information. Changes, which are made here, affect the hardware. That's why it's not allowed to make any changes here.

Gain offset on amplifier 2 downlink. The object aimosRemoteV1GainOffsetAge indicates the age of this information. Changes, which are made here, affect the hardware. That's why it's not allowed to make any changes here.

Gain offset on amplifier 2 uplink. The object aimosRemoteV1GainOffsetAge indicates the age of this information. Changes, which are made here, affect the hardware. That's why it's not allowed to make any changes here.

Gain offset on amplifier 3 downlink. The object aimosRemoteV1GainOffsetAge indicates the age of this information. Changes, which are made here, affect the hardware. That's why it's not allowed to make any changes here.

Gain offset on amplifier 3 uplink. The object aimosRemoteV1GainOffsetAge indicates the age of this information. Changes, which are made here, affect the hardware. That's why it's not allowed to make any changes here.

For each one of the three frequency bands supported by the Remote Unit . the output power at the downlink amplifier can be limited (DL) and . the input power at the optical interface can be limited (UL). For this, the MIB contains the following six objects: . aimosRemoteV1ALCThresholdAmp1DL . aimosRemoteV1ALCThresholdAmp1UL . aimosRemoteV1ALCThresholdAmp2DL . aimosRemoteV1ALCThresholdAmp2UL . aimosRemoteV1ALCThresholdAmp3DL . aimosRemoteV1ALCThresholdAmp3UL These objects area of type ALCThreshold and show the threshold values. The time when the value was last read is recorded in the object aimosRemoteV1ALCThresholdAge of type VariableTime. This value can be set to empty text in order to prompt the Controller to query the values anew with the next request to a cachedValue(2)-instance directly at the Master Controller.

ALC threshold on amplifier 1 downlink. The object aimosRemoteV1ALCThresholdAge indicates the age of this information. Changes, which are made here, affect the hardware. That's why it's not allowed to make any changes here.

ALC threshold on amplifier 1 uplink. The object aimosRemoteV1ALCThresholdAge indicates the age of this information. Changes, which are made here, affect the hardware. That's why it's not allowed to make any changes here.

ALC threshold on amplifier 2 downlink. The object aimosRemoteV1ALCThresholdAge indicates the age of this information. Changes, which are made here, affect the hardware. That's why it's not allowed to make any changes here.

ALC threshold on amplifier 2 uplink. The object aimosRemoteV1ALCThresholdAge indicates the age of this information. Changes, which are made here, affect the hardware. That's why it's not allowed to make any changes here.

ALC threshold on amplifier 3 downlink. The object aimosRemoteV1ALCThresholdAge indicates the age of this information. Changes, which are made here, affect the hardware. That's why it's not allowed to make any changes here.

ALC threshold on amplifier 3 uplink. The object aimosRemoteV1ALCThresholdAge indicates the age of this information. Changes, which are made here, affect the hardware. That's why it's not allowed to make any changes here.

For both the uplink and downlink paths the optical loss can be read-off via the following two objects in the MIB: . aimosRemoteV1OpticalLossDL and . aimosRemoteV1OpticalLossUL. These objects are of type OpticalLoss and show the optical loss value. The time when the value was last read is recorded in the object aimosRemoteV1OpticalLossAge of type VariableTime. This value can be set to empty text in order to prompt the Controller to query the values anew with the next request to a cachedValue(2)-instance directly at the Master Controller.

Optical loss on downlink fibre. The object aimosRemoteV1OpticalLossAge indicates the age of this information.

Optical loss on uplink fibre. The object aimosRemoteV1OpticalLossAge indicates the age of this information.

Names the output pin 1 for recognition what is connected. Changes, which are made here, affect the hardware. That's why TelCo's are not allowed to make any changes here.

Names the output pin 2 for recognition what is connected. Changes, which are made here, affect the hardware. That's why TelCo's are not allowed to make any changes here.

Names the output pin 3 for recognition what is connected. Changes, which are made here, affect the hardware. That's why TelCo's are not allowed to make any changes here.

Names the output pin 4 for recognition what is connected. Changes, which are made here, affect the hardware. That's why TelCo's are not allowed to make any changes here.

Each of the four digital outputs available at the Remote Unit can be accessed individually via one of the following four objects: . aimosRemoteV1Output1Value, . aimosRemoteV1Output2Value, . aimosRemoteV1Output3Value, . aimosRemoteV1Output4Value. These objects are of the Boolean type and determine the status of the corresponding output. The time when the value was last read is recorded in the object aimosRemoteV1OutputAge of type VariableTime. This value can be set to empty text in order to prompt the Controller to query the values anew with the next request to a cachedValue(2)-instance directly at the Master Controller.

State on external out pin 1. The object aimosRemoteV1OutputAge indicates the age of this information. Changes, which are made here, affect the hardware. That's why TelCo's are not allowed to make any changes here.

State on external out pin 2. The object aimosRemoteV1OutputAge indicates the age of this information. Changes, which are made here, affect the hardware. That's why TelCo's are not allowed to make any changes here.

State on external out pin 3. The object aimosRemoteV1OutputAge indicates the age of this information. Changes, which are made here, affect the hardware. That's why TelCo's are not allowed to make any changes here.

State on external out pin 4. The object aimosRemoteV1OutputAge indicates the age of this information. Changes, which are made here, affect the hardware. That's why TelCo's are not allowed to make any changes here.

Names the input pin 1 for recognition what is connected. Changes, which are made here, affect the hardware. That's why TelCo's are not allowed to make any changes here.

Names the input pin 2 for recognition what is connected. Changes, which are made here, affect the hardware. That's why TelCo's are not allowed to make any changes here.

Names the input pin 3 for recognition what is connected. Changes, which are made here, affect the hardware. That's why TelCo's are not allowed to make any changes here.

Names the input pin 4 for recognition what is connected. Changes, which are made here, affect the hardware. That's why TelCo's are not allowed to make any changes here.

Hardware version related informations about the GSM NSO's. Insert rows: must only be done by system Delete rows: must only be done by system

see description for table entry...

This object of type UnitReference is the first index of this table. It unambiguously identifies the unit, independent of its kind (Master Unit, Sub Rack Master Unit, Remote Unit,...).

This object of type ValueSource is the second index in this table. It indicates, which value is to be addressed (actual, cached or desired value): . actual : An access to the hardware takes place in order to query the current values. These values are stored in the SNMP Agents local database. Actual values are read only. . cached : The values stored with the last hardware access are indicated. This is the default in order to shorten the period of reply. If the associated age value is missing, then the access is treated in such a way, as if actual one would have indicated. Cached values are read only (see remark below). . desired: Has to be used, if values on the hardware are to be changed. Remark: Although write accesses on cached values do not make a sense, are they permitted in order to facilitate handling with the MIB. Write accesses on cached values are treated in such a way, as if desired one would have indicated.

Presents the unique 8 character name of the NSO.

Denotes the intervall time the NSO will restart its measurement. Note, the NSO needs approximately 60 seconds for measurement and some seconds for transmitting data to the master. So you should not determine a value smaller than 180.

Denotes if the BCCH channel will be scanned.

Cell State Bit Remark 0 CELL_SUITABLE 1 CELL_LOW_PRIORITY 2 CELL_BARRED 3 CELL_LOW_LEVEL 4 CELL_FORBIDDEN 5 CELL_OTHER Other cell states indicating an alarm state.

Channels with a lower RX level are not scanned.

Signal strength modifications within the hysteresis do not cause the NSO to send data with new signal strength values. E.g., a hysteresis of +/- 1 dB ignores signal strength modifications within a range of 2 dB. If actually the signal strength is 20, you will recognize signal strength modification if the value gets lower than 19 or higher than 21.

RX levels with a lower level indicating an alarm state.

RX levels with a higher level indicating an alarm state.

Bit Error Rates with a higher level indicating an alarm state.

GSM NSO measurement data. Insert rows: must only be done by system Delete rows: must only be done by system

see description for table entry...

Identifies the table entry. This value ist determined by the system.

Local Area Code.

Cell Identifier

Time of measurement.

Channel

Base Station Identity Code.

Cell Status

Current RX level.

Current Bit Error Rate.

Hardware version related informations about the UMTS NSO's. Insert rows: must only be done by system Delete rows: must only be done by system

see description for table entry...

This object of type UnitReference is the first index of this table. It unambiguously identifies the unit, independent of its kind (Master Unit, Sub Rack Master Unit, Remote Unit,...).

This object of type ValueSource is the second index in this table. It indicates, which value is to be addressed (actual, cached or desired value): . actual : An access to the hardware takes place in order to query the current values. These values are stored in the SNMP Agents local database. Actual values are read only. . cached : The values stored with the last hardware access are indicated. This is the default in order to shorten the period of reply. If the associated age value is missing, then the access is treated in such a way, as if actual one would have indicated. Cached values are read only (see remark below). . desired: Has to be used, if values on the hardware are to be changed. Remark: Although write accesses on cached values do not make a sense, are they permitted in order to facilitate handling with the MIB. Write accesses on cached values are treated in such a way, as if desired one would have indicated.

UMTS NSO measurement data. Insert rows: must only be done by system Delete rows: must only be done by system

see description for table entry...

Identifies the table entry. This value ist determined by the system.

This object identity provides means to execute Network Element Operations. For example it is possible to request for a reboot of a NE.

This table contains the Network Elements capable of operation execution. The following Network Elements are supported (V 2.8.0): - Node M - Node C - Node G - Node A - Node AM - MRx18 - ION-M RU - ION-M EU

see description for table entry...

This object of type UnitReference uniquely identifies the Network Element. This value is related to the column 'NE No.' of the 'Network Element List' (A.I.M.O.S. Visu).

This object of type SDN shows the System Distinguished Name which consists of a chaining of all RDN's all the way down from the OMC point of view to the desired unit. The RDN's are divided by the Distinguished Name Concatenator defined in aimosOrgDNConcatenator. (e.g. SDN for MC=11: OMC=1,MC=11)

This object of type Text contains the Network Elements TrapInfo.

This object of type Text contains the Network Elements Component Name.

This object of type Text contains the Network Elements Location.

This object of type Text contains the Network Elements Unique System ID.

This object of type Boolean indicates whether or not a Network Element (or at least one component capable of de-/activation if applicable) is active. This object will report true for a - Node M if 'Complete Network Element Active' is true - Node C if 'Complete Network Element Active' is true - Node G if 'Complete Network Element Active' is true - Node A if 'Disable Repeater' is false - Node AM if 'Disable Repeater' is false - MRx18 if at least one Segment is powered on - ION-M RU if at least one Amplifier is active - ION-M EU if at least one Amplifier is active Otherwise it will report false.

This object of type NEOperationStatus provides means to deactivate a Network Element by applying a value of neoSubmit(2). Deactivation is performed in the following way: - Node M : 'Complete Network Element Active' is set to false - Node C : 'Complete Network Element Active' is set to false - Node G : 'Complete Network Element Active' is set to false - Node A : 'Disable Repeater' is set to true - Node AM : 'Disable Repeater' is set to true - MRx18 : all Segments are powered off - ION-M RU: all Amplifiers are deactivated - ION-M EU: all Amplifiers are deactivated Furthermore its values indicates the progress of the Deactivation Command Transmission to the Network Element. If no Deactivation was initiated since Agent Startup this object's value is neoIdle(1).

This object of type Text is the textual representation of the value retunred by aimosNEOperationsDeactivateNE. In case it is neoFailed(10) a more precise description is returned.

This object of type NEOperationStatus provides means to activate a Network Element by applying a value of neoSubmit(2). Activation is performed in the following way: - Node M : 'Complete Network Element Active' is set to true - Node C : 'Complete Network Element Active' is set to true - Node G : 'Complete Network Element Active' is set to true - Node A : 'Disable Repeater' is set to false - Node AM : 'Disable Repeater' is set to false - MRx18 : all Segments are powered on - ION-M RU: all Amplifiers are activated - ION-M EU: all Amplifiers are activated Furthermore its values indicates the progress of the Activation Command Transmission to the Network Element. If no Activation was initiated since Agent Startup this object's value is neoIdle(1).

This object of type Text is the textual representation of the value retunred by aimosNEOperationsActivateNE. In case it is neoFailed(10) a more precise description is returned.

This object of type NEOperationStatus provides means to initiate a reboot of a Network Element by applying a value of neoSubmit(2). Furthermore its values indicates the progress of the Reboot Command Transmission to the Network Element. If no Reboot was initiated since Agent Startup this object's value is neoIdle(1).

This object of type Text is the textual representation of the value retunred by aimosNEOperationsReboot. In case it is neoFailed(10) a more precise description is returned.

This object of type NEOperationStatus provides means to forward a Query Alarms Command to a Network Element by applying a value of neoSubmit(2). Furthermore its values indicates the progress of the Query Alarms Command Transmission to the Network Element. If no Query Alarms has been requested since Agent Startup this object's value is neoIdle(1).

This object of type Text is the textual representation of the value retunred by aimosNEOperationsQueryAlarms. In case it is neoFailed(10) a more precise description is returned.

The A.I.M.O.S. SNMP Agent sends alarm notifications to as many alarm recipients as desired. All notifications contains the following objects: . sysUpTime duration of time the SNMP Agent is running . snmpTrapOID notification OID (note: if aimosPhoneBookInterfaceType is set to ifAimosObsolete(4) aimosTrapOID is used instead) . aimosOMCSDN name of the OMC / SNMP Agent . aimosOrgID the SNMP Managers organisation ID . aimosAlarmTrapID trap number (unambiguous from SNMP Agents view) . aimosAlarmTrapNotificationID trap number (contiguous enumerated from SNMP Managers view) . aimosAlarmListID identifies an alarm list entry . aimosAlarmListAlarmEventID contiguously enumerates alarm events, change and clear alarms has the same event ID as the raise aimosAgentAnnouncement notifications have afterwards the following object: . aimosAgentState indicates of what the A.I.M.O.S. SNMP Agent is about to do aimosAlarmNew, aimosAlarmChanged and aimosAlarmCleared notifications have afterwards the following objects: . aimosAlarmListAlarmID kind of alarm . aimosAlarmListEventType . aimosAlarmListEventTime . aimosAlarmListProbableCause compliant to X.733 with additions . aimosAlarmListSpecificProblem . aimosAlarmListSeverity compliant to X.733 with one addition . aimosAlarmListTrendIndication . aimosAlarmListAdditionalText . aimosAlarmListSDN unique name of the affected device . aimosAlarmListCustomerMasterInfo custom name for the affected Master Unit . aimosAlarmListCustomerSubRackInfo custom name for the affected Sub Rack Master Unit . aimosAlarmListCustomerCableInfo custom names of the cables used in the interconnection between Master & Remote Unit . aimosAlarmListCustomerRemoteInfo custom name for the affected Remote Unit aimosAlarmCleared notifications have afterwards the following object: . aimosAlarmListClearReason the reason why alarm has gone All alarms end with the following objects: . aimosAcknowledgementOID acknowledgement OID value . snmpTrapEnterprise enterprise OID value (note: if aimosPhoneBookInterfaceType is set to ifAimosObsolete(4) aimosTrapEnterprise is used instead) If aimosPhoneBookInterfaceType is on its default value ifMIBDefault(0), then each of the object mentioned before has an appropriate instance identifier. That is, aimosOrgID has the OrgID itself as instance identifier and, for example, aimosAlarmListID has aimosOrgID and aimosAlarmListID as instance identifier, since these objects are defined in that manner. If aimosPhoneBookInterfaceType is set to ifAimosObsolete(4), then each object in the alarm notification has an instance identifier of zero. The only exception from this rule is aimosTrapOID. This object has no instance identifier. After having emitted an alarm notification with the objects mentioned before included, the A.I.M.O.S. SNMP Agent expects an acknowledgement within a certain period of time. This interval can be specified in aimosAlarmAckExpectInterval. Each SNMP Manager must confirm the receipt of the notification unless its inability of acknowledgements is indicated by appropriate settings made to aimosPhoneBookAckCapability. The acknowledgement will be done by setting aimosAlarmTrapAcknowledgementState to acknowledged(2). This OID is indexed by aimosOrgID, aimosAlarmTrapID and aimosAlarmListID. The notification makes the OID required for acknowledgement (object including instance identifiers) available in the aimosAcknowledgementOID. If a set request is made to aimosAlarmTrapAcknowledgementState, additionally aimosAlarmTrapAcknowledgementUser is set to the current user and aimosAlarmTrapAcknowledgementTime is set to the time of the acknowledgement. If an expected acknowledgement is missed by the A.I.M.O.S. SNMP Agent it will send the alarm repeatedly again until the alarm is acknowledged by the affected SNMP Manager. The objects contents of a re-sending alarm notification are identical to the preceding ones, especially the counter values (aimosAlarmTrapID, aimosAlarmTrapNotificationID, aimosAlarmListID, aimosAlarmListAlarmEventID). Each SNMP Manager may examine the incoming alarms notification ID. If it is not incremented by one since the last notification, it is an indication for missing notifications. The SNMP manager should wait a while until the SnMP Agent has resend the missing notification(s) unless acknowledgement is deactivated (aimosPhoneBookAckCapability is false(0)). In the latter case the SNMP Manager should synchronize its alarm table with the SNMP Agent ones by setting aimosPhoneBookAlarmListResync to start(5).

This value indicates what the agent is about to do. Please refer also to the DESCRIPTION clause for aimosAgentAnnouncement.

This object comprises the OID, the value of which must be set to acknowledged(2) in order to confirm the alarm reception (i.e. perform the acknowledgement). If a SNMP Manager is not able to perform an acknowledgement, it should set aimosPhoneBookAckCapability to false.

This object was intended to carry the entrerprise OID value in notifications, although the existing object snmpTrapEnterprise had already exactly this task. This object is used in notifications instead of snmpTrapEnterprise if aimosPhoneBookInterfaceType is set to ifAimosObsolete(4) for compatibility reasons to the first version of this MIB. It is recommended to leave aimosPhoneBookInterfaceType on its default value ifMIBDefault(0). In that case snmpTrapEnterprise is used.

A aimosAgentAnnouncement notification is emitted by the agent if it is put in or out of operation. aimosAgentState of type AgentState indicates what actually happens. aimosAgentAnnouncement notification has no aimosAlarmCleared notification. Cold Start ========== A aimosAgentState of snmpColdStart(1) indicates, that the agent has been started. Already existing Sessions are invalid; requests will be responded by authorisation errors. The relevant alarm list entry contains aimosAlarmListAlarmID set to alarmOMC(62) and aimosAlarmListSpecificProblem set to 8880. Pause ===== A aimosAgentState of snmpPause(2) signifies that the A.I.M.O.S. SNMP Agent is proceed to pause its activity. Even though the A.I.M.O.S. SNMP Agent's process will remain active, requests will result in time outs until aimosAgentAnnouncement with aimosAgentState set to snmpResume(3) is forwarded. The relevant alarm list entry contains aimosAlarmListAlarmID set to alarmOMC(62) and aimosAlarmListSpecificProblem set to 8887. The agent is waiting a certain period of time for acknowledgements before going in pause mode. If the agent comes back in operation, it will recognise missing acknowledgements and continue sending out aimosAgentAnnouncement notifications regarding the AgentState of snmpPause(2) additional to the aimosAgentAnnouncement notifications regarding the AgentState of snmpResume(3). This may prevent the manager from requesting a synchronisation of the alarm list due to the gap in the sequence of notification ID's. Resume ====== A aimosAgentState of snmpResume(3) signifies that the A.I.M.O.S. SNMP Agent is resuming its activity. Already existing Sessions remain valid, except they were not used for a period longer than the one specified in aimosSessionTimeout. The relevant alarm list entry contains aimosAlarmListAlarmID set to alarmOMC(62) and aimosAlarmListSpecificProblem set to 8881. Shut Down ========= A aimosAgentState of snmpShutDown(4) signifies that the A.I.M.O.S. SNMP Agent is about to shut down. The A.I.M.O.S. SNMP Agent waits a certain time for the SNMP Managers to be able to acknowledge this notification before actually shutting down. If the process terminates, all Sessions are invalidated. The agent doesn't respond to requests until aimosAgentAnnouncement with aimosAgentState set to snmpColdStart(1) is forwarded. The relevant alarm list entry contains aimosAlarmListAlarmID set to alarmOMC(62) and aimosAlarmListSpecificProblem set to 8889. If the A.I.M.O.S. SNMP Agent comes back in operation, it will recognise missing acknowledgements and continue sending out aimosAgentAnnouncement notifications regarding the AgentState of snmpShutDown(4) additional to the aimosAgentAnnouncement notifications regarding the AgentState of snmpColdStart(1). This may prevent the manager from requesting a synchronisation of the alarm list due to the gapin the sequence of notification ID's.

The aimosAlarmNew notification is used when a new alarm appears. It contains a new aimosAlarmListAlarmEventID. The aimosAlarmNew notification causes the A.I.M.O.S. SNMP Agent to create . one alarm list entry per affected organisation and . one alarm trap list entry per affected SNMP Manager containing the values of the notification objects.

The aimosAlarmChanged notification is used when the severity of an uncleared alarm has changed. The alarm is correlated with the aimosAlarmNew notification by identical values in aimosAlarmListAlarmEventID. The aimosAlarmChanged notification causes the A.I.M.O.S. SNMP Agent to create . one alarm list entry per affected organisation and . one alarm trap list entry per affected SNMP Manager containing the values of the notifications objects.

The aimosAlarmCleared notification is used when an alarm gets cleared. The alarm is correlated with the aimosAlarmNew and aimosAlarmCleared notification by identical values in aimosAlarmListAlarmEventID. It has an additional object aimosAlarmListClearReason. In contrast to aimosAlarmNew and aimosAlarmCleared the alarm notification object aimosAlarmListEventTime contains the time when the alarm condition is cleared. The aimosAlarmCleared notification causes the A.I.M.O.S. SNMP Agent to . create a new alarm trap list entry containing the values of the notification objects, . but not to create a new alarm list entry. Instead, the agent makes some amendments to the alarm list. Its entries created for the aimosAlarmNew and if applicable aimosAlarmChanged notifications (correlated with the aimosAlarmCleared notification by identical values in aimosAlarmListAlarmEventID) are modified in the following manner: . the notifications value of aimosAlarmListClearReason is assigned to the alarm lists value of aimosAlarmListClearReason . the notifications value of aimosAlarmListEventTime is assigned to the alarm lists value of aimosAlarmListClearTime After a aimosAlarmCleared notification was acknowledged all information of the alarm trap table entries and the alarm list entries are combined and filed in a new alarm log table entry. In this process, the entry from the alarm trap table is always deleted. The alarm list entry is also deleted, if no acknowledgement of another SNMP Manager of the according organisation is missing.

The aimosAlarmListRebuildInitiated notification is sent, when an alarm list rebuild process was triggered. The notification will be emitted prior to the rebuild, immediately after dropping the content of the alarm table. On reception of this notification, the SNMP Manager shall clean the internal alarm table to be synchronised with the agent prior to acknowledge this notification. Before acknowledgement the agent will not send any notification (expect of re-send this notification by the A.I.M.O.S. SNMP Agent until acknowledgement is received by the A.I.M.O.S. SNMP Agent). The alarm list contains one entry with . aimosAlarmListID and aimosAlarmListAlarmEventID set to 1 . aimosAlarmListAlarmID set to alarmOMC(62) . aimosAlarmListSpecificProblem set to 8885. The alarm trap list contains one entry per affected SNMP Manager (alarm recipient) with . aimosAlarmTrapNotificationID set to 1 for each SNMP Manager . aimosAlarmTrapID set to 1 for the first SNMP Manager, 2 for the second, ... There is no aimosAlarmCleared-notification for this alarm. It is cleared by acknowledgement.

The aimosHeartbeat notification is sent out each [aimosWorkShiftHeartbeatInterval] minutes to the members of the Alarm Recipient List specified by the object [aimosWorkShiftHeartbeatRecipientList]. This notification must not be acknowledged, even if the SNMP Manager performs acknowledgement to all other notifications. Additionally, this notifications are neither inserted to the Alarm Table nor to the Alarm Log. Therefore this notification contains no continuous numbering.

The aimosAlarmRecognized alarm is raised in case an alarm is recognized . either via aimosAlarmListRecognitionState . by means of the AIMOS_VIsu program The description for aimosAlarmListRecognitionState provides more information about this notification.

Group objects

Description.

Description.

Description.

Description.

Description.

Description.

Description.

Description.

Description.

Description.

Description.

Description.

Description.

Description.

Description.

Description.

Description.

Description.

Description.

Description.

Description.

Description.

Description.

Description.

Description.

Description.

Description.

Compliance objects

Description.