---
oid: "1.3.6.1.4.1.2.6.148.3.1.6.1.1.2"
short-description: "swPortBcastAlarmLevel OBJECT-TYPE"
last-modified: "2026-09-11"
parent-oid: "1.3.6.1.4.1.2.6.148.3.1.6.1.1"
---

## OID: `1.3.6.1.4.1.2.6.148.3.1.6.1.1.2`

```asn1
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 2 ibmProd(6) ibm8275(148) enetSwitchMgmt(3) sw(1) swAlarm(6) swPortBcastAlarmTable(1) swPortBcastAlarmTblEntry(1) swPortBcastAlarmLevel(2)}
```

### Description

```asn1
swPortBcastAlarmLevel OBJECT-TYPE
SYNTAX INTEGER {other(1), high(2), -- high volume
middle(3), -- Middle volume
low(4) -- low volume}
ACCESS read-write
STATUS mandatory
DESCRIPTION
"Specify the broadcast packets volume that received on this port will
be monitored. The broadcast level is defined by two attributes,
the utilization and the broadcast packet rate of this switch's port,
where
(Packets * (96+64)) + (Octets) * 8
(1) Utilization = ------------------------------------- * 100%
Sampling Interval
with Sampling Interval = 1 second,
broadcast packet received
(2) Broadcast packet rate = --------------------------------- * 100%
total number of packet received
The value of these attributes defined for this object is following:
- when the value high(2) is selected, the broadcast storming will
be determined only if the product of (1) and (2) (Utilization * Broadcast packet rate)
is greater than 30%.
- when the value middle(3) is selected, the broadcast storming will
be determined only if the product of (1) and (2) (Utilization * Broadcast packet rate)
is greater than 20%.
- when the value low(4) is selected, the broadcast storming will
be determined only if the product of (1) and (2) (Utilization * Broadcast packet rate)
is greater than 10%.
Note: The equation of Utilization defined here does fully comply
with the Utilization defined in the RFC1757 RMON-MIB."
```

**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.