Trend Micro TippingPointTM

Threat Protection System (TPS)
MIBs Guide
Actionable threat defense against advanced targeted attacks.

TMTrend Micro Incorporated reserves the right to make changes to thisdocument and to the product described herein without notice. Before
installing and using the product, review the readme files, release notes,
and/or the latest version of the applicable documentation, which areavailable from the Trend Micro website at:https://docs.trendmicro.com/en-us/tippingpoint/threat-protectionsystem.aspx
Trend Micro, the Trend Micro t-ball logo, TippingPoint, and Digital Vaccine
are trademarks or registered trademarks of Trend Micro Incorporated. Allother product or company names may be trademarks or registeredtrademarks of their owners.
Copyright © 2024. Trend Micro Incorporated. All rights reserved.
Document Part No.: TPEM69851/230927
Release Date: April 2024
Protected by U.S. Patent No.: PendingThis documentation introduces the main features of the product and/or
provides installation instructions for a production environment. Readthrough the documentation before installing or using the product.
Detailed information about how to use specific features within the productmay be available at the Trend Micro Online Help Center and/or the Trend
Micro Knowledge Base.
Trend Micro always seeks to improve its documentation. If you havequestions, comments, or suggestions about this or any Trend Microdocument, please contact us at docs@trendmicro.com.
Evaluate this documentation on the following site:
https://www.trendmicro.com/download/documentation/rating.asp

Privacy and Personal Data Collection Disclosure
Certain features available in Trend Micro products collect and send feedback
regarding product usage and detection information to Trend Micro. Some ofthis data is considered personal in certain jurisdictions and under certain
regulations. If you do not want Trend Micro to collect personal data, youmust ensure that you disable the related features.
The following link outlines the types of data that TippingPoint ThreatProtection System collects and provides detailed instructions on how todisable the specific features that feedback the information.
https://success.trendmicro.com/data-collection-disclosure
Data collected by Trend Micro is subject to the conditions stated in the Trend
Micro Privacy Notice:https://www.trendmicro.com/privacy

Table of Contents
Chapter 1: TPS MIBs Guide
Standard SNMP MIBs supported .......................................... 1-2
SNMPv2-MIB ................................................................ 1-2
IF-MIB ......................................................................... 1-3
EtherLike-MIB .............................................................. 1-3
IP-MIB ......................................................................... 1-4
SNMP-USER-BASED-SM-MIB ......................................... 1-4
SNMP-VIEW-BASED-ACM-MIB ...................................... 1-4
Reference sites for standard MIBs .................................. 1-5
TPS-supported MIBs ........................................................... 1-5
TIPPINGPOINT-REG-MIB .............................................. 1-5
TPT-BAY ....................................................................... 1-6
TPT-COMPACT-FLASH-MIB ......................................... 1-10
TPT-HEALTH-MIB ...................................................... 1-11
Temperature ......................................................... 1-11
Fans ..................................................................... 1-13
Voltage ................................................................. 1-14
TPT-HIGH-AVAIL-MIB ................................................. 1-15
TPT-HOST .................................................................. 1-23
TPT-LICENSE .............................................................. 1-23
TPT-MISC-NOTIFY-MIB ............................................... 1-24
Common TPT notification objects .......................... 1-25
Management TPT notification objects .................... 1-25
Quarantine TPT notification objects ....................... 1-25
Congestion notifications ........................................ 1-26
System Log TPT notification objects ....................... 1-28
Audit Log TPT notification objects .......................... 1-28
TPT-MULTIDV-MIB ..................................................... 1-32
TPT-NPSTATS-MIB ...................................................... 1-33
Segment port stats ................................................ 1-39
SSL inspection objects ........................................... 1-41
TPT-POLICY-MIB ........................................................ 1-42iTPS MIBs Guide

TPT-PORT-CONFIG-MIB .............................................. 1-55
TPT-RESOURCE-MIB ................................................... 1-56
Notifications ......................................................... 1-57
File system ........................................................... 1-59
Memory ............................................................... 1-60
CPU ..................................................................... 1-61
Chassis temperature ............................................. 1-62
Power supply ........................................................ 1-63
System information ............................................... 1-64
TPT-SFLOW ................................................................ 1-65
TPT-SMSMIBS ............................................................. 1-66
TPT-SMS-TRAP-MIB .................................................... 1-67
TPT-TPA-HARDWARE-MIB .......................................... 1-71
Fans ..................................................................... 1-71
Power supply ........................................................ 1-74
TPT-TRAFFIC .............................................................. 1-76
Rate limiter .......................................................... 1-76
Rate limit historical seconds .................................. 1-77
Rate limit historical minutes .................................. 1-78
Rate limit historical hours ..................................... 1-79
TPT-TPAMIBS-MIB ...................................................... 1-79
TPT-TSE ..................................................................... 1-80
Adaptive filter configuration .................................. 1-81
Connection blocks table ........................................ 1-81
Rate limit streams table ......................................... 1-83
Connection trusts table ......................................... 1-84

Chapter 2: Using HP Network Node Manager i with MIBs
Loading TippingPoint Enterprise MIBs ................................ 2-2
MIB Application Builder ..................................................... 2-2
Discovering the device ........................................................ 2-3
Creating graphs with Application Builder ............................. 2-4

ii

iii

Chapter 1

MIB files for the Threat Protection
SystemA management information base (MIB) is a type of database that enables you
to manage devices in a communications network. Database entries are
addressed through object identifiers (OIDs). MIB files are descriptions of
network objects that can be managed using the Simple Network Management
Protocol (SNMP). The format of the MIB is defined as part of the SNMP.
This information includes the following topics:• Standard SNMP MIBs supported on page 1-2• TPS-supported MIBs on page 1-5

1-1

TPS MIBs Guide

Standard SNMP MIBs supported
Important
In a production environment, do not perform excessive SNMP Get requests(or walks) against standard MIBs.

This topic contains the following information:• SNMPv2-MIB on page 1-2• IF-MIB on page 1-3• EtherLike-MIB on page 1-3• IP-MIB on page 1-4• SNMP-USER-BASED-SM-MIB on page 1-4• SNMP-VIEW-BASED-ACM-MIB on page 1-4• Reference sites for standard MIBs on page 1-5

SNMPv2-MIB
Defines common information typically provided by managed systems. The
Threat Protection System (TPS) supports the following items.
Name

1-2

Type

Description

SystemGroup

A collection of objects common to all managed systems. This
includes information such as model, contact and location, up
time, services, and system ID.

SNMP

Group

A collection of objects providing information on SNMP protocolstats, such as the number of packets received and transmitted.

coldStart

Notification

Signifies that the TPS device is reinitializing itself, typically areboot.

TPS MIBs Guide

IF-MIB
Contains objects for managing and monitoring network interfaces. Only
physical interfaces have stats in the following tables. Logical interfaces, such
as VLAN and Bridge, are listed, but stats are always 0.
Name

Type

Description

ifTableTable

List of information and stats foreach interface of a system. The
number of entries is given by thevalue of ifNumber.

ifXTable

Table

List of interface entries. The numberof entries is given by the value of
ifNumber. This table contains
additional objects for the interface
table.

linkUp

Notification

A linkUp notification signifies that acommunication link has left the
down state and is now in the up
state.

linkDown

Notification

A linkDown notification signifies
that a communication link has left
the up state and is now in the downstate.

EtherLike-MIB
Provides information representing attributes of an interface to an Ethernetlike communications medium.
Name

Type

Description

dot3StatsTable

Table

Contains statistics for a collection of ethernet-like interfaces
attached to a particular system.

dot3HCStatsTable

Table

Contains 64-bit versions of error counters from thedot3StatsTable.

1-3

TPS MIBs Guide

IP-MIB
Name

Type

Description

IP

Group

A collection of object stats that include such information as
IP datagrams received or transmitted.

ipv4InterfaceTable

Table

Contains per-interface IPv4-specific information.

ipv6InterfaceTable

Table

Contains per-interface IPv6-specific information.

IpSystemStatsTable

Table

Contains system-wide, IP version-specific traffic statistics.

IpAddressTable

Table

Contains addressing information relevant to the entity's
interfaces.

ipNetToPhysicalTable

Table

Contains the IP Address Translation table used for mappingfrom IP addresses to physical addresses.

SNMP-USER-BASED-SM-MIB
Defines the SNMPv3 user-based Security Model (USM). The Threat Protection
System (TPS) supports the following groups.
Name

Type

Description

usmStatsGroup

A collection of scalar objects that provide information, such as thenumber of unknown user names, engine IDs, or unsupported security
levels.

SNMP-VIEW-BASED-ACM-MIB
This MIB defines the SNMPv3 View-based Access Control Model (VACM) for
use in the Simple Network Management Protocol (SNMP) architecture. The
Threat Protection System (TPS) supports the following tables.
Type

Name

1-4

Description

vacmContextTable

Table

Locally available security contexts

vacmSecurityToGroupTable

Table

Maps a security context with groups

vacmAccessTable

Table

Access rights for groups

TPS MIBs GuideNamevacmViewTreeFamilyTable

Type
Table

Description
Locally held information about families of
sub-trees within MIB views

Reference sites for standard MIBs
• IETF: http://www.ietf.org — where all the standard RFCs are kept for
MIBs• http://www.net-snmp.org/docs/mibs/ucdavis.html — a well maintainedsite with standard and company specific MIBs

TPS-supported MIBs
The Threat Protection System (TPS) supports these MIBs fully except where
noted. These are non-standard MIBs with TPT-specific definitions for Trend
Micro™ TippingPoint™ products only.

TIPPINGPOINT-REG-MIB
Note
This MIB file must be loaded before you load any other TippingPoint MIB
files.

Defines the object identifier (OID) sub-tree assigned to Trend by the Internet
Assigned Numbers Agency (IANA), as well as sub-trees for registered
modules, object and event definitions, agent profiles, management
application requirements, and experimental definitions.
The following table describes TIPPINGPOINT-REG-MIB sub-trees:
Objecttpt-reg

OID
1.3.6.1.4.1.10734.1

Description
Sub-tree for the registered
modules

1-5

TPS MIBs Guide

ObjectOID

Description

tpt-generic (notsupported)

1.3.6.1.4.1.10734.2

Sub-tree for common object andevent definitions

tpt-products

1.3.6.1.4.1.10734.3

Sub-tree for specific object andevent definitions

tpt-caps (not supported)

1.3.6.1.4.1.10734.4

Sub-tree for agent profiles

tpt-reqs (not supported)

1.3.6.1.4.1.10734.5

Sub-tree for management
application requirements

tpt-expr (not supported)

1.3.6.1.4.1.10734.6

Sub-tree for experimental
definitions

TPT-BAY
Used to define the status and configuration of the module slots on NX Series
and TX Series devices.
Object

1-6

OID

Description

tpt-slot-objs

1.3.6.1.4.1.10734.3.3.2.17

Slot information.

slotTempTable

1.3.6.1.4.1.10734.3.3.2.17.1

A list of the slots on thedevice.

slotTempEntry

1.3.6.1.4.1.10734.3.3.2.17.1.1

An entry in the slot table.
Rows cannot be added ordeleted.

slotTempIndex

1.3.6.1.4.1.10734.3.3.2.17.1.1.1

The index number of the slot.

slotName

1.3.6.1.4.1.10734.3.3.2.17.1.1.2

The name of the slot.

slotModuleName

1.3.6.1.4.1.10734.3.3.2.17.1.1.3

String description of the typeof module in the slot.

TPS MIBs Guide

ObjectslotStatus

OID
1.3.6.1.4.1.10734.3.3.2.17.1.1.4

Description
The slot status.
0: Empty; no module iscurrently installed.
1: Active; a module is present
in the slot and active.
2: Error. The module might
have failed to initialize, or theconfigured module typemight not match the module
currently inserted in the slot.

slotModuleSerialNum

1.3.6.1.4.1.10734.3.3.2.17.1.1.5

The serial number of themodule currently installed in
the slot.

1-7

TPS MIBs Guide

ObjectslotModuleType

OID
1.3.6.1.4.1.10734.3.3.2.17.1.1.6

Description
The module type currently
installed in the slot.
type-12-port-1g-copper(1)type-12-port-1g-sfp(2)type-12-port-25g-sfp(24)type-8-port-10g-sfp(3)type-8-port-100g-qsfp(25)type-8-port-25g-sr-bypass(26)type-8-port-25g-lr-bypass(27)type-2-port-40g-qsfp(4)type-6100(5)type-5100(6)type-2500(7)type-1400(8)type-660(9)type-330(10)type-110(11)type-10(12)type-empty(13)type-8-port-1g-copperbypass(14)type-4-port-100g-sr4bypass(28)type-4-port-100g-lr4bypass(29)type-4-port-1g-sfp-srbypass(15)type-4-port-1g-sfp-lrbypass(16)1-8TPS MIBs Guide

ObjectOID

Description
type-4-port-10g-sfp-srbypass(17)type-4-port-10g-sfp-lrbypass(18)type-2-port-40g-qsfp-sr4bypass(19)type-2-port-40g-qsfp-lr4bypass(20)type440T(21)type2200T(22)typeVSA(23)type-4-port-40g-sr4bypass(30)type-4-port-40g-lr4bypass(31)type-8-port-10g-sr-bypass(32)type-8-port-10g-lr-bypass(33)type-8-port-1g-sx-bypass(34)type-8-port-1g-lx-bypass(35)type-12-port-1g-copperbypass(36)tptSlotDeviceID

1.3.6.1.4.1.10734.3.3.3.1.281

The unique identifier of thedevice that is sending thenotification.

tptSlotID

1.3.6.1.4.1.10734.3.3.3.1.282

The index number of the slotthat is sending thenotification.

1-9

TPS MIBs Guide

ObjecttptSlotEvent

OID
1.3.6.1.4.1.10734.3.3.3.1.283

Description
The status of the slot.
0: A module has been
removed.
1: A module has been
inserted.
2: Error. The module might
have failed to initialize, or theconfigured module typemight not match the module
currently inserted in the slot.

tptSlotChangeNotify

1.3.6.1.4.1.10734.3.3.3.0.54

A notification of activity on
the slot.

TPT-COMPACT-FLASH-MIB
The Threat Protection System (TPS) provides no notification support for thisMIB. Defines the status and operating mode of the external storage card.
The following table describes compact flash data objects:
ObjectOID

Description

tpt-compact-flash

1.3.6.1.4.1.10734.3.3.2.14

Sub-tree for all external storage
card information.

compactFlashPresent

1.3.6.1.4.1.10734.3.3.2.14.1

Indicates card presence.
• 0: present• 1: absent

compactFlashMounted

1.3.6.1.4.1.10734.3.3.2.14.2

Indicates card mount status.
• 0: mounted• 1: unmounted

compactFlashFormatted

1.3.6.1.4.1.10734.3.3.2.14.3

Indicates card format status.
• 0: formatted• 1: unformatted

1-10

TPS MIBs Guide

ObjectOID

Description

compactFlashOperationM
ode

1.3.6.1.4.1.10734.3.3.2.14.4

Indicates card operation mode.
• 0: secure mode—requires
authentication• 1: auto-mount enabled—
cards are automaticallymounted when inserted

vendorInformation

1.3.6.1.4.1.10734.3.3.2.14.5

Sub-tree of external storage card
informational details.

serialNumber

1.3.6.1.4.1.10734.3.3.2.14.5.1

Card serial number.

model

1.3.6.1.4.1.10734.3.3.2.14.5.2

Card model name.

capacity

