B-31
Cisco SCE 2000 and SCE 1000 Software Configuration Guide
OL-7827-12
Appendix B Proprietary MIB Reference
pcubeWorkgroup (1.3.6.1.4.1.5655.4)
• attackTypeTotalNumFlows (1.3.6.1.4.1.5655.4.1.15.1.1.5), page B-90
• attackTypeTotalNumSeconds (1.3.6.1.4.1.5655.4.1.15.1.1.6), page B-90
• vasServersTable (1.3.6.1.4.1.5655.4.1.16.1), page B-91
• vasServerEntry (1.3.6.1.4.1.5655.4.1.16.1.1), page B-91
• vasServerIndex (1.3.6.1.4.1.5655.4.1.16.1.1.1), page B-91
• vasServerId (1.3.6.1.4.1.5655.4.1.16.1.1.2), page B-91
• vasServerAdminStatus (1.3.6.1.4.1.5655.4.1.16.1.1.3), page B-92
• vasServerOperStatus (1.3.6.1.4.1.5655.4.1.16.1.1.4), page B-92
• mplsVpnSoftwareCountersTable (1.3.6.1.4.1.5655.4.1.17.1), page B-92
• mplsVpnSoftwareCountersEntry (1.3.6.1.4.1.5655.4.1.17.1.1), page B-92
• mplsVpnMaxHWMappings (1.3.6.1.4.1.5655.4.1.17.1.1.1), page B-93
• mplsVpnCurrentHWMappings (1.3.6.1.4.1.5655.4.1.17.1.1.2), page B-93
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
}
Access RO
Access RO