TELESTE-COMMON-MIB

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-TYPE

This is the logical name of the controlling module of the network element. The name may or may not be the same as the module's name in the moduleTable.

OBJECT-TYPE

This object tells whether the device is a single compact device or a modular device.

OBJECT-TYPE

This object is an indicator about changes in the network element configuration. How the value is formed is device dependent. It can be a counter, a checksum of the device configuration parameters, a DateAndTime type variable or even SysUptime, if no other information is available. DateAndTime is the recommended value. This object is intended to permit a management application to maintain configuration (including moduleTable) syncronization with the agent.

OBJECT-TYPE

Total number of software resets during the device's life time.

OBJECT-TYPE

The total uptime the device (software) has been running. Unit 1 day.

OBJECT-TYPE

Device latitude coordinate. Unit 0.00001 degrees.

OBJECT-TYPE

Device longitude coordinate. Unit 0.00001 degrees.

OBJECT-TYPE

Device altitude coordinate. Unit 1 metre.

OBJECT-IDENTITY

OBJECT-TYPE

A number stating the general status of the element. Values: 1 = Normal 2 = At least one Notification is active 3 = At least one Warning is active 4 = At least one Alarm is active If the element has more than one state active, then the state with the highest value is returned.

OBJECT-TYPE

A number stating the Bus Master status of the NE. Values: 1 = The NE is a slave-only device 2 = The NE is configured as slave 3 = The NE is configured as master but is currently slave because a stronger master is on the bus 4 = The NE is currently the bus master

OBJECT-TYPE

A number telling if the Local Management Terminal (LMT) is connected to the element. Values: 1 = The element does not have an LMT interface 2 = The element can not detect if an LMT is connected 3 = The element has not detected a connected LMT 4 = The element has detected a connected LMT Note! Applies only to fysically point-to-point connected LMT's to device, not via bus ot other shared medias.

OBJECT-TYPE

Element lid status: 1 = no lid (no lid sensor is available) 2 = lid is closed 3 = lid is open

OBJECT-TYPE

Element temperature status: 1 = normal 2 = HIHI 3 = Hi 4 = Lo 5 = LOLO

OBJECT-TYPE

A common status object for all fans in the device. fanNormal(1) = all fans operate normally fanFailure(2) = at least one fan has a failure

OBJECT-TYPE

Device hardware status: hwNormal(1) = the hardware operates normally hwFailure(2) = a hardware failure is detected

OBJECT-TYPE