1.3.6.1.4.1.10734.3.3.2.14.5.3

Card capacity.

revision

1.3.6.1.4.1.10734.3.3.2.14.5.4

Card firmware revision.

The following notifications and SNMP traps apply to changes in the status of
the Compact Flash state:
OID

Description

tptCFInsertedNotify

1.3.6.1.4.1.10734.3.3.3.0.51

External storage was inserted on
this device.

tptCFEjectedNotify

1.3.6.1.4.1.10734.3.3.3.0.52

External storage was ejected on
this device.

ObjectTPT-HEALTH-MIB
Indicates the health status of the IPS. Features monitored temperatures, fan
speeds, and voltage levels. The Threat Protection System (TPS) provides nohealth2CTable support.

Temperature
The Temperature objects monitor the device temperature. Alarms are
generated when the temperature at a sensor passes a specified threshold.

1-11

TPS MIBs Guide

The following table describes temperature objects:
ObjectOID

Description

healthTempTable

1.3.6.1.4.1.10734.3.3.2.13.1

Lists the readings at the device
temperature sensors

healthTempEntry

1.3.6.1.4.1.10734.3.3.2.13.1.1

Entry in the temperature table.
Rows are predefined and cannot
be created or deleted.

healthTempIndex

1.3.6.1.4.1.10734.3.3.2.13.1.1.
1Index number of the entry

healthTempChannel

1.3.6.1.4.1.10734.3.3.2.13.1.1.
2

Location of the temperature
sensor.

healthTempValue

1.3.6.1.4.1.10734.3.3.2.13.1.1.
3

Temperature in degrees
centigrade

healthTempSeverity

1.3.6.1.4.1.10734.3.3.2.13.1.1.
4

Can be one of the following
values:• 0: normal• 1: informational note
• 2: minor• 3: major• 4: critical

healthTempThresholdType

1.3.6.1.4.1.10734.3.3.2.13.1.1.
5

Determines the application ofthresholds:• 1: minimum; value should
not go below threshold• 2: range; value should
remain with a designatedrange• 3: maximum; value should
not go above thresholdhealthTempMajor

1-12

1.3.6.1.4.1.10734.3.3.2.13.1.1.
6

Major threshold temperature indegrees centigradeTPS MIBs Guide

ObjecthealthTempCritical

OID

Description

1.3.6.1.4.1.10734.3.3.2.13.1.1.
7

Critical threshold temperature indegrees centigrade

Fans
The fan objects monitor the fan performance and health.
The following table describes fan objects:
ObjectOID

Description

healthFanTable

1.3.6.1.4.1.10734.3.3.2.13.2

Lists all fans inside the device

healthFanEntry

1.3.6.1.4.1.10734.3.3.2.13.2.1

Entry in the fans table. Rows arepredefined and cannot becreated or deleted.

healthFanIndex

1.3.6.1.4.1.10734.3.3.2.13.2.1.
1

Index number of the entry

healthFanChannel

1.3.6.1.4.1.10734.3.3.2.13.2.1.
2

String identifying the fan

healthFanValue

1.3.6.1.4.1.10734.3.3.2.13.2.1.
3

Speed of the fan in RPM

healthFanSeverity

1.3.6.1.4.1.10734.3.3.2.13.2.1.
4

Can be one of the following
values:• 0: normal• 1: informational note
• 2: minor• 3: major• 4: critical

1-13

TPS MIBs Guide

ObjectOID

Description

healthFanThresholdType

1.3.6.1.4.1.10734.3.3.2.13.2.1.
5

Determines the application ofthresholds:• 1: minimum; value should
not go below threshold• 2: range; value should
remain with a designatedrange• 3: maximum; value should
not go above thresholdhealthFanMajor

1.3.6.1.4.1.10734.3.3.2.13.2.1.
6

Major threshold speed in RPM

healthFanMinor

1.3.6.1.4.1.10734.3.3.2.13.2.1.
7

Critical threshold speed in RPM

Voltage
The voltage objects monitor the voltage levels at various locations within thedevice.
The following table describes voltage objects:
Object

1-14

OID

Description

healthVoltageTable

1.3.6.1.4.1.10734.3.3.2.13.3

List of all voltages at various
locations inside the device

healthVoltageEntry

1.3.6.1.4.1.10734.3.3.2.13.3.1

An entry in the voltage table.
Rows are predefined and cannot
be created or deleted.

healthVoltageIndex

1.3.6.1.4.1.10734.3.3.2.13.3.1.
1

Index number of the entry

healthVoltageChannel

1.3.6.1.4.1.10734.3.3.2.13.3.1.
2

Location of the voltage sensor

healthVoltageValue

1.3.6.1.4.1.10734.3.3.2.13.3.1.
3

Voltage reading in millivolts

TPS MIBs Guide

ObjecthealthVoltageSeverity

OID
1.3.6.1.4.1.10734.3.3.2.13.3.1.
4

Description
Can be one of the following
values:• 0: normal• 1: informational note
• 2: minor• 3: major• 4: critical

healthVoltageThresholdType

1.3.6.1.4.1.10734.3.3.2.13.3.1.
5

Determines the application ofthresholds:• 1: minimum; value should
not go below threshold• 2: range; value should
remain with a designatedrange• 3: maximum; value should
not go above thresholdhealthVoltageMajor

1.3.6.1.4.1.10734.3.3.2.13.3.1.
6

Major threshold delta above or
below the nominal voltage
value, in millivolts

healthVoltageMinor

1.3.6.1.4.1.10734.3.3.2.13.3.1.
7

Critical threshold delta above or
below the nominal voltage
value, in millivolts

healthVoltageNominal

1.3.6.1.4.1.10734.3.3.2.13.3.1.
8

Optimal voltage value at thissensor location

TPT-HIGH-AVAIL-MIB
Defines the conditions and actions for Intrinsic Network HA, Transparent
Network HA, and Zero-Power HA, and also offers information about thecurrent fault state of the device.

1-15

TPS MIBs Guide

ObjectOID

Description

highAvailTimeStamp

1.3.6.1.4.1.10734.3.3.2.6.1

The last transition of the fault
state in seconds since
January 1, 1970. The value iszero if the fault state has notchanged since the last reboot.

highAvailFaultState

1.3.6.1.4.1.10734.3.3.2.6.2

The current fault state of thedevice:• 0: normal• 1: fallback

highAvailFaultCause

1.3.6.1.4.1.10734.3.3.2.6.3

The reason for the current
fault state:• 0: none• 1: suspended task
• 2: out of memory• 3: hardware breaking
point• 4: TSE failure• 5: watchdog timeout• 6: user reset• 7: user-initiated fallback• 8: threshold failure• 9: software watchdog
timeout• 10: OAM fault• 11: hard disk disabled

highAvailThresholdEnabled

1-16

1.3.6.1.4.1.10734.3.3.2.6.4

The current Layer-2 Fallback(L2FB) threshold-enabled
setting for the device.

TPS MIBs Guide

ObjectOID

Description

highAvailThresholdPercent

1.3.6.1.4.1.10734.3.3.2.6.5

If the fallback threshold isenabled, the percent packet
loss at which the device isconfigured to enter L2FB.

highAvailEnabled

1.3.6.1.4.1.10734.3.3.2.6.6

Indicates whether intrinsic
network HA has beenenabled.

highAvailTransparentState

1.3.6.1.4.1.10734.3.3.2.6.7

State of the connection to thedevice’s transparent HA
partner:• 0: not connected• 1: unresponsive• 2: connected

highAvailTransparentEnabled

1.3.6.1.4.1.10734.3.3.2.6.8

Indicates whether
transparent HA has beenenabled.

highAvailTransparentPartner

1.3.6.1.4.1.10734.3.3.2.6.9

Network address or serial
number of the device’s
transparent HA partner.

highAvailZeroPowerState

1.3.6.1.4.1.10734.3.3.2.6.10

The current ZPHA state.

highAvailZeroPowerQuantity

1.3.6.1.4.1.10734.3.3.2.6.11

The number of segments with
ZPHA modules.

highAvailZeroPowerTable

1.3.6.1.4.1.10734.3.3.2.6.12

Table of segments with ZPHA
modules.

highAvailZeroPowerEntry

1.3.6.1.4.1.10734.3.3.2.6.12.1

An entry in the ZPHA table.

highAvailZeroPowerIndex

1.3.6.1.4.1.10734.3.3.2.6.12.1.
1

The index number of theentry.

highAvailZeroPowerSegment

1.3.6.1.4.1.10734.3.3.2.6.12.1.
2

The name of the segment on
which ZPHA is enabled. For
TPS devices, this name will
always be Segment ALL.

1-17

TPS MIBs Guide

ObjecthighAvailZeroPowerActive

OID

Description

1.3.6.1.4.1.10734.3.3.2.6.12.1.
3

The current ZPHA state of thesegment:• 0: normal, ZPHA inactive• 1: TPS bypass, ZPHA
activeTPS devices return a separate
value for each bypass I/O
module:• 0• 1highAvailZeroPowerAction

1.3.6.1.4.1.10734.3.3.2.6.12.1.
4

The action taken when ZPHA
is active. For TPS devices, thismode will always be 1:
bypass.

highAvailZeroPowerMode

1.3.6.1.4.1.10734.3.3.2.6.12.1.
5

The fiber mode of this ZPHA.
For TPS devices, this mode
will always be 0: unknown.

highAvailZeroPowerPresence

1.3.6.1.4.1.10734.3.3.2.6.13

Indicates ZPHA presence:• 0: present• 1: absent

The following notifications and SNMP traps apply to Intrinsic Network HA.

1-18

TPS MIBs Guide

ObjecttptIhaNotify

OID
1.3.6.1.4.1.10734.3.3.3.0.15

Description
The notification object that
informs the management
station of changes in the
Intrinsic HA state of thedevice.
Triggered when the device
enters or exits L2FB. Possible
causes:• Depleted memory.
• User reset – Manuallyclearing L2FB.
• User fallback – Manuallyentering L2FB.
• Threshold failure –Performance protection
triggers L2FB.
• Process error – Crash of avital process.
• Watchdog timeout –Failure of processmonitoring.

tptIhaNotifyDeviceID

1.3.6.1.4.1.10734.3.3.3.1.81

The unique identifier of thedevice sending thenotification.

tptIhaNotifyTimeStamp

1.3.6.1.4.1.10734.3.3.3.1.82

The timestamp of thenotification in seconds since
January 1, 1970.

tptIhaNotifyFaultState

1.3.6.1.4.1.10734.3.3.3.1.83

The current fault state of thedevice:• 0: normal• 1: fallback

1-19

TPS MIBs Guide

ObjecttptIhaNotifyFaultCauseOID
1.3.6.1.4.1.10734.3.3.3.1.84

Description
The reason for the current
fault state:• out-of-memory• user-reset (usermanually clears L2FB)• user-fallback (usermanually enters L2FB)• threshold failure (L2FB
triggered by
performance protection)• process error (crash ofvital process)• software watchdog
timeout (failure ofprocess monitoring)

The following notifications and SNMP traps apply to Transparent Network
HA.
ObjecttptTrhaNotify

OID
1.3.6.1.4.1.10734.3.3.3.0.18

Description
The notification object that
informs the management
station of changes in thetransparent HA state of thedevice.
Triggered when the HA
partner is connected or notconnected (including
unresponsive).

tptTrhaNotifyDeviceID

1-20

1.3.6.1.4.1.10734.3.3.3.1.86

The unique identifier of thedevice sending thenotification.

TPS MIBs Guide

ObjectOID

Description

tptTrhaNotifyTimeSta
mp

1.3.6.1.4.1.10734.3.3.3.1.87

The timestamp of thenotification in seconds since
January 1, 1970.

tptTrhaNotifyNewState

1.3.6.1.4.1.10734.3.3.3.1.88

State of the connection to thedevice’s transparent HA
partner:• not connected• connected

The following notifications and SNMP traps apply to Zero-Power HA (ZPHA).
ObjectOID

Description

tptZphaNotify

1.3.6.1.4.1.10734.3.3.3.0.24

The notification object that
informs the management
station of changes in the
ZPHA state of the device.

tptZphaNotifyDeviceID

1.3.6.1.4.1.10734.3.3.3.1.161

The unique identifier of thedevice sending thenotification.

tptZphaNotifyTimeStamp

1.3.6.1.4.1.10734.3.3.3.1.162

The timestamp of thenotification in seconds since
January 1, 1970.

tptZphaNotifySegmentName

1.3.6.1.4.1.10734.3.3.3.1.163

The name of the segment on
which ZPHA is enabled.

tptZphaNotifyNewState

1.3.6.1.4.1.10734.3.3.3.1.164

The current ZPHA state of thesegment:• 0: normal, ZPHA inactive• 1: IPS bypass, ZPHA
active

The following notifications and SNMP traps apply to changes in the
Performance Protection state.

1-21

TPS MIBs Guide

ObjectOID

Description

tptPerfProtNotify

1.3.6.1.4.1.10734.3.3.3.0.21

Triggered when performanceprotection is triggered byengine or NIC congestion.

tptPerfProtNotifyDeviceID

1.3.6.1.4.1.10734.3.3.3.1.141

The unique identifier of thedevice sending thenotification.

tptPerfProtNotifyTimeStamp

1.3.6.1.4.1.10734.3.3.3.1.142

The timestamp of thenotification in seconds since
January 1, 1970.

tptPerfProtNotifyPhase

1.3.6.1.4.1.10734.3.3.3.1.143

Indicates the current
performance protectionmode:• 1: entering• 2: continuing• 3: exiting

1-22

tptPerfProtNotifyPacketLoss

1.3.6.1.4.1.10734.3.3.3.1.144

The current packet loss rate
per thousand. When exiting
performance protectionmode, the value will always
be 0 (zero).

tptPerfProtNotifyLossThreshold

1.3.6.1.4.1.10734.3.3.3.1.145

The current packet loss
threshold per thousand.

tptPerfProtNotifyDuration

1.3.6.1.4.1.10734.3.3.3.1.146

The number of seconds that
performance protection will
be active.

tptPerfProtNotifyMissedAlerts

1.3.6.1.4.1.10734.3.3.3.1.147

The number of alerts missed
during the performanceprotection period. When
exiting performanceprotection mode, the value
will always be 0 (zero).

TPS MIBs Guide

TPT-HOSTDefines the IPS host information, the default gateway address, and indicates
whether the device is currently configured for service access.
ObjectOID

Description

hostIPv4Gateway

1.3.6.1.4.1.10734.3.3.2.12.2

The IPv4 default gateway.

hostIPv6Gateway

1.3.6.1.4.1.10734.3.3.2.12.3

The IPv6 default gateway.
• 0: disabled• 1: enabled

hostIPv6Enabled

1.3.6.1.4.1.10734.3.3.2.12.4

Indicates whether IPv6 isenabled on the device.
• 0: disabled• 1: enabled

hostSSLCert

1.3.6.1.4.1.10734.3.3.2.12.8

The currently active SSL cert.
• 0: none• 1: temporary• 2: authorized

hostInitState

1.3.6.1.4.1.10734.3.3.2.12.9

The current host initialization
state.
• 0: in progress• 1: complete

TPT-LICENSE
Support for TippingPoint license packages, including TOS, Digital Vaccine,
Reputation DV, and other services.
ObjectlicenseTable

OID
1.3.6.1.4.1.10734.3.3.2.15.1

Description
Table of licensed features.

1-23

TPS MIBs Guide

ObjectOID

Description

licenseEntry

1.3.6.1.4.1.10734.3.3.2.15.1.1

