|
|
Table Of Contents
pcubeModules (1.3.6.1.4.1.5655.2)
pcubeSeMIB (1.3.6.1.4.1.5655.2.3)
pcubeWorkgroup (1.3.6.1.4.1.5655.4)
Proprietary MIB Reference
This appendix describes the pcube proprietary MIB supported by the SCE platform. A MIB (Management Information Base) is a database of objects that can be monitored by a network management system (NMS). The SCE platform supports both the standard MIB-II and a proprietary Service Control Enterprise MIB. This proprietary pcube MIB enables the external management system to perform configuration, performance, troubleshooting and alerting operations specific to the SCE platform, and therefore not provided by the standard MIB.
Note
Information and proprietary MIB files supported by the SCOS can be downloaded from: http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml under the Cisco Service Routing Products section.
pcube Enterprise MIB
The pcube Enterprise MIB splits into four main groups:
•
•
•
•
The pcube enterprise tree structure is defined in a MIB file named PCUBE-SMI.my .
Note
The figure below illustrates the pcube Service Control Enterprise MIB structure.
Conventions used in the diagram:
•
•
Figure B-1 Cisco Service Control MIB Structure
The pcubeProducts subtree
The pcubeProducts subtree contains the OIDs of Cisco Service Control products. These OIDs are used only to describe the Cisco Service Control platforms, not as roots for other OIDs.
This subtree does not contain online data, just global definitions.
The pcubeProductsMIB is defined the MIB file: PCUBE-PRODUCTS-MIB.my
The pcubeModules subtree
The pcubeModules subtree provides a root object identifier under which MIB modules can be defined.
This subtree does not contain online data, just global definitions.
The pcubeMgmt subtree
The pcubeMgmt subtree is the root for pcube MIBs that are relevant to multiple products.
The pcubeWorkgroups subtree
The pcubeWorkgroups subtree contains the actual MIBs for Cisco Service Control devices and sub-devices. This is where the SCE platform, the dispatcher, and also the SCA BB application, hook their actual OIDs and notifications. This means that the branches in this subtree are defined in multiple MIB files.
The pcubeConfigCopyMib subtree
The pcubeConfigCopy MIB is a subset of the Cisco Config-Copy-MIB ported to the pcube enterprise subtree. It supports only local copying of running config to startup config.
The pcubeConfigCopyMIB is defined the MIB file: PCUBE-CONFIG-COPY-MIB.my
The config copy MIB is intended for use by all pcube products, and is therefore placed under the pcubeMgmt subtree.
The pcubeSE MIB
The pcubeSE MIB comprises two branches:
pcubeSeEvents
Contains the OIDs used for sending enterprise-specific notifications.
pcubeSEObjs
Contains the OIDs that belong to the SCE platform, divided into groups according to functionality.
Application MIB Integration
The pcubeSeMIB described above contains information about the SCE platform. Information regarding the SML application running on the SCE platform is available through the following two interfaces:
•
•
Application and Subscriber groups
These groups allow the operator to view information exposed by the application. In essence, these groups contain tables that allow access to viewables and tuneables defined in the installed SML application. This mechanism is general, and does not require specific adjustments of the SCOS platform for an application. Any installed application can define variables that would then automatically be accessible through the application or subscriber groups.
The Application Group
The application group contains information about the application itself. It also contains two tables:
•
Contains a list of properties of the application. These properties are SML viewables and tuneables that are defined in global scope. Each property has a name and a type (both are strings).
This table is updated when the application is installed, and has read-only access. It is therefore managed by the agent (the SCOS).
•
Contains information about the application properties that appear in the appPropertiesTable , described above. For each such property, a value is available in one or more formats, as appropriate:
–
–
–
•
This table is cleared when an application is unloaded, or when the system resets. The manager may add rows to the table after the system starts, with properties taken from the appPropertiesTable , and then it is possible to poll these variables for their values. It is the manager's responsibility to read the value in the correct format (according to the "type" field in the appPropertiesTable ).
Note that the values cannot be changed through SNMP. Tuneables and Viewables are the same in this respect, they can only be viewed.
Note as well that all the properties in the application group are global properties.
The Subscriber Group
The subscribers group contains global statistics about the subscribers. It also contains two tables, which work in a mechanism very similar to that of the application properties tables described above:
•
Contains a list of "subscriber properties" that the installed application has defined. These properties are SML viewables and tuneables that are defined in subscriber scope. Each property has a name and a type (both are strings).
This table is updated when the application is installed, and has read-only access. It is therefore it is managed by the agent (the SCOS).
•
Like the appPropertiesValueTable , this table also uses the RowStatus mechanism to allow addition and removal of rows by the manager. Once a row is created in the subscriberValueTable , it is possible to poll the value of the property for the requested subscriber. The values are given in three formats (string, integer, and 64-bit integer, it being the responsibility of the manager to read the appropriate field, according to the type of the property)
In order to retrieve the value of a subscriber property, the manager must supply the following:
–
–
•
This table is also used by the pcubeEngageMIB .
The Engage MIB (pcubeEngageMIB)
The application group of the pcubeSeMIB allows the manager to retrieve information about the application. However, due to its generality, it requires quite a bit of intelligence from the management station. The pcubeEngageMIB is an application-specific MIB that supplies information relevant only to the SCA BB (Engage) application.
All information that the application may want to publish is stored in viewables and tuneables. However, there is currently no automatic way for the application to declare that a certain OID should reflect a certain application variable. For this reason, the Engage application MIB is actually implemented by the SCOS.
The Engage subscriber tables rely on the SCOS subscriber value tables described above. Since there is no table that contains a list of the subscribers in the system, the only subscribers referred to in the Engage tables are the ones that appear in the SCOS subscribersPropertiesValueTable . The spvIndex is used to index the subscribers in the pcubeEngageMIB as well.
Using this Reference
This reference describes all existing MIB objects. For each object, the following information is presented:
pcubeModules (1.3.6.1.4.1.5655.2)
pcubeModules provides a root object identifier from which module identity values may be assigned.
Modules:
•
•
pcubeSeMIB (1.3.6.1.4.1.5655.2.3)
Main SNMP MIB for the Cisco SCE products such as SCE 2000 and SCE 1000. This MIB provides configuration and runtime status for chassis, control modules, and line modules on the SCOS systems.
pcubeSeMIB Object Groups (1.3.6.1.4.1.5655.2.3.1.1)
Following is a list of the pcubeSeMIB object groups. Each object group consists of a number of related objects. All individual objects are listed and described in the pcubeWorkgroup section.
System Group: pcubeSystemGroup (1.3.6.1.4.1.5655.2.3.1.1.1)
The System group provides data on the system-wide functionality of the SCE platform.
Objects:
1.
2.
3.
Chassis Group: pcubeChassisGroup (1.3.6.1.4.1.5655.2.3.1.1.2)
The Chassis group defines and identifies the chassis, as well as environmental alarms related to the chassis.
Objects:
1.
2.
3.
4.
5.
6.
7.
8.
9.
Module Group: pcubeModuleGroup (1.3.6.1.4.1.5655.2.3.1.1.3)
The Module group identifies and defines the modules, or cards, in the SCE platform.
Objects:
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
Link Group: pcubeLinkGroup (1.3.6.1.4.1.5655.2.3.1.1.4)
The Link group defines and identifies the link. It provides information regarding the mode of operation of the link defined for each status of the platform.
Objects:
1.
2.
3.
4.
5.
6.
7.
8.
Disk Group: pcubeDiskGroup (1.3.6.1.4.1.5655.2.3.1.1.5)
The Disk group provides data regarding the space utilization on the disk.
Objects:
1.
2.
RDR Formatter Group: pcubeRdrFormatterGroup (1.3.6.1.4.1.5655.2.3.1.1.6)
The RDR Formatter provides information regarding RDR Formatter destinations (Collection Managers), as well as RDR statistics.
Objects:
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
19.
20.
21.
22.
23.
24.
25.
26.
27.
28.
29.
Logger Group: pcubeLoggerGroup (1.3.6.1.4.1.5655.2.3.1.1.7)
The Logger group is responsible for logging the system synchronous and asynchronous events.
Objects:
1.
2.
3.
4.
5.
6.
Subscribers Group: pcubeSubscribersGroup (1.3.6.1.4.1.5655.2.3.1.1.8)
The Subscribers group provides statistics concerning the number of subscribers and subscriber mappings. It also provides data on the subscriber properties and the value of those properties for a specified subscriber.
Objects:
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
19.
20.
21.
22.
23.
24.
25.
26.
Traffic Processor Group: pcubeTrafficProcessorGroup (1.3.6.1.4.1.5655.2.3.1.1.9)
The Traffic Processor group provides statistics regarding the traffic flow handled by each traffic processor.
Objects:
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
19.
20.
21.
22.
23.
24.
25.
26.
27.
28.
29.
30.
31.
32.
33.
34.
35.
36.
37.
38.
39.
40.
41.
Port Group: pcubePortGroup (1.3.6.1.4.1.5655.2.3.1.1.10)
The Port group provides data regarding the port, such as its type and speed.
Objects:
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
Transmit Queues Group: pcubeTxQueuesGroup (1.3.6.1.4.1.5655.2.3.1.1.11)
The Transmit Queues group provides data regarding the transmit queue counters.
Objects:
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
Global Controllers Group: pcubeGlobalControllersGroup (1.3.6.1.4.1.5655.2.3.1.1.12)
The Global Controllers group provides data regarding the Global Controllers configuration and counters.
Objects:
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
Application Group: pcubeApplicationGroup (1.3.6.1.4.1.5655.2.3.1.1.13)
The Application group indicates which application is installed in the SCE platform, and what the properties of the application and values of those properties are.
Objects:
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
Traffic Counters Group: pcubeTrafficCountersGroup (1.3.6.1.4.1.5655.2.3.1.1.14)
The Traffic Counters group provides information regarding the value of different the traffic counters.
Objects:
1.
2.
3.
4.
Attack Group: pcubeaAtackGroup (1.3.6.1.4.1.5655.2.3.1.1.15)
The Attack group provides information regarding detected attacks, aggregated by attack type.
Objects:
1.
2.
3.
4.
5.
6.
VAS Group: pcubeVasTrafficForwardingGroup (1.3.6.1.4.1.5655.2.3.1.1.16)
The VAS group provides information regarding the status of the VAS servers.
Objects:
1.
2.
3.
4.
MPLS/VPN Group: pcubeMplsVpnAutoLearnGroup (1.3.6.1.4.1.5655.2.3.1.1.17)
The MPLS/VPN Group provides data regarding MPLS/VPN auto-learning.
Objects:
1.
2.
Traps Group: pcubeTrapObjectsGroup (1.3.6.1.4.1.5655.2.3.1.1.18)
The traps group includes strings used for notifications.
Objects:
1.
2.
3.
pcubeCompliances (1.3.6.1.4.1.5655.2.3.1.2)
Module compliance is a compliance statement defined in this MIB module that defines which groups must be implemented.
pcubeCompliance module-compliances (1.3.6.1.4.1.5655.2.3.1.2.1)
A compliance statement defined in this MIB module, for SCE platform SNMP agents.
Module Name:
pcubeSeMIB
Mandatory Groups
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
pcubeWorkgroup (1.3.6.1.4.1.5655.4)
pcubeWorkgroup is the main subtree for objects and events of the Cisco SCE platform products.
Notification Types
Following is a list of the SCE platform notification types
operationalStatusOperationalTrap (1.3.6.1.4.1.5655.4.0.1)
The system operational state of the SCE platform has changed to Operational(3).
operationalStatusWarningTrap (1.3.6.1.4.1.5655.4.0.2)
The system operational state of the SCE platform has changed to Warning(4).
operationalStatusFailureTrap (1.3.6.1.4.1.5655.4.0.3)
The system operational state of the SCE platform has changed to Failure(5).
systemResetTrap (1.3.6.1.4.1.5655.4.0.4)
The agent entity is about to reset itself either per user request or due to a fatal event.
chassisTempAlarmOnTrap (1.3.6.1.4.1.5655.4.0.5)
The chassisTempAlarm object in this MIB has transitioned to the On(3) state, indicating that the temperature is too high.
chassisTempAlarmOffTrap (1.3.6.1.4.1.5655.4.0.6)
The chassisTempAlarm object in this MIB has transitioned to the Off(2) state, indicating that the temperature level is back to normal.
chassisVoltageAlarmOnTrap (1.3.6.1.4.1.5655.4.0.7)
The chassisVoltageAlarm object in this MIB has transitioned to the On(3) state, indicating that the voltage level is is out of safe bounds.
chassisFansAlarmOnTrap (1.3.6.1.4.1.5655.4.0.8)
The chassisFansAlarm object in this MIB has transitioned to the On(3) state, indicating fan malfunction.
chassisPowerSupplyAlarmOnTrap (1.3.6.1.4.1.5655.4.0.9)
The chassisPowerSupplyAlarm object in this MIB has transitioned to the On(3) state, indicating power supply malfunction.
rdrActiveConnectionTrap (1.3.6.1.4.1.5655.4.0.10)
One of the RDR-formatter connections has become the active connection.
rdrNoActiveConnectionTrap (1.3.6.1.4.1.5655.4.0.11)
There is no active connection between the RDR-formatter and any Collection Manager.
rdrConnectionUpTrap (1.3.6.1.4.1.5655.4.0.12)
The rdrFormatterDestConnectionStatus object in this MIB has transitioned to Up(2), indicating that one of the RDR-formatter connections was established.
rdrConnectionDownTrap (1.3.6.1.4.1.5655.4.0.13)
The rdrFormatterDestConnectionStatus object in this MIB has transitioned to Down(3), indicating that one of the RDR-formatter connections was disconnected.
loggerUserLogIsFullTrap (1.3.6.1.4.1.5655.4.0.18)
The User log file is full. The agent entity then rolls to the next file.
sntpClockDriftWarnTrap (1.3.6.1.4.1.5655.4.0.19)
The SNTP agent has not received an SNTP time update for a long period, which may result in a time drift of the agent entity's clock.
linkModeBypassTrap (1.3.6.1.4.1.5655.4.0.20)
The link mode has changed to bypass.
linkModeForwardingTrap (1.3.6.1.4.1.5655.4.0.21)
The link mode has changed to forwarding.
linkModeCutoffTrap (1.3.6.1.4.1.5655.4.0.22)
The link mode has changed to cutoff.
moduleAttackFilterActivatedTrap (1.3.6.1.4.1.5655.4.0.25)
The attack filter module has detected an attack and activated a filter. The type of attack-filter that was activated is returned in pcubeSeEventGenericString1.
Following are several examples of pcubeSeEventGenericString1 for various scenarios:
•
–
•
Attack detected: Attack from IP address 10.1.4.134, from subscriber side, protocol UDP. 10000 concurrent open flows detected, 57 concurrent Ddos-suspected flows detected. Action is: Report.–
•
Attack detected: Attack on IP address 10.1.4.135, from subscriber side, protocol ICMP. 745 concurrent open flows detected, 500 concurrent Ddos-suspected flows detected. Action is: Block.•
–
•
Attack filter: Forced block of flows from IP address 10.1.1.1, from subscriber side, protocol TCP. Attack forced using a force-filter command.–
•
Attack filter: Forced report to IP address 10.1.1.1, from network side, protocol Other. Attack forced using a force-filter command.moduleAttackFilterDeactivatedTrap (1.3.6.1.4.1.5655.4.0.26)
The attack filter module has removed a filter that was previously activated.
•
•
Following are several examples of pcubeSeEventGenericString1 for various scenarios:
•
End-of-attack detected — Attack on IP address 10.1.4.135, from subscriber side, protocol UDP. Action is: Report. Duration 20 seconds, attack comprised of 11736 flows.
End-of-attack detected — Attack from IP address 10.1.4.134, from subscriber side, protocol ICMP. Action is: Block. Duration 10 seconds, attack comprised of 2093 flows.
•
Attack filter — Forced to end block of flows from IP address 10.1.1.1, from subscriber side, protocol TCP. Attack end forced using a 'no force-filter' or a 'dont-filter' command. Duration 6 seconds, 1 flows blocked.
Attack filter — Forced to end report to IP address 10.1.1.1, from network side, protocol Other. Attack end forced using a 'no force-filter' or a 'dont-filter' command. Duration 13 seconds, attack comprised of 1 flows.
moduleEmAgentGenericTrap (1.3.6.1.4.1.5655.4.0.27)
A generic trap used by the Cisco management agent.
•
•
linkModeSniffingTrap (1.3.6.1.4.1.5655.4.0.28)
The agent entity has detected that the linkOperMode object in this MIB has changed to sniffing(5).
moduleRedundancyReadyTrap (1.3.6.1.4.1.5655.4.0.29)
The module was able to connect and synch with a redundant entity, and is now ready to handle fail-over if needed.
moduleRedundantConfigurationMismatchTrap (1.3.6.1.4.1.5655.4.0.30)
The module was not able to synch with a redundant entity, due to an incompatibility in essential configuration parameters between the module and the redundant entity.
moduleLostRedundancyTrap (1.3.6.1.4.1.5655.4.0.31)
The module has lost the ability to perform the fail-over procedure.
moduleSmConnectionDownTrap (1.3.6.1.4.1.5655.4.0.32)
The virtual connection to the SM (Subscriber Manager) is broken.
moduleSmConnectionUpTrap (1.3.6.1.4.1.5655.4.0.33)
The virtual connection to the SM is up and working.
moduleOperStatusChangeTrap (1.3.6.1.4.1.5655.4.0.34)
The value of moduleOperStatus has changed.
portOperStatusChangeTrap (1.3.6.1.4.1.5655.4.0.35)
The value of the portOperStatus object of the portIndex has changed, indicating that the link was either forced down or the force down was released.
chassisLineFeedAlarmOnTrap (1.3.6.1.4.1.5655.4.0.36)
The agent entity has detected that the chassisLineFeed object in this MIB has changed to the on(3) state.
rdrFormatterCategoryDiscardingReportsTrap (1.3.6.1.4.1.5655.4.0.37)
Theagent entity has detected that reports sent to this category are being discarded.
The rdrFormatterCategoryNumReportsDiscarded object in this MIB counts the number of discarded reports.
rdrFormatterCategoryStoppedDiscardingReportsTrap (1.3.6.1.4.1.5655.4.0.38)
The agent entity has detected that reports sent to this category are no longer being discarded.
The rdrFormatterCategoryNumReportsDiscarded object in this MIB counts the number of discarded reports.
sessionStartedTrap (1.3.6.1.4.1.5655.4.0.39)
The agent entity has accepted a new session. The pcubeSeEventGenericString1 contains the session type (telnet/SSH) and client IP address.
sessionEndedTrap (1.3.6.1.4.1.5655.4.0.40)
The agent entity has detected the end of a session. The pcubeSeEventGenericString1 contains the session type (telnet/SSH) and client IP address.
sessionDeniedAccessTrap (1.3.6.1.4.1.5655.4.0.41)
The agent entity has refused a session from unauthorized source. The pcubeSeEventGenericString1 contains the session type (telnet/SSH) and client IP address.
sessionBadLoginTrap (1.3.6.1.4.1.5655.4.0.42)
The agent entity has detected attempt to login with a wrong password. The pcubeSeEventGenericString1 contains the session type (telnet/SSH) and client IP address.
illegalSubscriberMappingTrap (1.3.6.1.4.1.5655.4.0.43)
The agent entity has detected that an external entity has attempted to create an illegal or inconsistent subscriber mapping.
pcubeSeEventGenericString1contains a message describing the problem.
loggerLineAttackLogFullTrap (1.3.6.1.4.1.5655.4.0.44)
The agent entity has detected that the attack log is full and a new log file is opened.
vasServerOperationalStatusChangeTrap (1.3.6.1.4.1.5655.4.0.45)
The agent entity has detected a change in the operational status of a VAS server.
pullRequestNumber (1.3.6.1.4.1.5655.4.0.46)
The number of pull requests currently issued for the anonymous subscriber identified in the pullRequestRetryFailedTra p.
Always returns a value of 0.
pullRequestRetryFailedTrap (1.3.6.1.4.1.5655.4.0.47)
An unknown subscriber could not be identified after a certain number of pull requests, and is suspected to be an intruder.
pcubeSeEventGenericString1contains subscriber ID.
mplsVpnTotalHWMappingsThresholdExceededTrap (1.3.6.1.4.1.5655.4.0.48)
The value of mplsVpnCurrentHWMappings exceeds the allowed threshold.
pcubeSe Objects
The pcubeSe objects provide configuration and runtime status for the SCE platform.
sysOperationalStatus (1.3.6.1.4.1.5655.4.1.1.1)
Indicates the operational status of the system.
Syntax
INTEGER {1 (other)— none of the following2 (boot)— the system is in boot process3 (operational)— the system is operational4 (warning)— the system is in Warning status5 (failure)— the system is in Failure status }sysFailureRecovery (1.3.6.1.4.1.5655.4.1.1.2)
Indicates the behavior of the system after abnormal boot.
Syntax
INTEGER {1 (other)— none of the following2 (operational)— the system should enter Operational mode after abnormal boot3 (non-operational)— the system should enter Failure mode after abnormal boot }sysVersion (1.3.6.1.4.1.5655.4.1.1.3)
The system version.
Syntax
DisplayStringpchassisSysType (1.3.6.1.4.1.5655.4.1.2.1)
The chassis system type.
Syntax
INTEGER {1 (other)— none of the following2 (SE1000)— SCE 1000 platform3 (SE100)— SCE 100 platform4 (SE2000)— SCE 2000 platform }pchassisPowerSupplyAlarm (1.3.6.1.4.1.5655.4.1.2.2)
Indicates whether the power supply to the chassis is normal. If the alarm is `on', it means that one or more of the power supplies is not functional
Syntax
INTEGER {1 (other)— none of the following2 (off)— the power supply to the chassis is normal3 (on)— the power supply to the chassis is not normal, and probably one or more of the power supplies is not functional. }pchassisFansAlarm (1.3.6.1.4.1.5655.4.1.2.3)
Indicates whether all the fans on the chassis are functional.
Syntax
INTEGER {1 (other)— none of the following2 (off)— all fans are functional3 (on)— one or more fans is not functional. }pchassisTempAlarm (1.3.6.1.4.1.5655.4.1.2.4)
Indicates the chassis temperature alarm status.
Syntax
INTEGER {1 (other)— none of the following2 (off)— temperature is within acceptable range3 (on)— temperature is too high. }pchassisVoltageAlarm (1.3.6.1.4.1.5655.4.1.2.5)
Indicates the chassis internal voltage alarm status. If the alarm is `on', it indicates that the voltage level of one or more unit in the chassis is not in the normal range.
Syntax
INTEGER {1 (other)— none of the following2 (off)— voltage level is within normal range3 (on)— voltage level is out of the acceptable bounds. }pchassisNumSlots (1.3.6.1.4.1.5655.4.1.2.6)
Indicates the number of slots in the chassis available for plug-in modules, including both currently occupied and empty slots.
Syntax
INTEGER (0..255)pchassisSlotConfig (1.3.6.1.4.1.5655.4.1.2.7)
An indication of which slots in the chassis are occupied.
This is an integer value with bits set to indicate configured modules. It is expressed as the function:
Sum of f(x) as x goes from 1 to the number of slots, where:
•
•
Syntax
INTEGER (0..65535)pchassisPsuType (1.3.6.1.4.1.5655.4.1.2.8)
Indicates the type of the power supplies.
Syntax
INTEGER {1 (other)— none of the following2 (AC)— AC power supply3 (DC)— DC power supply }pchassisLineFeedAlarm (1.3.6.1.4.1.5655.4.1.2.9)
Indicates whether the line feed to the chassis is connected and whether it is supplying power to the power supply unit.
Syntax
INTEGER {1 (other)— none of the following2 (OFF)— The line feed to the chassis is connected and has power3 (ON)— The line feed to the chassis is not normal. One or both of the line feeds may not be connected properly or have no power. }pmoduleTable (1.3.6.1.4.1.5655.4.1.3.1)
A list of module entries containing information defining the modules in the chassis.
The number of entries is the number of modules in the chassis.
Syntax
Sequence of pmoduleEntrypmoduleEntry (1.3.6.1.4.1.5655.4.1.3.1.1)
Entry containing a number of parameters defining the physical characteristics of one module in the chassis.
Index
{pmoduleIndex}Syntax
SEQUENCE {pmoduleIndexpmoduleTypepmoduleNumTrafficProcessorspmoduleSlotNumpmoduleHwVersionpmoduleNu mPortspmoduleNumLinkspmoduleConnectionModepmoduleSerialNumberpmoduleUpStreamAttackFilterin gTimepmoduleUpStreamLastAttackFilteringTimepmoduleDownStreamAttackFilteringTimepmoduleDown StreamLastAttackFilteringTimepmoduleAttackObjectsClearTimepmoduleAdminStatuspmoduleOperSta tus}pmoduleIndex (1.3.6.1.4.1.5655.4.1.3.1.1.1)
An ID number identifying the module. A unique value for each module within the chassis.
Syntax
INTEGER (1..255)pmoduleType (1.3.6.1.4.1.5655.4.1.3.1.1.2)
The type of module.
Syntax
INTEGER {1 (other)— none of the following2 (gbe2Module)— 2 port Gigabit Ethernet line interface, 2 Fast Ethernet 10/100 management interfaces 3 (fe2Module)— 2 port Fast Ethernet line interface, 1 Fast Ethernet 10/100 management interface4 (gbe4Module)— 4 port Gigabit Ethernet line interface, 2 Fast Ethernet 10/100 management interfaces5 (fe4Module)— 4 port Fast Ethernet line interface, 2 Fast Ethernet 10/100 management interfaces6 (oc12-4Module)— 4 port OC12 line interface, 2 Fast Ethernet 10/100 management interfaces7 (fe8Module)— 8 port Fast Ethernet line interface, 2 Fast Ethernet 10/100 management interfaces }pmoduleNumTrafficProcessors (1.3.6.1.4.1.5655.4.1.3.1.1.3)
The number of traffic processors supported by the module.
Syntax
INTEGER (0..255)pmoduleSlotNum (1.3.6.1.4.1.5655.4.1.3.1.1.4)
The number of the slot in the chassis in which the module is installed.
Valid entries are from 1 to the value of pchassisNumSlot s.
Syntax
INTEGER (1..255)pmoduleHwVersion (1.3.6.1.4.1.5655.4.1.3.1.1.5)
The hardware version of the module.
Syntax
DisplayStringpmoduleNumPorts (1.3.6.1.4.1.5655.4.1.3.1.1.6)
The number of ports supported by the module.
Syntax
INTEGER (0..255)pmoduleNumLinks (1.3.6.1.4.1.5655.4.1.3.1.1.7)
The number of links carrying inband traffic that are supported by the module. The link is uniquely defined by the two ports that are at its endpoints.
Syntax
INTEGER (0..255)pmoduleConnectionMode (1.3.6.1.4.1.5655.4.1.3.1.1.8)
Indicates the connection mode of the module.
Syntax
INTEGER {1 (other)— none of the following2 (inline)— SCE is both receiving and transmitting traffic on the line ports.3 (receive-only)— SCE can only receive packets from the line ports. This mode is suitable for external splitting topology.4 (inline-cascade)— SCE is both receiving and transmitting traffic on the line ports and the cascade ports.5 (receive-only-cascade)— SCE can only receive packets from the line and the cascade ports. This mode is suitable for external splitting topology }pmoduleSerialNumber (1.3.6.1.4.1.5655.4.1.3.1.1.9)
The serial number of the module.
Syntax
DisplayStringpmoduleUpStreamAttackFilteringTime (1.3.6.1.4.1.5655.4.1.3.1.1.10)
The accumulated time (in hundredths of a second) during which attack up-stream traffic was filtered.
Syntax
TimeTickspmoduleUpStreamLastAttackFilteringTime (1.3.6.1.4.1.5655.4.1.3.1.1.11)
The time (in hundredths of a second) since the previous attack filtered in the up-stream traffic.
Syntax
TimeTickspmoduleDownStreamAttackFilteringTime (1.3.6.1.4.1.5655.4.1.3.1.1.12)
The accumulated time (in hundredths of a second) during which attack down-stream traffic was filtered.
Syntax
TimeTickspmoduleDownStreamLastAttackFilteringTime (1.3.6.1.4.1.5655.4.1.3.1.1.13)
The time (in hundredths of a second) since the previous attack filtered in the down-stream traffic.
Syntax
TimeTickspmoduleAttackObjectsClearTime (1.3.6.1.4.1.5655.4.1.3.1.1.14)
The time (in hundredths of a second) since the attack objects were cleared. Writing a 0 to this object causes the counters to be cleared.
Syntax
TimeTickspmoduleAdminStatus (1.3.6.1.4.1.5655.4.1.3.1.1.15)
Indicates whether the module is configured to handle traffic on startup or reboot (active), to be the hot standby.
Syntax
INTEGER {1 (other)— none of the following2 (primary)— Handle traffic on startup.3 (secondary)— Fail-over module on startup. }pmoduleOperStatus (1.3.6.1.4.1.5655.4.1.3.1.1.16)
Indicates whether the module is currently handling (active), or is on standby.
Syntax
INTEGER {1 (other)— none of the following2 (active)— Currently is handling traffic.3 (standby)— Currently is the fail-over module. }linkTable (1.3.6.1.4.1.5655.4.1.4.1)
A list of link entries containing information regarding the configuration and status of the links that pass through the SCE platform and carry in-band traffic.
The number of entries is determined by the number of modules in the chassis and the number of links on each module.
Syntax
Sequence of linkEntrylinkEntry (1.3.6.1.4.1.5655.4.1.4.1.1)
Entry containing information about the Link.
Index
{linkModuleIndex, linkIndex}Syntax
SEQUENCE {linkModuleIndexlinkIndexlinkAdminModeOnActivelinkAdminModeOnFailurelinkOperModelinkStatus ReflectionEnablelinkSubscriberSidePortIndexlinkNetworkSidePortIndex}linkModuleIndex (1.3.6.1.4.1.5655.4.1.4.1.1.1)
An index value ( pmoduleInde x) that uniquely identifies the module where this link is located.
Syntax
INTEGER (1..255)linkIndex (1.3.6.1.4.1.5655.4.1.4.1.1.2)
An index value that uniquely identifies the link within the specified module.
Valid entries are 1 to the value of pmoduleNumLinks for this module.
Syntax
INTEGER (1..255)linkAdminModeOnActive (1.3.6.1.4.1.5655.4.1.4.1.1.3)
The desired mode of the link when the operating status of the module is active and it is not in boot or failure.
Possible values ( LinkModeType):
•
•
Syntax
LinkModeTypelinkAdminModeOnFailure (1.3.6.1.4.1.5655.4.1.4.1.1.4)
The desired mode of the link when the system status is failure.
Possible values ( LinkModeType):
•
•
Syntax
LinkModeTypelinkOperMode (1.3.6.1.4.1.5655.4.1.4.1.1.5)
The current operational mode of the link.
Possible values ( LinkModeType):
•
•
•
Syntax
LinkModeTypelinkStatusReflectionEnable (1.3.6.1.4.1.5655.4.1.4.1.1.6)
Indicates whether failure of the physical link on one interface should trigger the failure of the link on the other interface on the module.
Syntax
INTEGER {1 (enabled)2 (disabled)}linkSubscriberSidePortIndex (1.3.6.1.4.1.5655.4.1.4.1.1.7)
An index value that uniquely identifies this link with the related port that is connected to the subscriber side.
Syntax
INTEGER (0..255)linkNetworkSidePortIndex (1.3.6.1.4.1.5655.4.1.4.1.1.8)
An index value that uniquely identifies this link with the related port that is connected to the network side.
Syntax
INTEGER (0..255)diskNumUsedBytes (1.3.6.1.4.1.5655.4.1.5.1)
The number of used bytes on the disk.
Syntax
Unsigned32 (0...4294967295)diskNumFreeBytes (1.3.6.1.4.1.5655.4.1.5.2)
The number of free bytes on the disk.
Syntax
Unsigned32 (0...4294967295)rdrFormatterEnable (1.3.6.1.4.1.5655.4.1.6.1)
Indicates whether the RDR-formatter is enabled or disabled.
When the RDR-formatter is enabled, it sends the reports it gets from the traffic processors to the Collection Manager as defined in the rdrFormatterDestTable.
Syntax
INTEGER {1 (enabled)2 (disabled)}rdrFormatterDestTable (1.3.6.1.4.1.5655.4.1.6.2)
This table lists the addresses of Collection Managers.
If the RDR-formatter is enabled, the destination with the highest priority to which a TCP connection can be established is designated as the active connection, and would receive the reports generated by the traffic processors.
The table may contain a maximum of three entries.
Syntax
Sequence of rdrFormatterDestEntryrdrFormatterDestEntry (1.3.6.1.4.1.5655.4.1.6.2.1)
Entry defining one RDR destination.
Index
{rdrFormatterDestIPAddr, rdrFormatterDestPort}Syntax
SEQUENCE {rdrFormatterDestIPAddrrdrFormatterDestPortrdrFormatterDestPriorityrdrFormatterDestStatusr drFormatterDestConnectionStatusrdrFormatterDestNumReportsSentrdrFormatterDestNumReportsDis cardedrdrFormatterDestReportRaterdrFormatterDestReportRatePeakrdrFormatterDestReportRatePe akTime}rdrFormatterDestIPAddr (1.3.6.1.4.1.5655.4.1.6.2.1.1)
The IP address of a Collection Manager.
Syntax
IP AddressrdrFormatterDestPort (1.3.6.1.4.1.5655.4.1.6.2.1.2)
The TCP port on which the Collection Manager listens and the to which the RDR-Formatter should connect.
Syntax
INTEGER (1...65535)rdrFormatterDestPriority (1.3.6.1.4.1.5655.4.1.6.2.1.3)
The priority given to the Collection Manager. The active Collection Manager is the Collection Manager with the highest priority whose TCP connection is up.
Syntax
INTEGER (1...100)rdrFormatterDestStatus (1.3.6.1.4.1.5655.4.1.6.2.1.4)
Indicates whether this destination is the active one.
In redundancy and simple-load-balancing modes there can be only one `active' destination, which is the one to which the reports are sent. In multicast mode all destinations receive the active mode.
Syntax
INTEGER {1 (other)— none of the following2 (active)— this destination is where the reports are sent3 (standby)— this destination is a backup }rdrFormatterDestConnectionStatus (1.3.6.1.4.1.5655.4.1.6.2.1.5)
The status of TCP connection to this destination.
Syntax
INTEGER {1 (other)— none of the following2 (up)— the TCP connection to this destination is up3 (down)— the TCP connection to this destination is down }rdrFormatterDestNumReportsSent (1.3.6.1.4.1.5655.4.1.6.2.1.6)
The number of reports sent by the RDR-formatter to this destination.
Syntax
Unsigned32 (0...4294967295)rdrFormatterDestNumReportsDiscarded (1.3.6.1.4.1.5655.4.1.6.2.1.7)
The number of reports dropped by the RDR-formatter at this destination.
Syntax
Unsigned32 (0...4294967295)rdrFormatterDestReportRate (1.3.6.1.4.1.5655.4.1.6.2.1.8)
The current rate (in reports per second) of sending reports to this destination.
Syntax
Unsigned32 (0...4294967295)rdrFormatterDestReportRatePeak (1.3.6.1.4.1.5655.4.1.6.2.1.9)
The maximum rate of sending reports to this destination.
Syntax
Unsigned32 (0...4294967295)rdrFormatterDestReportRatePeakTime (1.3.6.1.4.1.5655.4.1.6.2.1.10)
The time (in hundredths of a second) since the rdrFormatterDestReportRatePeak value occurred.
Syntax
TimeTicksrdrFormatterNumReportsSent (1.3.6.1.4.1.5655.4.1.6.3)
The number of reports sent by the RDR-formatter.
Syntax
Unsigned32 (0...4294967295)rdrFormatterNumReportsDiscarded (1.3.6.1.4.1.5655.4.1.6.4)
The number of reports dropped by the RDR-formatter.
Syntax
Unsigned32 (0...4294967295)rdrFormatterClearCountersTime (1.3.6.1.4.1.5655.4.1.6.5)
The time (in hundredths of a second) since the RDR-formatter counters were last cleared. Writing a 0 to this object causes the RDR-formatter counters to be cleared.
Syntax
TimeTicksrdrFormatterReportRate (1.3.6.1.4.1.5655.4.1.6.6)
The current rate (in reports per second) of sending reports to all destinations.
Syntax
Unsigned32 (0...4294967295)rdrFormatterReportRatePeak (1.3.6.1.4.1.5655.4.1.6.7)
The maximum rate of sending reports to all destinations.
Syntax
Unsigned32 (0...4294967295)rdrFormatterReportRatePeakTime (1.3.6.1.4.1.5655.4.1.6.8)
The time (in hundredths of a second) since the rdrFormatterReportRatePeak value occurred.
Syntax
TimeTicksrdrFormatterProtocol (1.3.6.1.4.1.5655.4.1.6.9)
The RDR protocol currently in use.
Syntax
INTEGER {1 (other)— none of the following2 (RDRv1)— RDR protocol version 13 (RDRv2)— RDR protocol version 2 }rdrFormatterForwardingMode (1.3.6.1.4.1.5655.4.1.6.10)
The manner in which the RDR formatter sends the reports to the destinations.
Syntax
INTEGER {1 (other)— none of the following2 (redundancy)— all RDRs are sent to the primary (active) destination, and all other destinations are in standby3 (simpleLoadBalancing)— each successive RDR is sent to a different destination, one destination after the other, in a round robin manner4 (multicast)— all RDRs are sent to all destinations }rdrFormatterCategoryTable (1.3.6.1.4.1.5655.4.1.6.11)
This table describes the different categories of RDRs and supplies some statistical information about the RDRs sent to these categories
Syntax
Sequence of rdrFormatterCategoryEntryrdrFormatterCategoryEntry (1.3.6.1.4.1.5655.4.1.6.11.1)
Entry containing information about the RDR formatter categories.
Index
{rdrFormatterCategoryIndex}Syntax
SEQUENCE {rdrFormatterCategoryIndexrdrFormatterCategoryNamerdrFormatterCategoryNumReportsSentrdrFor matterCategoryNumReportsDiscardedrdrFormatterCategoryReportRaterdrFormatterCategoryReportR atePeakrdrFormatterCategoryReportRatePeakTimerdrFormatterCategoryNumReportsQueued}rdrFormatterCategoryIndex (1.3.6.1.4.1.5655.4.1.6.11.1.1)
The RDR formatter category number.
Syntax
INTEGER (1..4)rdrFormatterCategoryName (1.3.6.1.4.1.5655.4.1.6.11.1.2)
The name of the category.
Syntax
DisplayStringrdrFormatterCategoryNumReportsSent (1.3.6.1.4.1.5655.4.1.6.11.1.3)
The number of reports sent by the RDR-formatter to this category.
Syntax
Unsigned32 (0...4294967295)rdrFormatterCategoryNumReportsDiscarded (1.3.6.1.4.1.5655.4.1.6.11.1.4)
The number of reports dropped by the RDR formatter for this category.
Syntax
Unsigned32 (0...4294967295)rdrFormatterCategoryReportRate (1.3.6.1.4.1.5655.4.1.6.11.1.5)
The rate of the reports (in reports per second) currently sent to this category.
Syntax
Unsigned32 (0...4294967295)rdrFormatterCategoryReportRatePeak (1.3.6.1.4.1.5655.4.1.6.11.1.6)
The maximum report rate sent to this category.
Syntax
Unsigned32 (0...4294967295)rdrFormatterCategoryReportRatePeakTime (1.3.6.1.4.1.5655.4.1.6.11.1.7)
The time (in hundredths of a second) since the rdrFormatterCategoryReportRatePeak value occurred.
Syntax
TimeTicksrdrFormatterCategoryNumReportsQueued (1.3.6.1.4.1.5655.4.1.6.11.1.8)
The number of pending reports in this category.
Syntax
Unsigned32 (0...4294967295)rdrFormatterCategoryDestTable (1.3.6.1.4.1.5655.4.1.6.12)
This table describes the partition of the RDR destinations between the different categories and the priority and status of each destination in each category
Syntax
Sequence of rdrFormatterCategoryDestEntryrdrFormatterCategoryDestEntry (1.3.6.1.4.1.5655.4.1.6.12.1)
A destination table entry.
Index
{rdrFormatterCategoryIndex, rdrFormatterDestIPAddr, rdrFormatterDestPort}Syntax
SEQUENCE {rdrFormatterCategoryDestPriorityrdrFormatterCategoryDestStatus}rdrFormatterCategoryDestPriority (1.3.6.1.4.1.5655.4.1.6.12.1.1)
The priority assigned to the Collection Manager for this category.
The active Collection Manager is the Collection Manager with the highest priority and a TCP connection that is up.
Syntax
INTEGER (1...100)rdrFormatterCategoryDestStatus (1.3.6.1.4.1.5655.4.1.6.12.1.2)
Indicates whether the destination is currently active or standby.
In redundancy and in simple Load Balancing rdrFormatterForwardingMode there can be only one active destination, which is where the reports are currently being sent. In multicast mode, all destinations will be assigned the active(2) status
Syntax
INTEGER {1 (other)— none of the following2 (active)— this is the destination to which reports are currently being sent3 (standby)— this destination is a backup }loggerUserLogEnable (1.3.6.1.4.1.5655.4.1.7.1)
Indicates whether the logging of user information is enabled or disabled.
Syntax
INTEGER {1 (enabled)2 (disabled)}loggerUserLogNumInfo (1.3.6.1.4.1.5655.4.1.7.2)
The number of Info messages logged into the user log file since last reboot or last time the counter was cleared
Syntax
Unsigned32 (0...4294967295)loggerUserLogNumWarning (1.3.6.1.4.1.5655.4.1.7.3)
The number of Warning messages logged into the user log file since last reboot or last time the counter was cleared.
Syntax
Unsigned32 (0...4294967295)loggerUserLogNumError (1.3.6.1.4.1.5655.4.1.7.4)
The number of Error messages logged into the user log file since last reboot or last time the counter was cleared.
Syntax
Unsigned32 (0...4294967295)loggerUserLogNumFatal (1.3.6.1.4.1.5655.4.1.7.5)
The number of Fatal messages logged into the user log file since last reboot or last time the counter was cleared
Syntax
Unsigned32 (0...4294967295)loggerUserLogClearCountersTime (1.3.6.1.4.1.5655.4.1.7.6)
The time (in hundredths of a second) since user log counters were last cleared.
Writing a 0 to this object causes the user log counters to be cleared.
Syntax
TimeTickssubscribersInfoTable (1.3.6.1.4.1.5655.4.1.8.1)
Data regarding subscriber management operations performed.
Syntax
Sequence of subscribersInfoEntrysubscribersInfoEntry (1.3.6.1.4.1.5655.4.1.8.1.1)
Entry describing the subscriber management operations performed on a certain module.
Index
{pmoduleIndex}Syntax
SEQUENCE {subscribersNumIntroduced subscribersNumFree subscribersNumIpAddrMappings subscribersNumIpAddrMappingsFree subscribersNumIpRangeMappings subscribersNumIpRangeMappingsFree subscribersNumVlanMappings subscribersNumVlanMappingsFree subscribersNumActive subscribersNumActivePeak subscribersNumActivePeakTime subscribersNumUpdatessubscribersCountersClearTimesubscriberssubscribersNumTpIpRangeMapping ssubscribersNumTpIpRangeMappingsFreeCountersClearTimesubscribersNumAnonymoussubscribersNum WithSessions}subscribersNumIntroduced (1.3.6.1.4.1.5655.4.1.8.1.1.1)
The current number of subscribers introduced to the SCE. These subscribers may or may not have IP address or VLAN mappings. Subscribers who do not have mappings of any kind cannot be associated with traffic, and will be served by the SCE according to the default settings.
Syntax
Unsigned32 (0...4294967295)subscribersNumFree (1.3.6.1.4.1.5655.4.1.8.1.1.2)
The number of subscribers that may be introduced in addition to the currently introduced subscribers.
Syntax
Unsigned32 (0...4294967295)subscribersNumIpAddrMappings (1.3.6.1.4.1.5655.4.1.8.1.1.3)
The current number of IP address to subscriber mappings.
Syntax
Unsigned32 (0...4294967295)subscribersNumIpAddrMappingsFree (1.3.6.1.4.1.5655.4.1.8.1.1.4)
The number of free IP address to subscriber mappings that are available for defining new mappings.
Syntax
Unsigned32 (0...4294967295)subscribersNumIpRangeMappings (1.3.6.1.4.1.5655.4.1.8.1.1.5)
The current number of IP-range to subscriber mappings.
Syntax
Unsigned32 (0...4294967295)subscribersNumIpRangeMappingsFree (1.3.6.1.4.1.5655.4.1.8.1.1.6)
The number of free IP range to subscriber mappings that are available for defining new mappings.
Syntax
Unsigned32 (0...4294967295)subscribersNumVlanMappings (1.3.6.1.4.1.5655.4.1.8.1.1.7)
The current number of VLAN to subscriber mappings
Syntax
Unsigned32 (0...4294967295)subscribersNumVlanMappingsFree (1.3.6.1.4.1.5655.4.1.8.1.1.8)
The number of free VLAN to subscriber mappings that are available for defining new mappings.
Syntax
Unsigned32 (0...4294967295)subscribersNumActive (1.3.6.1.4.1.5655.4.1.8.1.1.9)
The current number of active subscribers. These subscribers necessarily have IP address or VLAN mappings that define the traffic to be served according to the subscriber service agreement.
Syntax
Unsigned32 (0...4294967295)subscribersNumActivePeak (1.3.6.1.4.1.5655.4.1.8.1.1.10)
The peak value of subscribersNumActive since the last time it was cleared or the system started.
Syntax
Unsigned32 (0...4294967295)subscribersNumActivePeakTime (1.3.6.1.4.1.5655.4.1.8.1.1.11)
The time (in hundredths of a second) since the subscribersNumActivePeak value occurred.
Syntax
TimeTickssubscribersNumUpdates (1.3.6.1.4.1.5655.4.1.8.1.1.12)
The accumulated number of subscribers database updates received by the SCE.
Syntax
Unsigned32 (0...4294967295)subscribersCountersClearTime (1.3.6.1.4.1.5655.4.1.8.1.1.13)
The time (in hundredths of a second) since the subscribers counters were cleared.
Writing a 0 to this object causes the counters to be cleared.
Syntax
TimeTickssubscribersNumTpIpRangeMappings (1.3.6.1.4.1.5655.4.1.8.1.1.14)
The current number of IP range to Traffic Processor mappings.
Syntax
Unsigned32 (0...4294967295)subscribersNumTpIpRangeMappingsFree (1.3.6.1.4.1.5655.4.1.8.1.1.15)
The current number of IP range to Traffic Processor mappings that are available for defining new mappings.
Syntax
Unsigned32 (0...4294967295)subscribersNumAnonymous (1.3.6.1.4.1.5655.4.1.8.1.1.16)
The current number of anonymous subscribers.
Syntax
Unsigned32 (0...4294967295)subscribersNumWithSessions (1.3.6.1.4.1.5655.4.1.8.1.1.17)
The current number of subscribers with open sessions.
Syntax
Unsigned32 (0...4294967295)subscribersPropertiesTable (1.3.6.1.4.1.5655.4.1.8.2)
List of all subscriber properties. This table is updated each time an application is loaded on the SCE platform.
Syntax
Sequence of subscribersPropertiesEntrysubscribersPropertiesEntry (1.3.6.1.4.1.5655.4.1.8.2.1)
Entry describing subscriber properties of the application relevant for a certain module.
Index
{pmoduleIndex, spIndex}Syntax
SEQUENCE {spIndexspNamespType}spIndex (1.3.6.1.4.1.5655.4.1.8.2.1.1)
An index value that uniquely identifies the subscriber property.
Syntax
INTEGER (1..255)spName (1.3.6.1.4.1.5655.4.1.8.2.1.2)
Name of the subscriber property.
Syntax
DisplayStringspType (1.3.6.1.4.1.5655.4.1.8.2.1.3)
Property type in respect to: variable type (integer, boolean, string etc), number of elements (scalar or array), and restrictions, if any.
Syntax
DisplayStringsubscriberPropertiesValuesTable (1.3.6.1.4.1.5655.4.1.8.3)
The subscriber properties value table is used to provide values for the subscriber properties for a specific subscriber introduced into the SCE platform.
An entry must be created by setting the entry spvRowStatus object with CreateAndGo (4) before setting the name of the subscriber and the property requested. The property requested must be one of the properties from the subscribersPropertiesTable. To remove an entry set the spvRowStatus object with Destroy (6).
To poll the subscriber property, either of these objects should be polled:
•
•
The table is cleared when the application is unloaded.
Syntax
Sequence of subscribersPropertiesValueEntrysubscriberPropertiesValueEntry (1.3.6.1.4.1.5655.4.1.8.3.1)
Entry providing information on the value of one of the specified subscriber properties.
Index
{pmoduleIndex, spvIndex}Syntax
SEQUENCE {SpvIndexspvSubNamespvPropertyNamespvRowStatusspvPropertyStringValuespvPropertyUintValuesp vPropertyCounter64Value}spvIndex (1.3.6.1.4.1.5655.4.1.8.3.1.1)
An index value that uniquely identifies the entry.
Syntax
INTEGER (1.. 1024)spvSubName (1.3.6.1.4.1.5655.4.1.8.3.1.2)
A name that uniquely identifies the subscriber.
Syntax
DisplayString (Size 1...40)spvPropertyName (1.3.6.1.4.1.5655.4.1.8.3.1.3)
A name that uniquely identifies the subscriber property.
Array-type properties may be accessed one element at a time in C-like format. (For example: x[1], or y[1][2])
Syntax
DisplayString (Size 1...128)spvRowStatus (1.3.6.1.4.1.5655.4.1.8.3.1.4)
Controls creation of a table entry. Only setting CreateAndGo (4) and Destroy (6) will change the status of the entry.
Syntax
RowStatusspvPropertyStringValue (1.3.6.1.4.1.5655.4.1.8.3.1.5)
The value of the subscriber property in display string format.
Syntax
DisplayString (SIZE 0...128)spvPropertyUintValue (1.3.6.1.4.1.5655.4.1.8.3.1.6)
The value of the subscriber property in Uint format.
If the property cannot be cast to Uint format, getting this object returns zero.
Syntax
Unsigned32 (0...4294967295)spvPropertyCounter64Value (1.3.6.1.4.1.5655.4.1.8.3.1.7)
The value of the subscriber property in Counter64 format.
If the property cannot be cast toCounter64 format, getting this object returns zero.
Syntax
Counter64tpInfoTable (1.3.6.1.4.1.5655.4.1.9.1)
The Traffic Processor Info table consists of data regarding traffic handled by the traffic processors, classified by packets and flows.
Syntax
Sequence of tpInfoEntrytpInfoEntry (1.3.6.1.4.1.5655.4.1.9.1.1)
Entry containing information from the traffic processors.
Index
{tpModuleIndex, tpIndex}Syntax
SEQUENCE {tpModuleIndextpIndextpTotalNumHandledPacketstpTotalNumHandledFlows tpNumActiveFlows tpNumActiveFlowsPeak tpNumActiveFlowsPeakTime tpNumTcpActiveFlows tpNumTcpActiveFlowsPeak tpNumTcpActiveFlowsPeakTime tpNumUdpActiveFlows tpNumUdpActiveFlowsPeak tpNumUdpActiveFlowsPeakTime tpNumNonTcpUdpActiveFlowstpNumNonTcpUdpActiveFlowsPeak tpNumNonTcpUdpActiveFlowsPeakTime tpTotalNumBlockedPacketstpTotalNumBlockedFlowstpTotalNumDiscardedPacketsDueToBwLimittpTota lNumWredDiscardedPacketstpTotalNumFragmentstpTotalNumNonIpPacketstpTotalNumIpCrcErrPackets tpTotalNumIpLengthErrPacketstpTotalNumIpBroadcastPacketstpTotalNumTtlErrPacketstpTotalNumT cpUdpCrcErrPacketstpClearCountersTimetpHandledPacketsRatetpHandledPacketsRatePeaktpHandled PacketsRatePeakTimetpHandledFlowsRatetpHandledFlowsRatePeaktpHandledFlowsRatePeakTimetpCpu UtilizationtpCpuUtilizationPeaktpCpuUtilizationPeakTimetpFlowsCapacityUtilizationtpFlowsCa pacityUtilizationPeaktpFlowsCapacityUtilizationPeakTimetpServiceLoss}tpModuleIndex (1.3.6.1.4.1.5655.4.1.9.1.1.1)
An index value ( pmoduleIndex ) that uniquely identifies the module in which this traffic processor is located.
Syntax
INTEGER (1...255)tpIndex (1.3.6.1.4.1.5655.4.1.9.1.1.2)
An index value that uniquely identifies the traffic processor within the specified module. The value is determined by the location of the traffic processor on the module.
Valid entries are 1 to the value of pmoduleNumTrafficProcessors for the specified module.
Syntax
INTEGER (1...255)tpTotalNumHandledPackets (1.3.6.1.4.1.5655.4.1.9.1.1.3)
The accumulated number of packets handled by this traffic processor since last reboot or last time this counter was cleared.
Syntax
Unsigned32 (0...4294967295)tpTotalNumHandledFlows (1.3.6.1.4.1.5655.4.1.9.1.1.4)
The accumulated number of flows handled by this traffic processor since last reboot or last time this counter was cleared.
Syntax
Unsigned32 (0...4294967295)tpNumActiveFlows (1.3.6.1.4.1.5655.4.1.9.1.1.5)
The number of flows currently being handled by this traffic processor.
Syntax
Unsigned32 (0...4294967295)tpNumActiveFlowsPeak (1.3.6.1.4.1.5655.4.1.9.1.1.6)
The peak value of tpNumActiveFlows since the last time it was cleared or the system started.
Syntax
Unsigned32 (0...4294967295)tpNumActiveFlowsPeakTime (1.3.6.1.4.1.5655.4.1.9.1.1.7)
The time (in hundredths of a second) since the tpNumActiveFlowsPeak value occurred.
Syntax
TimeTickstpNumTcpActiveFlows (1.3.6.1.4.1.5655.4.1.9.1.1.8)
The number of TCP flows currently being handled by this traffic processor
Syntax
Unsigned32 (0...4294967295)TpNumTcpActiveFlowsPeak (1.3.6.1.4.1.5655.4.1.9.1.1.9)
The peak value of tpNumTcpActiveFlows since the last time it was cleared or the system started.
Syntax
Unsigned32 (0...4294967295)tpNumTcpActiveFlowsPeakTime (1.3.6.1.4.1.5655.4.1.9.1.1.10)
The time (in hundredths of a second) since the tpNumTcpActiveFlowsPeak value occurred.
Syntax
TimeTickstpNumUdpActiveFlows (1.3.6.1.4.1.5655.4.1.9.1.1.11)
The number of UDP flows currently being handled by the traffic processor.
Syntax
Unsigned32 (0...4294967295)tpNumUdpActiveFlowsPeak (1.3.6.1.4.1.5655.4.1.9.1.1.12)
The peak value of tpNumUdpActiveFlows since the last time it was cleared or the system started.
Syntax
Unsigned32 (0...4294967295)tpNumUdpActiveFlowsPeakTime (1.3.6.1.4.1.5655.4.1.9.1.1.13)
The time (in hundredths of a second) since the tpNumUdpActiveFlowsPeak value occurred.
Syntax
TimeTickstpNumNonTcpUdpActiveFlows (1.3.6.1.4.1.5655.4.1.9.1.1.14)
The number of non TCP/UDP flows currently being handled by the traffic processor.
Syntax
Unsigned32 (0...4294967295)tpNumNonTcpUdpActiveFlowsPeak (1.3.6.1.4.1.5655.4.1.9.1.1.15)
The peak value of tpNumNonTcpUdpActiveFlows since the last time it was cleared or the system started.
Syntax
Unsigned32 (0...4294967295)tpNumNonTcpUdpActiveFlowsPeakTime (1.3.6.1.4.1.5655.4.1.9.1.1.16)
The time (in hundredths of a second) since the tpNumNonTcpUdpActiveFlowsPeak value occurred.
Syntax
TimeTickstpTotalNumBlockedPackets (1.3.6.1.4.1.5655.4.1.9.1.1.17)
The accumulated number of packets discarded by the traffic processor according to application blocking rules.
Syntax
Unsigned32 (0...4294967295)tpTotalNumBlockedFlows (1.3.6.1.4.1.5655.4.1.9.1.1.18)
The accumulated number of flows discarded by the traffic processor according to application blocking rules.
Syntax
Unsigned32 (0...4294967295)tpTotalNumDiscardedPacketsDueToBwLimit (1.3.6.1.4.1.5655.4.1.9.1.1.19)
The accumulated number of packets discarded by the traffic processor due to subscriber bandwidth limitations.
Syntax
Unsigned32 (0...4294967295)tpTotalNumWredDiscardedPackets (1.3.6.1.4.1.5655.4.1.9.1.1.20)
The accumulated number of packets discarded by the traffic processor due to congestion in the queues.
Syntax
Unsigned32 (0...4294967295)tpTotalNumFragments (1.3.6.1.4.1.5655.4.1.9.1.1.21)
The accumulated number of fragmented packets handled by the traffic processor.
Syntax
Unsigned32 (0...4294967295)tpTotalNumNonIpPackets (1.3.6.1.4.1.5655.4.1.9.1.1.22)
The accumulated number of non IP packets handled by the traffic processor.
Syntax
Unsigned32 (0...4294967295)tpTotalNumIpCrcErrPackets (1.3.6.1.4.1.5655.4.1.9.1.1.23)
The accumulated number of packets with IP CRC error handled by the traffic processor.
Syntax
Unsigned32 (0...4294967295)tpTotalNumIpLengthErrPackets (1.3.6.1.4.1.5655.4.1.9.1.1.24)
The accumulated number of packets with IP length error handled by the traffic processor.
Syntax
Unsigned32 (0...4294967295)tpTotalNumIpBroadcastPackets (1.3.6.1.4.1.5655.4.1.9.1.1.25)
The accumulated number of IP broadcast packets handled by the traffic processor.
Syntax
Unsigned32 (0...4294967295)tpTotalNumTtlErrPackets (1.3.6.1.4.1.5655.4.1.9.1.1.26)
The accumulated number of packets with TTL error handled by the traffic processor.
Syntax
Unsigned32 (0...4294967295)tpTotalNumTcpUdpCrcErrPackets (1.3.6.1.4.1.5655.4.1.9.1.1.27)
The accumulated number of TCP/UDP packets with CRC error handled by the traffic processor.
Syntax
Unsigned32 (0...4294967295)tpClearCountersTime (1.3.6.1.4.1.5655.4.1.9.1.1.28)
The time (in hundredths of a second) since the traffic processor statistics counters were last cleared. Writing a 0 to this object causes the RDR-formatter counters to be cleared.
Syntax
TimeTickstpHandledPacketsRate (1.3.6.1.4.1.5655.4.1.9.1.1.29)
The rate in packets per second of the packets handled by this traffic processor..
Syntax
Unsigned32 (0... 4294967295)tpHandledPacketsRatePeak (1.3.6.1.4.1.5655.4.1.9.1.1.30)
The peak value of tpHandledPacketsRate since the last time it was cleared or the system started.
Syntax
Unsigned32 (0...4294967295)tpHandledPacketsRatePeakTime (1.3.6.1.4.1.5655.4.1.9.1.1.31)
The time (in hundredths of a second) since the tpHandledPacketsRatePeak value occurred.
Syntax
TimeTickstpHandledFlowsRate (1.3.6.1.4.1.5655.4.1.9.1.1.32)
The rate in flows start per second of the flows handled by this traffic processor.
Syntax
Unsigned32 (0...4294967295)tpHandledFlowsRatePeak (1.3.6.1.4.1.5655.4.1.9.1.1.33)
The peak value of tpHandledFlowsRate since the last time it was cleared or the system started.
Syntax
Unsigned32 (0...4294967295)tpHandledFlowsRatePeakTime (1.3.6.1.4.1.5655.4.1.9.1.1.34)
The time (in hundredths of a second) since the tpHandledFlowsRatePeak value occurred.
Syntax
TimeTickstpCpuUtilization (1.3.6.1.4.1.5655.4.1.9.1.1.35)
The current percentage of CPU utilization
Syntax
INTEGER (1..100)tpCpuUtilizationPeak (1.3.6.1.4.1.5655.4.1.9.1.1.36)
The peak value of tpCpuUtilization since the last time it was cleared or the system started.
Syntax
INTEGER (1..100)tpCpuUtilizationPeakTime (1.3.6.1.4.1.5655.4.1.9.1.1.37)
The time (in hundredths of a second) since the pCpuUtilizationPeak value occurred.
Syntax
TimeTickstpFlowsCapacityUtilization (1.3.6.1.4.1.5655.4.1.9.1.1.38)
The percentage of flows capacity utilization.
Syntax
INTEGER (1..100)tpFlowsCapacityUtilizationPeak (1.3.6.1.4.1.5655.4.1.9.1.1.39)
The peak value of tpFlowsCapacityUtilization since the last time it was cleared or the system started.
Syntax
INTEGER (1..100)tpFlowsCapacityUtilizationPeakTime (1.3.6.1.4.1.5655.4.1.9.1.1.40)
The time (in hundredths of a second) since the tpFlowsCapacityUtilizationPeak value occurred.
Syntax
TimeTickstpServiceLoss (1.3.6.1.4.1.5655.4.1.9.1.1.41)
The relative amount of service loss in this traffic processor, in units of 0.001%, since last reboot or last time this counter was cleared.
Syntax
INTEGER (1..100000)pportTable (1.3.6.1.4.1.5655.4.1.10.1)
A list of port entries.
The number of entries is determined by the number of modules in the chassis and the number of ports on each module.
Syntax
Sequence of pportEntrypportEntry (1.3.6.1.4.1.5655.4.1.10.1.1)
Entry containing information for a specified port on a module.
Index
{pportModuleIndex, pportIndex}Syntax
SEQUENCE {pportModuleIndexpportIndexpportTypepportNumTxQueuespportIfIndexpportAdminSpeedpportAdminD uplexpportOperDuplexpportLinkIndexpportOperStatus}pportModuleIndex (1.3.6.1.4.1.5655.4.1.10.1.1.1)
An index value ( pmoduleIndex ) that uniquely identifies the module where the port is located.
Syntax
INTEGER (1..255)pportIndex (1.3.6.1.4.1.5655.4.1.10.1.1.2)
An index value that uniquely identifies the port within the specified module. The value is determined by the location of the port on the module.
Valid entries are 1 to the value of pmoduleNumPorts for this module.
Syntax
INTEGER (1..255)pportType (1.3.6.1.4.1.5655.4.1.10.1.1.3)
The type of physical layer medium dependent interface on the port.
Syntax
INTEGER {1 (other)— none of the following11 (e100BaseTX)— UTP Fast Ethernet (Cat 5)28 (e1000BaseSX)— Short Wave fiber Giga Ethernet }pportNumTxQueues (1.3.6.1.4.1.5655.4.1.10.1.1.4)
The number of transmit queues supported by this port.
Syntax
INTEGER (1..255)pportIfIndex (1.3.6.1.4.1.5655.4.1.10.1.1.5)
The value of the instance of the ifIndex object, defined in MIB-II, for this port.
Syntax
INTEGER (1..255)pportAdminSpeed (1.3.6.1.4.1.5655.4.1.10.1.1.6)
The desired speed of the port. The current operational speed of the port can be determined from ifSpeed.
Syntax
INTEGER {1 (autoNegotiation)— 10000000 (s10000000)— 10 Mbps100000000 (s100000000)— 100 Mbps1000000000 (s1000000000)— 1 Gbps }pportAdminDuplex (1.3.6.1.4.1.5655.4.1.10.1.1.7)
The desired duplex of the port.
Syntax
INTEGER {1 (half)2 (full)4 (auto)}pportOperDuplex (1.3.6.1.4.1.5655.4.1.10.1.1.8)
Indicates whether the port is operating in half-duplex or full-duplex.
Syntax
INTEGER {1 (half)2 (full)}pportLinkIndex (1.3.6.1.4.1.5655.4.1.10.1.1.9)
The linkIndex of the link to which this port belongs.
Value of 0 indicates that this port is not associated with any link.
Value of -1 indicates that this port is associated with multiple links.
Syntax
INTEGER (-1..255)pportOperStatus (1.3.6.1.4.1.5655.4.1.10.1.1.10)
The status of the port. If the port is down, the reason is indicated.
Syntax
INTEGER {1 (other)— none of the following2 (up)— the port is up3 (reflectionForcingDown)— the port is currently forced down due to the link reflection mechanism4 (redundancyForcingDown)— the port is currently forced down due to redundancy reasons5 (otherDown)— the port is down due to other reasons }txQueuesTable (1.3.6.1.4.1.5655.4.1.11.1)
A list of information for each SCE platform transmit queue.
Syntax
Sequence of txQueuesEntrytxQueuesEntry (1.3.6.1.4.1.5655.4.1.11.1.1)
Entry containing information for a specified SCE transmit queue.
Index
{txQueuesModuleIndex, txQueuesPortIndex, txQueuesQueueIndex}Syntax
SEQUENCE {txQueuesModuleIndextxQueuesPortIndextxQueuesQueueIndextxQueuesDescriptiontxQueuesBandwidt htxQueuesUtilizationtxQueuesUtilizationPeaktxQueuesUtilizationPeakTimetxQueuesClearCounter sTime}txQueuesModuleIndex (1.3.6.1.4.1.5655.4.1.11.1.1.1)
An index value ( pmoduleIndex ) that uniquely identifies the module where the queue is located.
Syntax
INTEGER (1..255)txQueuesPortIndex (1.3.6.1.4.1.5655.4.1.11.1.1.2)
An index value that uniquely identifies the port on which the queue is located.
Syntax
INTEGER (1..255)txQueuesQueueIndex (1.3.6.1.4.1.5655.4.1.11.1.1.3)
An index value that uniquely identifies the queue within the specified port. The value is determined by the location of the queue on the port.
Valid entries are 1 to the value of pportNumTxQueues for the specified port.
Syntax
INTEGER (1..255)txQueuesDescription (1.3.6.1.4.1.5655.4.1.11.1.1.4)
Description of the transmit queue.
Syntax
DisplayStringtxQueuesBandwidth (1.3.6.1.4.1.5655.4.1.11.1.1.5)
The bandwidth in kbps configured for this queue.
Syntax
INTEGER (1...1000000)txQueuesUtilization (1.3.6.1.4.1.5655.4.1.11.1.1.6)
The percentage of bandwidth utilization relative to the to the configured rate.
Syntax
INTEGER (0...100)txQueuesUtilizationPeak (1.3.6.1.4.1.5655.4.1.11.1.1.7)
The peak value of txQueuesUtilization since the last time it was cleared or the system started.
Syntax
INTEGER (0...100)txQueuesUtilizationPeakTime (1.3.6.1.4.1.5655.4.1.11.1.1.8)
The time (in hundredths of a second) since the txQueuesUtilizationPeak value occurred.
Syntax
TimeTickstxQueuesClearCountersTime (1.3.6.1.4.1.5655.4.1.11.1.1.9)
The time (in hundredths of a second) since the transmit queues statistics counters were last cleared.
Writing a 0 to this object causes the transmit queues counters to be cleared.
Syntax
TimeTickstxQueuesDroppedBytes (1.3.6.1.4.1.5655.4.1.11.1.1.10)
Number of dropped bytes. Valid only if the system is configured to count dropped bytes per TX queue.
Syntax
Counter64globalControllersTable (1.3.6.1.4.1.5655.4.1.12.1)
A list of information for each global controller.
Syntax
Sequence of globalControllersEntryglobalControllersEntry (1.3.6.1.4.1.5655.4.1.12.1.1)
Entry containing information for a specified global controller.
Index
{globalControllersModuleIndex, globalControllersPortIndex, globalControllersIndex}Syntax
SEQUENCE {globalControllersModuleIndexglobalControllersPortIndexglobalControllersIndexglobalControl lersDescriptionglobalControllersBandwidthglobalControllersUtilizationglobalControllersUtil izationPeakglobalControllersUtilizationPeakTimeglobalControllersClearCountersTimeglobalCon trollersDroppedBytes}globalControllersModuleIndex (1.3.6.1.4.1.5655.4.1.12.1.1.1)
An index value ( pmoduleIndex ) that uniquely identifies the module where the Global Controller is located.
Syntax
INTEGER (1..255)globalControllersPortIndex (1.3.6.1.4.1.5655.4.1.12.1.1.2)
An index value that uniquely identifies the port on which the Global Controller is located.
Syntax
INTEGER (1..255)globalControllersIndex (1.3.6.1.4.1.5655.4.1.12.1.1.3)
An index value that uniquely identifies this Global Controller within the specified port.
Syntax
INTEGER (1..255)globalControllersDescription (1.3.6.1.4.1.5655.4.1.12.1.1.4)
Description of the Global Controller.
Syntax
DisplayStringglobalControllersBandwidth (1.3.6.1.4.1.5655.4.1.12.1.1.5)
The bandwidth in kbps configured for this Global Controller.
Syntax
INTEGER (1...1000000)globalControllersUtilization (1.3.6.1.4.1.5655.4.1.12.1.1.6)
The percentage of bandwidth utilization relative to the configured rate ( globalControllersBandwidth ).
Syntax
INTEGER (0...100)globalControllersUtilizationPeak (1.3.6.1.4.1.5655.4.1.12.1.1.7)
The peak value of bwLimitersUtilization since the last time it was cleared or the system started.
Syntax
INTEGER (0...100)globalControllersUtilizationPeakTime (1.3.6.1.4.1.5655.4.1.12.1.1.8)
The time (in hundredths of a second) since the globalControllersUtilizationPeak value occurred.
Syntax
TimeTicksglobalControllersClearCountersTime (1.3.6.1.4.1.5655.4.1.12.1.1.9)
The time (in hundredths of a second) since the Global Controller statistics counters were last cleared.
Writing a 0 to this object causes the Global Controller counters to be cleared.
Syntax
TimeTicksglobalControllersDroppedBytes (1.3.6.1.4.1.5655.4.1.12.1.1.10)
Number of dropped bytes. Valid only if the system is configured to count dropped bytes per global controller.
Syntax
Counter64appInfoTable (1.3.6.1.4.1.5655.4.1.13.1)
Information identifying the application that is currently installed in the SCE platform.
Syntax
Sequence of appInfoEntryappInfoEntry (1.3.6.1.4.1.5655.4.1.13.1.1)
Entry containing identifying information for the application that is currently installed in the SCE platform.
Index
{moduleIndex}Syntax
SEQUENCE {appNameappDescriptionappVersion}appName (1.3.6.1.4.1.5655.4.1.13.1.1.1)
Name of the application currently installed in the SCE platform. This object returns an empty string if no application is currently installed.
Syntax
DisplayStringappDescription (1.3.6.1.4.1.5655.4.1.13.1.1.2)
Description of the application currently installed in the SCE platform.
Syntax
DisplayStringappVersion (1.3.6.1.4.1.5655.4.1.13.1.1.3)
Version information for the application currently installed in the SCE platform.
Syntax
DisplayStringappPropertiesTable (1.3.6.1.4.1.5655.4.1.13.2)
List of all properties available for the application. The table is cleared when the application is unloaded.
Syntax
Sequence of appPropertiesEntryappPropertiesEntry (1.3.6.1.4.1.5655.4.1.13.2.1)
Entry describing one of the properties available for the application.
Index
{moduleIndex, apIndex}Syntax
SEQUENCE {apIndexapNameapType}apIndex (1.3.6.1.4.1.5655.4.1.13.2.1.1)
An index value that uniquely identifies the property.
Syntax
INTEGER (1..255)apName (1.3.6.1.4.1.5655.4.1.13.2.1.2)
Name of the property.
Syntax
DisplayStringapType (1.3.6.1.4.1.5655.4.1.13.2.1.3)
Property type in respect to: variable type (integer, boolean, string etc), number of elements (scalar or array), and restrictions, if any.
Syntax
DisplayStringappPropertiesValuesTable (1.3.6.1.4.1.5655.4.1.13.3)
The applications properties value table is used to provide specific values for the applications properties.
An entry must be created by setting the entry apvRowStatus object with CreateAndGo (4) before setting the name of the property requested. The property requested must be one of the properties from the appPropertiesTable. To remove an entry set the apvRowStatus object with Destroy (6).
To poll the application property, any of these objects should be polled:
•
•
•
The table is cleared when the application is unloaded.
Syntax
Sequence of appPropertiesValueEntryappPropertiesValueEntry (1.3.6.1.4.1.5655.4.1.13.3.1)
Entry providing information on the value of one of the specified application properties.
Index
{moduleIndex, apvIndex}Syntax
SEQUENCE {apvIndexapvPropertyNameapvRowStatusapvPropertyStringValueapvPropertyUintValueapvPropertyC ounter64Value}apvIndex (1.3.6.1.4.1.5655.4.1.13.3.1.1)
An index value that uniquely identifies the property.
Syntax
INTEGER (1.. 1024)apvPropertyName (1.3.6.1.4.1.5655.4.1.13.3.1.2)
A name that uniquely identifies the application property.
Array-type properties may be accessed one element at a time in C-like format. (For example: x[1], or y[1][2])
Syntax
DisplayStringapvRowStatus (1.3.6.1.4.1.5655.4.1.13.3.1.3)
Controls creation of a table entry.
Syntax
RowStatusapvPropertyStringValue (1.3.6.1.4.1.5655.4.1.13.3.1.4)
The value of the application property in display string format.
Syntax
DisplayString (SIZE 0...128)apvPropertyUintValue (1.3.6.1.4.1.5655.4.1.13.3.1.5)
The value of the application property in Uint format.
If the property cannot be cast to Uint format, getting this object returns zero.
Syntax
Unsigned32 (0...4294967295)apvPropertyCounter64Value (1.3.6.1.4.1.5655.4.1.13.3.1.6)
The value of the application property in Counter64 format.
If the property cannot be cast to Counter64 format, getting this object returns zero.
Syntax
Counter64trafficCountersTable (1.3.6.1.4.1.5655.4.1.14.1)
A list of information for each traffic counter.
Syntax
Sequence of trafficCountersEntrytrafficCountersEntry (1.3.6.1.4.1.5655.4.1.14.1.1)
Entry containing information for a specified traffic counter.
Index
{trafficCounterIndex}Syntax
SEQUENCE {trafficCounterIndextrafficCounterValuetrafficCounterNametrafficCounterType}trafficCounterIndex (1.3.6.1.4.1.5655.4.1.14.1.1.1)
An index value that uniquely identifies the counter.
Syntax
INTEGER (1..255)trafficCounterValue (1.3.6.1.4.1.5655.4.1.14.1.1.2)
The 64 bit counter value.
Syntax
Counter64trafficCounterName (1.3.6.1.4.1.5655.4.1.14.1.1.3)
The name of the counter.
Syntax
DisplayStringtrafficCounterType (1.3.6.1.4.1.5655.4.1.14.1.1.4)
Defines whether the traffic counters counts by packets (3) or by bytes (2).
Syntax
INTEGER {1 (other)— none of the following2 (bytes)— counts by bytes3 (packets)— counts by packets }attackTypeTable (1.3.6.1.4.1.5655.4.1.15.1)
A list of information for defined attack types.
Syntax
Sequence of AttackTypeEntryattackTypeEntry (1.3.6.1.4.1.5655.4.1.15.1.1)
Entry containing information for a specified attack type.
Index
{pmoduleIndex, attackTypeIndex}Syntax
SEQUENCE {attackTypeIndexattackTypeNameattackTypeCurrentNumAttacksattackTypeTotalNumAttacksattackTy peTotalNumFlowsattackTypeTotalNumSeconds}attackTypeIndex (1.3.6.1.4.1.5655.4.1.15.1.1.1)
An index value that uniquely identifies the attack type.
Syntax
INTEGER (1..255)attackTypeName (1.3.6.1.4.1.5655.4.1.15.1.1.2)
The name of the attack type.
Syntax
DisplayStringattackTypeCurrentNumAttacks (1.3.6.1.4.1.5655.4.1.15.1.1.3)
The number of attacks currently detected of this type.
Syntax
Unsigned32 (0...4294967295)attackTypeTotalNumAttacks (1.3.6.1.4.1.5655.4.1.15.1.1.4)
The total number of attacks of this type detected since last clear.
Syntax
Unsigned32 (0...4294967295)attackTypeTotalNumFlows (1.3.6.1.4.1.5655.4.1.15.1.1.5)
The total number of flows in attacks of this type detected since last clear.
Syntax
Counter64attackTypeTotalNumSeconds (1.3.6.1.4.1.5655.4.1.15.1.1.6)
The total duration (in seconds) of attacks of this type detected since last clear.
Syntax
Unsigned32 (0...4294967295)vasServersTable (1.3.6.1.4.1.5655.4.1.16.1)
A list of information for the VAS servers.
Syntax
Sequence of VasServerEntryvasServerEntry (1.3.6.1.4.1.5655.4.1.16.1.1)
Entry containing information for a specified VAS server.
Index
{vasServerIndex}Syntax
SEQUENCE {vasServerIndexvasServerIdvasServerAdminStatusvasServerOperStatus}vasServerIndex (1.3.6.1.4.1.5655.4.1.16.1.1.1)
An index value that uniquely identifies the VAS server.
Syntax
Unsigned32 (0...4294967295)vasServerId (1.3.6.1.4.1.5655.4.1.16.1.1.2)
The VAS server ID number in the system.
Syntax
Unsigned32 (0...4294967295)vasServerAdminStatus (1.3.6.1.4.1.5655.4.1.16.1.1.3)
The administrative status of the VAS server.
Syntax
INTEGER {1 (other)2 (up)3 (down)}vasServerOperStatus (1.3.6.1.4.1.5655.4.1.16.1.1.4)
The operational status of the VAS server.
Syntax
INTEGER {1 (other)2 (up)3 (down)}mplsVpnSoftwareCountersTable (1.3.6.1.4.1.5655.4.1.17.1)
A list of information on various system software counters related to MPLS/VPN auto-learning.
Syntax
Sequence of mplsVpnSoftwareCountersEntrymplsVpnSoftwareCountersEntry (1.3.6.1.4.1.5655.4.1.17.1.1)
Entry containing information regarding MPLS/VPN auto-learning.
Syntax
SEQUENCE {mplsVpnMaxHWMappingsmplsVpnCurrentHWMappings}mplsVpnMaxHWMappings (1.3.6.1.4.1.5655.4.1.17.1.1.1)
The maximum number of hardware mappings permitted.
Syntax
INTEGER (1..1000000)mplsVpnCurrentHWMappings (1.3.6.1.4.1.5655.4.1.17.1.1.2)
The current number of hardware mappings in the system.
Syntax
INTEGER (1..1000000)Supported Standards
The SCE platform supports the SNMP related standards listed in the following table.
Posted: Wed May 30 08:46:09 PDT 2007
All contents are Copyright © 1992--2007 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
