BRCM-PING-MGMT-MIB

All MIBs › BRCM-PING-MGMT-MIB

Organization: Broadcom Corporation

Last Updated: 2007-02-05

Category: Broadcom DOCSIS / Cable Modem, Diagnostics & Testing

Description: Provides ICMP ping diagnostic test initiation and result objects for Broadcom cable modems.

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.

What Is BRCM-PING-MGMT-MIB?

BRCM-PING-MGMT-MIB is a Broadcom proprietary MIB for DOCSIS cable modems that provides runtime configuration and control of an ICMP ping diagnostic test. It exposes objects for setting a ping target address, packet count/sizes, interval, and timeout, along with a trigger object and result counters. It is used mainly for software/network-path health monitoring rather than physical hardware sensors -- an operator remotely triggers a ping test to verify IP reachability and round-trip behavior of a subscriber's cable modem, useful for diagnosing connectivity outages without a truck roll. It is conceptually similar to the IETF DISMAN-PING-MIB but implemented as a simplified Broadcom-specific module, typically deployed alongside DOCSIS cable device MIBs such as DOCS-CABLE-DEVICE-MIB. It is deployed on Broadcom-chipset cable modems and eMTAs, invoked by an ISP's network management system for remote subscriber troubleshooting. Engineers can download the BRCM-PING-MGMT-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in BRCM-PING-MGMT-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

Broadcom-chipset DOCSIS cable modem
cable eMTA gateway

Monitoring Examples

An operator sets pingTargetAddressType/pingTargetAddress, pingNumPkts, pingPktStartSize/pingPktEndSize/pingPktStepSize, then triggers the test via pingNow; pingPktsSent and related result objects report the outcome. Repeated failed or timed-out tests (using pingTimeout and pingVerifyReply) after normal triggering point to a WAN-side connectivity problem on that modem. pingInterval lets the admin tune how the packet stream is paced during the test.

What Can Be Monitored

ping test target address
packet count and size parameters
ping interval and timeout
packets sent/reply verification
test trigger status

Imported Objects

From BRCM-CABLEDATA-MGMT-MIB

cableDataMgmtBase

OBJECT-IDENTITY

From INET-ADDRESS-MIB

InetAddress
InetAddressType

From SNMPv2-SMI

Counter32
Integer32
IpAddress
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE
TimeTicks
Unsigned32

From SNMPv2-TC

DisplayString
TruthValue

OIDs