An entry in the licensedfeatures table. Rows cannot
be added or deleted.

licenseEntryIndex

1.3.6.1.4.1.10734.3.3.2.15.1.1.
1

The index number of theentry.

licenseEntryFeature

1.3.6.1.4.1.10734.3.3.2.15.1.1.
2

The name of the licensedfeature.

licenseEntryStatus

1.3.6.1.4.1.10734.3.3.2.15.1.1.
3

Status of the licensed feature:• 0: informational
message• 1: license valid• 2: warning• 3: error

licenseEntryAction

1.3.6.1.4.1.10734.3.3.2.15.1.1.
4

Action to take for the licensedfeature.
• 0: allow• 1: denylicenseEntryExpiry

1.3.6.1.4.1.10734.3.3.2.15.1.1.
5

The date on which thislicensed feature will expire.

licenseEntryDetails

1.3.6.1.4.1.10734.3.3.2.15.1.1.
6

Any additional information
about this licensed feature.

TPT-MISC-NOTIFY-MIB
Notifications for logs and other features.
Note
The MIB file includes references to Network Discovery Scan.

This object applies to all notifications.

1-24

TPS MIBs Guide

Common TPT notification objects
The following table describes general notification objects:
ObjecttptMiscNotifyDeviceID

OID

Description

1.3.6.1.4.1.10734.3.3.3.1.31

The unique identifier of thedevice sending the notification.
This is the first payload
parameter for all notifications in
the TPT-MISC-NOTIFY module.

Management TPT notification objects
The following table describes management notification objects. These
notifications communicate with the management station:
ObjectOID

Description

tptManagedNotify

1.3.6.1.4.1.10734.3.3.3.0.9

Informs the management stationthat the device is now being
managed by that station

tptUnmanagedNotify

1.3.6.1.4.1.10734.3.3.3.0.10

Informs the management stationthat the device is no longer
being managed by that station

Quarantine TPT notification objects
The following notifications are generated by quarantine actions:
OID

Description

tptQuarantineNotify

1.3.6.1.4.1.10734.3.3.3.0.20

The notification thatindicates that a host has
been added to or removed
from the quarantine list.

tptQuarantineNotifyNetAddr

1.3.6.1.4.1.10734.3.3.3.1.132

The network address of thehost being quarantined or
removed from thequarantine list.

Object1-25

TPS MIBs Guide

ObjectOID

Description

tptQuarantineNotifyHostNetAddr
V6

1.3.6.1.4.1.10734.3.3.3.1.133

The IPv6 network addressof the host.

tptQuarantineNotifyReason

1.3.6.1.4.1.10734.3.3.3.1.134

The reason that the hostwas quarantined. The
parameter is undefined if
the host was removed.

tptQuarantineNotifySegmentNa
me

1.3.6.1.4.1.10734.3.3.3.1.135

The segment related to thequarantine or removal fromthe quarantine list.

tptQuarantineNotifyAction

1.3.6.1.4.1.10734.3.3.3.1.136

Whether the host wasadded to or removed fromthe quarantine list.
• 1: add• 2: remove

tptQuarantineNotifySslInspected.1.3.6.1.4.1.10734.3.3.3.1.18
1Flag indicating if thisquarantine action was
performed on an inspected
SSL data stream.
• 1: Yes• 2: No

Congestion notifications
The following notifications and SNMP traps are generated when congestion
thresholds are met.
ObjecttptCongestionPacketLoss

1-26

OID

Description

1.3.6.1.4.1.10734.3.3.3.1.153

The current packet-loss rate
per thousand.

TPS MIBs Guide

ObjecttptCongestionNotifyPhase

OID

Description

1.3.6.1.4.1.10734.3.3.3.1.154

Indicates whether the device
is entering, continuing, or
exiting congestion thresholdmode.
• 1: entering• 2: continuing• 3: exiting

tptCongestionThreshold

1.3.6.1.4.1.10734.3.3.3.1.155

The current packet-loss
threshold per thousand.

tptTier3CongestionPacketLoss1.3.6.1.4.1.10734.3.3.3.1.156

The current Tier 3 packet-loss
rate per thousand.

tptTier3CongestionNotifyPha
se

1.3.6.1.4.1.10734.3.3.3.1.157

Indicates whether the device
is entering, continuing, or
exiting Tier 3 congestion
threshold mode.

tptTier3CongestionThreshold

1.3.6.1.4.1.10734.3.3.3.1.158

The current Tier 3 packet-loss
threshold per thousand.

tptCongestionThresholdNotify1.3.6.1.4.1.10734.3.3.3.0.25

The notification that thedevice-wide congestion hasreached the configured
congestion threshold.
Triggered only by engine
congestion, not NIC
congestion.

tptiTier3CongestionNotify

1.3.6.1.4.1.10734.3.3.3.0.26

The notification that the Tier
3 congestion has reached theconfigured congestion
threshold. Triggered only byengine congestion, not NIC
congestion.

1-27

TPS MIBs Guide

System Log TPT notification objects
The following notifications are generated when a critical message, error
message, or warning is logged in the system log:
Note
These objects are deprecated.
ObjectOID

Description

tptSystemLogNotify

1.3.6.1.4.1.10734.3.3.3.0.16

The notification that a criticalmessage, error message, or
warning has been logged.

tptSystemLogNotifyText

1.3.6.1.4.1.10734.3.3.3.1.92

The text of the message being
logged.

tptSystemLogNotifySequence

1.3.6.1.4.1.10734.3.3.3.1.93

The log file entry sequencenumber corresponding to thisnotification. This value will
always be 0 (zero).

tptSystemLogNotifySeverity

1.3.6.1.4.1.10734.3.3.3.1.94

The severity of the attack:• 1: critical• 2: error• 4: warning

tptSystemLogNotifyTimeSec

1.3.6.1.4.1.10734.3.3.3.1.95

The time that this message waslogged, in seconds since January
1, 1970.

tptSystemLogNotifyTimeNano

1.3.6.1.4.1.10734.3.3.3.1.96

The nanoseconds portion of
tptSystemLogNotifyTimeSec.

Audit Log TPT notification objects
The following notifications are generated when a message or warning islogged in the audit log:

1-28

TPS MIBs Guide

Note
These objects are deprecated.
ObjectOID

Description

tptAuditLogCapacityNotify
Percent

1.3.6.1.4.1.10734.3.3.3.1.201

The percentage of the audit log
data threshold.

tptAuditLogCapacityOrFail
ureNotifyTime

1.3.6.1.4.1.10734.3.3.3.1.202

The time of the data capacity
threshold notification.

tptAuditLogNotify

1.3.6.1.4.1.10734.3.3.3.0.60

Audit log notification uses thefollowing fields:• tptMiscNotifyDeviceID• tptAuditLogNotifyTime• tptAuditLogNotifyAccess• tptAuditLogNotifyType• tptAuditLogNotifyIpAddrType• tptAuditLogNotifyIpAddr• tptAuditLogNotifyCategory• tptAuditLogNotifyResult• tptAuditLogNotifyUser• tptAuditLogNotifyMessage

tptAuditLogNotifyTime

1.3.6.1.4.1.10734.3.3.3.1.170

The date and time when theentry was logged.

1-29

TPS MIBs Guide

ObjectOID

tptAuditLogNotifyAccess1.3.6.1.4.1.10734.3.3.3.1.171

Description
The access level of the user
initiating the audit check andgenerating the log.
This is a bit field with thefollowing mapping:• 0x0 – normal• 0x1 – operator• 0x4 – administrator• 0x8 – super-user

1-30

tptAuditLogNotifyType

1.3.6.1.4.1.10734.3.3.3.1.172

Interface source of the audit log
action.

tptAuditLogNotifyIpAddrT
ype

1.3.6.1.4.1.10734.3.3.3.1.173

Type of IP address from which
the user connected.

tptAuditLogNotifyIpAddr

1.3.6.1.4.1.10734.3.3.3.1.174

IP address from which the user
connected

TPS MIBs Guide

ObjectOID

Description

tptAuditLogNotifyCategory

1.3.6.1.4.1.10734.3.3.3.1.175

Functional area where the audit
log was generated:
1: undefined
2: general
3: login
4: logout
5: user
6: time7: policy
8: update
9: boot
10: report
11: host
12: cfg
13: device
14: sms
15: server
16: segment
17: license
18: ha19: monitor
20: ipFilter
21: connTable
22: hostComm
23: tse24: cf

1-31

TPS MIBs Guide

ObjectOID

tptAuditLogNotifyResult

1.3.6.1.4.1.10734.3.3.3.1.176

Description
The result, pass or fail, of anaudit check:
1: success
2: failed

tptAuditLogNotifyUser

1.3.6.1.4.1.10734.3.3.3.1.177

The user initiating the audit
check and generating the log.

tptAuditLogNotifyMessage

1.3.6.1.4.1.10734.3.3.3.1.178

A description of what
configuration change wasattempted (and possibly
succeeded) by the user.

TPT-MULTIDV-MIB
Manages the Multiple Digital Vaccine feature. This feature allows the IPS tomanage multiple types of Digital Vaccine packages, if they are currently
available from Trend.
ObjectDescription

installedDVTable

1.3.6.1.4.1.10734.3.3.2.1.10.
2.1

Table of installed Digital
Vaccine (DV) packages.

installedDVEntry

1.3.6.1.4.1.10734.3.3.2.1.10.
2.1.1

An entry in the Installed DV
table. Rows cannot be addedor removed.

installedDVIndex

1.3.6.1.4.1.10734.3.3.2.1.10.
2.1.1.1.1

Index of the DVs installed.

installedDVVersion

1.3.6.1.4.1.10734.3.3.2.1.10.
2.1.1.2.1

The version number of the DV
on this machine.

installedDVIsActive

1.3.6.1.4.1.10734.3.3.2.1.10.
2.1.1.3.1

The active state of the DV.

Auxiliary DV objects

1-32

OID

TPS MIBs Guide

ObjectOID

Description

auxiliaryDVTable

1.3.6.1.4.1.10734.3.3.2.1.10.2.
2

Table of auxiliary Digital
Vaccine (DV) packages.

auxiliaryDVEntry

1.3.6.1.4.1.10734.3.3.2.1.10.2.
2.1

An entry in the Auxiliary DV
table. Rows cannot be addedor removed.

auxiliaryDVIndex

1.3.6.1.4.1.10734.3.3.2.1.10.2.
2.1.1

The index number of theentry.

auxiliaryDVType1.3.6.1.4.1.10734.3.3.2.1.10.2.
2.1.2

The type of the auxiliary DV.

auxiliaryDVName

1.3.6.1.4.1.10734.3.3.2.1.10.2.
2.1.3

The name of the auxiliary DV.

auxiliaryDVVersion

1.3.6.1.4.1.10734.3.3.2.1.10.2.
2.1.4

The auxiliary DV version
number.

auxiliaryDVPackage

1.3.6.1.4.1.10734.3.3.2.1.10.2.
2.1.5

The auxiliary DV version in
string format:
major.minor.patch.build

TPT-NPSTATS-MIB
Information about network processor statistics.
The following objects apply to the NP tier statistics.
OID

Description

npstatsTiersTable

1.3.6.1.4.1.10734.3.3.2.10.2

A table of network processor
statistics, sorted by tier.

npstatsTiersEntry

1.3.6.1.4.1.10734.3.3.2.10.2.1

An entry in the network
processor statistics tiers
table.

npstatsTierNumber

1.3.6.1.4.1.10734.3.3.2.10.2.1.
1

The tier number.

Object1-33

TPS MIBs Guide

Object

1-34

OID

Description

npstatsTiersReceiveMbps

1.3.6.1.4.1.10734.3.3.2.10.2.1.
2

The current receive rate on
the tier in Mbps.

npstatsTiersRxPktsPerSec

1.3.6.1.4.1.10734.3.3.2.10.2.1.
4

The current receive rate inpackets per second.

npstatsTiersMaxPktsPerSec

1.3.6.1.4.1.10734.3.3.2.10.2.1.
5The maximum receive rate inpackets per second.

npstatsTiersAvgBytesPerPkt

1.3.6.1.4.1.10734.3.3.2.10.2.1.
6

The average packet size inbytes.

npstatsTiersUtilizationPercent1.3.6.1.4.1.10734.3.3.2.10.2.1.
7

The percent utilization of thistier.

npstatsTier1UtilizationPercent1.3.6.1.4.1.10734.3.3.2.10.2.1.
7.1

Utilization ratio of total traffic
against the licensed
throughput of the device forTier-1.

npstatsTier2UtilizationPercent1.3.6.1.4.1.10734.3.3.2.10.2.1.
7.2

Utilization ratio of total traffic
against the licensed
throughput of the device forTier-2.

npstatsTier3UtilizationPercent1.3.6.1.4.1.10734.3.3.2.10.2.1.
7.3

Utilization ratio of total traffic
against the licensed
throughput of the device forTier-3.

npstatsTier4UtilizationPercent1.3.6.1.4.1.10734.3.3.2.10.2.1.
7.4

Utilization ratio of total traffic
against the licensed
throughput of the device forTier-4.

npstatsTiersRatioToNextPer1
0K

1.3.6.1.4.1.10734.3.3.2.10.2.1.
8

The ratio of this tier’s
throughput to the next per
10,000.

TPS MIBs Guide

ObjectOID

Description

npstatsTiersMaxReceiveMbps

1.3.6.1.4.1.10734.3.3.2.10.2.1.
9The maximum receive rate in
Mbps.

npstatsTiersMaxTransmitMbps

1.3.6.1.4.1.10734.3.3.2.10.2.1.
10The maximum transmit rate
in Mbps.

npstatsTiersMaxUtilizationPer
cent

1.3.6.1.4.1.10734.3.3.2.10.2.1.
2.11

The maximum percent
utilization of this tier.

npstatsTierMaxRatiotoNextPe
r10K

1.3.6.1.4.1.10734.3.3.2.10.2.1.
2.12

The max ratio of this tier's
throughput to the next per
10K.

The following objects apply to other NP statistics.
OID

Description

npstatsTiersExtra

1.3.6.1.4.1.10734.3.3.2.10.3

A list of additional network
processor statistics
information.

npstatsTier1BypassMbps

1.3.6.1.4.1.10734.3.3.2.10.3.1

The current bypass rate in
Mbps.

npstatsTier1Balance

1.3.6.1.4.1.10734.3.3.2.10.3.2

The load balance acrossnetwork processors. A valueof 1000 is exactly balanced,
and 0 indicates all traffic isbeing handled on one
processor. For TPS devices,
this value is always 0 (zero).

npstatsTier1MaxPktsPerSecA

1.3.6.1.4.1.10734.3.3.2.10.3.3

The maximum processor A
receive rate in packets per
second.

npstatsTier1MaxPktsPerSecB

1.3.6.1.4.1.10734.3.3.2.10.3.4

The maximum processor B
receive rate in packets per
second. For TPS devices, thisvalue is always 0 (zero).

Object1-35

TPS MIBs Guide

Object

1-36

OID

Description

npstatsTier1TxPktsPerSec

1.3.6.1.4.1.10734.3.3.2.10.3.8

The transmit rate in packets
per second.

npstatsTier1MaxTxPktsPerSec

1.3.6.1.4.1.10734.3.3.2.10.3.9

The maximum transmit ratein packets per second.

npstatsTier4TriggerMatchPer
1000

1.3.6.1.4.1.10734.3.3.2.10.3.5

Proportion of traffic
inspected because of a trigger
match (percent value times
100).

