STARENT-MIB
AI MIB Summary
The STARENT-MIB module provides SNMP management and monitoring capabilities for Cisco ASR 5000 and ASR 5500 multimedia core platforms, specifically exposing metrics related to 2G/3G/4G and WiFi subscriber sessions, inline service states, and carrier-class high-availability status.
Cisco Systems ASR 5xxx series of multimedia core platforms (ASR 5000, ASR 5500) Designed exclusively for mobile and fixed mobile converged applications, Cisco's ASR 5xxx series products provide a high-performance, highly intelligent platform ideally suited for development in mobile operator networks to fulfill key multimedia core networking functions. The platform features 2G/3G/4G and WiFi multi-service access indepedent capabilities coupled with a carrier class high-availability design. Harnessing subscriber awareness with an abundant supply of distributed processing resources, the ASR 5xxx series offers a variety of high touch Inline Services to enable service providers to monetize the value of the network while enriching the overall subscriber experience.
Main OID:
starentMIB.1.3.6.1.4.1.8164
2183
Objects
Active
Status
7
Dependencies
Imported Objects
Objects
2183 total| Object Name |
|---|
starentMIBCisco Systems ASR 5xxx series of multimedia core platforms (ASR 5000, ASR 5500) Designed exclusively for mobile and fixed mobile converged applications, Cisco's ASR 5xxx series products provide a high-performance, highly intelligent platform ideally suited for development in mobile operator networks to fulfill key multimedia core networking functions. The platform features 2G/3G/4G and WiFi multi-service access indepedent capabilities coupled with a carrier class high-availability design. Harnessing subscriber awareness with an abundant supply of distributed processing resources, the ASR 5xxx series offers a variety of high touch Inline Services to enable service providers to monetize the value of the network while enriching the overall subscriber experience. MODULE-IDENTITY .1.3.6.1.4.1.8164 |
starentMIBObjects OBJECT IDENTIFIER .1.3.6.1.4.1.8164.1 |
starentChassis OBJECT IDENTIFIER .1.3.6.1.4.1.8164.1.1 |
starChassisCriticalCOThe current state of the Critical Central Office (CO) relayro StarRelayState .1.3.6.1.4.1.8164.1.1.1 |
starChassisMajorCOThe current state of the Major Central Office (CO) relayro StarRelayState .1.3.6.1.4.1.8164.1.1.2 |
starChassisMinorCOThe current state of the Minor Central Office (CO) relayro StarRelayState .1.3.6.1.4.1.8164.1.1.3 |
starChassisActionTrigger to perform certain system-wide operations. noaction(1) performs no operation. It is the normal value received when this attribute is read. aco(2) triggers the Alarm Cut-Off, which shuts off all of the Central Office (CO) audible/visual relays. reset(3) triggers a system-wide restart. It will completely disrupt service on the device.rw Enumeration .1.3.6.1.4.1.8164.1.1.5 |
starTimeTicksTime ticks since the Epochro Unsigned32 .1.3.6.1.4.1.8164.1.1.6 |
starChassisAudibleAlarmThe current state of the chassis Audible Alarmro StarRelayState .1.3.6.1.4.1.8164.1.1.7 |
starChassisUTCTimeThe current time on the chassis, in UTC formatro DateAndTime (SNMPv2-TC) .1.3.6.1.4.1.8164.1.1.8 |
starChassisLocalTimeThe current time on the chassis, converted to the local timezonero DateAndTime (SNMPv2-TC) .1.3.6.1.4.1.8164.1.1.9 |
starChassisTypeThe type of physical chassisro Enumeration .1.3.6.1.4.1.8164.1.1.10 |
starChassisDescriptionA brief description of the chassisro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.1.11 |
starChassisSWRevisionThe software revision running on the chassisro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.1.12 |
starChassisPeakCpuUsagePercentage of the system level peak cpu usage.starChassisPeakCpuUsage is the percentage value times 100; for example,2.3% would be represented as 230ro Integer32 .1.3.6.1.4.1.8164.1.1.13 |
starChassisPeakMemoryUsageThe system level peak memory usage, in kilobytes, rounded down (i.e. 1023 bytes = 0 kilobytes)ro Integer32 .1.3.6.1.4.1.8164.1.1.14 |
starentSlots OBJECT IDENTIFIER .1.3.6.1.4.1.8164.1.2 |
starSlotTableA table containing information on all of the slots SEQUENCE OF StarSlotEntry .1.3.6.1.4.1.8164.1.2.1 |
starSlotEntryInformation about a particular slot StarSlotEntry .1.3.6.1.4.1.8164.1.2.1.1 |
starSlotNumThe slot numberro Integer32 .1.3.6.1.4.1.8164.1.2.1.1.1 |
starSlotTypeThe type of the slot.ro StarentSlotType .1.3.6.1.4.1.8164.1.2.1.1.2 |
starCardTypeThe type of the card which is plugged into a slotro StarentCardType .1.3.6.1.4.1.8164.1.2.1.1.3 |
starCardOperStateThe current operational state of the cardro Enumeration .1.3.6.1.4.1.8164.1.2.1.1.4 |
starCardAdminStateThe administrative state of the cardro Enumeration .1.3.6.1.4.1.8164.1.2.1.1.5 |
starCardRevisionThe revision number of the card that is physically present in this slotro StarentVersionNum .1.3.6.1.4.1.8164.1.2.1.1.6 |
starCardLastStateChangeThe time when the last state change occurred for this row. A manager could poll this variable to determine if information has changed.ro DateAndTime (SNMPv2-TC) .1.3.6.1.4.1.8164.1.2.1.1.7 |
starCardModeThe desired mode of the card. This field is applicable only to slots which can contain PAC/PSC and TAC cards. The active(4) value is obsolete and has been replaces with activepac(5) and activetac(6)ro Enumeration .1.3.6.1.4.1.8164.1.2.1.1.8 |
starCardPacStandbyPriorityro Gauge32 .1.3.6.1.4.1.8164.1.2.1.1.9 |
starCardHaltIssuedOnly applicable to SPC cardsro Enumeration .1.3.6.1.4.1.8164.1.2.1.1.10 |
starCardLockIdentifies if the card lock is currently engaged. A value of locked(2) means that the lock is engaged, and thus the card could not be removed from the chassis. A value of unlocked(3) means that the lock is not engaged, and an operator could remove the card from the chassis. A value of unknown(1) should represent that there is no card physically in the slot.ro Enumeration .1.3.6.1.4.1.8164.1.2.1.1.11 |
starCardRebootPendingIdentifies if a reboot operation is currently pending for this card.ro Enumeration .1.3.6.1.4.1.8164.1.2.1.1.12 |
starCardUsableIdentifies if the card is currently usable.ro Enumeration .1.3.6.1.4.1.8164.1.2.1.1.13 |
starCardSinglePOFIdentifies if this card represents a single point of failure (POF). A value of no(1) indicates that this card is supported by a redundant card which can take over in the event of a failure. A value of yes(2) indicates that this card does not have a redundant partner, and that a failure of this card could result in service interruption.ro Enumeration .1.3.6.1.4.1.8164.1.2.1.1.14 |
starCardAttachmentIdentifies if the card is currently attached to another card (a PAC/PSC attached to a line card, or visa versa, for examplero Enumeration .1.3.6.1.4.1.8164.1.2.1.1.15 |
starCardTemperatureThe temperature, in degrees Celcius, as measured on the card. A value of 0 indicates that the temperature cannot be read, or that the card is not present. The maximum measurable temperature is 70 Cro Gauge32 UNITS "degrees Celcius" .1.3.6.1.4.1.8164.1.2.1.1.16 |
starSlotVoltage1dot5The current voltage, in millivolts, of the nominal 1.5V power supply. The working range for this card is the range defined by variables starSlotVoltage1dot5LowThresh and starSlotVoltage1dot5HighThresh. A value of 0 indicates that this voltage level is not present on this card, or that the card is not present. This attribute is obsolete.roobsolete Gauge32 UNITS "millivolts" .1.3.6.1.4.1.8164.1.2.1.1.20 |
starSlotVoltage1dot5LowThreshThe voltage level, in millivolts, which is the lowest allowable value for the nominal 1.5V power supply. A value of 0 indicates that there is no card present. This attribute is obsolete.roobsolete Gauge32 UNITS "millivolts" .1.3.6.1.4.1.8164.1.2.1.1.21 |
starSlotVoltage1dot5HighThreshThe voltage level, in millivolts, which is the highest allowable value for the nominal 1.5V power supply. A value of 0 indicates that there is no card present. This attribute is obsolete.roobsolete Gauge32 UNITS "millivolts" .1.3.6.1.4.1.8164.1.2.1.1.22 |
starSlotVoltage1dot8The current voltage, in millivolts, of the nominal 1.8V power supply. The working range for this card is the range defined by variables starSlotVoltage1dot8LowThresh and starSlotVoltage1dot8HighThresh. A value of 0 indicates that this voltage level is not present on this card, or that the card is not present. This attribute is obsolete.roobsolete Gauge32 UNITS "millivolts" .1.3.6.1.4.1.8164.1.2.1.1.23 |
starSlotVoltage1dot8LowThreshThe voltage level, in millivolts, which is the lowest allowable value for the nominal 1.8V power supply. A value of 0 indicates that there is no card present. This attribute is obsolete.roobsolete Gauge32 UNITS "millivolts" .1.3.6.1.4.1.8164.1.2.1.1.24 |
starSlotVoltage1dot8HighThreshThe voltage level, in millivolts, which is the highest allowable value for the nominal 1.8V power supply. A value of 0 indicates that there is no card present. This attribute is obsolete.roobsolete Gauge32 UNITS "millivolts" .1.3.6.1.4.1.8164.1.2.1.1.25 |
starSlotVoltage2dot5The current voltage, in millivolts, of the nominal 2.5V power supply. The working range for this card is the range defined by variables starSlotVoltage2dot5LowThresh and starSlotVoltage2dot5HighThresh. A value of 0 indicates that the voltage cannot be read, or that the card is not present. This attribute is obsolete.roobsolete Gauge32 UNITS "millivolts" .1.3.6.1.4.1.8164.1.2.1.1.26 |
starSlotVoltage2dot5LowThreshThe voltage level, in millivolts, which is the lowest allowable value for the nominal 2.5V power supply. A value of 0 indicates that there is no card present. This attribute is obsolete.roobsolete Gauge32 UNITS "millivolts" .1.3.6.1.4.1.8164.1.2.1.1.27 |
starSlotVoltage2dot5HighThreshThe voltage level, in millivolts, which is the highest allowable value for the nominal 2.5V power supply. A value of 0 indicates that there is no card present. This attribute is obsolete.roobsolete Gauge32 UNITS "millivolts" .1.3.6.1.4.1.8164.1.2.1.1.28 |
starSlotVoltage3dot3The current voltage, in millivolts, of the nominal 3.3V power supply. The working range for this card is the range defined by variables starSlotVoltage3dot3LowThresh and starSlotVoltage3dot3HighThresh. A value of 0 indicates that the voltage cannot be read, or that the card is not present. This attribute is obsolete.roobsolete Gauge32 UNITS "millivolts" .1.3.6.1.4.1.8164.1.2.1.1.29 |
starSlotVoltage3dot3LowThreshThe voltage level, in millivolts, which is the lowest allowable value for the nominal 3.3V power supply. A value of 0 indicates that there is no card present. This attribute is obsolete.roobsolete Gauge32 UNITS "millivolts" .1.3.6.1.4.1.8164.1.2.1.1.30 |
starSlotVoltage3dot3HighThreshThe voltage level, in millivolts, which is the highest allowable value for the nominal 3.3V power supply. A value of 0 indicates that there is no card present. This attribute is obsolete.roobsolete Gauge32 UNITS "millivolts" .1.3.6.1.4.1.8164.1.2.1.1.31 |
starSlotVoltage5dot0The current voltage, in millivolts, of the nominal 5.0V power supply. The working range for this card is the range defined by variables starSlotVoltage5dot0LowThresh and starSlotVoltage5dot0HighThresh. A value of 0 indicates that the voltage cannot be read, or that the card is not present. This attribute is obsolete.roobsolete Gauge32 UNITS "millivolts" .1.3.6.1.4.1.8164.1.2.1.1.32 |
starSlotVoltage5dot0LowThreshThe voltage level, in millivolts, which is the lowest allowable value for the nominal 5.0V power supply. A value of 0 indicates that there is no card present. This attribute is obsolete.roobsolete Gauge32 UNITS "millivolts" .1.3.6.1.4.1.8164.1.2.1.1.33 |
starSlotVoltage5dot0HighThreshThe voltage level, in millivolts, which is the highest allowable value for the nominal 5.0V power supply. A value of 0 indicates that there is no card present. This attribute is obsolete.roobsolete Gauge32 UNITS "millivolts" .1.3.6.1.4.1.8164.1.2.1.1.34 |
starSlotNumPortsNumber of data ports on this card. This value will be 0 for cards that do not contain ports, such as SPC/SMC/PAC/PSC/TAC cards, or for slots which do not contain a card. This attribute is obsolete.ro Gauge32 .1.3.6.1.4.1.8164.1.2.1.1.35 |
starSlotActionTrigger to perform certain slot operations. noaction(1) performs no operation. It is the normal value received when this attribute is read. reset(2) causes the slot to be resetrw Enumeration .1.3.6.1.4.1.8164.1.2.1.1.36 |
starSlotVoltageStateThe state of the voltage supplies on the card. A value of unknown(0) means that the state cannot be identified; normal(1) represents a properly functioning card; outofrange(2) indicates that one or more voltage sources are not within their specified operating range.ro Enumeration .1.3.6.1.4.1.8164.1.2.1.1.37 |
starSlotNumCPUThe number of general-purpose CPUs on this cardro Integer32 .1.3.6.1.4.1.8164.1.2.1.1.38 |
starSlotPartNumberThe part number of this cardro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.2.1.1.39 |
starSlotPartRevisionThe revision number of this cardro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.2.1.1.40 |
starSlotSerialNumberThe serial number of this cardro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.2.1.1.41 |
starSlotCLEICodeThe CLEI code of this cardro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.2.1.1.42 |
starSlotCiscoModelNameCisco-defined Product Identifier (PID). The PID is an alphanumeric identifier used to identify specific Cisco product hardware, and may be up to 18 characters in length. starSlotCiscoModelName will be blank (zero characters) if no PID is available.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.2.1.1.43 |
starSlotCiscoHardwareRevCisco-defined Version Identifier (VID). The VID is used to track the version of the Customer-Orderable Cisco Product Identifier (PID) [starSlotCiscoModelName]. The data convention for VID is 'V' followed by a two digit number. VID numbering typically begins at 'V01' but can be initiated at a higher value. starSlotCiscoHardwareRev will be blank (zero characters) if no VID is available.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.2.1.1.44 |
starSlotCiscoSerialNumberCisco-defined Serial Number (SN). The SN is an 11 character identifier used in conjunction with the Cisco Product Identifier (PID) [starSlotCiscoModelName] to identify a unique product or Field Replaceable Unit (FRU) of a product. starSlotCiscoSerialNumber will be blank (zero characters) if no VID is available.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.2.1.1.45 |
starDeviceNumThe device numberro Integer32 .1.3.6.1.4.1.8164.1.2.1.1.46 |
starSerdesNumThe serdes lane index numberro Integer32 .1.3.6.1.4.1.8164.1.2.1.1.47 |
starentSlotMapping OBJECT IDENTIFIER .1.3.6.1.4.1.8164.1.3 |
starSlotMappingTableA table identifying all of the slot mappings. This table is applicable only to starChassisType ASR5000 platform. SEQUENCE OF StarSlotMappingEntry .1.3.6.1.4.1.8164.1.3.1 |
starSlotMappingEntryInformation about a particular slot mapping StarSlotMappingEntry .1.3.6.1.4.1.8164.1.3.1.1 |
starSlotMappingNumThe slot number. This always represents a slot in the back of the chassis. Integer32 .1.3.6.1.4.1.8164.1.3.1.1.1 |
starSlotMappingTypeThe type of the slot mapping. The value none(1) represents that there is no mapping, which typically represents that there is no card present in this slot.ro Enumeration .1.3.6.1.4.1.8164.1.3.1.1.2 |
starSlotMappingRCCNumIdentifies which RCC card is responsible for this mapping. This value is only valid if the value of starSlotMappingType is rcc(3).ro Integer32 .1.3.6.1.4.1.8164.1.3.1.1.3 |
starSlotMappingToSlotThe slot number this slot is mapped to. This always represents a slot in the front of the chassisro Integer32 .1.3.6.1.4.1.8164.1.3.1.1.4 |
starentFans OBJECT IDENTIFIER .1.3.6.1.4.1.8164.1.4 |
starFanTableA table containing information on all of the fan controllers SEQUENCE OF StarFanEntry .1.3.6.1.4.1.8164.1.4.1 |
starFanEntryInformation about a particular fan controller StarFanEntry .1.3.6.1.4.1.8164.1.4.1.1 |
starFanNumThe fan controller numberro Integer32 .1.3.6.1.4.1.8164.1.4.1.1.1 |
starFanLocationThe physical location of the fan controllerro Enumeration .1.3.6.1.4.1.8164.1.4.1.1.2 |
starFanStatusA bitmask representing the status of the fan tray. 0x01 All Fans Good 0x02 Multiple Fans Bad 0x04 Single Fan Bad 0x08 HB Error 0x10 COM A Error 0x20 COM B Error 0x40 COMM Error 0x80 Not Present 0x100 Present 0x200 Filter Clogged 0x400 Unknown A normal, properly functioning fan tray would show 0x101 (257 decimal), meaning it is present (0x100) and all fans are working (0x1)ro Integer32 .1.3.6.1.4.1.8164.1.4.1.1.3 |
starFanSpeedThe speed of the fans controlled by this fan controller. The values represent the percentage that the speed is running relative to the maximum possible speed, speed100(12)ro Enumeration .1.3.6.1.4.1.8164.1.4.1.1.4 |
starentLogs OBJECT IDENTIFIER .1.3.6.1.4.1.8164.1.5 |
starLogTableA table containing information about all of the system logs SEQUENCE OF StarLogEntry .1.3.6.1.4.1.8164.1.5.1 |
starLogEntryInformation about a particular system log StarLogEntry .1.3.6.1.4.1.8164.1.5.1.1 |
starLogNameThe name of the system logro StarShortName .1.3.6.1.4.1.8164.1.5.1.1.1 |
starLogCurSizeThe size, in bytes, of this logro Gauge32 .1.3.6.1.4.1.8164.1.5.1.1.2 |
starLogMaxSizeThe maximum size, in bytes, of this logro Gauge32 .1.3.6.1.4.1.8164.1.5.1.1.3 |
starLogTextFor use in LogMsg trapro OCTET STRING .1.3.6.1.4.1.8164.1.5.1.1.4 |
starentAlertMan OBJECT IDENTIFIER .1.3.6.1.4.1.8164.1.8 |
starentFeedback OBJECT IDENTIFIER .1.3.6.1.4.1.8164.1.8.1 |
starMaxAlertsPerTimeThe maximum number of SNMP Traps which will be sent within the time period specified by starWindowTimero Unsigned32 .1.3.6.1.4.1.8164.1.8.1.1 |
starWindowTimeThe amount of time within which no more than starMaxAlertsPerTime SNMP Traps will be sent.ro Unsigned32 UNITS "seconds" .1.3.6.1.4.1.8164.1.8.1.2 |
starAlertSendingEnabledShows if SNMP traps are currently enabled or disabled. Traps are disabled when more than starMaxAlertsPerTime traps are sent within the starWindowTime time period. A value of true(1) indicates that traps will still be sent. A value of false(2) indicates that traps are no longer being generatedro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.8164.1.8.1.3 |
starentPolledLog OBJECT IDENTIFIER .1.3.6.1.4.1.8164.1.8.2 |
starentPower OBJECT IDENTIFIER .1.3.6.1.4.1.8164.1.9 |
starPowerTableA table containing information about all power filters SEQUENCE OF StarPowerEntry .1.3.6.1.4.1.8164.1.9.1 |
starPowerEntryInformation about a particular power filter StarPowerEntry .1.3.6.1.4.1.8164.1.9.1.1 |
starPowerNumberThe identifying number for this power filter.ro Enumeration .1.3.6.1.4.1.8164.1.9.1.1.1 |
starPowerStateThe state of the power filter. The value active(1) means that the power filter is present and operational. The value failed(2) means that the power filter is present, but not operational. The value not-present(3) means that the power filter is not physically present in the system.ro Enumeration .1.3.6.1.4.1.8164.1.9.1.1.2 |
starentCPU OBJECT IDENTIFIER .1.3.6.1.4.1.8164.1.10 |
starCPUTableA table containing information about all CPUs SEQUENCE OF StarCPUEntry .1.3.6.1.4.1.8164.1.10.1 |
starCPUEntryInformation about a particular CPU StarCPUEntry .1.3.6.1.4.1.8164.1.10.1.1 |
starCPUSlotThe slot number of the card holding this CPUro Integer32 .1.3.6.1.4.1.8164.1.10.1.1.1 |
starCPUNumberThe CPU number within this card. Numbers begin at 0.ro Integer32 .1.3.6.1.4.1.8164.1.10.1.1.2 |
starCPUUserPercentage of the CPU spent running user processes. starCPUUser is the percentage value times 100; for example, 2.3% would be represented as 230.ro Gauge32 .1.3.6.1.4.1.8164.1.10.1.1.3 |
starCPUSystemPercentage of the CPU spent running system processes. starCPUSystem is the percentage value times 100; for example, 2.3% would be represented as 230.ro Gauge32 .1.3.6.1.4.1.8164.1.10.1.1.4 |
starCPUIdlePercentage of the CPU spent idle. starCPUIdle is the percentage value times 100; for example, 2.3% would be represented as 230.ro Gauge32 .1.3.6.1.4.1.8164.1.10.1.1.6 |
starCPUIOPercentage of the CPU spent running io processes. starCPUIo is the percentage value times 100; for example, 2.3% would be represented as 230.ro Gauge32 .1.3.6.1.4.1.8164.1.10.1.1.7 |
starCPUIRQPercentage of the CPU spent running irq processes. starCPUIrq is the percentage value times 100; for example, 2.3% would be represented as 230.ro Gauge32 .1.3.6.1.4.1.8164.1.10.1.1.8 |
starCPULoad1MinThe average CPU load over the last minute. The CPU load is defined to be the number of processes who are ready to run. starCPULoad1Min is the average number of processes times 100; for example, 2.45 would be represented as 245.ro Gauge32 .1.3.6.1.4.1.8164.1.10.1.1.11 |
starCPULoad5MinThe average CPU load over the last 5 minutes. The CPU load is defined to be the number of processes who are ready to run. starCPULoad5Min is the average number of processes times 100; for example, 2.45 would be represented as 245.ro Gauge32 .1.3.6.1.4.1.8164.1.10.1.1.12 |
starCPULoad15MinThe average CPU load over the last 15 minutes. The CPU load is defined to be the number of processes who are ready to run. starCPULoad15Min is the average number of processes times 100; for example, 2.45 would be represented as 245.ro Gauge32 .1.3.6.1.4.1.8164.1.10.1.1.13 |
starCPUMemTotalThe total amount of memory dedicated to this CPU, in kilobytesro Integer32 .1.3.6.1.4.1.8164.1.10.1.1.14 |
starCPUMemUsedThe total amount of memory consumed by this CPU, in kilobytesro Gauge32 .1.3.6.1.4.1.8164.1.10.1.1.15 |
starCPUNumProcessesThe total number of processes which exist on this CPUro Gauge32 .1.3.6.1.4.1.8164.1.10.1.1.16 |
starCPUMemCachedThe total amount of memory consumed by the (reusable) memory cache on this CPU, in kilobytesro Gauge32 .1.3.6.1.4.1.8164.1.10.1.1.17 |
starentNPUMgr OBJECT IDENTIFIER .1.3.6.1.4.1.8164.1.11 |
starNPUMgrTableA table containing information about all NPU Managers SEQUENCE OF StarNPUMgrEntry .1.3.6.1.4.1.8164.1.11.1 |
starNPUMgrEntryInformation about a particular NPU Manager StarNPUMgrEntry .1.3.6.1.4.1.8164.1.11.1.1 |
starNPUMgrNumberThe identity of this NPUro Integer32 .1.3.6.1.4.1.8164.1.11.1.1.1 |
starentSessInP OBJECT IDENTIFIER .1.3.6.1.4.1.8164.1.12 |
starSessInProgCallsThe number of sessions current in progressro Gauge32 .1.3.6.1.4.1.8164.1.12.1 |
starSessInProgActiveCallsThe number of sessions with active callsro Gauge32 .1.3.6.1.4.1.8164.1.12.2 |
starSessInProgDormantCallsThe number of sessions assocated with dormant callsro Gauge32 .1.3.6.1.4.1.8164.1.12.3 |
starSessInProgArrivedThe number of sessions in the arrived statero Gauge32 .1.3.6.1.4.1.8164.1.12.4 |
starSessInProgLCPNegThe number of sessions in the link control protocol negotiation statero Gauge32 .1.3.6.1.4.1.8164.1.12.5 |
starSessInProgLCPUpThe number of sessions in the link control protocol up statero Gauge32 .1.3.6.1.4.1.8164.1.12.6 |
starSessInProgAuthenticatingThe number of sessions in the authenticating statero Gauge32 .1.3.6.1.4.1.8164.1.12.7 |
starSessInProgAuthenticatedThe number of sessions in the authenticated statero Gauge32 .1.3.6.1.4.1.8164.1.12.8 |
starSessInProgIPCPUpThe number of sessions in the IP control protocol up statero Gauge32 .1.3.6.1.4.1.8164.1.12.9 |
starSessInProgSIPConnThe number of sessions in the Simple IP connected statero Gauge32 .1.3.6.1.4.1.8164.1.12.10 |
starSessInProgMIPConnThe number of sessions in the Mobile IP connected statero Gauge32 .1.3.6.1.4.1.8164.1.12.11 |
starSessInProgDiscThe number of sessions in the disconnecting statero Gauge32 .1.3.6.1.4.1.8164.1.12.12 |
starentSessMgr OBJECT IDENTIFIER .1.3.6.1.4.1.8164.1.13 |
starSessMgrCountThe total number of session manager instancesro Gauge32 .1.3.6.1.4.1.8164.1.13.1 |
starSessTtlArrivedThe total number of requested sessionsro Gauge32 .1.3.6.1.4.1.8164.1.13.2 |
starSessTtlRejectedThe total number of rejected sessionsro Gauge32 .1.3.6.1.4.1.8164.1.13.3 |
starSessTtlConnectedThe total number of sessions which were connectedro Gauge32 .1.3.6.1.4.1.8164.1.13.4 |
starSessTtlAuthSuccThe total number of sessions where authentication was successfulro Gauge32 .1.3.6.1.4.1.8164.1.13.5 |
starSessTtlAuthFailThe total number of sessions which failed authenticationro Gauge32 .1.3.6.1.4.1.8164.1.13.6 |
starSessTtlLCPUpThe total number of sessions in the link control protocol up statero Gauge32 .1.3.6.1.4.1.8164.1.13.7 |
starSessTtlIPCPUpThe total number of IP control protocol up statero Gauge32 .1.3.6.1.4.1.8164.1.13.8 |
starSessTtlSrcViolThe total number of sessions which had an invalid sourcero Gauge32 .1.3.6.1.4.1.8164.1.13.9 |
starSessTtlKeepFailThe total number of sessions which had a keep alive failurero Gauge32 .1.3.6.1.4.1.8164.1.13.10 |
starSessTtlOctForwardedThe total number of octets forwarded (data + control)rodeprecated Counter32 UNITS "Megabytes" .1.3.6.1.4.1.8164.1.13.11 |
starSessTtlRPRegAcceptThe total number of Initial RRQ Acceptedro Counter32 .1.3.6.1.4.1.8164.1.13.12 |
starSessTtlRPRegAcceptInterPDSNThe total number of Inter PDSN Handoff RRQ Acceptedro Counter32 .1.3.6.1.4.1.8164.1.13.13 |
starSessCurrPPPSessionsThe current number of PPP sessionsro Gauge32 .1.3.6.1.4.1.8164.1.13.14 |
starSessTtlTxBytesThe total number of bytes transmitted from mobilesrodeprecated Counter32 UNITS "Megabytes" .1.3.6.1.4.1.8164.1.13.15 |
starSessTtlRxBytesThe total number of bytes received by mobilesrodeprecated Counter32 UNITS "Megabytes" .1.3.6.1.4.1.8164.1.13.16 |
starSessTtlSIPTxBytesThe total number of bytes transmitted from mobiles using SIProdeprecated Counter32 UNITS "Megabytes" .1.3.6.1.4.1.8164.1.13.17 |
starSessTtlSIPRxBytesThe total number of bytes received by mobiles using SIProdeprecated Counter32 UNITS "Megabytes" .1.3.6.1.4.1.8164.1.13.18 |
starSessTtlMIPTxBytesThe total number of bytes transmitted from mobiles using MIProdeprecated Counter32 UNITS "Megabytes" .1.3.6.1.4.1.8164.1.13.19 |
starSessTtlMIPRxBytesThe total number of bytes received by mobiles using MIProdeprecated Counter32 UNITS "Megabytes" .1.3.6.1.4.1.8164.1.13.20 |
starSessTtlOctForwardedGBThe total number of octets forwarded (data + control)rodeprecated Counter32 UNITS "Gigabytes" .1.3.6.1.4.1.8164.1.13.21 |
starSessTtlOctForwardedRev1The total number of octets forwarded (data + control). This object deprecates the old starSessTtlOctForwarded object.ro Counter64 UNITS "Megabytes" .1.3.6.1.4.1.8164.1.13.22 |
starSessTtlTxBytesRev1The total number of bytes transmitted from mobiles. This object deprecates the old starSessTtlTxBytes object.ro Counter64 UNITS "Megabytes" .1.3.6.1.4.1.8164.1.13.23 |
starSessTtlRxBytesRev1The total number of bytes received by mobiles. This object deprecates the old starSessTtlRxBytes object.ro Counter64 UNITS "Megabytes" .1.3.6.1.4.1.8164.1.13.24 |
starSessTtlSIPTxBytesRev1The total number of bytes transmitted from mobiles using SIP. This object deprecates the old starSessTtlSIPTxBytes object.ro Counter64 UNITS "Megabytes" .1.3.6.1.4.1.8164.1.13.25 |
starSessTtlSIPRxBytesRev1The total number of bytes received by mobiles using SIP. This object deprecates the old starSessTtlSIPRxBytes object.ro Counter64 UNITS "Megabytes" .1.3.6.1.4.1.8164.1.13.26 |
starSessTtlMIPTxBytesRev1The total number of bytes transmitted from mobiles using MIP. This object deprecates the old starSessTtlMIPTxBytes object.ro Counter64 UNITS "Megabytes" .1.3.6.1.4.1.8164.1.13.27 |
starSessTtlMIPRxBytesRev1The total number of bytes received by mobiles using MIP. This object deprecates the old starSessTtlMIPRxBytes object.ro Counter64 UNITS "Megabytes" .1.3.6.1.4.1.8164.1.13.28 |
starSessTtlOctForwardedGBRev1The total number of octets forwarded (data + control). This object deprecates the old starSessTtlOctForwardedGB object.ro Counter64 UNITS "Gigabytes" .1.3.6.1.4.1.8164.1.13.29 |
starentAAAMgr OBJECT IDENTIFIER .1.3.6.1.4.1.8164.1.14 |
starAAAMgrCountThe total number of AAA manager instancesro Gauge32 .1.3.6.1.4.1.8164.1.14.1 |
starAAATtlRequestsThe total number of AAA requestsro Counter32 .1.3.6.1.4.1.8164.1.14.2 |
starAAATtlAuthRequestsThe total number of AAA authentication requestsro Counter32 .1.3.6.1.4.1.8164.1.14.3 |
starAAATtlAcctRequestsThe total number of AAA accounting requestsro Counter32 .1.3.6.1.4.1.8164.1.14.4 |
starAAACurRequestsThe current number of AAA requestsro Gauge32 .1.3.6.1.4.1.8164.1.14.5 |
starAAACurAuthRequestsThe current number of AAA authentication requestsro Gauge32 .1.3.6.1.4.1.8164.1.14.6 |
starAAACurAcctRequestsThe current number of AAA accounting requestsro Gauge32 .1.3.6.1.4.1.8164.1.14.7 |
starAAATtlAcctSessThe total number of AAA accounting sessionsro Counter32 .1.3.6.1.4.1.8164.1.14.8 |
starAAACurAcctSessThe current number of AAA accounting sessionsro Gauge32 .1.3.6.1.4.1.8164.1.14.9 |
starAAATtlAuthSuccessThe total number of AAA authentication successesro Counter32 .1.3.6.1.4.1.8164.1.14.10 |
starAAATtlAuthFailureThe total number of AAA authentication failuresro Counter32 .1.3.6.1.4.1.8164.1.14.11 |
starentA11Mgr OBJECT IDENTIFIER .1.3.6.1.4.1.8164.1.15 |
starA11MgrCountThe total number of A11 manager instancesro Gauge32 .1.3.6.1.4.1.8164.1.15.1 |
starA11TtlArrivedThe total number of A11 session requestsro Counter32 .1.3.6.1.4.1.8164.1.15.2 |
starA11TtlRejectedThe total number of rejected A11 sessionsro Counter32 .1.3.6.1.4.1.8164.1.15.3 |
starA11TtlDemultiplexedThe total number of demultiplexed A11 sessionsro Counter32 .1.3.6.1.4.1.8164.1.15.4 |
starA11TtlDeregThe total number of A11 deregistrationsro Counter32 .1.3.6.1.4.1.8164.1.15.5 |
starA11CurActiveThe current number of active A11 sessionsro Gauge32 .1.3.6.1.4.1.8164.1.15.6 |
starentHAMgr OBJECT IDENTIFIER .1.3.6.1.4.1.8164.1.16 |
starHAMgrCountThe total number of home agent manager instancesro Gauge32 .1.3.6.1.4.1.8164.1.16.1 |
starHATtlArrivedThe total number of home agent session requestsro Counter32 .1.3.6.1.4.1.8164.1.16.2 |
starHATtlRejectedThe total number of rejected home agent sessionsro Counter32 .1.3.6.1.4.1.8164.1.16.3 |
starHATtlDemultiplexedThe total number of demultiplexed home agent sessionsro Counter32 .1.3.6.1.4.1.8164.1.16.4 |
starHATtlDeregThe total number of home agent deregistrationsro Counter32 .1.3.6.1.4.1.8164.1.16.5 |
starHACurActiveThe total number of active home agent sessionsro Gauge32 .1.3.6.1.4.1.8164.1.16.6 |
starentFAMgr OBJECT IDENTIFIER .1.3.6.1.4.1.8164.1.17 |
starFAMgrCountThe total number of foreign agent manager instancesro Gauge32 .1.3.6.1.4.1.8164.1.17.1 |
starFATtlArrivedThe total number of foreign agent session requestsro Counter32 .1.3.6.1.4.1.8164.1.17.2 |
starFATtlRejectedThe total number of rejected foreign agent sessionsro Counter32 .1.3.6.1.4.1.8164.1.17.3 |
starFATtlDemultiplexedThe total number of demultiplexed foreign agent sessionsro Counter32 .1.3.6.1.4.1.8164.1.17.4 |
starFATtlDeregThe total number of foreign agent deregistrationsro Counter32 .1.3.6.1.4.1.8164.1.17.5 |
starFACurActiveThe current number of active foreign agent sessionsro Gauge32 .1.3.6.1.4.1.8164.1.17.6 |
starentService OBJECT IDENTIFIER .1.3.6.1.4.1.8164.1.18 |
starServiceTable SEQUENCE OF StarServiceEntry .1.3.6.1.4.1.8164.1.18.1 |
starServiceEntryInformation on a particular Service Manager StarServiceEntry .1.3.6.1.4.1.8164.1.18.1.1 |
starServiceVpnIDThe internal identification of the VPN (context) Gauge32 .1.3.6.1.4.1.8164.1.18.1.1.1 |
starServiceSvcIDThe internal identification of this service; unique within a specific context Gauge32 .1.3.6.1.4.1.8164.1.18.1.1.2 |
starServiceVpnNameThe name of this VPN (context)ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.18.1.1.3 |
starServiceServNameThe name of this servicero DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.18.1.1.4 |
starServiceSubLimitThe configured subscriber limitro Unsigned32 .1.3.6.1.4.1.8164.1.18.1.1.5 |
starServiceSubCurrentThe current number of subscribers limitro Gauge32 .1.3.6.1.4.1.8164.1.18.1.1.6 |
starServiceTypeThe type of servicero Enumeration .1.3.6.1.4.1.8164.1.18.1.1.7 |
starServiceFAIpAddrThe IP address for an FA service. Where unknown or not applicable this will contain all zeroes.ro IpAddress .1.3.6.1.4.1.8164.1.18.1.1.8 |
starServiceHAIpAddrThe IP address for an HA service. Where unknown or not applicable this will contain all zeroes.ro IpAddress .1.3.6.1.4.1.8164.1.18.1.1.9 |
starentCLIMgr OBJECT IDENTIFIER .1.3.6.1.4.1.8164.1.19 |
starCLITableA table containing information on all interactive CLI sessions SEQUENCE OF StarCLIEntry .1.3.6.1.4.1.8164.1.19.1 |
starCLIEntryInformation on a particular CLI Session StarCLIEntry .1.3.6.1.4.1.8164.1.19.1.1 |
starCLIIDThe internal identifier of this CLI session. Gauge32 .1.3.6.1.4.1.8164.1.19.1.1.1 |
starCLIUsernameThe name of the user logged into this CLI session, or 'unknown' if not nonero DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.19.1.1.2 |
starCLITtynameThe name of the TTY device for this CLI sessionro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.19.1.1.3 |
starCLIPrivsThe user presentable form of the privilege level of this CLI sessionro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.19.1.1.4 |
starCLITypeThe type of CLI; commandline(1) represents the normal interactive command line; ftp(2) represents an incoming FTP sessionro Enumeration .1.3.6.1.4.1.8164.1.19.1.1.5 |
starCLIRemoteIpAddrTypeThe type of remote IP address used to access this CLI session.ro InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.4.1.8164.1.19.1.1.6 |
starCLIRemoteIpAddrThe remote IP address used to access this CLI session. Where unknown or not applicable (such as access through a serial port) this will be 0ro InetAddress (INET-ADDRESS-MIB) .1.3.6.1.4.1.8164.1.19.1.1.7 |
starCLIContextThe context (VPN) currently being managed/viewed by the CLI session.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.19.1.1.8 |
starCLIDatabaseUsernameThe username of the user record in the database which was acted upon by the CLI sessionro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.19.1.1.9 |
starentTaskMgr OBJECT IDENTIFIER .1.3.6.1.4.1.8164.1.20 |
starTaskTableA table containing information about all active tasks SEQUENCE OF StarTaskEntry .1.3.6.1.4.1.8164.1.20.1 |
starTaskEntryInformation on a particular Task StarTaskEntry .1.3.6.1.4.1.8164.1.20.1.1 |
starTaskFacilityThe internal facility identifier Unsigned32 .1.3.6.1.4.1.8164.1.20.1.1.1 |
starTaskInstanceThe internal instance identifier which uniquely idenfies this task without a given facilityro Unsigned32 .1.3.6.1.4.1.8164.1.20.1.1.2 |
starTaskFacilityNameThe name of the facility for this taskro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.20.1.1.3 |
starTaskCardThe slot number of the card where this task is runningro Unsigned32 .1.3.6.1.4.1.8164.1.20.1.1.4 |
starTaskCPUThe CPU number where this task is runningro Unsigned32 .1.3.6.1.4.1.8164.1.20.1.1.5 |
starentPPP OBJECT IDENTIFIER .1.3.6.1.4.1.8164.1.21 |
starPPPStatTableA table containing PPP Stats SEQUENCE OF StarPPPStatEntry .1.3.6.1.4.1.8164.1.21.1 |
starPPPStatEntryThe statistics for an individual entry for a PPP context and service StarPPPStatEntry .1.3.6.1.4.1.8164.1.21.1.1 |
starPPPStatVpnIDThe internal identification of the PPP VPN (context) Gauge32 .1.3.6.1.4.1.8164.1.21.1.1.1 |
starPPPStatSvcIDThe service identification is made up from first 8 chars of context name and first 8 chars of service name separated by (:) StarShortID .1.3.6.1.4.1.8164.1.21.1.1.2 |
starPPPStatVpnNameThe name of the PPP VPN (context)ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.21.1.1.3 |
starPPPStatServNameThe name of the PPP servicero DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.21.1.1.4 |
starPPPStatInitThe number of initialized PPP sessions for the associated VPN servicero Counter32 .1.3.6.1.4.1.8164.1.21.1.1.5 |
starPPPStatRenegThe number of PPP session renegotiations for the associated VPN servicero Counter32 .1.3.6.1.4.1.8164.1.21.1.1.6 |
starPPPStatSuccessThe number of PPP session negotiation successes for the associated VPN servicero Counter32 .1.3.6.1.4.1.8164.1.21.1.1.7 |
starPPPStatFailedThe number of PPP session negotiation failures for the associated VPN servicero Counter32 .1.3.6.1.4.1.8164.1.21.1.1.8 |
starPPPStatReleasedThe number of PPP sessions released for the associated VPN servicero Counter32 .1.3.6.1.4.1.8164.1.21.1.1.9 |
starPPPStatReleasedLocalThe number of PPP sessions where the release was initiated locally for the associated VPN servicero Counter32 .1.3.6.1.4.1.8164.1.21.1.1.10 |
starPPPStatReleasedRemoteThe number of PPP sessions where the release was initiated remotely for the associated VPN servicero Counter32 .1.3.6.1.4.1.8164.1.21.1.1.11 |
starPPPStatLcpFailMaxRetryThe number of PPP sessions which failed to bring up the link control protocol due to excessive retries for the associated VPN servicero Counter32 .1.3.6.1.4.1.8164.1.21.1.1.12 |
starPPPStatLcpFailOptionThe number of PPP sessions which failed to bring up the link control protocol due to an invalid option being received for the associated VPN servicero Counter32 .1.3.6.1.4.1.8164.1.21.1.1.13 |
starPPPStatIpcpFailMaxRetryThe number of PPP sessions which failed to start the IP control protocol due to excessive retries for the associated VPN servicero Counter32 .1.3.6.1.4.1.8164.1.21.1.1.14 |
starPPPStatIpcpFailOptionThe number of PPP sessions which failed to start the IP control protocol due to an invalid option being received for the associated VPN servicero Counter32 .1.3.6.1.4.1.8164.1.21.1.1.15 |
starPPPStatCcpFailThe number of PPP sessions which failed to initialize the CCPro Counter32 .1.3.6.1.4.1.8164.1.21.1.1.16 |
starPPPStatAuthFailThe number of PPP sessions which failed authentication for the associated VPNro Counter32 .1.3.6.1.4.1.8164.1.21.1.1.17 |
starPPPStatLcpEnteredThe number of PPP sessions which successfully initialized the link control protocolro Counter32 .1.3.6.1.4.1.8164.1.21.1.1.18 |
starPPPStatAuthEnteredThe number of PPP sessions which were successfully authenticatedro Counter32 .1.3.6.1.4.1.8164.1.21.1.1.19 |
starPPPStatIpcpEnteredThe number of PPP sessions which successfully initialized the IP control protocolro Counter32 .1.3.6.1.4.1.8164.1.21.1.1.20 |
starPPPStatRenegPdsnThe number of PPP sessions which renegotiated the PDSN service accessro Counter32 .1.3.6.1.4.1.8164.1.21.1.1.21 |
starPPPStatRenegMobilThe number of PPP sessions which renegotiated the Mobile IP service accessro Counter32 .1.3.6.1.4.1.8164.1.21.1.1.22 |
starPPPStatRenegAddrMismatchThe number of PPP sessions which had an IP address mismatch during renegotiationro Counter32 .1.3.6.1.4.1.8164.1.21.1.1.23 |
starPPPStatRenegOtherThe number of PPP sessions which failed renegotiation for reasons other than IP address mismatchro Counter32 .1.3.6.1.4.1.8164.1.21.1.1.24 |
starPPPStatChapAuthAttemptThe number of PPP CHAP authentication attempts for the associated VPN servicero Counter32 .1.3.6.1.4.1.8164.1.21.1.1.25 |
starPPPStatPapAuthAttemptThe number of PPP PAP authentication attempts for the associated VPN servicero Counter32 .1.3.6.1.4.1.8164.1.21.1.1.26 |
starPPPStatMSChapAuthAttemptThe number of PPP MSCHAP authentication attempts for the associated VPN servicero Counter32 .1.3.6.1.4.1.8164.1.21.1.1.27 |
starPPPStatChapAuthFailThe number of PPP CHAP authentication attempt failures for the associated VPN servicero Counter32 .1.3.6.1.4.1.8164.1.21.1.1.28 |
starPPPStatPapAuthFailThe number of PPP PAP authentication failures for the associated VPN servicero Counter32 .1.3.6.1.4.1.8164.1.21.1.1.29 |
starPPPStatMSChapAuthFailThe number of PPP MSCHAP authentication failures for the associated VPN servicero Counter32 .1.3.6.1.4.1.8164.1.21.1.1.30 |
starPPPStatStacCompThe number of PPP sessions which had STAC compression enabled for the associated VPN servicero Counter32 .1.3.6.1.4.1.8164.1.21.1.1.31 |
starPPPStatMppcCompThe number of PPP sessions which had MPPC compression enabled for the associated VPN servicero Counter32 .1.3.6.1.4.1.8164.1.21.1.1.32 |
starPPPStatDeflCompThe number of PPP sessions which had DEFLATE compression enabled for the associated VPN servicero Counter32 .1.3.6.1.4.1.8164.1.21.1.1.33 |
starPPPStatFscErrsThe number of PPP forward sequence control errors in messagingro Counter32 .1.3.6.1.4.1.8164.1.21.1.1.34 |
starPPPStatUnknProtoThe number of PPP sessions which failed due to an unknown protocol received for the associated VPN servicero Counter32 .1.3.6.1.4.1.8164.1.21.1.1.35 |
starPPPStatBadAddrThe number of PPP sessions which failed due to a bad address being received for the associated VPN servicero Counter32 .1.3.6.1.4.1.8164.1.21.1.1.36 |
starPPPStatBadCtrlThe number of PPP sessions in which a bad control sequence was receivedro Counter32 .1.3.6.1.4.1.8164.1.21.1.1.37 |
starPPPStatVjCompThe number of PPP sessions which had VJ header compression enabled for the associated VPN servicero Counter32 .1.3.6.1.4.1.8164.1.21.1.1.38 |
starPPPStatDiscLcpRemoteThe number of PPP sessions which were disconnected via the link control protocol from the remote end for the associated VPN servicero Counter32 .1.3.6.1.4.1.8164.1.21.1.1.39 |
starPPPStatDiscRpRemoteThe number of PPP sessions which were disconnected by the remote via the R-P interface for the associated VPN servicero Counter32 .1.3.6.1.4.1.8164.1.21.1.1.40 |
starPPPStatDiscAdminThe number of PPP sessions which were disconnected by a local administrator for the associated VPN servicero Counter32 .1.3.6.1.4.1.8164.1.21.1.1.41 |
starPPPStatDiscIdleTimeoutThe number of PPP sessions disconnected due to session idle timer expiration for the associated VPN servicero Counter32 .1.3.6.1.4.1.8164.1.21.1.1.42 |
starPPPStatDiscAbsTimeoutThe number of PPP sessions disconnected due to the session absolute timer expiration for the associated VPN servicero Counter32 .1.3.6.1.4.1.8164.1.21.1.1.43 |
starPPPStatDiscPPPKeepaliveThe number of PPP sessions disconnected due to PPP keep alive failure for the associated VPN servicero Counter32 .1.3.6.1.4.1.8164.1.21.1.1.44 |
starPPPStatDiscNoResourceThe number of PPP sessions disconnected due to local resource shortage for the associated VPN servicero Counter32 .1.3.6.1.4.1.8164.1.21.1.1.45 |
starPPPStatDiscMiscThe number of PPP sessions disconnected due to any cause which does not match any other existing disconnect statistics for the associated VPN servicero Counter32 .1.3.6.1.4.1.8164.1.21.1.1.46 |
starPPPStatFailedRenegThe number of failed PPP renegotiations the associated VPN servicero Counter32 .1.3.6.1.4.1.8164.1.21.1.1.47 |
starPPPStatLcpFailUnknownThe number of failed PPP LCP that are due to unknown reasons for the associated VPN servicero Counter32 .1.3.6.1.4.1.8164.1.21.1.1.48 |
starPPPStatIpcpFailUnknownThe number of failed PPP IPCP that are due to unknown reasons for the associated VPN servicero Counter32 .1.3.6.1.4.1.8164.1.21.1.1.49 |
starPPPStatAuthAbortThe number of aborted PPP authentications for the associated VPN servicero Counter32 .1.3.6.1.4.1.8164.1.21.1.1.50 |
starPPPStatLowerLayerDiscThe number of Failed PPP session due to RP disconnect for the associated VPN servicero Counter32 .1.3.6.1.4.1.8164.1.21.1.1.51 |
starPPPStatLcpSuccessThe number of successful PPP LCPs for the associated VPN servicero Counter32 .1.3.6.1.4.1.8164.1.21.1.1.52 |
starPPPStatAuthSuccessThe number of successful PPP authentications for the associated VPN servicero Counter32 .1.3.6.1.4.1.8164.1.21.1.1.53 |
starPPPStatRenegLowerLayerHandoffThe number of PPP renigotiations for RP handoff for the associated VPN servicero Counter32 .1.3.6.1.4.1.8164.1.21.1.1.54 |
starPPPStatRenegParamUpdateThe number of PPP renigotiations for parameter update for the associated VPN servicero Counter32 .1.3.6.1.4.1.8164.1.21.1.1.55 |
starPPPStatChapAuthSuccessThe number of successful PPP CHAP authentications for the associated VPN servicero Counter32 .1.3.6.1.4.1.8164.1.21.1.1.56 |
starPPPStatPapAuthSuccessThe number of successful PPP PAP authentications for the associated VPN servicero Counter32 .1.3.6.1.4.1.8164.1.21.1.1.57 |
starPPPStatMSChapAuthSuccessThe number of successful PPP MSCHAP authentications for the associated VPN servicero Counter32 .1.3.6.1.4.1.8164.1.21.1.1.58 |
starPPPStatChapAuthAbortThe number of aboted PPP CHAP authentications for the associated VPN servicero Counter32 .1.3.6.1.4.1.8164.1.21.1.1.59 |
starPPPStatPapAuthAbortThe number of aboted PPP PAP authentications for the associated VPN servicero Counter32 .1.3.6.1.4.1.8164.1.21.1.1.60 |
starPPPStatMSChapAuthAbortThe number of aboted PPP MSCHAP authentications for the associated VPN servicero Counter32 .1.3.6.1.4.1.8164.1.21.1.1.61 |
starPPPStatSessSkipAuthThe number of PPP sessions that skipped authentications for the associated VPN servicero Counter32 .1.3.6.1.4.1.8164.1.21.1.1.62 |
starPPPStatNegCompThe number of PPP sessions that negotiated compressions for the associated VPN servicero Counter32 .1.3.6.1.4.1.8164.1.21.1.1.63 |
starPPPStatCCPNegFailCompThe number of PPP sessions that failed compression negotiation for the associated VPN servicero Counter32 .1.3.6.1.4.1.8164.1.21.1.1.64 |
starPPPStatDiscLocalLowerLayerThe number of disconnected PPP sessions due to local RP disconnect for the associated VPN servicero Counter32 .1.3.6.1.4.1.8164.1.21.1.1.65 |
starPPPStatDiscAddFlowFailThe number of disconnected PPP sessions due to failure in adding new flow for the associated VPN servicero Counter32 .1.3.6.1.4.1.8164.1.21.1.1.66 |
starPPPStatDiscMaxRetriesLCPThe number of disconnected PPP sessions due to max retries for LCP for the associated VPN servicero Counter32 .1.3.6.1.4.1.8164.1.21.1.1.67 |
starPPPStatDiscMaxRetriesIPCPThe number of disconnected PPP sessions due to max retries for IPCP for the associated VPN servicero Counter32 .1.3.6.1.4.1.8164.1.21.1.1.68 |
starPPPStatDiscMaxSetupTimerThe number of disconnected PPP sessions due to max setup time out for the associated VPN servicero Counter32 .1.3.6.1.4.1.8164.1.21.1.1.69 |
starPPPStatDiscInvalidDestVpnThe number of disconnected PPP sessions due to invalid destination VPN for the associated VPN servicero Counter32 .1.3.6.1.4.1.8164.1.21.1.1.70 |
starPPPStatDiscOptNegFailLCPThe number of disconnected PPP sessions due to invalid destination VPN for the associated VPN servicero Counter32 .1.3.6.1.4.1.8164.1.21.1.1.71 |
starPPPStatDiscOptNegFailIPCPThe number of disconnected PPP sessions due to failed IPCP option negotiation for the associated VPN servicero Counter32 .1.3.6.1.4.1.8164.1.21.1.1.72 |
starPPPStatDiscNoRemoteIpAddrThe number of disconnected PPP sessions due to no remote ip address for the associated VPN servicero Counter32 .1.3.6.1.4.1.8164.1.21.1.1.73 |
starPPPStatDiscCallTypeDetectFailThe number of disconnected PPP sessions due to failure detecting call type for the associated VPN servicero Counter32 .1.3.6.1.4.1.8164.1.21.1.1.74 |
starPPPStatDiscRemoteDiscUpLayerThe number of disconnected PPP sessions due to failure detecting call type for the associated VPN servicero Counter32 .1.3.6.1.4.1.8164.1.21.1.1.75 |
starPPPStatDiscLongDuraTimeoutThe number of disconnected PPP sessions due to long duration time out for the associated VPN servicero Counter32 .1.3.6.1.4.1.8164.1.21.1.1.76 |
starPPPStatDiscAuthFailThe number of disconnected PPP sessions due to failed authentication for the associated VPN servicero Counter32 .1.3.6.1.4.1.8164.1.21.1.1.77 |
starPPPStatLCPEchoTotalReqThe total number of PPP LCP echo requests for the associated VPN servicero Counter32 .1.3.6.1.4.1.8164.1.21.1.1.78 |
starPPPStatLCPEchoReqResentThe total number of PPP LCP echo requests resent for the associated VPN servicero Counter32 .1.3.6.1.4.1.8164.1.21.1.1.79 |
starPPPStatLCPEchoRepRecvedThe total number of PPP LCP echo replys received for the associated VPN servicero Counter32 .1.3.6.1.4.1.8164.1.21.1.1.80 |
starPPPStatLCPEchoReqTimeoutThe total number of PPP LCP echo requests time out for the associated VPN servicero Counter32 .1.3.6.1.4.1.8164.1.21.1.1.81 |
starPPPStatRecvErrBadCtrlFieldThe total number of received PPP error due to bad control fields for the associated VPN servicero Counter32 .1.3.6.1.4.1.8164.1.21.1.1.82 |
starPPPStatRecvErrBadPacketLenThe total number of received PPP error due to bad packet length for the associated VPN servicero Counter32 .1.3.6.1.4.1.8164.1.21.1.1.83 |
starPPPStatRemoteTermThe total number of PPP remote terminations for the associated VPN servicero Counter32 .1.3.6.1.4.1.8164.1.21.1.1.84 |
starPPPStatMiscFailThe number of misc PPP failures for the associated VPN servicero Counter32 .1.3.6.1.4.1.8164.1.21.1.1.85 |
starentMIPHA OBJECT IDENTIFIER .1.3.6.1.4.1.8164.1.22 |
starMIPHAStatTableA table containing MIP HA Stats SEQUENCE OF StarMIPHAStatEntry .1.3.6.1.4.1.8164.1.22.1 |
starMIPHAStatEntryThe Mobile IP home agent statistics for a specific VPN (context) and service StarMIPHAStatEntry .1.3.6.1.4.1.8164.1.22.1.1 |
starMIPHAStatVpnIDThe internal identification of the home agent Mobile IP VPN (context)ro Gauge32 .1.3.6.1.4.1.8164.1.22.1.1.1 |
starMIPHAStatSvcIDThe service identification is made up from first 8 chars of context name and first 8 chars of service name separated by (:) StarShortID .1.3.6.1.4.1.8164.1.22.1.1.2 |
starMIPHAStatVpnNameThe name of the VPN (context)ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.22.1.1.3 |
starMIPHAStatServNameThe Mobile IP home agent service namero DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.22.1.1.4 |
starMIPHAStatDisconnectsThe number of session disconnects for the associated Mobile IP home agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.22.1.1.5 |
starMIPHAStatExpiryThe number of session expirations for the associated Mobile IP home agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.22.1.1.6 |
starMIPHAStatDeregThe number of session deregistrations for the associated Mobile IP home agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.22.1.1.7 |
starMIPHAStatAdminDropThe number of session disconnects due to administrator actions for the associated Mobile IP home agent VPNro Counter32 .1.3.6.1.4.1.8164.1.22.1.1.8 |
starMIPHAStatRegRecvTotalThe number of session registrations received for the associated Mobile IP home agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.22.1.1.9 |
starMIPHAStatRegRecvInitialThe number of initial session registrations received for the associated Mobile IP home agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.22.1.1.10 |
starMIPHAStatRegRecvRenewThe number of session registration renewals received for the associated Mobile IP home agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.22.1.1.11 |
starMIPHAStatRegRecvDeregThe number of session deregistrations received for the associated Mobile IP home agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.22.1.1.12 |
starMIPHAStatRegAcceptTotalThe number of session registrations accepted for the associated Mobile IP home agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.22.1.1.13 |
starMIPHAStatRegAcceptRegThe number of session registrations accepted for the associated Mobile IP home agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.22.1.1.14 |
starMIPHAStatRegAcceptRenewThe number of session registration renewals accepted for the associated Mobile IP home agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.22.1.1.15 |
starMIPHAStatRegAcceptDeregThe number of session deregistrations accepted for the associated Mobile IP home agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.22.1.1.16 |
starMIPHAStatRegDeniedTotalThe number of session registrations denied for the associated Mobile IP home agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.22.1.1.17 |
starMIPHAStatRegDeniedInitialThe number of session initial registrations denied for the associated Mobile IP home agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.22.1.1.18 |
starMIPHAStatRegDeniedRenewThe number of session registration renewals denied for the associated Mobile IP home agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.22.1.1.19 |
starMIPHAStatRegDeniedDeregThe number of session deregistrations denied for the associated Mobile IP home agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.22.1.1.20 |
starMIPHAStatRegReplyTotalThe total number of session registration replies for the associated Mobile IP home agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.22.1.1.21 |
starMIPHAStatRegReplyAcceptRegThe number of session registration replies accepted indicating registration for the associated Mobile IP home agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.22.1.1.22 |
starMIPHAStatRegReplyAcceptDeregThe number of session registration replies accepted indicated deregistration for the associated Mobile IP home agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.22.1.1.23 |
starMIPHAStatRegReplyDeniedThe number of session registration replies which were denied for the associated Mobile IP home agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.22.1.1.24 |
starMIPHAStatRegReplyBadReqThe number of session registration replies indicating a bad request for the associated Mobile IP home agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.22.1.1.25 |
starMIPHAStatRegReplyMismatchIDThe number of session registration replies indicating an ID mismatch for the associated Mobile IP home agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.22.1.1.26 |
starMIPHAStatRegReplyAdminProhibThe number of session registration replies indicating administrator prohibition for the associated Mobile IP home agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.22.1.1.27 |
starMIPHAStatRegReplyUnspecErrThe number of session registration replies with an unspecified error for the associated Mobile IP home agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.22.1.1.28 |
starMIPHAStatRegReplyNoResourceThe number of session registration replies indicating no resources for the associated Mobile IP home agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.22.1.1.29 |
starMIPHAStatRegReplyMnAuthFailThe number of session registration replies indication mobile number authentication failure for the associated Mobile IP home agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.22.1.1.30 |
starMIPHAStatRegReplyFAAuthFailThe number of session registration replies indicating a foreign agent authentication failure for the associated Mobile IP home agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.22.1.1.31 |
starMIPHAStatRegReplySimulBindThe number of session registration replies indicating a simultaneous bind condition for the associated Mobile IP home agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.22.1.1.32 |
starMIPHAStatRegReplyUnknownHAThe number of session registration replies indicating unknown home agent for the associated Mobile IP home agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.22.1.1.33 |
starMIPHAStatRegReplyRevTunUnavThe number of session registration replies indicating no reverse tunnel available for the associated Mobile IP home agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.22.1.1.34 |
starMIPHAStatRegReplyRevTunMandThe number of session registration replies indicating reverse tunneling is mandatory for the associated Mobile IP home agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.22.1.1.35 |
starMIPHAStatRegReplyEncapUnavThe number of session registration replies indicating IP encapsulation was not available for the associated Mobile IP home agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.22.1.1.36 |
starMIPHAStatRegReplySendErrorThe number of session registration replies indicating a send error occurred for the associated Mobile IP home agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.22.1.1.37 |
starMIPHAStatFARevocationsThe number of FA revocations for the associated Mobile IP home agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.22.1.1.38 |
starMIPHAStatRegAcceptHOThe number of hand over session registrations accepted for the associated Mobile IP home agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.22.1.1.39 |
starMIPHAStatRegDeniedHOThe number of hand over session registrations denied for the associated Mobile IP home agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.22.1.1.40 |
starMIPHAStatRegDiscardTotalThe number of session registrations discarded for the associated Mobile IP home agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.22.1.1.41 |
starentMIPFA OBJECT IDENTIFIER .1.3.6.1.4.1.8164.1.23 |
starMIPFAStatTableA table containing MIP FA Stats SEQUENCE OF StarMIPFAStatEntry .1.3.6.1.4.1.8164.1.23.1 |
starMIPFAStatEntryThe statistics for a specific foreign agent Mobile IP VPN (context) service StarMIPFAStatEntry .1.3.6.1.4.1.8164.1.23.1.1 |
starMIPFAStatVpnIDInternal identication of the foreign agent Mobile IP VPN (context)ro Gauge32 .1.3.6.1.4.1.8164.1.23.1.1.1 |
starMIPFAStatSvcIDThe service identification is made up from first 8 chars of context name and first 8 chars of service name separated by (:) StarShortID .1.3.6.1.4.1.8164.1.23.1.1.2 |
starMIPFAStatVpnNameThe foreign agent mobile IP VPN (context) namero DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.23.1.1.3 |
starMIPFAStatServNameThe Mobile IP foreign agent service namero DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.23.1.1.4 |
starMIPFAStatAdvertSendThe number of advertisements sent for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.5 |
starMIPFAStatDiscExpiryThe number of session disconnects due to expiration for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.6 |
starMIPFAStatDiscDeregThe number of session disconnects due to deregistration for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.7 |
starMIPFAStatDiscAdminThe number of dession disconnects due to administrator action for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.8 |
starMIPFAStatAuthAttemptThe number of session authentication attempts for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.9 |
starMIPFAStatAuthSuccessThe number of session authentication successes for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.10 |
starMIPFAStatAuthFailureThe number of session authentication failures for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.11 |
starMIPFAStatRegRecvTotalThe total number of session registrations received for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.12 |
starMIPFAStatRegRecvInitialThe number of initial session registrations received for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.13 |
starMIPFAStatRegRecvRenewalThe number of session registration renewals for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.14 |
starMIPFAStatRegRecvDeregThe number of session deregistrations for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.15 |
starMIPFAStatRegAcceptTotalThe total number of session registrations accepted for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.16 |
starMIPFAStatRegAcceptInitialThe number of initial session registrations accepted for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.17 |
starMIPFAStatRegAcceptRenewalThe number of session registration renewals accepted for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.18 |
starMIPFAStatRegAcceptDeregThe number of session deregistrations accepted for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.19 |
starMIPFAStatRegDenTotalThe total number of session registrations denied for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.20 |
starMIPFAStatRegDenInitialThe number of initial session registrations denied for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.21 |
starMIPFAStatRegDenRenewalThe number of session registration renewals denied for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.22 |
starMIPFAStatRegDenDeregThe number of session deregistrations denied for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.23 |
starMIPFAStatRegDiscardTotalThe total number of session registrations discarded for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.24 |
starMIPFAStatRegDiscardInitialThe total number of session registrations discarded for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.25 |
starMIPFAStatRegDiscardRenewalThe number of session registration renewals discarded for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.26 |
starMIPFAStatRegDiscardDeregThe number of dession reregistrations discarded for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.27 |
starMIPFAStatRegRelayedTotalThe total number of session registrations relayed for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.28 |
starMIPFAStatRegRelayedInitialThe number of initial session registrations relayed for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.29 |
starMIPFAStatRegRelayedRenewalThe number of dession registration renewals relayed for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.30 |
starMIPFAStatRegRelayedDeregThe number of session deregistrations relayed for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.31 |
starMIPFAStatRegAuthFailTotalThe total number of session registration authentication failures for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.32 |
starMIPFAStatRegAuthFailInitialThe number of initial session registration failures for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.33 |
starMIPFAStatRegAuthFailRenewalThe number of session registration renewal failures for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.34 |
starMIPFAStatRegAuthFailDeregThe number of session deregistration authentication failures for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.35 |
starMIPFAStatRegDenPDSNTotalThe total number of PDSN session registrations denied for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.36 |
starMIPFAStatRegDenPDSNInitialThe number of initial PDSN session registrations denied for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.37 |
starMIPFAStatRegDenPDSNRenewalThe number of PDSN session registration renewals denied for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.38 |
starMIPFAStatRegDenPDSNDeregThe number of PDSN session deregistrations denied for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.39 |
starMIPFAStatRegDenHATotalThe total number of session deregistrations denied by the home agent for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.40 |
starMIPFAStatRegDenHAInitialThe number of initial session registrations denied by the home agent for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.41 |
starMIPFAStatRegDenHARenewalThe number of session registration renewals denied by the home agent for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.42 |
starMIPFAStatRegDenHADeregThe number of session deregistrations denied by the home agent for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.43 |
starMIPFAStatRegDenPDSNUnspecThe number of PDSN session registrations denied for an unspecified reason for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.44 |
starMIPFAStatRegDenPDSNTimeoutThe number of PDSN session registrations denied due to timer expiration for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.45 |
starMIPFAStatRegDenPDSNAdminThe number of PDSN session registrations denied due to administrator prohibition for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.46 |
starMIPFAStatRegDenPDSNResourcesThe number of PDSN session registrations denied due to no resources for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.47 |
starMIPFAStatRegDenPDSNMnAuthThe number of PDSN session registrations denied due to mobile number authentication for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.48 |
starMIPFAStatRegDenPDSNHAAuthThe number of PDSN session registrations denied by the home agent for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.49 |
starMIPFAStatRegDenPDSNTooLongThe number of PDSN session registrations denied due to a life too long indication for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.50 |
starMIPFAStatRegDenPDSNBadReqThe number of PDSN session registrations denied due to a bad request indication for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.51 |
starMIPFAStatRegDenPDSNEncapUnavThe number of PDSN session registrations denied due to no IP encapsulation available for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.52 |
starMIPFAStatRegDenPDSNRevTunUnavThe number of PDSN session registrations denied due to no reverse tunnel available for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.53 |
starMIPFAStatRegDenPDSNRevTunMandThe number of PDSN session registration denied due to reverse tunneling being mandatory for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.54 |
starMIPFAStatRegDenHAFAAuthThe number of PDSN registrations denied by the home agent due to authentication failure for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.55 |
starMIPFAStatRegDenHABadReqThe number of session registration denied by the home agent due to the request being invalid for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.56 |
starMIPFAStatRegDenHAMismatchIDThe number of session registrations denied by the home agent due to an ID mismatch for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.57 |
starMIPFAStatRegDenHASimulBindThe number of session registrations denied by the home agent due to a simultaneous bind attempt for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.58 |
starMIPFAStatRegDenHAUnknownHAThe number of session registrations denied by the home agent for an unknown reason for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.59 |
starMIPFAStatRegDenHARevRunUnavailThe number of session registrations denied by the home agent due to no reverse tunnel being available for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.60 |
starMIPFAStatRegRplRcvTotalThe total number of session registration replies received for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.61 |
starMIPFAStatRegRplRcvTotalRlyThe total number of session registration replies relayed for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.62 |
starMIPFAStatRegRplRcvErrorsThe total number of session registration replies received indicating errors for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.63 |
starMIPFAStatRegRplRcvInitialThe number of initial session registration replies received for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.64 |
starMIPFAStatRegRplRcvInitialRlyThe number of initial session registration replies relayed for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.65 |
starMIPFAStatRegRplRcvRenewalThe number of session registration renewal replies received for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.66 |
starMIPFAStatRegRplRcvRenewalRlyThe number of session registration renewal replies received for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.67 |
starMIPFAStatRegRplRcvDeregThe number of session registration replies received indicating deregistration for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.68 |
starMIPFAStatRegRplRcvDeregRlyThe number of session registration replies relayed indicating deregistration for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.69 |
starMIPFAStatRegRplSentTotalThe total number of session registration replies sent for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.70 |
starMIPFAStatRegRplSentAcceptRegThe number of session registration replies which were sent and accepted for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.71 |
starMIPFAStatRegRplSentAcceptDeregThe number of session registration replies which were sent and accepted indication deregistration for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.72 |
starMIPFAStatRegRplSentBadReqThe number of session registration replies which were sent indicating the request was invalid for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.73 |
starMIPFAStatRegRplSentTooLongThe number of session registration replies which were sent indicating life too long for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.74 |
starMIPFAStatRegRplSentMnAuthFailThe number of session registration replies which were sent indicating mobile number authentication failure for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.75 |
starMIPFAStatRegRplSentHAAuthFailThe number of session registration replies which were sent indicating home agent authentication failure for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.76 |
starMIPFAStatRegRplSentAdminProhibThe number of session registration replies which were sent indicating prohibited by the administration for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.77 |
starMIPFAStatRegRplSentNoResourcesThe number of session registration replies which were sent indicating no resources available for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.78 |
starMIPFAStatRegRplSentRevTunUnavThe number of session registration replies which were sent indicating no reverse tunnel available for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.79 |
starMIPFAStatRegRplSentRevTunMandThe number of session registration replies which were sent indicating reverse tunneling was mandatory for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.80 |
starMIPFAStatRegRplSentSendErrorsThe number of session registration replies which were sent indicating there were errors in transmission for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.81 |
starMIPFAStatRegDenPDSNBadReplyThe number of session registrations denied by PDSN due to bad relply from HA for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.82 |
starMIPFAStatRegDenPDSNMissNAIThe number of session registrations denied by PDSN due to missing NAI for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.83 |
starMIPFAStatRegDenPDSNMissHomeAgentThe number of session registrations denied by PDSN due to missing home agent for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.84 |
starMIPFAStatRegDenPDSNMissHomeAddrThe number of session registrations denied by PDSN due to missing home address for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.85 |
starMIPFAStatRegDenPDSNUnknChallengeThe number of session registrations denied by PDSN due to unknown challenge for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.86 |
starMIPFAStatRegDenPDSNMissChallengeThe number of session registrations denied by PDSN due to missing challenge for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.87 |
starMIPFAStatRegDenPDSNStaleChallengeThe number of session registrations denied by PDSN due to stale challenge for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.88 |
starMIPFAStatRegDenPDSNMNTooDistantThe number of session registrations denied by PDSN due to MN too distant for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.89 |
starMIPFAStatRegDenPDSNStyleUnavailThe number of session registration denied by PDSN due to style not available for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.90 |
starMIPFAStatRegDenPDSNHANetUnreachThe number of session registrations denied by PDSN due to HA network unreachable for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.91 |
starMIPFAStatRegDenPDSNHAHostUnreachThe number of session registrations denied by PDSN due to HA host unreachable for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.92 |
starMIPFAStatRegDenPDSNHAPortUnreachThe number of session registrations denied by PDSN due to HA port unreachable for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.93 |
starMIPFAStatRegDenPDSNHAUnreachThe number of session registrations denied by PDSN due to HA unreachable for misc reasons for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.94 |
starMIPFAStatRegDenPDSNInvCOAThe number of session registrations denied by PDSN due to invalid COA for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.95 |
starMIPFAStatRegReqSentInitTotalThe number of initial session registrations for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.96 |
starMIPFAStatRegReqSentInitResendThe number of initial session registrations retried for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.97 |
starMIPFAStatRegReqSentRenewTotalThe number of renewal session registrations for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.98 |
starMIPFAStatRegReqSentRenewResendThe number of renewal session registrations retried for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.99 |
starMIPFAStatRegReqSentDeregTotalThe number of session deregistrations for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.100 |
starMIPFAStatRegReqSentDeregResendThe number of session deregistrations retried for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.101 |
starMIPFAStatRegRplSentMNTooDistantThe number of session registration reply that indicate MN too distant for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.102 |
starMIPFAStatRegRplSentInvCOAThe number of session registration reply that indicate invalid COA for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.103 |
starMIPFAStatRegRplSentHANetUnreachThe number of session registration reply that indicate HA network unreachable for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.104 |
starMIPFAStatRegRplSentHAHostUnreachThe number of session registration reply that indicate HA host unreachable for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.105 |
starMIPFAStatRegRplSentHAPortUnreachThe number of session registration reply that indicate HA port unreachable for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.106 |
starMIPFAStatRegRplSentHAUnreachThe number of session registration reply that indicate HA unreachable due to misc reasons for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.107 |
starMIPFAStatRegRplSentRegTimeoutThe number of session registration reply that indicate registration time out for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.108 |
starMIPFAStatRegRplSentMissNAIThe number of session registration reply that indicate NAI missing for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.109 |
starMIPFAStatRegRplSentMissHomeAgentThe number of session registration reply that indicate HA missing for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.110 |
starMIPFAStatRegRplSentMissHomeAddrThe number of session registration reply that indicate home address missing for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.111 |
starMIPFAStatRegRplSentUnknChallengeThe number of session registration reply that indicate unknown challenge for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.112 |
starMIPFAStatRegRplSentMissChallengeThe number of session registration reply that indicate challenge missing for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.113 |
starMIPFAStatRegRplSentStaleChallengeThe number of session registration reply that indicate stale challenge for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.114 |
starMIPFAStatRegRplSentBadReplyThe number of session registration reply that indicate bad reply for the associated Mobile IP foreign agent VPN servicero Counter32 .1.3.6.1.4.1.8164.1.23.1.1.115 |
starentRP OBJECT IDENTIFIER .1.3.6.1.4.1.8164.1.24 |
starRPStatTableA table containing MIP FA Stats SEQUENCE OF StarRPStatEntry .1.3.6.1.4.1.8164.1.24.1 |
starRPStatEntryThe statistics for a specific R-P VPN (context) service StarRPStatEntry .1.3.6.1.4.1.8164.1.24.1.1 |
starRPStatVpnIDThe internal identification of the R-P VPN (context)ro Gauge32 .1.3.6.1.4.1.8164.1.24.1.1.1 |
starRPStatSvcIDThe service identification is made up from first 8 chars of context name and first 8 chars of service name separated by (:) StarShortID .1.3.6.1.4.1.8164.1.24.1.1.2 |
starRPStatVpnNameThe R-P VPN (context) namero DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.24.1.1.3 |
starRPStatServNameThe R-P service namero DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.24.1.1.4 |
starRPRegRecvTotalThe total number of session registrations received for the associated R-P VPN servicero Counter32 .1.3.6.1.4.1.8164.1.24.1.1.5 |
starRPRegAcceptTotalThe total number of session registrations accepted for the associated R-P VPN servicero Counter32 .1.3.6.1.4.1.8164.1.24.1.1.6 |
starRPRegDeniedTotalThe total number of session registrations denied for the associated R-P VPN servicero Counter32 .1.3.6.1.4.1.8164.1.24.1.1.7 |
starRPRegDiscardTotalThe total number of session registrations discarded for the associated R-P VPN servicero Counter32 .1.3.6.1.4.1.8164.1.24.1.1.8 |
starRPRegAcceptInitialThe total number of initial session registrations accepted for the associated R-P VPN servicero Counter32 .1.3.6.1.4.1.8164.1.24.1.1.9 |
starRPRegAcceptIntraPDSNThe number of Intra-PDSN session registrations accepted for the associated R-P VPN serviceroobsolete Counter32 .1.3.6.1.4.1.8164.1.24.1.1.10 |
starRPRegAcceptInterPDSNThe number of Inter-PDSN session registrations accepted for the associated R-P VPN servicero Counter32 .1.3.6.1.4.1.8164.1.24.1.1.11 |
starRPRegDeniedInitialThe number of initial session registrations denied for the associated R-P VPN servicero Counter32 .1.3.6.1.4.1.8164.1.24.1.1.12 |
starRPRegAcceptRenewThe number of session registration renewals accepted for the associated R-P VPN servicero Counter32 .1.3.6.1.4.1.8164.1.24.1.1.13 |
starRPRegDeniedRenewThe number of session registration renewals denied for the associated R-P VPN servicero Counter32 .1.3.6.1.4.1.8164.1.24.1.1.14 |
starRPRegAcceptDeregThe number of session deregistrations accepted for the associated R-P VPN servicero Counter32 .1.3.6.1.4.1.8164.1.24.1.1.15 |
starRPRegDeniedDeregThe number of session deregistrations denied for the associated R-P VPN servicero Counter32 .1.3.6.1.4.1.8164.1.24.1.1.16 |
starRPRegSendErrorThe number of session registrations with errors in transmission for the associated R-P VPN servicero Counter32 .1.3.6.1.4.1.8164.1.24.1.1.17 |
starRPRegHashErrorThe number of session registrations with hash errors for the associated R-P VPN servicero Counter32 .1.3.6.1.4.1.8164.1.24.1.1.18 |
starRPRegDecodeErrorThe number of sessions registrations with decode errors for the associated R-P VPN servicero Counter32 .1.3.6.1.4.1.8164.1.24.1.1.19 |
starRPRegUnhandledThe number of session registrations unable to by proceeded for the associated R-P VPN servicero Counter32 .1.3.6.1.4.1.8164.1.24.1.1.20 |
starRPRegAirlinkSeqErrorThe number of session registrations with air link sequence errors for the associated R-P VPN servicero Counter32 .1.3.6.1.4.1.8164.1.24.1.1.21 |
starRPRegDenyUnspecThe number of session registrations denied for an unspecified reason for the associated R-P VPN servicero Counter32 .1.3.6.1.4.1.8164.1.24.1.1.22 |
starRPRegDenyAdminProhibThe number of session registrations denied due to administrator prohibition for the associated R-P VPN servicero Counter32 .1.3.6.1.4.1.8164.1.24.1.1.23 |
starRPRegDenyNoResourceThe number of session registrations denied due to no resources available for the associated R-P VPN servicero Counter32 .1.3.6.1.4.1.8164.1.24.1.1.24 |
starRPRegDenyAuthThe number of session registrations denied due to authentication failure for the associated R-P VPN servicero Counter32 .1.3.6.1.4.1.8164.1.24.1.1.25 |
starRPRegDenyMismatchIDThe number of session registrations denied due to an ID mismatch for the associated R-P VPN servicero Counter32 .1.3.6.1.4.1.8164.1.24.1.1.26 |
starRPRegDenyBadRequestThe number of session registrations denied due to the request being invalid for the associated R-P VPN servicero Counter32 .1.3.6.1.4.1.8164.1.24.1.1.27 |
starRPRegDenyUnknownPDSNThe number of session registrations denied due to the packet data service not being recognized for the associated R-P VPN servicero Counter32 .1.3.6.1.4.1.8164.1.24.1.1.28 |
starRPRegDenyRevTunUnavThe number of session registrations denied due to no reverse tunnel being available for the associated R-P VPN servicero Counter32 .1.3.6.1.4.1.8164.1.24.1.1.29 |
starRPRegDenyRevTunReqThe number of session registrations denied due to reverse tunneling being mandatory for the associated R-P VPN servicero Counter32 .1.3.6.1.4.1.8164.1.24.1.1.30 |
starRPRegDenyUnrecogVendThe number of session registrations denied due to the vendor not being recognized for the associated R-P VPN servicero Counter32 .1.3.6.1.4.1.8164.1.24.1.1.31 |
starRPRegUpdTotalThe total number of session registration updates for the associated R-P VPN servicero Counter32 .1.3.6.1.4.1.8164.1.24.1.1.32 |
starRPRegUpdAcceptThe number of session registration updates which were accepted for the associated R-P VPN servicero Counter32 .1.3.6.1.4.1.8164.1.24.1.1.33 |
starRPRegUpdDeniedThe number of session registration updates which were denied for the associated R-P VPN servicero Counter32 .1.3.6.1.4.1.8164.1.24.1.1.34 |
starRPRegUpdUnackThe number of session registration updates which were not acknowledged for the associated R-P VPN servicero Counter32 .1.3.6.1.4.1.8164.1.24.1.1.35 |
starRPRegUpdTransThe number of session registration updates sent for the associated R-P VPN servicero Counter32 .1.3.6.1.4.1.8164.1.24.1.1.36 |
starRPRegUpdRetransThe number of session registration updates resent for the associated R-P VPN servicero Counter32 .1.3.6.1.4.1.8164.1.24.1.1.37 |
starRPRegUpdReceivedThe number of session registration updates received for the associated R-P VPN servicero Counter32 .1.3.6.1.4.1.8164.1.24.1.1.38 |
starRPRegUpdDiscardThe number of session registration updates discarded for the associated R-P VPN servicero Counter32 .1.3.6.1.4.1.8164.1.24.1.1.39 |
starRPRegUpdSendErrorThe number of session registration updates with errors in transmission for the associated R-P VPN servicero Counter32 .1.3.6.1.4.1.8164.1.24.1.1.40 |
starRPRegUpdUplyrInitThe number of session registration updates with up-link reinitializationsro Counter32 .1.3.6.1.4.1.8164.1.24.1.1.41 |
starRPRegUpdOtherThe number of session registration updates with a reason of 'other' for the associated R-P VPN servicero Counter32 .1.3.6.1.4.1.8164.1.24.1.1.42 |
starRPRegUpdHandoffThe number of session registration updates due to a mobile hand-off for the associated R-P VPN servicero Counter32 .1.3.6.1.4.1.8164.1.24.1.1.43 |
starRPRegUpdDenyUnspecThe number of session registration updates denied for an unspecified reason for the associated R-P VPN servicero Counter32 .1.3.6.1.4.1.8164.1.24.1.1.44 |
starRPRegUpdDenyAdminProhibThe number of session registration updates denied due to administration prohibition for the associated R-P VPN servicero Counter32 .1.3.6.1.4.1.8164.1.24.1.1.45 |
starRPRegUpdDenyAuthThe number of session registration updates denied due to authentication failure for the associated R-P VPN servicero Counter32 .1.3.6.1.4.1.8164.1.24.1.1.46 |
starRPRegUpdDenyMismatchIDThe number of session registration updates denied due to an ID mismatch for the associated R-P VPN servicero Counter32 .1.3.6.1.4.1.8164.1.24.1.1.47 |
starRPRegUpdDenyBadRequestThe number of session registration updates denied due to the request being invalid for the associated R-P VPN servicero Counter32 .1.3.6.1.4.1.8164.1.24.1.1.48 |
starRPSecViolationsThe total number of session security violations for the associated R-P VPN servicero Counter32 .1.3.6.1.4.1.8164.1.24.1.1.49 |
starRPSecBadAuthThe total number of session security authentication violations for the associated R-P VPN servicero Counter32 .1.3.6.1.4.1.8164.1.24.1.1.50 |
starRPSecBadIDThe total number of session security ID violations for the associated R-P VPN servicero Counter32 .1.3.6.1.4.1.8164.1.24.1.1.51 |
starRPSecBadSpiThe total number of session security SPI violations for the associated R-P VPN servicero Counter32 .1.3.6.1.4.1.8164.1.24.1.1.52 |
starRPSecMissingMnHAAuthThe total number of session security missing mobile number home agent authentication violation for the associated R-P VPN servicero Counter32 .1.3.6.1.4.1.8164.1.24.1.1.53 |
starRPSecMissingRegUpdateThe total number of session missing registration update violations for the associated R-P VPN servicero Counter32 .1.3.6.1.4.1.8164.1.24.1.1.54 |
starRPRegRecvInitialThe total number of initial session registration for the associated R-P VPN servicero Counter32 .1.3.6.1.4.1.8164.1.24.1.1.55 |
starRPRegAcceptActvStartIntraPDSNThe number of accepted registration request during intraPDSN handoff which contains active start for the associated R-P VPN servicero Counter32 .1.3.6.1.4.1.8164.1.24.1.1.56 |
starRPRegAcceptActvStopIntraPDSNThe number of accepted registration request during intraPDSN handoff which contains active stop for the associated R-P VPN servicero Counter32 .1.3.6.1.4.1.8164.1.24.1.1.57 |
starRPRegRecvRenewThe number of received renew registration request for the associated R-P VPN servicero Counter32 .1.3.6.1.4.1.8164.1.24.1.1.58 |
starRPRegActvStartRenewThe number of received renew registration request that contains active start for the associated R-P VPN servicero Counter32 .1.3.6.1.4.1.8164.1.24.1.1.59 |
starRPRegActvStopRenewThe number of received renew registration request that contains active stop for the associated R-P VPN servicero Counter32 .1.3.6.1.4.1.8164.1.24.1.1.60 |
starRPRegRecvDeregThe number of received deregistration request for the associated R-P VPN servicero Counter32 .1.3.6.1.4.1.8164.1.24.1.1.61 |
starRPRegAcceptActvStopDeregThe number of accepted deregistration request that contains active stop for the associated R-P VPN servicero Counter32 .1.3.6.1.4.1.8164.1.24.1.1.62 |
starRPDiscSessAbsentThe number of registration request discarded due to no session for the associated R-P VPN servicero Counter32 .1.3.6.1.4.1.8164.1.24.1.1.63 |
starRPDiscNoMemoryThe number of registration request discarded due to no memory for the associated R-P VPN servicero Counter32 .1.3.6.1.4.1.8164.1.24.1.1.64 |
starRPDiscMalformedThe number of registration request discarded because malformed for the associated R-P VPN servicero Counter32 .1.3.6.1.4.1.8164.1.24.1.1.65 |
starRPDiscAuthFailThe number of registration request discarded because authentication failed for the associated R-P VPN servicero Counter32 .1.3.6.1.4.1.8164.1.24.1.1.66 |
starRPDiscInternalBounceThe number of registration request discarded because internal bounce for the associated R-P VPN servicero Counter32 .1.3.6.1.4.1.8164.1.24.1.1.67 |
starRPDiscInpuQueueExceededThe number of registration request discarded because internal queue exceeded for the associated R-P VPN servicero Counter32 .1.3.6.1.4.1.8164.1.24.1.1.68 |
starRPDiscMismatchedIdThe number of registration request discarded because mismatched ID for the associated R-P VPN servicero Counter32 .1.3.6.1.4.1.8164.1.24.1.1.69 |
starRPDiscInvPacketLenThe number of registration request discarded because invalid packet length for the associated R-P VPN servicero Counter32 .1.3.6.1.4.1.8164.1.24.1.1.70 |
starRPDiscMiscThe number of registration request discarded due to misc reasons for the associated R-P VPN servicero Counter32 .1.3.6.1.4.1.8164.1.24.1.1.71 |
starRP1xTxBytesThe number of 1x bytes transmitted, in megabytesro Counter32 UNITS "Megabytes" .1.3.6.1.4.1.8164.1.24.1.1.72 |
starRP1xRxBytesThe number of 1x bytes received, in megabytesro Counter32 UNITS "Megabytes" .1.3.6.1.4.1.8164.1.24.1.1.73 |
starRP1xTxPacketsThe number of 1x packets transmitted, in thousandsro Counter32 UNITS "Thousands" .1.3.6.1.4.1.8164.1.24.1.1.74 |
starRP1xRxPacketsThe number of 1x packets received, in thousandsro Counter32 UNITS "Thousands" .1.3.6.1.4.1.8164.1.24.1.1.75 |
starRPDoTxBytesThe number of Do bytes transmitted, in megabytesro Counter32 UNITS "Megabytes" .1.3.6.1.4.1.8164.1.24.1.1.76 |
starRPDoRxBytesThe number of Do bytes received, in megabytesro Counter32 UNITS "Megabytes" .1.3.6.1.4.1.8164.1.24.1.1.77 |
starRPDoTxPacketsThe number of Do packets transmitted, in thousandsro Counter32 UNITS "Thousands" .1.3.6.1.4.1.8164.1.24.1.1.78 |
starRPDoRxPacketsThe number of Do packets received, in thousandsro Counter32 UNITS "Thousands" .1.3.6.1.4.1.8164.1.24.1.1.79 |
starentSubscriber OBJECT IDENTIFIER .1.3.6.1.4.1.8164.1.26 |
starSubTableA table containing subscriber information SEQUENCE OF StarSubEntry .1.3.6.1.4.1.8164.1.26.1 |
starSubEntryInformation for a specific Subscriber StarSubEntry .1.3.6.1.4.1.8164.1.26.1.1 |
starSubContextThe context the subscriber is inro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.26.1.1.1 |
starSubMSIDThe MSID of the subscriberro OCTET STRING .1.3.6.1.4.1.8164.1.26.1.1.2 |
starSubNameThe name of the subscriberro OCTET STRING .1.3.6.1.4.1.8164.1.26.1.1.3 |
starSubTimerDurationThe length of the long-duration timer in secondsro Unsigned32 .1.3.6.1.4.1.8164.1.26.1.1.4 |
starSubLongDurTimeoutActionThe action taken by the system upon detection of a long-duration sessionro StarLongDurTimeoutAction .1.3.6.1.4.1.8164.1.26.1.1.5 |
starSubSetupTimeThe time when the call was setupro DateAndTime (SNMPv2-TC) .1.3.6.1.4.1.8164.1.26.1.1.6 |
starSubHomeAddrThe ipv4 home address.ro IpAddress .1.3.6.1.4.1.8164.1.26.1.1.7 |
starSubHomeAddrv6The ipv6 home address.ro Ipv6Address (IPV6-TC) .1.3.6.1.4.1.8164.1.26.1.1.8 |
starentEISServer OBJECT IDENTIFIER .1.3.6.1.4.1.8164.1.27 |
starEISServerTableA table containing EIS Server information SEQUENCE OF StarEISServerEntry .1.3.6.1.4.1.8164.1.27.1 |
starEISServerEntryInformation for a specific EIS Server StarEISServerEntry .1.3.6.1.4.1.8164.1.27.1.1 |
starEISServerVPNIDThe VPN ID for the EIS Server Gauge32 .1.3.6.1.4.1.8164.1.27.1.1.1 |
starEISServerAddrThe IP Address for the EIS Serverro IpAddress .1.3.6.1.4.1.8164.1.27.1.1.2 |
starEISServerVPNNameThe VPN Name for this EIS Serverro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.27.1.1.3 |
starentThresholds OBJECT IDENTIFIER .1.3.6.1.4.1.8164.1.28 |
starThreshMeasuredPctThe measured value of a thresholded parameterro Gauge32 .1.3.6.1.4.1.8164.1.28.1 |
starThreshPctThe configured value of a thresholded parameterro Integer32 .1.3.6.1.4.1.8164.1.28.2 |
starThreshMeasuredIntThe measured value of a thresholded parameterro Gauge32 .1.3.6.1.4.1.8164.1.28.3 |
starThreshIntThe configured value of a thresholded parameterro Unsigned32 .1.3.6.1.4.1.8164.1.28.4 |
starThreshMeasuredMBThe measured value of a thresholded parameterro Gauge32 UNITS "Megabytes" .1.3.6.1.4.1.8164.1.28.5 |
starThreshMBThe configured value of a thresholded parameterro Unsigned32 UNITS "Megabytes" .1.3.6.1.4.1.8164.1.28.6 |
starThreshMeasuredGBThe measured value of a thresholded parameterro Gauge32 UNITS "Gigabytes" .1.3.6.1.4.1.8164.1.28.7 |
starThreshGBThe configured value of a thresholded parameterro Unsigned32 UNITS "Gigabytes" .1.3.6.1.4.1.8164.1.28.8 |
starThreshPeriodIntThe configured value of a thresholded parameterro Integer32 .1.3.6.1.4.1.8164.1.28.9 |
starThreshDeviceNumThe configured value of a thresholded parameterro Integer32 .1.3.6.1.4.1.8164.1.28.10 |
starentPort OBJECT IDENTIFIER .1.3.6.1.4.1.8164.1.29 |
starPortTableA table containing Port information SEQUENCE OF StarPortEntry .1.3.6.1.4.1.8164.1.29.1 |
starPortEntryInformation for a specific Port StarPortEntry .1.3.6.1.4.1.8164.1.29.1.1 |
starPortSlotThe Slot number for this portro Integer32 .1.3.6.1.4.1.8164.1.29.1.1.1 |
starPortNumThe Port number within this slotro Integer32 .1.3.6.1.4.1.8164.1.29.1.1.2 |
starPortTypero Enumeration .1.3.6.1.4.1.8164.1.29.1.1.3 |
starPortTypeDescrA texual representing of the starPortType attributero DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.29.1.1.4 |
starPortAdminStateThe administrative start of the portro Enumeration .1.3.6.1.4.1.8164.1.29.1.1.5 |
starPortOperStatero Enumeration .1.3.6.1.4.1.8164.1.29.1.1.6 |
starPortOperModero Enumeration .1.3.6.1.4.1.8164.1.29.1.1.7 |
starPortLinkStatero Enumeration .1.3.6.1.4.1.8164.1.29.1.1.8 |
starRedundantPortSlotThe Slot number for the port the current port is redundant with, or 0 if unknownro Integer32 .1.3.6.1.4.1.8164.1.29.1.1.9 |
starRedundantPortNumThe Port number for the port the current port is redundant with, or 0 if unknownro Integer32 .1.3.6.1.4.1.8164.1.29.1.1.10 |
starPortRxBytesThe number of bytes successfully received, in megabytes. For ports of type rs232(8) or bitst1e1(9) this value will always be zero.ro Counter32 UNITS "Megabytes" .1.3.6.1.4.1.8164.1.29.1.1.11 |
starPortTxBytesThe number of bytes successfully transmitted, in megabytes. For ports of type rs232(8) or bitst1e1(9) this value will always be zero.ro Counter32 UNITS "Megabytes" .1.3.6.1.4.1.8164.1.29.1.1.12 |
starPortRxFramesThe number of frames successfully received, in thousands. For ports of type rs232(8) or bitst1e1(9) this value will always be zero. For ports of type oc3atm(5) and oc12atm(6) this is the count of cells receivedro Counter32 UNITS "Thousands" .1.3.6.1.4.1.8164.1.29.1.1.13 |
starPortTxFramesThe number of frames successfully transmitted, in thousands. For ports of type rs232(8) or bitst1e1(9) this value will always be zero. For ports of type oc3atm(5) and oc12atm(6) this is the count of cells receivedro Counter32 UNITS "Thousands" .1.3.6.1.4.1.8164.1.29.1.1.14 |
starPortRxDiscardsThe number of inbound packets which were chosen to be discarded even though no errors had been detected to prevent their being deliverable to a higher-layer protocol. One possible reason for discarding such a packet could be to free up buffer space.ro Counter32 .1.3.6.1.4.1.8164.1.29.1.1.15 |
starPortTxDiscardsThe number of outbound packets which were chosen to be discarded even though no errors had been detected to prevent their being transmitted. One possible reason for discarding such a packet could be to free up buffer space.ro Counter32 .1.3.6.1.4.1.8164.1.29.1.1.16 |
starPortRxErrorsThe number of inbound packets that contained errors preventing them from being deliverable to a higher-layer protocol.ro Counter32 .1.3.6.1.4.1.8164.1.29.1.1.17 |
starPortTxErrorsThe number of outbound packets that could not be transmitted because of errors.ro Counter32 UNITS "Thousands" .1.3.6.1.4.1.8164.1.29.1.1.18 |
starentIPPool OBJECT IDENTIFIER .1.3.6.1.4.1.8164.1.30 |
starIPPoolTableA table containing IP Pool information SEQUENCE OF StarIPPoolEntry .1.3.6.1.4.1.8164.1.30.1 |
starIPPoolEntryInformation for a specific IP Pool StarIPPoolEntry .1.3.6.1.4.1.8164.1.30.1.1 |
starIPPoolVpnIDThe context ID for this poolro Gauge32 .1.3.6.1.4.1.8164.1.30.1.1.1 |
starIPPoolIDThe service identification is made up from first 8 chars of context name and first 16 chars of pool name separated by (:) StarMediumID .1.3.6.1.4.1.8164.1.30.1.1.2 |
starIPPoolContextThe context name string for this poolro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.30.1.1.3 |
starIPPoolGroupThe name of the group to which the IP pool belongsro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.30.1.1.4 |
starIPPoolNameThe name of the IP poolro OCTET STRING .1.3.6.1.4.1.8164.1.30.1.1.5 |
starIPPoolTypeThe type of the poolro Enumeration .1.3.6.1.4.1.8164.1.30.1.1.6 |
starIPPoolStateThe state of the poolro Enumeration .1.3.6.1.4.1.8164.1.30.1.1.7 |
starIPPoolStartAddrThe start IP address of the poolro IpAddress .1.3.6.1.4.1.8164.1.30.1.1.8 |
starIPPoolMaskorEndAddrThe mask or end IP address of the poolro IpAddress .1.3.6.1.4.1.8164.1.30.1.1.9 |
starIPPoolPriorityThe priority of the poolro Integer32 .1.3.6.1.4.1.8164.1.30.1.1.10 |
starIPPoolUsedThe number of IP addresses in USED state in the poolro Gauge32 .1.3.6.1.4.1.8164.1.30.1.1.11 |
starIPPoolHoldThe number of IP addresses in HOLD state in the poolro Gauge32 .1.3.6.1.4.1.8164.1.30.1.1.12 |
starIPPoolReleaseThe number of IP addresses in RELEASE state in the poolro Gauge32 .1.3.6.1.4.1.8164.1.30.1.1.13 |
starIPPoolFreeThe number of IP addresses in FREE state in the poolro Gauge32 .1.3.6.1.4.1.8164.1.30.1.1.14 |
starentTrapData OBJECT IDENTIFIER .1.3.6.1.4.1.8164.1.31 |
starCongestionPolicyThe policy invoked for congestion eventsro Enumeration .1.3.6.1.4.1.8164.1.31.1 |
starCongestionResourceTypeThe resource type for a congestion eventro Enumeration .1.3.6.1.4.1.8164.1.31.2 |
starPTACConfigThe number of PACs/PSCs//TACs configured in the systemro Integer32 .1.3.6.1.4.1.8164.1.31.3 |
starPTACActiveThe number of PACs/PSCs/TACs active in the systemro Integer32 .1.3.6.1.4.1.8164.1.31.4 |
starContextNameThe name of a context configured on the IMGro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.31.5 |
starInterfaceNameThe name of an interfacero DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.31.6 |
starPCFAddressThe IP address of a PCFro IpAddress .1.3.6.1.4.1.8164.1.31.7 |
starPeerAddressPeer Addressro IpAddress .1.3.6.1.4.1.8164.1.31.8 |
starLicensedSessionsThe number of sessions enabled by the software licensero Unsigned32 .1.3.6.1.4.1.8164.1.31.9 |
starCurrentSessionsThe number of current sessions in use against a software licensero Gauge32 .1.3.6.1.4.1.8164.1.31.10 |
starL3AddressL3 Addressro IpAddress .1.3.6.1.4.1.8164.1.31.11 |
starUDPPortNumUDP Port Numberro Integer32 .1.3.6.1.4.1.8164.1.31.12 |
starSRPIpAddressSRP IP Addressro IpAddress .1.3.6.1.4.1.8164.1.31.13 |
starBGPPeerIpAddressBGP Peer IP Addressro IpAddress .1.3.6.1.4.1.8164.1.31.14 |
starContFiltCFFilenameFile name for the OPTCMDBro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.31.15 |
starContFiltCFErrorCodeError codero Enumeration .1.3.6.1.4.1.8164.1.31.16 |
starFecthedFromAAAMgrThe number calls fetched from aaa mgrro Integer32 .1.3.6.1.4.1.8164.1.31.17 |
starPriorToAuditThe number calls prior to auditro Integer32 .1.3.6.1.4.1.8164.1.31.18 |
starPassedAuditsThe number of calls passed auditro Integer32 .1.3.6.1.4.1.8164.1.31.19 |
starCallsRecoveredThe number of calls recoveredro Integer32 .1.3.6.1.4.1.8164.1.31.20 |
starAllCallLinesThe number of a11 call linesro Integer32 .1.3.6.1.4.1.8164.1.31.21 |
starElapsedMsThe audit time elapsed in msro Integer32 .1.3.6.1.4.1.8164.1.31.22 |
starCDRFilenameThe name of a CDR (EDR/UDR) filero DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.31.23 |
starDiameterVpnNameDiameter VPN (Context) Namero DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.31.24 |
starDiameterPeerAddrDiameter Peer Addressro IpAddress .1.3.6.1.4.1.8164.1.31.25 |
starDiameterEndpointNameDiameter Endpoint Namero DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.31.26 |
starInterfaceIPAddressInterface IP Addressro IpAddress .1.3.6.1.4.1.8164.1.31.27 |
starOSPFNeighborRouterIDInterface IP Addressro IpAddress .1.3.6.1.4.1.8164.1.31.28 |
starOSPFFromStateFROM state for OSPF Neighborro StarOSPFNeighborState .1.3.6.1.4.1.8164.1.31.29 |
starOSPFToStateTO state for OSPF Neighborro StarOSPFNeighborState .1.3.6.1.4.1.8164.1.31.30 |
starBLFilenameFile name for the OPTBLDBro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.31.31 |
starBLErrorCodeError codero Enumeration .1.3.6.1.4.1.8164.1.31.32 |
starDiameterECodeDiameter Cause Codero Enumeration .1.3.6.1.4.1.8164.1.31.33 |
starDiameterPeerAddrIpv6Diameter Peer Addressro Ipv6Address (IPV6-TC) .1.3.6.1.4.1.8164.1.31.34 |
starContFiltCFUpgradeFilenameFile name for the Full or Incremental OPTCMDBro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.31.35 |
starContFiltCFUpgradeErrorCodeError codero Enumeration .1.3.6.1.4.1.8164.1.31.36 |
starBLUpgradeFilenameFile name for the Full OPTBLDBro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.31.37 |
starBLUpgradeErrorCodeError codero Enumeration .1.3.6.1.4.1.8164.1.31.38 |
starDynPkgFilenameFile name for the DynPkgro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.31.39 |
starDynCFErrorCodeError codero Enumeration .1.3.6.1.4.1.8164.1.31.40 |
starDynPkgUpgradeFilenameFile name for the Full DynPkgro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.31.41 |
starDynCFUpgradeErrorCodeError codero Enumeration .1.3.6.1.4.1.8164.1.31.42 |
starCscfSessCongestionResourceTypeCscf Session resource type for a congestion eventro Enumeration .1.3.6.1.4.1.8164.1.31.43 |
starSmgrIdSession Manager Instance IDro Integer32 .1.3.6.1.4.1.8164.1.31.44 |
starEGTPVpnNameThe name of this VPN (context)ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.31.45 |
starEGTPServNameThe name of this servicero DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.31.46 |
starEGTPInterfaceTypeEgtp interface typero Enumeration .1.3.6.1.4.1.8164.1.31.47 |
starEGTPSelfPortThe Port number of the EGTPro Gauge32 .1.3.6.1.4.1.8164.1.31.48 |
starEGTPSelfAddrThe IP Address of the EGTPro IpAddress .1.3.6.1.4.1.8164.1.31.49 |
starEGTPPeerPortThe Port number of the PeerNodero Gauge32 .1.3.6.1.4.1.8164.1.31.50 |
starEGTPPeerAddrThe IP Address of the PeerNodero IpAddress .1.3.6.1.4.1.8164.1.31.51 |
starEGTPPeerOldRstCntEGTP peer old restart counterro Gauge32 .1.3.6.1.4.1.8164.1.31.52 |
starEGTPPeerNewRstCntEGTP peer new restart counterro Gauge32 .1.3.6.1.4.1.8164.1.31.53 |
starEGTPPeerSessCntEGTP peer session countro Gauge32 .1.3.6.1.4.1.8164.1.31.54 |
starEGTPFailureReasonEgtp path failure reasonro Enumeration .1.3.6.1.4.1.8164.1.31.55 |
starGSSCDRLossConfiguredThe configured value of threshold CDR Loss at GSSro Unsigned32 .1.3.6.1.4.1.8164.1.31.56 |
starGSSCDRLossMeasuredThe Measured value of CDR Loss at GSSro Unsigned32 .1.3.6.1.4.1.8164.1.31.57 |
starLicenseKeyThe license keyro Unsigned32 .1.3.6.1.4.1.8164.1.31.58 |
starLicenseExpiryDateThe license expiration date/timero DateAndTime (SNMPv2-TC) .1.3.6.1.4.1.8164.1.31.59 |
starLicenseDaysRemainingThe number of days remaining before the license expiresro Unsigned32 .1.3.6.1.4.1.8164.1.31.60 |
starLicenseDaysAfterExpiryThe number of days after the license has expiredro Unsigned32 .1.3.6.1.4.1.8164.1.31.61 |
starNPUSlotThe NPU slot numberro Integer32 .1.3.6.1.4.1.8164.1.31.62 |
starSPRServerIpAddrThe IP Address of the SSC Serverro IpAddress .1.3.6.1.4.1.8164.1.31.63 |
starMVGEndpointNameMVG Endpoint Namero DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.31.66 |
starMVGProtocolTypeMVG Protocol Typesro Enumeration .1.3.6.1.4.1.8164.1.31.68 |
starMVGCauseCodeMVG Cause Codero Enumeration .1.3.6.1.4.1.8164.1.31.69 |
starPCCNtfyIntfPeerNameIPCF Event Notification Interface Peer Namero DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.31.73 |
starECSTotalDNSLearntIPThresholdInstanceACSMgr Instance Idro Integer32 .1.3.6.1.4.1.8164.1.31.74 |
starECSTotalDNSLearntIPThresholdconfiguredConfigured Threshold value in Percentagero Integer32 .1.3.6.1.4.1.8164.1.31.75 |
starECSTotalDNSLearntIPThresholdmeasuredMeasured value in Percentagero Integer32 .1.3.6.1.4.1.8164.1.31.76 |
starPeerAddressIpv6Peer Ipv6 Addressro Ipv6Address (IPV6-TC) .1.3.6.1.4.1.8164.1.31.77 |
starLAGPartnerThe name of this servicero DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.31.78 |
starSGSServiceVpnNameSGS service context namero DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.31.79 |
starSGSServiceServNameSGS service namero DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.31.80 |
starVLRNameVLR namero DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.31.81 |
starVLRIpAddr1VLR IP Address1ro IpAddress .1.3.6.1.4.1.8164.1.31.82 |
starVLRIpAddr2VLR IP Address2ro IpAddress .1.3.6.1.4.1.8164.1.31.83 |
starVLRPortNumVLR Port Numberro Integer32 .1.3.6.1.4.1.8164.1.31.84 |
starCongestionTypeThe type congestion threshold hitro Enumeration .1.3.6.1.4.1.8164.1.31.85 |
starCongestionActionProfileNameThe name of a action profile asscociated with the threshold typero DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.31.86 |
starSessMgrFlowInstIdSession Manager instance IDro Integer32 .1.3.6.1.4.1.8164.1.31.87 |
starSessMgrFlowPDNNoTota PDNs Availablero Integer32 .1.3.6.1.4.1.8164.1.31.88 |
starSessMgrFlowMemUsageTotat Memory Usage of this instancero Integer32 .1.3.6.1.4.1.8164.1.31.89 |
starSessMgrFlowCounterSession Manager Active Flowsro Integer32 .1.3.6.1.4.1.8164.1.31.90 |
starSessMgrTotalFlowCountSession Manager Active Flowsro Integer32 .1.3.6.1.4.1.8164.1.31.91 |
starHENBGWServiceVpnNameHENBGW Service VPN Namero DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.31.92 |
starHENBGWServiceServNameHENBGW Service Namero DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.31.93 |
starHENBGWServiceLogicalENBIdHENBGW Service Logical Enodb IDro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.31.94 |
starHENBGWServiceMMEServNameHENBGW Service MME Namero DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.31.95 |
starHENBGWServiceSelfAddrHENBGW Service Self IP Address IpAddress .1.3.6.1.4.1.8164.1.31.96 |
starHENBGWServicePeerAddrHENBGW Service Peer IP Addressro IpAddress .1.3.6.1.4.1.8164.1.31.97 |
starHENBGWServiceSelfPortHENBGW Service Self Port Number Integer32 .1.3.6.1.4.1.8164.1.31.98 |
starHENBGWServicePeerPortHENBGW Service Peer Port Numberro Integer32 .1.3.6.1.4.1.8164.1.31.99 |
starNPUSlotNumberNPU Slot Numberro Integer32 .1.3.6.1.4.1.8164.1.31.100 |
starNPUCPUNumberNPU CPU Numberro Integer32 .1.3.6.1.4.1.8164.1.31.101 |
starNPUNPUNumberNPU's NPU Numberro Integer32 .1.3.6.1.4.1.8164.1.31.102 |
starChassisCrashListChassis Crash List Fullro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.8164.1.31.103 |
starLIRcvryErrTypeLI Recovery Error Typesro Enumeration .1.3.6.1.4.1.8164.1.31.104 |
starLIRcvryErrStringLI Recovery Error Stringro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.31.105 |
starPMIPVpnNameThe name of this VPN (context)ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.31.106 |
starPMIPServNameThe name of this servicero DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.31.107 |
starPMIPSelfAddrTypeThe IP Address of the PMIPro InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.4.1.8164.1.31.108 |
starPMIPSelfAddrThe IP Address of the PMIPro InetAddress (INET-ADDRESS-MIB) .1.3.6.1.4.1.8164.1.31.109 |
starPMIPPeerAddrTypeThe IP Address of the PMIPro InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.4.1.8164.1.31.110 |
starPMIPPeerAddrThe IP Address of the PMIPro InetAddress (INET-ADDRESS-MIB) .1.3.6.1.4.1.8164.1.31.111 |
starPMIPPeerOldRstCntPMIP peer old restart counterro Counter32 .1.3.6.1.4.1.8164.1.31.112 |
starPMIPPeerNewRstCntPMIP peer new restart counterro Counter32 .1.3.6.1.4.1.8164.1.31.113 |
starPMIPPeerSessCntPMIP peer session countro Counter32 .1.3.6.1.4.1.8164.1.31.114 |
starPMIPFailureReasonPMIP path failure reasonro Enumeration .1.3.6.1.4.1.8164.1.31.115 |
starMMEInitialDisallowReasonMME initial connection disallow reason.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.31.116 |
starSLSServiceVpnNameSLS service context namero DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.31.117 |
starSLSServiceServNameSLS service namero DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.31.118 |
starESMLCIdESMLC Idro Integer32 .1.3.6.1.4.1.8164.1.31.119 |
starESMLCIpAddr1ESMLC IP Address1ro IpAddress .1.3.6.1.4.1.8164.1.31.120 |
starESMLCIpAddr2ESMLC IP Address2ro IpAddress .1.3.6.1.4.1.8164.1.31.121 |
starESMLCPortNumESMLC Port Numberro Integer32 .1.3.6.1.4.1.8164.1.31.122 |
starSBCServiceVpnNameSBc service context namero DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.31.123 |
starSBCServiceServNameSBc service namero DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.31.124 |
starPeerIdPeer Idro Integer32 .1.3.6.1.4.1.8164.1.31.125 |
starPeerIpAddrPeer IP Addressro IpAddress .1.3.6.1.4.1.8164.1.31.126 |
starPeerPortNumPeer Port Numberro Integer32 .1.3.6.1.4.1.8164.1.31.127 |
starBfdSrcAddressTypeThis object specifies IP address type of the source IP address of this BFD session. Only values unknown(0), ipv4(1), ipv6(2), or ipv6z(4) have to be supported. The value of unknown(0) is allowed only when the session is singleHop(1) and the source IP address of this BFD session is derived from the outgoing interface, or when the BFD session is not associated with a specific interface.ro InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.4.1.8164.1.31.128 |
starBfdSrcAddressThis object specifies the source IP address of this BFD session.ro InetAddress (INET-ADDRESS-MIB) .1.3.6.1.4.1.8164.1.31.129 |
starBfdDstAddressTypeThis object specifies IP address type of the neighboring IP address which is being monitored with this BFD session. Only values unknown(0), ipv4(1), ipv6(2), or ipv6z(4) have to be supported. The value of unknown(0) is allowed only when the session is singleHop(1) and the outgoing interface is of type point-to-point, or when the BFD session is not associated with a specific interface.ro InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.4.1.8164.1.31.130 |
starBfdDstAddressThis object specifies the neighboring IP address which is being monitored with this BFD session.ro InetAddress (INET-ADDRESS-MIB) .1.3.6.1.4.1.8164.1.31.131 |
starBfdLocalDiscThis object specifies the local discriminator for this BFD session, used to uniquely identify itro Unsigned32 .1.3.6.1.4.1.8164.1.31.132 |
starBfdRemDiscThis object specifies the session discriminator chosen by the remote system for this BFD session. The value may be zero(0) if the remote discriminator is not yet known or if the session is in the down or adminDown(1) state.ro Unsigned32 .1.3.6.1.4.1.8164.1.31.133 |
starBfdSessDiagCodeA diagnostic code specifying the local system's reason for the last transition of the session from up(4) to some other state.ro Enumeration .1.3.6.1.4.1.8164.1.31.134 |
starSRPSwitchReasonA Switchover code specifying the SRP's Switchover reason. The following reasons would appear when chassis transitioning from Active to Standby State: notDefined(0), aaaFailure(1), bgpFailure(2), bfdFailure(3), diameterFailure(4), hsrpSwitchover(5), dualActive(7) manualSwitchOver(11), egqcFailure(12), The following reasons would appear when chassis transitioning from Standby to Pending Active State: notDefined(0), chassisChassisBfdFailure(6), deadTimerExpiry(9)ro Enumeration .1.3.6.1.4.1.8164.1.31.135 |
starHENBGWServiceTLRIHENBGW Service Overload Traffic load reduction indication percentage.ro Unsigned32 .1.3.6.1.4.1.8164.1.31.136 |
starCBSServiceVpnNameCBS service context namero DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.31.139 |
starIuBcSelfPortNumIuBc Self Port Numberro Integer32 .1.3.6.1.4.1.8164.1.31.140 |
starIuBcSelfIpAddrIuBc Self IP Addressro IpAddress .1.3.6.1.4.1.8164.1.31.141 |
starIuBcPeerPortNumPeer Port Numberro Integer32 .1.3.6.1.4.1.8164.1.31.142 |
starIuBcPeerIpAddrIuBc Peer IP Addressro IpAddress .1.3.6.1.4.1.8164.1.31.143 |
starIuBcTcpConnCauseStrIuBc Tcp Conn Cause Strro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.31.144 |
starPhyPortIdPhysical Port Id as IfIndexro Integer32 .1.3.6.1.4.1.8164.1.31.145 |
starGTPCRLFSessMgrInstSession Manager Instancero Integer32 .1.3.6.1.4.1.8164.1.31.146 |
starGTPCRLFVPNNameThe context name of VPN isro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.31.147 |
starGTPCRLFVPNIdThe context Id of VPN isro Integer32 .1.3.6.1.4.1.8164.1.31.148 |
starGTPCRLFContextNameThe name of Context isro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.31.149 |
starGTPCRLFCurrAppTPSThe current applied TPS value isro Integer32 .1.3.6.1.4.1.8164.1.31.150 |
starGTPCRLFCurrAppDelayTolThe current applied delay Tolerance value isro Integer32 .1.3.6.1.4.1.8164.1.31.151 |
starBGPPeerIpv6AddressDiameter Peer Address in IPv6ro Ipv6Address (IPV6-TC) .1.3.6.1.4.1.8164.1.31.152 |
starMMEEMBMSServiceVpnNameMME-EMBMS service context namero DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.31.153 |
starMMEEMBMSServiceServNameMME-EMBMS service namero DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.31.154 |
starMMEEMBMSPeerIdPeer Idro Integer32 .1.3.6.1.4.1.8164.1.31.155 |
starMMEEMBMSPeerIpAddrPeer IP Addressro IpAddress .1.3.6.1.4.1.8164.1.31.156 |
starMMEEMBMSPeerPortNumPeer Port Numberro Integer32 .1.3.6.1.4.1.8164.1.31.157 |
starImsimgrInstIdImsi Manager Instancero Integer32 .1.3.6.1.4.1.8164.1.31.158 |
starLAGGroupThe group number of the LAG groupro Integer32 .1.3.6.1.4.1.8164.1.31.159 |
starLAGMinlinkThe Minlink configured for this lag_groupro Integer32 .1.3.6.1.4.1.8164.1.31.160 |
starVRFNameVRF Namero DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.31.161 |
starStatFilesizeLimitThe Stat File Size in integerro Integer32 .1.3.6.1.4.1.8164.1.31.162 |
starStatFilesizeMeasuredThe Stat file Size measuredro Integer32 .1.3.6.1.4.1.8164.1.31.163 |
starentGGSNService OBJECT IDENTIFIER .1.3.6.1.4.1.8164.1.32 |
starGGSNSerTableA table containing GGSN related information SEQUENCE OF StarGGSNSerEntry .1.3.6.1.4.1.8164.1.32.1 |
starGGSNSerEntryThe statistics for a specific GGSN service StarGGSNSerEntry .1.3.6.1.4.1.8164.1.32.1.1 |
starGGSNSerVpnIDThe internal identification of the VPN (context) Gauge32 .1.3.6.1.4.1.8164.1.32.1.1.1 |
starGGSNSerSvcIDThe internal identification of this service; unique within a specific context Gauge32 .1.3.6.1.4.1.8164.1.32.1.1.2 |
starSessGGSNVpnNameThe name of this VPN (context)ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.32.1.1.3 |
starSessGGSNServNameThe name of this servicero DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.32.1.1.4 |
starSessGGSNPeerPortThe Peer Port for which PATH Failure has occuredro Gauge32 .1.3.6.1.4.1.8164.1.32.1.1.5 |
starSessGGSNPeerAddrThe Peer Address for which PATH Failure has occuredro IpAddress .1.3.6.1.4.1.8164.1.32.1.1.6 |
starSessGGSNImsiThe IMSI of the subscriberro OCTET STRING .1.3.6.1.4.1.8164.1.32.1.1.7 |
starSessGGSNSubsNameThe name of the subscriberro OCTET STRING .1.3.6.1.4.1.8164.1.32.1.1.8 |
starSessGGSNAPNNameThe name of the APNro OCTET STRING .1.3.6.1.4.1.8164.1.32.1.1.9 |
starSessGTPPGroupNameThe name of the GTPP Groupro OCTET STRING .1.3.6.1.4.1.8164.1.32.1.1.10 |
starentL2TP OBJECT IDENTIFIER .1.3.6.1.4.1.8164.1.33 |
starL2TPTableA table containing L2TP related information SEQUENCE OF StarL2TPEntry .1.3.6.1.4.1.8164.1.33.1 |
starL2TPEntryThe statistics for a L2TP entry StarL2TPEntry .1.3.6.1.4.1.8164.1.33.1.1 |
starL2TPLocalTunnelIDThe internal identification of the L2TP local tunnel IDro Unsigned32 .1.3.6.1.4.1.8164.1.33.1.1.1 |
starL2TPPeerTunnelIDThe internal identification of the L2TP peer tunnel IDro Unsigned32 .1.3.6.1.4.1.8164.1.33.1.1.2 |
starL2TPContextNameThe name of the contextro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.33.1.1.3 |
starL2TPServiceNameThe name of the servicero DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.33.1.1.4 |
starL2TPServiceTypeNameThe name of the service typero DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.33.1.1.5 |
starL2TPLocalAddressThe local address of the servicero IpAddress .1.3.6.1.4.1.8164.1.33.1.1.6 |
starL2TPPeerAddressThe peer address of the servicero IpAddress .1.3.6.1.4.1.8164.1.33.1.1.7 |
starSessSub1 OBJECT IDENTIFIER .1.3.6.1.4.1.8164.1.34 |
starSessSub1ContextThe name of the context for this subscriber. If a SET is received, triggers a lookup for a subscriber that matches the specified search criteria and fills in the various objects in this row.rw DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.34.1 |
starSessSub1NAIThe NAI for this subscriber If a SET is received, triggers a lookup for a subscriber that matches the specified search criteria and fills in the various objects in this row.rw OCTET STRING .1.3.6.1.4.1.8164.1.34.2 |
starSessSub1MSIDThe MSID for this subscriber If a SET is received, triggers a lookup for a subscriber that matches the specified search criteria and fills in the various objects in this row.rw OCTET STRING .1.3.6.1.4.1.8164.1.34.3 |
starSessSub1IpAddrThe remote IP address for this subscriber If a SET is received, triggers a lookup for a subscriber that matches the specified search criteria and fills in the various objects in this row.rw IpAddress .1.3.6.1.4.1.8164.1.34.4 |
starSessSub1LastResultThe result of the last search. A value of unknown(0) means that the query wasn't created properly, or that no query has been performed; error(1) indicates an internal error performing the query, this is an abnormal condition that shouldn't normally be seen; nomatch(2) means that the query did not find a matching subscriber; onematch(3) means that the query found exactly one subscriber; multimatch(4) means that more than one subscriber matched; the information for one (random) subscriber was fetchedro Enumeration .1.3.6.1.4.1.8164.1.34.5 |
starSessSub1ServiceNameThe service name of the subscriber.ro OCTET STRING .1.3.6.1.4.1.8164.1.34.6 |
starSessSub1HAIpAddrThe HA IP address for FA MIP connectionsro IpAddress .1.3.6.1.4.1.8164.1.34.7 |
starSessSub1PeerIpAddrThe remote IP address of the peer. The type of peer depends on the session type. Session Type Peer ------------ --------- PDSN PCF GGSN SGSN HA Mobile IP/HA IPSEC FA LAC LNS LNS LACro IpAddress .1.3.6.1.4.1.8164.1.34.8 |
starSessSub1InPacketsThe number of incoming packets for the subscriberro Counter32 .1.3.6.1.4.1.8164.1.34.9 |
starSessSub1InPacketsDroppedThe number of incoming packets dropped for the subscriberro Counter32 .1.3.6.1.4.1.8164.1.34.10 |
starSessSub1InBytesThe count of incoming bytes for the subscriber, in kilobytes, rounded down (i.e. 1023 bytes = 0 kilobytesro Counter32 UNITS "KB" .1.3.6.1.4.1.8164.1.34.11 |
starSessSub1OutPacketsThe number of outgoing packets for the subscriberro Counter32 .1.3.6.1.4.1.8164.1.34.12 |
starSessSub1OutPacketsDroppedThe number of out going packets dropped for the subscriberro Counter32 .1.3.6.1.4.1.8164.1.34.13 |
starSessSub1OutBytesThe count of outgoing bytes for the subscriber, in kilobytes, rounded down (i.e. 1023 bytes = 0 kilobytesro Counter32 UNITS "KB" .1.3.6.1.4.1.8164.1.34.14 |
starSessSub1ActivityTBDro Gauge32 UNITS "%" .1.3.6.1.4.1.8164.1.34.15 |
starSessSub1StateThe state of the subscriberro Enumeration .1.3.6.1.4.1.8164.1.34.16 |
starSessSub1CallIDThe internal call ID of the subscriberro Integer32 .1.3.6.1.4.1.8164.1.34.17 |
starSessSub1ConnectTimeThe connect time for the subscriber, in UTC. The UNIX epoch (Jan 1, 1970) is used if no value is availablero DateAndTime (SNMPv2-TC) .1.3.6.1.4.1.8164.1.34.18 |
starSessSub1CallDurationThe duration of the call, in secondsro Counter32 UNITS "Seconds" .1.3.6.1.4.1.8164.1.34.19 |
starSessSub1TimeIdleThe idle time of the call, in secondsro Gauge32 UNITS "Seconds" .1.3.6.1.4.1.8164.1.34.20 |
starSessSub1AccessTypeThe access type for the subscriberro Enumeration .1.3.6.1.4.1.8164.1.34.21 |
starSessSub1AccessTechThe access technology for the subscriberro Enumeration .1.3.6.1.4.1.8164.1.34.22 |
starSessSub1LinkStatusThe link status for the subscriberro Enumeration .1.3.6.1.4.1.8164.1.34.23 |
starSessSub1NetworkTypeThe network type for the subscriberro Enumeration .1.3.6.1.4.1.8164.1.34.24 |
starSessSub1CarrierIDCarrier IDro OCTET STRING .1.3.6.1.4.1.8164.1.34.25 |
starSessSub1ESNElectronic Serial Numberro OCTET STRING .1.3.6.1.4.1.8164.1.34.26 |
starSessSub1GMTTimezoneOffsetTimezone offset from GMT, in seconds. This is a signed valuero Integer32 UNITS "Seconds" .1.3.6.1.4.1.8164.1.34.27 |
starSessSub1SessMgrThe instance number of the session manager for this subscriber.ro Unsigned32 .1.3.6.1.4.1.8164.1.34.28 |
starSessSub1RemoteIPAddrRemote IP Addressro IpAddress .1.3.6.1.4.1.8164.1.34.29 |
starSessSub1CardThe card holding the session manager for this session. Use in combination with starSessSub1CPUro Integer32 .1.3.6.1.4.1.8164.1.34.30 |
starSessSub1CPUThe CPU holding the session manager for this session. Use in combination with starSessSub1Cardro Integer32 .1.3.6.1.4.1.8164.1.34.31 |
starSessSub1TimeIdleLeftThe remaining idle time of the call, in seconds. A value of 0xffffffff is used if the call does not have an idle timeoutro Gauge32 UNITS "Seconds" .1.3.6.1.4.1.8164.1.34.32 |
starSessSub1TimeLeftThe remaining session time of the call, in seconds. A value of 0xffffffff is used if the call does not have a session timeoutro Gauge32 UNITS "Seconds" .1.3.6.1.4.1.8164.1.34.33 |
starSessSub1TimeLongDurLeftThe remaining long duration time of the call, in seconds. A value of 0xffffffff is used if the call does not have a long duration timerro Gauge32 UNITS "Seconds" .1.3.6.1.4.1.8164.1.34.34 |
starSessSub1LongDurActionThe action to take when the long duration timer is reachedro StarLongDurTimeoutAction .1.3.6.1.4.1.8164.1.34.35 |
starSessSub1AlwaysOnro Enumeration .1.3.6.1.4.1.8164.1.34.36 |
starSessSub1IPPoolNamero OCTET STRING .1.3.6.1.4.1.8164.1.34.37 |
starSessSub1VLANID0 is returned if this is not applicablero Unsigned32 .1.3.6.1.4.1.8164.1.34.38 |
starSessSub1LNSIPAddrOnly valid if starSessSub1NetworkType is l2tp(3), otherwise 0.0.0.0ro IpAddress .1.3.6.1.4.1.8164.1.34.39 |
starSessSub1ProxyMIPro Enumeration .1.3.6.1.4.1.8164.1.34.40 |
starSessSub1GGSNMIPro Enumeration .1.3.6.1.4.1.8164.1.34.41 |
starSessSub1HomeAgentIpAddrThe IP address of the Home Agent. This value is applicable only if one of the following is true: 1. The value of starSessSub1AccessType is pdsnmobileip(2) 2. The value of starSessSub1ProxyMIP is enabled(1) 3. The value of starSessSub1GGSNMIP is enabled(1) If not applicable, a value of 0.0.0.0 will be returnedro IpAddress .1.3.6.1.4.1.8164.1.34.42 |
starSessSub1LocalIPAddrThe Local IP address of the Home Agent. This value is applicable only if one of the following is true: 1. The value of starSessSub1AccessType is pdsnsimpleip(1) 2. The value of starSessSub1AccessType is ggsnpdptypeppp(5) 3. The value of starSessSub1AccessType is lnsl2tp(7) If not applicable, a value of 0.0.0.0 will be returnedro IpAddress .1.3.6.1.4.1.8164.1.34.43 |
starSessSub1FAServiceNameThe FA service name for the subscriber. This value is applicable only if one of the following is true: 1. The value of starSessSub1AccessType is pdsnmobileip(2) 2. The value of starSessSub1ProxyMIP is enabled(1) 3. The value of starSessSub1GGSNMIP is enabled(1)ro OCTET STRING .1.3.6.1.4.1.8164.1.34.44 |
starSessSub1FAVPNNameThe FA VPN (Context) name. This value is applicable only if one of the following is true: 1. The value of starSessSub1AccessType is pdsnmobileip(2) 2. The value of starSessSub1ProxyMIP is enabled(1) 3. The value of starSessSub1GGSNMIP is enabled(1)ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.34.45 |
starSessSub1SourceVPNThe Source VPN (Context) name.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.34.46 |
starSessSub1DestVPNThe Destination VPN (Context) name.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.34.47 |
starSessSub1AAAVPNro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.34.48 |
starSessSub1AAADomainro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.34.49 |
starSessSub1AAAStartro Counter32 .1.3.6.1.4.1.8164.1.34.50 |
starSessSub1AAAStopro Counter32 .1.3.6.1.4.1.8164.1.34.51 |
starSessSub1AAAInterimro Counter32 .1.3.6.1.4.1.8164.1.34.52 |
starSessSub1AcctSessionIDro OCTET STRING .1.3.6.1.4.1.8164.1.34.53 |
starSessSub1AAARadiusGroupro OCTET STRING .1.3.6.1.4.1.8164.1.34.54 |
starSessSub1AAARadiusAuthServerIPAddrro IpAddress .1.3.6.1.4.1.8164.1.34.55 |
starSessSub1AAARadiusAcctServerIPAddrro IpAddress .1.3.6.1.4.1.8164.1.34.56 |
starSessSub1NASIPAddrNAS IP Address (D2)ro IpAddress .1.3.6.1.4.1.8164.1.34.57 |
starSessSub1NexthopIPAddrro IpAddress .1.3.6.1.4.1.8164.1.34.58 |
starSessSub1ActiveInACLro OCTET STRING .1.3.6.1.4.1.8164.1.34.59 |
starSessSub1ActiveOutACLro OCTET STRING .1.3.6.1.4.1.8164.1.34.60 |
starSessSub1ECSRulebasero OCTET STRING .1.3.6.1.4.1.8164.1.34.61 |
starSessSub1InPlcyGrpro OCTET STRING .1.3.6.1.4.1.8164.1.34.62 |
starSessSub1OutPlcyGrpro OCTET STRING .1.3.6.1.4.1.8164.1.34.63 |
starSessSub1DownTrafPolStateDownlink traffic policing statero Enumeration .1.3.6.1.4.1.8164.1.34.64 |
starSessSub1DownCommDataRateDownlink committed data rate, in bps. This value is only valid if starSessSub1DownTrafPolState is enabled(1)ro Unsigned32 UNITS "bps" .1.3.6.1.4.1.8164.1.34.65 |
starSessSub1DownPeakDataRateDownlink peak data rate, in bps. This value will be 0 if the value of starSessSub1DownTrafPolState is anything other than enabled(1)ro Unsigned32 UNITS "bps" .1.3.6.1.4.1.8164.1.34.66 |
starSessSub1DownBurstSizeDownlink burst size, in bytes. This value will be 0 if the value of starSessSub1DownTrafPolState is anything other than enabled(1)ro Unsigned32 UNITS "bytes" .1.3.6.1.4.1.8164.1.34.67 |
starSessSub1DownExceedActionDownlink Exceed Action. This value will be notapplicable(1) if the value of starSessSub1DownTrafPolState is anything other than enabled(1)ro StarQOSTPAction .1.3.6.1.4.1.8164.1.34.68 |
starSessSub1DownViolateActionDownlink Violate Action. This value will be notapplicable(1) if the value of starSessSub1DownTrafPolState is anything other than enabled(1)ro StarQOSTPAction .1.3.6.1.4.1.8164.1.34.69 |
starSessSub1DownExceedDownlink packets exceeded bandwidth parametersro Counter32 UNITS "packets" .1.3.6.1.4.1.8164.1.34.70 |
starSessSub1DownViolateDownlink packets violated bandwidth parametersro Counter32 UNITS "packets" .1.3.6.1.4.1.8164.1.34.71 |
starSessSub1UpTrafPolStateUplink traffic policing statero Enumeration .1.3.6.1.4.1.8164.1.34.72 |
starSessSub1UpCommDataRateUplink committed data rate, in bps. This value is only valid if starSessSub1UpTrafPolState is enabled(1)ro Unsigned32 UNITS "bps" .1.3.6.1.4.1.8164.1.34.73 |
starSessSub1UpPeakDataRateUplink peak data rate, in bps. This value will be 0 if the value of starSessSub1UpTrafPolState is anything other than enabled(1)ro Unsigned32 UNITS "bps" .1.3.6.1.4.1.8164.1.34.74 |
starSessSub1UpBurstSizeUplink burst size, in bytes. This value will be 0 if the value of starSessSub1UpTrafPolState is anything other than enabled(1)ro Unsigned32 UNITS "bytes" .1.3.6.1.4.1.8164.1.34.75 |
starSessSub1UpExceedActionUplink Exceed Action. This value will be notapplicable(1) if the value of starSessSub1UpTrafPolState is anything other than enabled(1)ro StarQOSTPAction .1.3.6.1.4.1.8164.1.34.76 |
starSessSub1UpViolateActionUplink Violate Action. This value will be notapplicable(1) if the value of starSessSub1UpTrafPolState is anything other than enabled(1)ro StarQOSTPAction .1.3.6.1.4.1.8164.1.34.77 |
starSessSub1UpExceedUplink packets exceeded bandwidth parametersro Counter32 UNITS "packets" .1.3.6.1.4.1.8164.1.34.78 |
starSessSub1UpViolateUplink packets violated bandwidth parametersro Counter32 UNITS "packets" .1.3.6.1.4.1.8164.1.34.79 |
starSessSub1L3TunnelingStateIdentifies if L3 tunneling is enabled. This value should be enabled(1) if starSessSub1NetworkType is ipinip(5) or gre(6)ro Enumeration .1.3.6.1.4.1.8164.1.34.80 |
starSessSub1L3TunLocalIPAddrL3 tunnel local address. This value is valid only if starSessSub1L3TunnelState is enabled(1), other it will be 0.0.0.0ro IpAddress .1.3.6.1.4.1.8164.1.34.81 |
starSessSub1L3TunRemoteIPAddrL3 tunnel remote address. This value is valid only if starSessSub1L3TunnelState is enabled(1), other it will be 0.0.0.0ro IpAddress .1.3.6.1.4.1.8164.1.34.82 |
starSessSub1AddrViaDHCPro Enumeration .1.3.6.1.4.1.8164.1.34.83 |
starSessSub1DHCPServNameDHCP service name. This value is only valid if starSessSub1DHCPAddrViaDHCP is enabled(1)ro OCTET STRING .1.3.6.1.4.1.8164.1.34.84 |
starSessSub1DHCPServIPAddrDHCP service IP address. This value is only valid if starSessSub1DHCPAddrViaDHCP is enabled(1), otherwise it will be 0.0.0.0ro IpAddress .1.3.6.1.4.1.8164.1.34.85 |
starSessSub1AccessLinkIPFragro Enumeration .1.3.6.1.4.1.8164.1.34.86 |
starSessSub1IgnoreDFBitIgnore DF-bit data-tunnelro Enumeration .1.3.6.1.4.1.8164.1.34.87 |
starSessSub1MIPGratARPModeThis field is only applicable if starSessSub1AccessType is hamobileip(3) or haipsec(8)ro Enumeration .1.3.6.1.4.1.8164.1.34.88 |
starSessSub1ExtInlSrvrProcThe state of external inline server processingro Enumeration .1.3.6.1.4.1.8164.1.34.89 |
starSessSub1ExtInlSrvrIngrIPAddrThe external inline server ingress IP address. This value is only valid if starSessSub1ExtInlSrvrProc is enabled(1)ro IpAddress .1.3.6.1.4.1.8164.1.34.90 |
starSessSub1ExtInlSrvrIngrVLANTagThe external inline server ingress VLAN tag. This value is only valid if starSessSub1ExtInlSrvrProc is enabled(1)ro Unsigned32 .1.3.6.1.4.1.8164.1.34.91 |
starSessSub1ExtInlSrvrEgrIPAddrThe external inline server egress IP address. This value is only valid if starSessSub1ExtInlSrvrProc is enabled(1)ro IpAddress .1.3.6.1.4.1.8164.1.34.92 |
starSessSub1ExtInlSrvrEgrVLANTagThe external inline server egress VLAN tag. This value is only valid if starSessSub1ExtInlSrvrProc is enabled(1)ro Unsigned32 .1.3.6.1.4.1.8164.1.34.93 |
starSessSub1ExtInlSrvrVPNNameThe external inline server context (VPN). This value is only valid if starSessSub1ExtInlSrvrProc is enabled(1)ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.34.94 |
starSessSub1RadAcctModeRadius Accounting Modero Enumeration .1.3.6.1.4.1.8164.1.34.95 |
starSessSub1InBytesDroppedThe count of incoming bytes dropped for the subscriber, in kilobytes, rounded down (i.e. 1023 bytes = 0 kilobytesro Counter32 UNITS "KB" .1.3.6.1.4.1.8164.1.34.96 |
starSessSub1OutBytesDroppedThe count of outgoing bytes dropped for the subscriber, in kilobytes, rounded down (i.e. 1023 bytes = 0 kilobytesro Counter32 UNITS "KB" .1.3.6.1.4.1.8164.1.34.97 |
starSessSub1PeakBPSTxPeak rate from user, in bytes per secondro Gauge32 UNITS "Bytes per second" .1.3.6.1.4.1.8164.1.34.98 |
starSessSub1PeakBPSRxPeak rate to user, in bytes per secondro Gauge32 UNITS "Bytes per second" .1.3.6.1.4.1.8164.1.34.99 |
starSessSub1AveBPSTxAverage rate from user, in bytes per secondro Gauge32 UNITS "Bytes per second" .1.3.6.1.4.1.8164.1.34.100 |
starSessSub1AveBPSRxAverage rate to user, in bytes per secondro Gauge32 UNITS "Bytes per second" .1.3.6.1.4.1.8164.1.34.101 |
starSessSub1SustBPSTxSustained rate from user, in bytes per secondro Gauge32 UNITS "Bytes per second" .1.3.6.1.4.1.8164.1.34.102 |
starSessSub1SustBPSRxSustained rate to user, in bytes per secondro Gauge32 UNITS "Bytes per second" .1.3.6.1.4.1.8164.1.34.103 |
starSessSub1PeakPPSTxPeak rate from user, in packets per secondro Gauge32 UNITS "Packets per second" .1.3.6.1.4.1.8164.1.34.104 |
starSessSub1PeakPPSRxPeak rate to user, in packets per secondro Gauge32 UNITS "Packets per second" .1.3.6.1.4.1.8164.1.34.105 |
starSessSub1AvePPSTxAverage rate from user, in packets per secondro Gauge32 UNITS "Packets per second" .1.3.6.1.4.1.8164.1.34.106 |
starSessSub1AvePPSRxAverage rate to user, in packets per secondro Gauge32 UNITS "Packets per second" .1.3.6.1.4.1.8164.1.34.107 |
starSessSub1SustPPSTxSustained rate from user, in packets per secondro Gauge32 UNITS "Packets per second" .1.3.6.1.4.1.8164.1.34.108 |
starSessSub1SustPPSRxSustained rate to user, in packets per secondro Gauge32 UNITS "Packets per second" .1.3.6.1.4.1.8164.1.34.109 |
starSessSub1ActivePctLink online/active percentagero Integer32 .1.3.6.1.4.1.8164.1.34.110 |
starSessSub1IPv4BadHdrIPv4 Bad Headersro Counter32 .1.3.6.1.4.1.8164.1.34.111 |
starSessSub1IPv4TtlExceededIPv4 Total Exceededro Counter32 .1.3.6.1.4.1.8164.1.34.112 |
starSessSub1IPv4FragSentIPv4 Fragments sentro Counter32 .1.3.6.1.4.1.8164.1.34.113 |
starSessSub1IPv4FragFailIPv4 Could Not Fragment errorsro Counter32 .1.3.6.1.4.1.8164.1.34.114 |
starSessSub1IPv4InACLDropIPv4 Input ACL Dropsro Counter32 .1.3.6.1.4.1.8164.1.34.115 |
starSessSub1IPv4OutACLDropIPv5 Output ACL Dropsro Counter32 .1.3.6.1.4.1.8164.1.34.116 |
starSessSub1IPv4InCSSDownDropIPv4 Input CSS Down Dropsro Counter32 .1.3.6.1.4.1.8164.1.34.117 |
starSessSub1IPv4OutCSSDownDropIPv4 Output CSS Down Dropsro Counter32 .1.3.6.1.4.1.8164.1.34.118 |
starSessSub1IPv4OutXOFFDropPktIPv4 Output XOFF Packets Dropro Counter32 UNITS "packets" .1.3.6.1.4.1.8164.1.34.119 |
starSessSub1IPv4OutXOFFDropByteIPv4 Output XOFF Bytes Dropro Counter32 .1.3.6.1.4.1.8164.1.34.120 |
starSessSub1IPv4SrcViolIPv4 Source Violationsro Counter32 .1.3.6.1.4.1.8164.1.34.121 |
starSessSub1IPv4ProxyDNSRedirIPv4 Proxy-DNS Redirectro Counter32 .1.3.6.1.4.1.8164.1.34.122 |
starSessSub1IPv4SrcProxyDNSPThruIPv4 Proxy-DNS Pass-Thruro Counter32 .1.3.6.1.4.1.8164.1.34.123 |
starSessSub1IPv4ProxyDNSDropIPv4 Proxy-DNS Dropro Counter32 .1.3.6.1.4.1.8164.1.34.124 |
starSessSub1IPv4SrcViolNoAcctIPv4 Source Violations No Accountro Counter32 .1.3.6.1.4.1.8164.1.34.125 |
starSessSub1IPv4SrcViolIgnoredIPv4 Source Violations Ignoredro Counter32 .1.3.6.1.4.1.8164.1.34.126 |
starSessSub1ExtInlSrvrTxPktPackets transmitted to inline server. This value is valid only if the value of starSessSub1ExtInlSrvrProc is enabled(1)ro Counter32 UNITS "packets" .1.3.6.1.4.1.8164.1.34.127 |
starSessSub1ExtInlSrvrRxPktPackets received from inline server. This value is valid only if the value of starSessSub1ExtInlSrvrProc is enabled(1)ro Counter32 UNITS "packets" .1.3.6.1.4.1.8164.1.34.128 |
starSessSub1IPv4ICMPDropPktIPv4 ICMP Packets droppedro Counter32 UNITS "packets" .1.3.6.1.4.1.8164.1.34.129 |
starSessSub1TunnelTypeTunnel Typero Enumeration .1.3.6.1.4.1.8164.1.34.130 |
starSessSub1IPSECTunDownDropPktPool IPSEC tunnel down packets dropped. This value is only valid if the value of starSessSub1TunnelType is esp(6)ro Counter32 UNITS "packets" .1.3.6.1.4.1.8164.1.34.131 |
starSessSub1IPSECFlowIDIP Pool IPSEC flow id. This value is only valid if the value of starSessSub1TunnelType is esp(6)ro Integer32 .1.3.6.1.4.1.8164.1.34.132 |
starSessSub1DormancyTotalDormancy total. This value is not valid if the value of starSessSub1AccessType is ggsnpdptypeipv4(4) or ggsnpdptypeppp(5)ro Counter32 .1.3.6.1.4.1.8164.1.34.133 |
starSessSub1HandoffTotalHandoff total. This value is not valid if the value of starSessSub1AccessType is ggsnpdptypeipv4(4) or ggsnpdptypeppp(5)ro Counter32 .1.3.6.1.4.1.8164.1.34.134 |
starSessSub1AccessFlowsAccess flowsro Gauge32 .1.3.6.1.4.1.8164.1.34.135 |
starSessSub1TFTNumber of TFTsro Gauge32 .1.3.6.1.4.1.8164.1.34.136 |
starSessSub1NASPortNAS portro Integer32 .1.3.6.1.4.1.8164.1.34.137 |
starSessSub1CorrIDThreeGPP2-correlation-id (C2)ro OCTET STRING .1.3.6.1.4.1.8164.1.34.139 |
starSessSub1L2TPPeerIPAddrL2TP Peer address. This value is only valid if the value of starSessSub1NetworkType is l2tp(3)ro IpAddress .1.3.6.1.4.1.8164.1.34.140 |
starSessSub1IPv4EarlyPDURecvIPv4 early PDU receivedro Counter32 .1.3.6.1.4.1.8164.1.34.141 |
starentNwReachServer OBJECT IDENTIFIER .1.3.6.1.4.1.8164.1.35 |
starNwReachTableA table containing Network Reacheable Server information SEQUENCE OF StarNwReachEntry .1.3.6.1.4.1.8164.1.35.1 |
starNwReachEntryInformation for a specific Ntw Reachable Server StarNwReachEntry .1.3.6.1.4.1.8164.1.35.1.1 |
starNwReachNameThe Name for this Network Reacheable Serverro OCTET STRING .1.3.6.1.4.1.8164.1.35.1.1.1 |
starNwReachSrvrAddrThe IP Address for the Network Reacheable Serverro IpAddress .1.3.6.1.4.1.8164.1.35.1.1.2 |
starentIPSEC OBJECT IDENTIFIER .1.3.6.1.4.1.8164.1.36 |
starIPSECContextNameThe name of a contextro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.36.1 |
starIPSECGroupNameThe name of a crypto groupro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.36.2 |
starIPSECTunLocalIpAddrThe local IP Address for an IPSEC tunnelro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.36.3 |
starIPSECTunRemoteIpAddrThe remote IP Address for an IPSEC tunnelro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.36.4 |
starIPSECPolicyNameAn IPSEC policy namero DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.36.5 |
starIPSECDynPolicyTypeAn IPSEC dynamic policy type. Note that the value test(5) is used only for internal testingro Enumeration .1.3.6.1.4.1.8164.1.36.6 |
starIPSECDynPolicyPayloadTypeAn IPSEC dynamic policy payload typero Enumeration .1.3.6.1.4.1.8164.1.36.7 |
starIPSECLocalGatewayro IpAddress .1.3.6.1.4.1.8164.1.36.8 |
starIPSECRemoteGatewayro IpAddress .1.3.6.1.4.1.8164.1.36.9 |
starentSIPRoute OBJECT IDENTIFIER .1.3.6.1.4.1.8164.1.37 |
starSIPRouteTableA table containing SIPRoute related information SEQUENCE OF StarSIPRouteEntry .1.3.6.1.4.1.8164.1.37.1 |
starSIPRouteEntryThe statistics for a specific SIPRoute service StarSIPRouteEntry .1.3.6.1.4.1.8164.1.37.1.1 |
starSIPRouteVpnIDThe internal identification of the VPN (context) Gauge32 .1.3.6.1.4.1.8164.1.37.1.1.1 |
starSIPRouteVpnNameThe name of this VPN (context)ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.37.1.1.2 |
starSIPRouteVmgNameThe name of this VMG (context)ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.37.1.1.3 |
starSIPRouteAsNameThe name of this AS (context)ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.37.1.1.4 |
starSIPRouteDestPartyNumThe dest. party numberro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.37.1.1.5 |
starSIPRouteReqNumThe request numberro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.37.1.1.6 |
starentRPServiceOption OBJECT IDENTIFIER .1.3.6.1.4.1.8164.1.38 |
starRPServiceOptionTable SEQUENCE OF StarRPServiceOptionEntry .1.3.6.1.4.1.8164.1.38.1 |
starRPServiceOptionEntry StarRPServiceOptionEntry .1.3.6.1.4.1.8164.1.38.1.1 |
starRPServiceOptionNum Integer32 .1.3.6.1.4.1.8164.1.38.1.1.1 |
starRPServiceOptionCallsro Gauge32 .1.3.6.1.4.1.8164.1.38.1.1.2 |
starentPCFStats OBJECT IDENTIFIER .1.3.6.1.4.1.8164.1.39 |
starPCFStatTableA table of per-PCF statistics SEQUENCE OF StarPCFStatEntry .1.3.6.1.4.1.8164.1.39.1 |
starPCFStatEntryThe statistics for a specific PCF StarPCFStatEntry .1.3.6.1.4.1.8164.1.39.1.1 |
starPCFStatVpnID Gauge32 .1.3.6.1.4.1.8164.1.39.1.1.1 |
starPCFStatIpAddr IpAddress .1.3.6.1.4.1.8164.1.39.1.1.2 |
starPCFStatVpnNamero DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.39.1.1.3 |
starPCFStatRxPktsro Counter32 UNITS "Millions" .1.3.6.1.4.1.8164.1.39.1.1.4 |
starPCFStatTxPktsro Counter32 UNITS "Millions" .1.3.6.1.4.1.8164.1.39.1.1.5 |
starPCFStatRxBytesro Counter32 UNITS "Megabytes" .1.3.6.1.4.1.8164.1.39.1.1.6 |
starPCFStatTxBytesro Counter32 UNITS "Megabytes" .1.3.6.1.4.1.8164.1.39.1.1.7 |
starPCFStatTotalSessionsro Counter32 .1.3.6.1.4.1.8164.1.39.1.1.8 |
starPCFStatCurrentSessionsro Gauge32 .1.3.6.1.4.1.8164.1.39.1.1.9 |
starPCFStatCurrentActiveSessionsro Gauge32 .1.3.6.1.4.1.8164.1.39.1.1.10 |
starPCFStatCurrentDormantSessionsro Gauge32 .1.3.6.1.4.1.8164.1.39.1.1.11 |
starPCFStatCurrentSIPConnectedro Gauge32 .1.3.6.1.4.1.8164.1.39.1.1.12 |
starPCFStatCurrentMIPConnectedro Gauge32 .1.3.6.1.4.1.8164.1.39.1.1.13 |
starPCFStatCurrentPMIPConnectedro Gauge32 .1.3.6.1.4.1.8164.1.39.1.1.14 |
starPCFStatCurrentL2TPLACConnectedro Gauge32 .1.3.6.1.4.1.8164.1.39.1.1.15 |
starPCFStatCurrentOtherConnectedro Gauge32 .1.3.6.1.4.1.8164.1.39.1.1.16 |
starPCFTableA table of per service PCF statistics SEQUENCE OF StarPCFEntry .1.3.6.1.4.1.8164.1.39.2 |
starPCFEntryThe statistics for a specific PCF per service StarPCFEntry .1.3.6.1.4.1.8164.1.39.2.1 |
starPCFSvcIDThe service identification is made up from first 8 chars of context name and first 8 chars of service name separated by (:), with the lengh of this structure at the beginning StarShortID .1.3.6.1.4.1.8164.1.39.2.1.1 |
starPCFIpAddrThe PCF IP address IpAddress .1.3.6.1.4.1.8164.1.39.2.1.2 |
starPCFVpnIDThe internal identification of the VPN (context)ro Gauge32 .1.3.6.1.4.1.8164.1.39.2.1.3 |
starPCFVpnNameThe VPN (context) namero DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.39.2.1.4 |
starPCFServNameThe name of this servicero DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.39.2.1.5 |
starPCFRrqRcvdNumber of rrq receivedro Counter32 .1.3.6.1.4.1.8164.1.39.2.1.6 |
starPCFRrqAcceptedNumber of rrq acceptedro Counter32 .1.3.6.1.4.1.8164.1.39.2.1.7 |
starPCFRrqDeniedNumber of rrq deniedro Counter32 .1.3.6.1.4.1.8164.1.39.2.1.8 |
starPCFRrqDiscardedNumber of rrq discardedro Counter32 .1.3.6.1.4.1.8164.1.39.2.1.9 |
starPCFInitialRrqRcvdInitial rrq receivedro Counter32 .1.3.6.1.4.1.8164.1.39.2.1.10 |
starPCFInitialRrqAcceptedInitial rrq acceptedro Counter32 .1.3.6.1.4.1.8164.1.39.2.1.11 |
starPCFIntraPDSNActiveHORrqAcceptedIntra PDSN active handoff rrq acceptedro Counter32 .1.3.6.1.4.1.8164.1.39.2.1.12 |
starPCFIntraPDSNDormantHORrqAcceptedIntra PDSN dormant handoff rrq acceptedro Counter32 .1.3.6.1.4.1.8164.1.39.2.1.13 |
starPCFInterPDSNHORrqAcceptedInter PDSN handoff rrq accptedro Counter32 .1.3.6.1.4.1.8164.1.39.2.1.14 |
starPCFInitialRrqDeniedIntial rrq deniedro Counter32 .1.3.6.1.4.1.8164.1.39.2.1.15 |
starPCFInitialRrqDiscardedIntial rrq discardedro Counter32 .1.3.6.1.4.1.8164.1.39.2.1.16 |
starPCFRenewRrqRcvdRenew rrq receivedro Counter32 .1.3.6.1.4.1.8164.1.39.2.1.17 |
starPCFRenewRrqAcceptedRenew rrq acceptedro Counter32 .1.3.6.1.4.1.8164.1.39.2.1.18 |
starPCFRenewActiveRrqAcceptedRenew active rrq acceptedro Counter32 .1.3.6.1.4.1.8164.1.39.2.1.19 |
starPCFRenewDormantRrqAcceptedRenew dormant rrq acceptedro Counter32 .1.3.6.1.4.1.8164.1.39.2.1.20 |
starPCFRenewRrqDeniedRenew rrq deniedro Counter32 .1.3.6.1.4.1.8164.1.39.2.1.21 |
starPCFRenewRrqDiscardedRenew rrq discardedro Counter32 .1.3.6.1.4.1.8164.1.39.2.1.22 |
starPCFDeregRrqRcvdDeregistration rrq receivedro Counter32 .1.3.6.1.4.1.8164.1.39.2.1.23 |
starPCFDeregRrqAcceptedDeregistration rrq acceptedro Counter32 .1.3.6.1.4.1.8164.1.39.2.1.24 |
starPCFDeregDormantRrqAcceptedDeregistration dormant rrq acceptedro Counter32 .1.3.6.1.4.1.8164.1.39.2.1.25 |
starPCFDeregRrqDeniedDeregistration rrq deniedro Counter32 .1.3.6.1.4.1.8164.1.39.2.1.26 |
starPCFDeregRrqDiscardedDeregistration rrq discardedro Counter32 .1.3.6.1.4.1.8164.1.39.2.1.27 |
starPCFIntraPDSNActiveAnidHORrqAcceptedIntra PDSN active anid handoff rrq acceptedro Counter32 .1.3.6.1.4.1.8164.1.39.2.1.28 |
starPCFIntraPDSNDormantAnidHORrqAcceptedIntra PDSN dormant anidhandoff rrq acceptedro Counter32 .1.3.6.1.4.1.8164.1.39.2.1.29 |
starPCFDeniedUnSpeReasonDenied unspecified reasonro Counter32 .1.3.6.1.4.1.8164.1.39.2.1.30 |
starPCFDeniedAdmProhDenied admin prohibitedro Counter32 .1.3.6.1.4.1.8164.1.39.2.1.31 |
starPCFDeniedInsufResourceDenied insufficient resourcesro Counter32 .1.3.6.1.4.1.8164.1.39.2.1.32 |
starPCFDeniedMobNodeAuthFailDenied mobile node authentication failurero Counter32 .1.3.6.1.4.1.8164.1.39.2.1.33 |
starPCFDeniedIdentMismatchDenied identification mismatchro Counter32 .1.3.6.1.4.1.8164.1.39.2.1.34 |
starPCFDeniedPoorFormedReqDenied poor formed requestro Counter32 .1.3.6.1.4.1.8164.1.39.2.1.35 |
starPCFDeniedUnknownPDSNAddrDenied unknown PDSN addressro Counter32 .1.3.6.1.4.1.8164.1.39.2.1.36 |
starPCFDeniedRevTunnelUnavailDenied rev tunnel unavilablero Counter32 .1.3.6.1.4.1.8164.1.39.2.1.37 |
starPCFDeniedRevTunnelRequireDenied rev tunnel requiredro Counter32 .1.3.6.1.4.1.8164.1.39.2.1.38 |
starPCFDeniedUnrecogVendorIdDenied unrecognized vendor idro Counter32 .1.3.6.1.4.1.8164.1.39.2.1.39 |
starPCFDeniedSessionClosedDenied session closedro Counter32 .1.3.6.1.4.1.8164.1.39.2.1.40 |
starPCFDeniedBsnSessionInfoUnavailDenied bsn session information unavilablero Counter32 .1.3.6.1.4.1.8164.1.39.2.1.41 |
starPCFRegUpdTransmittedRegistration updates transmittedro Counter32 .1.3.6.1.4.1.8164.1.39.2.1.42 |
starPCFRegUpdAcceptedRegistration updates acceptedro Counter32 .1.3.6.1.4.1.8164.1.39.2.1.43 |
starPCFRegUpdateRpLifetimeExpiryRegistration update rp life time expiryro Counter32 .1.3.6.1.4.1.8164.1.39.2.1.44 |
starPCFRegUpdateUpperLayerIntiatedRegistration update upper layer intiatedro Counter32 .1.3.6.1.4.1.8164.1.39.2.1.45 |
starPCFRegUpdateOtherReasonRegistration update other reasonro Counter32 .1.3.6.1.4.1.8164.1.39.2.1.46 |
starPCFRegUpdateHOReleaseRegistration update handoff releasero Counter32 .1.3.6.1.4.1.8164.1.39.2.1.47 |
starPCFRegUpdateSessmgrDiedRegistration update sessmgr deniedro Counter32 .1.3.6.1.4.1.8164.1.39.2.1.48 |
starPCFAuxA10ConnectionsSetupAux a10 connections setupro Counter32 .1.3.6.1.4.1.8164.1.39.2.1.49 |
starPCFSessionsDeniedNumber of sessions deniedro Counter32 .1.3.6.1.4.1.8164.1.39.2.1.50 |
starPCFSessionsInitNumber of sessions initiatedro Counter32 .1.3.6.1.4.1.8164.1.39.2.1.51 |
starPCFSessionsRenegNumber of PCF sessions renegotiatedro Counter32 .1.3.6.1.4.1.8164.1.39.2.1.52 |
starPCFDiscLcpRemoteDisconnect reason lcp remotero Counter32 .1.3.6.1.4.1.8164.1.39.2.1.53 |
starPCFDiscRpRemoteDisconnect reason rp remotero Counter32 .1.3.6.1.4.1.8164.1.39.2.1.54 |
starPCFDiscRpLocalDisconnect reason rp localro Counter32 .1.3.6.1.4.1.8164.1.39.2.1.55 |
starPCFDiscMaxIpcpRetrDisconnect reason ppp maximum ipcp retriesro Counter32 .1.3.6.1.4.1.8164.1.39.2.1.56 |
starPCFDiscMaxIpv6cpRetrDisconnect reason max ipv6cp retriesro Counter32 .1.3.6.1.4.1.8164.1.39.2.1.57 |
starPCFDiscMaxLcpRetrDisconnect reason max lcp retriesro Counter32 .1.3.6.1.4.1.8164.1.39.2.1.58 |
starPCFDiscAuthFailDisconnect reason authentication failurero Counter32 .1.3.6.1.4.1.8164.1.39.2.1.59 |
starPCFDiscSessSetupTimeoutDisconnect reason session setup timeoutro Counter32 .1.3.6.1.4.1.8164.1.39.2.1.60 |
starPCFDiscFlowAddFailDisconnect reason flow add failurero Counter32 .1.3.6.1.4.1.8164.1.39.2.1.61 |
starPCFDiscInvDestContextDisconnect reason invalid destination contextro Counter32 .1.3.6.1.4.1.8164.1.39.2.1.62 |
starPCFDiscLcpOptFailDisconnect reason lcp option failurero Counter32 .1.3.6.1.4.1.8164.1.39.2.1.63 |
starPCFDiscIpcpOptFailDisconnect reason lcp option failurero Counter32 .1.3.6.1.4.1.8164.1.39.2.1.64 |
starPCFDiscIpv6cpOptFailDisconnect reason ipv6cp option failurero Counter32 .1.3.6.1.4.1.8164.1.39.2.1.65 |
starPCFDiscNoRemIpAddrDisconnect reason no ip remote ip addressro Counter32 .1.3.6.1.4.1.8164.1.39.2.1.66 |
starPCFDiscDetectionFailDisconnect reason detection failurero Counter32 .1.3.6.1.4.1.8164.1.39.2.1.67 |
starPCFDiscMiscDisconnect reason misallaneousro Counter32 .1.3.6.1.4.1.8164.1.39.2.1.68 |
starPCFCurrentSessionsCurrent sessionsro Gauge32 .1.3.6.1.4.1.8164.1.39.2.1.69 |
starPCFSessionsSetupSession setupro Counter32 .1.3.6.1.4.1.8164.1.39.2.1.70 |
starPCFSessionsRelseseSessions releasero Counter32 .1.3.6.1.4.1.8164.1.39.2.1.71 |
starPCFCurrentRevaSessionsCurrent reva sessionsro Gauge32 .1.3.6.1.4.1.8164.1.39.2.1.72 |
starPCFRevaSessionsSetupReva session setupro Counter32 .1.3.6.1.4.1.8164.1.39.2.1.73 |
starPCFRevaSessionsRelseseReva session releasero Counter32 .1.3.6.1.4.1.8164.1.39.2.1.74 |
starentSIPRouteServer OBJECT IDENTIFIER .1.3.6.1.4.1.8164.1.40 |
starSIPRouteServerTableA table containing SIPRouteServer related information SEQUENCE OF StarSIPRouteServerEntry .1.3.6.1.4.1.8164.1.40.1 |
starSIPRouteServerEntryThe statistics for a specific SIPRouteServer StarSIPRouteServerEntry .1.3.6.1.4.1.8164.1.40.1.1 |
starSIPRouteServerVpnIDThe internal identification of the VPN (context) Gauge32 .1.3.6.1.4.1.8164.1.40.1.1.1 |
starSIPRouteServerVpnNameThe name of this VPN (context)ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.40.1.1.2 |
starSIPRouteServerVmgNameThe name of this VMG (context)ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.40.1.1.3 |
starSIPRouteServerAsNameThe name of this AS (context)ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.40.1.1.4 |
starSIPRouteServerIpAddrThe Sip Route Server IP Addressro IpAddress .1.3.6.1.4.1.8164.1.40.1.1.5 |
starentVIMService OBJECT IDENTIFIER .1.3.6.1.4.1.8164.1.41 |
starVIMServiceTableA table containing VIM's Service related information SEQUENCE OF StarVIMServiceEntry .1.3.6.1.4.1.8164.1.41.1 |
starVIMServiceEntryThe statistics for a specific VIM's Service StarVIMServiceEntry .1.3.6.1.4.1.8164.1.41.1.1 |
starVIMServiceVpnIDThe internal identification of the VPN (context) Gauge32 .1.3.6.1.4.1.8164.1.41.1.1.1 |
starVIMServiceVpnNameThe name of this VPN (context)ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.41.1.1.2 |
starVIMServiceInstanceIdThe VIM Instance IDro Unsigned32 .1.3.6.1.4.1.8164.1.41.1.1.3 |
starVIMServiceFMDMaxCallRateConfigured FMD max call ratero Unsigned32 UNITS "Calls per minute" .1.3.6.1.4.1.8164.1.41.1.1.4 |
starVIMServiceFMDContinuousLoadCountConfigured FMD continuous load countro Unsigned32 .1.3.6.1.4.1.8164.1.41.1.1.5 |
starentGSS OBJECT IDENTIFIER .1.3.6.1.4.1.8164.1.42 |
starGSSClusterNameThe name of the Storage Server Clusterro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.42.1 |
starGSSClusterNodeNameThe name of a node within a Storage Server Clusterro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.42.2 |
starGSSClusterRgNameResource Groupro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.42.3 |
starGSSClusterRsNameResource Namero DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.42.4 |
starGSSClusterNodeStatero DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.42.5 |
starGSSClusterPrevOnlineNodero DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.42.6 |
starGSSClusterFromNodero DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.42.7 |
starGSSClusterToNodero DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.42.8 |
starGSSDiskPathro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.42.9 |
starGSSTransportPathro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.42.10 |
starGSSIPMPGroupNamero DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.42.11 |
starGSSInterfaceNamero DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.42.12 |
starentPDIFSys OBJECT IDENTIFIER .1.3.6.1.4.1.8164.1.43 |
starPDIFSysStatusThe overall status of the chassis as a PDIF service. A value of noservice(1) means that the chassis is not configured/licensed for PDIF; active(2) indicates that at least one PDIF service is available for processing sessions; temporary(3) indicates that PDIF is running in a temporary capacity, such as running in standby mode during an online upgrade; outofservice(4) indicates that no PDIF service is currently active, but one or more PDIF services are configuredro Enumeration .1.3.6.1.4.1.8164.1.43.1 |
starPDIFSysNumServiceThe number of PDIF services configuredro Unsigned32 UNITS "Services" .1.3.6.1.4.1.8164.1.43.2 |
starPDIFSysSessCurrentThe number of current PDIF sessions for this chassisro Gauge32 .1.3.6.1.4.1.8164.1.43.3 |
starPDIFSysSessCurrActiveThe number of currently active PDIF sessions for this chassisro Gauge32 .1.3.6.1.4.1.8164.1.43.4 |
starPDIFSysSessCurrDormantThe number of currently dormant PDIF sessions for this chassisro Gauge32 .1.3.6.1.4.1.8164.1.43.5 |
starPDIFSysSessTtlSetupThe cumulative total number of PDIF sessions that has been setupro Counter32 .1.3.6.1.4.1.8164.1.43.6 |
starPDIFSysChildSACurrentThe number of current PDIF child SAs for this chassisro Gauge32 .1.3.6.1.4.1.8164.1.43.7 |
starentPDIFService OBJECT IDENTIFIER .1.3.6.1.4.1.8164.1.44 |
starPDIFTableA table of per-service PDIF information SEQUENCE OF StarPDIFEntry .1.3.6.1.4.1.8164.1.44.1 |
starPDIFEntryThe information for a PDIF service StarPDIFEntry .1.3.6.1.4.1.8164.1.44.1.1 |
starPDIFSvcIDThe service identification is made up from first 8 chars of context name and first 8 chars of service name separated by (:) StarShortID .1.3.6.1.4.1.8164.1.44.1.1.1 |
starPDIFVpnIDThe internal identification of the VPN (context). Note that this identifier can change due to configuration changes and/or the restart of the PDIF device; in general starPDIFVpnName should be used to identify the VPN (context)ro Gauge32 .1.3.6.1.4.1.8164.1.44.1.1.2 |
starPDIFVpnNameThe VPN (context) namero DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.44.1.1.3 |
starPDIFServNameThe name of this servicero DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.44.1.1.4 |
starPDIFStatusThe state of this PDIF service. The value unknown(0) indicates that the system is unable to determine the status; inservice(1) indicates that the service is available for processing sessions; outofservice(2) indicates that the service is configured, but unavailable, either due to operator action or due to a fault.ro Enumeration .1.3.6.1.4.1.8164.1.44.1.1.5 |
starPDIFSessCurrentThe number of current sessions for this PDIF service.ro Gauge32 .1.3.6.1.4.1.8164.1.44.1.1.6 |
starPDIFSessRemainA count of the remaining capacity for this PDIF service, in terms of sessions. If a session limit is configured for this PDIF service, starPDIFSessRemain will identify the difference between this limit and starPDIFSessCurrent. If no individual limit has been configured for this service, starPDIFSessRemain will identify the remaining capacity for the entire chassis. Note that in this latter case, the value for starPDIFSessRemain cannot be summed across multiple services.ro Gauge32 .1.3.6.1.4.1.8164.1.44.1.1.7 |
starPDIFSessCurrentActiveThe number of currently active sessions for this PDIF servicero Gauge32 .1.3.6.1.4.1.8164.1.44.1.1.8 |
starPDIFSessCurrentDormantThe number of currently dormant sessions for this PDIF service. Note that this value will always be 0, as the current system does not identify PDIF sessions as dormant.ro Gauge32 .1.3.6.1.4.1.8164.1.44.1.1.9 |
starPDIFSessCurrentIpv6ActiveThe number of currently active IPv6 sessions for this PDIF service. Note that this value will always be 0, as the current system does not support IPv6 sessions.ro Gauge32 .1.3.6.1.4.1.8164.1.44.1.1.10 |
starPDIFSessCurrentIpv6DormantThe number of currently dormant IPv6 sessions for this PDIF service. Note that this value will always be 0, as the current system does not support IPv6 sessions.ro Gauge32 .1.3.6.1.4.1.8164.1.44.1.1.11 |
starPDIFSessCurrentIpv4ActiveThe number of currently active IPv4 sessions for this PDIF service. Note that all PDIF sessions are currently identified as 'active', and the value for starPDIFSessCurrentIpv4Dormant will always be zero.ro Gauge32 .1.3.6.1.4.1.8164.1.44.1.1.12 |
starPDIFSessCurrentIpv4DormantThe number of currently dormant IPv4 sessions for this PDIF service. Note that all PDIF sessions are currently identified as 'active', so the value for starPDIFSessCurrentIPv4Dormant will always be zero.ro Gauge32 .1.3.6.1.4.1.8164.1.44.1.1.13 |
starPDIFBindIpAddressThe bind IP address for this PDIF servicero IpAddress .1.3.6.1.4.1.8164.1.44.1.1.14 |
starPDIFBindIpPortThe bind IP port for this PDIF servicero Integer32 .1.3.6.1.4.1.8164.1.44.1.1.15 |
starPDIFBindSlotThe physical slot number for the physical port which holds the interface bound to the starPDIFBindIpAddress address.ro Integer32 .1.3.6.1.4.1.8164.1.44.1.1.16 |
starPDIFBindPortThe physical port number for the physical port which holds the interface bound to the starPDIFBindIpAddress address.ro Integer32 .1.3.6.1.4.1.8164.1.44.1.1.17 |
starentSGSNService OBJECT IDENTIFIER .1.3.6.1.4.1.8164.1.45 |
starSGSNSerTableA table containing SGSN related information SEQUENCE OF StarSGSNSerEntry .1.3.6.1.4.1.8164.1.45.1 |
starSGSNSerEntryThe statistics for a specific SGSN service StarSGSNSerEntry .1.3.6.1.4.1.8164.1.45.1.1 |
starSGSNSerVpnIDThe internal identification of the VPN (context) Gauge32 .1.3.6.1.4.1.8164.1.45.1.1.1 |
starSGSNSerSvcIDThe internal identification of this service; unique within a specific context Gauge32 .1.3.6.1.4.1.8164.1.45.1.1.2 |
starSessSGSNVpnNameThe name of this VPN (context)ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.45.1.1.3 |
starSessSGSNServNameThe name of this servicero DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.45.1.1.4 |
starSessSGSNMccMobile Country Codero OCTET STRING .1.3.6.1.4.1.8164.1.45.1.1.5 |
starSessSGSNMncMobile Network Codero OCTET STRING .1.3.6.1.4.1.8164.1.45.1.1.6 |
starSessSGSNRncIdThe Id of the RNCro Gauge32 .1.3.6.1.4.1.8164.1.45.1.1.7 |
starSessSGSNHlrNumThe Id of the HLRro OCTET STRING .1.3.6.1.4.1.8164.1.45.1.1.8 |
starentSS7Rd OBJECT IDENTIFIER .1.3.6.1.4.1.8164.1.46 |
starSS7RdTableA table containing SS7Rd related information SEQUENCE OF StarSS7RdEntry .1.3.6.1.4.1.8164.1.46.1 |
starSS7RdEntryThe statistics for a specific ss7rd StarSS7RdEntry .1.3.6.1.4.1.8164.1.46.1.1 |
starSS7rdIdSS7 Routing Domain identificationro Gauge32 .1.3.6.1.4.1.8164.1.46.1.1.1 |
starSS7PcPoint Codero Gauge32 .1.3.6.1.4.1.8164.1.46.1.1.2 |
starSS7M3UAPsIdPeer Server identificationro Gauge32 .1.3.6.1.4.1.8164.1.46.1.1.3 |
starSS7M3UAPspIdPeer Server process identificationro Gauge32 .1.3.6.1.4.1.8164.1.46.1.1.4 |
starSS7MTP3LinkSetIdMTP3 LinkSet Identifierro Gauge32 .1.3.6.1.4.1.8164.1.46.1.1.5 |
starSS7MTP3LinkIdMTP3 Link Identifierro Gauge32 .1.3.6.1.4.1.8164.1.46.1.1.6 |
starSS7SCTPSelfAddrThe self end point IP Addressro IpAddress .1.3.6.1.4.1.8164.1.46.1.1.7 |
starSS7SCTPPeerAddrThe IP Address of the PeerNodero IpAddress .1.3.6.1.4.1.8164.1.46.1.1.8 |
starSS7SCTPSelfPortThe self end point sctp portro Gauge32 .1.3.6.1.4.1.8164.1.46.1.1.9 |
starSS7SCTPPeerPortThe peer end point sctp portro Gauge32 .1.3.6.1.4.1.8164.1.46.1.1.10 |
starSS7CongLevelCongestion Level Valuero Gauge32 .1.3.6.1.4.1.8164.1.46.1.1.11 |
starSS7LocalCongLocal Congestion Valuero Gauge32 .1.3.6.1.4.1.8164.1.46.1.1.12 |
starSS7CauseStringCause string for failurero DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.46.1.1.13 |
starentSccpNw OBJECT IDENTIFIER .1.3.6.1.4.1.8164.1.47 |
starSccpNwTableA table containing Sccp Network related information SEQUENCE OF StarSccpNwEntry .1.3.6.1.4.1.8164.1.47.1 |
starSccpNwEntryThe statistics for a specific Sccp Network StarSccpNwEntry .1.3.6.1.4.1.8164.1.47.1.1 |
starSccpNwIdSCCP Network Idro Gauge32 .1.3.6.1.4.1.8164.1.47.1.1.1 |
starSccpSsnSub System Numberro Gauge32 .1.3.6.1.4.1.8164.1.47.1.1.2 |
starentSGTPService OBJECT IDENTIFIER .1.3.6.1.4.1.8164.1.48 |
starSGTPSerTableA table containing SGTP Service related information SEQUENCE OF StarSGTPSerEntry .1.3.6.1.4.1.8164.1.48.1 |
starSGTPSerEntryThe statistics for a specific SGTP service StarSGTPSerEntry .1.3.6.1.4.1.8164.1.48.1.1 |
starSGTPSerVpnIDThe internal identification of the VPN (context) Gauge32 .1.3.6.1.4.1.8164.1.48.1.1.1 |
starSGTPSerSvcIDThe internal identification of this service; unique within a specific context Gauge32 .1.3.6.1.4.1.8164.1.48.1.1.2 |
starSGTPVpnNameThe name of this VPN (context)ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.48.1.1.3 |
starSGTPServNameThe name of this servicero DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.48.1.1.4 |
starSGTPSelfAddrThe IP Address of the SGSNro IpAddress .1.3.6.1.4.1.8164.1.48.1.1.5 |
starSGTPPeerAddrThe IP Address of the PeerNodero IpAddress .1.3.6.1.4.1.8164.1.48.1.1.6 |
starSGTPSelfPortThe self end point sgtp portro Gauge32 .1.3.6.1.4.1.8164.1.48.1.1.7 |
starSGTPPeerPortThe peer end point sgtp portro Gauge32 .1.3.6.1.4.1.8164.1.48.1.1.8 |
starentIPMSServer OBJECT IDENTIFIER .1.3.6.1.4.1.8164.1.49 |
starIPMSServerTableA table containing information on IPMS Servers SEQUENCE OF StarIPMSServerEntry .1.3.6.1.4.1.8164.1.49.1 |
starIPMSServerEntryInformation about a particular IPMS Server StarIPMSServerEntry .1.3.6.1.4.1.8164.1.49.1.1 |
starIPMSServerVpnIDThe internal identification of the VPN (context) Gauge32 .1.3.6.1.4.1.8164.1.49.1.1.1 |
starIPMSServerAddrThe IP address of the IPMS server within this VPN (context)ro IpAddress .1.3.6.1.4.1.8164.1.49.1.1.2 |
starIPMSServerVpnNameThe name of this VPN (context)ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.49.1.1.3 |
starentCert OBJECT IDENTIFIER .1.3.6.1.4.1.8164.1.50 |
starCertTableA table containing information on X.509 Certificates SEQUENCE OF StarCertEntry .1.3.6.1.4.1.8164.1.50.1 |
starCertEntryInformation about a particular X.509 Certificate StarCertEntry .1.3.6.1.4.1.8164.1.50.1.1 |
starCertSerialNumberThe serial number for the certificatero DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.50.1.1.1 |
starCertExpiryTimeThe Certificate expiration date/timero DateAndTime (SNMPv2-TC) .1.3.6.1.4.1.8164.1.50.1.1.2 |
starCertIssuerThe Certificate issuerro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.50.1.1.3 |
starentFile OBJECT IDENTIFIER .1.3.6.1.4.1.8164.1.51 |
starFileTableA table of files stored on a mass storage device SEQUENCE OF StarFileEntry .1.3.6.1.4.1.8164.1.51.1 |
starFileEntryInformation about a particular file on a mass storage device StarFileEntry .1.3.6.1.4.1.8164.1.51.1.1 |
starFileNameThe name (full path) of the filero DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.51.1.1.1 |
starFileApplicationThe application that owns this filero Enumeration .1.3.6.1.4.1.8164.1.51.1.1.2 |
starentFTPServ OBJECT IDENTIFIER .1.3.6.1.4.1.8164.1.52 |
starFTPServTableA table of FTP servers configured SEQUENCE OF StarFTPServEntry .1.3.6.1.4.1.8164.1.52.1 |
starFTPServEntryInformation about a particular FTP Server StarFTPServEntry .1.3.6.1.4.1.8164.1.52.1.1 |
starFTPServVpnIDThe internal identification of the VPN (context) used to reach this FTP server Unsigned32 .1.3.6.1.4.1.8164.1.52.1.1.1 |
starFTPServIpAddrThe IP address of the FTP serverro IpAddress .1.3.6.1.4.1.8164.1.52.1.1.2 |
starFTPServVpnNameThe name of the VPN (context)ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.52.1.1.3 |
starentCSCFPeerServer OBJECT IDENTIFIER .1.3.6.1.4.1.8164.1.53 |
starCSCFPeerServerTableA table containing PeerServer related information SEQUENCE OF StarCSCFPeerServerEntry .1.3.6.1.4.1.8164.1.53.1 |
starCSCFPeerServerEntryThe statistics for a specific CSCF service StarCSCFPeerServerEntry .1.3.6.1.4.1.8164.1.53.1.1 |
starCSCFPeerServerVpnIDThe internal identification of the VPN (context) Gauge32 .1.3.6.1.4.1.8164.1.53.1.1.1 |
starCSCFPeerServerSvcIDThe internal identification of this CSCF service; unique within a specific context Gauge32 .1.3.6.1.4.1.8164.1.53.1.1.2 |
starCSCFPeerServerVpnNameThe name of this VPN (context)ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.53.1.1.3 |
starCSCFPeerServerSvcNameThe name of this CSCF-servicero DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.53.1.1.4 |
starCSCFPeerServerListNameThe name of the cscf-peer-serverro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.53.1.1.5 |
starCSCFPeerServerNameThe name of the cscf-peer-serverro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.53.1.1.6 |
starCSCFPeerServerStateThe state of the cscf-peer-serverro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.53.1.1.7 |
starentSDH OBJECT IDENTIFIER .1.3.6.1.4.1.8164.1.54 |
starSDHTableA table ... SEQUENCE OF StarSDHEntry .1.3.6.1.4.1.8164.1.54.1 |
starSDHEntryInformation about a specific ... StarSDHEntry .1.3.6.1.4.1.8164.1.54.1.1 |
starSDHSlotThe slot number for this portro Integer32 .1.3.6.1.4.1.8164.1.54.1.1.1 |
starSDHPortThe port number within this slotro Integer32 .1.3.6.1.4.1.8164.1.54.1.1.2 |
starSDHOperStateA bitmask indicating the state of SDH layer SCT. 0x0000 Good 0x0001 lais 0x0002 linesd 0x0004 linesf 0x0010 lof 0x0020 los 0x0040 msrdiro Integer32 .1.3.6.1.4.1.8164.1.54.1.1.3 |
starentSDHPath OBJECT IDENTIFIER .1.3.6.1.4.1.8164.1.55 |
starSDHPathTableA table ... SEQUENCE OF StarSDHPathEntry .1.3.6.1.4.1.8164.1.55.1 |
starSDHPathEntryInformation about a specific ... StarSDHPathEntry .1.3.6.1.4.1.8164.1.55.1.1 |
starSDHPathSlotThe slot number for this portro Integer32 .1.3.6.1.4.1.8164.1.55.1.1.1 |
starSDHPathPortThe port number within this slotro Integer32 .1.3.6.1.4.1.8164.1.55.1.1.2 |
starSDHPathNumThe path numberro Integer32 .1.3.6.1.4.1.8164.1.55.1.1.3 |
starSDHPathOperStateA bitmask indicating the state of SDH Path HOP. 0x0000 Good 0x0001 hopathsd 0x0002 hopathsf 0x0020 ppdi 0x0040 prdi 0x0080 perdi 0x0100 perdival 0x0200 perdivaloffro Integer32 .1.3.6.1.4.1.8164.1.55.1.1.4 |
starentE1Trib OBJECT IDENTIFIER .1.3.6.1.4.1.8164.1.56 |
starE1TribTableA table ... SEQUENCE OF StarE1TribEntry .1.3.6.1.4.1.8164.1.56.1 |
starE1TribEntryInformation about a specific ... StarE1TribEntry .1.3.6.1.4.1.8164.1.56.1.1 |
starE1TribSlotThe slot number for this portro Integer32 .1.3.6.1.4.1.8164.1.56.1.1.1 |
starE1TribPortThe port number within this slotro Integer32 .1.3.6.1.4.1.8164.1.56.1.1.2 |
starE1TribPathro Integer32 .1.3.6.1.4.1.8164.1.56.1.1.3 |
starE1TribTug2ro Integer32 .1.3.6.1.4.1.8164.1.56.1.1.4 |
starE1TribTu12ro Integer32 .1.3.6.1.4.1.8164.1.56.1.1.5 |
starE1TribOperStateLOPA bitmask indicating the state of SDH layer LOP. 0x0000 Good 0x0001 lopathsd 0x0002 lopathsf 0x0100 erdi 0x0200 rdi 0x0400 lop 0x0800 ais 0x1000 lomro Integer32 .1.3.6.1.4.1.8164.1.56.1.1.6 |
starE1TribOperStateA bitmask 0x0000 Good 0x0001 inf 0x0002 insmf 0x0004 incmf 0x0008 ooof 0x0010 raiccrc 0x0020 cfebe 0x0040 rai 0x0080 rmai 0x0100 aisd 0x0200 red 0x0400 ais 0x0800 ts16aisdro Integer32 .1.3.6.1.4.1.8164.1.56.1.1.7 |
starentGPRSLink OBJECT IDENTIFIER .1.3.6.1.4.1.8164.1.57 |
starGPRSLinkTableA table containing GPRSService Link related information SEQUENCE OF StarGPRSLinkEntry .1.3.6.1.4.1.8164.1.57.1 |
starGPRSLinkEntryThe link statistics for a specific GPRS service StarGPRSLinkEntry .1.3.6.1.4.1.8164.1.57.1.1 |
starGPRSNseiNetwork Service Entity Indentifierro Gauge32 .1.3.6.1.4.1.8164.1.57.1.1.1 |
starGPRSNsvciNetwork Service Virtual Circuit Identifierro Gauge32 .1.3.6.1.4.1.8164.1.57.1.1.2 |
starGPRSBvciBase Station System GPRS(General Packet Radio Service) Protocl Virtual Circuit Identifierro Gauge32 .1.3.6.1.4.1.8164.1.57.1.1.3 |
starentFractE1Trib OBJECT IDENTIFIER .1.3.6.1.4.1.8164.1.58 |
starFractE1TribTableA table ... SEQUENCE OF StarFractE1TribEntry .1.3.6.1.4.1.8164.1.58.1 |
starFractE1TribEntryInformation about a specific ... StarFractE1TribEntry .1.3.6.1.4.1.8164.1.58.1.1 |
starFractE1TribSlotThe slot number for this portro Integer32 .1.3.6.1.4.1.8164.1.58.1.1.1 |
starFractE1TribPortThe port number within this slotro Integer32 .1.3.6.1.4.1.8164.1.58.1.1.2 |
starFractE1TribPathro Integer32 .1.3.6.1.4.1.8164.1.58.1.1.3 |
starFractE1TribTug2ro Integer32 .1.3.6.1.4.1.8164.1.58.1.1.4 |
starFractE1TribTu12ro Integer32 .1.3.6.1.4.1.8164.1.58.1.1.5 |
starFractE1TribBundNumobsolete Integer32 .1.3.6.1.4.1.8164.1.58.1.1.6 |
starFractE1TribTimeslotsro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.58.1.1.7 |
starentStorage OBJECT IDENTIFIER .1.3.6.1.4.1.8164.1.59 |
starStorageTableA table of mass storage devices SEQUENCE OF StarStorageEntry .1.3.6.1.4.1.8164.1.59.1 |
starStorageEntryInformation about a particular file on a mass storage device StarStorageEntry .1.3.6.1.4.1.8164.1.59.1.1 |
starStorageSlotThe slot number of the card holding this storage devicero Integer32 .1.3.6.1.4.1.8164.1.59.1.1.1 |
starStorageNameThe name of the storage devicero DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.59.1.1.2 |
starStorageDeviceTypeThe storage device type. A value of independent(1) means that the device can be accessed as a standalone device, and is not part of a raid array. A value of raid(2) means that this device is a raid array. A value of raidmember(3) means the device is part of a raid array, and thus cannot be read/written to outside of the raid arrayro Enumeration .1.3.6.1.4.1.8164.1.59.1.1.3 |
starentFNGSys OBJECT IDENTIFIER .1.3.6.1.4.1.8164.1.60 |
starFNGSysStatusThe overall status of the chassis as a FNG service. A value of noservice(1) means that the chassis is not configured/licensed for FNG; active(2) indicates that at least one FNG service is available for processing sessions; temporary(3) indicates that FNG is running in a temporary capacity, such as running in standby mode during an online upgrade; outofservice(4) indicates that no FNG service is currently active, but one or more FNG services are configuredro Enumeration .1.3.6.1.4.1.8164.1.60.1 |
starFNGSysNumServiceThe number of FNG services configuredro Unsigned32 UNITS "Services" .1.3.6.1.4.1.8164.1.60.2 |
starFNGSysSessCurrentThe number of current FNG sessions for this chassisro Gauge32 .1.3.6.1.4.1.8164.1.60.3 |
starFNGSysSessCurrActiveThe number of currently active FNG sessions for this chassisro Gauge32 .1.3.6.1.4.1.8164.1.60.4 |
starFNGSysSessCurrDormantThe number of currently dormant FNG sessions for this chassisro Gauge32 .1.3.6.1.4.1.8164.1.60.5 |
starFNGSysSessTtlSetupThe cumulative total number of FNG sessions that has been setupro Counter32 .1.3.6.1.4.1.8164.1.60.6 |
starFNGSysChildSACurrentThe number of current FNG child SAs for this chassisro Gauge32 .1.3.6.1.4.1.8164.1.60.7 |
starentFNGService OBJECT IDENTIFIER .1.3.6.1.4.1.8164.1.61 |
starFNGTableA table of per-service FNG information SEQUENCE OF StarFNGEntry .1.3.6.1.4.1.8164.1.61.1 |
starFNGEntryThe information for a FNG service StarFNGEntry .1.3.6.1.4.1.8164.1.61.1.1 |
starFNGSvcIDThe service identification is made up from first 8 chars of context name and first 8 chars of service name separated by (:) StarShortID .1.3.6.1.4.1.8164.1.61.1.1.1 |
starFNGVpnIDThe internal identification of the VPN (context). Note that this identifier can change due to configuration changes and/or the restart of the FNG device; in general starFNGVpnName should be used to identify the VPN (context)ro Gauge32 .1.3.6.1.4.1.8164.1.61.1.1.2 |
starFNGVpnNameThe VPN (context) namero DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.61.1.1.3 |
starFNGServNameThe name of this servicero DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.61.1.1.4 |
starFNGStatusThe state of this FNG service. The value unknown(0) indicates that the system is unable to determine the status; inservice(1) indicates that the service is available for processing sessions; outofservice(2) indicates that the service is configured, but unavailable, either due to operator action or due to a fault.ro Enumeration .1.3.6.1.4.1.8164.1.61.1.1.5 |
starFNGSessCurrentThe number of current sessions for this FNG service.ro Gauge32 .1.3.6.1.4.1.8164.1.61.1.1.6 |
starFNGSessRemainA count of the remaining capacity for this FNG service, in terms of sessions. If a session limit is configured for this FNG service, starFNGSessRemain will identify the difference between this limit and starFNGSessCurrent. If no individual limit has been configured for this service, starFNGSessRemain will identify the remaining capacity for the entire chassis. Note that in this latter case, the value for starFNGSessRemain cannot be summed across multiple services.ro Gauge32 .1.3.6.1.4.1.8164.1.61.1.1.7 |
starFNGSessCurrentActiveThe number of currently active sessions for this FNG servicero Gauge32 .1.3.6.1.4.1.8164.1.61.1.1.8 |
starFNGSessCurrentDormantThe number of currently dormant sessions for this FNG servicero Gauge32 .1.3.6.1.4.1.8164.1.61.1.1.9 |
starFNGSessCurrentIpv6ActiveThe number of currently active IPv6 sessions for this FNG service. Note that this value will always be 0, as the current system does not support IPv6 sessions.ro Gauge32 .1.3.6.1.4.1.8164.1.61.1.1.10 |
starFNGSessCurrentIpv6DormantThe number of currently dormant IPv6 sessions for this FNG service. Note that this value will always be 0, as the current system does not support IPv6 sessions.ro Gauge32 .1.3.6.1.4.1.8164.1.61.1.1.11 |
starFNGSessCurrentIpv4ActiveThe number of currently active IPv4 sessions for this FNG service. Note that all FNG sessions are currently identified as 'active', and the value for starFNGSessCurrentIPv4Dormant will always be zero.ro Gauge32 .1.3.6.1.4.1.8164.1.61.1.1.12 |
starFNGSessCurrentIpv4DormantThe number of currently dormant IPv4 sessions for this FNG service. Note that all FNG sessions are currently identified as 'active', so the value for starFNGSessCurrentIPv4Dormant will always be zero.ro Gauge32 .1.3.6.1.4.1.8164.1.61.1.1.13 |
starFNGBindIpAddressThe bind IP address for this FNG servicero IpAddress .1.3.6.1.4.1.8164.1.61.1.1.14 |
starFNGBindIpPortThe bind IP port for this FNG servicero Integer32 .1.3.6.1.4.1.8164.1.61.1.1.15 |
starFNGBindSlotThe physical slot number for the physical port which holds the interface bound to the starFNGBindIpAddress address.ro Integer32 .1.3.6.1.4.1.8164.1.61.1.1.16 |
starFNGBindPortThe physical port number for the physical port which holds the interface bound to the starFNGBindIpAddress address.ro Integer32 .1.3.6.1.4.1.8164.1.61.1.1.17 |
starentPDGSys OBJECT IDENTIFIER .1.3.6.1.4.1.8164.1.62 |
starPDGSysStatusThe overall status of the chassis as a PDG service. A value of noservice(1) means that the chassis is not configured/licensed for PDG; active(2) indicates that at least one PDG service is available for processing sessions; temporary(3) indicates that PDG is running in a temporary capacity, such as running in standby mode during an online upgrade; outofservice(4) indicates that no PDG service is currently active, but one or more PDG services are configuredro Enumeration .1.3.6.1.4.1.8164.1.62.1 |
starPDGSysNumServiceThe number of PDG services configuredro Unsigned32 UNITS "Services" .1.3.6.1.4.1.8164.1.62.2 |
starPDGSysSessCurrentThe number of current PDG sessions for this chassisro Gauge32 .1.3.6.1.4.1.8164.1.62.3 |
starPDGSysSessCurrActiveThe number of currently active PDG sessions for this chassisro Gauge32 .1.3.6.1.4.1.8164.1.62.4 |
starPDGSysSessCurrDormantThe number of currently dormant PDG sessions for this chassisro Gauge32 .1.3.6.1.4.1.8164.1.62.5 |
starPDGSysSessTtlSetupThe cumulative total number of PDG sessions that has been setupro Counter32 .1.3.6.1.4.1.8164.1.62.6 |
starPDGSysChildSACurrentThe number of current PDG child SAs for this chassisro Gauge32 .1.3.6.1.4.1.8164.1.62.7 |
starentPDGService OBJECT IDENTIFIER .1.3.6.1.4.1.8164.1.63 |
starPDGTableA table of per-service PDG information SEQUENCE OF StarPDGEntry .1.3.6.1.4.1.8164.1.63.1 |
starPDGEntryThe information for a PDG service StarPDGEntry .1.3.6.1.4.1.8164.1.63.1.1 |
starPDGSvcIDThe service identification is made up from first 8 chars of context name and first 8 chars of service name separated by (:) StarShortID .1.3.6.1.4.1.8164.1.63.1.1.1 |
starPDGVpnIDThe internal identification of the VPN (context). Note that this identifier can change due to configuration changes and/or the restart of the PDG device; in general starPDGVpnName should be used to identify the VPN (context)ro Gauge32 .1.3.6.1.4.1.8164.1.63.1.1.2 |
starPDGVpnNameThe VPN (context) namero DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.63.1.1.3 |
starPDGServNameThe name of this servicero DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.63.1.1.4 |
starPDGStatusThe state of this PDG service. The value unknown(0) indicates that the system is unable to determine the status; inservice(1) indicates that the service is available for processing sessions; outofservice(2) indicates that the service is configured, but unavailable, either due to operator action or due to a fault.ro Enumeration .1.3.6.1.4.1.8164.1.63.1.1.5 |
starPDGSessCurrentThe number of current sessions for this PDG service.ro Gauge32 .1.3.6.1.4.1.8164.1.63.1.1.6 |
starPDGSessRemainA count of the remaining capacity for this PDG service, in terms of sessions. If a session limit is configured for this PDG service, starPDGSessRemain will identify the difference between this limit and starPDGSessCurrent. If no individual limit has been configured for this service, starPDGSessRemain will identify the remaining capacity for the entire chassis. Note that in this latter case, the value for starPDGSessRemain cannot be summed across multiple services.ro Gauge32 .1.3.6.1.4.1.8164.1.63.1.1.7 |
starPDGSessCurrentActiveThe number of currently active sessions for this PDG servicero Gauge32 .1.3.6.1.4.1.8164.1.63.1.1.8 |
starPDGSessCurrentDormantThe number of currently dormant sessions for this PDG servicero Gauge32 .1.3.6.1.4.1.8164.1.63.1.1.9 |
starPDGSessCurrentIpv6ActiveThe number of currently active IPv6 sessions for this PDG service. Note that this value will always be 0, as the current system does not support IPv6 sessions.ro Gauge32 .1.3.6.1.4.1.8164.1.63.1.1.10 |
starPDGSessCurrentIpv6DormantThe number of currently dormant IPv6 sessions for this PDG service. Note that this value will always be 0, as the current system does not support IPv6 sessions.ro Gauge32 .1.3.6.1.4.1.8164.1.63.1.1.11 |
starPDGSessCurrentIpv4ActiveThe number of currently active IPv4 sessions for this PDG service. Note that all PDG sessions are currently identified as 'active', and the value for starPDGSessCurrentIPv4Dormant will always be zero.ro Gauge32 .1.3.6.1.4.1.8164.1.63.1.1.12 |
starPDGSessCurrentIpv4DormantThe number of currently dormant IPv4 sessions for this PDG service. Note that all PDG sessions are currently identified as 'active', so the value for starPDGSessCurrentIPv4Dormant will always be zero.ro Gauge32 .1.3.6.1.4.1.8164.1.63.1.1.13 |
starPDGBindIpAddressThe bind IP address for this PDG servicero IpAddress .1.3.6.1.4.1.8164.1.63.1.1.14 |
starPDGBindIpPortThe bind IP port for this PDG servicero Integer32 .1.3.6.1.4.1.8164.1.63.1.1.15 |
starPDGBindSlotThe physical slot number for the physical port which holds the interface bound to the starPDGBindIpAddress address.ro Integer32 .1.3.6.1.4.1.8164.1.63.1.1.16 |
starPDGBindPortThe physical port number for the physical port which holds the interface bound to the starPDGBindIpAddress address.ro Integer32 .1.3.6.1.4.1.8164.1.63.1.1.17 |
starentIPPoolGroup OBJECT IDENTIFIER .1.3.6.1.4.1.8164.1.64 |
starIPPoolGroupTableA table containing IP Pool Group information SEQUENCE OF StarIPPoolGroupEntry .1.3.6.1.4.1.8164.1.64.1 |
starIPPoolGroupEntryInformation for a specific IP Pool Group StarIPPoolGroupEntry .1.3.6.1.4.1.8164.1.64.1.1 |
starIPPoolGroupVpnIDThe context ID for this pool group Gauge32 .1.3.6.1.4.1.8164.1.64.1.1.1 |
starIPPoolGroupIDThe service identification is made up from first 8 chars of context name and first 16 chars of pool group name separated by (:) StarMediumID .1.3.6.1.4.1.8164.1.64.1.1.2 |
starIPPoolGroupNameThe name of the IP pool groupro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.64.1.1.3 |
starIPPoolGroupVpnNameThe context name string for this pool groupro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.64.1.1.4 |
starIPPoolGroupUsedThe number of IP addresses in USED state in the pool groupro Gauge32 .1.3.6.1.4.1.8164.1.64.1.1.5 |
starIPPoolGroupHoldThe number of IP addresses in HOLD state in the pool groupro Gauge32 .1.3.6.1.4.1.8164.1.64.1.1.6 |
starIPPoolGroupReleaseThe number of IP addresses in RELEASE state in the pool groupro Gauge32 .1.3.6.1.4.1.8164.1.64.1.1.7 |
starIPPoolGroupFreeThe number of IP addresses in FREE state in the pool groupro Gauge32 .1.3.6.1.4.1.8164.1.64.1.1.8 |
starIPPoolGroupPctUsedThe percentage of IP addresses in USED state in the pool group is the percentage value times 100; for example,2.3% would be represented as 230ro Integer32 .1.3.6.1.4.1.8164.1.64.1.1.9 |
starIPPoolGroupAvailThe number of IP addresses in AVAILABLE state in the pool groupro Gauge32 .1.3.6.1.4.1.8164.1.64.1.1.10 |
starentHNBGWService OBJECT IDENTIFIER .1.3.6.1.4.1.8164.1.65 |
starHNBGWServTableA table containing HNBGW related information SEQUENCE OF StarHNBGWServEntry .1.3.6.1.4.1.8164.1.65.1 |
starHNBGWServEntryThe statistics for a specific HNBGW service StarHNBGWServEntry .1.3.6.1.4.1.8164.1.65.1.1 |
starHNBGWServVpnIDThe internal identification of the VPN (context) Gauge32 .1.3.6.1.4.1.8164.1.65.1.1.1 |
starHNBGWServSvcIDThe internal identification of this service; unique within a specific context Gauge32 .1.3.6.1.4.1.8164.1.65.1.1.2 |
starSessHNBGWVpnNameThe name of this VPN (context)ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.65.1.1.3 |
starSessHNBGWServNameThe name of this Servicero DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.65.1.1.4 |
starSessHNBGWCsNwNameThe name of the CS NWro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.65.1.1.5 |
starSessHNBGWPsNwNameThe name of the PS NWro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.65.1.1.6 |
starSessHNBGWSgsnPtCdSGSN Point Codero Integer32 .1.3.6.1.4.1.8164.1.65.1.1.7 |
starSessHNBGWMscPtCdMSC Point Codero Integer32 .1.3.6.1.4.1.8164.1.65.1.1.8 |
starentALCAPService OBJECT IDENTIFIER .1.3.6.1.4.1.8164.1.66 |
starALCAPServTableA table containing ALCAP relate information SEQUENCE OF StarALCAPServEntry .1.3.6.1.4.1.8164.1.66.1 |
starALCAPServEntryThe statistics for a specific ALCAP service StarALCAPServEntry .1.3.6.1.4.1.8164.1.66.1.1 |
starALCAPSerVpnIDThe internal identification of the VPN (context) Gauge32 .1.3.6.1.4.1.8164.1.66.1.1.1 |
starALCAPSerSvcIDThe internal identification of this service; unique within a specific context Gauge32 .1.3.6.1.4.1.8164.1.66.1.1.2 |
starSessALCAPVpnNameThe name of this VPN (context)ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.66.1.1.3 |
starSessALCAPServNameThe name of this Servicero DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.66.1.1.4 |
starSessALCAPAAL2NodeNameThe name of the AAL2 Nodero DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.66.1.1.5 |
starSessALCAPPathIdThe path id of AAL2 pathro Integer32 .1.3.6.1.4.1.8164.1.66.1.1.6 |
starentMMES1Assoc OBJECT IDENTIFIER .1.3.6.1.4.1.8164.1.67 |
starMMES1AssocTableA table of MME S1 Associations SEQUENCE OF StarMMES1AssocEntry .1.3.6.1.4.1.8164.1.67.1 |
starMMES1AssocEntryInformation about a particular MME S1 Association StarMMES1AssocEntry .1.3.6.1.4.1.8164.1.67.1.1 |
starMMES1AssocSvcIDThe service identification is made up from the first 8 characters of the VPN name and the first 16 characters of the service name seperated by (:) StarMediumID .1.3.6.1.4.1.8164.1.67.1.1.1 |
starMMES1AssocENBIDThe identification of the eNodeBro StarENBID .1.3.6.1.4.1.8164.1.67.1.1.2 |
starMMES1AssocVpnNameThe name of this VPN (context)ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.67.1.1.3 |
starMMES1AssocServNameThe name of this MME Servicero DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.67.1.1.4 |
starentMMES1Path OBJECT IDENTIFIER .1.3.6.1.4.1.8164.1.70 |
starMMES1PathTableA table of MME S1 Path SEQUENCE OF StarMMES1PathEntry .1.3.6.1.4.1.8164.1.70.1 |
starMMES1PathEntryInformation about a particular MME S1 Pathiation StarMMES1PathEntry .1.3.6.1.4.1.8164.1.70.1.1 |
starMMES1PathSvcIDThe service identification is made up from the first 8 characters of the VPN name and the first 16 characters of the service name seperated by (:) StarMediumID .1.3.6.1.4.1.8164.1.70.1.1.1 |
starMMES1PathENBIDThe identification of the eNodeBro StarENBID .1.3.6.1.4.1.8164.1.70.1.1.2 |
starMMES1PathVpnNameThe name of this VPN (context)ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.70.1.1.3 |
starMMES1PathServNameThe name of this MME Servicero DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8164.1.70.1.1.4 |
starMMES1PathSelfAddrInterface IP Addressro IpAddress .1.3.6.1.4.1.8164.1.70.1.1.5 |
starMMES1PathSelfPortSelf port numberro Gauge32 .1.3.6.1.4.1.8164.1.70.1.1.6 |
starMMES1PathPeerAddrInterface IP Addressro IpAddress .1.3.6.1.4.1.8164.1.70.1.1.7 |
starMMES1PathPeerPortPeer port numberro Gauge32 .1.3.6.1.4.1.8164.1.70.1.1.8 |
starentTraps OBJECT IDENTIFIER .1.3.6.1.4.1.8164.2 |
starCardTempOverheatThe card has reached a temperature beyond its safe operating range. Probable Cause: External temperature is too high; One or more fan failures; blockages the prevent fan air inflow/outflow. Action to be Taken: Inspect chassis for any item that may be blocking chassis air flow. Verify adjacent equipment is not obstructing air flow. Verify that the fans are running via the CLI/EMS. Check air filters. Check chassis maintenance schedule to see if chassis needs routine air filter replacement. Verify room temperature is within acceptable operating conditions. Clear Condition: This condition is cleared when the card reaches its operating temperature range or is removed from the system. Condition Clear Alarm: This condition is cleared by a starCardTempOK notification. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1 |
starCardTempOKThe temperature of the card is now within its safe operating range. This notification is only generated if the card has previosly generated a starCardTempOverheat notification. Action to be Taken: No action required. The cause for the card overheat condition should be investigated. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.2 |
starCardResetA reset operation has been invoked on the card. This trap is obsolete.obsolete NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.3 |
starCardRebootRequestA Reboot operation has been invoked on this card by an administrator. If successful, a subsequent CardDown trap is typically generated. Action to be Taken: No action required. If the reboot was not scheduled the admin logs can be examined to determine who invoked the reboot operation NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.4 |
starCardUpThe card is up (operational) NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.5 |
starCardVoltageFailureA voltage regulation failure has been detected this card. Probable Cause: Problem with incoming power; failure of power filters; hardware issue with card. Note that this is an extremely abnormal condition. Action To Be Taken: Verify that the power supplied to the chassis is operating correctly; use the CLI/EMS to check the state of the chassis power filters; replace the card Clear Condition: This is not a recoverable error except via restarting the card, so the condition is only cleared via a starCardUp or starCardActive notification NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.6 |
starCardRemovedA card has been removed from the chassis. Probable Cause: An operator has physically unlocked and removed a card from the chassis Action to be Taken: No action is required. If the card removal was unplanned, the admin logs can identify the time when the card was initially unlocked. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.7 |
starCardInsertedA card has been inserted into the chassis. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.8 |
starCardBootFailedA card has failed to startup properly. The card is not operational Probable Cause: The system logs should contain additional information about the cause of the boot failure NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.9 |
starCardFailedThe card has failed and is no longer operational. This trap is obsolete and has been replaced with more specific traps to identify specific failures.obsolete NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.10 |
starCardSWFailedA unrecoverable software error has occured on the card. This trap is obsolete and has been replaced with more specific traps to identify specific failures.obsolete NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.11 |
starCardRCCFailedThe RCC has failed. Probable Cause: A hardware failure on the RCC card. This trap is obsolete.obsolete NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.12 |
starCardMismatchThe card does not match its configuration, or the card does not match the slot it was inserted into, or the card is of an unsupported type. Probable Cause: A card was inserted into a slot which was configured for a different type of card. For example, a Gigabit Ethernet card was inserted into a slot configured for a Fast Ethernet card. A starCardUp or starCardActive notification would indicate that this condition has been cleared. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.13 |
starCardFailureLEDOnThe failure LED is illuminated on the card. This trap is obsolete and has been replaced with more specific traps for specific failures.obsolete NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.14 |
starCardFailureLEDOffThe failure LED is no longer illuminated on the card. This notification is only generated if the card has previously generated a starCardFailureLEDOn notification. This trap is obsolete and has been replaced with more specific traps for specific failures.obsolete NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.15 |
starCardPACMigrateStartA PAC/PSC Migration operation has begun. The first varbind identifies the PAC/PSC being migrated away from; the second varbind identifies the PAC/PSC being migrated to. Probable Cause: This is typically caused by an operator action; it can also represent the system recovering from a software or hardware fault. A starCardPACMigrateComplete is generated when the migration is completeddeprecated NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.16 |
starCardPACMigrateCompleteA PAC/PSC Migration operation has successfully completed. The first varbind identifies the PAC/PSC that was migrated away from; the second varbind identifies the PAC/PSC that was migrated to.deprecated NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.17 |
starCardPACMigrateFailedA PAC/PSC Migration operation has failed. The first varbind identifies the PAC/PSC that was attemped to be migrated away from; the second varbind identifies the PAC/PSC that was attempted to be migrated to. Probable Cause: The PAC/PSC being migrated to was removed or reset before the migration completed; the migration operation was terminated by an operator; or a software or hardware failure on either PAC/PSC involved in the migration operation. The PAC/PSC in question will be reset; a starCardUp notification will be generated when the card is operational again.deprecated NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.18 |
starCardSPCSwitchoverStartAn SPC switchover operation has begun. The first varbind identifies the SPC being switched away from; the second varbind identifies the SPC being switched to. Note that since an SPC switchover can cause a momentary loss of communication through the management (SPIO) interface, it is possible that this trap will not be successfully delivered. Probable Cause: This is typically caused by an operator action; it can also represent the system recovering from a software or hardware fault. Action to be Taken: If the SPC switchover was unplanned, the admin logs should be examined for the cause of the switchover. If the cause was a software failure, the system crash logs should be examined. Clear Condition: Verify the SPC switchover completes successfully. Clear Condition Alarm: A starCardSPCSwitchoverComplete is generated when the switchover operation has completed.deprecated NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.19 |
starCardSPCSwitchoverCompleteAn SPC Switchover has completed successfully. The starSlotNum varbind identifies the new primary SPC Action to be Taken: If the SPC switchover was unplanned, the admin logs should be examined for the cause of the switchover. If the cause was a software failure, the system crash logs should be examined.deprecated NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.20 |
starCardSPCSwitchoverFailedAn SPC switchover operation has failed. The first varbind identifies the SPC that was attempted to be switched away from; the second varbind identifies the SPC that was attempted to be switched to. Probable Cause: The SPC being migrated to was removed or reset before the migration completed; the migration operation was terminated by an operator; or a software or hardware failure on either SPC. Action to be Taken: Verify that both SPCs have the card locks in the locked position; examine the admin logs for the cause of the failure. If the cause was a software failure, the system crash logs should be examined. Clear Condition: The SPC in question will be reset; a starCardUp notification will be generated when the card is operational again.deprecated NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.21 |
starFanFailedOne of more fans have failed on the indicated fan controller. Probable Cause: A hardware failure on the fan tray. The fan tray should be replaced. Action to be Taken: Verify there is no physical obstruction to the fans; Replace the fan tray. Clear Condition: Verify the fans are running Condition Clear Alarm: A starFanInserted notification will be generated when the fan tray is replaced. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.22 |
starFanRemovedA fan tray has been removed Action to be Taken: Replace the fan tray Clear Condition: Verify both fan trays are present and operational. Condition Clear Alarm: A starFanInserted notification will be generated when the fan tray is replaced. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.23 |
starFanInsertedA fan tray has been inserted NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.24 |
starLogThresholdA system log has reached its maximum size. This trap is obsolete.obsolete NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.25 |
starCPUBusyThe CPU is experiencing very high usage. Probable Cause: For SPC/SMC CPUs this typically represents an abnormal amount of management (CLI, SNMP, CORBA) requests. For PAC/PSC cards this indicates that the system is reaching its capacity. Action to be Taken: For SPC/SMC cards, this may be a transient condition because of a burst of management activity. Monitor the CPU usage and if it is persistently high, examine the CPU table to determine which management activity is causing the excessive usage. For PAC/PSC cards, this indicates the system is nearing its overall capacity. Monitor CPU usage and if it is persistently high, the system may need additional PACs/PSCs to keep up with the system load. Clear Condition: Verify that CPU usage returned to a normal load. This can represent a transient condition; the trap will be periodically repeated if the condition persists. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.26 |
starCPUMemoryLowThe CPU is experiencing a low memory condition. Probable Cause: For SPC CPUs this typically represents an abnormal number of management sessions, in particular CLI sessions. For PAC/PCS cards this indicates that the system is reaching its capacity. Action to be Taken: For SPC cards, this may be a transient condition because of a burst of management activity. Monitor memory usage and if it is persistently high, examine the CPU table to determine which management activity is causing the excessive usage. Verify that large numbers of CLI sessions are not being generated and, if needed, terminate extra sessions. For PAC/PCS cards, this indicated the system is nearing its overall capacity. Monitor memory usage and if it is persistently high, the system may need additional PACs/PCSs or additional PAC/PCS memory to keep up with the system load. Clear Condition: Verify that memory usage returned to a normal load. This can represent a transient condition; the trap will be periodically repeated if the condition persists. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.27 |
starCPUMemoryFailedThe memory on this CPU has failed. Probable Cause: This indicates a hardware problem. Action to be Taken: Replace the failing card. The card will be reset; a starCardUp will be generated if the card is restored to an operational state. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.28 |
starCPUFailedThe CPU has failed. Probable Cause: This indicates a hardware problem. Action to be Taken: Replace the failing card. The card will be reset; a starCardUp will be generated if the card is restored to an operational state. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.29 |
starCPUWatchDogExpiredThe watch dog timer has failed on this CPU. Probable Cause; This could indicate an extremely busy CPU, a software problem, or a hardware issue. Action to be Taken: Check the admin logs for an indication of the problem. Check the system crash logs for an indication of software problems. If the problem persists, replace the card. Clear Condition: Verify that an SPC/SMC switchover or PAC/PSC migration completes successfully to recover from the failure condition. Condition Clear Alarm: A starCardUp will be generated if the card is restored to an operational state. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.30 |
starNPUARPPoolExhaustedThe ARP pool on this NPU manager is exhausted. When this occurs, the ARP entry isn't added and traffic to the local device is fowarded through a slower path. Action To Be Taken: Reduce the total number of directly connected devices or clear ARP entries. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.31 |
starPowerFilterUnitFailedA Power Filter Unit (PFU) failed. Probable Cause: The external power source has failed or has been disconnected, or a hardware failure on the PFU. Action to be Taken: Verify that the input power to the power filter is operational and repair if needed. Verify that the connections to the power filter are intact and that the power filter is properly inserted into the chassis. Replace the power filter if required. Clear Condition: Verify that both power filters are operating. Condition Clear Alarm: A starPowerFilterAvail will be generated when the power filter is replaced.deprecated NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.32 |
starPowerFilterUnitUnavailA Power Filter Unit (PFU) is unavailable. Probable Cause: The power filter has been removed from the chassis, or no power is being provided to the PFU. Action to be Taken: If the power filter removal wasn't planned, Verify that the input power to the power filter is operational and repair if needed. Verify that the connections to the power filter are intact and that the power filter is properly inserted into the chassis. Replace the power filter if required. Clear Condition: Verify that both power filters are operating. Condition Clear Alarm: A starPowerFilterUnitAvail will be generated when the power filter is replaced. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.33 |
starPowerFilterUnitAvailA Power Filter Unit (PFU) is available. This typically means that a PFU has been inserted into the chassis or has has its power source restored. Action to be Taken: No action required NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.34 |
starAlertsDisabledThe sending of SNMP Traps has been disabled because too many alerts were generated within the defined window type Probable Cause: Either a large number of SNMP notifications are being generated, or the configured threshold which limits the number of notifications is set too aggressively. Actions to be Taken: Examine the admin logs and the SNMP trap logs to determine the source of the large number of traps and take appropriate actions; verify that the configured limit for the rate at which traps will be sent is appropriate for your environment. Clear Condition Alarm: When the rate of SNMP notifications goes down a starAlertsEnabled notification is generated NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.37 |
starAlertsEnabledThe sending of SNMP Traps has been reenabled NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.38 |
starAAAAuthServerUnreachableThe Authentication, Authorization and Accouting (AAA) server cannot be reached. Probable Cause: The AAA server is down, or there is a network issue preventing communication with the AAA server. Actions to be Taken: Restore the AAA server to an operational status; Verify that the AAA server is reachable by performing a 'ping' operation from the CLI in the appropriate context. Check the admin logs for notification of communication problems. Clear Condition: Verify that communication to the AAA authentication server has been restored. Condition Clear Alarm: When this condition clears a starAAAAuthServerReachable notification will be generated. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.39 |
starAAAAuthServerReachableThe Authentication, Authorization and Accouting (AAA) server is now reachable. This can be the result of a system startup, the configuration of a new server, or a previously unreachable server becoming reachable. Action to be Taken: No Action Required. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.40 |
starAAAAuthServerMisconfiguredThe Authentication, Authorization and Accounting (AAA) server has been misconfigured. This server is not usable until this condition is repaired. Action to be Taken: Examine the system configuration and correct the misconfiguration. See the user documentation for details on AAA configuration. Clear Condition: Verify that communication to the AAA authentication server has been restored. Condition Clear Alarm: When this condition clears a starAAAAuthServerReachable notification will be generated. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.41 |
starAAAAccServerUnreachableThe Authentication, Authorization and Accouting (AAA) server cannot be reached. Probable Cause: The AAA server is down, or there is a network issue preventing communication with the AAA server. Actions to be Taken: Restore the AAA server to an operational status; Verify that the AAA server is reachable by performing a 'ping' operation from the CLI in the appropriate context. Check the admin logs for notification of communication problems. Clear Condition: Verify that communication to the AAA accounting server has been restored. Condition Clear Alarm: When this condition clears a starAAAAccServerReachable notification will be generated. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.42 |
starAAAAccServerReachableThe Authentication, Authorization and Accouting (AAA) server is now reachable. This can be the result of a system startup, the configuration of a new server, or a previously unreachable server becoming reachable. Note that since Accounting servers are not responding to 'hello'-type messages, it is not always possible to accurately determine when an accounting server is reachable. A server may be declared 'reachable' when the ST16 is ready to start using the server, but before any acknowledgement is actually received from the server. Once accounting information actually is sent to the server a starAAAAccServerUnreachable will be generated if the server does not properly respond. Action to be Taken: No Action Required. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.43 |
starAAAAccServerMisconfiguredThe Authentication, Authorization and Accounting (AAA) server has been misconfigured. This server is not usable until this condition is repaired. Action to be Taken: Examine the system configuration and correct the misconfiguration. See the user documentation for details on AAA configuration. Clear Condition: Verify that communication to the AAA authentication server has been restored. Condition Clear Alarm: When this condition clears a starAAAAccServerReachable notification will be generated. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.44 |
starLogMsgA log message. This trap is used only for debugging. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.45 |
starPDSNServiceStartA PDSN Service has started Action to be Taken: No action required NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.46 |
starPDSNServiceStopA PDSN Service has stopped. Probable Cause: This is typically caused by operator invention. In unusual cases it can be caused by the loss of resources (PACs/PSCs) to support the running configuration. Action to be Taken: If the PDSN service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured PACs/PSCs are present and running in the system. Check the crash logs for an indication of a software failure. Clear Condition: Verify that the PDSN service is operational. Condition Clear Alarm: A starPDSNServiceStart notification will be generated when the service is restarted NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.47 |
starHAServiceStartAn HA Service has started Action to be Taken: No action required NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.48 |
starHAServiceStopAn HA Service has stopped Probable Cause: This is typically caused by operator invention. In unusual cases it can be caused by the loss of resources (PACs/PSCs) to support the running configuration. Action to be Taken: If the PDSN service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured PACs/PSCs are present and running in the system. Check the crash logs for an indication of a software failure. Clear Condition: Verify that the PDSN service is operational. Condition Clear Alarm: A starHAServiceStart notification will be generated when the service is restarted NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.49 |
starFAServiceStartAn FA Service has started Action to be Taken: No action required NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.50 |
starFAServiceStopAn FA Service has stopped Probable Cause: This is typically caused by operator invention. In unusual cases it can be caused by the loss of resources (PACs/PSCs) to support the running configuration. Action to be Taken: If the FA service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured PACs/PSCs are present and running in the system. Check the crash logs for an indication of a software failure. Clear Condition: Verify that the FA service is operational. Condition Clear Alarm: A starFAServiceStart notification will be generated when the service is restarted NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.51 |
starCLISessionStartAn interactive CLI session has started A starCLISessionEnd notification will be sent when the CLI session is terminated. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.52 |
starCLISessionEndAn interactive CLI session has ended. The CLI session may have been terminated by the CLI user; the session may have expired due to an idle timeout, or a session timeout; or the session may have been terminated by operator intervention. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.53 |
starCritTaskFailedA critical task has failed and the appropriate recovery steps begun. The card containing the failed task will be restarted; migration/recovery operations will proceed. Probable Cause: Software error Actions to be Taken: Examine the admin logs for an indication of the source of the failure. Clear Condition: Verify that an SPC switchover or PAC/PSC migration completes to recover from this condition. Condition Clear Alarm: A starCardUp will be generated when the card has successfully restarted. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.54 |
starCardActiveThe card is now active. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.55 |
starLACServiceStartA LAC Service has started Action to be Taken: No action required NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.56 |
starLACServiceStopA LAC Service has stopped Probable Cause: This is typically caused by operator invention. In unusual cases it can be caused by the loss of resources (PACs/PSCs) to support the running configuration. Action to be Taken: If the LAC service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured PACs/PSCs are present and running in the system. Check the crash logs for an indication of a software failure. Clear Condition: Verify that the LAC service is operational. Condition Clear Alarm: A starLACServiceStart notification will be generated when the service is restarted NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.57 |
starLNSServiceStartA LNS Service has started Action to be Taken: No Action Required NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.58 |
starLNSServiceStopA LNS Service has stopped Probable Cause: This is typically caused by operator invention. In unusual cases it can be caused by the loss of resources (PACs/PSCs) to support the running configuration. Action to be Taken: If the LNS service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured PACs/PSCs are present and running in the system. Check the crash logs for an indication of a software failure. Clear Condition: Verify that the LNS service is operational. Condition Clear Alarm: A starLNSServiceStart notification will be generated when the service is restarted NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.59 |
starCardDownThe card is now down. Probable Cause: The card was shut down by an operator; the card was removed by an operator; or a hardware or software fault caused the card to shut down. In the latter case an additional notification is generated with the specific failure. Action to be Taken: If the card shutdown was not planned, verify that the card is present in the system and its card lock is in the locked position. Check the admin logs for the cause of the card shutdown. Clear Condition: Verify that an SPC switchover/card migration completes to recover from the card shutdown. Condition Clear Alarm: A starCardUp notification is generated when the card is restarted. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.60 |
starGGSNServiceStartA GGSN Service has started Action to be Taken: No action required NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.63 |
starGGSNServiceStopA GGSN Service has stopped Probable Cause: This is typically caused by operator invention. In unusual cases it can be caused by the loss of resources (PACs/PSCs) to support the running configuration. Action to be Taken: If the GGSN service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured PACs/PSCs are present and running in the system. Check the crash logs for an indication of a software failure. Clear Condition: Verify that the GGSN service is operational. Condition Clear Alarm: A starGGSNServiceStart notification will be generated when the service is restarted NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.64 |
starLicenseExceededThe licenses session limit has been exceeded; note that a small number of sessions are permitted beyond the licensed limit. Probable Cause: The usage of the system has exceeded the capacity of the license installed; The license installed does not match the identification of the system; No license is installed Action to be Taken: Verify that the proper license is installed on the system; verify that the SPCs present in the system match those identified in the software license. If required, install an additional higher-capacity license. Clear Condition: This condition is cleared when usage goes under the licensed limit. Condition Clear Alarm: This condition is cleared by a starLicenseUnderLimit notification. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.65 |
starSubscriberLimitThe specified service has reached its configured limit for number of subscribers Action to be Taken: Verify that the configured subscriber limit is correct. Configure additional services, or configure the existing service to permit a larger number of subscribers NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.66 |
starSessionRejectNoResourceA session setup was rejected because of a lack of available resources Probable Cause: The system has reached its maximum capacity based on the number of available PACs/PSCs/CPUs/memory. Actions to be Taken: Examine the system CPU table to determine if there is abnormal system usage or if the system is reaching its capacity. If this condition persists, additional PACs/PSCs or PAC/PSC memory may be required. Note that there is a configuration threshold which can be setup to monitor the number of NORESOURCE rejects. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.67 |
starLongDurTimerExpiryThe long duration timer has expired for the identified subscriber. Note that either starSubHomeAddr or starSubHomeAddrv6 is typically filled in, as appropriate. The other attribute will be all zero octets. Action to be Taken: No action is typically required. If an abnormal number of expiries occur, verify that the configuration expiry time is correct NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.68 |
starClosedRPServiceStartClosed RP Service has started Action to be Taken: No action required NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.69 |
starClosedRPServiceStopClosed RP Service has stopped Probable Cause: This is typically caused by operator invention. In unusual cases it can be caused by the loss of resources (PACs/PSCs) to support the running configuration. Action to be Taken: If the Closed RP service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured PACs/PSCs are present and running in the system. Check the crash logs for an indication of a software failure. Clear Condition: Verify that the Closed RP service is operational. Condition Clear Alarm: A starClosedRPServiceStart notification will be generated when the service is restarted NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.70 |
starGtpcPathFailureGTP Control Path Failure. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.71 |
starGtpuPathFailureGTP Data Path Failure. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.72 |
starManagerFailureSoftware manager Failure. Probable Cause: A software failure. The failing manager will be restarted. Action to be Taken: Examine the admin and crash logs for more information about the failure NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.73 |
starEISServerAliveEIS Server alive NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.74 |
starEISServerDeadEIS Server down. Probable Cause: The remote EIS server is down or there is a network error making it unreachable. Condition Clear Alarm: A starEISServerAlive notification will be generated when this condition is cleared NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.75 |
starCgfAliveGTPP CGF Server Alive. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.76 |
starCgfDeadGTPP CGF Server Dead. Probable Cause: The remote CGF server is down or there is a network error making it unreachable. Action to be Taken: Verify that the CGF server is functioning properly; verify network connectivity to the CGF server. Clear Condition: This condition is cleared when the CGF server becomes reachable. Condition Clear Alarm: A starCgfServerAlive notification will be generated when this condition is cleared NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.77 |
starStorageServerAliveGTPP Storage Server is Alive. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.78 |
starStorageServerDeadGTPP Storage Server is Dead. Probable Cause: The remote Storage server is down or there is a network error making it unreachable. Action to be Taken: Verify that the Storage server is functioning properly; verify network connectivity to the Storage server. Clear Condition: This condition is cleared when the Storage server becomes reachable. Condition Clear Alarm: A starStorageServerAlive notification will be generated when this condition is cleared NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.79 |
starGgsnInitiatedUpdtFailedGGSN Initiated Update PDP Context Response Failed. Probable Cause: This can happen if there is an inter-SGSN handoff and the new SGSN is not listed in GGSN service and its PLMN policy is set to reject unknown SGSNs. Action to be Taken: List the SGSN address in the GGSN service. Condition Clear Alarm: NA NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.80 |
starCongestionA congestion condition has occurred. Probable Cause: This is the result of an operator-configured congestion threshold being reached. This can be due to high usage of the resource being monitored which indicates that the IMG is reaching its peak capacity, or could be caused by the incorrect configuration of the congestion thresholds. Actions to be Taken: Verify that the congestion thresholds are correct; if the congested state is seem repeatedly, or for sustained periods of time, additional system capacity may need to be brought online. This system is cleared when the use of the specific resource falls below the configured limit. Condition Clear Alarm: A starCongestionClear notification is sent when there are no congestion conditions for a service type NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.81 |
starCongestionClearA congestion condition has cleared NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.82 |
starServiceLossPTACsA service loss condition has occurred due to PAC/PSC/TAC failure or removal. Probable cause: Multiple PAC/PSC/TAC cards are no longer available, due to failure, removal, or operator action -- or configuration changes have been made which eliminated the availability of redundant cards. Action to be Taken: Bring additional PAC/PSC/TAC cards online to match the number of configured cards, or update the configuration to require fewer active PAC/PSC/TAC cards. Clear Condition: This condition is cleared when the number of active PAC/PSC/TAC cards reaches or exceeds the configured number. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.83 |
starServiceLossLCA service loss condition has occurred due to LC failure or removal. Probable cause: The upper and lower Line Cards (LCs) are both no longer available, due to failure, removal, or operator action. Action to be Taken: Fix or replace the line cards. Clear Condition: This condition is cleared when one of the two card becomes active. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.84 |
starServiceLossSPIOA service loss condition has occurred due to SPIO failure or removal. NOTE: Since the SPIO contains the ports used for SNMP access, this notification cannot normally be delivered as an SNMP trap. The notification will be logged and stored in the historical trap list, and if the system is configured to send INFORM PDUs the notification might be delivered at a later time. Probable cause: Both SPIOs are no longer available, due to failure, removal, or operator action. Action to be Taken: Bring at least one SPIO online. Clear Condition: This condition is cleared when a SPIO is made active NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.85 |
starIPSPAllAddrsFreeAll IP addresses are now free on the IP Pool Sharing Protocol (IPSP) primary HA. Probable Cause: IP Pool Sharing Protocol (IPSP) is running between two HAs (a primary and a secondary). The primary HA has now released the last address that was in use. This presumably is done in preparation for taking the primary HA out of server. User Action: Perform the desired maintenance on the primary HA that required taking the device out of service. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.86 |
starPCFUnreachableA PCF that the IMG communicates which is no longer reachable. Probable Cause: The PCF has failed or is otherwise unavailable, or a network connectivity problem makes it unreachable. Action to be Taken: If the PCF outage was unplanned, restart/reset the PCF; verify network connectivity Clear Condition: The condition is cleared when the PCF address becomes reachable, or if the configuration is changes to not use this server. Condition Clear Alarm: A starPCFReachable notification is generated when the pcf address becomes reachable. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.87 |
starDhcpAliveDHCP Server Alive. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.88 |
starDhcpDeadDHCP Server Dead. Probable Cause: The remote DHCP server is down or there is a network error making it unreachable. Action to be Taken: Verify that the DHCP server is functioning properly; verify network connectivity to the DHCP server. Clear Condition: The condition is cleared when the DHCP server becomes reachable, or if the configuration is changes to not use this server. Condition Clear Alarm: A starDhcpAlive notification is generated when the server becomes reachable. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.89 |
starNTPPeerUnreachableNTP Peer Unreachable. Probable Cause: The NTP server is down or unavailable, or there is a network connectivity issue that prevents access to the NTP server. Action to be Taken: Verify that the NTP server is running properly; verify that the connection to the NTP server is functioning. Clear Condition: This condition is cleared when the NTP server becomes reachable. Condition Clear Alarm: This condition is cleared by a starNTPPeerReachable notification. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.90 |
starNTPSyncLostNTP Synchronization Lost. Probable Cause: All configured NTP server are no longer available, or some/all NTP servers have been unconfigured by an operator. Action to be Taken: Verify that the NTP server(s) are running properly and that the network connections to the NTP servers are available. Check the configured of the NTP servers for correctness. If needed, configure additional NTP servers. Clear Condition: This condition is cleared when any (one) NTP server becomes reachable. Condition Clear Alarm: This condition is cleared by a starNTPSyncEstablished notification. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.91 |
starL2TPTunnelDownPeerUnreachableL2TP tunnel down due to peer unreachable. Probable Cause: Misconfiguration of the peer router address or inability to route to the peer. Action to be Taken: Verify the peer address is correct; verify that the peer is operational; verify network connectivity to the peer. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.92 |
starCardStandbyThe card is now standby. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.93 |
starLicenseUnderLimitUsage is now under the licensed session limit. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.94 |
starIPSECPriTunDownIPSEC Primary Tunnel Down NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.95 |
starIPSECPriTunUpIPSEC Primary Tunnel Up NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.96 |
starIPSECSecTunDownIPSEC Secondary Tunnel Down NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.97 |
starIPSECSecTunUpIPSEC Secondary Tunnel Up NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.98 |
starIPSECTunSwitchFailIPSEC Tunnel Switchover failed or unable to be attempted NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.99 |
starIPSECTunSwitchCompleteIPSEC Tunnel Switchover complete NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.100 |
starNwReachServerAliveNw Reacheable Server alive NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.101 |
starNwReachServerDeadNw Reacheable Server Dead. Probable Cause: The remote server is down or there is a network error making it unreachable. A starNwReachServerAlive notification will be generated when this condition is cleared NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.102 |
starStorageServerUnackedGcdrVolPurgeGTPP storage server has performed unacked GCDRs volume purge. Probable Cause: GTPP storage server has purged unacked GCDRs after hitting the max allowed configured limit on unacked GCDR in the backup database. Action to be Taken: Check for the unacked file generated for these GCDRs. Clear Condition: There is no clear condition for this notification. Condition Clear Alarm: There is no clear alarm for this notification. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.103 |
starStorageServerUnackedGcdrFileGenGTPP storage server has exported the unacked GCDRs to file from backup db. Probable Cause: GTPP storage server has generated and saved all the unacked GCDRs to file. Action to be Taken: Operator needs to ftp the generated file. Clear Condition: There is no clear condition for this notification. Condition Clear Alarm: There is no clear alarm for this notification. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.104 |
starNTPPeerReachableNTP Peer Reachable. Probable Cause: The NTP server is reachable. This could indicate a newly configured NTP server (including an initial configuration on system startup) or could indicate a previously unreachable server has become reachable. Action to be Taken: No action required. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.105 |
starNTPSyncEstablishedNTP Synchronization Established. Probable Cause: An NTP server is available when previously no server was available. This could indicuate a newly configured NTP server (including an initial configuration on system startup) or could indicate that one or more previously unreachable server(s) has become reachable. Action to be Taken: No action required. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.106 |
starSIPServiceStartA SIP service has started Action to be Taken: No action required NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.107 |
starSIPServiceStopA SIP service has stopped Action to be Taken: No action required NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.108 |
starVIMServiceStartA VIM service has started Action to be taken: No action required NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.109 |
starVIMServiceStopA VIM service has stopped. This is because of application out-of-service or if vim is down or no app. server Action to be taken: No action required NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.110 |
starCHATCONFServiceStartA CHAT/CONF service has started Action to be taken: No action required NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.111 |
starCHATCONFServiceStopA CHAT/CONF service has stopped. This is because of application out-of-service or if chatconf is down or no app. server Action to be taken: No action required NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.112 |
starSIPRouteNomatchSIP session has failed since there is no match in the routing table with matching prefix Action to be taken: Operator has to configure with matching prefix if required NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.113 |
starL3AddrUnreachableA L3 Address is unreachable through the specific slot and port. Action to be taken: No action required NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.114 |
starSWUpgradeStartAn operator has begun to upgrade the software on the chassis. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.115 |
starSWUpgradeCompleteAn operator-initiated software upgrade has been completed. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.116 |
starSWUpgradeAbortedAn operator-initiated software upgrade has been aborted. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.117 |
starBGPPeerSessionUpThe BGP peer session to the specified IP address is operational. This may indicate the initial configuration of a new peer, the initial connectivity after a system restart, or the restoration of connectivity after a starBGNPeerSessionDown event. Action to be Taken: No action required. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.118 |
starBGPPeerSessionDownThe BGP peer session to the specified IP address is no longer operational. Probable Cause: The BGP peer is not-operational; the network between the ST16 and the BGP peer is experiencing an outage; LC failure(s) on the ST16. Action to be Taken: Verify the BGP peer is operational; verify network connectivity to the BGP peer. Clear Condition Alarm: A starBGPPeerSessionUp is generated when connectivity is reestablished NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.119 |
starSRPActiveThe SRP Chassis Status is now Active. Action to be Taken: No action is required. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.120 |
starSRPStandbyThe SRP Chassis Status is now Standby. Action to be Taken: No action is required. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.121 |
starBGPPeerReachableThe monitored BGP peer is now Reachable. This notification can represent the initial detection of the peer's state, or the reconnection to a peer after a starBGPPeerDown notification. Action to be Taken: No action is required. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.122 |
starBGPPeerUnreachableThe monitored BGP peer is now Unreachable. Action to be Taken: Verify that the BGP Peer is running and is properly configured. Verify the network link to the BGP Peer. Clear Condition: This condition is cleared when communication with the BGP peer is reestablished. Condition Clear Alarm: This condition is cleared by a starBGPPeerReachable notification. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.123 |
starSRPAAAReachableThe SRP AAA monitor has found a reachable AAA server. This notification can represent the initial detection of an AAA server, or the restoration of reachability after a starSRPAAAUnreachable notification. This notification is only generated if there was previously no reachable AAA server. Action to be Taken: No action required. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.124 |
starSRPAAAUnreachableThe SRP AAA monitor has determined that all AAA servers are unreachable. Action to be Taken: Verify the state of the configured AAA Server(s) and restart them if required. Verify the network link to the AAA Server(s). Configure additional AAA Servers if required. Clear Condition: This condition is cleared when communication with any single AAA service is (re)established. Condition Clear Alarm: This condition is cleared by a starSRPAAAReachable notification. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.125 |
starSRPSwitchoverInitiatedAn SRP (ICSR) Switchover operation has been initiated by an operator. Action to be Taken: Verify that the switchover was a planned operator action. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.126 |
starSRPCheckpointFailureThe system has detected that a checkpoint messaged failed to be sent successfully to the standby HA. If the active HA were to fail, this information will be lost. Action to be Taken: Verify the communication path to the Standby HA. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.127 |
starSRPConfigOutOfSyncThe system has detected that the standby HA has a different configuration than the active HA. In the event of a failure of the active HA, it is possible that the standby HA is not configured properly to be able to take over. Action to be Taken: Update the configuration of the standby HA to match the active HA. Clear Condition: This condition is cleared when the active HA confirms that the standby HA has an identify configuration. Condition Clear Alarm: This condition is cleared by a starSRPConfigInSync notification. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.128 |
starSRPConfigInSyncThe system has detected that the standby HA has a matching configuration as the active HA. This notification is generated only after a starSRPConfigOutOfSync notification. Action to be Taken: No action required. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.129 |
starGESwitchFailureA failure of an internal Gigabit Ethernet switch has been detected. If it is possible to determine the slot containing the failed switch it is identified in starSlotNum, otherwise starSlotNum is 0. Action to be Taken: If this condition persists, the identified card needs to be replaced. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.130 |
starSIPRouteServerAvailableSIP route server is available Action to be taken: None NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.131 |
starSIPRouteServerUnavailableSIP session has failed since the server is unavailable Action to be taken: Operator has to check the reasons for the unavailability of the server and act accordingly NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.132 |
starFMDMaxCallRateReachedFMD max call rate reached Action to be taken: Increase the value of fmd-max-call-rate or set no fmd-max-call-rate Condition Clear Alarm: This condition is cleared by a starFMDCallRateUnderControl notification NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.133 |
starFMDCallRateUnderControlFMD call rate under control Action to be taken: None NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.134 |
starStorageServerCPUBusyGTPP Storage Server is experiencing high CPU usage. The usage has exceeded an operator-configure value. Note that this is an external server, not part of the ST16. Probable Cause: The amount of information being sent to the Storage Server is approaching the server's capacity; the Storage Server has other tasks running on it which are taking CPU time; a problem with the Storage Server is causing the CPU to be abnormally busy; Condition Clear Alarm: This condition is cleared by a starStorageServerCPUNormal notification NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.135 |
starStorageServerCPUNormalGTPP Storage Server CPU usage has returned to a normal range. Note that this is an external server, not part of the ST16. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.136 |
starStorageServerDiskSpaceLowGTPP Storage Server is experiencing low available disk space. The available disk space has gone below an operator-configure value. Note that this is an external server, not part of the ST16. Probable Cause: The amount of information being sent to the Storage Server is approaching the server's capacity; the Storage Server has other information consuming disk space; a problem with the Storage Server is causing less disk space to be available then normal. Condition Clear Alarm: If the GTPP Storage Server is configured to run in an 'alarm' model, this condition is cleared by a starStorageServerDiskSpaceOK notification. Otherwise the starStorageServerDiskSpaceLow notification will be generated periodically until the condition is cleared. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.137 |
starStorageServerDiskSpaceOKGTPP Storage Server available disk space to a normal range. Note that this is an external server, not part of the ST16. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.138 |
starCardSPOFAlarmThe identified card is a Single Point of Failure (SPOF). There is no redundant card available to take over in the event of a failure. Probable Cause: This can be caused by an improper configuration, or by the failure or removal of other cards in the system. Action to be Taken: Install or configure additional redundant cards. Clear Condition: A starCardSPOFClear notification will be generated is a redundant card becomes available. Notifications like starCardDown could also obsolete this notification NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.139 |
starCardSPOFClearThe identified card is no longer a Single Point of Failure (SPOF) NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.140 |
starStorageServerOldGcdrPendingGTPP Storage Server reports that GCDR files have been unprocessed for too long. Note that this is an external server, not part of the ST16. Probable Cause: No action has been taken long for the GCDR files generated by Storage Server. Condition Clear Alarm: If the GTPP Storage Server is configured to run in an 'alarm' model, this condition is cleared by a starStorageServerOldGcdrCleared notification. Otherwise the starStorageServerOldGCDRPending notification will be generated periodically NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.141 |
starStorageServerOldGcdrClearedGCDR files on the Storage Server have been processed on the Storage Server. The threshold condition is now clear. Note that this is an external server, not part of the ST16. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.142 |
starLoginFailureA login failure occurred attempting to establish a CLI or FTP session. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.143 |
starIPSGServiceStartA IP Services Gateway (IPSG) Service has started Action to be Taken: No action required NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.144 |
starIPSGServiceStopA IP Services Gateway (IPSG) Service has stopped. Probable Cause: This is typically caused by operator invention. In unusual cases it can be caused by the loss of resources (PACs/PSCs) to support the running configuration. Action to be Taken: If the IPSG service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured PACs/PSCs are present and running in the system. Check the crash logs for an indication of a software failure. Clear Condition: Verify that the IPSG service is operational. Condition Clear Alarm: A starIPSGServiceStart notification will be generated when the service is restarted NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.145 |
starHAUnreachableA monitored HA is unreachable from the identified FA Service. Condition Clear Alarm: A starHAReachable notification will be generated when the HA becomes reachable NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.146 |
starHAReachableA monitored HA is now reachable. A starHAReachable notification is only generated for monitored HA's which previously were marked unreachable. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.147 |
starASNGWServiceStartA WiMAX ASN Gateway (ASNGW) Service has started Action to be Taken: No action required NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.148 |
starASNGWServiceStopA WiMAX ASN Gateway (ASNGW) Service has stopped. Probable Cause: This is typically caused by operator invention. In unusual cases it can be caused by the loss of resources (PACs/PSCs) to support the running configuration. Action to be Taken: If the ASNGW service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured PACs/PSCs are present and running in the system. Check the crash logs for an indication of a software failure. Clear Condition: Verify that the ASNGW service is operational. Condition Clear Alarm: A starASNGWServiceStart notification will be generated when the service is restarted NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.149 |
starTaskFailedA non-critical task has failed and the appropriate recovery steps begun. The failing task will be restarted. Probable Cause: Software error Actions to be Taken: Examine the admin logs for an indication of the source of the failure. Clear Condition: Verify that the task has been restarted. Condition Clear Alarm: A starTaskRestart notification will be generated when task has successfully restarted. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.150 |
starTaskRestartA non-critical task has restarted after an earlier failure. Actions to be Taken: None NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.151 |
starCSCFServiceStartAn CSCF Service has started Action to be Taken: No action required NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.152 |
starCSCFServiceStopAn CSCF Service has stopped Probable Cause: This is typically caused by operator invention. In unusual cases it can be caused by the loss of resources (PACs/PSCs) to support the running configuration. Action to be Taken: If the CSCF service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured PACs/PSCs are present and running in the system. Check the crash logs for an indication of a software failure. Clear Condition: Verify that the CSCF service is operational. Condition Clear Alarm: A starCSCFServiceStart notification will be generated when the service is restarted NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.153 |
starDhcpServiceStartedA DHCP Service has started Action to be Taken: No action required NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.154 |
starDhcpServiceStoppedA DHCP Service has stopped Probable Cause: This is typically caused by operator invention. In unusual cases it can be caused by the loss of resources (PACs/PSCs) to support the running configuration. Action to be Taken: If the DHCP service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured PACs/PSCs are present and running in the system. Check the crash logs for an indication of a software failure. Clear Condition: Verify that the DHCP service is operational. Condition Clear Alarm: A starDHCPServiceStart notification will be generated when the service is restarted NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.155 |
starContFiltDBErrorThe Content Filtering OPTCMDB file error displayed with an error code. Action to be Taken: If no OPTCMDB file is there in the specified directory then Place a OPTCMDB-FULL file in the directory and give an upgrade command or place an OPTCMDB file and load the SRDBs by killing them all. Condition Clear Alarm: This condition is cleared by a starContFiltDBErrorClear notification NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.156 |
starContFiltDBErrorClearThe Content Filtering OPTCMDB file error removed. Action to be Taken: No action required NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.157 |
starBLDBErrorThe Blacklisting OPTBLDB file error displayed with an error code. Action to be Taken: If no or invalid OPTBLDB file is there in the specified directory then Place a OPTBLDB_FULL file in the directory and give an upgrade command. Condition Clear Alarm: This condition is cleared by a starBLDBErrorClear notification NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.158 |
starBLDBErrorClearThe Blacklisting OPTBLDB file error removed. Action to be Taken: No action required NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.159 |
starContFiltDBUpgradeErrorThe Content Filtering OPTCMDB file error displayed with an error code. Action to be Taken: Place a valid OPTCMDB-FULL file or OPTCMDB_INCR file in the directory and give an upgrade command. Condition Clear Alarm: This condition is cleared by a starContFiltDBUpgradeErrorClear notification NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.160 |
starContFiltDBUpgradeErrorClearThe Content Filtering OPTCMDB file error removed. Action to be Taken: No action required NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.161 |
starBLDBUpgradeErrorThe Blacklisting OPTBLDB file error displayed with an error code. Action to be Taken: Place a valid OPTBLDB-FULL file file in the directory and give an upgrade command. Condition Clear Alarm: This condition is cleared by a starBLDBUpgradeErrorClear notification NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.162 |
starBLDBUpgradeErrorClearThe Blacklisting OPTBLDB file error removed. Action to be Taken: No action required NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.163 |
starIPSECDynTunUpIPSEC Dynamic Tunnel Up. Action to be Taken: No action required NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.164 |
starIPSECDynTunDownIPSEC Dynamic Tunnel Down. Condition Clear Alarm: a starIPSECDynTunUp notification will be sent when the tunnel is operational again. Note however that a tunnel may go down due to administrative action, or the tunnel may not longer be required, thus a starIPSECDynTunUp may not follow. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.165 |
starHeartbeatPeriodic SNMP heartbeat. A starHeartbeat notification can be generated periodically if the system is configured to do so. These notifications serve only to validate that there is communication to external entities which sink SNMP notifications NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.166 |
starOverloadSystemA system-wide congestion overload condition has occurred. Probable Cause: This is the result of an operator-configured congestion overload value reached. This notification indicated a chassis-wide overload condition, typically overall system usage reaching some fraction of capacity. Once this limit is reached, the configured behavior is taken. This will cause certain older and/or dormant calls to be dropped in favor of newer calls. Note that this is similar to, but different than, the starCongestion notification. Typically the 'overload' condition will be configured to trigger at an earlier point. Actions to be Taken: Verify that the congestion overload thresholds are correct; if the congested state is seem repeatedly, or for sustained periods of time, additional system capacity may need to be brought online. This system is cleared when the use of the specific resource falls below the configured limit. Condition Clear Alarm: A starOverloadSystemClear notification is sent when the system overload condition is clear NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.167 |
starOverloadSystemClearA system-wide congestion overload condition has cleared NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.168 |
starOverloadServiceA service-specific congestion overload condition has occurred. Probable Cause: This is the result of an operator-configured congestion overload value reached. This notification indicated a service-specific overload condition, typically the use of the service reaching some fraction of capacity. Once this limit is reached, the configured behavior is taken. This will cause certain older and/or dormant calls to be dropped in favor of newer calls. Note that this is similar to, but different than, the starCongestion notification. Typically the 'overload' condition will be configured to trigger at an earlier point. Since this is a service-specific notification, it is possible to receive multipe notifications for different services. Each Actions to be Taken: Verify that the congestion overload thresholds are correct; if the congested state is seem repeatedly, or for sustained periods of time, additional system capacity may need to be brought online. This system is cleared when the use of the specific resource falls below the configured limit. Condition Clear Alarm: A starOverloadServiceClear notification is sent when the service-specific overload condition is clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.169 |
starOverloadServiceClearA service-specific congestion overload condition has cleared NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.170 |
starStorageServerClusterStateChangeGTPP Storage Server cluster state has been changed. GTPP Storage Server may have gone offline from all the nodes or switchover has been occured. Note that this is an external server, not part of the ST16. Probable Cause: GTPP Storage Server cluster hardware/software component failure or maintenance of GTPP Storage Server is in progress NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.171 |
starStorageServerClusSwitchOverGTPP Storage Server switchover from current online node to next available node in cluster. Note that this is an external server, not part of the ST16. Probable Cause: GTPP Storage Server cluster Hardware/Software component failure or maintenance of GTPP Storage Server is in progress NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.172 |
starStorageServerClusPathFailGTPP Storage Server cluster disk path failure has been occured. Note that this is an external server, not part of the ST16. Probable Cause: Fibre cable may have been damaged, fibre cable may have been pulled out or disk fault may have been occured. Condition Clear Alarm: This condition is cleared by a starStorageServerClusPathOK notification NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.173 |
starStorageServerClusPathOKGTPP Storage Server cluster disk path failure has been restored to ok state. Note that this is an external server, not part of the ST16 NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.174 |
starStorageServerClusInterCFailGTPP Storage Server cluster transport path (Interconnect) failure has been occured. Note that this is an external server, not part of the ST16. Probable Cause: Interconnect interface may have been failed, Interconnect interface cable may have been pulled out. Condition Clear Alarm: This condition is cleared by a starStorageServerClusInterCOK notification NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.175 |
starStorageServerClusInterCOKGTPP Storage Server cluster transport path (Interconnect) failure has been restored to an operational state. Note that this is an external server, not part of the ST16 NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.176 |
starStorageServerClusIntfFailGTPP Storage Server cluster GE Interface failure has been occured. Note that this is an external server, not part of the ST16. Probable Cause: Interface may have been failed, interface cable may have been pulled out. Condition Clear Alarm: This condition is cleared by a starStorageServerClusIntfOK notification NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.177 |
starStorageServerClusIntfOKGTPP Storage Server cluster GE Interface failure failure has been restored to ok state. Note that this is an external server, not part of the ST16 NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.178 |
starStorageServerMemLowGTPP Storage Server is experiencing a low memory condition. Note that this is an external server, not part of the ST16. Probable Cause: The amount of free memory used by Storage Server is approaching the server's capacity; Condition Clear Alarm: This condition is cleared by a starStorageServerMemNormal notification NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.179 |
starStorageServerMemNormalGTPP Storage Server Memory usage has returned to a normal range. Note that this is an external server, not part of the ST16. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.180 |
starPDIFServiceStartA PDIF Service has started Action to be Taken: No action required NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.181 |
starPDIFServiceStopA PDIF Service has stopped. Probable Cause: This is typically caused by operator invention. In rare cases it can be caused by the loss of resources (PACs) to support the running configuration. Action to be Taken: If the PDIF service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured PACs are present and running in the system. Check the crash logs for an indication of a software failure. Clear Condition: Verify that the PDIF service is operational. Condition Clear Alarm: A starPDIFServiceStart notification will be generated when the service is restarted NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.182 |
starSessMgrRecoveryCompleteA Sess Mgr Recovery Complete Probable Cause: This is typically caused by session manager task fails and successfully completed recovery. Action to be Taken: None NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.183 |
starDiameterPeerDownA diameter peer is down. Problem Cause: The diameter peer has failed, or a network connectivity prevents reaching the peer. Condition Clear Alarm: A starDiameterPeerUp notification will be generated when the peer is up NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.184 |
starDiameterPeerUpA diameter peer is up. This notification is only generated for peers which have previously been declared down. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.185 |
starDiameterServerUnreachableA diameter server is down. Problem Cause: The diameter server has failed, or a network connectivity prevents reaching the server. Condition Clear Alarm: A starDiameterServerReachable notification will be generated when the server is reachable NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.186 |
starDiameterServerReachableA diameter server is up. This notification is only generated for servers which have previously been declared unreachable. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.187 |
starCDRFileRemovedA Charging Data Record (CDR) file has been deleted from the system due to a lack of available storage space. When required, the system deletes old files to make space for new files. This notification is only generated when specifically enabled on the system. Probable Cause: CDR files are not being moved off the system, or these files are not being deleted after they have been transferred. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.188 |
starCSCFPeerServerReachableA peer server is reachable NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.189 |
starCSCFPeerServerUnreachableA peer server is unreachable NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.190 |
starCLIConfigModeAn interactive CLI session has enter 'configuration' mode for the specified context. This CLI user can thus potentially start issuing configuration commands which will impact the overall system configuration. Note that this notification is not enabled by default; it is only generated if the system is specifically configured to enable it. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.192 |
starSGSNServiceStartA SGSN Service has started Action to be Taken: No action required NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.194 |
starSGSNServiceStopA SGSN Service has stopped. Probable Cause: This is typically caused by operator invention. In unusual cases it can be caused by the loss of resources (PACs/PSCs) to support the running configuration. Action to be Taken: If the SGSN service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured PACs/PSCs are present and running in the system. Check the crash logs for an indication of a software failure. Clear Condition: Verify that the SGSN service is operational. Condition Clear Alarm: A starSGSNServiceStart notification will be generated when the service is restarted NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.195 |
starM3UAPCUnavailableM3UA Route to the Point code becomes unavailable. Possibe reason: 1. Received destination unavailable (DUNA) message or 2. SCTP association is down or 3. Remote peer server is down Condition Clear Alarm: A starM3UAPCAvailable notification will be generated when the reemore peer identified by the point code becomes reachable NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.196 |
starM3UAPCAvailableM3UA Route to the Point code becomes available. Possible reason: 1. Received destination available (DAVA) message. 2. SCTP association is up 3. Remote peer server is up starM3UAPCAvailable is generated only when a previous starM3UAPCUnavailable is generated. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.197 |
starThreshCPUUtilizationThe overall CPU utilization for the identified processor has exceeded for configured threshold value for the current monitoring period. Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearCPUUtilization notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.200 |
starThreshClearCPUUtilizationThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.201 |
starThreshCPUMemoryThe amount of available memory for the identified processor has fallen below the configured threshold value. Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearCPUMemory notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.202 |
starThreshClearCPUMemoryThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.203 |
starThreshLicenseThe percentage available, licensed subscribers has fallen below the configured threshold value. Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearLicense notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.204 |
starThreshClearLicenseThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.205 |
starThreshSubscriberTotalThe total number of subscribers is above the configured threshold value. Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearSubscriberTotal notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.206 |
starThreshClearSubscriberTotalThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.207 |
starThreshSubscriberActiveThe total number of active subscribers is above the configured threshold value. Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearSubscriberActive notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.208 |
starThreshClearSubscriberActiveThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.209 |
starThreshPortRxUtilThe Rx utilization of the port has exceeded the configured threshold value during the current monitoring period. Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearPortRxUtil notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.210 |
starThreshClearPortRxUtilThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.211 |
starThreshPortTxUtilThe Tx utilization of the port has exceeded the configured threshold value during the current monitoring period. Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearPortTxUtil notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.212 |
starThreshClearPortTxUtilThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.213 |
starThreshPortHighActivityHigh activity on the port has exceeded the configured threshold value during the current monitoring period. Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearPortHighActivity notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.214 |
starThreshClearPortHighActivityThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.215 |
starThreshAAAAuthFailThe number of AAA authentication failures has exceeded the configured threshold during the current monitoring period. Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearAAAAuthFail notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.216 |
starThreshClearAAAAuthFailThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.217 |
starThreshAAAAuthFailRateThe percentage of AAA authentication requests which failed has exceeded the configured threshold during the current monitoring period. Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearAAAAuthFailRate notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.218 |
starThreshClearAAAAuthFailRateThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.219 |
starThreshAAAAcctFailThe number of AAA accounting failures has exceeded the configured threshold during the current monitoring period. Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearAAAAcctFail notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.220 |
starThreshClearAAAAcctFailThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.221 |
starThreshAAAAcctFailRateThe percentage of AAA accounting requests which failed has exceeded the configured threshold during the current monitoring period. Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearAAAAcctFailRate notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.222 |
starThreshClearAAAAcctFailRateThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.223 |
starThreshAAARetryRateThe percentage of AAA requests which has to be retried has exceeded the configured threshold during the current monitoring period. Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearAAARetryRate notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.224 |
starThreshClearAAARetryRateThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.225 |
starThreshCallSetupThe number of call setup operations has exceeded the configured threshold during the current monitoring period. Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearCallSetup notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.226 |
starThreshClearCallSetupThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.227 |
starThreshCallSetupFailureThe number of call setup operations which failed has exceeded the configured threshold during the current monitoring period. Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearCallSetupFailure notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.228 |
starThreshClearCallSetupFailureThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.229 |
starThreshCallRejectNoResourceThe number of call setup operations which were rejected due to a no resource condition has exceeded the configured threshold during the current monitoring period. Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearCallRejectNoResource notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.230 |
starThreshClearCallRejectNoResourceThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.231 |
starThreshPacketsFilteredDroppedThe number of user data packets filtered has exceeded the configured threshold for the current monitoring period. Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearPacketsFilteredDropped notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.232 |
starThreshClearPacketsFilteredDroppedThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.233 |
starThreshPacketsForwardedThe number of user data packets forwarded has exceeded the configured threshold for the current monitoring period. Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearPacketsForwarded notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.234 |
starThreshClearPacketsForwardedThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.235 |
starThreshSessCPUThroughputThe total session throughout for the specified processor has exceeded the configured threshold for the current monitoring period. Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearSessCPUThroughput notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.236 |
starThreshClearSessCPUThroughputThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.237 |
starThreshIPPoolAvailThe available IP pool addresses in a context has fallen below the configured threshold Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearIPPoolAvail notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.238 |
starThreshClearIPPoolAvailThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.239 |
starThreshCPUUtilization10SecThe CPU utilization of 10 second measurement for the identified processor has exceeded for configured threshold value for the current monitoring period. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.240 |
starThreshClearCPUUtilization10SecThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.241 |
starThreshCPULoadThe CPU load for the identified processor has exceeded for configured threshold value for the current monitoring period. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.242 |
starThreshClearCPULoadThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.243 |
starThreshCPUMemUsageThe CPU mem usage for the identified processor has exceeded for configured threshold value for the current monitoring period. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.244 |
starThreshClearCPUMemUsageThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.245 |
starThreshPDSNSessionsThe total number of PDSN sessions is above the configured threshold value. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.246 |
starThreshClearPDSNSessionsThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.247 |
starThreshGGSNSessionsThe total number of GGSN sessions is above the configured threshold value. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.248 |
starThreshClearGGSNSessionsThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.249 |
starThreshHASessionsThe total number of HA sessions is above the configured threshold value. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.250 |
starThreshClearHASessionsThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.251 |
starThreshLNSSessionsThe total number of L2TP LNS sessions is above the configured threshold value. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.252 |
starThreshClearLNSSessionsThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.253 |
starThreshPerServicePDSNSessionsThe total number of PDSN sessions in a service is above the configured threshold value. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.254 |
starThreshClearPerServicePDSNSessionsThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.255 |
starThreshPerServiceGGSNSessionsThe total number of GGSN sessions in a service is above the configured threshold value. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.256 |
starThreshClearPerServiceGGSNSessionsThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.257 |
starThreshPerServiceHASessionsThe total number of HA sessions in a service is above the configured threshold value. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.258 |
starThreshClearPerServiceHASessionsThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.259 |
starThreshPerServiceLNSSessionsThe total number of L2TP LNS sessions in a service is above the configured threshold value. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.260 |
starThreshClearPerServiceLNSSessionsThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.261 |
starThreshIPPoolHoldThe percentage IP pool addresses in HOLD state in a context has gone above the configured threshold NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.262 |
starThreshClearIPPoolHoldThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.263 |
starThreshIPPoolUsedThe percentage IP pool addresses in USED state in a context has gone above the configured threshold NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.264 |
starThreshClearIPPoolUsedThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.265 |
starThreshIPPoolReleaseThe percentage IP pool addresses in RELEASE state in a context has gone above the configured threshold NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.266 |
starThreshClearIPPoolReleaseThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.267 |
starThreshIPPoolFreeThe percentage IP pool addresses in HOLD state in a context has gone below the configured threshold NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.268 |
starThreshClearIPPoolFreeThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.269 |
starThreshAAAAcctArchiveThe AAA accounting archive size has gone above the configured threshold NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.270 |
starThreshClearAAAAcctArchiveThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.271 |
starThreshPortSpecRxUtilThe Rx utilization of the port has exceeded the configured threshold value during the current monitoring period. Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearPortSpecRxUtil notification will be generated when the measured value falls below the threshold.deprecated NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.272 |
starThreshClearPortSpecRxUtilThe threshold condition is now clear.deprecated NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.273 |
starThreshPortSpecTxUtilThe Tx utilization of the port has exceeded the configured threshold value during the current monitoring period. Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearPortSpecTxUtil notification will be generated when the measured value falls below the threshold.deprecated NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.274 |
starThreshClearPortSpecTxUtilThe threshold condition is now clear.deprecated NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.275 |
starThreshHACallSetupRateThe per-context HA call setup rate (calls per second) has gone above the configured threshold Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearHACallSetupRate notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.276 |
starThreshClearHACallSetupRateThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.277 |
starThreshHASvcCallSetupRateThe per-service HA Call setup rate (calls per second) has gone above the configured threshold Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearHASvcCallSetupRate notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.278 |
starThreshClearHASvcCallSetupRateThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.279 |
starThreshHASvcRegReplyErrorThe per-service HA Reg Reply Error count has gone above the configured threshold Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearHASvcRegReplyError notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.280 |
starThreshClearHASvcRegReplyErrorThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.281 |
starThreshHASvcReregReplyErrorThe per-service HA Rereg Reply Error count has gone above the configured threshold Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearHASvcReregReplyError notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.282 |
starThreshClearHASvcReregReplyErrorThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.283 |
starThreshHASvcDeregReplyErrorThe per-service HA Dereg Reply Error count has gone above the configured threshold Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearHASvcDeregReplyError notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.284 |
starThreshClearHASvcDeregReplyErrorThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.285 |
starThreshFASvcRegReplyErrorThe Per-Service FA Reg Reply Error count has gone above the configured threshold Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearFASvcRegReplyError notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.286 |
starThreshClearFASvcRegReplyErrorThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.287 |
starThreshPDSNCallSetupRateThe Per-Context PDSN Call Setup Rate (calls per second) has gone above the configured threshold Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearPDSNCallSetupRate notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.288 |
starThreshClearPDSNCallSetupRateThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.289 |
starThreshPDSNSvcCallSetupRateThe Per-Service PDSN Call Setup Rate (calls per second) has gone above the configured threshold Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearPDSNSvcCallSetupRate notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.290 |
starThreshClearPDSNSvcCallSetupRateThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.291 |
starThreshPDSNSvcA11RRPFailureThe Per-Service PDSN A11 RRP Failure count has gone above the configured threshold Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearPDSNSvcA11RRPFailure notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.292 |
starThreshClearPDSNSvcA11RRPFailureThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.293 |
starThreshPDSNSvcA11RRQMsgDiscardThe Per-Service PDSN A11 RRQ Msg Discard count has gone above the configured threshold Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearPDSNSvcA11RRQMsgDiscard notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.294 |
starThreshClearPDSNSvcA11RRQMsgDiscardThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.295 |
starThreshPDSNSvcA11RACMsgDiscardThe Per-Service PDSN A11 RAC Msg Discard count has gone above the configured threshold Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearPDSNSvcA11RACMsgDiscard notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.296 |
starThreshClearPDSNSvcA11RACMsgDiscardThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.297 |
starThreshPDSNSvcA11PPPSendDiscardThe Per-Service PDSN A11 PPP Send Discard count has gone above the configured threshold Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearPDSNSvcA11PPPSendDiscard notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.298 |
starThreshClearPDSNSvcA11PPPSendDiscardThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.299 |
starThreshAAAMgrQueueThe Per-AAA Manager internal request queue usage has gone above the configured threshold Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearAAAMgrQueue will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.300 |
starThreshClearAAAMgrQueueThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.301 |
starThreshCPUOrbsWarnThe ORBs task has exceeding the CPU usage configured as a warning NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.302 |
starThreshClearCPUOrbsWarnThe threshold condition is now clear NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.303 |
starThreshCPUOrbsCriticalThe ORBs task has exceeded the CPU usage configured as a critical error NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.304 |
starThreshClearCPUOrbsCriticalThe threshold condition is now clear NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.305 |
starThreshRPSetupFailRateThe RP call setup failure rate has exceeded the configured threshold NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.306 |
starThreshClearRPSetupFailRateThe threshold condition is now clear NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.307 |
starThreshPPPSetupFailRateThe PPP call setup failure rate has exceeded the configured threshold NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.308 |
starThreshClearPPPSetupFailRateThe threshold condition is now clear NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.309 |
starThreshStorageUtilizationThe utilization of a mass storage device has exeeded the configured threshold NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.310 |
starThreshClearStorageUtilizationThe threshold condition is now clear NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.311 |
starThreshDCCAProtocolErrorsThe number of DCCA Protocol Errors has exceeded the configured threshold NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.312 |
starThreshClearDCCAProtocolErrorsThe threshold condition is now clear NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.313 |
starThreshDCCABadAnswersThe number of DCCA BadAnswers has exceeded the configured threshold NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.314 |
starThreshClearDCCABadAnswersThe threshold condition is now clear NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.315 |
starThreshDCCAUnknownRatingGroupThe number of DCCA UnknownRatingGroup has exceeded the configured threshold NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.316 |
starThreshClearDCCAUnknownRatingGroupThe threshold condition is now clear NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.317 |
starThreshDCCARatingFailedThe number of DCCA RatingFailed has exceeded the configured threshold NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.318 |
starThreshClearDCCARatingFailedThe threshold condition is now clear NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.319 |
starThreshIPSECIKERequestsThe number of IPSEC IKE requests seen for this HA service has exceeded the configured threshold. Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearIPSECIKERequests notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.320 |
starThreshClearIPSECIKERequestsThe threshold condition is now clear NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.321 |
starThreshIPSECIKEFailuresThe number of IPSEC IKE failures seen for this HA service has exceeded the configured threshold. Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearIPSECIKEFailures notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.322 |
starThreshClearIPSECIKEFailuresThe threshold condition is now clear NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.323 |
starThreshIPSECIKEFailRateThe rate of IPSEC IKE failures (as a percentage of total requests) seen for this HA service has exceeded the configured threshold. Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearIPSECIKEFailRate notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.324 |
starThreshClearIPSECIKEFailRateThe threshold condition is now clear NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.325 |
starThreshIPSECTunSetupThe number of IPSEC tunnels setup over the last measurement period for this HA service has exceeded the configured threshold. Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearIPSECTunSetup notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.326 |
starThreshClearIPSECTunSetupThe threshold condition is now clear NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.327 |
starThreshIPSECTunEstablThe current number of IPSEC tunnels established for this HA service has exceeded the configured threshold. Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearIPSECTunEstabl notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.328 |
starThreshClearIPSECTunEstablThe threshold condition is now clear NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.329 |
starThreshIPSECCallReqRejThe number of IPSEC Rejected Call Requests has exceeded the configured threshold. Probable Cause: This is a user configurable threshold. Reject Call Requests indicate that an IPSEC Manager has reached its maximum allowable number of IPSEC tunnels. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearIPSECTunnelsTotal notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.330 |
starThreshClearIPSECCallReqRejThe threshold condition is now clear NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.331 |
starThreshCSCFSvcRouteFailureThe Per-Service CSCF Route failure count has gone above the configured threshold Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearCSCFSvcRouteFailure notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.332 |
starThreshClearCSCFSvcRouteFailureThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.333 |
starThreshContFiltRatingThe number of Content Filtering Rating operations performed has gone above the configured threshold. Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearContFiltRating notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.334 |
starThreshClearContFiltRatingThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.335 |
starThreshContFiltBlockThe number of Content Filtering Block operations performed has gone above the configured threshold. Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearContFiltBlock notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.336 |
starThreshClearContFiltBlockThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.337 |
starThreshCDRFileSpaceThe CDR file space usage is above the configured threshold percentage Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearCDRFileSpaceOverLimit notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.338 |
starThreshClearCDRFileSpaceThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.339 |
starThreshEDRFileSpaceThe EDR file space usage is above the configured threshold percentage Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearEDRFileSpaceOverLimit notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.340 |
starThreshClearEDRFileSpaceThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.341 |
starThreshPDIFCurrSessThe chassis-wide count of current PDIF sessions has gone above the configured threshold Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearPDIFCurrSess notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.342 |
starThreshClearPDIFCurrSessThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.343 |
starThreshPDIFCurrActSessThe chassis-wide count of current PDIF active sessions has gone above the configured threshold Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearPDIFCurrActiveSess notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.344 |
starThreshClearPDIFCurrActSessThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.345 |
starThreshCDRFlowControlThe number of Charging Data Record (CDR) records which have been discarded at an ACSMGR due to flow control has gone above the configured threshold. Probable Cause: This is a user configurable threshold. This threshold potentially indicates an overload condition due which prevents processes CDR messages at the same rate as the incoming packets. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.346 |
starThreshClearCDRFlowControlThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.347 |
starThreshASNGWSessTimeoutThe ASNGW session timeout has gone above the configured threshold Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshASNGWSessTimeout notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.348 |
starThreshClearASNGWSessTimeoutThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.349 |
starThreshASNGWSessSetupTimeoutThe ASNGW session setup timeout has gone above the configured threshold Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshASNGWSessSetupTimeout notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.350 |
starThreshClearASNGWSessSetupTimeoutThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.351 |
starThreshASNGWAuthFailThe number of ASNGW authentication failures has exceeded the configured threshold during the current monitoring period. Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshASNGWAuthFail notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.352 |
starThreshClearASNGWAuthFailThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.353 |
starThreshASNGWR6InvNaiThe number of ASNGW R6 Invalid Nai has exceeded the configured threshold during the current monitoring period. Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshASNGWR6InvNai notification will be generated when the measured value falls below the threshold. This trap is obsolete.obsolete NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.354 |
starThreshClearASNGWR6InvNaiThe threshold condition is now clear. This trap is obsolete.obsolete NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.355 |
starThreshASNGWMaxEAPRetryThe number of ASNGW Maximum EAP Retry has exceeded the configured threshold during the current monitoring period. Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshASNGWMaxEAPRetry notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.356 |
starThreshClearASNGWMaxEAPRetryThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.357 |
starThreshASNGWNWEntryDenialThe number of ASNGW Network Entry Denial has exceeded the configured threshold during the current monitoring period. Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshASNGWNWEntryDenial notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.358 |
starThreshClearASNGWNWEntryDenialThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.359 |
starThreshASNGWHandoffDenialThe number of ASNGW Handoff Denial has exceeded the configured threshold during the current monitoring period. Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshASNGWHandoffDenial notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.360 |
starThreshClearASNGWHandoffDenialThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.361 |
starThreshSGSNSessionsThe total number of SGSN sessions is above the configured threshold value. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.362 |
starThreshClearSGSNSessionsThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.363 |
starThreshPerServiceSGSNSessionsThe total number of SGSN sessions in a service is above the configured threshold value. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.364 |
starThreshClearPerServiceSGSNSessionsThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.365 |
starThreshSGSNPdpSessionsThe total number of SGSN PDP sessions is above the configured threshold value. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.366 |
starThreshClearSGSNPdpSessionsThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.367 |
starThreshPerServiceSGSNPdpSessionsThe total number of SGSN PDP sessions in a service is above the configured threshold value. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.368 |
starThreshClearPerServiceSGSNPdpSessionsThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.369 |
starThreshFWDosAttackThe cumulative number of FW Dos-Attacks has exceeded the configured threshold during the current monitoring period. Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearFWDosAttack notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.370 |
starThreshClearFWDosAttackThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.371 |
starThreshFWDropPacketThe cumulative number of FW Dropped Packets has exceeded the configured threshold during the current monitoring period. Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearFWDropPacket notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.372 |
starThreshClearFWDropPacketThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.373 |
starThreshFWDenyRuleThe cumulative number of FW Deny-Rules has exceeded the configured threshold during the current monitoring period. Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearFWDenyRule notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.374 |
starThreshClearFWDenyRuleThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.375 |
starThreshFWNoRuleThe cumulative number of FW No Rules has exceeded the configured threshold during the current monitoring period. Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearFWNoRule notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.376 |
starThreshClearFWNoRuleThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.377 |
starThreshPHSGWSessTimeoutThe PHSGW session timeout has gone above the configured threshold Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshPHSGWSessTimeout notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.378 |
starThreshClearPHSGWSessTimeoutThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.379 |
starThreshPHSGWSessSetupTimeoutThe PHSGW session setup timeout has gone above the configured threshold Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshPHSGWSessSetupTimeout notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.380 |
starThreshClearPHSGWSessSetupTimeoutThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.381 |
starThreshPHSGWAuthFailThe number of PHSGW authentication failures has exceeded the configured threshold during the current monitoring period. Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshPHSGWAuthFail notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.382 |
starThreshClearPHSGWAuthFailThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.383 |
starThreshPHSGWMaxEAPRetryThe number of PHSGW Maximum EAP Retry has exceeded the configured threshold during the current monitoring period. Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshPHSGWMaxEAPRetry notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.384 |
starThreshClearPHSGWMaxEAPRetryThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.385 |
starThreshPHSGWNWEntryDenialThe number of PHSGW Network Entry Denial has exceeded the configured threshold during the current monitoring period. Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshPHSGWNWEntryDenial notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.386 |
starThreshClearPHSGWNWEntryDenialThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.387 |
starThreshPHSGWHandoffDenialThe number of PHSGW Handoff Denial has exceeded the configured threshold during the current monitoring period. Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshPHSGWHandoffDenial notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.388 |
starThreshClearPHSGWHandoffDenialThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.389 |
starThreshASNGWSessionsThe total number of ASNGW sessions is above the configured threshold value. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.390 |
starThreshClearASNGWSessionsThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.391 |
starThreshPerServiceASNGWSessionsThe total number of ASNGW sessions in a service is above the configured threshold value. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.392 |
starThreshClearPerServiceASNGWSessionsThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.393 |
starThreshPHSPCSessSetupTimeoutThe PHSPC session setup timeout has gone above the configured threshold Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshPHSPCSessSetupTimeout notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.394 |
starThreshClearPHSPCSessSetupTimeoutThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.395 |
starThreshPHSPCSleepModeTimeoutThe PHSPC idle mode timeout has gone above the configured threshold Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshPHSPCSleepModeTimeout notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.396 |
starThreshClearPHSPCSleepModeTimeoutThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.397 |
starThreshPHSPCSmEntryDenialThe number of PHSPC sm entry denial has exceeded the configured threshold during the current monitoring period. Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshPHSPCSmEntryDenial notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.398 |
starThreshClearPHSPCSmEntryDenialThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.399 |
starThreshSGWSessionsThe total number of SGW sessions is above the configured threshold value. Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearSGWSessions notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.408 |
starThreshClearSGWSessionsThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.409 |
starThreshPGWSessionsThe total number of PGW sessions is above the configured threshold value. Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearSGWSessions notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.410 |
starThreshClearPGWSessionsThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.411 |
starThreshLMASessionsThe total number of LMA sessions is above the configured threshold value. Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearLMASessions notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.412 |
starThreshClearLMASessionsThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.413 |
starThreshMAGSessionsThe total number of MAG sessions is above the configured threshold value. Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearMAGSessions notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.414 |
starThreshClearMAGSessionsThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.415 |
starThreshFNGCurrSessThe chassis-wide count of current FNG sessions has gone above the configured threshold Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearFNGCurrSess notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.416 |
starThreshClearFNGCurrSessThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.417 |
starThreshFNGCurrActSessThe chassis-wide count of current FNG active sessions has gone above the configured threshold Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearFNGCurrActiveSess notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.418 |
starThreshClearFNGCurrActSessThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.419 |
starThreshPHSGWEAPOLAuthFailureThe number of PHSGW EAPOL Auth Failure has exceeded the configured threshold during the current monitoring period. Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshPHSGWEAPOLAuthFailure notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.420 |
starThreshClearPHSGWEAPOLAuthFailureThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.421 |
starThreshPHSGWMaxEAPOLRetryThe number of PHSGW max EAPOL retry has exceeded the configured threshold during the current monitoring period. Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshPHSGWMaxEAPOLRetry notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.422 |
starThreshClearPHSGWMaxEAPOLRetryThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.423 |
starThreshHSGWSessionsThe total number of HSGW sessions is above the configured threshold value. Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearHSGWSessions notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.424 |
starThreshClearHSGWSessionsThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.425 |
starThreshPDGCurrSessThe chassis-wide count of current PDG sessions has gone above the configured threshold Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearPDGCurrSess notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.426 |
starThreshClearPDGCurrSessThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.427 |
starThreshPDGCurrActSessThe chassis-wide count of current PDG active sessions has gone above the configured threshold Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearPDGCurrActiveSess notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.428 |
starThreshClearPDGCurrActSessThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.429 |
starThreshNATPortChunksThe NAT port chunks utilization of NAT pool is above the configured threshold value. Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearNATPortChunks notification will be generated when the measured value exceeds the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.430 |
starThreshClearNATPortChunksThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.431 |
starThreshGPRSSessionsThe total number of GPRS sessions is above the configured threshold value. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.432 |
starThreshClearGPRSSessionsThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.433 |
starThreshPerServiceGPRSSessionsThe total number of GPRS sessions in a service is above the configured threshold value. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.434 |
starThreshClearPerServiceGPRSSessionsThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.435 |
starThreshGPRSPdpSessionsThe total number of GPRS PDP sessions is above the configured threshold value. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.436 |
starThreshClearGPRSPdpSessionsThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.437 |
starThreshPerServiceGPRSPdpSessionsThe total number of GPRS PDP sessions in a service is above the configured threshold value. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.438 |
starThreshClearPerServiceGPRSPdpSessionsThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.439 |
starThreshMMESessionsThe total number of subscribers is above the configured threshold value. Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearMMESessions notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.440 |
starThreshClearMMESessionsThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.441 |
starThreshMMEAuthFailThe total number of subscribers is above the configured threshold value. Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearMMEAuthFail notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.442 |
starThreshClearMMEAuthFailThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.443 |
starThreshMMEAttachFailThe total number of subscribers is above the configured threshold value. Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearMMEAttachFail notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.444 |
starThreshClearMMEAttachFailThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.445 |
starThreshCSCFSvcRegRcvdRateThe Per-Service CSCF Registration Per Interval count has gone above the configured threshold Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearCSCFSvcRegRcvdRate notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.446 |
starThreshClearCSCFSvcRegRcvdRateThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.447 |
starThreshCSCFSvcTotalActiveRegThe Per-Service CSCF Total Active Registrations count has gone above the configured threshold Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearCSCFSvcTotalActiveReg notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.448 |
starThreshClearCSCFSvcTotalActiveRegThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.449 |
starThreshCSCFSvcInviteRcvdRateThe Per-Service CSCF Calls Per Interval count has gone above the configured threshold Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearCSCFSvcInviteRcvdRate notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.450 |
starThreshClearCSCFSvcInviteRcvdRateThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.451 |
starThreshCSCFSvcTotalActiveCallsThe Per-Service CSCF Total Active Calls count has gone above the configured threshold Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearCSCFSvcTotalActiveCalls notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.452 |
starThreshClearCSCFSvcTotalActiveCallsThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.453 |
starThreshCSCFSvcTotalCallFailureThe Per-Service CSCF Total Call Failure count has gone above the configured threshold Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearCSCFSvcTotalCallFailure notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.454 |
starThreshClearCSCFSvcTotalCallFailureThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.455 |
starThreshCSCFSvcErrorNoResourceThe Per-Service CSCF No resource failure count has gone above the configured threshold Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearCSCFSvcErrorNoResource notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.456 |
starThreshClearCSCFSvcErrorNoResourceThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.457 |
starThreshCSCFSvcErrorTcpThe Per-Service CSCF Tcp failure count has gone above the configured threshold Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearCSCFSvcErrorTcp notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.458 |
starThreshClearCSCFSvcErrorTcpThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.459 |
starThreshCSCFSvcErrorPresenceThe Per-Service CSCF Presence failure count has gone above the configured threshold Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearCSCFSvcErrorPresence notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.460 |
starThreshClearCSCFSvcErrorPresenceThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.461 |
starThreshCSCFSvcErrorRegAuthThe Per-Service CSCF Reg-Auth failure count has gone above the configured threshold Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearCSCFSvcErrorRegAuth notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.462 |
starThreshClearCSCFSvcErrorRegAuthThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.463 |
starThreshBGPRoutesThe Total number of BGP routes is above the configured threshold value. Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearBGPRoutes notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.464 |
starThreshClearBGPRoutesThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.465 |
starThreshPCCPolicySessionsThe total number of PCC-Policy sessions is above the configured threshold value. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.466 |
starThreshClearPCCPolicySessionsThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.467 |
starThreshPerServicePCCPolicySessionsThe total number of PCC-Policy sessions in a service is above the configured threshold value. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.468 |
starThreshClearPerServicePCCPolicySessionsThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.469 |
starThreshPCCQuotaSessionsThe total number of PCC-Quota sessions is above the configured threshold value. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.470 |
starThreshClearPCCQuotaSessionsThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.471 |
starThreshPerServicePCCQuotaSessionsThe total number of PCC-Quota sessions in a service is above the configured threshold value. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.472 |
starThreshClearPerServicePCCQuotaSessionsThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.473 |
starThreshPCCAFSessionsThe total number of PCC-AF sessions is above the configured threshold value. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.474 |
starThreshClearPCCAFSessionsThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.475 |
starThreshPerServicePCCAFSessionsThe total number of PCC-AF sessions in a service is above the configured threshold value. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.476 |
starThreshClearPerServicePCCAFSessionsThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.477 |
starThreshNPUUtilizationThe overall NPU utilization for the identified processor has exceeded for configured threshold value for the current monitoring period. Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearNPUUtilization notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.478 |
starThreshClearNPUUtilizationThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.479 |
starThreshDnsLookupFailureThe Total number of DNS lookup failures is above the configured threshold value. Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearDnsLookupFailure notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.480 |
starThreshClearDnsLookupFailureThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.481 |
starThreshDiameterRetryRateThe percentage of Diameter requests which has to be retried has exceeded the configured threshold during the current monitoring period. Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearDiameterRetryRate notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.482 |
starThreshClearDiameterRetryRateThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.483 |
starThreshHNBGWHnbSessThe chassis-wide count of current HNBGW HNB sessions has gone above the configured threshold NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.484 |
starThreshClearHNBGWHnbSessThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.485 |
starThreshHNBGWUeSessThe chassis-wide count of current HNBGW UE sessions has gone above the configured threshold NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.486 |
starThreshClearHNBGWUeSessThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.487 |
starThreshHNBGWIuSessThe chassis-wide count of current HNBGW IU sessions has gone above the configured threshold NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.488 |
starThreshClearHNBGWIuSessThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.489 |
starThreshPerServicePDGSessionsThe total number of PDG sessions in a service is above the configured threshold value. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.491 |
starThreshClearPerServicePDGSessionsThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.492 |
starThreshSystemCapacityThe System resource capacity has exceeded the configured threshold NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.493 |
starThreshClearSystemCapacityThe threshold condition is now clear for system capacity. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.494 |
starThreshTpoRtoTimeoutThe total number of TPO RTO timeouts is above the configured threshold value. Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearTpoRtoTimeout notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.495 |
starThreshClearTpoRtoTimeoutThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.496 |
starThreshTpoDnsFailureThe total number of TPO DNS query failure is above the configured threshold value. Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearTpoDnsFailure notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.497 |
starThreshClearTpoDnsFailureThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.498 |
starThreshTpoLowCompressionGainThe total number of TPO low compression gain is above the configured threshold value. Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearTpoLowCompressionGain notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.499 |
starThreshClearTpoLowCompressionGainThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.500 |
starThreshEPDGCurrSessThe chassis-wide count of current EPDG sessions has gone above the configured threshold Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearEPDGCurrSess notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.501 |
starThreshClearEPDGCurrSessThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.502 |
starThreshCardTemperatureNearPowerOffLimitOn the certain card, the distance between the poweroff/reset point and current temperature on card is smaller than the setted threshold, during the current monitoring period. Probable Cause: This is a user configurable threshold. Possible reason to cause this alarm: 1) External temperature is too high; 2) One or more fan failures; 3) Blockages the prevent fan air inflow/outflow. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearCardTemperaturePowerOffLimit notification will be generated when the measured temperature falls, making the distance between the poweroff/reset point and current temperature larger than the setted threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.503 |
starThreshClearCardTemperaturePowerOffLimitOn the certain card, the distance between the poweroff/reset point and current temperature on card is larger than the setted clear point. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.504 |
starThreshAAAAcctArchiveQueue1The Per-Sessmgr Archive queue usage is above the configured threshold percentage Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearAAAAcctArchiveQueue-1 notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.505 |
starThreshClearAAAAcctArchiveQueue1The threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.506 |
starThreshAAAAcctArchiveQueue2The Sessmgr Archive queue usage is above the configured threshold percentage Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearAAAAcctArchiveQueue-2 notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.507 |
starThreshClearAAAAcctArchiveQueue2The threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.508 |
starThreshAAAAcctArchiveQueue3The Sessmgr Archive queue usage is above the configured threshold percentage Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearAAAAcctArchiveQueue-3 notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.509 |
starThreshClearAAAAcctArchiveQueue3The threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.510 |
starThreshDnsLookupSrvFailureThe Total number of DNS SRV lookup failures is above the configured threshold value. Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearSrvLookupSrvFailure notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.511 |
starThreshClearDnsLookupSrvFailureThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.512 |
starThreshHENBGWHenbSessionsThe total number of HENBGW Henb sessions is above the configured threshold value. Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearHENBGWHenbSessions notification will be generated when the measure value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.513 |
starThreshClearHENBGWHenbSessionsThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.514 |
starThreshHENBGWUeSessionsThe total number of HENBGW UE sessions is above the configured threshold value. Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearHENBGWUeSessions notification will be generated when the measure value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.515 |
starThreshClearHENBGWUeSessionsThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.516 |
starThreshHENBGWPagingMessagesThe total number of HENBGW Paging Messages received is above the configured threshold value. Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshClearHENBGWPagingMessages notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.517 |
starThreshClearHENBGWPagingMessagesThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.518 |
starThreshPerServiceSAMOGSessionsThe total number of SAMOG sessions in a service is above the configured threshold value. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.519 |
starThreshClearPerServiceSAMOGSessionsThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.520 |
starThreshNATPktDropThe NAT packet drops from a NAT pool is above the configured threshold value. Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshNATPktDrop notification will be generated when the measured value exceeds the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.521 |
starThreshClearNATPktDropThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.522 |
starThreshFabricEGQDiscardsThe number of EGQDiscards observed during configured threshold and interval exceeded. Probable Cause: Possible FAP or FE issue. Collect more data by running .show fabric health. command. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.523 |
starThreshClearFabricEGQDiscardsThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.524 |
starGILANServiceStartA GILAN Service has started Action to be Taken: No action required NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.525 |
starGILANServiceStopA GILAN Service has stopped Probable Cause: This is typically caused by operator invention. In unusual cases it can be caused by the loss of resources (PACs/PSCs) to support the running configuration. Action to be Taken: If the GILAN service shutdown was not planned, examine the admin logs for an indication of the failure. Check the crash logs for an indication of a software failure. Clear Condition: Verify that the GILAN service is operational. Condition Clear Alarm: A starGILANServiceStart notification will be generated when the service is restarted NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.526 |
starThreshEPDGIKEV2SetupAttemptsThe number of IKEv2 Setup attepmts requests seen for this ePDG service has exceeded the configured threshold. Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshEPDGIKEV2SetupAttempts notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.527 |
starThreshClearEPDGIKEV2SetupAttemptsThe threshold condition is now clear NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.528 |
starThreshEPDGIKEV2AuthFailuresThe number of IKEv2 Authentication Failures seen for this ePDG service has exceeded the configured threshold. Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshEPDGIKEV2AuthFailures notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.529 |
starThreshClearEPDGIKEV2AuthFailuresThe threshold condition is now clear NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.530 |
starThreshEPDGIKEV2SetupSuccessThe number of IKEv2 Setup Success seen for this ePDG service has exceeded the configured threshold. Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshEPDGIKEV2SetupSuccess notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.531 |
starThreshClearEPDGIKEV2SetupSuccessThe threshold condition is now clear NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.532 |
starThreshEPDGIKEV2SetupFailureThe number of IKEv2 Setup Failure seen for this ePDG service has exceeded the configured threshold. Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshEPDGIKEV2SetupFailure notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.533 |
starThreshClearEPDGIKEV2SetupFailureThe threshold condition is now clear NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.534 |
starThreshEPDGIKEV2SetupFailureRateThe rate of IKEv2 Setup failures (as a percentage of total requests) seen for this ePDG service has exceeded the configured threshold. Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model, a starThreshEPDGIKEV2SetupFailureRate notification will be generated when the measured value falls below the threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.535 |
starThreshClearEPDGIKEV2SetupFailureRateThe threshold condition is now clear NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.536 |
starOSPFNeighborDownAn OSPF neighbor is down. Condition Clear Alarm: A starOSPFNeighborFull notification will be generated when the neighbor is restored. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1001 |
starOSPFNeighborFullAn OSPF neighbor is full. A starOSPFNeighborFull notification is only sent for neighbors which had previous been declared down via a starOSPFNeighborDown notification. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1002 |
starM3UAPSDownThe M3UA Peer Server is unavailable. Possibe reason: All related Peer Server Processes(PSPs) are in the ASP-DOWN state for this Peer Server. Condition Clear Alarm: A starM3UAPSActive notification will be generated when the Peer Server becomes reachable as at least one PSP is in ASP-ACTIVE state NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1004 |
starM3UAPSActivePeer Server is available and application traffic is active.This state implies that at least one PSP is in the ASP-ACTIVE state. starM3UAPSActive is only generated for Application Services which were previously declared down via a starM3UAPSDown notification NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1005 |
starM3UAPSPDownAn ASP Down message received from the remote M3UA peer indicates the adaptation layer at the remote M3UA peer is NOT ready to receive DATA, SSNM, RKM or ASPTM messages Possibe reason: 1. SCTP association is down or 2. Remote peer server process is down Condition Clear Alarm: A starM3UAPSPUp notification will be generated when the reemote ASP becomes available NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1006 |
starM3UAPSPUpAn ASP Up message received from the remote M3UA peer indicates that that the adaptation layer at the remote peer is ready to receive any ASPSM/ASPTM messages for all Routing Keys that the ASP is configured to serve starM3UAPSPUp is generated only when previous starM3UAPSPDown was generated NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1007 |
starSCCPSspRcvdSubsystem prohibitted received from a peer. The receiving node needs to update the translation tables so that traffic could be re routed to a backup system if available Condition Clear: A starSCCPSspClear notification will be generated when this condition is cleared. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1008 |
starSCCPSspClearSusbsystem available received from a peer. This indicates a previously prohibited node is now available. Receiving node needs to update its translation tables A starSCCPSspClear notification is only generated for peers which had previously generated a starSCCPSspRcvd noficiation NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1009 |
starSGSNRNCResetSGSN has received an Radio Network Controller(RNC) reset event.SGSN will clean up all the Iu connections with the RNC. This event is not generated when we get RNC Reset the firt time system boots up. This trap is generated only on subsequent reset events NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1010 |
starSGSNHLRResetHome Location register(HLR) reset event received. SGSN will mark all the subscribers served by this HLR so that the subscription record can be fetched again on subsequent user activity NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1011 |
starSGSNGtpcPathFailureNo response received from peer GPRS Serving Node(GSN) as several messages have timed out. The control path towards the peer GSN is down. Check that the peer GGSN or SGSN is UP Possibe reason: Remote GSN is down Condition Clear Alarm: A starSGSNGtpcPathFailureClear notification will be generated when the control path towards the peer GSN is available NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1012 |
starSGSNGtpcPathFailureClearThe path to the peer GSN which was down is now available A starSGSNGtpcPathFailureClear notification is only generated for GSNs which had previously generated a starSGSNGtpcPathFailure notification NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1013 |
starSGSNGtpuPathFailureNo response received for ECHO request sent from SGSN. Data path failure detected towards peer GPRS Serving Node(GSN) or Radio Network Controller(RNC). Check if the peer RNC or GSN is up Possibe reason: Remote GSN is down Condition Clear Alarm: A starSGSNGtpuPathFailureClear notification will be generated when the data path to the remote GSN becomes available NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1014 |
starSGSNGtpuPathFailureClearThe data path toward peer GSN or RNC is now available A starSGSNGtpuPathFailureClear notification is only sent for peers which had previously generated a starSGSNGtpuPathFailure notification. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1015 |
starMTP3LinkOutOfServiceMessage Transfer Part(MTP3) link out of service. Possibe reason: 1. Physical link is down or 2. Layer 2 (SSCOP/MTP2) is down 3. Operator action - link deactivated. Condition Clear Alarm: A starMTP3LinkInService notification will be generated when the link comes back in service NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1016 |
starMTP3LinkInServiceMessage Transfer Part(MTP3) link is in service. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1017 |
starMTP3LinkSetUnAvailableMessage Transfer Part(MTP3) linkset Unavailable Possibe reason: 1. All the links in the linkset is down. 2. Operator action - linkset deactivated. Condition Clear Alarm: A starMTP3LinkSetAvailable notification will be generated when the previously down linkset is available NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1018 |
starMTP3LinkSetAvailableMessage Transfer Part(MTP3) linkset Available. A starMTP3LinkSetAvailable notification is only generated for linksets which previously generated a starMTP3LinkSetUnavailable notification NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1019 |
starSCTPAssociationFailM3UA Stream Control Transmission Protocol(SCTP) association establishment failure. Possibe reason: The peer is down. or network reachability to the remote server is down or the end point configuration is not correct at our end. Condition Clear Alarm: A starSCTPAssociationEstablished notification will be generated when the previously failed association is successfully established again NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1020 |
starSCTPAssociationEstablishedM3UA Stream Control Transmission Protocol (SCTP) association establishment ok. Previoulsy there was a failure to establish the same association A starM3UASCTPAssociationEstabalish notification is only generated for peers which previously generated a starM3UASCRPAssociationFail notification NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1021 |
starSCTPPathDownStream Control Transmission Protoco(SCTP) path down. Possible reason: The peer is down. or network reachability to the remote server is down or the end point configuration is not correct at our end. Condition Clear Alarm: A starSCTPPathUp notification will be generated when the previously down path becomes usable NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1022 |
starSCTPPathUpStream Control Transmission Protocol(SCTP) path up. A starSCTPPathUp notification is only generated for peers which had previously generated a starSCTPPathDown notification NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1023 |
starPortDownPort status is Down. This notification is only generated for physical port. Action to be Taken: No action required. The cause for the port down should be investigated. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1024 |
starPortUpPort status is up. This notification is only generated for physical port and a 'starPortDown' notification was previously generated. Action to be Taken: No action required NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1025 |
starBSReachableThe Base Station is reachable now. This can be result of Base Station Startup, etc. Action to be Taken: No Action Required NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1026 |
starBSUnreachableA Base Station that the IMG communicates with is no longer reachable. Probable Cause: The Base Station has failed or is otherwise unavailable, or a network connectivity problem makes it unreachable. Action to be Taken: If the Base Station outage was unplanned, restart/reset the Base Station; verify network connectivity. Condition Clear Alarm: This condition is cleared by a starBSReachable notification. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1027 |
starSystemStartupThe system has completed a reboot/startup NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1028 |
starMTP3PCUnavailableMessage Transfer Part(MTP3) Route to the Point code becomes unavailable. Possibe reason: 1. Associated linkset (all links within this linkset) becomes unavailable, hence route to the point code also becomes unvailable throught this linkset. 2. Remote peer is down Condition Clear Alarm: A starMTP3PCAvailable notification will be generated when the reemore peer identified by the point code becomes reachable NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1029 |
starMTP3PCAvailableMessage Transfer Part(MTP3) Route to the Point code becomes available. Possible reason: 1. Associated linkset (one of the links in the linkset) becomes available. 2. Remote peer is up starMTP3PCAvailable is generated only when a previous starMTP3PCUnavailable is generated. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1030 |
starSS7PCUnavailableSS7 Point code is unavailable, all the routes to this point code is unavailable. Possibe reason: 1. All the routes (both M3UA and MTP3) to this point code becomes unavailable. Condition Clear Alarm: A starSS7PCAvailable notification will be generated when the reemore peer identified by the point code becomes reachable NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1031 |
starSS7PCAvailableSS7 Point code is available, one of the routes to this point code is available. Possible reason: 1. One of the routes (either M3UA or MTP3) to this point code becomes available. starSS7PCAvailable is generated only when a previous starSS7PCUnavailable is generated. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1032 |
starASNPCServiceStartA WiMAX ASN Paging Controller (ASNPC) Service has started Action to be Taken: No action required NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1033 |
starASNPCServiceStopA WiMAX ASN Paging Controller (ASNPC) Service has stopped. Probable Cause: This is typically caused by operator invention. In unusual cases it can be caused by the loss of resources (PACs/PSCs) to support the running configuration. Action to be Taken: If the ASNPC service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured PACs/PSCs are present and running in the system. Check the crash logs for an indication of a software failure. Clear Condition: Verify that the ASNPC service is operational. Condition Clear Alarm: A starASNPCServiceStart notification will be generated when the service is restarted NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1034 |
starDiameterCapabilitiesExchangeFailureCapability negotiations has failed and connections are down. Problem Cause: Due to an error in Capability Exchange Answer received from the peer the connections have been torn down. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1035 |
starDiameterCapabilitiesExchangeSuccessA diameter server is up. This notification is only generated for servers which have previously been declared unreachable. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1036 |
starSRPConnDownThe connection to the standby SRP system is down. While this connection is down, the active system is operating without a standby and would be unable to perform an SRP switchover. Action to be Taken: Verify that the standby system is operational; verify the network between systems is operational. Clear Condition: This condition is cleared when the active system is reconnected to the standby SRP system. Condition Clear Alarm: A starSRPConnUp notification is generated when this condition is clear NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1037 |
starSRPConnUpThe connection to the standby SRP system is now up. This notification is only generated if a starSRPConnDown had previously been generated. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1038 |
starDiameterIpv6PeerDownA diameter peer is down. This diameter peer is reached using an IPv6 address. For IPv4-connected diameter peers, a starDiameterPeerDown notification would be generated. Problem Cause: The diameter peer has failed, or a network connectivity prevents reaching the peer. Condition Clear Alarm: A starDiameterPeerUp notification will be generated when the peer is up NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1039 |
starDiameterIpv6PeerUpA diameter peer is up. This diameter peer is reached using an IPv6 address. This notification is only generated for peers which have previously been declared down. For IPv4-connected diameter peers, a starDiameterPeerUp notification would be generated. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1040 |
starIPMSServerUnreachableAn IPMS server is unreachable. Probable Cause: The IPMS server has failed, or a network connectivity issue prevents reaching the server. Condition Clear Alarm: A starIPMSServerReachable notification will be generated when the server becomes reachable. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1041 |
starIPMSServerReachableAn IPMS server is reachable. A starIPMSServerReachable notification is only generated for servers which had previously been declared unreachable. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1042 |
starCertShortLifetimeA certificate is approaching its expiration. The certificate is still valid, but should be updated with a new certificate. Action to be Taken: A new certificate should be created and configured on the system. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1043 |
starCertExpiredA certificate has expired. The certificate is no longer valid. Action to be Taken: A new certificate should be created and configured on the system. Condition Clear Alarm: A starCertValid notification is sent when a new, valid, certificate is configured. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1044 |
starCertValidA valid certificate has been configured. This notification is only generated if a starCertExpired had been previously generated. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1045 |
starFTPPushFailAn FTP push operation has failed for the specified file to the specified server. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1046 |
starFTPServSwitchAn FTP server switchover has been performed; that is, the system has determined that an external FTP server is unreachable, and is not using an alternate FTP server NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1047 |
starSDHSectionDownThe SDH interface on this port is down. The starSDHOperState identifies the specific issue. Probable Cause: Action to be Taken: Condition Clear Alarm: This condition is cleared by a starSDHSectionUp notification, NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1048 |
starSDHSectionUpThe SDH interface on this port is now up. A starSDHSectionUp notification is only generated if a starSDHSectionDown was previously generated for this port. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1049 |
starSDHPathHopDownThe identified SDH Path is down. The value of starSDHPathOperState identifies the specific failure bits. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1050 |
starSDHPathHopUpThe identified SDH Path is up. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1051 |
starSDHLopDownThe identified E1 Tributary on this port is down. The value of starE1TribOperStateLOP identifies the specific failure bits. Probable Cause: Action to be Taken: Condition Clear Alarm: This condition is cleared by a starSDHLopDown notification, NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1052 |
starSDHLopUpThe identified E1 Tributary on this port is now up. A starE1TributaryUp notification is only generated if a starSDHLopDown was previously generated for this E1 tributary. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1053 |
starSS7PCCongestedSS7 Point code is congested, all the routes to this point-code is congested. Possible reason: 1. All the routes (both M3UA and MTP3) to this Point Code have become congested. Condition Clear Alarm: A starSS7PCCongestionCleared notification will be generated when the congestion gets cleared for any one of the routes NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1056 |
starSS7PCCongestionClearedSS7 Point code Congestion gets cleared, one of the routes to this point-code is cleared from congestion. Possible reason: 1. One of the routes (either M3UA or MTP3) to this Point Code has resumed from congestion. starSS7PCCongestionCleared is generated only when a previous starSS7PCCongested is generated. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1057 |
starPHSGWServiceStartA PHS-GW Service has started Action to be Taken: No action required NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1058 |
starPHSGWServiceStopA PHS-GW Service has stopped. Probable Cause: This is typically caused by operator invention. In rare cases it can be caused by the loss of resources (PACs/PSCs) to support the running configuration. Action to be Taken: If the PHS-GW service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured PACs are present and running in the system. Check the crash logs for an indication of a software failure. Clear Condition: Verify that the PHS-GW service is operational. Condition Clear Alarm: A starPHSGWServiceStart notification will be generated when the service is restarted NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1059 |
starGPRSServiceStartA GPRS Service has started Action to be Taken: No action required NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1060 |
starGPRSServiceStopA GPRS Service has stopped. Probable Cause: In unusual cases it can be caused by the loss of resources (PACs/PSCs) to support the running configuration.This can also happen due to some misconfiguration of the service parameters. Action to be Taken: If the GPRS service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured PACs/PSCs are present and running in the system. Check the crash logs for an indication of a software failure. Clear Condition: Verify that the GPRS service is operational. Condition Clear Alarm: A starGPRSServiceStart notification will be generated when the service is restarted NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1061 |
starGPRSNseDownNetwork Service Entity (NSE) is down. Possible reason: The Last NSVC(Network Service virtual circuit in the NSE is down. Condition Clear Alarm: A starGPRSNseUp will be generated when at least one NSVC in the NSE comes up NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1062 |
starGPRSNseUpNetwork Service Entity (NSE) is up. Possible reason: The First NSVC(Network Service virtual circuit in the NSE is up. starGPRSNseUp is generated only when a previous starGPRSNseDown has been generated NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1063 |
starGPRSNsvcDownNetwork Service Entity Virtual Circuit (NSVC) is down. Possible reasons: 1) NS_ALIVE heartbeat messages sent from the Serving GPRS support Node (SGSN) were not acknowledged by the Base Station Subsystem(BSS) for a configured number of maximum retries. This trap is generated only when an NSVC goes down due to reasons other than physical port failure. A separate trap is generated for a physical port failure event. Condition Clear Alarm: A starGPRSNsvcUp will be generated when the NSVC comes up NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1064 |
starGPRSNsvcUpAn Network Service Entity Virtual Circuit (NSVC) comes up An starGPRSNsvcUp trap is generated only when a previous starGPRSNsvcDown was generated NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1065 |
starGPRSBvcDownBase Station Subsystem (BSS) GPRS (General Packet Radio Service) Protocol (BSSGP) Virtual Circuit (BVC) is Down. Possible reason: 1) ALL Network Service Entity Virtual Circuit (NSVC) associated with this BVC are down Condition Clear Alarm: A starGPRSBvcUp will be generated when the BVC is available NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1066 |
starGPRSBvcUpBase Station Subsystem (BSS) GPRS ((General Packet Radio Service) Protocol (BSSGP) Virtual Circuit (BVC) is Up Possible reasons: 1) Atleast one NSVC associated with the BVC becomes available. starGPRSBvcUp is generated only when a previous starGPRSBvcDown has been generated. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1067 |
starSDHE1TribDownThe identified E1 Tributary on this port is down. Probable Cause: Action to be Taken: Condition Clear Alarm: This condition is cleared by a starSDHTugUp notification, NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1068 |
starSDHE1TribUpThe identified E1 Tributary on this port is up. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1069 |
starSDHFractE1LMIDownThe identified fractional E1 Tributary on this port is down. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1070 |
starSDHFractE1LMIUpThe identified fractional E1 Tributary on this port is up. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1071 |
starPHSPCServiceStartA PHS-PC Service has started Action to be Taken: No action required NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1072 |
starPHSPCServiceStopA PHS-PC Service has stopped. Probable Cause: This is typically caused by operator invention. In rare cases it can be caused by the loss of resources (PACs/PSCs) to support the running configuration. Action to be Taken: If the PHS-PC service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured PACs are present and running in the system. Check the crash logs for an indication of a software failure. Clear Condition: Verify that the PHS-PC service is operational. Condition Clear Alarm: A starPHSPCServiceStart notification will be generated when the service is restarted NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1073 |
starM3UAPSPCongestedPeer Server Process (PSP) link is congested, when the congestion queue size rises above the threshold limit. Possible reason: 1. No Stream Control Transmission Protocol (SCTP) Acknowledgement from peer end due to packet loss 2. Acknowledgement with zero window size Condition Clear Alarm: A starM3UAPSPCongestionCleared notification will be generated when the congestion queue size goes below the threshold limit NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1074 |
starM3UAPSPCongestionClearedPeer Server Process (PSP) link Congestion gets cleared, when the congestion queue size goes below the threshold limit. starM3UAPSPCongestionCleared is generated only when a previous starM3UAPSPCongested is generated. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1075 |
starStorageFailedThe specified storage device has failed. This storage device is now out of service and cannot be used to store additional data. This notification is currently only generated for failures on the hard drive attached to the SMC card. Probable Cause: A hardware failure on the device; a hardware failure on the card to which the device is attached. Action to be Taken: Replace the card Condition Clear Alarm: A starCardRemoved notification will be generated when the card is removed from the chassis. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1076 |
starRaidFailedThe specified raid array has failed. The raid array can no longer be used to store data. Probable Cause: Hardware failure(s) on the devices within the raid array; Hardware failure(s) on the card(s) to which the devices are attached; the removal of the cards containing devices in the array; operator action which disabled the raid array. Condition Clear Alarm: a starRaidStarted notification will be generated when the raid array is online. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1077 |
starRaidStartedThe specific raid array has resumed operation. This notification is only generated if a starRaidFailed notification was previously generated for this array. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1078 |
starRaidDegradedThe specified raid array is running in a degraded state. This typically means one of the member devices has failed or become unavailable. The raid array continues to function and can read/store data, but may not be operating in a redundant manner. Probable Cause: Hardware failure(s) on the devices within the raid array; Hardware failure(s) on the card(s) to which the devices are attached; the removal of the cards containing devices in the array; operator action which disabled the raid array. The first variable binding, starStorageName is indicating the raid array name; The second variable binding, starStorageSlot is the disk card number, in which the fail happens; The third varbind, which is also the second starStorageName, is the name of the disk that the fail happens. Condition Clear Alarm: a starRaidRecovered notification will be generated when the raid array is fully recovered. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1079 |
starRaidRecoveredThe specific raid array has been recovered and is running in its normal, redundant state. This notification is only generated if a starRaidDegraded notification was previously generated for this array. As to the variable bindings, please refer to the trap starRaidDegraded. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1080 |
starPGWServiceStartA Packet Data Network Gateway (PGW) Service has started. Action to be Taken: No action required NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1081 |
starPGWServiceStopA Packet Data Network Gateway (PGN) Service has stopped. Probable Cause: This is typically caused by operator intervention. In rare cases it can be caused by the loss of resources (PSCs) to support the running configuration. Action to be Taken: If the PGW service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured PSCs are present and running in the system. Check the crash logs for an indication of a software failure. Clear Condition: Verify that the PGW service is operational. Condition Clear Alarm: A starPGWServiceStart notification will be generated when the service is restarted NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1082 |
starSGWServiceStartA Serving Gateway (SGW) Service has started. Action to be Taken: No action required NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1083 |
starSGWServiceStopA Serving Gateway (SGW) Service has stopped. Probable Cause: This is typically caused by operator intervention. In rare cases it can be caused by the loss of resources (PSCs) to support the running configuration. Action to be Taken: If the SGW service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured PSCs are present and running in the system. Check the crash logs for an indication of a software failure. Clear Condition: Verify that the SGW service is operational. Condition Clear Alarm: A starSGWServiceStart notification will be generated when the service is restarted NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1084 |
starEGTPServiceStartAn Evolved GPRS Tunneling Protocol (EGTP) Service has started. Action to be Taken: No action required NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1085 |
starEGTPServiceStopAn Evolved GPRS Tunneling Protocol (EGTP) Service has stopped. Probable Cause: This is typically caused by operator intervention. In rare cases it can be caused by the loss of resources (PSCs) to support the running configuration. Action to be Taken: If the EGTP service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured PSCs are present and running in the system. Check the crash logs for an indication of a software failure. Clear Condition: Verify that the EGTP service is operational. Condition Clear Alarm: A starEGTPServiceStart notification will be generated when the service is restarted NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1086 |
starLMAServiceStartA Local Mobility Anchor (LMA) Service has started. Action to be Taken: No action required NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1087 |
starLMAServiceStopA Local Mobility Anchor (LMA) Service has stopped. Probable Cause: This is typically caused by operator intervention. In rare cases it can be caused by the loss of resources (PSCs) to support the running configuration. Action to be Taken: If the LMA service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured PSCs are present and running in the system. Check the crash logs for an indication of a software failure. Clear Condition: Verify that the LMA service is operational. Condition Clear Alarm: A starLMAServiceStart notification will be generated when the service is restarted NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1088 |
starMAGServiceStartA Mobile Access Gateway (MAG) Service has started. Action to be Taken: No action required NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1089 |
starMAGServiceStopA MAG Service has stopped. Probable Cause: This is typically caused by operator intervention. In rare cases it can be caused by the loss of resources (PSCs) to support the running configuration. Action to be Taken: If the MAG service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured PSCs are present and running in the system. Check the crash logs for an indication of a software failure. Clear Condition: Verify that the MAG service is operational. Condition Clear Alarm: A starMAGServiceStart notification will be generated when the service is restarted NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1090 |
starMMEServiceStartA Mobility Management Entity (MME) Service has started. Action to be Taken: No action required NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1091 |
starMMEServiceStopA Mobility Management Entity (MME) Service has stopped. Probable Cause: This is typically caused by operator intervention. In rare cases it can be caused by the loss of resources (PSCs) to support the running configuration. Action to be Taken: If the MME service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured PSCs are present and running in the system. Check the crash logs for an indication of a software failure. Clear Condition: Verify that the MME service is operational. Condition Clear Alarm: A starMMEServiceStart notification will be generated when the service is restarted NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1092 |
starHSGWServiceStartA HRPD Serving Gateway (HSGW) Service has started. Action to be Taken: No action required NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1093 |
starHSGWServiceStopA HRPD Serving Gateway (HSGW) Service has stopped. Probable Cause: This is typically caused by operator intervention. In rare cases it can be caused by the loss of resources (PSCs) to support the running configuration. Action to be Taken: If the HSGW service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured PSCs are present and running in the system. Check the crash logs for an indication of a software failure. Clear Condition: Verify that the HSGW service is operational. Condition Clear Alarm: A starHSGWServiceStart notification will be generated when the service is restarted NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1094 |
starCPUBusyClearThe CPU is no longer busy. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1095 |
starCPUMemoryLowClearThe CPU is no longer experiencing a low memory condition. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1096 |
starFNGServiceStartA FNG Service has started Action to be Taken: No action required NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1097 |
starFNGServiceStopA FNG Service has stopped. Probable Cause: This is typically caused by operator invention. In rare cases it can be caused by the loss of resources (PACs) to support the running configuration. Action to be Taken: If the FNG service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured PACs are present and running in the system. Check the crash logs for an indication of a software failure. Clear Condition: Verify that the FNG service is operational. Condition Clear Alarm: A starFNGServiceStart notification will be generated when the service is restarted NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1098 |
starManagerRestartThe identified manager task has been restarted. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1099 |
starConfigurationUpdateThe configuration of the chassis has been changed. This notification is generated based on a periodic polling of the chassis, it is not real-time generated based on individual changes. The configuration change could have been made via CLI sessions, CORBA management operations, or other methods. This notification is not generated by default; it is only generated if the configuration polling mechanism is specifically enabled. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1100 |
starPDGServiceStartA PDG Service has started Action to be Taken: No action required NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1101 |
starPDGServiceStopA PDG Service has stopped. Probable Cause: This is typically caused by operator invention. In rare cases it can be caused by the loss of resources (PACs) to support the running configuration. Action to be Taken: If the PDG service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured PACs are present and running in the system. Check the crash logs for an indication of a software failure. Clear Condition: Verify that the PDG service is operational. Condition Clear Alarm: A starPDGServiceStart notification will be generated when the service is restarted NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1102 |
starDynPkgLoadErrorThe Dynamic rater package error displayed with an error code. Action to be Taken: If no or invalid rater.pkg file is there in the specified directory then Place a rater_f.pkg file in the directory and give an upgrade command or place a valid Rater.pkg file and load the SRDBs by killing them all. Condition Clear Alarm: This condition is cleared by a starDynPkgLoadErrorClear notification NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1103 |
starDynPkgLoadErrorClearThe Dynamic rater package error removed. Action to be Taken: No action required NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1104 |
starDynPkgUpgradeErrorThe Dynamic rater package error displayed with an error code. Action to be Taken: Place a valid rater_f.pkg file in the directory and give an upgrade command. Condition Clear Alarm: This condition is cleared by a starDynPkgUpgradeErrorClear notification NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1105 |
starDynPkgUpgradeErrorClearThe Dynamic Rater package error removed. Action to be Taken: No action required NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1106 |
starCSCFPeerServerUnavailablePeer server is unavailable NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1107 |
starCSCFPeerServerOutofServicePeer server is out-of-service NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1108 |
starCSCFPeerServerInServicePeer server unavailable and/or out of service condition cleared NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1109 |
starServiceLossPTACsClearService Loss condition is no longer valid for PAC/PSC/TACs. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1110 |
starServiceLossLCClearService Loss condition is no longer valid for LC. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1111 |
starEgtpcPathFailureEGTP Control Path Failure. No response received for GTPV2 request sent from MME or SGW or PGW. Possibe reason: Remote peer MME or SGW or PGW is down Condition Clear Alarm: A StarEgtpcPathFailureClear notification will be generated when the control path to the remote peer MME or SGW or PGW becomes available NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1112 |
starEgtpcPathFailureClearEGTP Control Path Failure condition is no longer valid. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1113 |
starCscfSessResourceCongestionA congestion condition has occurred at Session Manager for Cscf Service. Probable Cause: This is the result of an operator-configured congestion threshold being reached for Cscf Service at Session Manager. This can be due to high usage of the resource being monitored which indicates that the IMG is reaching its peak capacity, or could be caused by the incorrect configuration of the congestion thresholds. Actions to be Taken: Verify that the congestion thresholds are correct; if the congested state is seem repeatedly, or for sustained periods of time, additional system capacity may need to be brought online. This system is cleared when the use of the specific resource falls below the configured limit. Condition Clear Alarm: A starCscfSessResourceCongestionClear notification is sent when there are no congestion conditions for cscf service in that Session Manager Instance NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1114 |
starCscfSessResourceCongestionClearA congestion condition has cleared at Session Manager for Cscf service NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1115 |
starOSPFv3NeighborDownAn OSPFv3 neighbor is down. Condition Clear Alarm: A starOSPFv3NeighborFull notification will be generated when the neighbor is restored. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1116 |
starOSPFv3NeighborFullAn OSPFv3 neighbor is full. A starOSPFv3NeighborFull notification is only sent for neighbors which had previous been declared down via a starOSPFv3NeighborDown notification. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1117 |
starServiceLossSPIOClearService Loss condition is no longer valid for SPIO. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1118 |
starEgtpuPathFailureNo response received for GTP-U ECHO requests. Data path failure detected towards peer EPC Node. Check if the peer RNC or GSN is up Possible reason: Remote EPC node is down Condition Clear Alarm: A starEgtpuPathFailureClear notification will be generated when the data path towards the peer node is available NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1119 |
starEgtpuPathFailureClearThe data path to the peer EPC node which was down is now available A starEgtpuPathFailureClear notification is only generated for nodes which had previously generated a starEgtpuPathFailure notification NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1120 |
starStorageServerCDRLossGTPP Storage Server is experiencing CDR Loss greater than the configured threshold value at the GSS. Note that this is an external server, not part of the ST16. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1121 |
starHNBGWServiceStartA Home Node B Gateway (HNB GW) Service has started. Action to be Taken: No action required NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1122 |
starHNBGWServiceStopA Home Node B Gateway (PGN) Service has stopped. Probable Cause: This is typically caused by operator intervention. In rare cases it can be caused by the loss of resources (PSCs) to support the running configuration. Action to be Taken: If the HNB GW service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured PSCs are present and running in the system. Check the crash logs for an indication of a software failure. Clear Condition: Verify that the HNB GW service is operational. Condition Clear Alarm: A starHNBGWServiceStart notification will be generated when the service is restarted NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1123 |
starSystemRebootThe system has rebooted by the operator. If successful, a subsequent starSystemStartup trap is typically generated. Action to be Taken: No action required. If the reboot was not scheduled the admin logs can be examined to determine who invoked the reboot operation. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1124 |
starLicenseAboutToExpireA license is about to expire. Action to be Taken: A new license should be created and configured on the system before the grace period is over. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1125 |
starLicenseExpiredA license is in the grace period and should be updated with a new license. Action to be Taken: A new license should be created and configured on the system. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1126 |
starPCCPolicyServiceStartA PCC-Policy Service has started Action to be Taken: No action required NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1127 |
starPCCPolicyServiceStopA PCC-Policy Service has stopped. Probable Cause: This is typically caused by operator invention. In rare cases it can be caused by the loss of resources (PACs/PSCs) to support the running configuration. Action to be Taken: If the PCC-Policy service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured PACs/PSCs are present and running in the system. Check the crash logs for an indication of a software failure. Clear Condition: Verify that the PCC-Policy service is operational. Condition Clear Alarm: A starPCCPolicyServiceStart notification will be generated when the service is restarted NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1128 |
starPCCQuotaServiceStartA PCC-Quota Service has started Action to be Taken: No action required NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1129 |
starPCCQuotaServiceStopA PCC-Quota Service has stopped. Probable Cause: This is typically caused by operator invention. In rare cases it can be caused by the loss of resources (PACs/PSCs) to support the running configuration. Action to be Taken: If the PCC-Quota service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured PACs/PSCs are present and running in the system. Check the crash logs for an indication of a software failure. Clear Condition: Verify that the PCC-Quota service is operational. Condition Clear Alarm: A starPCCQuotaServiceStart notification will be generated when the service is restarted NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1130 |
starPCCAFServiceStartA PCC-AF Service has started Action to be Taken: No action required NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1131 |
starPCCAFServiceStopA PCC-AF Service has stopped. Probable Cause: This is typically caused by operator invention. In rare cases it can be caused by the loss of resources (PACs/PSCs) to support the running configuration. Action to be Taken: If the PCC-AF service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured PACs/PSCs are present and running in the system. Check the crash logs for an indication of a software failure. Clear Condition: Verify that the PCC-AF service is operational. Condition Clear Alarm: A starPCCAFServiceStart notification will be generated when the service is restarted NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1132 |
starSPRServerUnreachableThe Subscriber Profile Repository (SPR) server cannot be reached. Probable Cause: The SPR server is down, or there is a network issue preventing communication with the SPR server. Actions to be Taken: Restore the SPR server to an operational status; Verify that the SPR server is reachable by performing a 'ping' operation from the CLI in the appropriate context. Check the admin logs for notification of communication problems. Clear Condition: Verify that communication to the SPR authentication server has been restored. Condition Clear Alarm: When this condition clears a starSPRServerReachable notification will be generated. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1133 |
starSPRServerReachableThe Subscriber Profile Repository (SPR) server is now reachable. This can be the result of a system startup, the configuration of a new server, or a previously unreachable server becoming reachable. Action to be Taken: No Action Required. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1134 |
starGSServiceStartA GS Service has started Action to be Taken: No action required NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1135 |
starGSServiceStopA GS Service has stopped. Probable Cause: This is typically caused by operator invention. In unusual cases it can be caused by the loss of resources (PACs/PSCs) to support the running configuration. Action to be Taken: If the GS service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured PACs/PSCs are present and running in the system. Check the crash logs for an indication of a software failure. Clear Condition: Verify that the GS service is operational. Condition Clear Alarm: A starGSServiceStart notification will be generated when the service is restarted NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1136 |
starMAPServiceStartA MAP Service has started Action to be Taken: No action required NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1137 |
starMAPServiceStopA MAP Service has stopped. Probable Cause: This is typically caused by operator invention. In unusual cases it can be caused by the loss of resources (PACs/PSCs) to support the running configuration. Action to be Taken: If the MAP service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured PACs/PSCs are present and running in the system. Check the crash logs for an indication of a software failure. Clear Condition: Verify that the MAP service is operational. Condition Clear Alarm: A starMAPServiceStart notification will be generated when the service is restarted NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1138 |
starIUPSServiceStartAn IUPS Service has started Action to be Taken: No action required NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1139 |
starIUPSServiceStopAn IUPS Service has stopped. Probable Cause: This is typically caused by operator invention. In unusual cases it can be caused by the loss of resources (PACs/PSCs) to support the running configuration. Action to be Taken: If the IUPS service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured PACs/PSCs are present and running in the system. Check the crash logs for an indication of a software failure. Clear Condition: Verify that the IUPS service is operational. Condition Clear Alarm: A starIUPSServiceStart notification will be generated when the service is restarted NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1140 |
starSGTPServiceStartA SGTP Service has started Action to be Taken: No action required NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1141 |
starSGTPServiceStopA SGTP Service has stopped. Probable Cause: This is typically caused by operator invention. In unusual cases it can be caused by the loss of resources (PACs/PSCs) to support the running configuration. Action to be Taken: If the SGTP service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured PACs/PSCs are present and running in the system. Check the crash logs for an indication of a software failure. Clear Condition: Verify that the SGTP service is operational. Condition Clear Alarm: A starSGTPServiceStart notification will be generated when the service is restarted NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1142 |
starEPDGServiceStartA EPDG Service has started Action to be Taken: No action required NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1143 |
starEPDGServiceStopA EPDG Service has stopped. Probable Cause: This is typically caused by operator invention. In unusual cases it can be caused by the loss of resources (PACs/PSCs) to support the running configuration. Action to be Taken: If the EPDG service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured PACs/PSCs are present and running in the system. Check the crash logs for an indication of a software failure. Clear Condition: Verify that the EPDG service is operational. Condition Clear Alarm: A starEPDGServiceStart notification will be generated when the service is restarted NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1144 |
starApsCommandSuccessAPS Command Success Status. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1145 |
starApsCommandFailureAPS Command Failure Status. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1146 |
starApsSwitchSuccessAPS Switch Success Status. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1147 |
starApsSwitchFailureAPS Switch Failure Status. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1148 |
starApsModeMismatchAPS Mode Mismatch Status. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1149 |
starApsChannelMismatchAPS Channel Mismatch Status. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1150 |
starApsByteMismatchAPS Byte Mismatch Status. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1151 |
starApsFeProtLineFailureAPS FE Protocol Line Failure Status. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1152 |
starApsLossOfRedundancyAPS Loss of Redundancy Status. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1153 |
starApsLossOfRedundancyClearAPS Loss of Redundancy Clear Status. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1154 |
starHNBGWSGSNRanapResetRANAP Reset Received from SGSN NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1155 |
starHNBGWMSCRanapResetRANAP Reset Received from MSC NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1156 |
starALCAPNodeResetALCAP Node Reset Received from MGW NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1157 |
starALCAPPathResetALCAP Path Reset Received from MGW NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1158 |
starALCAPPathBlockALCAP Block Received from MGW NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1159 |
starALCAPPathUnBlockALCAP Un Block Received from MGW NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1160 |
starSGSServiceStartA SGS Service has started Action to be Taken: No action required NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1161 |
starSGSServiceStopA SGS Service has stopped. Probable Cause: This is typically caused by operator invention. In unusual cases it can be caused by the loss of resources (PACs/PSCs) to support the running configuration. Action to be Taken: If the SGS service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured PACs/PSCs are present and running in the system. Check the crash logs for an indication of a software failure. Clear Condition: Verify that the SGS service is operational. Condition Clear Alarm: A starSGSServiceStart notification will be generated when the service is restarted NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1162 |
starSgsnGnMsgDelayMessaging Dealy seen towards GGSN as many messages sent to that GGSN did not receive response within a certain time NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1163 |
starSgsnGnMsgDelayClearThe delay seen towards GGSN is no longer seen as message responses are received in time as expected NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1164 |
starBNGServiceStartA BNG Service has started Action to be Taken: No action required NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1165 |
starBNGServiceStopA BNG Service has stopped. Probable Cause: This is typically caused by operator invention. In unusual cases it can be caused by the loss of resources (PACs/PSCs) to support the running configuration. Action to be Taken: If the BNG service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured PACs/PSCs are present and running in the system. Check the crash logs for an indication of a software failure. Clear Condition: Verify that the BNG service is operational. Condition Clear Alarm: A starBNGServiceStart notification will be generated when the service is restarted NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1166 |
starMMES1AssocFailAn S1 Association between an MME service and an eNodeB has failed. Action to be Taken: If the shutdown of the eNodeB was not planned, determine the health/status of the eNodeB. If available, verify the health of the network between the two elements. Clear Condition: The condition is cleared with the S1 Association is reestablished. Condition Clear Alarm: A starMMES1AssocEstab notification will be generated when the S1 association is re-established NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1167 |
starMMES1AssocSetupAn S1 Association between an MME service and an eNodeB has been established. Normally a starMMES1AssocSetup notification would be generated only for an associated which had previously failed, but optionally this notification can be generated for any association setup. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1168 |
starMVGPeerDownA MVG peer is down. Problem Cause: The MVG peer has failed, or a network connectivity prevents reaching the peer. Condition Clear Alarm: A starMVGPeerUp notification will be generated when the peer is up NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1169 |
starMVGPeerUpA MVG peer is up. This notification is only generated for peers which have previously been declared down. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1170 |
starPCCNtfyIntfPeerUnreachableThe IPCF Event Notification Interface peer cannot be reached. ? Probable Cause: The Event Notification server on SPR is down Or the IP-address/port configuration does not match with the server Actions to be Taken: Check the Event notification server on SPR and ensure it is running. Ensure that IP-address port combination on IPCF match the server side configurations. Clear Condition: Verify that the Event notification interface status on boxer is up. Condition Clear Alarm: When this condition clears a starNtfyIntfPeerReachable notification will be generated. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1173 |
starPCCNtfyIntfPeerReachableThe Notification Interface peer can be reached.? Action to be Taken: No Action Required. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1174 |
starIPSecNodePeerDownA Node Service peer has stopped responding. Problem Cause: The IPSec Node peer has failed, or a network connectivity prevents reaching the peer. Condition Clear Alarm: A starIPSecNodePeerUp notification will be generated when the peer is up NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1175 |
starIPSecNodePeerUpA Node Service peer is back online Action to be Taken: No action required NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1176 |
starApsRemoteResponseFailAPS Remote Response Fail. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1177 |
starCdrPurgedCDRs purged NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1178 |
starLocalUserAddedA local user was added to the system. Probable Cause: A command was issued which resulted in a new user being added to the local user database. If this was not a planned action then further investigation is advised. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1180 |
starLocalUserRemovedA local user was removed from the system. Probable Cause: A command was issued which resulted in an existing user being removed from the local user database. If this was not a planned action then further investigation is advised. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1181 |
starLocalUserPrivilegeChangedA local user's privileges were modified. Probable Cause: A command was issued which resulted in an existing user's privileges being modified. If this was not a planned action then further investigation is advised. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1182 |
starOsShellAccessedA user has accessed the OS shell. Probable Cause: A command was issued which resulted in a user's access to the operating system shell. If this activity was not anticipated, then further investigation should be performed. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1183 |
starTestModeEnteredA user has entered the StarOS Test Mode. Probable Cause: A command was issued which resulted in a user entering the CLI test command mode. The test command mode is only intended for maintenance and diagnostic activity and could result in major service disruptions. If this action was not intentional, the user should exit from test mode. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1184 |
starLicenseFeaturesModifiedA user has manually modified the StarOS license feature set through the CLI. Probable Cause: A command was issued which resulted in a user modifying the set of license features available to the user. This capability was only intended for maintenance and diagnostic activity and could result in major service disruptions. If this action was not intentional, the user should restore the original license feature set. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1185 |
starHiddenAccessEnabledAn administrator has explicitly enabled the use of hidden test commands. Probable Cause: A command was configured which resulted in users having access to the specific test commands which may have been previously unavailable. If this action was not intentional, the user should disable access to the hidden test commands. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1186 |
starHiddenAccessDisabledAn administrator has explicitly disabled the use of hidden test commands. Probable Cause: A command was configured which resulted in users no longer having access to specific test commands which may have been previously available. If this action was not intentional, the user should re-enable access to the hidden test commands. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1187 |
starLawfulInterceptChangedOriginal Lawful Intercept configured by Admin: %s is changed by Admin: %s NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1188 |
starMMES1PathFailAn S1 Path between an MME service and an eNodeB has failed. Action to be Taken: If the shutdown of the eNodeB was not planned, determine the health/status of the eNodeB. If available, verify the health of the network between the two elements. Clear Condition: The condition is cleared with the S1 Path is reestablished. Condition Clear Alarm: A starMMES1PathEstab notification will be generated when the S1 path is re-established NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1189 |
starMMES1PathSetupAn S1 Path between an MME service and an eNodeB has been established. Normally a starMMES1PathSetup notification would be generated only for a path which had previously failed, but optionally this notification can be generated for any path setup. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1190 |
starSAEGWServiceStartA SAEGW Service has started Action to be Taken: No action required NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1191 |
starSAEGWServiceStopA SEAGW Service has stopped. Probable Cause: This is typically caused by operator invention. In unusual cases it can be caused by the loss of resources (PACs/PSCs) to support the running configuration. Action to be Taken: If the SAEGW service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured PACs/PSCs are present and running in the system. Check the crash logs for an indication of a software failure. Clear Condition: Verify that the SEAGW service is operational. Condition Clear Alarm: A starSAEGWServiceStart notification will be generated when the service is restarted NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1192 |
starHenbgwAccessServiceStartA HENBGW Access Service has started Action to be Taken: No action required NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1193 |
starHenbgwAccessServiceStopA HENBGW Access Service has stopped. Probable Cause: This is typically caused by operator invention. In unusual cases it can be caused by the loss of resources (PACs/PSCs) to support the running configuration. Action to be Taken: If the HENBGW Access service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured PACs/PSCs are present and running in the system. Check the crash logs for an indication of a software failure. Clear Condition: Verify that the HENBGW Access service is operational. Condition Clear Alarm: A starHenbgwAccessServiceStart notification will be generated when the service is restarted NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1194 |
starHenbgwNetworkServiceStartA HENBGW Network Service has started Action to be Taken: No action required NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1195 |
starHenbgwNetworkServiceStopA HENBGW Network Service has stopped. Probable Cause: This is typically caused by operator invention. In unusual cases it can be caused by the loss of resources (PACs/PSCs) to support the running configuration. Action to be Taken: If the HENBGW Network service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured PACs/PSCs are present and running in the system. Check the crash logs for an indication of a software failure. Clear Condition: Verify that the HENBGW Network service is operational. Condition Clear Alarm: A starHenbgwNetworkServiceStart notification will be generated when the service is restarted NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1196 |
starAAAArchiveStartedArchive started NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1197 |
starECSTotalDNSLearntIPv4ThresholdDNS Learnt IPv4 entries exceed the threshold limit (high water mark) configured. For IPv4 Max IP entries = 512,00 Alarm Cleared when the IPv4 entries go below the Lower Water Mark configured NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1198 |
starECSTotalDNSLearntIPv4ThresholdClearDNS Learnt IPv4 entries reach below the threshold limit (lower water mark) configured. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1199 |
starECSTotalDNSLearntIPv6ThresholdDNS Learnt IPv6 entries exceed the threshold limit (high water mark) configured. For IPv6 Max IP entries = 256,00 Alarm Cleared when the IPv6 entries go below the Lower Water Mark configured NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1200 |
starECSTotalDNSLearntIPv6ThresholdClearDNS Learnt IPv6 entries reach below the threshold limit (lower water mark) configured. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1201 |
starIPSecNodeIpv6PeerDownA Node Service peer has stopped responding. This peer is reached using an IPv6 address. For IPv4-connected peers, a starIPSecNodePeerDown notification would be generated. Problem Cause: The IPSec Node peer has failed, or a network connectivity prevents reaching the peer. Condition Clear Alarm: A starIPSecNodeIpv6PeerUp notification will be generated when the peer is up NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1202 |
starIPSecNodeIpv6PeerUpA Node Service peer is back online. This peer is reached using an IPv6 address. For IPv4-connected peers, a starIPSecNodePeerUp notification would be generated. Action to be Taken: No action required NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1203 |
starLAGGroupDownLAG group status is Down. This notification is only generated for master physical port and a previous 'starLAGGroupUp' notification was previously generated. Action to be Taken: No action required. The cause for the LAG down should be investigated. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1204 |
starLAGGroupUpLAG group status is up. This notification is only generated for master physical port. Action to be Taken: No action required NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1205 |
starVLRAssocDownA VLR Association is down. Problem Cause: The VLR Association has failed, or a network connectivity prevents reaching the VLR. Condition Clear Alarm: A starVLRAssocUp notification will be generated when the VLR association is up NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1206 |
starVLRAssocUpA VLR Association is up. This notification is only generated for Association which have previously been declared down. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1207 |
starVLRAllAssocDownAll the VLR Associations are down. Problem Cause: All the VLR Associations has failed, or network connectivity prevents reaching the VLRs. Condition Clear Alarm: A starVLRAllAssocUp notification will be generated when all the VLR associations are up NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1208 |
starVLRAllAssocDownClearVLR at least one association is up. This notification is only generated for all the Association which have previously been declared down. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1209 |
starEnhancedCongestionA congestion condition has occurred. Probable Cause: This is the result of an operator-configured congestion threshold being reached. This can be due to high usage of the resource being monitored which indicates that the IMG is reaching its peak capacity, or could be caused by the incorrect configuration of the congestion thresholds. Actions to be Taken: Verify that the congestion thresholds are correct; if the congested state is seem repeatedly, or for sustained periods of time, additional system capacity may need to be brought online. This system is cleared when the use of the specific resource falls below the configured limit. Condition Clear Alarm: A starCongestionClear notification is sent when there are no congestion conditions for a service type NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1210 |
starEnhancedCongestionClearA congestion condition has cleared. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1211 |
starSGSNRNCNoResetAckSGSN has not received an Radio Network Controller(RNC) reset-ack event. This event is generated on expiry of all retransmission for RNC Reset and non-receipt of Reset-Ack. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1212 |
starThreshSAEGWSessionsThe total number of SAEGW sessions is above the configured threshold value. Probable Cause: This is a user configurable threshold. If the thresholding subsystem is configured to run in an 'alarm' model,a starThreshClearSAEGWSessions notification will be generated when the measured value falls below the threshold NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1213 |
starThreshClearSAEGWSessionsThe threshold condition is now clear. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1214 |
starSGSNRMCPUWarnThe CPU usage is goin in Warning level. This event is generated when current CPU usage reaches 90% of allocated limit. Condition Clear Alarm: A starSGSNRMCPUWarnClear notification is sent when there CPU usage reaches 50% of allocated limit after warning NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1215 |
starSGSNRMCPUWarnClearThe CPU usage is coming back to normal once warned. This event is generated when current CPU usage reaches 50% of allocated limit after warning. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1216 |
starSGSNRMMemWarnThe Memory usage for the proclet is going in Warning level. This event is generated when current Memory usage exceeds allocated limit. Condition Clear Alarm: A starSGSNRMMemWarnClear notification is sent when current Memory usage reaches below 95% of allocated limit once warned. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1217 |
starSGSNRMMemWarnClearThe Memory usage for the proclet is coming back to normal once warned. This event is generated when current Memory usage reaches below 95% of allocated limit once warned. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1218 |
starRMCPUOverThe CPU usage is goin in Overlaod level. This event is generated when current CPU usage reaches 50% more of allocated limit. Condition Clear Alarm: A starRMCPUOverClear notification is sent when urrent CPU usage reaches 50% of allocated limit after over NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1219 |
starRMCPUOverClearThe CPU usage is going back to normal level. This event is generated when current CPU usage reaches 50% of allocated limit after over. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1220 |
starSGSNRMMemOverThe Memory usage of the task is going in Overload level. This event is generated when current Memory usage reached twice allocated limit. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1221 |
starSGSNRMMemOverClearThe Memory usage for a proclet reached normal after overload. This event is generated when current Memory usage reaches 95% of allocated limit once overloaded. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1222 |
starSessMgrFlowCountSession Manager Flows counting, This event is genereted when number of flows in a session manager instance goes beyond configured threshold,it will also print number of PDN, Memeory usage and sess manager instance number. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1223 |
starSessMgrFlowCountClearClear Session Manager Flows Counting Trap, This event is genereted when number of flows in a session manager instance goes below configured threshold,it will also print number of PDN, Memeory usage and sess manager instance number. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1224 |
starStorageFoundThe specified storage device is found and mounted successfully on the card. This notification only generated to the storage device for which 'starStorageNotFound' notification was generated NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1225 |
starStorageNotFoundThe specified storage device not found on the card. This notification is currently only generated for failures to access the specified storage device on the card. Probable Cause: The storage device is not accessible on the card. Action to be Taken: Verify the storage device on the card is attached correctly. Condition Clear Alarm: A starStorageFound notification will be generated when the storage device is mounted on the card. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1226 |
starHENBGWMMESCTPAssocDownA HENBGW MME SCTP Association is down. Problem Cause: The HENBGW MME SCTP Association has failed, or a network connectivity prevents reaching the MME. Condition Clear Alarm: A starHENBGWMMESCTPAssocUp notification will be generated when the HENBGW MME SCTP association is up. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1227 |
starHENBGWMMESCTPAssocUpA HENBGW MME SCTP Association is up. This notification is only generated for Association which have previously been declared down, optionally this notification can be generated for any association up. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1228 |
starHENBGWMMESCTPAllAssocDownAll the HENBGW MME SCTP Associations are down. Problem Cause: All the HENBGW MME SCTP Associations has failed, or network connectivity prevents reaching the MMEs. Condition Clear Alarm: A starHENBGWMMESCTPAllAssocDownClear notification will be generated when at least one HENBGW MME SCTP association is up. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1229 |
starHENBGWMMESCTPAllAssocDownClearHENBGW MME SCTP at least one association is up. This notification is only generated for all the Association which have previously been declared down. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1230 |
starNPDBConnectionDownA NPDB connection is down. Probable Cause: This is typically caused when NPDB server resets the socket. Action to be Taken: Check if the NDPB Server is running. Clear Condition: Verify that PING PONG messages are exchanged with the NPDB Server. Condition Clear Alarm: A startNPDBConnectionUp notification will be generated when the service is restarted NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1231 |
starNPDBConnectionUpA NPDB connection is up. Action to be Taken: No action required NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1232 |
starNPUMissedARPFramesThis trap will be raised when NPU misses the ARP and packets route to kernel. This will print the slot number CPU number and NPU number NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1233 |
starNPUMissedARPFramesClearThis clear trap will be raised when NPU misses the ARP and packets route to kernel recovers. This will print the slot number CPU number and NPU number NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1234 |
starChassisCrashListFullChassis crash list is reached full. This notification is generated when no more space is left to store the crash list and reached to disk limit. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1235 |
starSessMgrCSCFServiceRecoveryCompleteIndicates that the CSCF Service had completed recovery. This trap is generated when all the calls are recovered and the listen socket becomes active to accept packets NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1236 |
starECSreaddressServerDownServer from readdress server list is detected down This notification is generated when there are consecutive failures for server. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1237 |
starECSreaddressServerUpServer from readdress server list is detected up This notification is generated when after deadtime server is detected up. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1238 |
starCdrHDDStartCDRs are being written to the HDD NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1239 |
starCdrStreamingStartCDR streaming is started NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1240 |
starCdrStreamingCompleteCDR streaming is Completed NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1241 |
starVLRDownA VLR is down. Problem Cause: The VLR has failed, or a network connectivity prevents reaching the VLR. Condition Clear Alarm: A starVLRUp notification will be generated when the VLR is up NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1242 |
starVLRUpA VLR is up. This notification is only generated for VLRs which have previously been declared down. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1243 |
starPCFReachableA PCF that the IMG communication is reachable. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1244 |
starLIRcvryErrorThis trap will be raised when Lawful Intercepts cannot be saved or recovered to/from backup. This will print the type of error and error string NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1245 |
starLIRcvryCompleteThis trap will be raised when Lawful Intercepts are successfully recovered NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1246 |
starCGWServiceStartA Serving Gateway (CGW) Service has started. Action to be Taken: No action required NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1247 |
starCGWServiceStopA Serving Gateway (CGW) Service has stopped. Probable Cause: This is typically caused by operator intervention. In rare cases it can be caused by the loss of resources (PSCs) to support the running configuration. Action to be Taken: If the CGW service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured PSCs are present and running in the system. Check the crash logs for an indication of a software failure. Clear Condition: Verify that the CGW service is operational. Condition Clear Alarm: A starCGWServiceStart notification will be generated when the service is restarted NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1248 |
starMMENewConnectionsDisallowedThe demultiplexer on the MME chassis has reached a condition where new connections are being dropped/rejected on MME services due to the specified reason.Please note that this is the initial trigger for this condition. More reasons/triggers may be activated later i.e. after the trap has been sent. These are not indicated via a new trap. Action to be Taken: If this is not intentional (i.e not driven by policy/configuration), cross-check IMSImgr counters using the reason provided. Clear Condition: The condition is cleared when new connections at the MME are re-allowed. Condition Clear Alarm: A starMMENewConnectionsAllowed notification will be generated when the condition is cleared. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1249 |
starMMENewConnectionsAllowedThe MME chassis is now accepting new connections again. All conditions causing MME to disallow new connections have cleared. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1250 |
starSAMOGServiceStartA SAMOG Service has started Action to be Taken: No action required NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1251 |
starSAMOGServiceStopA SAMOG Service has stopped. Probable Cause: This is typically caused by operator invention. In unusual cases it can be caused by the loss of resources (PACs/PSCs) to support the running configuration. Action to be Taken: If the SAMOG service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured PACs/PSCs are present and running in the system. Check the crash logs for an indication of a software failure. Clear Condition: Verify that the SAMOG service is operational. Condition Clear Alarm: A starSAMOGServiceStart notification will be generated when the service is restarted NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1252 |
starCardSwitchoverStartA management card (SPC/MMIO) switchover operation has begun. The first varbind identifies from which management card switchover started. The second varbind identifies to which management card switchover is planned to switch. Switchover can cause a momentary loss of communication through the management interface (SPIO incase of ASR5000) , it is possible that this trap will not be successfully delivered. Probable Cause: This is typically caused by an operator action; it can also represent the system recovering from a software or hardware fault. Action to be Taken: If the management card switchover was unplanned, the admin logs should be examined for the cause of the switchover. If the cause was a software failure, the system crash logs should be examined. Clear Condition: Verify the management card switchover completed successfully. Clear Condition Alarm: A starCardSPCSwitchoverComplete is generated when the switchover operation has completed. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1253 |
starCardSwitchoverCompleteA management card (SPC/MMIO) Switchover has completed successfully. The first varbind identifies from which management card switchover started. The second varbind identifies to which management card switchover is completed. Action to be Taken: If the management card switchover was unplanned, the admin logs should be examined for the cause of the switchover. If the cause was a software failure, the system crash logs should be examined. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1254 |
starCardSwitchoverFailedA management card (SPC/MMIO) switchover operation has failed. The first varbind identifies from which management card switchover started. The second varbind identifies to which management card switchover is failed. Probable Cause: The management card being switched to was removed or reset before the switchover completed; the switchover operation was terminated by an operator; or a software or hardware failure on another management card. Action to be Taken: Verify that both management cards have the card locks in the locked position; examine the admin logs for the cause of the failure. If the cause was a software failure, the system crash logs should be examined. Clear Condition: The management card in question will be reset; a starCardUp notification will be generated when the card is operational again. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1255 |
starCardMigrateStartA data processing card (PAC/PSC/DPC) Migration operation has begun. The first varbind identifies from which data processing card migration has started. The second varbind identifies to which data processing card migration is planned to migrate. Probable Cause: This is typically caused by an operator action; it can also represent the system recovering from a software or hardware fault. A starCardMigrateComplete is generated when the migration is completed NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1256 |
starCardMigrateCompleteA data processing card (PAC/PSC/DPC) Migration operation has successfully completed. The first varbind identifies from which data processing card migration has started. The second varbind identifies to which data processing card migration has completed. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1257 |
starCardMigrateFailedA data processing card (PAC/PSC/DPC) Migration operation has failed. The first varbind identifies from which data processing card migration has started. The second varbind identifies to which data processing card migration has failed to migrate. Probable Cause: The data processing card being migrated to was removed or reset before the migration completed; the migration operation was terminated by an operator; or a software or hardware failure on another data processing card involved in the migration operation. The data processing card in question will be reset; a starCardUp notification will be generated when the card is operational again. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1258 |
starTechSuppPasswdChangedA user has changed the StarOS tech-support password. Probable Cause: A command was issued which resulted in a user changing the tech-support password value. The tech-support password is used to gain access to the CLI test-commands. These CLI test commands are only intended for maintenance and diagnostic activity and could result in major service disruptions. If this action was unintended, the user should notify the Cisco TAC group to reset the tech-support password. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1259 |
starPMIPPathFailurePMIP Path Failure. Possibe reason: This trap will be triggered by MAGMGR/HAMGR when path failure or node restart is detected. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1260 |
starPMIPPathFailureClearPMIP Control Path Failure condition is no longer valid. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1261 |
starHENBGWMMESCTPAssocDestAddrDownA HENBGW MME SCTP Association Destination Address is down. Problem Cause: One of destination MME SCTP address is not reachable or removed. Condition Clear Alarm: A starHENBGWMMESCTPAssocDestAddrUp notification will be generated when the HENBGW MME SCTP association destination address is reachable again NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1262 |
starHENBGWMMESCTPAssocDestAddrUpA HENBGW MME SCTP Association Destination Address is up. This notification is only generated for Association Destination Address which have previously been declared down. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1263 |
starMRMEServiceStartA Multi Radio Management (MRME) Service has started. Action to be Taken: No action required NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1264 |
starMRMEServiceStopA Multi Radio Management (MRME) Service has stopped. Probable Cause: This is typically caused by operator invention. In unusual cases it can be caused by the loss of resources (PACs/PSCs) to support the running configuration. Action to be Taken: If the MRME service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured PACs/PSCs are present and running in the system. Check \ the crash logs for an indication of a software failure. Clear Condition: Verify that the MRME service is operational. Condition Clear Alarm: A starMRMEServiceStart notification will be \ generated when the service is restarted NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1265 |
starSLSServiceStartAn SLS Service has started Action to be Taken: No action required NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1266 |
starSLSServiceStopAn SLS Service has stopped. Probable Cause: This is typically caused by operator invention. In unusual cases it can be caused by the loss of resources (PACs/PSCs) to support the running configuration. Action to be Taken: If the SLS service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured PACs/PSCs are present and running in the system. Check the crash logs for an indication of a software failure. Clear Condition: Verify that the SLS service is operational. Condition Clear Alarm: A starSLSServiceStart notification will be generated when the service is restarted NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1267 |
starESMLCAssocDownAn ESMLC Association is down. Problem Cause: The ESMLC Association has failed, or a network connectivity prevents reaching the ESMLC. Condition Clear Alarm: A starESMLCAssocUp notification will be generated when the ESMLC association is up NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1268 |
starESMLCAssocUpAn ESMLC Association is up. This notification is only generated for Association which have previously been declared down. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1269 |
starESMLCAllAssocDownAll the ESMLC Associations are down. Problem Cause: All the ESMLC Associations has failed, or network connectivity prevents reaching the ESMLCs. Condition Clear Alarm: An starESMLCAllAssocUp notification will be generated when all the ESMLC associations are up NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1270 |
starESMLCAllAssocDownClearAt least one ESMLC associations is up. This notification is only generated for all the Association which have previously been declared down. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1271 |
starSBCServiceStartAn SBc Service has started Action to be Taken: No action required NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1272 |
starSBCServiceStopAn SBc Service has stopped. Probable Cause: This is typically caused by operator intervention, when a critical parameter associated with sbc-service is changed/removed. In unusual cases it can be caused by the loss of resources (PACs/PSCs) to support the running configuration. Action to be Taken: If the SBc service shutdown was not planned, examine the admin logs for any indication of the failure. Verify that all configured PACs/PSCs are present and running in the system. Check for any sbc-service related configuration errors by running show configuration errors section sbc-service. Note that sbc-service should be associated to an mme-service to be operationally up. In case the associated mme-service is down, sbc-service is also stopped. Also check the crash logs for any indication of a software failure. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1273 |
starCBCAssocDownA CBC Association is down. Problem Cause: SCTP connection between MME and CBC has been brought down - could be for any of the following reasons - i) network connectivity between MME and CBC is broken. ii) CBC has gracefully terminated the SCTP association with MME. iii) MME has gracefully terminated the SCTP association with CBC, typically due to operation intervention that would have effected sbc-service. Action to be taken - In case the SCTP association between MME and CBC is abnormally closed, check for network connectivity between MME and CBC. Condition Clear Alarm: In case the association termination was abnormal, A starPeerAssocUp notification will be generated when the CBC association is up NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1274 |
starCBCAssocUpA CBC Association is up. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1275 |
starBFDSessUpThe BFD Session to the specified IP address is operational. This may indicate the initial configuration of a new neighbor, the initial connectivity after a system restart, or the restoration of connectivity after a starBFDSessDown event. Action to be Taken: No action required. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1276 |
starBFDSessDownThe BFD Session to the specified IP address is no longer operational. Probable Cause: The BFD Session is not-operational; the network between the ASR5x00 and the BFD Neighbor is experiencing an outage; Look into the Diagnostic Code for further details. Action to be Taken: Verify the BFD Session is operational; verify network connectivity to the BFD Neighbor. Clear Condition Alarm: A starBFDSessUp is generated when connectivity is reestablished NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1277 |
starSRPSwitchoverOccuredAn SRP (ICSR) Switchover Occurred. Chassis has transitioned from Active to Standby State or Chassis has transitioned from Standby to PendingActive State. Action to be Taken: Verify Active and Standby Chassis States of ICSR pair. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1278 |
starHENBGWMMEOverloadStartA HENBGW MME Overload Start message received. Condition Clear Alarm: A starHENBGWMMEOverloadStop notification will be generated when the HENBGW MME overload stop message received. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1279 |
starHENBGWMMEOverloadStopA HENBGW MME Overload Stop message received. This notification is only generated for the MME which have previously been generated overload start message, optionally this notification can be generated for any overload stop message received from MME. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1280 |
starNpudriverECCErrorA double bit ECC error occured. Action to be taken - RMA this card. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1281 |
starGTPCRLFOverThresholdGTP RLF Status update - GTP RLF Over Threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1282 |
starGTPCRLFOverLimitGTP RLF Status update - GTP RLF Over Limit. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1283 |
starGTPCRLFOverThresholdClearGTP RLF Status update - GTP RLF Over Threshold Cleared. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1284 |
starGTPCRLFOverLimitClearGTP RLF Status update - GTP RLF Over Limit Cleared. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1285 |
starS102ServiceStartAn S102 Service has started Action to be Taken: No action required NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1286 |
starS102ServiceStopAn S102 Service has stopped Probable Cause: This is typically caused by operator invention. In unusual cases it can be caused by the loss of resources (PACs/PSCs) to support the running configuration. Action to be Taken: If the S102 service shutdown was not planned, examine the admin logs for an indication of the failure. Verify that all configured PACs/PSCs are present and running in the system. Check the crash logs for an indication of a software failure. Clear Condition: Verify that the S102 service is operational. Condition Clear Alarm: A starS102ServiceStart notification will be generated when the service is restarted NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1287 |
starBGPPeerSessionIPv6UpThe BGP peer session to the specified IP v6 address is operational. This may indicate the initial configuration of a new peer, the initial connectivity after a system restart, or the restoration of connectivity after a starBGNPeerSessionDown event. Action to be Taken: No action required. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1288 |
starBGPPeerSessionIPv6DownThe BGP peer session to the specified IP v6 address is no longer operational. Probable Cause: The BGP peer is not-operational; the network between the ST16 and the BGP peer is experiencing an outage; LC failure(s) on the ST16. Action to be Taken: Verify the BGP peer is operational; verify network connectivity to the BGP peer. Clear Condition Alarm: A starBGPPeerSessionUp is generated when connectivity is reestablished NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1289 |
starMMEEMBMSServiceStartAn MME-EMBM Service has started Action to be Taken: No action required NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1290 |
starMMEEMBMSServiceStopAn MME-EMBMS Service has stopped. Probable Cause: This is typically caused by operator intervention, when a critical parameter associated with mme-embms-service is changed/removed. In unusual cases it can be caused by the loss of resources (PACs/PSCs) to support the running configuration. Action to be Taken: If the MME-EMBMS service shutdown was not planned, examine the admin logs for any indication of the failure. Verify that all configured PACs/PSCs are present and running in the system. Check for any mme-embms-service related configuration errors by running show configuration errors section mme-embms-service. Also check the crash logs for any indication of a software failure. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1291 |
starMCEAssocDownAn MCE Association is down. Problem Cause: SCTP connection between MME and MCE has been brought down - could be for any of the following reasons - i) network connectivity between MME and MCE is broken. ii) MCE has gracefully terminated the SCTP association with MME. iii) MME has gracefully terminated the SCTP association with MCE, typically due to operation intervention that would have effected mme-embms-service. Action to be taken - In case the SCTP association between MME and MCE is abnormally closed, check for network connectivity between MME and MCE. Condition Clear Alarm: In case the association termination was abnormal, A starPeerAssocUp notification will be generated when the MCE association is up NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1292 |
starMCEAssocUpA MCE Association is up. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1293 |
starIuBcTcpConnDownA TCP connection at IuBc interface is down. Problem Cause: TCP connection between HNBGW and CBC server has been brought down - could be for any of the following reasons - i) network connectivity between HNBGW and CBC server is broken. ii) CBC Server has gracefully terminated the TCP connection with HNBGW. iii) HNBGW has gracefully terminated the TCP connection with CBC server, typically due to operation intervention that would have effected cbs-service. Action to be taken - In case the TCP connection between HNBGW and CBC server is abnormally closed, check for network connectivity between HNBGW and CBC server. Condition Clear Alarm: In case the connection termination was abnormal, A IuBcTCPConnUp notification will be generated when the TCP connection is up NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1294 |
starIuBcTcpConnUpA TCP Connection is up. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1295 |
starSessCapReachedSession manager will start rejecting new calls as the capacity reached. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1298 |
starLAGGroupDownDueToMinlinkLAG group status is Down due to links in LAG group falls below minlink . This notification is only generated for master physical port and a previous 'starLAGGroupUp' notification was previously generated. Action to be Taken: No action required. The cause for the LAG down should be investigated. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1299 |
starSerdesLanePermDownA serdes lanes is a high speed serial link between a FAP(chip on an MIO/DPC/DPC2/MIO2) and an FE(chip on an FSC card). When a serdes lane has errors, we calibrate it to get optimized Rx parameters. If we attempt to calibrate a lane more than 5 times, it is taken offline. By taking it offline we no longer use it so we are eliminating potential traffic loss.. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1303 |
starThreshAllFramedRoutesAll framed routes crosses user defined threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1304 |
starThreshAllFramedRoutesClearAll framed routes crosses user defined threshold cleared. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1305 |
starThreshAllTotalRoutesAll total routes crosses user defined threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1306 |
starThreshAllTotalRoutesClearAll total routes crosses user defined threshold cleared. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1307 |
starThreshVRFFramedRoutesTotal number of VRF framed routes crosses user defined threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1308 |
starThreshVRFFramedRoutesClearTotal number of VRF framed routes crosses user defined threshold cleared. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1309 |
starThreshVRFTotalRoutesTotal number of VRF total routes crosses user defined threshold. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1310 |
starThreshVRFTotalRoutesClearTotal number of VRF total routes crosses user defined threshold cleared. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1311 |
starStatFilesizeExceededActual Bulkstat filesize crosses 80% user defined Bulkstat filesize. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1312 |
starStatFilesizeClearActual Bulkstat filesize crosses 80% user defined Bulkstat filesize condition cleared. NOTIFICATION-TYPE .1.3.6.1.4.1.8164.2.1313 |
starentMIBConformance OBJECT IDENTIFIER .1.3.6.1.4.1.8164.3 |
starentMIBGroups OBJECT IDENTIFIER .1.3.6.1.4.1.8164.3.1 |
starChassisGroupA collection of objects providing information about a chassis Unknown .1.3.6.1.4.1.8164.3.1.1 |
starAlertGroupA collection of objects to control the rate at which traps can be generated Unknown .1.3.6.1.4.1.8164.3.1.3 |
starAlertTrapGroupA collection of traps related to trap thresholding Unknown .1.3.6.1.4.1.8164.3.1.4 |
starTrapGroupA collection of objects which represent required notifications. Unknown .1.3.6.1.4.1.8164.3.1.5 |
starTrapObsoleteGroupA collection of objects which represent obsolete notifications.obsolete Unknown .1.3.6.1.4.1.8164.3.1.6 |
starChassisObsoleteGroupA collection of objects which are obsolete.obsolete Unknown .1.3.6.1.4.1.8164.3.1.7 |
starentMIBCompliances OBJECT IDENTIFIER .1.3.6.1.4.1.8164.3.2 |
starentMIBCompliance2The compliance statement for ... Unknown .1.3.6.1.4.1.8164.3.2.2 |