OID symbolic	OID numeric	Type	Access	Description
pingMgmt	1.3.6.1.4.1.4413.50.1.1.2.1.1.5			Broadcom proprietary MIB for runtime management and configuration of objects related to ICMP ping.
IPt pingTargetAddressType	1.3.6.1.4.1.4413.50.1.1.2.1.1.5.1	InetAddressType	read-write	The type of internet address used for pingTargetAddress. This object may be changed while a ping is in progress.
IP pingTargetAddress	1.3.6.1.4.1.4413.50.1.1.2.1.1.5.2	InetAddress	read-write	Sets the internet address of the entity to be pinged. Note that if an all-zeros value is specified for this object, then the ping will be sent to the default gateway, if one exists. This object may be changed while a ping is in progress.
U32 pingNumPkts	1.3.6.1.4.1.4413.50.1.1.2.1.1.5.3	Unsigned32	read-write	Allows the client to set the number of pings to be sent. This can be set to any number between 1 and (2^32 - 1), or can be set to 'infinite' by setting the value to 0. Note that if set to infinite, then the ping must be stopped explicitly in order to get it to stop. This object may be changed while a ping is in progress.
U32 pingPktStartSize	1.3.6.1.4.1.4413.50.1.1.2.1.1.5.4	Unsigned32	read-write	Allows the client to set the initial size of the ping packets that will be sent. This size includes the LLC header, IP header, ICMP header, and the CRC32 at the end. You must specify values between 64 and 1518, which are the min and max size Ethernet frames. This object may be changed while a ping is in progress.
U32 pingPktEndSize	1.3.6.1.4.1.4413.50.1.1.2.1.1.5.5	Unsigned32	read-write	Allows the client to set the final size of the ping packets that will be sent. This size includes the LLC header, IP header, ICMP header, and the CRC32 at the end. You must specify values between 64 and 1518, which are the min and max size Ethernet frames. This object may be changed while a ping is in progress.
I32 pingPktStepSize	1.3.6.1.4.1.4413.50.1.1.2.1.1.5.6	Integer32	read-write	Specifies the number of bytes by which each subsequent ping packet is incremented. The step amount can be any number from 0 (which leaves the ping size constant) up to (2^32 - 1). Note that after adding the step amount to the current ping size, if this is greater than the end size, then the current size will be wrapped around to the start size. If you want to send ping packets of the same size every time, set the start and end size to be equal, and the step amount to be 0. To do a sweeping ping of every packet size, set start to 64, end to 1518, and step amount to 1. You can set step amount to -1 to sweep in the other direction. This object may be changed while a ping is in progress.
U32 pingInterval	1.3.6.1.4.1.4413.50.1.1.2.1.1.5.7	Unsigned32	read-write	Allows the client to set the amount of time (in milliseconds) that the device will sleep before sending a ping. Generally, this is the time between when a ping reply is received and when the next ping will be sent. Note that the amount of time between sending one ping and sending the next ping varies depending on whether or not you enable waiting for replies, and how long it takes to receive the reply. If waiting for replies is disabled, then this is the time between sending one ping and sending the next ping. This object may be changed while a ping is in progress.
I32 pingTimeout	1.3.6.1.4.1.4413.50.1.1.2.1.1.5.8	Integer32	read-write	Allows the client to set the amount of time (in milliseconds) that the device should wait for a reply after sending a ping. If set to any non-negative value, then the device will send a ping and wait for a response for the specified amount of time. Event if set to 0, the thread will check for and process a reply packet. If set to -1, then the device will not wait at all, and won't even check for any replies. This object may be changed while a ping is in progress.
T/F pingVerifyReply	1.3.6.1.4.1.4413.50.1.1.2.1.1.5.9	TruthValue	read-write	Enables/disables verification of ping replies. If enabled, and if waiting for replies is enabled, then if a reply is received, it will verify that it matches the ping that was sent, and that all of the data is intact. This object may be changed while a ping is in progress.
I32 pingIpStackNumber	1.3.6.1.4.1.4413.50.1.1.2.1.1.5.10	Integer32	read-write	Allows the client to select the IP stack from which the pings will be sent. Specifying 0 means that the pings will be sent from the same IP stack on which this MIB is hosted. This object may not be changed while a ping is in progress.
T/F pingNow	1.3.6.1.4.1.4413.50.1.1.2.1.1.5.11	TruthValue	read-write	Starts or stops the pings, as well as indicating whether a ping is in progress when read. If a ping is already in progress and this object is set to true(1), then the ping will continue but the ping statistics will be reset. This object may be changed while a ping is in progress.
C32 pingPktsSent	1.3.6.1.4.1.4413.50.1.1.2.1.1.5.12	Counter32	read-only	Indicates the number of packets sent since the ping was started.
C32 pingRepliesReceived	1.3.6.1.4.1.4413.50.1.1.2.1.1.5.13	Counter32	read-only	Indicates the number of replies received since the ping was started.
C32 pingRepliesVerified	1.3.6.1.4.1.4413.50.1.1.2.1.1.5.14	Counter32	read-only	Indicates the number of replies which were verified since the ping was started.
C32 pingOctetsSent	1.3.6.1.4.1.4413.50.1.1.2.1.1.5.15	Counter32	read-only	Indicates the total number of octets that have been sent in pings since the ping was started.
C32 pingOctetsReceived	1.3.6.1.4.1.4413.50.1.1.2.1.1.5.16	Counter32	read-only	Indicates the total number of octets that have been sent in pings since the ping was started.
C32 pingIcmpErrors	1.3.6.1.4.1.4413.50.1.1.2.1.1.5.17	Counter32	read-only	Indicates the total ICMP errors which have been received since the ping was started.
U32 pingLastIcmpError	1.3.6.1.4.1.4413.50.1.1.2.1.1.5.18	Unsigned32	read-only	Indicates value of the last ICMP error which was received, if any. If there have been no errors, this object will have a value of 0.

RFC description

Broadcom proprietary SNMP MIB for managing PING (packet internet groper) diagnostic utilities and connectivity monitoring functions on Broadcom network devices, providing objects for configuring and monitoring network diagnostic operations.

Start monitoring Broadcom-chipset DOCSIS cable modems/gateways 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.

Download BRCM-PING-MGMT-MIB

What Is BRCM-PING-MGMT-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description