npstatsTier4ReroutePer1000

1.3.6.1.4.1.10734.3.3.2.10.3.6

Proportion of traffic
inspected because of areroute (percent value times
100).

npstatsTier4ProtoDcdPer1000

1.3.6.1.4.1.10734.3.3.2.10.3.11

Percentage of reroute packets
that are sent to TCP
reassembly when additional
analysis is required of a
protocol. Protocols that needfurther analysis include FTP
commands, Telnet, HTTP
encoded frames, Microsoft
SMB frames, and Microsoft
RPC frames.

npstatsTier4TcpSequencePer
1000

1.3.6.1.4.1.10734.3.3.2.10.3.7

Proportion of traffic
inspected because of TCP
sequence (percent value
times 100).

npstatsTier1MaxPktsPerSecC

1.3.6.1.4.1.10734.3.3.2.10.3.10

The maximum receive rate forprocessor C in packets per
second. For TPS devices, thisvalue is always 0 (zero).

npstatsTier1PatternMatch
ToRxPktsPerSecRatio

1.3.6.1.4.1.10734.3.3.2.10.3.21

The ratio of this tier’s patternmatch packets per second to
RX packets per second.

TPS MIBs Guide

ObjectOID

Description

npstatsTier1MaxPatternMatch
ToRxPktsPerSecRatio

1.3.6.1.4.1.10734.3.3.2.10.3.22

The maximum ratio of thistier’s pattern match packets
per second to RX packets per
second.

npstatsTier2MaxTxTrustedPkt
sPerSec

1.3.6.1.4.1.10734.3.3.2.10.3.23

The maximum Tier 2 Trusted
packets transmit rate inpackets per second.

npstatsTier3MaxTxTrustedPkt
sPerSec

1.3.6.1.4.1.10734.3.3.2.10.3.24

The maximum Tier 3 Trusted
packets transmit rate inpackets per second.

npstatsTier4MaxTxTrustedPkt
sPerSec

1.3.6.1.4.1.10734.3.3.2.10.3.25

The maximum Tier 4 Trusted
packets transmit rate inpackets per second.

npstatsTier4MaxTriggerMatch
Per1000

1.3.6.1.4.1.10734.3.3.2.10.3.26

Maximum proportion of
traffic inspected because oftrigger match (percent value
times 100).

npstatsTier4MaxReroutePer1000

1.3.6.1.4.1.10734.3.3.2.10.3.27

Maximum proportion of
traffic inspected because ofreroute (percent value times
100).

npstatsTier4MaxTcpSequence
Per1000

1.3.6.1.4.1.10734.3.3.2.10.3.28

Maximum proportion of
traffic inspected because of
TCP sequence (percent value
times 100).

npstatsTier4MaxProtoDcdPer
1000

1.3.6.1.4.1.10734.3.3.2.10.3.29

Maximum proportion ofreroute traffic inspected
because of protocol decode(percent value times 100).

npstatsMisc

1.3.6.1.4.1.10734.3.3.2.10.4

Miscellaneous network
processor statisticalinformation.

1-37

TPS MIBs Guide

1-38

ObjectOID

Description

npstatsMiscTxPktsBestEffort

1.3.6.1.4.1.10734.3.3.2.10.4.1

The number of packets per
second transmitted becauseof best effort mode.

npstatsMiscThroughputCurrent

1.3.6.1.4.1.10734.3.3.2.10.4.2

Current throughput in Kbps.

npstatsMiscThroughputPercent

1.3.6.1.4.1.10734.3.3.2.10.4.3

Current percentage oflicensed throughput.

npstatsMiscThroughputLicensed

1.3.6.1.4.1.10734.3.3.2.10.4.4

Licensed throughput in Kbps.

npstatsMiscThroughputHigh
WaterMark

1.3.6.1.4.1.10734.3.3.2.10.4.5

The highest throughput level
reached since the last clear or
reboot in Kbps.

npstatsMiscThroughputHigh
WaterMarkPercent

1.3.6.1.4.1.10734.3.3.2.10.4.6

The maximum seen
percentage of the licensed
throughput since the lastclear or reboot.

npstatsMiscThroughputNotify
DeviceID

1.3.6.1.4.1.10734.3.3.3.1.361

The unique identifier of thedevice sending thisnotification.

npstatsMiscThroughputNotify
TimeStamp

1.3.6.1.4.1.10734.3.3.3.1.362

The time of this notification(in seconds since January 1,1970).

npstatsMiscThroughputNotify
State

1.3.6.1.4.1.10734.3.3.3.1.363

The Throughput Utilization
state on the device.

npstatsMiscThroughputNotify
Transition

1.3.6.1.4.1.10734.3.3.3.1.364

The Throughput Utilization
state transition on the device.

npstatsMiscThroughputNotify
Current

1.3.6.1.4.1.10734.3.3.3.1.365

The current Throughput
Utilization in Kbps.

TPS MIBs Guide

ObjectOID

Description

npstatsMiscThroughputNotify

1.3.6.1.4.1.10734.3.3.3.0.80

Notification used to informthe management station ofchanges in the Throughput
Utilization state on thedevice.

Segment port stats
Statistical information pertaining to network segments for a stackconfiguration.
ObjectOID

Description

npstatsStackSegmentReceiveMbps

1.3.6.1.4.1.10734.3.3.2.10.1
0.1

Aggregate Rx rate in Mbps
from all network
segments.

npstatsStackSegmentMaxReceiveMbps

1.3.6.1.4.1.10734.3.3.2.10.1
0.2

Maximum Rx rate in Mbps
from all network
segments.

npstatsStackSegmentTransmitMbps

1.3.6.1.4.1.10734.3.3.2.10.1
0.3

Aggregate Tx rate in Mbps
to all network segments.

npstatsStackSegmentMaxTransmit
Mbps

1.3.6.1.4.1.10734.3.3.2.10.1
0.4

Maximum Tx rate in Mbps
to all network segments.

npstatsStackBalance

1.3.6.1.4.1.10734.3.3.2.10.1
0.5

The load balance percent
across all stack members.

npstatsStackMinBalance

1.3.6.1.4.1.10734.3.3.2.10.1
0.6

The minimum, non-zeroload balance percent
across all stack members.

npstatsStackSegmentRatioToTier1
Per10K

1.3.6.1.4.1.10734.3.3.2.10.1
0.7

The ratio of this tier's
throughput to tier 1 per
10,000 (percent value
times 100).

1-39

TPS MIBs Guide

ObjectOID

Description

npstatsStackSegmentMaxRatioToTi
er1Per10K

1.3.6.1.4.1.10734.3.3.2.10.1
0.8

The maximum ratio of thistier's throughput to tier 1
per 10,000 (percent value
times 100).

Stack member table
Statistical information related to network segments for each stack member.
ObjectOID

Description

npstatsStackMemberKey

1.3.6.1.4.1.10734.3.3.2.10.
10.9.1.2

Unique stack member
identifier.

npstatsStackMemberHostname

1.3.6.1.4.1.10734.3.3.2.10.
10.9.1.3

The stack member hostname.

npstatsStackMemberSegmentRecei
veMbps

1.3.6.1.4.1.10734.3.3.2.10.
10.9.1.4

The current segment Rx
rate in Mbps for a stackmember.

npstatsStackMemberMaxSegmentR
eceiveMbps

1.3.6.1.4.1.10734.3.3.2.10.
10.9.1.5

The maximum segment Rx
rate in Mbps for a stackmember.

Stacking port stats
Statistical information pertaining to stacking ports in a stack configuration.

1-40

ObjectOID

Description

npstatsStackPortsReceiveMb
ps

1.3.6.1.4.1.10734.3.3.2.10.11.1

Aggregate Rx rate in Mbps
from all stacking ports.

npstatsStackPortsMaxReceive
Mbps

1.3.6.1.4.1.10734.3.3.2.10.11.2

Maximum Rx rate in Mbps
from all stacking ports.

npstatsStackPortsTransmitM
bps

1.3.6.1.4.1.10734.3.3.2.10.11.3

Aggregate Tx rate in Mbps forall stacking ports.

TPS MIBs Guide

ObjectOID

Description

npstatsStackPortsMaxTransm
itMbps

1.3.6.1.4.1.10734.3.3.2.10.11.4

Maximum Tx rate in Mbps forall stacking ports.

npstatsStackRxToStackTxMbps

1.3.6.1.4.1.10734.3.3.2.10.11.5

Aggregate through traffic ratefrom segment ports tostacking ports.

npstatsStackMaxRxToStackTx
Mbps

1.3.6.1.4.1.10734.3.3.2.10.11.6

The maximum through traffic
rate from segment ports tostacking ports.

npstatsStackRxToSegmentTx
Mbps

1.3.6.1.4.1.10734.3.3.2.10.11.7

Return rate in Mbps for traffic
coming in on the stacking
ports and transmitted to thesegment ports.

npstatsStackMaxRxToSegmen
tTxMbps

1.3.6.1.4.1.10734.3.3.2.10.11.8

Maximum return rate in Mbps
for traffic coming in on thestacking ports andtransmitted to the segment
ports.

npstatsStackRatioToTier1Per1
0K

1.3.6.1.4.1.10734.3.3.2.10.11.9

Percent of traffic being
inspected by this device as aratio of the stack Rx traffic totier 1 per 10,000 (percent
value times 100).

npstatsStackMaxRatioToTier1
Per10K

1.3.6.1.4.1.10734.3.3.2.10.11.1
0Maximum percent of traffic
being inspected by thisdevice as a ratio of the stack
Rx traffic to tier 1 per 10,000(percent value times 100).

SSL inspection objects
SSL Inspection (SslInsp) objects provide information about SSL inspection
activity.

1-41

TPS MIBs Guide

ObjectOID

Description

npstatsSslInsp

1.3.6.1.4.1.10734.3.3.2.10.5

Sub-tree for all SSL inspection
statistics.

npstatsSslInspCurrentSessions1.3.6.1.4.1.10734.3.3.2.10.5.1

The current number of active
SSL sessions. This value is not
real-time and will lag
approximately 2 minutes from
actual, due to the timeinterval for calculating therate.

npstatsSslInspConnectionRate

1.3.6.1.4.1.10734.3.3.2.10.5.2

The average SSL connection
rate in connections per
second.

npstatsSslInspBlockedMaxConns

1.3.6.1.4.1.10734.3.3.2.10.5.3

The number of blocked SSL
sessions due to maximum
connection limit.

npstatsSslInspPassedMaxCon
ns

1.3.6.1.4.1.10734.3.3.2.10.5.4

The number of passed (notinspected) SSL sessions due tomaximum connection limit.

npstatsSslInspTotalBytesIn

1.3.6.1.4.1.10734.3.3.2.10.5.5

The number of inspected
inbound SSL bytes.

npstatsSslInspTotalBytesOut

1.3.6.1.4.1.10734.3.3.2.10.5.6

The number of inspected
outbound SSL bytes.

TPT-POLICY-MIB
The following notifications are generated by policy actions:ObjecttptPolicyNotify

1-42

OID

Description

1.3.6.1.4.1.10734.3.3.3.0.8

The notification that a policy
action has resulted from asignature match.

TPS MIBs Guide

ObjectOID

Description

tptPolicyNotifyClientip

1.3.6.1.4.1.10734.3.3.3.1.139

The client IP address
associated with thenotification. This value isalways set to "".

tptPolicyNotifyDeviceID

1.3.6.1.4.1.10734.3.3.3.1.11

The unique identifier of thedevice sending the policy
notification.

tptPolicyNotifyMetadata

1.3.6.1.4.1.10734.3.3.3.1.140

Additional event information
associated with thenotification. Because thisobject is targeted for future
support, this value is always
set to N/A.

tptPolicyNotifyPolicyID

1.3.6.1.4.1.10734.3.3.3.1.12

The unique identifier of thepolicy that causes thenotification.

tptPolicyNotifySignatureID

1.3.6.1.4.1.10734.3.3.3.1.13

The unique identifier of thesignature matching theincoming data stream.

tptPolicyNotifySegmentName(obsolete)

1.3.6.1.4.1.10734.3.3.3.1.14

The name of the segment towhich the notification applies.
Not included in notification.

tptPolicyNotifySrcNetAddr

1.3.6.1.4.1.10734.3.3.3.1.15

The IPv4 address of the sourceof the packet that triggered
the policy action.

tptPolicyNotifySrcNetAddrV6

1.3.6.1.4.1.10734.3.3.3.1.128

The IPv6 address of the sourceof the packet that triggered
the policy action.

tptPolicyNotifySrcNetPort

1.3.6.1.4.1.10734.3.3.3.1.16

The source port of the packet
that triggered the policy
action.

tptPolicyNotifyDestNetAddr

1.3.6.1.4.1.10734.3.3.3.1.17

The IPv4 address of thedestination of the packet thattriggered the policy action.

1-43

TPS MIBs Guide

ObjectOID

Description

tptPolicyNotifyDestNetAddrV6

1.3.6.1.4.1.10734.3.3.3.1.129

The IPv6 address of thedestination of the packet thattriggered the policy action.

tptPolicyNotifyDestNetPort

1.3.6.1.4.1.10734.3.3.3.1.18

The destination port of thepacket that triggered thepolicy action.

tptPolicyNotifyStartTimeSec

1.3.6.1.4.1.10734.3.3.3.1.19

The time at which the policy
was first triggered, marking
the start of the aggregation
period for this notification.
Measured in seconds since
January 1, 1970.

tptPolicyNotifyAlertAction

1.3.6.1.4.1.10734.3.3.3.1.20

The action associated with thisnotification.
• 1: deny• 2: allow

tptPolicyNotifyConfigAction

1.3.6.1.4.1.10734.3.3.3.1.21

The action configured for thepolicy, which in some cases
can differ from the action
associated with thenotification.
• 1: deny• 2: allow

tptPolicyNotifyComponentID

1.3.6.1.4.1.10734.3.3.3.1.22

The component identifier ofthe policy that causes thenotification:• 0: invalid• 1: deny• 2: allow• 7: alert• 8: block• 9: peer

1-44

TPS MIBs Guide

ObjectOID

Description

tptPolicyNotifyHitCount

1.3.6.1.4.1.10734.3.3.3.1.23

The number of policy hits
occurring during theaggregation period for thisnotification.

tptPolicyNotifyAggregationPer
iod

1.3.6.1.4.1.10734.3.3.3.1.24

The duration of theaggregation period for thisnotification, in minutes.

tptPolicyNotifySeverity

1.3.6.1.4.1.10734.3.3.3.1.25

The severity of the attack.
• 1: low• 2: minor• 3: major• 4: critical

tptPolicyNotifyProtocol

1.3.6.1.4.1.10734.3.3.3.1.26

The network protocol of thepacket(s) that triggered thepolicy action.
• 1: ICMP• 2: UDP• 3: TCP• 4: other IP• 5: ARP• 6: other ETH• 7: ICMP v6• 8: other IPV6

tptPolicyNotifyAlertTimeSec

1.3.6.1.4.1.10734.3.3.3.1.27

The time that the alert was
initiated, marking the end of
the aggregation period for thisnotification. Measured inseconds since January 1, 1970.

tptPolicyNotifyAlertTimeNano

1.3.6.1.4.1.10734.3.3.3.1.28

The nanoseconds portion of
the AlertTimeSec object.

1-45

TPS MIBs Guide

ObjecttptPolicyNotifyPacketTrace

OID

Description

1.3.6.1.4.1.10734.3.3.3.1.29