Device software status: swNormal(1) = the software operates normally swFailure(2) = a software failure is detected swMissing(3) = the software or firmware is missing sw(Initialising(4) = the software is initialising

OBJECT-TYPE

Status of device settings: settingsStable(1) = settings are stable settingsChanged(2) = settings have been (recently) changed settingsNotAvailable(3) = settings status is not available The value should stay in value 2 only a predefined time, e.g. 60 seconds or the time it takes until the settings are written into non-volatile memory.

OBJECT-IDENTITY

OBJECT-TYPE

On write requests this object commands the module to reset itself. If softReset(3) or hardReset(2) can not be performed, then BAD VALUE error is returned. On read requests value noReset(1) is returned.

OBJECT-TYPE

This object tells whether the element is configured as a bus master or not. Only relevant for bus master type of elements. Others return no(2).

OBJECT-TYPE

This variable is used to disable or enable the element alarm checking. When disabled(1), the element will not check any alarms (or send traps). Default value is enabled(2). Note: This variable must be consistent with commonAlarmDetectionControl in SCTE-HMS-COMMON-MIB, if that is implemented.

OBJECT-TYPE

Number of entries in the elementTrapReceiverTable. At least one trap entry must be supported.

OBJECT-TYPE

A table of manager trap receiver addresses, ports and communities. Total number of entries can not exceed elementNumberTrapReceivers. An entry is deleted from this table by setting its IP address to '0.0.0.0'. Note: one of the community strings must match to commonTrapCommunityString in SCTE-HMS-COMMON-MIB, if that is implemented.

OBJECT-TYPE

OBJECT-TYPE

Unique table index. Makes possible to have several ip-address of 0.0.0.0 entries so that no mechanism for row manipulation of table is needed.

OBJECT-TYPE

Ip address of the manager receiving Traps.

OBJECT-TYPE

Trap UDP port number. Default port is the standard trap port 162.

OBJECT-TYPE

Community string for the trap receiver. The agent is allowed to limit the length of the string. Minimum length of eight characters must be supported. Note: one of the community strings must match to commonTrapCommunityString in SCTE-HMS-COMMON-MIB, if that is implemented.

OBJECT-TYPE

Enables/disables trap sending. 1 = traps enabled 2 = traps disabled

OBJECT-TYPE

The minimum interval between traps. - Unit 10 milliseconds - Minimum value 0 (send as fast as possible) - Maximum value 1000 (10 seconds) - Default value is 100 (1 second)

OBJECT-TYPE

The maximum time a trap stays in the trap queue waiting for sending. - Unit 1 second. - Minimum value 10 - Maximum value 300 - Default value 60

OBJECT-TYPE

The minimum time an object's alarm/warning condition must exist before it is recorded as an alarm/warning. Common to all alarms/warnings - Unit 10 ms - Minimum value 10 (100 ms) - Maximum value 6000 (60 seconds) - Default value 100 (1 second)

OBJECT-TYPE

The minimum time an alarm/warning entry stays active after the object has reached it's normal condition. Common to all alarms/warnings. - Unit 10 ms - Minimum value 10 (100 ms) - Maximum value 6000 (60 seconds) - default value 100 (1 second)

OBJECT-TYPE

The time before a trap is sent after an alarm is detected. - Unit 10 ms - Minimum value 10 (100 ms) - Maximum value 6000 (60 seconds) - Default value 500 (5 seconds) This parameter can be used to control alarm storms e.g. in an amplifier cascade by using a different value in each amplifier.

OBJECT-IDENTITY

OBJECT-TYPE

Number of product keys supported by the device.

OBJECT-TYPE

OBJECT-TYPE

OBJECT-TYPE

Product key index.

OBJECT-TYPE

Product key value.

OBJECT-TYPE

Product key mask.

OBJECT-TYPE

Product key status: 1(keyInvalid) = the key is invalid or missing 2(keyValid) = the key is valid

OBJECT-TYPE

Cipher method supported by this key: 1(cipherOther) = other ciphering is used 2(cipherBlowFish) = BlowFish ciphering is used 3(cipherXXTEA) = XXTEA ciphering is used

OBJECT-TYPE

Number of features available with this key.

OBJECT-TYPE

OBJECT-TYPE

OBJECT-TYPE

Feature index (second index).

OBJECT-TYPE

A human-readable description of the feature.

OBJECT-TYPE

Status of the feature: 1(featureDisable) = the feature si disabled in this device 2(featureEnable) = the feature is enabled in this devices

OBJECT-TYPE

Number of days left before the feature expires. A zero value means infinite validity time. This object has a meaning only if the feature is enabled (productKeyFeatureEnable = 2(featureEnable)).

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-TYPE

This table lists basic module identification and configuration data of modules installed inside the managed element. The first row in the table list information about the element itself. If the element is not modular, only the first row exists in the table. Object moduleId is used for indexing the modules in all module section tables.

OBJECT-TYPE

OBJECT-TYPE

An unique module index identifying the (physical) modules inside the network element. The exact conjunction between the index and the physical modules depends on the element structural principle. For network elements containing plug-in modules the index should follow module slot numbering. This index should be used in all subsequent module tables.

OBJECT-TYPE

The identification name ('aliasname') of the module.

OBJECT-TYPE

The hardware type name of the module.

OBJECT-TYPE

Rack number of the module. This can be used to identify the physical position of the module in the case where the agent manages modules that are in several racks.

OBJECT-TYPE

Slot number of the module (within rack).

OBJECT-TYPE

This table lists detailed module data of modules installed inside the element. The first row in the table list information about the element itself. If the element is not modular, only the first row exists in the table.

OBJECT-TYPE

OBJECT-TYPE

Module MAC address. If the MAC address is unknown '00.00.00.00.00.00' is returned.

OBJECT-TYPE

Module bus address.

OBJECT-TYPE

Module application software date.

OBJECT-TYPE

Module application software version. If software version is undefined, then zero length string is returned.

OBJECT-TYPE

Module BIOS date.

OBJECT-TYPE

Module BIOS version. If bios version is undefined, a zero length string is returned.

OBJECT-TYPE

Module serial number.

OBJECT-TYPE

Module hardware version.

OBJECT-IDENTITY

OBJECT-TYPE

This table contains status objects for modules inside the network element.The first row in the table lists information about the host module. If the element is not modular, only the first row exists in the table.

OBJECT-TYPE

Row in moduleStatusTable. The index is moduleId from the moduleTable. Row in this table exist only if there is a row with the same moduleId in the moduleTable.

OBJECT-TYPE

Reason for the last reset. If the reason is unknown, the value is reasonUnknown(1). If the device makes self reset and it can detect it, then value is reasonSelfReset(2). If the reset was made by the user from the power switch and it can be sensed, then the value is reasonPowerReset(3). If the reason is an external command from the user interface or from the network message (e.g. commonReset), then the reason is reasonCommandedReset(4).

OBJECT-TYPE

Currently running software image number. Bios is 0, applications are numbered from 1..n, where n is the maximum image number.

OBJECT-TYPE

Device temperature, unit 0.1 deg C. Value is zero (0), if temperature is not available.

OBJECT-TYPE

Current lid status detected by the device. May or may not be the same variable as the elementLidStatus.

OBJECT-TYPE

This objects counts the number of restarts of the module. A start can be a cold start or a warm start.

OBJECT-IDENTITY

OBJECT-TYPE

This table contains common control commands for all the modules inside the element.

OBJECT-TYPE

OBJECT-TYPE

A variable to instruct how device LED's behave when the lid is closed.

OBJECT-TYPE

A variable to instruct the device to start and stop showing mark (blinking module LED). On read requests returns the current mark state.

OBJECT-TYPE

On write requests this object commands the module to reset itself. If softReset(3) or hardReset(2) can not be performed, then BAD VALUE error is returned. On read requests value noReset(1) is returned.

OBJECT-TYPE

Module temperature HiHi (high alarm) limit in 0.1 degC.

OBJECT-TYPE

Module temperature Hi (high warning) limit in 0.1 degC.

OBJECT-TYPE

Module temperature Lo (low warning) limit in 0.1 degC.

OBJECT-TYPE

Module temperature LoLo (low alarm) limit in 0.1 degC.

OBJECT-TYPE

Module temperature alarm/warning deadband in 0.1 degC. Common to all limit values (LoLo, Lo, Hi, HiHi). The deadband defines the difference between the 'ON' limit and the 'OFF' limit of the corresponding alarm. Example: The Hi limit is 65 degC and the deadband is 5 degC. The high warning is activated when the temperature exceeds 65 degC and deactivated only after it falls below 60 degC.

OBJECT-TYPE

This object defines whether the internal controller application is able to access the module parameters. This corresponds to the BXX module setting 'Allow Functions'. 1 = allow internal control 2 = deny internal control (remote control is possible)

OBJECT-TYPE

This object defines whether the local user interface (buttons, knobs etc.) is enabled or disabled. Values: 1 = disabled, local UI is locked 2 = enabled, local UI is active For modules/devices with no local UI this objects should return value 'disabled (1).

OBJECT-TYPE

A table of software update control objects.

OBJECT-TYPE

OBJECT-TYPE

Writing value updateStart(4) commands the module to run a software update. The software image location and file name are specified in sWUpdateURL and sWUpdateFilename. Writing a updateIdle(1) when the update is running will terminate the update process immediately. Writing any value when no update is runnign has no effect. Reading this object returns either updateIdle(1), updateRunning(2) or updateFailed(3) depending on the status of the (last) software update.

OBJECT-TYPE

The URL where the software image can be downloaded. Format e.g. TFTP:\\downloads\swupdate\.

OBJECT-TYPE

File name of the software image file to be downloaded.

OBJECT-TYPE

Description of the software update result. After successful update this object should return a string 'Software updated successfully on <date and time>'. If the update failed the returned value should be 'Software update failed'.

OBJECT-IDENTITY

OBJECT-TYPE

This table defines maximum number of entries in the registry tables. All the registry tables have fixed size defined in this table.

OBJECT-TYPE

OBJECT-TYPE

Max number of entries in the registryTable. The entries in the registryTable are numbered from 1..sizeofRegistry.

OBJECT-TYPE

Max number of entries in the repairlogTable. First entry (oldest entry) is deleted, when a new entry is added and the table is full.

OBJECT-TYPE

Max number of entries in the notebookTable. The lines in the notebookTable are numbered from 1..sizeofNotebook.

OBJECT-TYPE

This table lists user data for all modules installed inside the element. Table is indexed by the moduleId and regIndex. regIndex can have values 1..sizeofRegistry. A registryEntry is 'deleted' by setting its name to an empty string.

OBJECT-TYPE

OBJECT-TYPE

A second index to registryTable. Can have values 1..sizeofRegistryTable.

OBJECT-TYPE

Descriptive name for the parameter. The agent is allowed to limit the length of the name. Minimum length of eight characters must be supported. Writing empty string to this object removes it from the registryTable.

OBJECT-TYPE

Textual information describing the parameter information. The agent is allowed to limit the length of the name. Minimum length of eight characters must be supported.

OBJECT-TYPE

This table contains repair history entries for modules in the element. The table is indexed with moduleId and repairLogDate. The table can have sizeofRepairlog number of entries. If this number is exceeded when writing a new entry, the oldest entry is deleted and and a new entry is added.

OBJECT-TYPE

Row entry in RepairLogTable. Note that it uses double index: moduleId repairIndex. that uniquely identify each log entry. Rows for particular module exist only if there is row, that represents this module in the moduleTable. A row is 'deleted' by giving a date 0000-00-00.

OBJECT-TYPE

Row number of the Repairlog entry. Can have values between 1..sizeOfRepairlog. This field is a second index to moduleRepairLogTable.

OBJECT-TYPE

Date of this repair entry formatted as CCYY-MM-DD.

OBJECT-TYPE

Repair code for this entry.

OBJECT-TYPE

Repairer name code (initials) for this entry.

OBJECT-TYPE

Comment of the repair event. The agent is allowed to truncate the length of the comment, if it is too long to internal storage.

OBJECT-TYPE

Notebook is a free text area for manager or serviceman notes. It is divided into 50 character long character blocks or lines. Each line is an entry in the notebookTable. Indices are moduleName and lineNumber. A new line with the same lineNumber overwrites the old line.

OBJECT-TYPE

OBJECT-TYPE

The line number of the notebookTextLine. The number must be in between 1..sizeofNotebook. inclusive. Numbers should be used consecutively.

OBJECT-TYPE

Text field for storing notes about the module.