---
oid: "1.3.6.1.4.1.164.6.5.1.2.1.9"
short-description: "activeAlarmSourceName OBJECT-TYPE"
last-modified: "2024-05-03"
parent-oid: "1.3.6.1.4.1.164.6.5.1.2.1"
---

## OID: `1.3.6.1.4.1.164.6.5.1.2.1.9`

```asn1
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 164 radGen(6) fmObjects(5) alarmEventConfig(1) activeAlarmTable(2) activeAlarmEntry(1) activeAlarmSourceName(9)}
```

### Description

```asn1
activeAlarmSourceName OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (1..32))
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"ASCII String specifying the name of the source referenced by alarmEventLogSourceId.
The syntax will be similar to CLI.
Example: E1 2/4
where E1 is the source type, 2 is the slot number, 4 is the port number.
The general formula is as follows:
<Source Type> <Slot number>/<Port number>
Source Type is defined in: AlarmEventSourceType.
For types that have 2 words like Serial Bundle, the 1st letter of each word will be capitalized.
For abbreviations we shall have all capitals. Examples: OAM EFM.
CL cards will be: cl-a, cl-b. Main cards will be: main-a, main-b
For SDH over E1 for example with Slots we shall have the same syntax as in CLI.
Example: E1 1/2/3 means: slot=1/port SDH=2/port E1=3
About the slot numbers, these will be the logical numbers of the slots according to
whatever is written on the device panel. For example, if an IO card is in slot IO-5
on the panel, '5' will be displayed for the slot."
```

**Classification:** MIB object for network management

### Child OIDs

No child OID

### Terms of Use

[Terms of use](https://oid-base.com/disclaimer.htm.md)

**Note to implementers:**: The OID repository is constantly updated but does not necessarily store the latest (or most accurate) version of this formal description. For an implementation, it is recommended to search the web for a more recent description. If this is the case, please update the above description.