Indicates if a corresponding
packet trace was logged.
• 0: not logged• 1: logged.

tptPolicyNotifySequence

1.3.6.1.4.1.10734.3.3.3.1.30

The log file entry sequencenumber corresponding to thisnotification. This value isalways set to 0 (zero).

tptPolicyNotifyTraceBucket

1.3.6.1.4.1.10734.3.3.3.1.36

The bucket identifier for apacket trace.

tptPolicyNotifyTraceBegin1.3.6.1.4.1.10734.3.3.3.1.37

The starting sequence number
for a packet trace.

tptPolicyNotifyTraceEnd

1.3.6.1.4.1.10734.3.3.3.1.38

The ending sequence number
for a packet trace.

tptPolicyNotifyMessageParams

1.3.6.1.4.1.10734.3.3.3.1.39

A string containing parameters
separated by vertical bars (|)
that match information taggedwith Message in the Digital
Vaccine.

tptPolicyNotifyStartTimeNano

1.3.6.1.4.1.10734.3.3.3.1.40

The nanoseconds portion ofStartTimeSec.

tptPolicyNotifyAlertType

1.3.6.1.4.1.10734.3.3.3.1.41

A bit field defined as follows:• 0x0001 = Alert• 0x0002 = Block• 0x0020 = Peer-to-peer• 0x0040 = Invalid• 0x0080 = Threshold• 0x0100 = Management.

tptPolicyNotifyInputMphy

1-46

1.3.6.1.4.1.10734.3.3.3.1.57

The incoming physical port of
the triggering packet(s).

TPS MIBs Guide

ObjectOID

Description

tptPolicyNotifyVlanTag

1.3.6.1.4.1.10734.3.3.3.1.58

The VLAN tag of the triggering
packet(s).

tptPolicyNotifyZonePair

1.3.6.1.4.1.10734.3.3.3.1.59

A string that identifies the port
pair related to thisnotification. This value isalways set to "".

tptPolicyNotifyActionSetID

1.3.6.1.4.1.10734.3.3.3.1.130

The action set UUID
associated with thisnotification.

tptPolicyNotifyRate

1.3.6.1.4.1.10734.3.3.3.1.131

The rate-limit, in kbps, of theaction set associated with thisnotification.

tptPolicyNotifyFlowControl

1.3.6.1.4.1.10734.3.3.3.1.137

The action set flow control
associated with thisnotification.

tptPolicyNotifyActionSetName

1.3.6.1.4.1.10734.3.3.3.1.138

The action set nameassociated with thisnotification.

tptPolicyNotifySslInspected.1.3.6.1.4.1.10734.3.3.3.1.18
0

A flag indicating if thenotification is associated withan inspected SSL data stream.
This flag is only present on IPS
and Quarantine events anddoesn't apply to Reputation.
1: Yes2: No

tptPolicyNotifyVirtualSegment.1.3.6.1.4.1.10734.3.3.3.1.18
2

Virtual segment associatedwith this notification.

tptPolicyNotifySslInspEventTy
pe.1.3.6.1.4.1.10734.3.3.3.1.19
0

The SSL connection type. 1:
inbound 2: outbound (notsupported)

1-47

TPS MIBs Guide

ObjectOID

tptPolicyNotifySslInspAction.1.3.6.1.4.1.10734.3.3.3.1.19
1

Description
The SSL connection action
taken• 1: decrypted• 2: notDecrypted• 3: blocked

tptPolicyNotifySslInspDetails.1.3.6.1.4.1.10734.3.3.3.1.19
2

Free-form field that provides
additional details for theaction taken on a SSL
connection

tptPolicyNotifySslInspPolicy.1.3.6.1.4.1.10734.3.3.3.1.19
3

The SSL inspection policy.

tptPolicyNotifySslInspCert.1.3.6.1.4.1.10734.3.3.3.1.19
4

The certificate used to decrypt
SSL traffic.

tptPolicyNotifySslInspCltIF.1.3.6.1.4.1.10734.3.3.3.1.19
5The client-side interface
receiving SSL traffic.

tptPolicyNotifySslInspCltSslVer.1.3.6.1.4.1.10734.3.3.3.1.19
6

The client-side SSL protocol
version.
• 1: unknown• 2: sslv3• 3: tls10• 4: tls11• 5: tls12

1-48

tptPolicyNotifySslInspCltCrypto.1.3.6.1.4.1.10734.3.3.3.1.19
7

The client-side SSL cryptosuite.

tptPolicyNotifySslInspSrvIF.1.3.6.1.4.1.10734.3.3.3.1.19
8The server-side interface
sending SSL traffic.

TPS MIBs Guide

ObjectOID

Description

tptPolicyNotifySslInspSrvSslVer.1.3.6.1.4.1.10734.3.3.3.1.19
9The server-side SSL protocol
version.
• 1: unknown• 2: sslv3• 3: tls10• 4: tls11• 5: tls12

tptPolicyNotifySslInspSrvCryp
to.1.3.6.1.4.1.10734.3.3.3.1.20
0The server-side SSL cryptosuite.

The following variables apply to various policy statistics.
OID

Description

policyPacketsDropped

1.3.6.1.4.1.10734.3.3.2.1.1.0

The total number of packets
discarded because of network
congestion.

policyPacketsDropped64

1.3.6.1.4.1.10734.3.3.2.1.31.
0

The total number of 64-bit
packets discarded because of
network congestion.

policyPacketsBlocked

1.3.6.1.4.1.10734.3.3.2.1.2.0

The cumulative number ofpackets blocked by policy
actions.

policyPacketsBlocked64

1.3.6.1.4.1.10734.3.3.2.1.32.
0

The total number of 64-bit
packets blocked by policy
actions.

policyPacketsIncoming

1.3.6.1.4.1.10734.3.3.2.1.3.0

The total number of incoming
packets.

policyPacketsIncoming64

1.3.6.1.4.1.10734.3.3.2.1.33.
0

The total number of incoming
64-bit packets.

policyPacketsOutgoing

1.3.6.1.4.1.10734.3.3.2.1.4.0

The total number of outgoingpackets.

Object1-49

TPS MIBs Guide

ObjectOID

Description

policyPacketsOutgoing64

1.3.6.1.4.1.10734.3.3.2.1.34.
0

The total number of outgoing
64-bit packets.

policyPacketsInvalid

1.3.6.1.4.1.10734.3.3.2.1.6.0

The total number of packets
discarded because they wereinvalid.

policyPacketsInvalid64

1.3.6.1.4.1.10734.3.3.2.1.36.
0

The total number of 64-bit
packets discarded because
they were invalid.

policyPacketsPermitted

1.3.6.1.4.1.10734.3.3.2.1.7.0

The cumulative number ofpackets permitted because ofpolicy actions.

policyPacketsPermitted64

1.3.6.1.4.1.10734.3.3.2.1.37.
0

The cumulative number of 64bit packets permitted becauseof policy actions.

policyPacketsRateLimited64

1.3.6.1.4.1.10734.3.3.2.1.38.
0

The total number of 64-bit
packets discarded by ratelimiting filters.

policyPacketsTrusted64

1.3.6.1.4.1.10734.3.3.2.1.39.
0

The cumulative number of 64bit packets trusted because ofpolicy actions.

The following variable applies to Digital Vaccine (DV) statistics.
ObjectpolicyDVObjs

OID
1.3.6.1.4.1.10734.3.3.2.1.10.
1.0

Description
Sub-tree of Digital Vaccine
information.

The following table ranks the top ten policies according to hit count.
Object
topTenHitsByPolicyTable

1-50

OID

Description

1.3.6.1.4.1.10734.3.3.2.1.11

Table of the ten policies withthe largest number of hit
counts.

TPS MIBs Guide

ObjectOID

Description

topTenHitsByPolicyEntry

1.3.6.1.4.1.10734.3.3.2.1.11.1

An entry in the top ten
policies table.

topTenRank

1.3.6.1.4.1.10734.3.3.2.1.11.1.
1

The numerical ranking of thepolicy in the table. A rank of 1
indicates the policy has thelargest number of hits.

policyHitCount

1.3.6.1.4.1.10734.3.3.2.1.11.1.
2

The number of alerts
generated by the policy.

policyName

1.3.6.1.4.1.10734.3.3.2.1.11.1.
3

The policy name.

policyUUID

1.3.6.1.4.1.10734.3.3.2.1.11.1.
4

The global identifier of thepolicy.

The following variables apply to statistics of all policies at each protocol.
ObjectOID

Description

alertsByProtocolTable

1.3.6.1.4.1.10734.3.3.2.1.13

Table of alert counts of allpolicies at each protocol.

alertsByProtocolEntry

1.3.6.1.4.1.10734.3.3.2.1.13.
1

An entry in the alerts by
protocol table.

alertProtocol

1.3.6.1.4.1.10734.3.3.2.1.13.
1.1

Alerts of all policies at each
protocol.
• 1: ICMP• 2: UDP• 3: TCP• 4: other IP• 5: ARP• 6: other ETH• 7: ICMP v6• 8: other IPv6

1-51

TPS MIBs Guide

ObjectOID

Description

protocolAlertCount

1.3.6.1.4.1.10734.3.3.2.1.13.
1.2

The number of alerts
generated by all policies of agiven protocol.

packetsByProtocolTable

1.3.6.1.4.1.10734.3.3.2.1.20

Table of packet counts
received in each protocol.

packetsByProtocolEntry

1.3.6.1.4.1.10734.3.3.2.1.20.
1

An entry in the packets by
protocol table. Rows cannot
be added or deleted.

packetProtocol

1.3.6.1.4.1.10734.3.3.2.1.20.
1.1

The protocol of a policy.
• 1: ICMP• 2: UDP• 3: TCP• 4: other IP• 5: ARP• 6: other ETH• 7: ICMP v6• 8: other IPv6

protocolPacketCount

1.3.6.1.4.1.10734.3.3.2.1.20.
1.2

The count of packets received
for a given protocol.
• 1: ICMP• 2: UDP• 3: TCP• 4: other IP• 5: ARP• 6: other ETH• 7: ICMP v6• 8: other IPv6

1-52

TPS MIBs Guide

The following variables apply to information and statistics related to thesecurity zone port pair.
ObjectOID

Description

securityZonePairTable

1.3.6.1.4.1.10734.3.3.2.1.22

Table of information andstatistics for each virtual
segment.

securityZonePairEntry

1.3.6.1.4.1.10734.3.3.2.1.22.
1

An entry in the table.

szpName1.3.6.1.4.1.10734.3.3.2.1.22.
1.1

The name of a security zone
pair. Each of the 48 zone pairs
is identified by unique octet
strings.

szpInZoneName

1.3.6.1.4.1.10734.3.3.2.1.22.
1.2

The name of the input security
zone for each of the 48
security zone pairs.

szpOutZoneName

1.3.6.1.4.1.10734.3.3.2.1.22.
1.3

The name of the output
security zone for each of the
48 security zone pairs.

szpUUID

1.3.6.1.4.1.10734.3.3.2.1.22.
1.4

The UUID for each of the 48
security zone pairs.

szpInZoneUUID

1.3.6.1.4.1.10734.3.3.2.1.22.
1.5

The UUID of the input security
zone for each of the 48
security zone pairs.

szpOutZoneUUID

1.3.6.1.4.1.10734.3.3.2.1.22.
1.6

The UUID of the output
security zone for each of the
48 security zone pairs.

szpInPackets

1.3.6.1.4.1.10734.3.3.2.1.22.
1.7

The number of packets
received for each of the 48
security zone pairs.

szpInOctets

1.3.6.1.4.1.10734.3.3.2.1.22.
1.8

The number of bytes received
for each of the 48 security
zone pairs.

1-53

TPS MIBs Guide

ObjectOID

Description

szpAlerts

1.3.6.1.4.1.10734.3.3.2.1.22.
1.9

The number of alerts (blocks +permits) for each of the 48
security zone pairs.

szpBlocks

1.3.6.1.4.1.10734.3.3.2.1.22.
1.10

The number of blocks
generated for each of the 48
security zone pairs.

szpPermits

1.3.6.1.4.1.10734.3.3.2.1.22.
1.11

The number of permits
generated for each of the 48
security zone pairs.

szpPrecedence

1.3.6.1.4.1.10734.3.3.2.1.22.
1.12

The precedence for each of the
48 security zone pairs.

The following variables apply to statistics for each physical port.
ObjectOID

Description

portStatsTable

1.3.6.1.4.1.10734.3.3.2.1.23

Table of statistics for eachphysical port.

portStatsEntry

1.3.6.1.4.1.10734.3.3.2.1.23.
1

An entry in the port statistics
table. Rows cannot be added
or deleted.

portNumber

1.3.6.1.4.1.10734.3.3.2.1.23.
1.1

The numeric index of a port.
• 1: 0• 2: 1• 3: 2

portName

1.3.6.1.4.1.10734.3.3.2.1.23.
1.2

The name of a port.
• 1: 1A• 2: 1B• 3: 2A

portVlanTranslations

1-54

1.3.6.1.4.1.10734.3.3.2.1.23.
1.3

The number of packets leaving
this egress port whose VLAN
IDs were translated.

TPS MIBs Guide

TPT-PORT-CONFIG-MIB
Describes information about the device port configuration.
ObjectOID

Description

portConfigTable

1.3.6.1.4.1.10734.3.3.2.4.1

Table of ports on the device andtheir configuration settings. For
TPS devices, the loopback column
has no meaning and is set to 0.

portConfigEntry

1.3.6.1.4.1.10734.3.3.2.4.1.1

An entry in the ports table.

portConfigSlot

1.3.6.1.4.1.10734.3.3.2.4.1.1.1

The segment on which the port islocated.

portConfigPort

1.3.6.1.4.1.10734.3.3.2.4.1.1.2

The port number.

portConfigLineSpeed

1.3.6.1.4.1.10734.3.3.2.4.1.1.3

The line speed configuration:• 0: default• 1: 1GbE• 2: 100 Mb• 3: 10 Mb• 4: 10 GbE• 5: 40 GbE• 6: 25 GbE• 7: 100 GbE

portConfigDuplex

1.3.6.1.4.1.10734.3.3.2.4.1.1.4

The duplex configuration.
• 0: default• 1: half• 2: full

1-55

TPS MIBs Guide

ObjectportConfigAutoNeg

OID
1.3.6.1.4.1.10734.3.3.2.4.1.1.5

Description
The auto-negotiation
configuration.
• 0: default• 1: on• 2: off

portConfigShutdown

1.3.6.1.4.1.10734.3.3.2.4.1.1.6

The shutdown configuration.
• 0: disabled—The port cancome up normally.
• 1: enabled—The port is either
manually removed fromservice or link-down
synchronization takes it out ofservice.

portConfigLoopback

1.3.6.1.4.1.10734.3.3.2.4.1.1.7

The loopback configuration.
Because loopback is unsupported,
it is always set to 0 (disabled).

portConfigFailover

1.3.6.1.4.1.10734.3.3.2.4.1.1.8

The failover action configuration:• 0: block• 1: permit

portConfigLDSMode1.3.6.1.4.1.10734.3.3.2.4.1.1.9

The link-down synchronizationmode.
• 0: hub• 1: breaker• 2: write

portConfigLDSTimeout

1.3.6.1.4.1.10734.3.3.2.4.1.1.1
0

The link-down synchronization
timeout configuration.

TPT-RESOURCE-MIB
Describes filesystem, CPU, memory, temperature, power supply, and fan
information for the device.

1-56

TPS MIBs Guide

Notifications
The following notifications send information to the management system
about the system resources.
ObjectOID

