Brcm-BASPTrap-MIB

Description: Defines SNMP trap notifications for Broadcom Advanced Server Program (BASP) NIC teaming events.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Brcm-BASPTrap-MIB is a small Broadcom vendor MIB, under the broadcom/enet/basp enterprise branch, that defines a single SNMP trap, failoverEvent, for the Broadcom Advanced Server Program (BASP) NIC-teaming driver. The trap carries four varbinds -- trapAdapterName and trapTeamName identifying which physical adapter and logical team experienced the event, trapCauseDirection indicating whether the adapter became active or inactive, and trapAdapterActivityCause giving the reason (link change, adapter enabled/disabled, or adapter added/removed). Because BASP teaming provides NIC redundancy for server network connectivity, this trap is the primary real-time signal that a team member has failed over or recovered, making it valuable for detecting silent NIC or link failures on teamed server interfaces before they affect application traffic. It has no dependency on other MIBs beyond the standard RFC1155-SMI/RFC-1212/RFC-1215 base conventions it imports. It is deployed on servers running Broadcom's BASP NIC-teaming software alongside their network adapters, and administrators load the Brcm-BASPTrap-MIB MIB into their trap receiver to decode these failover events.

An operator's trap receiver logs a failoverEvent with trapCauseDirection=adapterInactive and trapAdapterActivityCause=linkChange for a specific trapTeamName; repeated occurrences for the same team would indicate a flapping physical link or failing NIC that keeps forcing failover within the team.

Reports Broadcom Advanced Server adapter failover events and team activity changes for network redundancy.