TIMETRA-PCEP-MIB :: tmnxPcepPeerNumPCRptSent

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › TIMETRA-PCEP-MIB › tmnxPcepPeerNumPCRptSent

tmnxPcepPeerNumPCRptSent

Module: TIMETRA-PCEP-MIB

OID (symbolic): TIMETRA-PCEP-MIB::tmnxPcepPeerNumPCRptSent

OID (numeric): 1.3.6.1.4.1.6527.3.1.2.101.3.3.1.1.3

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

Description: The value of tmnxPcepPeerNumPCRptSent indicates the number of PCRpt messages sent to this peer.

What is tmnxPcepPeerNumPCRptSent?

Counts the number of PCRpt (LSP state report) messages sent to this peer. A steady, expected rate confirms the PCC is actively reporting LSP state to this peer as designed; a stalled counter on an otherwise-up session would warrant investigation.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.6527.3.1.2.101.3.3.1.1.3
snmpwalk -v2c -c public <target> TIMETRA-PCEP-MIB::tmnxPcepPeerNumPCRptSent

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.6527.3.1.2.101.3.3.1.1.3.1
snmpget -v2c -c public <target> TIMETRA-PCEP-MIB::tmnxPcepPeerNumPCRptSent.1

Start monitoring Nokia SROS routers (7750 SR, 7450 ESS) acting as PCEP client/server (PCEP session admin/keepalive status) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the TIMETRA-PCEP-MIB::tmnxPcepPeerNumPCRptSent OID value, configure state conditions and alerts, and monitor any Nokia SROS routers (7750 SR, 7450 ESS) acting as PCEP client/server (PCEP session admin/keepalive status) from a single console.

How to Use in IPNetwork Monitor

Select a Nokia SROS routers (7750 SR, 7450 ESS) acting as PCEP client/server (PCEP session admin/keepalive status) as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type tmnxPcepPeerNumPCRptSent into the Find box to locate it in the OID tree, selecting the specific row/instance you want to monitor since this is a table column, then select it and click OK. The value of tmnxPcepPeerNumPCRptSent indicates the number of PCRpt messages sent to this peer. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is a Counter32-type OID, Value bounds is the most useful condition here — trigger an alert if the counter increases sharply between polls relative to its normal baseline, since an unexpected spike often reflects a real change in traffic or activity. Click Finish to create the monitor; you can adjust any parameter later.

OID Breakdown

Upper-level ancestors (10 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.6527timetraALCATEL-IND1-TIMETRA-GLOBAL-MIB
1.3.6.1.4.1.6527.3timetraProductsALCATEL-IND1-TIMETRA-GLOBAL-MIB
1.3.6.1.4.1.6527.3.1tmnxSRMIBALCATEL-IND1-TIMETRA-GLOBAL-MIB
1.3.6.1.4.1.6527.3.1.2tmnxSRObjsALCATEL-IND1-TIMETRA-GLOBAL-MIB
Numeric OIDNameModule
1.3.6.1.4.1.6527.3.1.2.101tmnxPcepObjectsTIMETRA-PCEP-MIB
1.3.6.1.4.1.6527.3.1.2.101.3tmnxPcepStatsObjectsTIMETRA-PCEP-MIB
1.3.6.1.4.1.6527.3.1.2.101.3.3tmnxPcepPeerStatsObjectsTIMETRA-PCEP-MIB
1.3.6.1.4.1.6527.3.1.2.101.3.3.1tmnxPcepPeerStatsTableTIMETRA-PCEP-MIB
1.3.6.1.4.1.6527.3.1.2.101.3.3.1.1tmnxPcepPeerStatsEntryTIMETRA-PCEP-MIB
1.3.6.1.4.1.6527.3.1.2.101.3.3.1.1.3tmnxPcepPeerNumPCRptSentTIMETRA-PCEP-MIB