Description

tptResourceNotify

1.3.6.1.4.1.10734.3.3.3.0.1
4Sub-tree of notifications thatindicate when a resource
parameter has crossed apredefined threshold.

tptResourceNotifyDeviceID

1.3.6.1.4.1.10734.3.3.3.1.6
1

The unique identifier of thedevice sending thenotification.

tptResourceNotifyIdentifier

1.3.6.1.4.1.10734.3.3.3.1.6
2

The type of resource thattriggered the notification.(1)• 1: filesystem• 2: CPU• 3: memory• 4: chassis temperature• 5: fan• 6: power supply

tptResourceNotifyFSIndex

1.3.6.1.4.1.10734.3.3.3.1.6
3

For a filesystem resource, thevalue is the resource
filesystem's table index(resourceFSIndex) thatgenerated the notification.
Otherwise, the value is 0
(zero).

tptResourceNotifyCurrentValue

1.3.6.1.4.1.10734.3.3.3.1.6
4

The current value of theresource that triggered thisnotification.

(1) This object is deprecated. For the current object, see tptResourceNotifyHWIdentifierin the last row of the table.

1-57

TPS MIBs Guide

1-58

ObjectOID

Description

tptResourceNotifyThresholdMaj

1.3.6.1.4.1.10734.3.3.3.1.6
5

The major threshold of thisresource (between green andyellow states).

tptResourceNotifyThresholdCrit1.3.6.1.4.1.10734.3.3.3.1.6
6

The critical threshold of thisresource (between yellow
and red states).

tptResourceNotifyRangeMin

1.3.6.1.4.1.10734.3.3.3.1.6
7

The minimum end of therange of values that thisresource can take.

tptResourceNotifyRangeMax

1.3.6.1.4.1.10734.3.3.3.1.6
8

The maximum end of therange of values that thisresource can take.

tptResourceNotifyStateBefore

1.3.6.1.4.1.10734.3.3.3.1.6
9The state of the resource
before the current threshold
transition.

tptResourceNotifyStateAfter

1.3.6.1.4.1.10734.3.3.3.1.7
0

The state of this resource
after the current threshold
transition.

tptResourceNotifyTimeStamp

1.3.6.1.4.1.10734.3.3.3.1.7
1

The timestamp of the eventthat generated thenotification, in seconds since
January 1, 1970.

tptResourceNotifySubIdentifier

1.3.6.1.4.1.10734.3.3.3.1.7
2

Sub-Identifier of the instanceof the resource that triggers
this notification. It is not usedin 5100N devices or earlier;
for these models, the value is
0 (zero).

TPS MIBs Guide

ObjectOID

tptResourceNotifyHWIdentifier

1.3.6.1.4.1.10734.3.3.3.1.7
3

Description
The type of resource thattriggered the notification.
• 0: sal• 1: CPU• 2: memory• 3: filesystem• 5: fan• 6: chassis temperature• 7: voltage• 10: power supply• 11: high availability• 12: audit log

File system
The following objects provide information about the device file systemobjects:
ObjectOID

Description

resourceNumberOfFilesystems

1.3.6.1.4.1.10734.3.3.2.5.1

Number of filesystems on thedevice’s hard disk

resourceFSTable

1.3.6.1.4.1.10734.3.3.2.5.2

Table of filesystem resource
information

resourceFSEntry

1.3.6.1.4.1.10734.3.3.2.5.2.1

An entry in the resource
filesystem table. Rows cannot
be added or deleted.

resourceFSInUseMB

1.3.6.1.4.1.10734.3.3.2.5.2.1.
1

Number of MB in use for thefilesystem

resourceFSThresholdMaj

1.3.6.1.4.1.10734.3.3.2.5.2.1.
2

Major threshold for the percent
of MB in use for the filesystem

1-59

TPS MIBs Guide

ObjectOID

Description

resourceFSThresholdCrit1.3.6.1.4.1.10734.3.3.2.5.2.1.
3

Critical threshold for thepercent of MB in use for thefilesystem

resourceFSRangeMin

1.3.6.1.4.1.10734.3.3.2.5.2.1.
4

Minimum value of the range of
MB in use, usually 0 (zero)

resourceFSRangeMax

1.3.6.1.4.1.10734.3.3.2.5.2.1.
5

Total size in MB of thefilesystem

resourceFSName

1.3.6.1.4.1.10734.3.3.2.5.2.1.
6

Name of this filesystem

resourceFSIndex

1.3.6.1.4.1.10734.3.3.2.5.2.1.
7Unique identifier for a given filesystem entry in the table

MemoryThe following table provides information about the device memory usage
objects:
OID

Description

resourceHPMemoryObjs

1.3.6.1.4.1.10734.3.3.2.5.3

Sub-tree of host processor
memory information

resourceHPMemoryInUsePercent

1.3.6.1.4.1.10734.3.3.2.5.3.1

Percentage of host processor
memory in use

resourceHPMemoryThresholdMaj

1.3.6.1.4.1.10734.3.3.2.5.3.2

Major threshold value forhost processor memory
usage

resourceHPMemoryThresholdC
rit

1.3.6.1.4.1.10734.3.3.2.5.3.3

Critical threshold value forhost processor memory
usage

resourceHPMemoryRangeMin

1.3.6.1.4.1.10734.3.3.2.5.3.4

Minimum percentage of hostprocessor memory usage,
usually 0 (zero)

Object1-60

TPS MIBs Guide

ObjectOID

Description

resourceHPMemoryRangeMax

1.3.6.1.4.1.10734.3.3.2.5.3.5

Maximum percentage of hostprocessor memory usage,
usually 100

resourceHPMemoryTotal

1.3.6.1.4.1.10734.3.3.2.5.3.6

Total size in megabytes ofhost processor memory

CPU
The following table provides information about CPU usage objects:
ObjectOID

Description

resourceHPCPUObjs

1.3.6.1.4.1.10734.3.3.2.5.4

Sub-tree of host processor
CPU information

resourceHPCPUBusyPercent

1.3.6.1.4.1.10734.3.3.2.5.4.1

Percentage of host processor
CPU that is currently busy

resourceHPCPUThresholdMaj

1.3.6.1.4.1.10734.3.3.2.5.4.2

Major threshold value forhost processor CPU activity

resourceHPCPUThresholdCrit1.3.6.1.4.1.10734.3.3.2.5.4.3

Critical threshold value ofhost processor CPU activity

resourceHPCPURangeMin

1.3.6.1.4.1.10734.3.3.2.5.4.4

Minimum percentage of hostprocessor CPU activity,
usually 0 (zero)

resourceHPCPURangeMax

1.3.6.1.4.1.10734.3.3.2.5.4.5

Maximum percentage of hostprocessor CPU activity,
usually 100

resourceNPCPUBusyPercentA

1.3.6.1.4.1.10734.3.3.2.5.4.6

Total Utilization of XLR A

resourceNPCPUBusyPercentTie
r2A

1.3.6.1.4.1.10734.3.3.2.5.4.7

F Thread Utilization of XLR A

resourceNPCPUBusyPercentTie
r3A

1.3.6.1.4.1.10734.3.3.2.5.4.8

KS Thread Utilization of XLR
A

1-61

TPS MIBs Guide

ObjectOID

Description

resourceNPCPUBusyPercentTie
r4A

1.3.6.1.4.1.10734.3.3.2.5.4.9

L Thread Utilization of XLR A

resourceNPCPUBusyPercentB

1.3.6.1.4.1.10734.3.3.2.5.4.10

Total Utilization of XLR B

resourceNPCPUBusyPercentTie
r2B

1.3.6.1.4.1.10734.3.3.2.5.4.11

F Thread Utilization of XLR B

resourceNPCPUBusyPercentTie
r3B

1.3.6.1.4.1.10734.3.3.2.5.4.12

KS Thread Utilization of XLR
BresourceNPCPUBusyPercentTie
r4B

1.3.6.1.4.1.10734.3.3.2.5.4.13

L Thread Utilization of XLR B

resourceNPCPUBusyPercentC

1.3.6.1.4.1.10734.3.3.2.5.4.14

Total Utilization of XLR C

resourceNPCPUBusyPercent2C

1.3.6.1.4.1.10734.3.3.2.5.4.15

F Thread Utilization of XLR C

resourceNPCPUBusyPercent3C

1.3.6.1.4.1.10734.3.3.2.5.4.16

KS Thread Utilization of XLR
CresourceNPCPUBusyPercent4C

1.3.6.1.4.1.10734.3.3.2.5.4.17

L Thread Utilization of XLR C

Chassis temperature
The following table provide information about the chassis temperature
objects:
OID

Description

resourceChassisTempObjs

1.3.6.1.4.1.10734.3.3.2.5.5

Sub-tree of chassis
temperature information

resourceChassisTempDegreesC

1.3.6.1.4.1.10734.3.3.2.5.5.1

Chassis temperature

resourceChassisTempThresholdMaj

1.3.6.1.4.1.10734.3.3.2.5.5.2

Major threshold value forchassis temperature

resourceChassisTempThresholdC
rit

1.3.6.1.4.1.10734.3.3.2.5.5.3

Critical threshold value ofchassis temperature

Object1-62

TPS MIBs Guide

ObjectOID

Description

resourceChassisTempRangeMin

1.3.6.1.4.1.10734.3.3.2.5.5.4

Minimum value of thechassis temperature range

resourceChassisTempRangeMax

1.3.6.1.4.1.10734.3.3.2.5.5.5

Maximum value of thechassis temperature range

Important
All values are in degrees Centigrade.

Power supply
The following table provides information about the power supply objects:
ObjectOID

Description

resourcePowerSupplyObjs

1.3.6.1.4.1.10734.3.3.2.5.9

Sub-tree of power supply
information

resourcePowerSupplyQuantity

1.3.6.1.4.1.10734.3.3.2.5.9.2

Number of power supplies

resourcePowerSupplyMonitoring

1.3.6.1.4.1.10734.3.3.2.5.9.3

Indicates if power supply
monitoring is enabled:• 0: disabled• 1: enabledresourcePowerSupplyTable

1.3.6.1.4.1.10734.3.3.2.5.9.4

Table of power supplies on
the device. The number of
entries depends on thevalue of theresourcePowerSupplyQuan
tity object. The maximum
number of entries depends
on the implementation.

resourcePowerSupplyEntry

1.3.6.1.4.1.10734.3.3.2.5.9.4.1

An entry in the power
supply table. Rows cannot
be created or deleted.

1-63

TPS MIBs Guide

ObjectOID

Description

powerSupplyUnitIndex

1.3.6.1.4.1.10734.3.3.2.5.9.4.1.
1

Index of the power supply
units on a device. The firstentry is 1.

powerSupplyStatus

1.3.6.1.4.1.10734.3.3.2.5.9.4.1.
2

If the device has dual power
supplies and power supply
monitoring is enabled, thisvalue indicates whether
one or both power supplies
is functional:• 1: red—critical• 2: green—normal

System information
The following table provides information about the system objects:
OID

Description

resourceDateTime

1.3.6.1.4.1.10734.3.3.2.5.10

Current date and time ofdevice in seconds since
January 1, 1970. There is notime zone offset.

resourceSnmpRunState

1.3.6.1.4.1.10734.3.3.2.5.11

Indicates which SNMP
versions are running:

Object• 0: none• 1: SNMP v2• 2: SNMP v3• 3: Both v2 and v3

1-64

TPS MIBs Guide

ObjectresourceSnmpConfig

OID
1.3.6.1.4.1.10734.3.3.2.5.12

Description
Indicates which SNMP
versions are configured:• 0: none• 1: SNMP v2• 2: SNMP v3• 3: Both v2 and v3

resourceRemoteAuthEnabled

1.3.6.1.4.1.10734.3.3.2.5.13

Indicates whether remoteauthentication is enabledresourceRemoteAuthTimeout

1.3.6.1.4.1.10734.3.3.2.5.14

The remote authentication
timeout in seconds

TPT-SFLOW
Provides sFlow status and collector information. The sFlow statistics are sentfrom the collector to the device.
sFlow collectors
ObjectOID

Description

sFlowCollectorTable

1.3.6.1.4.1.10734.3.3.2.18.1

Table of sFlow collectors. Up
to two collectors aresupported.

sFlowCollectorEntry

1.3.6.1.4.1.10734.3.3.2.18.1.1

A collector address and port
in the sFlowCollectorTable.
Rows cannot be created ordeleted.

collectorIndex

1.3.6.1.4.1.10734.3.3.2.18.1.1.
1Index into the sFlow collector
table, starting with 1.

collectorAddr

1.3.6.1.4.1.10734.3.3.2.18.1.1.
2

The IPv4 address of thecollector. If the address is not
set, the value will be an
empty string.

1-65

TPS MIBs Guide

ObjectOID

Description

udpPort1.3.6.1.4.1.10734.3.3.2.18.1.1.
3

The UDP port of the collector.

collectorAddrV6

1.3.6.1.4.1.10734.3.3.2.18.1.1.
4

The IPv6 address of thecollector. If the address is not
set, the value will be an
empty string.

OID

Description

1.3.6.1.4.1.10734.3.3.2.18.2

sFlow status for the device:sFlow status
ObjectsFlowStatus• 0: disabled• 1: enabled• 2: error• 3: not applicable

TPT-SMSMIBSDefines interactions between the SMS and the customer’s NMS.
SMS top level MIBs
Object

1-66

OID

Description

tpt-sms-conf

1.3.6.1.4.1.10734.3.4.1

SMS conformance objects
subtree.

tpt-sms-objs

1.3.6.1.4.1.10734.3.4.2

SMS managed objects subtree.

tpt-sms-events

1.3.6.1.4.1.10734.3.4.3

SMS events sub-tree that
includes all payload variables
needed for notifications.

TPS MIBs Guide

SMS conformance top-level MIBs
ObjectOID

Description

tpt-sms-groups

1.3.6.1.4.1.10734.3.4.1.1

SMS groups sub-tree.

tpt-sms-compls

1.3.6.1.4.1.10734.3.4.1.2

SMS compliance MIBs subtree.

SMS notification top-level MIBs
ObjectOID

Description

tpt-sms-eventsV2

1.3.6.1.4.1.10734.3.4.3.0

SMS events notification MIBs.

tpt-sms-notifypayload

1.3.6.1.4.1.10734.3.4.3.1

SMS MIB variables sent as
part of a notification payload.

Model number objects
Objecttpt-sms-familyOID
1.3.6.1.4.1.10734.1.4

Description
Registration for the SMS.

TPT-SMS-TRAP-MIB
Describes the notifications sent to and from an SMS device.
SMS Notification MIBs
ObjectOID

Description

tptSmsQuarantineRequest

1.3.6.1.4.1.10734.3.4.3.0.1

The SMS asks an external
NMS to quarantine an
endstation using the data
embedded in the request.

tptSmsQuarantineAck

1.3.6.1.4.1.10734.3.4.3.0.2

The external NMS notifies the
SMS that a quarantine
request was processed.

1-67

TPS MIBs Guide

Object

1-68

OID

Description

tptSmsQuarantineReleaseRe
quest

1.3.6.1.4.1.10734.3.4.3.0.3

The SMS asks an external
NMS to unquarantine an
endstation using the data
embedded in the request.

tptSmsQuarantineReleaseAck

1.3.6.1.4.1.10734.3.4.3.0.4

The external NMS notifies the
SMS that an unquarantine
request was processed.

tptSmsQuarantinePolicyNotif
ication

1.3.6.1.4.1.10734.3.4.3.0.5

The SMS sends notification ofa policy match.

tptSmsUnQuarantineRequest

1.3.6.1.4.1.10734.3.4.3.0.6

Commands the SMS tounquarantine an endstation.

tptSmsQuarantineCommand

1.3.6.1.4.1.10734.3.4.3.0.14

Commands the SMS toquarantine an endstation.

tptSmsBoot

1.3.6.1.4.1.10734.3.4.3.0.7

Indicates that the SMS hasbooted.

tptSmsReboot

1.3.6.1.4.1.10734.3.4.3.0.8

Indicates that the SMS isrebooting.

tptSmsShuttingDown

1.3.6.1.4.1.10734.3.4.3.0.9

Indicates that the system isshutting down.

tptSmsReady

1.3.6.1.4.1.10734.3.4.3.0.10

Indicates that the system isready.

tptSmsAuthenticationError

1.3.6.1.4.1.10734.3.4.3.0.11

Indicates that anauthentication error has
occurred.

tptSmsEgpNeighborDownstate1.3.6.1.4.1.10734.3.4.3.0.12

Indicates that the EGP
neighbor is going todownstate.

tptSmsSystemRestart

1.3.6.1.4.1.10734.3.4.3.0.13

Indicates that the server
process has restarted.

TPS MIBs Guide

ObjectOID

Description

tptSmsRepDvVerifySuccess1.3.6.1.4.1.10734.3.4.3.0.15

Indicates that the Reputation
DV was downloaded andverified.

tptSmsRepDvVerifyFail

1.3.6.1.4.1.10734.3.4.3.0.16

Indicates that the Reputation
DV downloaded but thatverification failed.

tptSmsTest

1.3.6.1.4.1.10734.3.4.3.0.17

SMS test trap.

tptSmsRebootingDevice

1.3.6.1.4.1.10734.3.4.3.0.18

Indicates that the SMS isrebooting a device.

tptDeviceNonComm

1.3.6.1.4.1.10734.3.4.3.0.19

Indicates that the SMS lost
communication with adevice.

tptDeviceBooted

1.3.6.1.4.1.10734.3.4.3.0.20

Indicates that a device was
rebooted.

OID

Description

SMS MIB Variables
ObjecttptSmsQuarantineNotifyId

1.3.6.1.4.1.10734.3.4.3.1.1

A unique incrementing
integer assigned to eachquarantine event.

tptSmsQuarantineNotifyData

1.3.6.1.4.1.10734.3.4.3.1.2

A string that identifies thedevice to be quarantined. The
format is NAME:VALUE.
Multiple parameters are
separated by a new line.

tptSmsQuarantinePolicyMatc
hData

1.3.6.1.4.1.10734.3.4.3.1.3

A string that identifies thematching policy.

tptSmsQuarantineNotifyType

1.3.6.1.4.1.10734.3.4.3.1.4

A string that identifies thetype of quarantine.

tptSmsQuarantineDeviceIP

1.3.6.1.4.1.10734.3.4.3.1.5

The IP address used as a trap
parameter.

1-69

TPS MIBs Guide

Object

1-70

OID

Description

tptSmsQuarantineDeviceMAC

1.3.6.1.4.1.10734.3.4.3.1.6

The MAC address used as a
trap parameter.

tptSmsQuarantineSwitchPort

1.3.6.1.4.1.10734.3.4.3.1.7

The port number or index
used as a trap parameter.

tptSmsQuarantineEndpointU
ser

1.3.6.1.4.1.10734.3.4.3.1.8

A string that identifies thequarantined endpoint user.

tptSmsQuarantineNotifyActio
nList

1.3.6.1.4.1.10734.3.4.3.1.9

A string that identifies thematching policy.

tptSmsQuarantineNotifyPara
mList

1.3.6.1.4.1.10734.3.4.3.1.10

A string that identifies thematching policy.

tptSmsQuarantineNotifyOpti
onList1.3.6.1.4.1.10734.3.4.3.1.11

A string that identifies thematching policy.

tptSmsQuarantinePolicyName

1.3.6.1.4.1.10734.3.4.3.1.12

The name of an SMS
quarantine policy.

tptSmsRepDvVersion

1.3.6.1.4.1.10734.3.4.3.1.13

The Reputation DV version.

tptSmsMessage

1.3.6.1.4.1.10734.3.4.3.1.14

A generic message parameter.

tptSmsQuarantineDataGroup

1.3.6.1.4.1.10734.3.4.1.1.1

Payload of SMS quarantine
traps consisting of a unique
identifier and a parseable
string.

tptSmsQuarantineNotifyGroup1.3.6.1.4.1.10734.3.4.1.1.2

SMS quarantine traps sent to
an NMS to indicate devices
that require a quarantine
operation.

tptSmsQuarantineNotifyAckG
roup

1.3.6.1.4.1.10734.3.4.1.1.3

SMS quarantine traps sent toan SMS system to indicate
devices that have beenquarantined.

TPS MIBs Guide

ObjectOID

tptSmsQuarantineRequestGr
oup

Description

1.3.6.1.4.1.10734.3.4.1.1.4

SMS quarantine traps
received to indicate devices
that require a (un)quarantine
operation.

TPT-TPA-HARDWARE-MIB
Describes the device hardware and its components, including ports, chassis,
fans, and power supplies.
The following table describes the hardware objects:
ObjectOID

Description

hw-numFans

1.3.6.1.4.1.10734.3.3.2.3.7

Number of fan subunits on thedevicehw-numPowerSupplies

1.3.6.1.4.1.10734.3.3.2.3.8

Number of power supply subunits
on the device

hw-numPEMs

1.3.6.1.4.1.10734.3.3.2.3.9

Number of power entry module
subunits on the device

hw-certificateNumber

1.3.6.1.4.1.10734.3.3.2.3.10

Hardware certificate number of thedevicehw-serialNumber

1.3.6.1.4.1.10734.3.3.2.3.11

Hardware serial number of thedeviceFans
The following table provides information about the fan hardware objects:
ObjectOID

Description

hw-fanTable

1.3.6.1.4.1.10734.3.3.2.3.3

Table of fan data for the device.
Represented as a table with one
row.

hw-fanEntry

1.3.6.1.4.1.10734.3.3.2.3.3.1

An entry in the fan table.

1-71

TPS MIBs Guide

ObjectOID

Description

fanSubunit

1.3.6.1.4.1.10734.3.3.2.3.3.1.1

The number for this entry in the
fan table. The controller is always
0 (zero).

fanType

1.3.6.1.4.1.10734.3.3.2.3.3.1.3

Type of hardware element:• 0: unequipped• 19: fan controller• 20: fan subunit

fanCfgType

1.3.6.1.4.1.10734.3.3.2.3.3.1.4

Fan configuration:• 0: unconfigured• 1: simplex• 2: duplex• 3: load share• 4: autonomous

fanRunState

1.3.6.1.4.1.10734.3.3.2.3.3.1.5

High-level hardware state of thefan:• 0: out of service• 1: initializing• 2: active• 3: standby• 4: diagnostic• 5: loopback• 6: active-FAF• 7: standby-FAF• 8: active - degraded• 9: standby - degraded

1-72

TPS MIBs Guide

ObjectfanQualifier1

OID
1.3.6.1.4.1.10734.3.3.2.3.3.1.6

Description
Further qualification/detail on thehigh-level hardware state:• 1: degraded• 13: yellow alarm• 14: red alarm

fanQualifier2

1.3.6.1.4.1.10734.3.3.2.3.3.1.7

Further qualification/detail on thehigh-level hardware state:• 1: degraded• 13: yellow alarm• 14: red alarm

fanQualifier3

1.3.6.1.4.1.10734.3.3.2.3.3.1.8

Further qualification/detail on thehigh-level hardware state:• 1: degraded• 13: yellow alarm• 14: red alarm

fanQualifier4

1.3.6.1.4.1.10734.3.3.2.3.3.1.9

Further qualification/detail on thehigh-level hardware state:• 1: degraded• 13: yellow alarm• 14: red alarm

fanStartTime

1.3.6.1.4.1.10734.3.3.2.3.3.1.10

Time at which the fan was
powered up

fanVendorID

1.3.6.1.4.1.10734.3.3.2.3.3.1.11

Identifying number of the fanvendorfanDeviceID

1.3.6.1.4.1.10734.3.3.2.3.3.1.12

An identifying number specific to
the fanfanProductID

1.3.6.1.4.1.10734.3.3.2.3.3.1.13

Versions and other inventory
information

1-73

TPS MIBs Guide

ObjectfanFPGAVersion

OID
1.3.6.1.4.1.10734.3.3.2.3.3.1.14

Description
Version of the TippingPoint FPGA
chip on the fan

For fan health, see Fans on page 1-13.

Power supply
The following table provides information about the power supply hardware
objects:
ObjectOID

Description

hw-psTable

1.3.6.1.4.1.10734.3.3.2.3.4

Table of power supply data forthe device. Represented as atable with one row.

hw-psEntry

1.3.6.1.4.1.10734.3.3.2.3.4.1

Entry in the power supply table

psSubunit

1.3.6.1.4.1.10734.3.3.2.3.4.1.1

The number for this entry in the
power supply table. This
number is always 0 (zero).

psType1.3.6.1.4.1.10734.3.3.2.3.4.1.3

Type of hardware element:• 0: unequipped• 17: power supply• 18: power supply sub-unit

psCfgType1.3.6.1.4.1.10734.3.3.2.3.4.1.4

Power supply configuration:• 0: unconfigured• 1: simplex• 2: duplex• 3: load share• 4: autonomous

1-74

TPS MIBs Guide

ObjectpsRunState

OID

Description

1.3.6.1.4.1.10734.3.3.2.3.4.1.5

High-level hardware state of thepower supply:• 0: out of service• 1: initializing• 2: active• 3: standby• 4: diagnostic• 5: loopback• 6: active-FAF• 7: standby-FAF• 8: active - degraded• 9: standby - degraded

psQualifier1

1.3.6.1.4.1.10734.3.3.2.3.4.1.6

Further qualification/detail on
the high-level hardware state.
• 1: degraded• 13: yellow alarm• 14: red alarm

psQualifier2

1.3.6.1.4.1.10734.3.3.2.3.4.1.7

Further qualification/detail on
the high-level hardware state.
• 1: degraded• 13: yellow alarm• 14: red alarm

psQualifier3

1.3.6.1.4.1.10734.3.3.2.3.4.1.8

Further qualification/detail on
the high-level hardware state.
• 1: degraded• 13: yellow alarm• 14: red alarm

1-75

TPS MIBs Guide

ObjectpsQualifier4

OID

Description

1.3.6.1.4.1.10734.3.3.2.3.4.1.9

Further qualification/detail on
the high-level hardware state.
• 1: degraded• 13: yellow alarm• 14: red alarm

psStartTime

1.3.6.1.4.1.10734.3.3.2.3.4.1.10

Time at which the power
supply was powered up

psVendorID

1.3.6.1.4.1.10734.3.3.2.3.4.1.11

Identifying number of thepower supply vendor

psDeviceID

1.3.6.1.4.1.10734.3.3.2.3.4.1.12

Identifying number specific to
the power supply

psProductID

1.3.6.1.4.1.10734.3.3.2.3.4.1.13

Versions and other inventory
information

psFPGAVersion

1.3.6.1.4.1.10734.3.3.2.3.4.1.14

Version of the TippingPointFPGA chip on the power supply

TPT-TRAFFICThe TPT-TRAFFIC MIB defines traffic rate-limiting information.
Note
The MIB file includes traffic threshold information.

Rate limiter
The following objects provide rate-limit statistics.
ObjectrateLimitTable

1-76

OID
1.3.6.1.4.1.10734.3.3.2.8.1

Description
A table providing data about
a rate-limit action set.

TPS MIBs Guide

ObjectOID

Description

rateLimitEntry

1.3.6.1.4.1.10734.3.3.2.8.1.1

An entry in the rate-limit
table. Rows cannot be added
or deleted.

rateLimitGlobalID

1.3.6.1.4.1.10734.3.3.2.8.1.1.1

The global ID of a rate-limit
action set.

rateLimitRequestedRate

1.3.6.1.4.1.10734.3.3.2.8.1.1.2

The bit rate in Kbps definedby the action set creator.

rateLimitActualRate

1.3.6.1.4.1.10734.3.3.2.8.1.1.3

The bit rate in Kbps definedat the hardware level.

rateLimitPacketsSent

1.3.6.1.4.1.10734.3.3.2.8.1.1.4

The number of packets sent
via this action set since thetable was last cleared.

rateLimitPacketsDropped

1.3.6.1.4.1.10734.3.3.2.8.1.1.5

The number of packets
dropped by this action set
since the table was lastcleared.

rateLimitPacketsQueued

1.3.6.1.4.1.10734.3.3.2.8.1.1.6

The number of packets
queued and ready to be sent
via this action set.

rateLimitHistNumSeconds

1.3.6.1.4.1.10734.3.3.2.8.1.1.7

The number of seconds ofvalid historical sample data
available.

rateLimitHistNumMinutes

1.3.6.1.4.1.10734.3.3.2.8.1.1.8

The number of minutes ofvalid historical sample data
available.

rateLimitHistNumHours

1.3.6.1.4.1.10734.3.3.2.8.1.1.9

The number of hours of valid
historical sample data
available.

Rate limit historical seconds
The following objects provide rate-limit statistics as recorded every second
for a minute.

1-77

TPS MIBs Guide

ObjectOID

Description

rateLimitHistSecondsTable

1.3.6.1.4.1.10734.3.3.2.8.2

Historical sample data as
recorded every second for aminute.

rateLimitHistSecondsEntry

1.3.6.1.4.1.10734.3.3.2.8.2.1

An entry in the rate-limit
history seconds table.

rateLimitHistSecondsGlobalID

1.3.6.1.4.1.10734.3.3.2.8.2.1.1

The global ID of a rate-limit
action set.

rateLimitHistSecondsIndex

1.3.6.1.4.1.10734.3.3.2.8.2.1.2

The index (0–59) of a second.

rateLimitHistSecondsBytesSe
nt

1.3.6.1.4.1.10734.3.3.2.8.2.1.3

The number of bytes sent in
the specified second.

rateLimitHistSecondsTimesta
mp1.3.6.1.4.1.10734.3.3.2.8.2.1.4

The time that this statistic
was updated, measured inseconds since January 1,
1970.

Rate limit historical minutes
The following objects provide rate-limit statistics as recorded every minutefor an hour.
Object

1-78

OID

Description

rateLimitHistMinutesTable

1.3.6.1.4.1.10734.3.3.2.8.3

Historical sample data as
recorded every minute for an
hour.

rateLimitHistMinutesEntry

1.3.6.1.4.1.10734.3.3.2.8.3.1

An entry in the rate-limit
history minutes table.

rateLimitHistMinutesGlobalID

1.3.6.1.4.1.10734.3.3.2.8.3.1.1

The global ID of a rate-limit
action set.

rateLimitHistMinutesIndex

1.3.6.1.4.1.10734.3.3.2.8.3.1.2

The index (0–59) of a minute.

rateLimitHistMinutesBytesSe
nt

1.3.6.1.4.1.10734.3.3.2.8.3.1.3

The number of bytes sent in
the specified minute.

TPS MIBs Guide

ObjectOID

rateLimitHistMinutesTimesta
mp1.3.6.1.4.1.10734.3.3.2.8.3.1.4

Description
The time that this statistic
was updated, measured inseconds since January 1,
1970.

Rate limit historical hours
The following objects provide rate-limit statistics as recorded every hour fora day.
ObjectOID

Description

rateLimitHistHoursTable

1.3.6.1.4.1.10734.3.3.2.8.4

Historical sample data as
recorded every hour for a day.

rateLimitHistHoursEntry

1.3.6.1.4.1.10734.3.3.2.8.4.1

An entry in the rate-limit
history hours table.

rateLimitHistHoursGlobalID

1.3.6.1.4.1.10734.3.3.2.8.4.1.1

The global ID of a rate limit
action set.

rateLimitHistHoursIndex

1.3.6.1.4.1.10734.3.3.2.8.4.1.2

The index (0–23) of an hour.

rateLimitHistHoursBytesSent

1.3.6.1.4.1.10734.3.3.2.8.4.1.3

The number of bytes sent in
the specified hour.

rateLimitHistHoursTimestamp

1.3.6.1.4.1.10734.3.3.2.8.4.1.4

The time that this statistic
was updated, measured inseconds since January 1,
1970.

TPT-TPAMIBS-MIB
Describes definitions for TPT device models. This section indicates the
addition of the Threat Protection System (TPS) models to the table. For
registration identifiers of other TPT models, refer to the MIBs Guide for those
products.
The following table identifies the TPS models:

1-79

TPS MIBs Guide

ObjectOID

Description

tpt-model-440T-IPS

1.3.6.1.4.1.10734.1.3.47

Registration for the 440T ThreatProtection System.

tpt-model-2200T-IPS

1.3.6.1.4.1.10734.1.3.48

Registration for the 2200T ThreatProtection System.

tpt-model-VTPS-Trial-IPS

1.3.6.1.4.1.10734.1.3.49

Registration for the TippingPointvTPS Standard Trial ThreatProtection System.

tpt-model-VTPSStandard-IPS

1.3.6.1.4.1.10734.1.3.50

Registration for the TippingPointvTPS Standard Threat Protection
System.

tpt-model-8200TX-IPS

1.3.6.1.4.1.10734.1.3.51

Registration for the 8200TX ThreatProtection System.

tpt-model-8400TX-IPS

1.3.6.1.4.1.10734.1.3.52

Registration for the 8400TX ThreatProtection System.

tpt-model-VTPS-CLOUD

1.3.6.1.4.1.10734.1.3.53

Registration for the TippingPoint
Cloud Threat Protection System.

tpt-model-1100TX-IPS

1.3.6.1.4.1.10734.1.3.54

Registration for the TippingPoint
1100TX Threat Protection System.

tpt-model 5500TX-IPS

1.3.6.1.4.1.10734.1.3.55

Registration for the TippingPoint
5500TX Threat Protection System.

tpt-model-8600TXE-IPS

1.3.6.1.4.1.10734.1.3.58

Registration for the 8600TXE ThreatProtection System.

tpt-model-9200TXE-IPS

1.3.6.1.4.1.10734.1.3.56

Registration for the TippingPoint
9200TXE Threat Protection System.

TPT-TSEDefines TSE settings, including adaptive filtering.

1-80

TPS MIBs Guide

Adaptive filter configuration
The following table lists the top ten filters in the Adaptive Filter
Configuration list.
ObjectOID

Description

topTenAdaptFilterTable

1.3.6.1.4.1.10734.3.3.2.7.1

Adaptive filter configuration
top ten list.

topTenAdaptFilterEntry

1.3.6.1.4.1.10734.3.3.2.7.1.1

An entry in the adaptive filter
configuration top ten list.
Rows cannot be added ordeleted.

topTenAdaptFilterRank

1.3.6.1.4.1.10734.3.3.2.7.1.1.1

The numerical ranking of afilter in the adaptive filter top
ten list.

adaptFilterName

1.3.6.1.4.1.10734.3.3.2.7.1.1.2

The name of the filter.

adaptFilterUUID

1.3.6.1.4.1.10734.3.3.2.7.1.1.3

The global identifier of thefilter.

adaptFilterSegment

1.3.6.1.4.1.10734.3.3.2.7.1.1.4

The segment to which thefilter applies.

adaptFilterEnabledState

1.3.6.1.4.1.10734.3.3.2.7.1.1.5

The state of the filter.

adaptFilterSigID

1.3.6.1.4.1.10734.3.3.2.7.1.1.7

The global identifier of asignature.

adaptFilterProfile

1.3.6.1.4.1.10734.3.3.2.7.1.1.8

The name of the profile
associated with the filter.

Connection blocks table
The following table lists all connection blocks.
ObjectconnectionBlockTable

OID
1.3.6.1.4.1.10734.3.3.2.7.2

Description
Table of connections that
correspond to blocked
streams.

1-81

TPS MIBs Guide

ObjectOID

Description

connectionBlockEntry

1.3.6.1.4.1.10734.3.3.2.7.2.1

An entry in the connection
block table. Rows cannot be
added or deleted.

connectionBlockIndex

1.3.6.1.4.1.10734.3.3.2.7.2.1.1

The index number of theentry in the connection block
table.

connectionBlockSrcAddr

1.3.6.1.4.1.10734.3.3.2.7.2.1.2

The source IPv4 address of a
blocked connection.

connectionBlockSrcPort

1.3.6.1.4.1.10734.3.3.2.7.2.1.3

The source port of a blocked
connection.

connectionBlockDestAddr

1.3.6.1.4.1.10734.3.3.2.7.2.1.4

The destination IPv4 addressof a blocked connection.

connectionBlockDestPort

1.3.6.1.4.1.10734.3.3.2.7.2.1.5

The destination port of a
blocked connection.

connectionBlockProtocol

1.3.6.1.4.1.10734.3.3.2.7.2.1.6

The transmission protocol ofa blocked connection.
• 1: ICMP• 2: UDP• 3: TCP• 4: other IP• 5: ARP• 6: other ETH• 7: ICMP v6• 8: other IPV6

1-82

connectionBlockPort

1.3.6.1.4.1.10734.3.3.2.7.2.1.7

The segment on which theincoming data caused theconnection to be blocked.

connectionBlockReason

1.3.6.1.4.1.10734.3.3.2.7.2.1.8

The UUID of the signaturethat caused the block.

TPS MIBs Guide

ObjectOID

Description

connectionBlockSrcAddrV6

1.3.6.1.4.1.10734.3.3.2.7.2.1.9

The source IPv6 address of a
blocked connection.

connectionBlockDestAddrV6

1.3.6.1.4.1.10734.3.3.2.7.2.1.1
0

The destination IPv6 addressof a blocked connection.

connectionBlockTotalCount

1.3.6.1.4.1.10734.3.3.2.7.3

The total number ofconnections corresponding toblocked streams. Only the
first 50 are included in theconnection block table.

Rate limit streams table
The following table lists connections that have been rate-limited.
ObjectOID

Description

rateLimitStreamTable

1.3.6.1.4.1.10734.3.3.2.7.4

Table of connections that
correspond to rate-limited
streams.

rateLimitStreamEntry

1.3.6.1.4.1.10734.3.3.2.7.4.1

An entry in the rate-limited
stream table. Rows cannot be
added or deleted.

rateLimitStreamIndex

1.3.6.1.4.1.10734.3.3.2.7.4.1.1

The index number of theentry in the rate-limited
stream table.

rateLimitStreamSrcAddr

1.3.6.1.4.1.10734.3.3.2.7.4.1.2

The source IPv4 address of arate-limited stream.

rateLimitStreamSrcPort

1.3.6.1.4.1.10734.3.3.2.7.4.1.3

The source port of a ratelimited stream.

rateLimitStreamDestAddr

1.3.6.1.4.1.10734.3.3.2.7.4.1.4

The destination IPv4 addressof a rate-limited stream.

rateLimitStreamDestPort

1.3.6.1.4.1.10734.3.3.2.7.4.1.5

The destination port of a ratelimited stream.

1-83

TPS MIBs Guide

ObjectrateLimitStreamProtocol

OID

Description

1.3.6.1.4.1.10734.3.3.2.7.4.1.6

The protocol of a rate-limited
stream.
• 1: ICMP• 2: UDP• 3: TCP• 4: other IP• 5: ARP• 6: other ETH• 7: ICMP v6• 8: other IPV6

rateLimitStreamPort

1.3.6.1.4.1.10734.3.3.2.7.4.1.7

The segment on which theincoming data caused theconnection to be rate-limited.

rateLimitStreamReason

1.3.6.1.4.1.10734.3.3.2.7.4.1.8

The UUID of the signaturethat caused the rate-limit.

rateLimitStreamSrcAddrV6

1.3.6.1.4.1.10734.3.3.2.7.4.1.9

The source IPv6 address of arate-limited stream.

rateLimitStreamDestAddrV6

1.3.6.1.4.1.10734.3.3.2.7.4.1.1
0

The destination IPv6 addressof a rate-limited stream.

rateLimitStreamTotalCount

1.3.6.1.4.1.10734.3.3.2.7.5

The total number ofconnections corresponding torate-limited streams. Only the
first 50 are included in therate limited stream table.

Connection trusts table
The following table lists trusted connections.

1-84

TPS MIBs Guide

ObjectOID

Description

connectionTrustTable

1.3.6.1.4.1.10734.3.3.2.7.6.2

Table of connections
that correspond totrusted streams.

connectionTrustEntry

1.3.6.1.4.1.10734.3.3.2.7.6.2.1

An entry in theconnection trust table.
Rows cannot be added
or deleted.

connectionTrustIndex

1.3.6.1.4.1.10734.3.3.2.7.6.2.1.1

The index number of theentry in the connection
trust table.

connectionTrustSrcAddr

1.3.6.1.4.1.10734.3.3.2.7.6.2.1.2

The source IPv4 addressof a trusted connection.

connectionTrustSrcPort

1.3.6.1.4.1.10734.3.3.2.7.6.2.1.3

The source port of atrusted connection.

connectionTrustDestAddr

1.3.6.1.4.1.10734.3.3.2.7.6.2.1.4

The destination IPv4
address of a trusted
connection.

connectionTrustDestPort

1.3.6.1.4.1.10734.3.3.2.7.6.2.1.5

The destination port of atrusted connection.

connectionTrustProtocol

1.3.6.1.4.1.10734.3.3.2.7.6.2.1.6

The protocol of a trusted
connection.
• 1: ICMP• 2: UDP• 3: TCP• 4: other IP• 5: ARP• 6: other ETH• 7: ICMP v6• 8: other IPV6

1-85

TPS MIBs Guide

Object

1-86

OID

Description

connectionTrustPort

1.3.6.1.4.1.10734.3.3.2.7.6.2.1.7

The segment on which
the incoming datacaused the connection
to be trusted.

connectionTrustReason

1.3.6.1.4.1.10734.3.3.2.7.6.2.1.8

The UUID of thesignature that caused
the trust.

connectionTrustSrcAddrV6

1.3.6.1.4.1.10734.3.3.2.7.6.2.1.9

The source IPv6 addressof a trusted connection.

connectionTrustDestAddrV6

1.3.6.1.4.1.10734.3.3.2.7.6.2.1.10

The destination IPv6
address of a trusted
connection.

connectionTrustTotalCount

1.3.6.1.4.1.10734.3.3.2.7.6.3

The total number ofconnections
corresponding totrusted streams. Only
the first 50 are includedin the connection trust
table.

Chapter 2

Using HP Network Node Manager i withMIBs
HP Network Node Manager i (NNMi) is a well-known commercial network
management system. Much of this information can be transposed onto othernetwork management systems.
This topic focuses on adding enterprise MIB monitoring and reporting to
NNMi. The examples in this topic were created on NNMi running on
Windows XP Professional Service Pack 1.
Note
To perform the procedures in this topic, you must have installed NNMi. Referto the NNMi documentation for more information about that product.

This topic includes the following:• Loading TippingPoint Enterprise MIBs on page 2-2• MIB Application Builder on page 2-2• Discovering the device on page 2-3• Creating graphs with Application Builder on page 2-4

2-1

TPS MIBs Guide

Loading TippingPoint Enterprise MIBs
Before you begin, you must configure NNMi to understand the TippingPoint
Enterprise MIBs.
1. In the NNMi Root Map, select the Options menu.
2. Select Load/Unload MIBs: SNMP.
3. Load TIPPINGPOINT-REG-MIB.
4. Load the remaining TPT MIBs in any order. NNMi might prompt you
when loading the MIBs to add a macro definition. This is normal
behavior, and you should accept the MIB.

MIB Application Builder
NNMi includes a tool called MIB Application Builder that allows you to build
custom applications that retrieve data using SNMP and to retrieve any
information stored in a MIB.
1. Select Options => MIB Application Builder: SNMP. The MIB
Application Builder: SNMP dialog box displays.
2. Select Edit => New item. The application prompts you with three fields:
Application ID, Application Type and Application Title.
• Enter 111 for the Application ID.
• Leave the Application Type as Form.
• Enter an Application Title.
3. Select the MIB Objects that have the information that you want to view.
4. Click Next. The MIB Application Builder / Add MIB Objects screen
displays.
5. In the navigation tree, locate iso.org.dod.internet.private.enterprises.
You are now at the start of the IPS MIBs.
6. In the tree, select the variables that you want to monitor and click Add.
Click Close to return to the previous screen.
2-2

Using HP Network Node Manager i with MIBs

7. Depending on how you added the objects, you might need to reorderthem. You can reorder the variables by using the Up and Down arrows in
the New MIB Application - Display Fields form.
8. Click Next to continue to the New MIB Application - NMN Integration
dialog screen.
9. Enter TippingPoint after Configuration->. The line should appear as
Configuration->TippingPoint under Menu Location. This creates amenu item under the Configuration menu on the main screen.
10. You can select an object on the map. Select Configuration from themenu and retrieve the information you created if the device is a
TippingPoint device.
11. Close the MIB Application Builder dialog box.

Discovering the device
By default, NNMi automatically discovers devices as they arrive on the
network. This form of discovery can be a slow process and might not display
devices for days (depending on the size of your network). To expedite thatprocess, use the loadhosts command.
1. Open your text editor and create a file named hosts.
2. In the file, enter the IP address of your device and the hostname. This
format is similar to the UNIX /etc/hosts file format. For example, you
might enter the following information:
192.168.65.20 nds10

3. Save the file and open a command shell.
4. Run the loadhosts command on the file. The command takes the
network mask and the file as arguments. For example:
loadhosts -m 255.255.255.0 hosts

After you run the loadhosts command, the device is now discovered by
NNMi. When you open the Internet icon on your NNMi map, a green square

2-3

TPS MIBs Guide

displays. This icon should be your device or devices. Select this icon andchoose Configuration from the menu bar to view the device.
NNMi has a number of built-in applications that can retrieve data fromstandard MIBs. For example, when you open the device configuration, all of
the Ethernet interfaces associated with that device are displayed. When you
right-click on the interface and choose Interface Properties, information forthat interface is displayed.

Creating graphs with Application Builder
You can create an application to graph the data with the MIB Application
Builder tool.
1. Select the Application Builder from the Options menu.
2. Open your existing applications and double-click to edit.
3. Change the Application Type from a Form to a Graph.
4. Set 10 as the Poll Interval and abc as the Y-axis label. You can changethese settings to fit your needs.
5. To generate the graph for your device, select the IPS green square.
Choose TippingPoint from the Configuration menu. A graph displays forthe device. Allow the graph to run about 30 seconds to begin trending
the data.

2-4

Using HP Network Node Manager i with MIBs

2-5

Item Code: TPEM69851/230927