STARENT-MIB

File: STARENT-MIB.mib (980849 bytes)

Imported modules

SNMPv2-SMI SNMPv2-TC IPV6-TC
SNMPv2-CONF INET-ADDRESS-MIB RADIUS-AUTH-CLIENT-MIB
RADIUS-ACC-CLIENT-MIB

Imported symbols

MODULE-IDENTITY OBJECT-TYPE enterprises
Integer32 Gauge32 Counter32
Counter64 Unsigned32 NOTIFICATION-TYPE
IpAddress TEXTUAL-CONVENTION DisplayString
DateAndTime TruthValue Ipv6Address
MODULE-COMPLIANCE OBJECT-GROUP NOTIFICATION-GROUP
InetAddressType InetAddress radiusAuthServerIndex
radiusAuthServerAddress radiusAccServerIndex radiusAccServerAddress

Defined Types

StarentSlotType  
Describes the type of a slot. Each slot in the chassis is build to contain specific type(s) of cards. Only a card of one of the appropriate types can be put into a specific slot.
TEXTUAL-CONVENTION    
  INTEGER unknown(1), pactac(2), spc(3), lc(4), rcc(5), spio(6)  

StarentCardType  
Describes the type of a card. Each type represents a physically different card which would have a unique part number.
TEXTUAL-CONVENTION    
  INTEGER none(1), unknown(2), spc(3), pac(4), spio(5), rcc(6), lceth(7), lcgeth(8), lcds3(9), tac(10), lcoc3(11), lcoc12(12), smc(13), psc(14), lcqgeth(15), lctgeth(16), vmc(17), vpc(18), vlceth1p(19), lcgeth2(20), lceth2(21), psc2(22), psc3(23), pscA(24), ppc(25), lcchan3p2(26), lcchan3p4(27), fanctrl6(28), vioc(29), gpdsp(30), xme(31), vop(32), edc(33), mio(34), mio10g10p(35), mio10g20p(36), mio40g2p(37), mio40g4p(38), mio40g12p(39), miodc(40), fsc(41), dpc(42), mdpc(43), dpcdc(44), ssc(45), voc(46), cfc(47), sfc1p(48), sfc2p(49), sfc3p(50), sfc4p(51), dpc2(52)  

StarentVersionNum  
TEXTUAL-CONVENTION    
  OCTET STRING Size(0..256)  

StarRelayState  
The state of a Central Office (CO) relay.
TEXTUAL-CONVENTION    
  INTEGER off(1), on(2), unknown(3)  

StarLongDurTimeoutAction  
The action taken by the system upon detection of a long-duration session
TEXTUAL-CONVENTION    
  INTEGER unknown(0), detection(1), disconnection(2), notapplicable(3), dormantdisconnection(4), dormantdetection(5)  

StarShortName  
A short identification string. Follows the same conventions as the DisplayString TEXTUAL-CONVENTION.
TEXTUAL-CONVENTION    
  OCTET STRING Size(1..32)  

StarShortID  
An abbreviated form for identifying a service, composed of the first 8 characters of the context name, and the first 8 characters of a service name, seperated by (:)
TEXTUAL-CONVENTION    
  OCTET STRING Size(1..17)  

StarMediumID  
An abbreviated form for identifying a context-specific object, composed of the first 8 characters of the context name, and the first 16 characters of the object name, seperated by (:)
TEXTUAL-CONVENTION    
  OCTET STRING Size(1..25)  

StarENBID  
An eNodeB identifier in the form aaa:bbb:cccccccc
TEXTUAL-CONVENTION    
  OCTET STRING Size(1..16)  

StarQOSTPAction  
Traffic Policing Action
TEXTUAL-CONVENTION    
  INTEGER unknown(0), notapplicable(1), transmit(2), drop(3), loweripprecedence(4)  

StarOSPFNeighborState  
OSPF Neighbore State
TEXTUAL-CONVENTION    
  INTEGER unknown(0), down(1), attempt(2), init(3), twoway(4), exstart(5), exchange(6), loading(7), full(8)  

StarSlotEntry  
SEQUENCE    
  starSlotNum Integer32
  starSlotType StarentSlotType
  starCardType StarentCardType
  starCardOperState INTEGER
  starCardAdminState INTEGER
  starCardRevision StarentVersionNum
  starCardLastStateChange DateAndTime
  starCardMode INTEGER
  starCardPacStandbyPriority Gauge32
  starCardHaltIssued INTEGER
  starCardLock INTEGER
  starCardRebootPending INTEGER
  starCardUsable INTEGER
  starCardSinglePOF INTEGER
  starCardAttachment INTEGER
  starCardTemperature Gauge32
  starSlotVoltage1dot5 Gauge32
  starSlotVoltage1dot5LowThresh Gauge32
  starSlotVoltage1dot5HighThresh Gauge32
  starSlotVoltage1dot8 Gauge32
  starSlotVoltage1dot8LowThresh Gauge32
  starSlotVoltage1dot8HighThresh Gauge32
  starSlotVoltage2dot5 Gauge32
  starSlotVoltage2dot5LowThresh Gauge32
  starSlotVoltage2dot5HighThresh Gauge32
  starSlotVoltage3dot3 Gauge32
  starSlotVoltage3dot3LowThresh Gauge32
  starSlotVoltage3dot3HighThresh Gauge32
  starSlotVoltage5dot0 Gauge32
  starSlotVoltage5dot0LowThresh Gauge32
  starSlotVoltage5dot0HighThresh Gauge32
  starSlotNumPorts Gauge32
  starSlotAction INTEGER
  starSlotVoltageState INTEGER
  starSlotNumCPU Integer32
  starSlotPartNumber DisplayString
  starSlotPartRevision DisplayString
  starSlotSerialNumber DisplayString
  starSlotCLEICode DisplayString
  starSlotCiscoModelName DisplayString
  starSlotCiscoHardwareRev DisplayString
  starSlotCiscoSerialNumber DisplayString
  starDeviceNum Integer32
  starSerdesNum Integer32

StarSlotMappingEntry  
SEQUENCE    
  starSlotMappingNum Integer32
  starSlotMappingType INTEGER
  starSlotMappingRCCNum Integer32
  starSlotMappingToSlot Integer32

StarFanEntry  
SEQUENCE    
  starFanNum Integer32
  starFanLocation INTEGER
  starFanStatus Integer32
  starFanSpeed INTEGER

StarLogEntry  
SEQUENCE    
  starLogName StarShortName
  starLogCurSize Gauge32
  starLogMaxSize Gauge32
  starLogText OCTET STRING

StarPowerEntry  
SEQUENCE    
  starPowerNumber INTEGER
  starPowerState INTEGER

StarCPUEntry  
SEQUENCE    
  starCPUSlot Integer32
  starCPUNumber Integer32
  starCPUUser Gauge32
  starCPUSystem Gauge32
  starCPUIdle Gauge32
  starCPUIO Gauge32
  starCPUIRQ Gauge32
  starCPULoad1Min Gauge32
  starCPULoad5Min Gauge32
  starCPULoad15Min Gauge32
  starCPUMemTotal Integer32
  starCPUMemUsed Gauge32
  starCPUNumProcesses Gauge32
  starCPUMemCached Gauge32

StarNPUMgrEntry  
SEQUENCE    
  starNPUMgrNumber Integer32

StarServiceEntry  
SEQUENCE    
  starServiceVpnID Gauge32
  starServiceSvcID Gauge32
  starServiceVpnName DisplayString
  starServiceServName DisplayString
  starServiceSubLimit Unsigned32
  starServiceSubCurrent Gauge32
  starServiceType INTEGER
  starServiceFAIpAddr IpAddress
  starServiceHAIpAddr IpAddress

StarCLIEntry  
SEQUENCE    
  starCLIID Gauge32
  starCLIUsername DisplayString
  starCLITtyname DisplayString
  starCLIPrivs DisplayString
  starCLIType INTEGER
  starCLIRemoteIpAddrType InetAddressType
  starCLIRemoteIpAddr InetAddress
  starCLIContext DisplayString
  starCLIDatabaseUsername DisplayString

StarTaskEntry  
SEQUENCE    
  starTaskFacility Unsigned32
  starTaskInstance Unsigned32
  starTaskFacilityName DisplayString
  starTaskCard Unsigned32
  starTaskCPU Unsigned32

StarPPPStatEntry  
SEQUENCE    
  starPPPStatVpnID Gauge32
  starPPPStatSvcID StarShortID
  starPPPStatVpnName DisplayString
  starPPPStatServName DisplayString
  starPPPStatInit Counter32
  starPPPStatReneg Counter32
  starPPPStatSuccess Counter32
  starPPPStatFailed Counter32
  starPPPStatReleased Counter32
  starPPPStatReleasedLocal Counter32
  starPPPStatReleasedRemote Counter32
  starPPPStatLcpFailMaxRetry Counter32
  starPPPStatLcpFailOption Counter32
  starPPPStatIpcpFailMaxRetry Counter32
  starPPPStatIpcpFailOption Counter32
  starPPPStatCcpFail Counter32
  starPPPStatAuthFail Counter32
  starPPPStatLcpEntered Counter32
  starPPPStatAuthEntered Counter32
  starPPPStatIpcpEntered Counter32
  starPPPStatRenegPdsn Counter32
  starPPPStatRenegMobil Counter32
  starPPPStatRenegAddrMismatch Counter32
  starPPPStatRenegOther Counter32
  starPPPStatChapAuthAttempt Counter32
  starPPPStatPapAuthAttempt Counter32
  starPPPStatMSChapAuthAttempt Counter32
  starPPPStatChapAuthFail Counter32
  starPPPStatPapAuthFail Counter32
  starPPPStatMSChapAuthFail Counter32
  starPPPStatStacComp Counter32
  starPPPStatMppcComp Counter32
  starPPPStatDeflComp Counter32
  starPPPStatFscErrs Counter32
  starPPPStatUnknProto Counter32
  starPPPStatBadAddr Counter32
  starPPPStatBadCtrl Counter32
  starPPPStatVjComp Counter32
  starPPPStatDiscLcpRemote Counter32
  starPPPStatDiscRpRemote Counter32
  starPPPStatDiscAdmin Counter32
  starPPPStatDiscIdleTimeout Counter32
  starPPPStatDiscAbsTimeout Counter32
  starPPPStatDiscPPPKeepalive Counter32
  starPPPStatDiscNoResource Counter32
  starPPPStatDiscMisc Counter32
  starPPPStatFailedReneg Counter32
  starPPPStatLcpFailUnknown Counter32
  starPPPStatIpcpFailUnknown Counter32
  starPPPStatAuthAbort Counter32
  starPPPStatLowerLayerDisc Counter32
  starPPPStatLcpSuccess Counter32
  starPPPStatAuthSuccess Counter32
  starPPPStatRenegLowerLayerHandoff Counter32
  starPPPStatRenegParamUpdate Counter32
  starPPPStatChapAuthSuccess Counter32
  starPPPStatPapAuthSuccess Counter32
  starPPPStatMSChapAuthSuccess Counter32
  starPPPStatChapAuthAbort Counter32
  starPPPStatPapAuthAbort Counter32
  starPPPStatMSChapAuthAbort Counter32
  starPPPStatSessSkipAuth Counter32
  starPPPStatNegComp Counter32
  starPPPStatCCPNegFailComp Counter32
  starPPPStatDiscLocalLowerLayer Counter32
  starPPPStatDiscAddFlowFail Counter32
  starPPPStatDiscMaxRetriesLCP Counter32
  starPPPStatDiscMaxRetriesIPCP Counter32
  starPPPStatDiscMaxSetupTimer Counter32
  starPPPStatDiscInvalidDestVpn Counter32
  starPPPStatDiscOptNegFailLCP Counter32
  starPPPStatDiscOptNegFailIPCP Counter32
  starPPPStatDiscNoRemoteIpAddr Counter32
  starPPPStatDiscCallTypeDetectFail Counter32
  starPPPStatDiscRemoteDiscUpLayer Counter32
  starPPPStatDiscLongDuraTimeout Counter32
  starPPPStatDiscAuthFail Counter32
  starPPPStatLCPEchoTotalReq Counter32
  starPPPStatLCPEchoReqResent Counter32
  starPPPStatLCPEchoRepRecved Counter32
  starPPPStatLCPEchoReqTimeout Counter32
  starPPPStatRecvErrBadCtrlField Counter32
  starPPPStatRecvErrBadPacketLen Counter32
  starPPPStatRemoteTerm Counter32
  starPPPStatMiscFail Counter32

StarMIPHAStatEntry  
SEQUENCE    
  starMIPHAStatVpnID Gauge32
  starMIPHAStatSvcID StarShortID
  starMIPHAStatVpnName DisplayString
  starMIPHAStatServName DisplayString
  starMIPHAStatDisconnects Counter32
  starMIPHAStatExpiry Counter32
  starMIPHAStatDereg Counter32
  starMIPHAStatAdminDrop Counter32
  starMIPHAStatRegRecvTotal Counter32
  starMIPHAStatRegRecvInitial Counter32
  starMIPHAStatRegRecvRenew Counter32
  starMIPHAStatRegRecvDereg Counter32
  starMIPHAStatRegAcceptTotal Counter32
  starMIPHAStatRegAcceptReg Counter32
  starMIPHAStatRegAcceptRenew Counter32
  starMIPHAStatRegAcceptDereg Counter32
  starMIPHAStatRegDeniedTotal Counter32
  starMIPHAStatRegDeniedInitial Counter32
  starMIPHAStatRegDeniedRenew Counter32
  starMIPHAStatRegDeniedDereg Counter32
  starMIPHAStatRegReplyTotal Counter32
  starMIPHAStatRegReplyAcceptReg Counter32
  starMIPHAStatRegReplyAcceptDereg Counter32
  starMIPHAStatRegReplyDenied Counter32
  starMIPHAStatRegReplyBadReq Counter32
  starMIPHAStatRegReplyMismatchID Counter32
  starMIPHAStatRegReplyAdminProhib Counter32
  starMIPHAStatRegReplyUnspecErr Counter32
  starMIPHAStatRegReplyNoResource Counter32
  starMIPHAStatRegReplyMnAuthFail Counter32
  starMIPHAStatRegReplyFAAuthFail Counter32
  starMIPHAStatRegReplySimulBind Counter32
  starMIPHAStatRegReplyUnknownHA Counter32
  starMIPHAStatRegReplyRevTunUnav Counter32
  starMIPHAStatRegReplyRevTunMand Counter32
  starMIPHAStatRegReplyEncapUnav Counter32
  starMIPHAStatRegReplySendError Counter32
  starMIPHAStatFARevocations Counter32
  starMIPHAStatRegAcceptHO Counter32
  starMIPHAStatRegDeniedHO Counter32
  starMIPHAStatRegDiscardTotal Counter32

StarMIPFAStatEntry  
SEQUENCE    
  starMIPFAStatVpnID Gauge32
  starMIPFAStatSvcID StarShortID
  starMIPFAStatVpnName DisplayString
  starMIPFAStatServName DisplayString
  starMIPFAStatAdvertSend Counter32
  starMIPFAStatDiscExpiry Counter32
  starMIPFAStatDiscDereg Counter32
  starMIPFAStatDiscAdmin Counter32
  starMIPFAStatAuthAttempt Counter32
  starMIPFAStatAuthSuccess Counter32
  starMIPFAStatAuthFailure Counter32
  starMIPFAStatRegRecvTotal Counter32
  starMIPFAStatRegRecvInitial Counter32
  starMIPFAStatRegRecvRenewal Counter32
  starMIPFAStatRegRecvDereg Counter32
  starMIPFAStatRegAcceptTotal Counter32
  starMIPFAStatRegAcceptInitial Counter32
  starMIPFAStatRegAcceptRenewal Counter32
  starMIPFAStatRegAcceptDereg Counter32
  starMIPFAStatRegDenTotal Counter32
  starMIPFAStatRegDenInitial Counter32
  starMIPFAStatRegDenRenewal Counter32
  starMIPFAStatRegDenDereg Counter32
  starMIPFAStatRegDiscardTotal Counter32
  starMIPFAStatRegDiscardInitial Counter32
  starMIPFAStatRegDiscardRenewal Counter32
  starMIPFAStatRegDiscardDereg Counter32
  starMIPFAStatRegRelayedTotal Counter32
  starMIPFAStatRegRelayedInitial Counter32
  starMIPFAStatRegRelayedRenewal Counter32
  starMIPFAStatRegRelayedDereg Counter32
  starMIPFAStatRegAuthFailTotal Counter32
  starMIPFAStatRegAuthFailInitial Counter32
  starMIPFAStatRegAuthFailRenewal Counter32
  starMIPFAStatRegAuthFailDereg Counter32
  starMIPFAStatRegDenPDSNTotal Counter32
  starMIPFAStatRegDenPDSNInitial Counter32
  starMIPFAStatRegDenPDSNRenewal Counter32
  starMIPFAStatRegDenPDSNDereg Counter32
  starMIPFAStatRegDenHATotal Counter32
  starMIPFAStatRegDenHAInitial Counter32
  starMIPFAStatRegDenHARenewal Counter32
  starMIPFAStatRegDenHADereg Counter32
  starMIPFAStatRegDenPDSNUnspec Counter32
  starMIPFAStatRegDenPDSNTimeout Counter32
  starMIPFAStatRegDenPDSNAdmin Counter32
  starMIPFAStatRegDenPDSNResources Counter32
  starMIPFAStatRegDenPDSNMnAuth Counter32
  starMIPFAStatRegDenPDSNHAAuth Counter32
  starMIPFAStatRegDenPDSNTooLong Counter32
  starMIPFAStatRegDenPDSNBadReq Counter32
  starMIPFAStatRegDenPDSNEncapUnav Counter32
  starMIPFAStatRegDenPDSNRevTunUnav Counter32
  starMIPFAStatRegDenPDSNRevTunMand Counter32
  starMIPFAStatRegDenHAFAAuth Counter32
  starMIPFAStatRegDenHABadReq Counter32
  starMIPFAStatRegDenHAMismatchID Counter32
  starMIPFAStatRegDenHASimulBind Counter32
  starMIPFAStatRegDenHAUnknownHA Counter32
  starMIPFAStatRegDenHARevRunUnavail Counter32
  starMIPFAStatRegRplRcvTotal Counter32
  starMIPFAStatRegRplRcvTotalRly Counter32
  starMIPFAStatRegRplRcvErrors Counter32
  starMIPFAStatRegRplRcvInitial Counter32
  starMIPFAStatRegRplRcvInitialRly Counter32
  starMIPFAStatRegRplRcvRenewal Counter32
  starMIPFAStatRegRplRcvRenewalRly Counter32
  starMIPFAStatRegRplRcvDereg Counter32
  starMIPFAStatRegRplRcvDeregRly Counter32
  starMIPFAStatRegRplSentTotal Counter32
  starMIPFAStatRegRplSentAcceptReg Counter32
  starMIPFAStatRegRplSentAcceptDereg Counter32
  starMIPFAStatRegRplSentBadReq Counter32
  starMIPFAStatRegRplSentTooLong Counter32
  starMIPFAStatRegRplSentMnAuthFail Counter32
  starMIPFAStatRegRplSentHAAuthFail Counter32
  starMIPFAStatRegRplSentAdminProhib Counter32
  starMIPFAStatRegRplSentNoResources Counter32
  starMIPFAStatRegRplSentRevTunUnav Counter32
  starMIPFAStatRegRplSentRevTunMand Counter32
  starMIPFAStatRegRplSentSendErrors Counter32
  starMIPFAStatRegDenPDSNBadReply Counter32
  starMIPFAStatRegDenPDSNMissNAI Counter32
  starMIPFAStatRegDenPDSNMissHomeAgent Counter32
  starMIPFAStatRegDenPDSNMissHomeAddr Counter32
  starMIPFAStatRegDenPDSNUnknChallenge Counter32
  starMIPFAStatRegDenPDSNMissChallenge Counter32
  starMIPFAStatRegDenPDSNStaleChallenge Counter32
  starMIPFAStatRegDenPDSNMNTooDistant Counter32
  starMIPFAStatRegDenPDSNStyleUnavail Counter32
  starMIPFAStatRegDenPDSNHANetUnreach Counter32
  starMIPFAStatRegDenPDSNHAHostUnreach Counter32
  starMIPFAStatRegDenPDSNHAPortUnreach Counter32
  starMIPFAStatRegDenPDSNHAUnreach Counter32
  starMIPFAStatRegDenPDSNInvCOA Counter32
  starMIPFAStatRegReqSentInitTotal Counter32
  starMIPFAStatRegReqSentInitResend Counter32
  starMIPFAStatRegReqSentRenewTotal Counter32
  starMIPFAStatRegReqSentRenewResend Counter32
  starMIPFAStatRegReqSentDeregTotal Counter32
  starMIPFAStatRegReqSentDeregResend Counter32
  starMIPFAStatRegRplSentMNTooDistant Counter32
  starMIPFAStatRegRplSentInvCOA Counter32
  starMIPFAStatRegRplSentHANetUnreach Counter32
  starMIPFAStatRegRplSentHAHostUnreach Counter32
  starMIPFAStatRegRplSentHAPortUnreach Counter32
  starMIPFAStatRegRplSentHAUnreach Counter32
  starMIPFAStatRegRplSentRegTimeout Counter32
  starMIPFAStatRegRplSentMissNAI Counter32
  starMIPFAStatRegRplSentMissHomeAgent Counter32
  starMIPFAStatRegRplSentMissHomeAddr Counter32
  starMIPFAStatRegRplSentUnknChallenge Counter32
  starMIPFAStatRegRplSentMissChallenge Counter32
  starMIPFAStatRegRplSentStaleChallenge Counter32
  starMIPFAStatRegRplSentBadReply Counter32

StarRPStatEntry  
SEQUENCE    
  starRPStatVpnID Gauge32
  starRPStatSvcID StarShortID
  starRPStatVpnName DisplayString
  starRPStatServName DisplayString
  starRPRegRecvTotal Counter32
  starRPRegAcceptTotal Counter32
  starRPRegDeniedTotal Counter32
  starRPRegDiscardTotal Counter32
  starRPRegAcceptInitial Counter32
  starRPRegAcceptIntraPDSN Counter32
  starRPRegAcceptInterPDSN Counter32
  starRPRegDeniedInitial Counter32
  starRPRegAcceptRenew Counter32
  starRPRegDeniedRenew Counter32
  starRPRegAcceptDereg Counter32
  starRPRegDeniedDereg Counter32
  starRPRegSendError Counter32
  starRPRegHashError Counter32
  starRPRegDecodeError Counter32
  starRPRegUnhandled Counter32
  starRPRegAirlinkSeqError Counter32
  starRPRegDenyUnspec Counter32
  starRPRegDenyAdminProhib Counter32
  starRPRegDenyNoResource Counter32
  starRPRegDenyAuth Counter32
  starRPRegDenyMismatchID Counter32
  starRPRegDenyBadRequest Counter32
  starRPRegDenyUnknownPDSN Counter32
  starRPRegDenyRevTunUnav Counter32
  starRPRegDenyRevTunReq Counter32
  starRPRegDenyUnrecogVend Counter32
  starRPRegUpdTotal Counter32
  starRPRegUpdAccept Counter32
  starRPRegUpdDenied Counter32
  starRPRegUpdUnack Counter32
  starRPRegUpdTrans Counter32
  starRPRegUpdRetrans Counter32
  starRPRegUpdReceived Counter32
  starRPRegUpdDiscard Counter32
  starRPRegUpdSendError Counter32
  starRPRegUpdUplyrInit Counter32
  starRPRegUpdOther Counter32
  starRPRegUpdHandoff Counter32
  starRPRegUpdDenyUnspec Counter32
  starRPRegUpdDenyAdminProhib Counter32
  starRPRegUpdDenyAuth Counter32
  starRPRegUpdDenyMismatchID Counter32
  starRPRegUpdDenyBadRequest Counter32
  starRPSecViolations Counter32
  starRPSecBadAuth Counter32
  starRPSecBadID Counter32
  starRPSecBadSpi Counter32
  starRPSecMissingMnHAAuth Counter32
  starRPSecMissingRegUpdate Counter32
  starRPRegRecvInitial Counter32
  starRPRegAcceptActvStartIntraPDSN Counter32
  starRPRegAcceptActvStopIntraPDSN Counter32
  starRPRegRecvRenew Counter32
  starRPRegActvStartRenew Counter32
  starRPRegActvStopRenew Counter32
  starRPRegRecvDereg Counter32
  starRPRegAcceptActvStopDereg Counter32
  starRPDiscSessAbsent Counter32
  starRPDiscNoMemory Counter32
  starRPDiscMalformed Counter32
  starRPDiscAuthFail Counter32
  starRPDiscInternalBounce Counter32
  starRPDiscInpuQueueExceeded Counter32
  starRPDiscMismatchedId Counter32
  starRPDiscInvPacketLen Counter32
  starRPDiscMisc Counter32
  starRP1xTxBytes Counter32
  starRP1xRxBytes Counter32
  starRP1xTxPackets Counter32
  starRP1xRxPackets Counter32
  starRPDoTxBytes Counter32
  starRPDoRxBytes Counter32
  starRPDoTxPackets Counter32
  starRPDoRxPackets Counter32

StarSubEntry  
SEQUENCE    
  starSubContext DisplayString
  starSubMSID OCTET STRING
  starSubName OCTET STRING
  starSubTimerDuration Unsigned32
  starSubLongDurTimeoutAction INTEGER
  starSubSetupTime DateAndTime
  starSubHomeAddr IpAddress
  starSubHomeAddrv6 Ipv6Address

StarEISServerEntry  
SEQUENCE    
  starEISServerVPNID Gauge32
  starEISServerAddr IpAddress
  starEISServerVPNName DisplayString

StarPortEntry  
SEQUENCE    
  starPortSlot Integer32
  starPortNum Integer32
  starPortType INTEGER
  starPortTypeDescr DisplayString
  starPortAdminState INTEGER
  starPortOperState INTEGER
  starPortOperMode INTEGER
  starPortLinkState INTEGER
  starRedundantPortSlot Integer32
  starRedundantPortNum Integer32
  starPortRxBytes Counter32
  starPortTxBytes Counter32
  starPortRxFrames Counter32
  starPortTxFrames Counter32
  starPortRxDiscards Counter32
  starPortTxDiscards Counter32
  starPortRxErrors Counter32
  starPortTxErrors Counter32

StarIPPoolEntry  
SEQUENCE    
  starIPPoolVpnID Gauge32
  starIPPoolID StarMediumID
  starIPPoolContext DisplayString
  starIPPoolGroup DisplayString
  starIPPoolName OCTET STRING
  starIPPoolType INTEGER
  starIPPoolState INTEGER
  starIPPoolStartAddr IpAddress
  starIPPoolMaskorEndAddr IpAddress
  starIPPoolPriority Integer32
  starIPPoolUsed Gauge32
  starIPPoolHold Gauge32
  starIPPoolRelease Gauge32
  starIPPoolFree Gauge32

StarIPPoolGroupEntry  
SEQUENCE    
  starIPPoolGroupVpnID Gauge32
  starIPPoolGroupID StarMediumID
  starIPPoolGroupName DisplayString
  starIPPoolGroupVpnName DisplayString
  starIPPoolGroupUsed Gauge32
  starIPPoolGroupHold Gauge32
  starIPPoolGroupRelease Gauge32
  starIPPoolGroupFree Gauge32
  starIPPoolGroupPctUsed Integer32
  starIPPoolGroupAvail Gauge32

StarL2TPEntry  
SEQUENCE    
  starL2TPLocalTunnelID Unsigned32
  starL2TPPeerTunnelID Unsigned32
  starL2TPContextName DisplayString
  starL2TPServiceName DisplayString
  starL2TPServiceTypeName DisplayString
  starL2TPLocalAddress IpAddress
  starL2TPPeerAddress IpAddress

StarGGSNSerEntry  
SEQUENCE    
  starGGSNSerVpnID Gauge32
  starGGSNSerSvcID Gauge32
  starSessGGSNVpnName DisplayString
  starSessGGSNServName DisplayString
  starSessGGSNPeerPort Gauge32
  starSessGGSNPeerAddr IpAddress
  starSessGGSNImsi OCTET STRING
  starSessGGSNSubsName OCTET STRING
  starSessGGSNAPNName OCTET STRING
  starSessGTPPGroupName OCTET STRING

StarNwReachEntry  
SEQUENCE    
  starNwReachName OCTET STRING
  starNwReachSrvrAddr IpAddress

StarSIPRouteEntry  
SEQUENCE    
  starSIPRouteVpnID Gauge32
  starSIPRouteVpnName DisplayString
  starSIPRouteVmgName DisplayString
  starSIPRouteAsName DisplayString
  starSIPRouteDestPartyNum DisplayString
  starSIPRouteReqNum DisplayString

StarRPServiceOptionEntry  
SEQUENCE    
  starRPServiceOptionNum Integer32
  starRPServiceOptionCalls Gauge32

StarPCFStatEntry  
SEQUENCE    
  starPCFStatVpnID Gauge32
  starPCFStatIpAddr IpAddress
  starPCFStatVpnName DisplayString
  starPCFStatRxPkts Counter32
  starPCFStatTxPkts Counter32
  starPCFStatRxBytes Counter32
  starPCFStatTxBytes Counter32
  starPCFStatTotalSessions Counter32
  starPCFStatCurrentSessions Gauge32
  starPCFStatCurrentActiveSessions Gauge32
  starPCFStatCurrentDormantSessions Gauge32
  starPCFStatCurrentSIPConnected Gauge32
  starPCFStatCurrentMIPConnected Gauge32
  starPCFStatCurrentPMIPConnected Gauge32
  starPCFStatCurrentL2TPLACConnected Gauge32
  starPCFStatCurrentOtherConnected Gauge32

StarPCFEntry  
SEQUENCE    
  starPCFSvcID StarShortID
  starPCFIpAddr IpAddress
  starPCFVpnID Gauge32
  starPCFVpnName DisplayString
  starPCFServName DisplayString
  starPCFRrqRcvd Counter32
  starPCFRrqAccepted Counter32
  starPCFRrqDenied Counter32
  starPCFRrqDiscarded Counter32
  starPCFInitialRrqRcvd Counter32
  starPCFInitialRrqAccepted Counter32
  starPCFIntraPDSNActiveHORrqAccepted Counter32
  starPCFIntraPDSNDormantHORrqAccepted Counter32
  starPCFInterPDSNHORrqAccepted Counter32
  starPCFInitialRrqDenied Counter32
  starPCFInitialRrqDiscarded Counter32
  starPCFRenewRrqRcvd Counter32
  starPCFRenewRrqAccepted Counter32
  starPCFRenewActiveRrqAccepted Counter32
  starPCFRenewDormantRrqAccepted Counter32
  starPCFRenewRrqDenied Counter32
  starPCFRenewRrqDiscarded Counter32
  starPCFDeregRrqRcvd Counter32
  starPCFDeregRrqAccepted Counter32
  starPCFDeregDormantRrqAccepted Counter32
  starPCFDeregRrqDenied Counter32
  starPCFDeregRrqDiscarded Counter32
  starPCFIntraPDSNActiveAnidHORrqAccepted Counter32
  starPCFIntraPDSNDormantAnidHORrqAccepted Counter32
  starPCFDeniedUnSpeReason Counter32
  starPCFDeniedAdmProh Counter32
  starPCFDeniedInsufResource Counter32
  starPCFDeniedMobNodeAuthFail Counter32
  starPCFDeniedIdentMismatch Counter32
  starPCFDeniedPoorFormedReq Counter32
  starPCFDeniedUnknownPDSNAddr Counter32
  starPCFDeniedRevTunnelUnavail Counter32
  starPCFDeniedRevTunnelRequire Counter32
  starPCFDeniedUnrecogVendorId Counter32
  starPCFDeniedSessionClosed Counter32
  starPCFDeniedBsnSessionInfoUnavail Counter32
  starPCFRegUpdTransmitted Counter32
  starPCFRegUpdAccepted Counter32
  starPCFRegUpdateRpLifetimeExpiry Counter32
  starPCFRegUpdateUpperLayerIntiated Counter32
  starPCFRegUpdateOtherReason Counter32
  starPCFRegUpdateHORelease Counter32
  starPCFRegUpdateSessmgrDied Counter32
  starPCFAuxA10ConnectionsSetup Counter32
  starPCFSessionsDenied Counter32
  starPCFSessionsInit Counter32
  starPCFSessionsReneg Counter32
  starPCFDiscLcpRemote Counter32
  starPCFDiscRpRemote Counter32
  starPCFDiscRpLocal Counter32
  starPCFDiscMaxIpcpRetr Counter32
  starPCFDiscMaxIpv6cpRetr Counter32
  starPCFDiscMaxLcpRetr Counter32
  starPCFDiscAuthFail Counter32
  starPCFDiscSessSetupTimeout Counter32
  starPCFDiscFlowAddFail Counter32
  starPCFDiscInvDestContext Counter32
  starPCFDiscLcpOptFail Counter32
  starPCFDiscIpcpOptFail Counter32
  starPCFDiscIpv6cpOptFail Counter32
  starPCFDiscNoRemIpAddr Counter32
  starPCFDiscDetectionFail Counter32
  starPCFDiscMisc Counter32
  starPCFCurrentSessions Gauge32
  starPCFSessionsSetup Counter32
  starPCFSessionsRelsese Counter32
  starPCFCurrentRevaSessions Gauge32
  starPCFRevaSessionsSetup Counter32
  starPCFRevaSessionsRelsese Counter32

StarSIPRouteServerEntry  
SEQUENCE    
  starSIPRouteServerVpnID Gauge32
  starSIPRouteServerVpnName DisplayString
  starSIPRouteServerVmgName DisplayString
  starSIPRouteServerAsName DisplayString
  starSIPRouteServerIpAddr IpAddress

StarVIMServiceEntry  
SEQUENCE    
  starVIMServiceVpnID Gauge32
  starVIMServiceVpnName DisplayString
  starVIMServiceInstanceId Unsigned32
  starVIMServiceFMDMaxCallRate Unsigned32
  starVIMServiceFMDContinuousLoadCount Unsigned32

StarPDIFEntry  
SEQUENCE    
  starPDIFSvcID StarShortID
  starPDIFVpnID Gauge32
  starPDIFVpnName DisplayString
  starPDIFServName DisplayString
  starPDIFStatus INTEGER
  starPDIFSessCurrent Gauge32
  starPDIFSessRemain Gauge32
  starPDIFSessCurrentActive Gauge32
  starPDIFSessCurrentDormant Gauge32
  starPDIFSessCurrentIpv6Active Gauge32
  starPDIFSessCurrentIpv6Dormant Gauge32
  starPDIFSessCurrentIpv4Active Gauge32
  starPDIFSessCurrentIpv4Dormant Gauge32
  starPDIFBindIpAddress IpAddress
  starPDIFBindIpPort Integer32
  starPDIFBindSlot Integer32
  starPDIFBindPort Integer32

StarPDGEntry  
SEQUENCE    
  starPDGSvcID StarShortID
  starPDGVpnID Gauge32
  starPDGVpnName DisplayString
  starPDGServName DisplayString
  starPDGStatus INTEGER
  starPDGSessCurrent Gauge32
  starPDGSessRemain Gauge32
  starPDGSessCurrentActive Gauge32
  starPDGSessCurrentDormant Gauge32
  starPDGSessCurrentIpv6Active Gauge32
  starPDGSessCurrentIpv6Dormant Gauge32
  starPDGSessCurrentIpv4Active Gauge32
  starPDGSessCurrentIpv4Dormant Gauge32
  starPDGBindIpAddress IpAddress
  starPDGBindIpPort Integer32
  starPDGBindSlot Integer32
  starPDGBindPort Integer32

StarHNBGWServEntry  
SEQUENCE    
  starHNBGWServVpnID Gauge32
  starHNBGWServSvcID Gauge32
  starSessHNBGWVpnName DisplayString
  starSessHNBGWServName DisplayString
  starSessHNBGWCsNwName DisplayString
  starSessHNBGWPsNwName DisplayString
  starSessHNBGWSgsnPtCd Integer32
  starSessHNBGWMscPtCd Integer32

StarALCAPServEntry  
SEQUENCE    
  starALCAPSerVpnID Gauge32
  starALCAPSerSvcID Gauge32
  starSessALCAPVpnName DisplayString
  starSessALCAPServName DisplayString
  starSessALCAPAAL2NodeName DisplayString
  starSessALCAPPathId Integer32

StarFNGEntry  
SEQUENCE    
  starFNGSvcID StarShortID
  starFNGVpnID Gauge32
  starFNGVpnName DisplayString
  starFNGServName DisplayString
  starFNGStatus INTEGER
  starFNGSessCurrent Gauge32
  starFNGSessRemain Gauge32
  starFNGSessCurrentActive Gauge32
  starFNGSessCurrentDormant Gauge32
  starFNGSessCurrentIpv6Active Gauge32
  starFNGSessCurrentIpv6Dormant Gauge32
  starFNGSessCurrentIpv4Active Gauge32
  starFNGSessCurrentIpv4Dormant Gauge32
  starFNGBindIpAddress IpAddress
  starFNGBindIpPort Integer32
  starFNGBindSlot Integer32
  starFNGBindPort Integer32

StarSGSNSerEntry  
SEQUENCE    
  starSGSNSerVpnID Gauge32
  starSGSNSerSvcID Gauge32
  starSessSGSNVpnName DisplayString
  starSessSGSNServName DisplayString
  starSessSGSNMcc OCTET STRING
  starSessSGSNMnc OCTET STRING
  starSessSGSNRncId Gauge32
  starSessSGSNHlrNum OCTET STRING

StarSS7RdEntry  
SEQUENCE    
  starSS7rdId Gauge32
  starSS7Pc Gauge32
  starSS7M3UAPsId Gauge32
  starSS7M3UAPspId Gauge32
  starSS7MTP3LinkSetId Gauge32
  starSS7MTP3LinkId Gauge32
  starSS7SCTPSelfAddr IpAddress
  starSS7SCTPPeerAddr IpAddress
  starSS7SCTPSelfPort Gauge32
  starSS7SCTPPeerPort Gauge32
  starSS7CongLevel Gauge32
  starSS7LocalCong Gauge32
  starSS7CauseString DisplayString

StarSccpNwEntry  
SEQUENCE    
  starSccpNwId Gauge32
  starSccpSsn Gauge32

StarSGTPSerEntry  
SEQUENCE    
  starSGTPSerVpnID Gauge32
  starSGTPSerSvcID Gauge32
  starSGTPVpnName DisplayString
  starSGTPServName DisplayString
  starSGTPSelfAddr IpAddress
  starSGTPPeerAddr IpAddress
  starSGTPSelfPort Gauge32
  starSGTPPeerPort Gauge32

StarIPMSServerEntry  
SEQUENCE    
  starIPMSServerVpnID Gauge32
  starIPMSServerAddr IpAddress
  starIPMSServerVpnName DisplayString

StarCertEntry  
SEQUENCE    
  starCertSerialNumber DisplayString
  starCertExpiryTime DateAndTime
  starCertIssuer DisplayString

StarFileEntry  
SEQUENCE    
  starFileName DisplayString
  starFileApplication INTEGER

StarFTPServEntry  
SEQUENCE    
  starFTPServVpnID Unsigned32
  starFTPServIpAddr IpAddress
  starFTPServVpnName DisplayString

StarCSCFPeerServerEntry  
SEQUENCE    
  starCSCFPeerServerVpnID Gauge32
  starCSCFPeerServerSvcID Gauge32
  starCSCFPeerServerVpnName DisplayString
  starCSCFPeerServerSvcName DisplayString
  starCSCFPeerServerListName DisplayString
  starCSCFPeerServerName DisplayString
  starCSCFPeerServerState DisplayString

StarSDHEntry  
SEQUENCE    
  starSDHSlot Integer32
  starSDHPort Integer32
  starSDHOperState Integer32

StarSDHPathEntry  
SEQUENCE    
  starSDHPathSlot Integer32
  starSDHPathPort Integer32
  starSDHPathNum Integer32
  starSDHPathOperState Integer32

StarE1TribEntry  
SEQUENCE    
  starE1TribSlot Integer32
  starE1TribPort Integer32
  starE1TribPath Integer32
  starE1TribTug2 Integer32
  starE1TribTu12 Integer32
  starE1TribOperStateLOP Integer32
  starE1TribOperState Integer32

StarFractE1TribEntry  
SEQUENCE    
  starFractE1TribSlot Integer32
  starFractE1TribPort Integer32
  starFractE1TribPath Integer32
  starFractE1TribTug2 Integer32
  starFractE1TribTu12 Integer32
  starFractE1TribBundNum Integer32
  starFractE1TribTimeslots DisplayString

StarGPRSLinkEntry  
SEQUENCE    
  starGPRSNsei Gauge32
  starGPRSNsvci Gauge32
  starGPRSBvci Gauge32

StarStorageEntry  
SEQUENCE    
  starStorageSlot Integer32
  starStorageName DisplayString
  starStorageDeviceType INTEGER

StarMMES1AssocEntry  
SEQUENCE    
  starMMES1AssocSvcID StarMediumID
  starMMES1AssocENBID StarENBID
  starMMES1AssocVpnName DisplayString
  starMMES1AssocServName DisplayString

StarMMES1PathEntry  
SEQUENCE    
  starMMES1PathSvcID StarMediumID
  starMMES1PathENBID StarENBID
  starMMES1PathVpnName DisplayString
  starMMES1PathServName DisplayString
  starMMES1PathSelfAddr IpAddress
  starMMES1PathSelfPort Gauge32
  starMMES1PathPeerAddr IpAddress
  starMMES1PathPeerPort Gauge32

Defined Values

starentMIB 1.1.8164
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.
MODULE-IDENTITY    

starentMIBObjects 1.1.8164.1
OBJECT IDENTIFIER    

starentChassis 1.1.8164.1.1
OBJECT IDENTIFIER    

starChassisCriticalCO 1.1.8164.1.1.1
The current state of the Critical Central Office (CO) relay
Status: current Access: read-only
OBJECT-TYPE    
  StarRelayState  

starChassisMajorCO 1.1.8164.1.1.2
The current state of the Major Central Office (CO) relay
Status: current Access: read-only
OBJECT-TYPE    
  StarRelayState  

starChassisMinorCO 1.1.8164.1.1.3
The current state of the Minor Central Office (CO) relay
Status: current Access: read-only
OBJECT-TYPE    
  StarRelayState  

starChassisAction 1.1.8164.1.1.5
Trigger 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.
Status: current Access: read-write
OBJECT-TYPE    
  INTEGER noaction(1), aco(2), reset(3)  

starTimeTicks 1.1.8164.1.1.6
Time ticks since the Epoch
Status: current Access: read-only
OBJECT-TYPE    
  Unsigned32  

starChassisAudibleAlarm 1.1.8164.1.1.7
The current state of the chassis Audible Alarm
Status: current Access: read-only
OBJECT-TYPE    
  StarRelayState  

starChassisUTCTime 1.1.8164.1.1.8
The current time on the chassis, in UTC format
Status: current Access: read-only
OBJECT-TYPE    
  DateAndTime  

starChassisLocalTime 1.1.8164.1.1.9
The current time on the chassis, converted to the local timezone
Status: current Access: read-only
OBJECT-TYPE    
  DateAndTime  

starChassisType 1.1.8164.1.1.10
The type of physical chassis
Status: current Access: read-only
OBJECT-TYPE    
  INTEGER unknown(0), st16(1), st40(2), xt2(3), st20(4), asr5000(5), asr5500(6), ssi(7), ssi-kvm-guest(8), ssi-kvm-vsm-guest(9), qvpc-di(10)  

starChassisDescription 1.1.8164.1.1.11
A brief description of the chassis
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

starChassisSWRevision 1.1.8164.1.1.12
The software revision running on the chassis
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

starChassisPeakCpuUsage 1.1.8164.1.1.13
Percentage of the system level peak cpu usage.starChassisPeakCpuUsage is the percentage value times 100; for example,2.3% would be represented as 230
Status: current Access: read-only
OBJECT-TYPE    
  Integer32 1..10000  

starChassisPeakMemoryUsage 1.1.8164.1.1.14
The system level peak memory usage, in kilobytes, rounded down (i.e. 1023 bytes = 0 kilobytes)
Status: current Access: read-only
OBJECT-TYPE    
  Integer32 1..2097152  

starentSlots 1.1.8164.1.2
OBJECT IDENTIFIER    

starSlotTable 1.1.8164.1.2.1
A table containing information on all of the slots
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    StarSlotEntry

starSlotEntry 1.1.8164.1.2.1.1
Information about a particular slot
Status: current Access: not-accessible
OBJECT-TYPE    
  StarSlotEntry  

starSlotNum 1.1.8164.1.2.1.1.1
The slot number
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Integer32 1..48  

starSlotType 1.1.8164.1.2.1.1.2
The type of the slot.
Status: current Access: read-only
OBJECT-TYPE    
  StarentSlotType  

starCardType 1.1.8164.1.2.1.1.3
The type of the card which is plugged into a slot
Status: current Access: read-only
OBJECT-TYPE    
  StarentCardType  

starCardOperState 1.1.8164.1.2.1.1.4
The current operational state of the card
Status: current Access: read-only
OBJECT-TYPE    
  INTEGER unknown(1), empty(2), offline(3), booting(4), ready(5), standby(6), active(7), migratefrom(8), migrateto(9), starting(10), initializing(11), secondary(12)  

starCardAdminState 1.1.8164.1.2.1.1.5
The administrative state of the card
Status: current Access: read-only
OBJECT-TYPE    
  INTEGER unknown(1), enabled(2), disabled(3)  

starCardRevision 1.1.8164.1.2.1.1.6
The revision number of the card that is physically present in this slot
Status: current Access: read-only
OBJECT-TYPE    
  StarentVersionNum  

starCardLastStateChange 1.1.8164.1.2.1.1.7
The time when the last state change occurred for this row. A manager could poll this variable to determine if information has changed.
Status: current Access: read-only
OBJECT-TYPE    
  DateAndTime  

starCardMode 1.1.8164.1.2.1.1.8
The 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)
Status: current Access: read-only
OBJECT-TYPE    
  INTEGER unknown(1), notapplicable(2), standby(3), active(4), activepac(5), activetac(6), activepsc(7), activevpc(8), activedpc(9)  

starCardPacStandbyPriority 1.1.8164.1.2.1.1.9
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starCardHaltIssued 1.1.8164.1.2.1.1.10
Only applicable to SPC cards
Status: current Access: read-only
OBJECT-TYPE    
  INTEGER notapplicable(1), yes(2), no(3)  

starCardLock 1.1.8164.1.2.1.1.11
Identifies 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.
Status: current Access: read-only
OBJECT-TYPE    
  INTEGER unknown(1), locked(2), unlocked(3)  

starCardRebootPending 1.1.8164.1.2.1.1.12
Identifies if a reboot operation is currently pending for this card.
Status: current Access: read-only
OBJECT-TYPE    
  INTEGER no(1), yes(2)  

starCardUsable 1.1.8164.1.2.1.1.13
Identifies if the card is currently usable.
Status: current Access: read-only
OBJECT-TYPE    
  INTEGER no(1), yes(2)  

starCardSinglePOF 1.1.8164.1.2.1.1.14
Identifies 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.
Status: current Access: read-only
OBJECT-TYPE    
  INTEGER notapplicable(1), no(2), yes(3)  

starCardAttachment 1.1.8164.1.2.1.1.15
Identifies if the card is currently attached to another card (a PAC/PSC attached to a line card, or visa versa, for example
Status: current Access: read-only
OBJECT-TYPE    
  INTEGER connected(1), unconnected(2)  

starCardTemperature 1.1.8164.1.2.1.1.16
The 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 C
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starSlotVoltage1dot5 1.1.8164.1.2.1.1.20
The 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.
Status: obsolete Access: read-only
OBJECT-TYPE    
  Gauge32  

starSlotVoltage1dot5LowThresh 1.1.8164.1.2.1.1.21
The 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.
Status: obsolete Access: read-only
OBJECT-TYPE    
  Gauge32  

starSlotVoltage1dot5HighThresh 1.1.8164.1.2.1.1.22
The 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.
Status: obsolete Access: read-only
OBJECT-TYPE    
  Gauge32  

starSlotVoltage1dot8 1.1.8164.1.2.1.1.23
The 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.
Status: obsolete Access: read-only
OBJECT-TYPE    
  Gauge32  

starSlotVoltage1dot8LowThresh 1.1.8164.1.2.1.1.24
The 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.
Status: obsolete Access: read-only
OBJECT-TYPE    
  Gauge32  

starSlotVoltage1dot8HighThresh 1.1.8164.1.2.1.1.25
The 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.
Status: obsolete Access: read-only
OBJECT-TYPE    
  Gauge32  

starSlotVoltage2dot5 1.1.8164.1.2.1.1.26
The 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.
Status: obsolete Access: read-only
OBJECT-TYPE    
  Gauge32  

starSlotVoltage2dot5LowThresh 1.1.8164.1.2.1.1.27
The 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.
Status: obsolete Access: read-only
OBJECT-TYPE    
  Gauge32  

starSlotVoltage2dot5HighThresh 1.1.8164.1.2.1.1.28
The 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.
Status: obsolete Access: read-only
OBJECT-TYPE    
  Gauge32  

starSlotVoltage3dot3 1.1.8164.1.2.1.1.29
The 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.
Status: obsolete Access: read-only
OBJECT-TYPE    
  Gauge32  

starSlotVoltage3dot3LowThresh 1.1.8164.1.2.1.1.30
The 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.
Status: obsolete Access: read-only
OBJECT-TYPE    
  Gauge32  

starSlotVoltage3dot3HighThresh 1.1.8164.1.2.1.1.31
The 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.
Status: obsolete Access: read-only
OBJECT-TYPE    
  Gauge32  

starSlotVoltage5dot0 1.1.8164.1.2.1.1.32
The 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.
Status: obsolete Access: read-only
OBJECT-TYPE    
  Gauge32  

starSlotVoltage5dot0LowThresh 1.1.8164.1.2.1.1.33
The 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.
Status: obsolete Access: read-only
OBJECT-TYPE    
  Gauge32  

starSlotVoltage5dot0HighThresh 1.1.8164.1.2.1.1.34
The 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.
Status: obsolete Access: read-only
OBJECT-TYPE    
  Gauge32  

starSlotNumPorts 1.1.8164.1.2.1.1.35
Number 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.
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starSlotAction 1.1.8164.1.2.1.1.36
Trigger 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 reset
Status: current Access: read-write
OBJECT-TYPE    
  INTEGER noaction(1), reset(2)  

starSlotVoltageState 1.1.8164.1.2.1.1.37
The 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.
Status: current Access: read-only
OBJECT-TYPE    
  INTEGER unknown(0), normal(1), outofrange(2)  

starSlotNumCPU 1.1.8164.1.2.1.1.38
The number of general-purpose CPUs on this card
Status: current Access: read-only
OBJECT-TYPE    
  Integer32  

starSlotPartNumber 1.1.8164.1.2.1.1.39
The part number of this card
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

starSlotPartRevision 1.1.8164.1.2.1.1.40
The revision number of this card
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

starSlotSerialNumber 1.1.8164.1.2.1.1.41
The serial number of this card
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

starSlotCLEICode 1.1.8164.1.2.1.1.42
The CLEI code of this card
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

starSlotCiscoModelName 1.1.8164.1.2.1.1.43
Cisco-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.
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

starSlotCiscoHardwareRev 1.1.8164.1.2.1.1.44
Cisco-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.
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

starSlotCiscoSerialNumber 1.1.8164.1.2.1.1.45
Cisco-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.
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

starDeviceNum 1.1.8164.1.2.1.1.46
The device number
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Integer32 1..4  

starSerdesNum 1.1.8164.1.2.1.1.47
The serdes lane index number
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Integer32 0..127  

starentSlotMapping 1.1.8164.1.3
OBJECT IDENTIFIER    

starSlotMappingTable 1.1.8164.1.3.1
A table identifying all of the slot mappings. This table is applicable only to starChassisType ASR5000 platform.
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    StarSlotMappingEntry

starSlotMappingEntry 1.1.8164.1.3.1.1
Information about a particular slot mapping
Status: current Access: not-accessible
OBJECT-TYPE    
  StarSlotMappingEntry  

starSlotMappingNum 1.1.8164.1.3.1.1.1
The slot number. This always represents a slot in the back of the chassis.
Status: current Access: not-accessible
OBJECT-TYPE    
  Integer32 17..48  

starSlotMappingType 1.1.8164.1.3.1.1.2
The 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.
Status: current Access: read-only
OBJECT-TYPE    
  INTEGER unknown(1), none(2), direct(3), rcc(4), cross(5)  

starSlotMappingRCCNum 1.1.8164.1.3.1.1.3
Identifies which RCC card is responsible for this mapping. This value is only valid if the value of starSlotMappingType is rcc(3).
Status: current Access: read-only
OBJECT-TYPE    
  Integer32 0..2  

starSlotMappingToSlot 1.1.8164.1.3.1.1.4
The slot number this slot is mapped to. This always represents a slot in the front of the chassis
Status: current Access: read-only
OBJECT-TYPE    
  Integer32 1..16  

starentFans 1.1.8164.1.4
OBJECT IDENTIFIER    

starFanTable 1.1.8164.1.4.1
A table containing information on all of the fan controllers
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    StarFanEntry

starFanEntry 1.1.8164.1.4.1.1
Information about a particular fan controller
Status: current Access: not-accessible
OBJECT-TYPE    
  StarFanEntry  

starFanNum 1.1.8164.1.4.1.1.1
The fan controller number
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Integer32 1..4  

starFanLocation 1.1.8164.1.4.1.1.2
The physical location of the fan controller
Status: current Access: read-only
OBJECT-TYPE    
  INTEGER upper(1), lower(2), lowerFront(3), lowerRear(4), upperFront(5), upperRear(6)  

starFanStatus 1.1.8164.1.4.1.1.3
A 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)
Status: current Access: read-only
OBJECT-TYPE    
  Integer32  

starFanSpeed 1.1.8164.1.4.1.1.4
The 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)
Status: current Access: read-only
OBJECT-TYPE    
  INTEGER unknown(1), speed50(2), speed55(3), speed60(4), speed65(5), speed70(6), speed75(7), speed80(8), speed85(9), speed90(10), speed95(11), speed100(12)  

starentLogs 1.1.8164.1.5
OBJECT IDENTIFIER    

starLogTable 1.1.8164.1.5.1
A table containing information about all of the system logs
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    StarLogEntry

starLogEntry 1.1.8164.1.5.1.1
Information about a particular system log
Status: current Access: not-accessible
OBJECT-TYPE    
  StarLogEntry  

starLogName 1.1.8164.1.5.1.1.1
The name of the system log
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  StarShortName  

starLogCurSize 1.1.8164.1.5.1.1.2
The size, in bytes, of this log
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starLogMaxSize 1.1.8164.1.5.1.1.3
The maximum size, in bytes, of this log
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starLogText 1.1.8164.1.5.1.1.4
For use in LogMsg trap
Status: current Access: read-only
OBJECT-TYPE    
  OCTET STRING Size(1..512)  

starentAlertMan 1.1.8164.1.8
OBJECT IDENTIFIER    

starentFeedback 1.1.8164.1.8.1
OBJECT IDENTIFIER    

starMaxAlertsPerTime 1.1.8164.1.8.1.1
The maximum number of SNMP Traps which will be sent within the time period specified by starWindowTime
Status: current Access: read-only
OBJECT-TYPE    
  Unsigned32  

starWindowTime 1.1.8164.1.8.1.2
The amount of time within which no more than starMaxAlertsPerTime SNMP Traps will be sent.
Status: current Access: read-only
OBJECT-TYPE    
  Unsigned32  

starAlertSendingEnabled 1.1.8164.1.8.1.3
Shows 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 generated
Status: current Access: read-only
OBJECT-TYPE    
  TruthValue  

starentPolledLog 1.1.8164.1.8.2
OBJECT IDENTIFIER    

starentPower 1.1.8164.1.9
OBJECT IDENTIFIER    

starPowerTable 1.1.8164.1.9.1
A table containing information about all power filters
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    StarPowerEntry

starPowerEntry 1.1.8164.1.9.1.1
Information about a particular power filter
Status: current Access: not-accessible
OBJECT-TYPE    
  StarPowerEntry  

starPowerNumber 1.1.8164.1.9.1.1.1
The identifying number for this power filter.
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  INTEGER powerA(1), powerB(2)  

starPowerState 1.1.8164.1.9.1.1.2
The 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.
Status: current Access: read-only
OBJECT-TYPE    
  INTEGER active(1), failed(2), notpresent(3)  

starentCPU 1.1.8164.1.10
OBJECT IDENTIFIER    

starCPUTable 1.1.8164.1.10.1
A table containing information about all CPUs
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    StarCPUEntry

starCPUEntry 1.1.8164.1.10.1.1
Information about a particular CPU
Status: current Access: not-accessible
OBJECT-TYPE    
  StarCPUEntry  

starCPUSlot 1.1.8164.1.10.1.1.1
The slot number of the card holding this CPU
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Integer32 1..48  

starCPUNumber 1.1.8164.1.10.1.1.2
The CPU number within this card. Numbers begin at 0.
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Integer32 0..3  

starCPUUser 1.1.8164.1.10.1.1.3
Percentage of the CPU spent running user processes. starCPUUser is the percentage value times 100; for example, 2.3% would be represented as 230.
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32 1..10000  

starCPUSystem 1.1.8164.1.10.1.1.4
Percentage of the CPU spent running system processes. starCPUSystem is the percentage value times 100; for example, 2.3% would be represented as 230.
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32 1..10000  

starCPUIdle 1.1.8164.1.10.1.1.6
Percentage of the CPU spent idle. starCPUIdle is the percentage value times 100; for example, 2.3% would be represented as 230.
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32 1..10000  

starCPUIO 1.1.8164.1.10.1.1.7
Percentage of the CPU spent running io processes. starCPUIo is the percentage value times 100; for example, 2.3% would be represented as 230.
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32 1..10000  

starCPUIRQ 1.1.8164.1.10.1.1.8
Percentage of the CPU spent running irq processes. starCPUIrq is the percentage value times 100; for example, 2.3% would be represented as 230.
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32 1..10000  

starCPULoad1Min 1.1.8164.1.10.1.1.11
The 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.
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32 1..10000  

starCPULoad5Min 1.1.8164.1.10.1.1.12
The 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.
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32 1..10000  

starCPULoad15Min 1.1.8164.1.10.1.1.13
The 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.
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32 1..10000  

starCPUMemTotal 1.1.8164.1.10.1.1.14
The total amount of memory dedicated to this CPU, in kilobytes
Status: current Access: read-only
OBJECT-TYPE    
  Integer32 1..2147483647  

starCPUMemUsed 1.1.8164.1.10.1.1.15
The total amount of memory consumed by this CPU, in kilobytes
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32 1..2147483647  

starCPUNumProcesses 1.1.8164.1.10.1.1.16
The total number of processes which exist on this CPU
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32 1..32768  

starCPUMemCached 1.1.8164.1.10.1.1.17
The total amount of memory consumed by the (reusable) memory cache on this CPU, in kilobytes
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32 1..2147483647  

starentSessInP 1.1.8164.1.12
OBJECT IDENTIFIER    

starSessInProgCalls 1.1.8164.1.12.1
The number of sessions current in progress
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starSessInProgActiveCalls 1.1.8164.1.12.2
The number of sessions with active calls
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starSessInProgDormantCalls 1.1.8164.1.12.3
The number of sessions assocated with dormant calls
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starSessInProgArrived 1.1.8164.1.12.4
The number of sessions in the arrived state
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starSessInProgLCPNeg 1.1.8164.1.12.5
The number of sessions in the link control protocol negotiation state
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starSessInProgLCPUp 1.1.8164.1.12.6
The number of sessions in the link control protocol up state
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starSessInProgAuthenticating 1.1.8164.1.12.7
The number of sessions in the authenticating state
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starSessInProgAuthenticated 1.1.8164.1.12.8
The number of sessions in the authenticated state
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starSessInProgIPCPUp 1.1.8164.1.12.9
The number of sessions in the IP control protocol up state
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starSessInProgSIPConn 1.1.8164.1.12.10
The number of sessions in the Simple IP connected state
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starSessInProgMIPConn 1.1.8164.1.12.11
The number of sessions in the Mobile IP connected state
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starSessInProgDisc 1.1.8164.1.12.12
The number of sessions in the disconnecting state
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starentNPUMgr 1.1.8164.1.11
OBJECT IDENTIFIER    

starNPUMgrTable 1.1.8164.1.11.1
A table containing information about all NPU Managers
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    StarNPUMgrEntry

starNPUMgrEntry 1.1.8164.1.11.1.1
Information about a particular NPU Manager
Status: current Access: not-accessible
OBJECT-TYPE    
  StarNPUMgrEntry  

starNPUMgrNumber 1.1.8164.1.11.1.1.1
The identity of this NPU
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Integer32 1..65535  

starentSessMgr 1.1.8164.1.13
OBJECT IDENTIFIER    

starSessMgrCount 1.1.8164.1.13.1
The total number of session manager instances
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starSessTtlArrived 1.1.8164.1.13.2
The total number of requested sessions
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starSessTtlRejected 1.1.8164.1.13.3
The total number of rejected sessions
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starSessTtlConnected 1.1.8164.1.13.4
The total number of sessions which were connected
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starSessTtlAuthSucc 1.1.8164.1.13.5
The total number of sessions where authentication was successful
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starSessTtlAuthFail 1.1.8164.1.13.6
The total number of sessions which failed authentication
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starSessTtlLCPUp 1.1.8164.1.13.7
The total number of sessions in the link control protocol up state
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starSessTtlIPCPUp 1.1.8164.1.13.8
The total number of IP control protocol up state
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starSessTtlSrcViol 1.1.8164.1.13.9
The total number of sessions which had an invalid source
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starSessTtlKeepFail 1.1.8164.1.13.10
The total number of sessions which had a keep alive failure
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starSessTtlOctForwarded 1.1.8164.1.13.11
The total number of octets forwarded (data + control)
Status: deprecated Access: read-only
OBJECT-TYPE    
  Counter32  

starSessTtlRPRegAccept 1.1.8164.1.13.12
The total number of Initial RRQ Accepted
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starSessTtlRPRegAcceptInterPDSN 1.1.8164.1.13.13
The total number of Inter PDSN Handoff RRQ Accepted
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starSessCurrPPPSessions 1.1.8164.1.13.14
The current number of PPP sessions
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starSessTtlTxBytes 1.1.8164.1.13.15
The total number of bytes transmitted from mobiles
Status: deprecated Access: read-only
OBJECT-TYPE    
  Counter32  

starSessTtlRxBytes 1.1.8164.1.13.16
The total number of bytes received by mobiles
Status: deprecated Access: read-only
OBJECT-TYPE    
  Counter32  

starSessTtlSIPTxBytes 1.1.8164.1.13.17
The total number of bytes transmitted from mobiles using SIP
Status: deprecated Access: read-only
OBJECT-TYPE    
  Counter32  

starSessTtlSIPRxBytes 1.1.8164.1.13.18
The total number of bytes received by mobiles using SIP
Status: deprecated Access: read-only
OBJECT-TYPE    
  Counter32  

starSessTtlMIPTxBytes 1.1.8164.1.13.19
The total number of bytes transmitted from mobiles using MIP
Status: deprecated Access: read-only
OBJECT-TYPE    
  Counter32  

starSessTtlMIPRxBytes 1.1.8164.1.13.20
The total number of bytes received by mobiles using MIP
Status: deprecated Access: read-only
OBJECT-TYPE    
  Counter32  

starSessTtlOctForwardedGB 1.1.8164.1.13.21
The total number of octets forwarded (data + control)
Status: deprecated Access: read-only
OBJECT-TYPE    
  Counter32  

starSessTtlOctForwardedRev1 1.1.8164.1.13.22
The total number of octets forwarded (data + control). This object deprecates the old starSessTtlOctForwarded object.
Status: current Access: read-only
OBJECT-TYPE    
  Counter64  

starSessTtlTxBytesRev1 1.1.8164.1.13.23
The total number of bytes transmitted from mobiles. This object deprecates the old starSessTtlTxBytes object.
Status: current Access: read-only
OBJECT-TYPE    
  Counter64  

starSessTtlRxBytesRev1 1.1.8164.1.13.24
The total number of bytes received by mobiles. This object deprecates the old starSessTtlRxBytes object.
Status: current Access: read-only
OBJECT-TYPE    
  Counter64  

starSessTtlSIPTxBytesRev1 1.1.8164.1.13.25
The total number of bytes transmitted from mobiles using SIP. This object deprecates the old starSessTtlSIPTxBytes object.
Status: current Access: read-only
OBJECT-TYPE    
  Counter64  

starSessTtlSIPRxBytesRev1 1.1.8164.1.13.26
The total number of bytes received by mobiles using SIP. This object deprecates the old starSessTtlSIPRxBytes object.
Status: current Access: read-only
OBJECT-TYPE    
  Counter64  

starSessTtlMIPTxBytesRev1 1.1.8164.1.13.27
The total number of bytes transmitted from mobiles using MIP. This object deprecates the old starSessTtlMIPTxBytes object.
Status: current Access: read-only
OBJECT-TYPE    
  Counter64  

starSessTtlMIPRxBytesRev1 1.1.8164.1.13.28
The total number of bytes received by mobiles using MIP. This object deprecates the old starSessTtlMIPRxBytes object.
Status: current Access: read-only
OBJECT-TYPE    
  Counter64  

starSessTtlOctForwardedGBRev1 1.1.8164.1.13.29
The total number of octets forwarded (data + control). This object deprecates the old starSessTtlOctForwardedGB object.
Status: current Access: read-only
OBJECT-TYPE    
  Counter64  

starentAAAMgr 1.1.8164.1.14
OBJECT IDENTIFIER    

starAAAMgrCount 1.1.8164.1.14.1
The total number of AAA manager instances
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starAAATtlRequests 1.1.8164.1.14.2
The total number of AAA requests
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starAAATtlAuthRequests 1.1.8164.1.14.3
The total number of AAA authentication requests
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starAAATtlAcctRequests 1.1.8164.1.14.4
The total number of AAA accounting requests
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starAAACurRequests 1.1.8164.1.14.5
The current number of AAA requests
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starAAACurAuthRequests 1.1.8164.1.14.6
The current number of AAA authentication requests
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starAAACurAcctRequests 1.1.8164.1.14.7
The current number of AAA accounting requests
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starAAATtlAcctSess 1.1.8164.1.14.8
The total number of AAA accounting sessions
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starAAACurAcctSess 1.1.8164.1.14.9
The current number of AAA accounting sessions
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starAAATtlAuthSuccess 1.1.8164.1.14.10
The total number of AAA authentication successes
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starAAATtlAuthFailure 1.1.8164.1.14.11
The total number of AAA authentication failures
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starentA11Mgr 1.1.8164.1.15
OBJECT IDENTIFIER    

starA11MgrCount 1.1.8164.1.15.1
The total number of A11 manager instances
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starA11TtlArrived 1.1.8164.1.15.2
The total number of A11 session requests
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starA11TtlRejected 1.1.8164.1.15.3
The total number of rejected A11 sessions
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starA11TtlDemultiplexed 1.1.8164.1.15.4
The total number of demultiplexed A11 sessions
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starA11TtlDereg 1.1.8164.1.15.5
The total number of A11 deregistrations
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starA11CurActive 1.1.8164.1.15.6
The current number of active A11 sessions
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starentHAMgr 1.1.8164.1.16
OBJECT IDENTIFIER    

starHAMgrCount 1.1.8164.1.16.1
The total number of home agent manager instances
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starHATtlArrived 1.1.8164.1.16.2
The total number of home agent session requests
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starHATtlRejected 1.1.8164.1.16.3
The total number of rejected home agent sessions
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starHATtlDemultiplexed 1.1.8164.1.16.4
The total number of demultiplexed home agent sessions
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starHATtlDereg 1.1.8164.1.16.5
The total number of home agent deregistrations
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starHACurActive 1.1.8164.1.16.6
The total number of active home agent sessions
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starentFAMgr 1.1.8164.1.17
OBJECT IDENTIFIER    

starFAMgrCount 1.1.8164.1.17.1
The total number of foreign agent manager instances
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starFATtlArrived 1.1.8164.1.17.2
The total number of foreign agent session requests
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starFATtlRejected 1.1.8164.1.17.3
The total number of rejected foreign agent sessions
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starFATtlDemultiplexed 1.1.8164.1.17.4
The total number of demultiplexed foreign agent sessions
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starFATtlDereg 1.1.8164.1.17.5
The total number of foreign agent deregistrations
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starFACurActive 1.1.8164.1.17.6
The current number of active foreign agent sessions
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starentService 1.1.8164.1.18
OBJECT IDENTIFIER    

starServiceTable 1.1.8164.1.18.1
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    StarServiceEntry

starServiceEntry 1.1.8164.1.18.1.1
Information on a particular Service Manager
Status: current Access: not-accessible
OBJECT-TYPE    
  StarServiceEntry  

starServiceVpnID 1.1.8164.1.18.1.1.1
The internal identification of the VPN (context)
Status: current Access: not-accessible
OBJECT-TYPE    
  Gauge32  

starServiceSvcID 1.1.8164.1.18.1.1.2
The internal identification of this service; unique within a specific context
Status: current Access: not-accessible
OBJECT-TYPE    
  Gauge32  

starServiceVpnName 1.1.8164.1.18.1.1.3
The name of this VPN (context)
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

starServiceServName 1.1.8164.1.18.1.1.4
The name of this service
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

starServiceSubLimit 1.1.8164.1.18.1.1.5
The configured subscriber limit
Status: current Access: read-only
OBJECT-TYPE    
  Unsigned32  

starServiceSubCurrent 1.1.8164.1.18.1.1.6
The current number of subscribers limit
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starServiceType 1.1.8164.1.18.1.1.7
The type of service
Status: current Access: read-only
OBJECT-TYPE    
  INTEGER unknown(1), pdsn(2), ggsn(3), ha(4), fa(5), l2tpserver(6), lac(7), lns(8), closedrp(9), ecs(10), cscf(11), ipsg(12), evdoreva(13), asngw(14), pdif(15), asnpc(16), mipv6ha(17), phsgw(18), phspc(19), sgw(20), pgw(21), mag(22), gprs(23), hsgw(24), sgsn(25), mme(26), pdg(27), standalonefa(28), imsue(29), fng(30), pccpolicy(31), pccquota(32), pccaf(33), hnbgw(34), non-anchor-phs-gateway(35), combination-3g-4g-gateway(36), epdg(37), pcp(38), henbgw-access(39), henbgw-network(40), wsg(41), samog(42), saegw(43), ppp-lback(44), dhcp(45), imsa(46), diameter(47), dhcpv6(48), lma(49), crdt-ctl(50), mme-hss(51), sgs(52), cbs(53), egtp-ingress(54), egtp-egress(55), egtp(56), gtpu(57), sgtpc(58), egtp-sv(59), megad(60), pcc(61), ipne(62), mseg(63), bng(64), gs(65), map(66), iups(67), sgtp(68), lcs(69), mme-embms(70)  

starServiceFAIpAddr 1.1.8164.1.18.1.1.8
The IP address for an FA service. Where unknown or not applicable this will contain all zeroes.
Status: current Access: read-only
OBJECT-TYPE    
  IpAddress  

starServiceHAIpAddr 1.1.8164.1.18.1.1.9
The IP address for an HA service. Where unknown or not applicable this will contain all zeroes.
Status: current Access: read-only
OBJECT-TYPE    
  IpAddress  

starentCLIMgr 1.1.8164.1.19
OBJECT IDENTIFIER    

starCLITable 1.1.8164.1.19.1
A table containing information on all interactive CLI sessions
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    StarCLIEntry

starCLIEntry 1.1.8164.1.19.1.1
Information on a particular CLI Session
Status: current Access: not-accessible
OBJECT-TYPE    
  StarCLIEntry  

starCLIID 1.1.8164.1.19.1.1.1
The internal identifier of this CLI session.
Status: current Access: not-accessible
OBJECT-TYPE    
  Gauge32  

starCLIUsername 1.1.8164.1.19.1.1.2
The name of the user logged into this CLI session, or 'unknown' if not none
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

starCLITtyname 1.1.8164.1.19.1.1.3
The name of the TTY device for this CLI session
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

starCLIPrivs 1.1.8164.1.19.1.1.4
The user presentable form of the privilege level of this CLI session
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

starCLIType 1.1.8164.1.19.1.1.5
The type of CLI; commandline(1) represents the normal interactive command line; ftp(2) represents an incoming FTP session
Status: current Access: read-only
OBJECT-TYPE    
  INTEGER unknown(0), commandline(1), ftp(2)  

starCLIRemoteIpAddrType 1.1.8164.1.19.1.1.6
The type of remote IP address used to access this CLI session.
Status: current Access: read-only
OBJECT-TYPE    
  InetAddressType  

starCLIRemoteIpAddr 1.1.8164.1.19.1.1.7
The remote IP address used to access this CLI session. Where unknown or not applicable (such as access through a serial port) this will be 0
Status: current Access: read-only
OBJECT-TYPE    
  InetAddress  

starCLIContext 1.1.8164.1.19.1.1.8
The context (VPN) currently being managed/viewed by the CLI session.
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

starCLIDatabaseUsername 1.1.8164.1.19.1.1.9
The username of the user record in the database which was acted upon by the CLI session
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

starentTaskMgr 1.1.8164.1.20
OBJECT IDENTIFIER    

starTaskTable 1.1.8164.1.20.1
A table containing information about all active tasks
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    StarTaskEntry

starTaskEntry 1.1.8164.1.20.1.1
Information on a particular Task
Status: current Access: not-accessible
OBJECT-TYPE    
  StarTaskEntry  

starTaskFacility 1.1.8164.1.20.1.1.1
The internal facility identifier
Status: current Access: not-accessible
OBJECT-TYPE    
  Unsigned32  

starTaskInstance 1.1.8164.1.20.1.1.2
The internal instance identifier which uniquely idenfies this task without a given facility
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Unsigned32  

starTaskFacilityName 1.1.8164.1.20.1.1.3
The name of the facility for this task
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

starTaskCard 1.1.8164.1.20.1.1.4
The slot number of the card where this task is running
Status: current Access: read-only
OBJECT-TYPE    
  Unsigned32  

starTaskCPU 1.1.8164.1.20.1.1.5
The CPU number where this task is running
Status: current Access: read-only
OBJECT-TYPE    
  Unsigned32  

starentPPP 1.1.8164.1.21
OBJECT IDENTIFIER    

starPPPStatTable 1.1.8164.1.21.1
A table containing PPP Stats
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    StarPPPStatEntry

starPPPStatEntry 1.1.8164.1.21.1.1
The statistics for an individual entry for a PPP context and service
Status: current Access: not-accessible
OBJECT-TYPE    
  StarPPPStatEntry  

starPPPStatVpnID 1.1.8164.1.21.1.1.1
The internal identification of the PPP VPN (context)
Status: current Access: not-accessible
OBJECT-TYPE    
  Gauge32  

starPPPStatSvcID 1.1.8164.1.21.1.1.2
The service identification is made up from first 8 chars of context name and first 8 chars of service name separated by (:)
Status: current Access: not-accessible
OBJECT-TYPE    
  StarShortID  

starPPPStatVpnName 1.1.8164.1.21.1.1.3
The name of the PPP VPN (context)
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

starPPPStatServName 1.1.8164.1.21.1.1.4
The name of the PPP service
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

starPPPStatInit 1.1.8164.1.21.1.1.5
The number of initialized PPP sessions for the associated VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPPPStatReneg 1.1.8164.1.21.1.1.6
The number of PPP session renegotiations for the associated VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPPPStatSuccess 1.1.8164.1.21.1.1.7
The number of PPP session negotiation successes for the associated VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPPPStatFailed 1.1.8164.1.21.1.1.8
The number of PPP session negotiation failures for the associated VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPPPStatReleased 1.1.8164.1.21.1.1.9
The number of PPP sessions released for the associated VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPPPStatReleasedLocal 1.1.8164.1.21.1.1.10
The number of PPP sessions where the release was initiated locally for the associated VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPPPStatReleasedRemote 1.1.8164.1.21.1.1.11
The number of PPP sessions where the release was initiated remotely for the associated VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPPPStatLcpFailMaxRetry 1.1.8164.1.21.1.1.12
The number of PPP sessions which failed to bring up the link control protocol due to excessive retries for the associated VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPPPStatLcpFailOption 1.1.8164.1.21.1.1.13
The number of PPP sessions which failed to bring up the link control protocol due to an invalid option being received for the associated VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPPPStatIpcpFailMaxRetry 1.1.8164.1.21.1.1.14
The number of PPP sessions which failed to start the IP control protocol due to excessive retries for the associated VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPPPStatIpcpFailOption 1.1.8164.1.21.1.1.15
The number of PPP sessions which failed to start the IP control protocol due to an invalid option being received for the associated VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPPPStatCcpFail 1.1.8164.1.21.1.1.16
The number of PPP sessions which failed to initialize the CCP
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPPPStatAuthFail 1.1.8164.1.21.1.1.17
The number of PPP sessions which failed authentication for the associated VPN
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPPPStatLcpEntered 1.1.8164.1.21.1.1.18
The number of PPP sessions which successfully initialized the link control protocol
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPPPStatAuthEntered 1.1.8164.1.21.1.1.19
The number of PPP sessions which were successfully authenticated
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPPPStatIpcpEntered 1.1.8164.1.21.1.1.20
The number of PPP sessions which successfully initialized the IP control protocol
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPPPStatRenegPdsn 1.1.8164.1.21.1.1.21
The number of PPP sessions which renegotiated the PDSN service access
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPPPStatRenegMobil 1.1.8164.1.21.1.1.22
The number of PPP sessions which renegotiated the Mobile IP service access
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPPPStatRenegAddrMismatch 1.1.8164.1.21.1.1.23
The number of PPP sessions which had an IP address mismatch during renegotiation
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPPPStatRenegOther 1.1.8164.1.21.1.1.24
The number of PPP sessions which failed renegotiation for reasons other than IP address mismatch
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPPPStatChapAuthAttempt 1.1.8164.1.21.1.1.25
The number of PPP CHAP authentication attempts for the associated VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPPPStatPapAuthAttempt 1.1.8164.1.21.1.1.26
The number of PPP PAP authentication attempts for the associated VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPPPStatMSChapAuthAttempt 1.1.8164.1.21.1.1.27
The number of PPP MSCHAP authentication attempts for the associated VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPPPStatChapAuthFail 1.1.8164.1.21.1.1.28
The number of PPP CHAP authentication attempt failures for the associated VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPPPStatPapAuthFail 1.1.8164.1.21.1.1.29
The number of PPP PAP authentication failures for the associated VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPPPStatMSChapAuthFail 1.1.8164.1.21.1.1.30
The number of PPP MSCHAP authentication failures for the associated VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPPPStatStacComp 1.1.8164.1.21.1.1.31
The number of PPP sessions which had STAC compression enabled for the associated VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPPPStatMppcComp 1.1.8164.1.21.1.1.32
The number of PPP sessions which had MPPC compression enabled for the associated VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPPPStatDeflComp 1.1.8164.1.21.1.1.33
The number of PPP sessions which had DEFLATE compression enabled for the associated VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPPPStatFscErrs 1.1.8164.1.21.1.1.34
The number of PPP forward sequence control errors in messaging
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPPPStatUnknProto 1.1.8164.1.21.1.1.35
The number of PPP sessions which failed due to an unknown protocol received for the associated VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPPPStatBadAddr 1.1.8164.1.21.1.1.36
The number of PPP sessions which failed due to a bad address being received for the associated VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPPPStatBadCtrl 1.1.8164.1.21.1.1.37
The number of PPP sessions in which a bad control sequence was received
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPPPStatVjComp 1.1.8164.1.21.1.1.38
The number of PPP sessions which had VJ header compression enabled for the associated VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPPPStatDiscLcpRemote 1.1.8164.1.21.1.1.39
The number of PPP sessions which were disconnected via the link control protocol from the remote end for the associated VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPPPStatDiscRpRemote 1.1.8164.1.21.1.1.40
The number of PPP sessions which were disconnected by the remote via the R-P interface for the associated VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPPPStatDiscAdmin 1.1.8164.1.21.1.1.41
The number of PPP sessions which were disconnected by a local administrator for the associated VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPPPStatDiscIdleTimeout 1.1.8164.1.21.1.1.42
The number of PPP sessions disconnected due to session idle timer expiration for the associated VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPPPStatDiscAbsTimeout 1.1.8164.1.21.1.1.43
The number of PPP sessions disconnected due to the session absolute timer expiration for the associated VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPPPStatDiscPPPKeepalive 1.1.8164.1.21.1.1.44
The number of PPP sessions disconnected due to PPP keep alive failure for the associated VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPPPStatDiscNoResource 1.1.8164.1.21.1.1.45
The number of PPP sessions disconnected due to local resource shortage for the associated VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPPPStatDiscMisc 1.1.8164.1.21.1.1.46
The number of PPP sessions disconnected due to any cause which does not match any other existing disconnect statistics for the associated VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPPPStatFailedReneg 1.1.8164.1.21.1.1.47
The number of failed PPP renegotiations the associated VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPPPStatLcpFailUnknown 1.1.8164.1.21.1.1.48
The number of failed PPP LCP that are due to unknown reasons for the associated VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPPPStatIpcpFailUnknown 1.1.8164.1.21.1.1.49
The number of failed PPP IPCP that are due to unknown reasons for the associated VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPPPStatAuthAbort 1.1.8164.1.21.1.1.50
The number of aborted PPP authentications for the associated VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPPPStatLowerLayerDisc 1.1.8164.1.21.1.1.51
The number of Failed PPP session due to RP disconnect for the associated VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPPPStatLcpSuccess 1.1.8164.1.21.1.1.52
The number of successful PPP LCPs for the associated VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPPPStatAuthSuccess 1.1.8164.1.21.1.1.53
The number of successful PPP authentications for the associated VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPPPStatRenegLowerLayerHandoff 1.1.8164.1.21.1.1.54
The number of PPP renigotiations for RP handoff for the associated VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPPPStatRenegParamUpdate 1.1.8164.1.21.1.1.55
The number of PPP renigotiations for parameter update for the associated VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPPPStatChapAuthSuccess 1.1.8164.1.21.1.1.56
The number of successful PPP CHAP authentications for the associated VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPPPStatPapAuthSuccess 1.1.8164.1.21.1.1.57
The number of successful PPP PAP authentications for the associated VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPPPStatMSChapAuthSuccess 1.1.8164.1.21.1.1.58
The number of successful PPP MSCHAP authentications for the associated VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPPPStatChapAuthAbort 1.1.8164.1.21.1.1.59
The number of aboted PPP CHAP authentications for the associated VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPPPStatPapAuthAbort 1.1.8164.1.21.1.1.60
The number of aboted PPP PAP authentications for the associated VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPPPStatMSChapAuthAbort 1.1.8164.1.21.1.1.61
The number of aboted PPP MSCHAP authentications for the associated VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPPPStatSessSkipAuth 1.1.8164.1.21.1.1.62
The number of PPP sessions that skipped authentications for the associated VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPPPStatNegComp 1.1.8164.1.21.1.1.63
The number of PPP sessions that negotiated compressions for the associated VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPPPStatCCPNegFailComp 1.1.8164.1.21.1.1.64
The number of PPP sessions that failed compression negotiation for the associated VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPPPStatDiscLocalLowerLayer 1.1.8164.1.21.1.1.65
The number of disconnected PPP sessions due to local RP disconnect for the associated VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPPPStatDiscAddFlowFail 1.1.8164.1.21.1.1.66
The number of disconnected PPP sessions due to failure in adding new flow for the associated VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPPPStatDiscMaxRetriesLCP 1.1.8164.1.21.1.1.67
The number of disconnected PPP sessions due to max retries for LCP for the associated VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPPPStatDiscMaxRetriesIPCP 1.1.8164.1.21.1.1.68
The number of disconnected PPP sessions due to max retries for IPCP for the associated VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPPPStatDiscMaxSetupTimer 1.1.8164.1.21.1.1.69
The number of disconnected PPP sessions due to max setup time out for the associated VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPPPStatDiscInvalidDestVpn 1.1.8164.1.21.1.1.70
The number of disconnected PPP sessions due to invalid destination VPN for the associated VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPPPStatDiscOptNegFailLCP 1.1.8164.1.21.1.1.71
The number of disconnected PPP sessions due to invalid destination VPN for the associated VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPPPStatDiscOptNegFailIPCP 1.1.8164.1.21.1.1.72
The number of disconnected PPP sessions due to failed IPCP option negotiation for the associated VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPPPStatDiscNoRemoteIpAddr 1.1.8164.1.21.1.1.73
The number of disconnected PPP sessions due to no remote ip address for the associated VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPPPStatDiscCallTypeDetectFail 1.1.8164.1.21.1.1.74
The number of disconnected PPP sessions due to failure detecting call type for the associated VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPPPStatDiscRemoteDiscUpLayer 1.1.8164.1.21.1.1.75
The number of disconnected PPP sessions due to failure detecting call type for the associated VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPPPStatDiscLongDuraTimeout 1.1.8164.1.21.1.1.76
The number of disconnected PPP sessions due to long duration time out for the associated VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPPPStatDiscAuthFail 1.1.8164.1.21.1.1.77
The number of disconnected PPP sessions due to failed authentication for the associated VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPPPStatLCPEchoTotalReq 1.1.8164.1.21.1.1.78
The total number of PPP LCP echo requests for the associated VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPPPStatLCPEchoReqResent 1.1.8164.1.21.1.1.79
The total number of PPP LCP echo requests resent for the associated VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPPPStatLCPEchoRepRecved 1.1.8164.1.21.1.1.80
The total number of PPP LCP echo replys received for the associated VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPPPStatLCPEchoReqTimeout 1.1.8164.1.21.1.1.81
The total number of PPP LCP echo requests time out for the associated VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPPPStatRecvErrBadCtrlField 1.1.8164.1.21.1.1.82
The total number of received PPP error due to bad control fields for the associated VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPPPStatRecvErrBadPacketLen 1.1.8164.1.21.1.1.83
The total number of received PPP error due to bad packet length for the associated VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPPPStatRemoteTerm 1.1.8164.1.21.1.1.84
The total number of PPP remote terminations for the associated VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPPPStatMiscFail 1.1.8164.1.21.1.1.85
The number of misc PPP failures for the associated VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starentMIPHA 1.1.8164.1.22
OBJECT IDENTIFIER    

starMIPHAStatTable 1.1.8164.1.22.1
A table containing MIP HA Stats
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    StarMIPHAStatEntry

starMIPHAStatEntry 1.1.8164.1.22.1.1
The Mobile IP home agent statistics for a specific VPN (context) and service
Status: current Access: not-accessible
OBJECT-TYPE    
  StarMIPHAStatEntry  

starMIPHAStatVpnID 1.1.8164.1.22.1.1.1
The internal identification of the home agent Mobile IP VPN (context)
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starMIPHAStatSvcID 1.1.8164.1.22.1.1.2
The service identification is made up from first 8 chars of context name and first 8 chars of service name separated by (:)
Status: current Access: not-accessible
OBJECT-TYPE    
  StarShortID  

starMIPHAStatVpnName 1.1.8164.1.22.1.1.3
The name of the VPN (context)
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

starMIPHAStatServName 1.1.8164.1.22.1.1.4
The Mobile IP home agent service name
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

starMIPHAStatDisconnects 1.1.8164.1.22.1.1.5
The number of session disconnects for the associated Mobile IP home agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPHAStatExpiry 1.1.8164.1.22.1.1.6
The number of session expirations for the associated Mobile IP home agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPHAStatDereg 1.1.8164.1.22.1.1.7
The number of session deregistrations for the associated Mobile IP home agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPHAStatAdminDrop 1.1.8164.1.22.1.1.8
The number of session disconnects due to administrator actions for the associated Mobile IP home agent VPN
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPHAStatRegRecvTotal 1.1.8164.1.22.1.1.9
The number of session registrations received for the associated Mobile IP home agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPHAStatRegRecvInitial 1.1.8164.1.22.1.1.10
The number of initial session registrations received for the associated Mobile IP home agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPHAStatRegRecvRenew 1.1.8164.1.22.1.1.11
The number of session registration renewals received for the associated Mobile IP home agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPHAStatRegRecvDereg 1.1.8164.1.22.1.1.12
The number of session deregistrations received for the associated Mobile IP home agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPHAStatRegAcceptTotal 1.1.8164.1.22.1.1.13
The number of session registrations accepted for the associated Mobile IP home agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPHAStatRegAcceptReg 1.1.8164.1.22.1.1.14
The number of session registrations accepted for the associated Mobile IP home agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPHAStatRegAcceptRenew 1.1.8164.1.22.1.1.15
The number of session registration renewals accepted for the associated Mobile IP home agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPHAStatRegAcceptDereg 1.1.8164.1.22.1.1.16
The number of session deregistrations accepted for the associated Mobile IP home agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPHAStatRegDeniedTotal 1.1.8164.1.22.1.1.17
The number of session registrations denied for the associated Mobile IP home agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPHAStatRegDeniedInitial 1.1.8164.1.22.1.1.18
The number of session initial registrations denied for the associated Mobile IP home agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPHAStatRegDeniedRenew 1.1.8164.1.22.1.1.19
The number of session registration renewals denied for the associated Mobile IP home agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPHAStatRegDeniedDereg 1.1.8164.1.22.1.1.20
The number of session deregistrations denied for the associated Mobile IP home agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPHAStatRegReplyTotal 1.1.8164.1.22.1.1.21
The total number of session registration replies for the associated Mobile IP home agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPHAStatRegReplyAcceptReg 1.1.8164.1.22.1.1.22
The number of session registration replies accepted indicating registration for the associated Mobile IP home agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPHAStatRegReplyAcceptDereg 1.1.8164.1.22.1.1.23
The number of session registration replies accepted indicated deregistration for the associated Mobile IP home agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPHAStatRegReplyDenied 1.1.8164.1.22.1.1.24
The number of session registration replies which were denied for the associated Mobile IP home agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPHAStatRegReplyBadReq 1.1.8164.1.22.1.1.25
The number of session registration replies indicating a bad request for the associated Mobile IP home agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPHAStatRegReplyMismatchID 1.1.8164.1.22.1.1.26
The number of session registration replies indicating an ID mismatch for the associated Mobile IP home agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPHAStatRegReplyAdminProhib 1.1.8164.1.22.1.1.27
The number of session registration replies indicating administrator prohibition for the associated Mobile IP home agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPHAStatRegReplyUnspecErr 1.1.8164.1.22.1.1.28
The number of session registration replies with an unspecified error for the associated Mobile IP home agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPHAStatRegReplyNoResource 1.1.8164.1.22.1.1.29
The number of session registration replies indicating no resources for the associated Mobile IP home agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPHAStatRegReplyMnAuthFail 1.1.8164.1.22.1.1.30
The number of session registration replies indication mobile number authentication failure for the associated Mobile IP home agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPHAStatRegReplyFAAuthFail 1.1.8164.1.22.1.1.31
The number of session registration replies indicating a foreign agent authentication failure for the associated Mobile IP home agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPHAStatRegReplySimulBind 1.1.8164.1.22.1.1.32
The number of session registration replies indicating a simultaneous bind condition for the associated Mobile IP home agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPHAStatRegReplyUnknownHA 1.1.8164.1.22.1.1.33
The number of session registration replies indicating unknown home agent for the associated Mobile IP home agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPHAStatRegReplyRevTunUnav 1.1.8164.1.22.1.1.34
The number of session registration replies indicating no reverse tunnel available for the associated Mobile IP home agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPHAStatRegReplyRevTunMand 1.1.8164.1.22.1.1.35
The number of session registration replies indicating reverse tunneling is mandatory for the associated Mobile IP home agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPHAStatRegReplyEncapUnav 1.1.8164.1.22.1.1.36
The number of session registration replies indicating IP encapsulation was not available for the associated Mobile IP home agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPHAStatRegReplySendError 1.1.8164.1.22.1.1.37
The number of session registration replies indicating a send error occurred for the associated Mobile IP home agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPHAStatFARevocations 1.1.8164.1.22.1.1.38
The number of FA revocations for the associated Mobile IP home agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPHAStatRegAcceptHO 1.1.8164.1.22.1.1.39
The number of hand over session registrations accepted for the associated Mobile IP home agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPHAStatRegDeniedHO 1.1.8164.1.22.1.1.40
The number of hand over session registrations denied for the associated Mobile IP home agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPHAStatRegDiscardTotal 1.1.8164.1.22.1.1.41
The number of session registrations discarded for the associated Mobile IP home agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starentMIPFA 1.1.8164.1.23
OBJECT IDENTIFIER    

starMIPFAStatTable 1.1.8164.1.23.1
A table containing MIP FA Stats
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    StarMIPFAStatEntry

starMIPFAStatEntry 1.1.8164.1.23.1.1
The statistics for a specific foreign agent Mobile IP VPN (context) service
Status: current Access: not-accessible
OBJECT-TYPE    
  StarMIPFAStatEntry  

starMIPFAStatVpnID 1.1.8164.1.23.1.1.1
Internal identication of the foreign agent Mobile IP VPN (context)
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starMIPFAStatSvcID 1.1.8164.1.23.1.1.2
The service identification is made up from first 8 chars of context name and first 8 chars of service name separated by (:)
Status: current Access: not-accessible
OBJECT-TYPE    
  StarShortID  

starMIPFAStatVpnName 1.1.8164.1.23.1.1.3
The foreign agent mobile IP VPN (context) name
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

starMIPFAStatServName 1.1.8164.1.23.1.1.4
The Mobile IP foreign agent service name
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

starMIPFAStatAdvertSend 1.1.8164.1.23.1.1.5
The number of advertisements sent for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatDiscExpiry 1.1.8164.1.23.1.1.6
The number of session disconnects due to expiration for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatDiscDereg 1.1.8164.1.23.1.1.7
The number of session disconnects due to deregistration for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatDiscAdmin 1.1.8164.1.23.1.1.8
The number of dession disconnects due to administrator action for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatAuthAttempt 1.1.8164.1.23.1.1.9
The number of session authentication attempts for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatAuthSuccess 1.1.8164.1.23.1.1.10
The number of session authentication successes for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatAuthFailure 1.1.8164.1.23.1.1.11
The number of session authentication failures for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegRecvTotal 1.1.8164.1.23.1.1.12
The total number of session registrations received for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegRecvInitial 1.1.8164.1.23.1.1.13
The number of initial session registrations received for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegRecvRenewal 1.1.8164.1.23.1.1.14
The number of session registration renewals for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegRecvDereg 1.1.8164.1.23.1.1.15
The number of session deregistrations for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegAcceptTotal 1.1.8164.1.23.1.1.16
The total number of session registrations accepted for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegAcceptInitial 1.1.8164.1.23.1.1.17
The number of initial session registrations accepted for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegAcceptRenewal 1.1.8164.1.23.1.1.18
The number of session registration renewals accepted for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegAcceptDereg 1.1.8164.1.23.1.1.19
The number of session deregistrations accepted for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegDenTotal 1.1.8164.1.23.1.1.20
The total number of session registrations denied for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegDenInitial 1.1.8164.1.23.1.1.21
The number of initial session registrations denied for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegDenRenewal 1.1.8164.1.23.1.1.22
The number of session registration renewals denied for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegDenDereg 1.1.8164.1.23.1.1.23
The number of session deregistrations denied for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegDiscardTotal 1.1.8164.1.23.1.1.24
The total number of session registrations discarded for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegDiscardInitial 1.1.8164.1.23.1.1.25
The total number of session registrations discarded for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegDiscardRenewal 1.1.8164.1.23.1.1.26
The number of session registration renewals discarded for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegDiscardDereg 1.1.8164.1.23.1.1.27
The number of dession reregistrations discarded for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegRelayedTotal 1.1.8164.1.23.1.1.28
The total number of session registrations relayed for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegRelayedInitial 1.1.8164.1.23.1.1.29
The number of initial session registrations relayed for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegRelayedRenewal 1.1.8164.1.23.1.1.30
The number of dession registration renewals relayed for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegRelayedDereg 1.1.8164.1.23.1.1.31
The number of session deregistrations relayed for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegAuthFailTotal 1.1.8164.1.23.1.1.32
The total number of session registration authentication failures for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegAuthFailInitial 1.1.8164.1.23.1.1.33
The number of initial session registration failures for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegAuthFailRenewal 1.1.8164.1.23.1.1.34
The number of session registration renewal failures for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegAuthFailDereg 1.1.8164.1.23.1.1.35
The number of session deregistration authentication failures for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegDenPDSNTotal 1.1.8164.1.23.1.1.36
The total number of PDSN session registrations denied for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegDenPDSNInitial 1.1.8164.1.23.1.1.37
The number of initial PDSN session registrations denied for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegDenPDSNRenewal 1.1.8164.1.23.1.1.38
The number of PDSN session registration renewals denied for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegDenPDSNDereg 1.1.8164.1.23.1.1.39
The number of PDSN session deregistrations denied for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegDenHATotal 1.1.8164.1.23.1.1.40
The total number of session deregistrations denied by the home agent for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegDenHAInitial 1.1.8164.1.23.1.1.41
The number of initial session registrations denied by the home agent for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegDenHARenewal 1.1.8164.1.23.1.1.42
The number of session registration renewals denied by the home agent for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegDenHADereg 1.1.8164.1.23.1.1.43
The number of session deregistrations denied by the home agent for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegDenPDSNUnspec 1.1.8164.1.23.1.1.44
The number of PDSN session registrations denied for an unspecified reason for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegDenPDSNTimeout 1.1.8164.1.23.1.1.45
The number of PDSN session registrations denied due to timer expiration for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegDenPDSNAdmin 1.1.8164.1.23.1.1.46
The number of PDSN session registrations denied due to administrator prohibition for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegDenPDSNResources 1.1.8164.1.23.1.1.47
The number of PDSN session registrations denied due to no resources for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegDenPDSNMnAuth 1.1.8164.1.23.1.1.48
The number of PDSN session registrations denied due to mobile number authentication for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegDenPDSNHAAuth 1.1.8164.1.23.1.1.49
The number of PDSN session registrations denied by the home agent for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegDenPDSNTooLong 1.1.8164.1.23.1.1.50
The number of PDSN session registrations denied due to a life too long indication for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegDenPDSNBadReq 1.1.8164.1.23.1.1.51
The number of PDSN session registrations denied due to a bad request indication for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegDenPDSNEncapUnav 1.1.8164.1.23.1.1.52
The number of PDSN session registrations denied due to no IP encapsulation available for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegDenPDSNRevTunUnav 1.1.8164.1.23.1.1.53
The number of PDSN session registrations denied due to no reverse tunnel available for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegDenPDSNRevTunMand 1.1.8164.1.23.1.1.54
The number of PDSN session registration denied due to reverse tunneling being mandatory for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegDenHAFAAuth 1.1.8164.1.23.1.1.55
The number of PDSN registrations denied by the home agent due to authentication failure for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegDenHABadReq 1.1.8164.1.23.1.1.56
The number of session registration denied by the home agent due to the request being invalid for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegDenHAMismatchID 1.1.8164.1.23.1.1.57
The number of session registrations denied by the home agent due to an ID mismatch for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegDenHASimulBind 1.1.8164.1.23.1.1.58
The number of session registrations denied by the home agent due to a simultaneous bind attempt for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegDenHAUnknownHA 1.1.8164.1.23.1.1.59
The number of session registrations denied by the home agent for an unknown reason for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegDenHARevRunUnavail 1.1.8164.1.23.1.1.60
The number of session registrations denied by the home agent due to no reverse tunnel being available for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegRplRcvTotal 1.1.8164.1.23.1.1.61
The total number of session registration replies received for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegRplRcvTotalRly 1.1.8164.1.23.1.1.62
The total number of session registration replies relayed for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegRplRcvErrors 1.1.8164.1.23.1.1.63
The total number of session registration replies received indicating errors for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegRplRcvInitial 1.1.8164.1.23.1.1.64
The number of initial session registration replies received for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegRplRcvInitialRly 1.1.8164.1.23.1.1.65
The number of initial session registration replies relayed for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegRplRcvRenewal 1.1.8164.1.23.1.1.66
The number of session registration renewal replies received for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegRplRcvRenewalRly 1.1.8164.1.23.1.1.67
The number of session registration renewal replies received for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegRplRcvDereg 1.1.8164.1.23.1.1.68
The number of session registration replies received indicating deregistration for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegRplRcvDeregRly 1.1.8164.1.23.1.1.69
The number of session registration replies relayed indicating deregistration for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegRplSentTotal 1.1.8164.1.23.1.1.70
The total number of session registration replies sent for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegRplSentAcceptReg 1.1.8164.1.23.1.1.71
The number of session registration replies which were sent and accepted for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegRplSentAcceptDereg 1.1.8164.1.23.1.1.72
The number of session registration replies which were sent and accepted indication deregistration for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegRplSentBadReq 1.1.8164.1.23.1.1.73
The number of session registration replies which were sent indicating the request was invalid for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegRplSentTooLong 1.1.8164.1.23.1.1.74
The number of session registration replies which were sent indicating life too long for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegRplSentMnAuthFail 1.1.8164.1.23.1.1.75
The number of session registration replies which were sent indicating mobile number authentication failure for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegRplSentHAAuthFail 1.1.8164.1.23.1.1.76
The number of session registration replies which were sent indicating home agent authentication failure for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegRplSentAdminProhib 1.1.8164.1.23.1.1.77
The number of session registration replies which were sent indicating prohibited by the administration for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegRplSentNoResources 1.1.8164.1.23.1.1.78
The number of session registration replies which were sent indicating no resources available for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegRplSentRevTunUnav 1.1.8164.1.23.1.1.79
The number of session registration replies which were sent indicating no reverse tunnel available for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegRplSentRevTunMand 1.1.8164.1.23.1.1.80
The number of session registration replies which were sent indicating reverse tunneling was mandatory for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegRplSentSendErrors 1.1.8164.1.23.1.1.81
The number of session registration replies which were sent indicating there were errors in transmission for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegDenPDSNBadReply 1.1.8164.1.23.1.1.82
The number of session registrations denied by PDSN due to bad relply from HA for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegDenPDSNMissNAI 1.1.8164.1.23.1.1.83
The number of session registrations denied by PDSN due to missing NAI for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegDenPDSNMissHomeAgent 1.1.8164.1.23.1.1.84
The number of session registrations denied by PDSN due to missing home agent for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegDenPDSNMissHomeAddr 1.1.8164.1.23.1.1.85
The number of session registrations denied by PDSN due to missing home address for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegDenPDSNUnknChallenge 1.1.8164.1.23.1.1.86
The number of session registrations denied by PDSN due to unknown challenge for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegDenPDSNMissChallenge 1.1.8164.1.23.1.1.87
The number of session registrations denied by PDSN due to missing challenge for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegDenPDSNStaleChallenge 1.1.8164.1.23.1.1.88
The number of session registrations denied by PDSN due to stale challenge for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegDenPDSNMNTooDistant 1.1.8164.1.23.1.1.89
The number of session registrations denied by PDSN due to MN too distant for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegDenPDSNStyleUnavail 1.1.8164.1.23.1.1.90
The number of session registration denied by PDSN due to style not available for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegDenPDSNHANetUnreach 1.1.8164.1.23.1.1.91
The number of session registrations denied by PDSN due to HA network unreachable for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegDenPDSNHAHostUnreach 1.1.8164.1.23.1.1.92
The number of session registrations denied by PDSN due to HA host unreachable for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegDenPDSNHAPortUnreach 1.1.8164.1.23.1.1.93
The number of session registrations denied by PDSN due to HA port unreachable for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegDenPDSNHAUnreach 1.1.8164.1.23.1.1.94
The number of session registrations denied by PDSN due to HA unreachable for misc reasons for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegDenPDSNInvCOA 1.1.8164.1.23.1.1.95
The number of session registrations denied by PDSN due to invalid COA for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegReqSentInitTotal 1.1.8164.1.23.1.1.96
The number of initial session registrations for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegReqSentInitResend 1.1.8164.1.23.1.1.97
The number of initial session registrations retried for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegReqSentRenewTotal 1.1.8164.1.23.1.1.98
The number of renewal session registrations for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegReqSentRenewResend 1.1.8164.1.23.1.1.99
The number of renewal session registrations retried for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegReqSentDeregTotal 1.1.8164.1.23.1.1.100
The number of session deregistrations for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegReqSentDeregResend 1.1.8164.1.23.1.1.101
The number of session deregistrations retried for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegRplSentMNTooDistant 1.1.8164.1.23.1.1.102
The number of session registration reply that indicate MN too distant for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegRplSentInvCOA 1.1.8164.1.23.1.1.103
The number of session registration reply that indicate invalid COA for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegRplSentHANetUnreach 1.1.8164.1.23.1.1.104
The number of session registration reply that indicate HA network unreachable for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegRplSentHAHostUnreach 1.1.8164.1.23.1.1.105
The number of session registration reply that indicate HA host unreachable for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegRplSentHAPortUnreach 1.1.8164.1.23.1.1.106
The number of session registration reply that indicate HA port unreachable for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegRplSentHAUnreach 1.1.8164.1.23.1.1.107
The number of session registration reply that indicate HA unreachable due to misc reasons for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegRplSentRegTimeout 1.1.8164.1.23.1.1.108
The number of session registration reply that indicate registration time out for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegRplSentMissNAI 1.1.8164.1.23.1.1.109
The number of session registration reply that indicate NAI missing for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegRplSentMissHomeAgent 1.1.8164.1.23.1.1.110
The number of session registration reply that indicate HA missing for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegRplSentMissHomeAddr 1.1.8164.1.23.1.1.111
The number of session registration reply that indicate home address missing for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegRplSentUnknChallenge 1.1.8164.1.23.1.1.112
The number of session registration reply that indicate unknown challenge for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegRplSentMissChallenge 1.1.8164.1.23.1.1.113
The number of session registration reply that indicate challenge missing for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegRplSentStaleChallenge 1.1.8164.1.23.1.1.114
The number of session registration reply that indicate stale challenge for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starMIPFAStatRegRplSentBadReply 1.1.8164.1.23.1.1.115
The number of session registration reply that indicate bad reply for the associated Mobile IP foreign agent VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starentRP 1.1.8164.1.24
OBJECT IDENTIFIER    

starRPStatTable 1.1.8164.1.24.1
A table containing MIP FA Stats
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    StarRPStatEntry

starRPStatEntry 1.1.8164.1.24.1.1
The statistics for a specific R-P VPN (context) service
Status: current Access: not-accessible
OBJECT-TYPE    
  StarRPStatEntry  

starRPStatVpnID 1.1.8164.1.24.1.1.1
The internal identification of the R-P VPN (context)
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starRPStatSvcID 1.1.8164.1.24.1.1.2
The service identification is made up from first 8 chars of context name and first 8 chars of service name separated by (:)
Status: current Access: not-accessible
OBJECT-TYPE    
  StarShortID  

starRPStatVpnName 1.1.8164.1.24.1.1.3
The R-P VPN (context) name
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

starRPStatServName 1.1.8164.1.24.1.1.4
The R-P service name
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

starRPRegRecvTotal 1.1.8164.1.24.1.1.5
The total number of session registrations received for the associated R-P VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starRPRegAcceptTotal 1.1.8164.1.24.1.1.6
The total number of session registrations accepted for the associated R-P VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starRPRegDeniedTotal 1.1.8164.1.24.1.1.7
The total number of session registrations denied for the associated R-P VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starRPRegDiscardTotal 1.1.8164.1.24.1.1.8
The total number of session registrations discarded for the associated R-P VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starRPRegAcceptInitial 1.1.8164.1.24.1.1.9
The total number of initial session registrations accepted for the associated R-P VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starRPRegAcceptIntraPDSN 1.1.8164.1.24.1.1.10
The number of Intra-PDSN session registrations accepted for the associated R-P VPN service
Status: obsolete Access: read-only
OBJECT-TYPE    
  Counter32  

starRPRegAcceptInterPDSN 1.1.8164.1.24.1.1.11
The number of Inter-PDSN session registrations accepted for the associated R-P VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starRPRegDeniedInitial 1.1.8164.1.24.1.1.12
The number of initial session registrations denied for the associated R-P VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starRPRegAcceptRenew 1.1.8164.1.24.1.1.13
The number of session registration renewals accepted for the associated R-P VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starRPRegDeniedRenew 1.1.8164.1.24.1.1.14
The number of session registration renewals denied for the associated R-P VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starRPRegAcceptDereg 1.1.8164.1.24.1.1.15
The number of session deregistrations accepted for the associated R-P VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starRPRegDeniedDereg 1.1.8164.1.24.1.1.16
The number of session deregistrations denied for the associated R-P VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starRPRegSendError 1.1.8164.1.24.1.1.17
The number of session registrations with errors in transmission for the associated R-P VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starRPRegHashError 1.1.8164.1.24.1.1.18
The number of session registrations with hash errors for the associated R-P VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starRPRegDecodeError 1.1.8164.1.24.1.1.19
The number of sessions registrations with decode errors for the associated R-P VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starRPRegUnhandled 1.1.8164.1.24.1.1.20
The number of session registrations unable to by proceeded for the associated R-P VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starRPRegAirlinkSeqError 1.1.8164.1.24.1.1.21
The number of session registrations with air link sequence errors for the associated R-P VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starRPRegDenyUnspec 1.1.8164.1.24.1.1.22
The number of session registrations denied for an unspecified reason for the associated R-P VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starRPRegDenyAdminProhib 1.1.8164.1.24.1.1.23
The number of session registrations denied due to administrator prohibition for the associated R-P VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starRPRegDenyNoResource 1.1.8164.1.24.1.1.24
The number of session registrations denied due to no resources available for the associated R-P VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starRPRegDenyAuth 1.1.8164.1.24.1.1.25
The number of session registrations denied due to authentication failure for the associated R-P VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starRPRegDenyMismatchID 1.1.8164.1.24.1.1.26
The number of session registrations denied due to an ID mismatch for the associated R-P VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starRPRegDenyBadRequest 1.1.8164.1.24.1.1.27
The number of session registrations denied due to the request being invalid for the associated R-P VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starRPRegDenyUnknownPDSN 1.1.8164.1.24.1.1.28
The number of session registrations denied due to the packet data service not being recognized for the associated R-P VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starRPRegDenyRevTunUnav 1.1.8164.1.24.1.1.29
The number of session registrations denied due to no reverse tunnel being available for the associated R-P VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starRPRegDenyRevTunReq 1.1.8164.1.24.1.1.30
The number of session registrations denied due to reverse tunneling being mandatory for the associated R-P VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starRPRegDenyUnrecogVend 1.1.8164.1.24.1.1.31
The number of session registrations denied due to the vendor not being recognized for the associated R-P VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starRPRegUpdTotal 1.1.8164.1.24.1.1.32
The total number of session registration updates for the associated R-P VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starRPRegUpdAccept 1.1.8164.1.24.1.1.33
The number of session registration updates which were accepted for the associated R-P VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starRPRegUpdDenied 1.1.8164.1.24.1.1.34
The number of session registration updates which were denied for the associated R-P VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starRPRegUpdUnack 1.1.8164.1.24.1.1.35
The number of session registration updates which were not acknowledged for the associated R-P VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starRPRegUpdTrans 1.1.8164.1.24.1.1.36
The number of session registration updates sent for the associated R-P VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starRPRegUpdRetrans 1.1.8164.1.24.1.1.37
The number of session registration updates resent for the associated R-P VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starRPRegUpdReceived 1.1.8164.1.24.1.1.38
The number of session registration updates received for the associated R-P VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starRPRegUpdDiscard 1.1.8164.1.24.1.1.39
The number of session registration updates discarded for the associated R-P VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starRPRegUpdSendError 1.1.8164.1.24.1.1.40
The number of session registration updates with errors in transmission for the associated R-P VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starRPRegUpdUplyrInit 1.1.8164.1.24.1.1.41
The number of session registration updates with up-link reinitializations
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starRPRegUpdOther 1.1.8164.1.24.1.1.42
The number of session registration updates with a reason of 'other' for the associated R-P VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starRPRegUpdHandoff 1.1.8164.1.24.1.1.43
The number of session registration updates due to a mobile hand-off for the associated R-P VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starRPRegUpdDenyUnspec 1.1.8164.1.24.1.1.44
The number of session registration updates denied for an unspecified reason for the associated R-P VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starRPRegUpdDenyAdminProhib 1.1.8164.1.24.1.1.45
The number of session registration updates denied due to administration prohibition for the associated R-P VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starRPRegUpdDenyAuth 1.1.8164.1.24.1.1.46
The number of session registration updates denied due to authentication failure for the associated R-P VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starRPRegUpdDenyMismatchID 1.1.8164.1.24.1.1.47
The number of session registration updates denied due to an ID mismatch for the associated R-P VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starRPRegUpdDenyBadRequest 1.1.8164.1.24.1.1.48
The number of session registration updates denied due to the request being invalid for the associated R-P VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starRPSecViolations 1.1.8164.1.24.1.1.49
The total number of session security violations for the associated R-P VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starRPSecBadAuth 1.1.8164.1.24.1.1.50
The total number of session security authentication violations for the associated R-P VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starRPSecBadID 1.1.8164.1.24.1.1.51
The total number of session security ID violations for the associated R-P VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starRPSecBadSpi 1.1.8164.1.24.1.1.52
The total number of session security SPI violations for the associated R-P VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starRPSecMissingMnHAAuth 1.1.8164.1.24.1.1.53
The total number of session security missing mobile number home agent authentication violation for the associated R-P VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starRPSecMissingRegUpdate 1.1.8164.1.24.1.1.54
The total number of session missing registration update violations for the associated R-P VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starRPRegRecvInitial 1.1.8164.1.24.1.1.55
The total number of initial session registration for the associated R-P VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starRPRegAcceptActvStartIntraPDSN 1.1.8164.1.24.1.1.56
The number of accepted registration request during intraPDSN handoff which contains active start for the associated R-P VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starRPRegAcceptActvStopIntraPDSN 1.1.8164.1.24.1.1.57
The number of accepted registration request during intraPDSN handoff which contains active stop for the associated R-P VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starRPRegRecvRenew 1.1.8164.1.24.1.1.58
The number of received renew registration request for the associated R-P VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starRPRegActvStartRenew 1.1.8164.1.24.1.1.59
The number of received renew registration request that contains active start for the associated R-P VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starRPRegActvStopRenew 1.1.8164.1.24.1.1.60
The number of received renew registration request that contains active stop for the associated R-P VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starRPRegRecvDereg 1.1.8164.1.24.1.1.61
The number of received deregistration request for the associated R-P VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starRPRegAcceptActvStopDereg 1.1.8164.1.24.1.1.62
The number of accepted deregistration request that contains active stop for the associated R-P VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starRPDiscSessAbsent 1.1.8164.1.24.1.1.63
The number of registration request discarded due to no session for the associated R-P VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starRPDiscNoMemory 1.1.8164.1.24.1.1.64
The number of registration request discarded due to no memory for the associated R-P VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starRPDiscMalformed 1.1.8164.1.24.1.1.65
The number of registration request discarded because malformed for the associated R-P VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starRPDiscAuthFail 1.1.8164.1.24.1.1.66
The number of registration request discarded because authentication failed for the associated R-P VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starRPDiscInternalBounce 1.1.8164.1.24.1.1.67
The number of registration request discarded because internal bounce for the associated R-P VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starRPDiscInpuQueueExceeded 1.1.8164.1.24.1.1.68
The number of registration request discarded because internal queue exceeded for the associated R-P VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starRPDiscMismatchedId 1.1.8164.1.24.1.1.69
The number of registration request discarded because mismatched ID for the associated R-P VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starRPDiscInvPacketLen 1.1.8164.1.24.1.1.70
The number of registration request discarded because invalid packet length for the associated R-P VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starRPDiscMisc 1.1.8164.1.24.1.1.71
The number of registration request discarded due to misc reasons for the associated R-P VPN service
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starRP1xTxBytes 1.1.8164.1.24.1.1.72
The number of 1x bytes transmitted, in megabytes
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starRP1xRxBytes 1.1.8164.1.24.1.1.73
The number of 1x bytes received, in megabytes
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starRP1xTxPackets 1.1.8164.1.24.1.1.74
The number of 1x packets transmitted, in thousands
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starRP1xRxPackets 1.1.8164.1.24.1.1.75
The number of 1x packets received, in thousands
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starRPDoTxBytes 1.1.8164.1.24.1.1.76
The number of Do bytes transmitted, in megabytes
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starRPDoRxBytes 1.1.8164.1.24.1.1.77
The number of Do bytes received, in megabytes
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starRPDoTxPackets 1.1.8164.1.24.1.1.78
The number of Do packets transmitted, in thousands
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starRPDoRxPackets 1.1.8164.1.24.1.1.79
The number of Do packets received, in thousands
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starentSubscriber 1.1.8164.1.26
OBJECT IDENTIFIER    

starSubTable 1.1.8164.1.26.1
A table containing subscriber information
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    StarSubEntry

starSubEntry 1.1.8164.1.26.1.1
Information for a specific Subscriber
Status: current Access: not-accessible
OBJECT-TYPE    
  StarSubEntry  

starSubContext 1.1.8164.1.26.1.1.1
The context the subscriber is in
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  DisplayString  

starSubMSID 1.1.8164.1.26.1.1.2
The MSID of the subscriber
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  OCTET STRING Size(1..16)  

starSubName 1.1.8164.1.26.1.1.3
The name of the subscriber
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  OCTET STRING Size(1..128)  

starSubTimerDuration 1.1.8164.1.26.1.1.4
The length of the long-duration timer in seconds
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Unsigned32  

starSubLongDurTimeoutAction 1.1.8164.1.26.1.1.5
The action taken by the system upon detection of a long-duration session
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  StarLongDurTimeoutAction  

starSubSetupTime 1.1.8164.1.26.1.1.6
The time when the call was setup
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  DateAndTime  

starSubHomeAddr 1.1.8164.1.26.1.1.7
The ipv4 home address.
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  IpAddress  

starSubHomeAddrv6 1.1.8164.1.26.1.1.8
The ipv6 home address.
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Ipv6Address  

starentEISServer 1.1.8164.1.27
OBJECT IDENTIFIER    

starEISServerTable 1.1.8164.1.27.1
A table containing EIS Server information
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    StarEISServerEntry

starEISServerEntry 1.1.8164.1.27.1.1
Information for a specific EIS Server
Status: current Access: not-accessible
OBJECT-TYPE    
  StarEISServerEntry  

starEISServerVPNID 1.1.8164.1.27.1.1.1
The VPN ID for the EIS Server
Status: current Access: not-accessible
OBJECT-TYPE    
  Gauge32  

starEISServerAddr 1.1.8164.1.27.1.1.2
The IP Address for the EIS Server
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  IpAddress  

starEISServerVPNName 1.1.8164.1.27.1.1.3
The VPN Name for this EIS Server
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  DisplayString  

starentThresholds 1.1.8164.1.28
OBJECT IDENTIFIER    

starThreshMeasuredPct 1.1.8164.1.28.1
The measured value of a thresholded parameter
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Gauge32 0..100  

starThreshPct 1.1.8164.1.28.2
The configured value of a thresholded parameter
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Integer32 0..100  

starThreshMeasuredInt 1.1.8164.1.28.3
The measured value of a thresholded parameter
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Gauge32  

starThreshInt 1.1.8164.1.28.4
The configured value of a thresholded parameter
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Unsigned32  

starThreshMeasuredMB 1.1.8164.1.28.5
The measured value of a thresholded parameter
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Gauge32  

starThreshMB 1.1.8164.1.28.6
The configured value of a thresholded parameter
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Unsigned32  

starThreshMeasuredGB 1.1.8164.1.28.7
The measured value of a thresholded parameter
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Gauge32  

starThreshGB 1.1.8164.1.28.8
The configured value of a thresholded parameter
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Unsigned32  

starThreshPeriodInt 1.1.8164.1.28.9
The configured value of a thresholded parameter
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Integer32 30..600  

starThreshDeviceNum 1.1.8164.1.28.10
The configured value of a thresholded parameter
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Integer32 1..4  

starentPort 1.1.8164.1.29
OBJECT IDENTIFIER    

starPortTable 1.1.8164.1.29.1
A table containing Port information
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    StarPortEntry

starPortEntry 1.1.8164.1.29.1.1
Information for a specific Port
Status: current Access: not-accessible
OBJECT-TYPE    
  StarPortEntry  

starPortSlot 1.1.8164.1.29.1.1.1
The Slot number for this port
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Integer32 1..48  

starPortNum 1.1.8164.1.29.1.1.2
The Port number within this slot
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Integer32 1..29  

starPortType 1.1.8164.1.29.1.1.3
Status: current Access: read-only
OBJECT-TYPE    
  INTEGER none(0), ethernet10100(1), ethernet1000dualmedia(2), ethernet1000(3), ds3(4), oc3atm(5), oc12atm(6), ds3e(7), rs232(8), bitst1e1(9), virtualethernet(10), ether10g(11)  

starPortTypeDescr 1.1.8164.1.29.1.1.4
A texual representing of the starPortType attribute
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

starPortAdminState 1.1.8164.1.29.1.1.5
The administrative start of the port
Status: current Access: read-only
OBJECT-TYPE    
  INTEGER unknown(0), enabled(1), disabled(2)  

starPortOperState 1.1.8164.1.29.1.1.6
Status: current Access: read-only
OBJECT-TYPE    
  INTEGER unknown(0), up(1), down(2), notapplicable(3)  

starPortOperMode 1.1.8164.1.29.1.1.7
Status: current Access: read-only
OBJECT-TYPE    
  INTEGER unknown(0), active(1), standby(2)  

starPortLinkState 1.1.8164.1.29.1.1.8
Status: current Access: read-only
OBJECT-TYPE    
  INTEGER unknown(0), up(1), down(2)  

starRedundantPortSlot 1.1.8164.1.29.1.1.9
The Slot number for the port the current port is redundant with, or 0 if unknown
Status: current Access: read-only
OBJECT-TYPE    
  Integer32 0..48  

starRedundantPortNum 1.1.8164.1.29.1.1.10
The Port number for the port the current port is redundant with, or 0 if unknown
Status: current Access: read-only
OBJECT-TYPE    
  Integer32 0..29  

starPortRxBytes 1.1.8164.1.29.1.1.11
The number of bytes successfully received, in megabytes. For ports of type rs232(8) or bitst1e1(9) this value will always be zero.
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPortTxBytes 1.1.8164.1.29.1.1.12
The number of bytes successfully transmitted, in megabytes. For ports of type rs232(8) or bitst1e1(9) this value will always be zero.
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPortRxFrames 1.1.8164.1.29.1.1.13
The 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 received
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPortTxFrames 1.1.8164.1.29.1.1.14
The 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 received
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPortRxDiscards 1.1.8164.1.29.1.1.15
The 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.
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPortTxDiscards 1.1.8164.1.29.1.1.16
The 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.
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPortRxErrors 1.1.8164.1.29.1.1.17
The number of inbound packets that contained errors preventing them from being deliverable to a higher-layer protocol.
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPortTxErrors 1.1.8164.1.29.1.1.18
The number of outbound packets that could not be transmitted because of errors.
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starentIPPool 1.1.8164.1.30
OBJECT IDENTIFIER    

starIPPoolTable 1.1.8164.1.30.1
A table containing IP Pool information
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    StarIPPoolEntry

starIPPoolEntry 1.1.8164.1.30.1.1
Information for a specific IP Pool
Status: current Access: not-accessible
OBJECT-TYPE    
  StarIPPoolEntry  

starIPPoolVpnID 1.1.8164.1.30.1.1.1
The context ID for this pool
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starIPPoolID 1.1.8164.1.30.1.1.2
The service identification is made up from first 8 chars of context name and first 16 chars of pool name separated by (:)
Status: current Access: not-accessible
OBJECT-TYPE    
  StarMediumID  

starIPPoolContext 1.1.8164.1.30.1.1.3
The context name string for this pool
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

starIPPoolGroup 1.1.8164.1.30.1.1.4
The name of the group to which the IP pool belongs
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

starIPPoolName 1.1.8164.1.30.1.1.5
The name of the IP pool
Status: current Access: read-only
OBJECT-TYPE    
  OCTET STRING Size(1..32)  

starIPPoolType 1.1.8164.1.30.1.1.6
The type of the pool
Status: current Access: read-only
OBJECT-TYPE    
  INTEGER unknown(0), private(1), public(2), static(3), resource(4), nat(5)  

starIPPoolState 1.1.8164.1.30.1.1.7
The state of the pool
Status: current Access: read-only
OBJECT-TYPE    
  INTEGER unknown(0), good(1), pendingdelete(2), alarm(3), resize(4), inactive(5)  

starIPPoolStartAddr 1.1.8164.1.30.1.1.8
The start IP address of the pool
Status: current Access: read-only
OBJECT-TYPE    
  IpAddress  

starIPPoolMaskorEndAddr 1.1.8164.1.30.1.1.9
The mask or end IP address of the pool
Status: current Access: read-only
OBJECT-TYPE    
  IpAddress  

starIPPoolPriority 1.1.8164.1.30.1.1.10
The priority of the pool
Status: current Access: read-only
OBJECT-TYPE    
  Integer32  

starIPPoolUsed 1.1.8164.1.30.1.1.11
The number of IP addresses in USED state in the pool
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starIPPoolHold 1.1.8164.1.30.1.1.12
The number of IP addresses in HOLD state in the pool
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starIPPoolRelease 1.1.8164.1.30.1.1.13
The number of IP addresses in RELEASE state in the pool
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starIPPoolFree 1.1.8164.1.30.1.1.14
The number of IP addresses in FREE state in the pool
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starentIPPoolGroup 1.1.8164.1.64
OBJECT IDENTIFIER    

starIPPoolGroupTable 1.1.8164.1.64.1
A table containing IP Pool Group information
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    StarIPPoolGroupEntry

starIPPoolGroupEntry 1.1.8164.1.64.1.1
Information for a specific IP Pool Group
Status: current Access: not-accessible
OBJECT-TYPE    
  StarIPPoolGroupEntry  

starIPPoolGroupVpnID 1.1.8164.1.64.1.1.1
The context ID for this pool group
Status: current Access: not-accessible
OBJECT-TYPE    
  Gauge32  

starIPPoolGroupID 1.1.8164.1.64.1.1.2
The service identification is made up from first 8 chars of context name and first 16 chars of pool group name separated by (:)
Status: current Access: not-accessible
OBJECT-TYPE    
  StarMediumID  

starIPPoolGroupName 1.1.8164.1.64.1.1.3
The name of the IP pool group
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

starIPPoolGroupVpnName 1.1.8164.1.64.1.1.4
The context name string for this pool group
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

starIPPoolGroupUsed 1.1.8164.1.64.1.1.5
The number of IP addresses in USED state in the pool group
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starIPPoolGroupHold 1.1.8164.1.64.1.1.6
The number of IP addresses in HOLD state in the pool group
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starIPPoolGroupRelease 1.1.8164.1.64.1.1.7
The number of IP addresses in RELEASE state in the pool group
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starIPPoolGroupFree 1.1.8164.1.64.1.1.8
The number of IP addresses in FREE state in the pool group
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starIPPoolGroupPctUsed 1.1.8164.1.64.1.1.9
The 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 230
Status: current Access: read-only
OBJECT-TYPE    
  Integer32 0..10000  

starIPPoolGroupAvail 1.1.8164.1.64.1.1.10
The number of IP addresses in AVAILABLE state in the pool group
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starentTrapData 1.1.8164.1.31
OBJECT IDENTIFIER    

starCongestionPolicy 1.1.8164.1.31.1
The policy invoked for congestion events
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  INTEGER reject(1), redirect(2), drop(3)  

starCongestionResourceType 1.1.8164.1.31.2
The resource type for a congestion event
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  INTEGER systemcpu(1), servicecpu(2), averagememory(3), queuesize(4), queuedelay(5), license(6), portutil(7), rxportutil(8), txportutil(9), rxperportutil(10), txperportutil(11), servicecapacity(12)  

starPTACConfig 1.1.8164.1.31.3
The number of PACs/PSCs//TACs configured in the system
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Integer32 0..14  

starPTACActive 1.1.8164.1.31.4
The number of PACs/PSCs/TACs active in the system
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Integer32 0..14  

starContextName 1.1.8164.1.31.5
The name of a context configured on the IMG
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  DisplayString  

starInterfaceName 1.1.8164.1.31.6
The name of an interface
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  DisplayString  

starPCFAddress 1.1.8164.1.31.7
The IP address of a PCF
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  IpAddress  

starPeerAddress 1.1.8164.1.31.8
Peer Address
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  IpAddress  

starLicensedSessions 1.1.8164.1.31.9
The number of sessions enabled by the software license
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Unsigned32  

starCurrentSessions 1.1.8164.1.31.10
The number of current sessions in use against a software license
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Gauge32  

starL3Address 1.1.8164.1.31.11
L3 Address
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  IpAddress  

starUDPPortNum 1.1.8164.1.31.12
UDP Port Number
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Integer32 1..65535  

starSRPIpAddress 1.1.8164.1.31.13
SRP IP Address
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  IpAddress  

starBGPPeerIpAddress 1.1.8164.1.31.14
BGP Peer IP Address
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  IpAddress  

starContFiltCFFilename 1.1.8164.1.31.15
File name for the OPTCMDB
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  DisplayString  

starContFiltCFErrorCode 1.1.8164.1.31.16
Error code
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  INTEGER unknownerror(1), notavailable(2), loadfailure(3)  

starFecthedFromAAAMgr 1.1.8164.1.31.17
The number calls fetched from aaa mgr
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Integer32  

starPriorToAudit 1.1.8164.1.31.18
The number calls prior to audit
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Integer32  

starPassedAudits 1.1.8164.1.31.19
The number of calls passed audit
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Integer32  

starCallsRecovered 1.1.8164.1.31.20
The number of calls recovered
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Integer32  

starAllCallLines 1.1.8164.1.31.21
The number of a11 call lines
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Integer32  

starElapsedMs 1.1.8164.1.31.22
The audit time elapsed in ms
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Integer32  

starCDRFilename 1.1.8164.1.31.23
The name of a CDR (EDR/UDR) file
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  DisplayString  

starDiameterVpnName 1.1.8164.1.31.24
Diameter VPN (Context) Name
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  DisplayString  

starDiameterPeerAddr 1.1.8164.1.31.25
Diameter Peer Address
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  IpAddress  

starDiameterEndpointName 1.1.8164.1.31.26
Diameter Endpoint Name
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  DisplayString  

starDiameterPeerAddrIpv6 1.1.8164.1.31.34
Diameter Peer Address
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Ipv6Address  

starInterfaceIPAddress 1.1.8164.1.31.27
Interface IP Address
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  IpAddress  

starOSPFNeighborRouterID 1.1.8164.1.31.28
Interface IP Address
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  IpAddress  

starOSPFFromState 1.1.8164.1.31.29
FROM state for OSPF Neighbor
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  StarOSPFNeighborState  

starOSPFToState 1.1.8164.1.31.30
TO state for OSPF Neighbor
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  StarOSPFNeighborState  

starBLFilename 1.1.8164.1.31.31
File name for the OPTBLDB
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  DisplayString  

starBLErrorCode 1.1.8164.1.31.32
Error code
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  INTEGER unknownerror(1), notavailable(2), loadfailure(3)  

starDiameterECode 1.1.8164.1.31.33
Diameter Cause Code
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  INTEGER notcomplete(1), hostnamemismatch(2), hostrealmmismatch(3), securitymismatch(4), tlssertificateerror(5), tlshandshakeerror(6), authappidmismatch(7)  

starContFiltCFUpgradeFilename 1.1.8164.1.31.35
File name for the Full or Incremental OPTCMDB
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  DisplayString  

starContFiltCFUpgradeErrorCode 1.1.8164.1.31.36
Error code
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  INTEGER unknownerror(1), upgradefullfailure(2), upgradeincrfailure(3)  

starBLUpgradeFilename 1.1.8164.1.31.37
File name for the Full OPTBLDB
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  DisplayString  

starBLUpgradeErrorCode 1.1.8164.1.31.38
Error code
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  INTEGER unknownerror(1), upgradefullfailure(2)  

starDynPkgFilename 1.1.8164.1.31.39
File name for the DynPkg
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  DisplayString  

starDynCFErrorCode 1.1.8164.1.31.40
Error code
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  INTEGER unknownerror(1), notavailable(2), loadfailure(3)  

starDynPkgUpgradeFilename 1.1.8164.1.31.41
File name for the Full DynPkg
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  DisplayString  

starDynCFUpgradeErrorCode 1.1.8164.1.31.42
Error code
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  INTEGER unknownerror(1), upgradefullfailure(2)  

starCscfSessCongestionResourceType 1.1.8164.1.31.43
Cscf Session resource type for a congestion event
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  INTEGER cpu(1), memory(2)  

starSmgrId 1.1.8164.1.31.44
Session Manager Instance ID
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Integer32 1..255  

starEGTPVpnName 1.1.8164.1.31.45
The name of this VPN (context)
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  DisplayString  

starEGTPServName 1.1.8164.1.31.46
The name of this service
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  DisplayString  

starEGTPInterfaceType 1.1.8164.1.31.47
Egtp interface type
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  INTEGER invalid(0), sgwingress(1), sgwegress(2), pgwingress(3), sgsn(4)  

starEGTPSelfPort 1.1.8164.1.31.48
The Port number of the EGTP
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Gauge32  

starEGTPSelfAddr 1.1.8164.1.31.49
The IP Address of the EGTP
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  IpAddress  

starEGTPPeerPort 1.1.8164.1.31.50
The Port number of the PeerNode
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Gauge32  

starEGTPPeerAddr 1.1.8164.1.31.51
The IP Address of the PeerNode
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  IpAddress  

starEGTPPeerOldRstCnt 1.1.8164.1.31.52
EGTP peer old restart counter
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Gauge32  

starEGTPPeerNewRstCnt 1.1.8164.1.31.53
EGTP peer new restart counter
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Gauge32  

starEGTPPeerSessCnt 1.1.8164.1.31.54
EGTP peer session count
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Gauge32  

starEGTPFailureReason 1.1.8164.1.31.55
Egtp path failure reason
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  INTEGER unknown(0), restartcounterchange(1), noresponsefrompeer(2)  

starGSSCDRLossConfigured 1.1.8164.1.31.56
The configured value of threshold CDR Loss at GSS
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Unsigned32  

starGSSCDRLossMeasured 1.1.8164.1.31.57
The Measured value of CDR Loss at GSS
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Unsigned32  

starLicenseKey 1.1.8164.1.31.58
The license key
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Unsigned32  

starLicenseExpiryDate 1.1.8164.1.31.59
The license expiration date/time
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  DateAndTime  

starLicenseDaysRemaining 1.1.8164.1.31.60
The number of days remaining before the license expires
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Unsigned32  

starLicenseDaysAfterExpiry 1.1.8164.1.31.61
The number of days after the license has expired
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Unsigned32  

starNPUSlot 1.1.8164.1.31.62
The NPU slot number
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Integer32 1..48  

starSPRServerIpAddr 1.1.8164.1.31.63
The IP Address of the SSC Server
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  IpAddress  

starMVGEndpointName 1.1.8164.1.31.66
MVG Endpoint Name
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  DisplayString  

starMVGCauseCode 1.1.8164.1.31.69
MVG Cause Code
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  INTEGER servernotreachable(1), servicereachable(2)  

starMVGProtocolType 1.1.8164.1.31.68
MVG Protocol Types
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  INTEGER protocolhttp(1), protocoltcp(2), protocolicmp(3)  

starPCCNtfyIntfPeerName 1.1.8164.1.31.73
IPCF Event Notification Interface Peer Name
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  DisplayString  

starECSTotalDNSLearntIPThresholdInstance 1.1.8164.1.31.74
ACSMgr Instance Id
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Integer32 1..65535  

starECSTotalDNSLearntIPThresholdconfigured 1.1.8164.1.31.75
Configured Threshold value in Percentage
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Integer32 1..100  

starECSTotalDNSLearntIPThresholdmeasured 1.1.8164.1.31.76
Measured value in Percentage
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Integer32 1..100  

starPeerAddressIpv6 1.1.8164.1.31.77
Peer Ipv6 Address
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Ipv6Address  

starLAGPartner 1.1.8164.1.31.78
The name of this service
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  DisplayString  

starSGSServiceVpnName 1.1.8164.1.31.79
SGS service context name
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  DisplayString  

starSGSServiceServName 1.1.8164.1.31.80
SGS service name
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  DisplayString  

starVLRName 1.1.8164.1.31.81
VLR name
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  DisplayString  

starVLRIpAddr1 1.1.8164.1.31.82
VLR IP Address1
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  IpAddress  

starVLRIpAddr2 1.1.8164.1.31.83
VLR IP Address2
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  IpAddress  

starVLRPortNum 1.1.8164.1.31.84
VLR Port Number
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Integer32 1..65535  

starCongestionType 1.1.8164.1.31.85
The type congestion threshold hit
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  INTEGER critical(1), major(2), minor(3)  

starCongestionActionProfileName 1.1.8164.1.31.86
The name of a action profile asscociated with the threshold type
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  DisplayString  

starSessMgrFlowInstId 1.1.8164.1.31.87
Session Manager instance ID
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Integer32 1..65535  

starSessMgrFlowPDNNo 1.1.8164.1.31.88
Tota PDNs Available
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Integer32 1..65535  

starSessMgrFlowMemUsage 1.1.8164.1.31.89
Totat Memory Usage of this instance
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Integer32 1..65535  

starSessMgrFlowCounter 1.1.8164.1.31.90
Session Manager Active Flows
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Integer32 1..65535  

starSessMgrTotalFlowCount 1.1.8164.1.31.91
Session Manager Active Flows
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Integer32 1..65535  

starHENBGWServiceVpnName 1.1.8164.1.31.92
HENBGW Service VPN Name
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  DisplayString  

starHENBGWServiceServName 1.1.8164.1.31.93
HENBGW Service Name
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  DisplayString  

starHENBGWServiceLogicalENBId 1.1.8164.1.31.94
HENBGW Service Logical Enodb ID
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  DisplayString  

starHENBGWServiceMMEServName 1.1.8164.1.31.95
HENBGW Service MME Name
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  DisplayString  

starHENBGWServiceSelfAddr 1.1.8164.1.31.96
HENBGW Service Self IP Address
Status: current Access: not-accessible
OBJECT-TYPE    
  IpAddress  

starHENBGWServicePeerAddr 1.1.8164.1.31.97
HENBGW Service Peer IP Address
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  IpAddress  

starHENBGWServiceSelfPort 1.1.8164.1.31.98
HENBGW Service Self Port Number
Status: current Access: not-accessible
OBJECT-TYPE    
  Integer32 1..65535  

starHENBGWServicePeerPort 1.1.8164.1.31.99
HENBGW Service Peer Port Number
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Integer32 1..65535  

starNPUSlotNumber 1.1.8164.1.31.100
NPU Slot Number
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Integer32 1..65535  

starNPUCPUNumber 1.1.8164.1.31.101
NPU CPU Number
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Integer32 1..65535  

starNPUNPUNumber 1.1.8164.1.31.102
NPU's NPU Number
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Integer32 1..65535  

starChassisCrashList 1.1.8164.1.31.103
Chassis Crash List Full
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  TruthValue  

starLIRcvryErrType 1.1.8164.1.31.104
LI Recovery Error Types
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  INTEGER syncerror(0), readerror(1), writeerror(2), integrityerror(3)  

starLIRcvryErrString 1.1.8164.1.31.105
LI Recovery Error String
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  DisplayString  

starPMIPVpnName 1.1.8164.1.31.106
The name of this VPN (context)
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  DisplayString  

starPMIPServName 1.1.8164.1.31.107
The name of this service
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  DisplayString  

starPMIPSelfAddrType 1.1.8164.1.31.108
The IP Address of the PMIP
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  InetAddressType  

starPMIPSelfAddr 1.1.8164.1.31.109
The IP Address of the PMIP
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  InetAddress  

starPMIPPeerAddrType 1.1.8164.1.31.110
The IP Address of the PMIP
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  InetAddressType  

starPMIPPeerAddr 1.1.8164.1.31.111
The IP Address of the PMIP
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  InetAddress  

starPMIPPeerOldRstCnt 1.1.8164.1.31.112
PMIP peer old restart counter
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Counter32  

starPMIPPeerNewRstCnt 1.1.8164.1.31.113
PMIP peer new restart counter
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Counter32  

starPMIPPeerSessCnt 1.1.8164.1.31.114
PMIP peer session count
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Counter32  

starPMIPFailureReason 1.1.8164.1.31.115
PMIP path failure reason
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  INTEGER unknown(0), heartbeatrsprestartchange(1), noresponsefrompeer(2)  

starMMEInitialDisallowReason 1.1.8164.1.31.116
MME initial connection disallow reason.
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  DisplayString  

starSLSServiceVpnName 1.1.8164.1.31.117
SLS service context name
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  DisplayString  

starSLSServiceServName 1.1.8164.1.31.118
SLS service name
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  DisplayString  

starESMLCId 1.1.8164.1.31.119
ESMLC Id
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Integer32 0..255  

starESMLCIpAddr1 1.1.8164.1.31.120
ESMLC IP Address1
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  IpAddress  

starESMLCIpAddr2 1.1.8164.1.31.121
ESMLC IP Address2
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  IpAddress  

starESMLCPortNum 1.1.8164.1.31.122
ESMLC Port Number
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Integer32 1..65535  

starSBCServiceVpnName 1.1.8164.1.31.123
SBc service context name
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  DisplayString  

starSBCServiceServName 1.1.8164.1.31.124
SBc service name
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  DisplayString  

starPeerId 1.1.8164.1.31.125
Peer Id
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Integer32 0..255  

starPeerIpAddr 1.1.8164.1.31.126
Peer IP Address
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  IpAddress  

starPeerPortNum 1.1.8164.1.31.127
Peer Port Number
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Integer32 1..65535  

starBfdSrcAddressType 1.1.8164.1.31.128
This 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.
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  InetAddressType  

starBfdSrcAddress 1.1.8164.1.31.129
This object specifies the source IP address of this BFD session.
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  InetAddress  

starBfdDstAddressType 1.1.8164.1.31.130
This 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.
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  InetAddressType  

starBfdDstAddress 1.1.8164.1.31.131
This object specifies the neighboring IP address which is being monitored with this BFD session.
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  InetAddress  

starBfdLocalDisc 1.1.8164.1.31.132
This object specifies the local discriminator for this BFD session, used to uniquely identify it
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Unsigned32  

starBfdRemDisc 1.1.8164.1.31.133
This 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.
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Unsigned32  

starBfdSessDiagCode 1.1.8164.1.31.134
A diagnostic code specifying the local system's reason for the last transition of the session from up(4) to some other state.
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  INTEGER noDiagnostic(0), controlDetectionTimeExpired(1), echoFunctionFailed(2), neighborSignaledSessionDown(3), forwardingPlaneReset(4), pathDown(5), concatenatedPathDown(6), administrativelyDown(7), reverseConcatenatedPathDown(8), misConnectivityDefect(9)  

starSRPSwitchReason 1.1.8164.1.31.135
A 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)
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  INTEGER notDefined(0), aaaFailure(1), bgpFailure(2), bfdFailure(3), diameterFailure(4), hsrpSwitchover(5), chassisChassisBfdFailure(6), dualActive(7), dualStandby(8), deadTimerExpiry(9), forceStateChange(10), manualSwitchOver(11), egqcFailure(12)  

starHENBGWServiceTLRI 1.1.8164.1.31.136
HENBGW Service Overload Traffic load reduction indication percentage.
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Unsigned32  

starCBSServiceVpnName 1.1.8164.1.31.139
CBS service context name
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  DisplayString  

starIuBcSelfPortNum 1.1.8164.1.31.140
IuBc Self Port Number
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Integer32 1..65535  

starIuBcSelfIpAddr 1.1.8164.1.31.141
IuBc Self IP Address
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  IpAddress  

starIuBcPeerPortNum 1.1.8164.1.31.142
Peer Port Number
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Integer32 1..65535  

starIuBcPeerIpAddr 1.1.8164.1.31.143
IuBc Peer IP Address
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  IpAddress  

starIuBcTcpConnCauseStr 1.1.8164.1.31.144
IuBc Tcp Conn Cause Str
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  DisplayString  

starPhyPortId 1.1.8164.1.31.145
Physical Port Id as IfIndex
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Integer32  

starGTPCRLFSessMgrInst 1.1.8164.1.31.146
Session Manager Instance
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Integer32  

starGTPCRLFVPNName 1.1.8164.1.31.147
The context name of VPN is
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  DisplayString  

starGTPCRLFVPNId 1.1.8164.1.31.148
The context Id of VPN is
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Integer32  

starGTPCRLFContextName 1.1.8164.1.31.149
The name of Context is
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  DisplayString  

starGTPCRLFCurrAppTPS 1.1.8164.1.31.150
The current applied TPS value is
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Integer32  

starGTPCRLFCurrAppDelayTol 1.1.8164.1.31.151
The current applied delay Tolerance value is
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Integer32  

starBGPPeerIpv6Address 1.1.8164.1.31.152
Diameter Peer Address in IPv6
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Ipv6Address  

starMMEEMBMSServiceVpnName 1.1.8164.1.31.153
MME-EMBMS service context name
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  DisplayString  

starMMEEMBMSServiceServName 1.1.8164.1.31.154
MME-EMBMS service name
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  DisplayString  

starMMEEMBMSPeerId 1.1.8164.1.31.155
Peer Id
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Integer32 0..255  

starMMEEMBMSPeerIpAddr 1.1.8164.1.31.156
Peer IP Address
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  IpAddress  

starMMEEMBMSPeerPortNum 1.1.8164.1.31.157
Peer Port Number
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Integer32 1..65535  

starImsimgrInstId 1.1.8164.1.31.158
Imsi Manager Instance
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Integer32  

starLAGGroup 1.1.8164.1.31.159
The group number of the LAG group
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Integer32 1..29  


starVRFName 1.1.8164.1.31.161
VRF Name
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  DisplayString  

starStatFilesizeLimit 1.1.8164.1.31.162
The Stat File Size in integer
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Integer32 1..29  

starStatFilesizeMeasured 1.1.8164.1.31.163
The Stat file Size measured
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Integer32 1..29  

starentL2TP 1.1.8164.1.33
OBJECT IDENTIFIER    

starL2TPTable 1.1.8164.1.33.1
A table containing L2TP related information
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    StarL2TPEntry

starL2TPEntry 1.1.8164.1.33.1.1
The statistics for a L2TP entry
Status: current Access: not-accessible
OBJECT-TYPE    
  StarL2TPEntry  

starL2TPLocalTunnelID 1.1.8164.1.33.1.1.1
The internal identification of the L2TP local tunnel ID
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Unsigned32  

starL2TPPeerTunnelID 1.1.8164.1.33.1.1.2
The internal identification of the L2TP peer tunnel ID
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Unsigned32  

starL2TPContextName 1.1.8164.1.33.1.1.3
The name of the context
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  DisplayString  

starL2TPServiceName 1.1.8164.1.33.1.1.4
The name of the service
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  DisplayString  

starL2TPServiceTypeName 1.1.8164.1.33.1.1.5
The name of the service type
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  DisplayString  

starL2TPLocalAddress 1.1.8164.1.33.1.1.6
The local address of the service
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  IpAddress  

starL2TPPeerAddress 1.1.8164.1.33.1.1.7
The peer address of the service
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  IpAddress  

starentGGSNService 1.1.8164.1.32
OBJECT IDENTIFIER    

starGGSNSerTable 1.1.8164.1.32.1
A table containing GGSN related information
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    StarGGSNSerEntry

starGGSNSerEntry 1.1.8164.1.32.1.1
The statistics for a specific GGSN service
Status: current Access: not-accessible
OBJECT-TYPE    
  StarGGSNSerEntry  

starGGSNSerVpnID 1.1.8164.1.32.1.1.1
The internal identification of the VPN (context)
Status: current Access: not-accessible
OBJECT-TYPE    
  Gauge32  

starGGSNSerSvcID 1.1.8164.1.32.1.1.2
The internal identification of this service; unique within a specific context
Status: current Access: not-accessible
OBJECT-TYPE    
  Gauge32  

starSessGGSNVpnName 1.1.8164.1.32.1.1.3
The name of this VPN (context)
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

starSessGGSNServName 1.1.8164.1.32.1.1.4
The name of this service
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

starSessGGSNPeerPort 1.1.8164.1.32.1.1.5
The Peer Port for which PATH Failure has occured
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Gauge32  

starSessGGSNPeerAddr 1.1.8164.1.32.1.1.6
The Peer Address for which PATH Failure has occured
Status: current Access: read-only
OBJECT-TYPE    
  IpAddress  

starSessGGSNImsi 1.1.8164.1.32.1.1.7
The IMSI of the subscriber
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  OCTET STRING Size(1..8)  

starSessGGSNSubsName 1.1.8164.1.32.1.1.8
The name of the subscriber
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  OCTET STRING Size(1..128)  

starSessGGSNAPNName 1.1.8164.1.32.1.1.9
The name of the APN
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  OCTET STRING Size(1..64)  

starSessGTPPGroupName 1.1.8164.1.32.1.1.10
The name of the GTPP Group
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  OCTET STRING Size(1..64)  

starSessSub1 1.1.8164.1.34
OBJECT IDENTIFIER    

starSessSub1Context 1.1.8164.1.34.1
The 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.
Status: current Access: read-write
OBJECT-TYPE    
  DisplayString  

starSessSub1NAI 1.1.8164.1.34.2
The 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.
Status: current Access: read-write
OBJECT-TYPE    
  OCTET STRING Size(1..128)  

starSessSub1MSID 1.1.8164.1.34.3
The 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.
Status: current Access: read-write
OBJECT-TYPE    
  OCTET STRING Size(1..16)  

starSessSub1IpAddr 1.1.8164.1.34.4
The 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.
Status: current Access: read-write
OBJECT-TYPE    
  IpAddress  

starSessSub1LastResult 1.1.8164.1.34.5
The 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 fetched
Status: current Access: read-only
OBJECT-TYPE    
  INTEGER unknown(0), error(1), nomatch(2), onematch(3), multimatch(4)  

starSessSub1ServiceName 1.1.8164.1.34.6
The service name of the subscriber.
Status: current Access: read-only
OBJECT-TYPE    
  OCTET STRING Size(1..63)  

starSessSub1HAIpAddr 1.1.8164.1.34.7
The HA IP address for FA MIP connections
Status: current Access: read-only
OBJECT-TYPE    
  IpAddress  

starSessSub1PeerIpAddr 1.1.8164.1.34.8
The 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 LAC
Status: current Access: read-only
OBJECT-TYPE    
  IpAddress  

starSessSub1InPackets 1.1.8164.1.34.9
The number of incoming packets for the subscriber
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starSessSub1InPacketsDropped 1.1.8164.1.34.10
The number of incoming packets dropped for the subscriber
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starSessSub1InBytes 1.1.8164.1.34.11
The count of incoming bytes for the subscriber, in kilobytes, rounded down (i.e. 1023 bytes = 0 kilobytes
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starSessSub1OutPackets 1.1.8164.1.34.12
The number of outgoing packets for the subscriber
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starSessSub1OutPacketsDropped 1.1.8164.1.34.13
The number of out going packets dropped for the subscriber
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starSessSub1OutBytes 1.1.8164.1.34.14
The count of outgoing bytes for the subscriber, in kilobytes, rounded down (i.e. 1023 bytes = 0 kilobytes
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starSessSub1Activity 1.1.8164.1.34.15
TBD
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starSessSub1State 1.1.8164.1.34.16
The state of the subscriber
Status: current Access: read-only
OBJECT-TYPE    
  INTEGER unknown(0), connecting(1), connected(2), disconnecting(3)  

starSessSub1CallID 1.1.8164.1.34.17
The internal call ID of the subscriber
Status: current Access: read-only
OBJECT-TYPE    
  Integer32  

starSessSub1ConnectTime 1.1.8164.1.34.18
The connect time for the subscriber, in UTC. The UNIX epoch (Jan 1, 1970) is used if no value is available
Status: current Access: read-only
OBJECT-TYPE    
  DateAndTime  

starSessSub1CallDuration 1.1.8164.1.34.19
The duration of the call, in seconds
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starSessSub1TimeIdle 1.1.8164.1.34.20
The idle time of the call, in seconds
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starSessSub1AccessType 1.1.8164.1.34.21
The access type for the subscriber
Status: current Access: read-only
OBJECT-TYPE    
  INTEGER unknown(0), pdsnsimpleip(1), pdsnmobileip(2), hamobileip(3), ggsnpdptypeipv4(4), ggsnpdptypeppp(5), ggsnpdptypeipv6(6), lnsl2tp(7), haipsec(8), ipsg(9), pdsnsipmip(10), mipproxyfa(11), imsa(12), bcmcs(13), ggsnmip(14), ipprobe(15), ansgw(16)  

starSessSub1AccessTech 1.1.8164.1.34.22
The access technology for the subscriber
Status: current Access: read-only
OBJECT-TYPE    
  INTEGER unknown(0), cdma1xrtt(1), cdmaevdo(2), cdmaother(3), wcdmautran(4), gprsgeran(5), gprsother(6), wirelesslan(7), ipsg(8), wimax(9), sip(10), other(11), cdmaevdoreva(12), pdif(13), phs(14), ehrpd(15), eutran(16), gan(17), hspa(18)  

starSessSub1LinkStatus 1.1.8164.1.34.23
The link status for the subscriber
Status: current Access: read-only
OBJECT-TYPE    
  INTEGER unknown(0), active(1), dormant(2)  

starSessSub1NetworkType 1.1.8164.1.34.24
The network type for the subscriber
Status: current Access: read-only
OBJECT-TYPE    
  INTEGER unknown(0), ip(1), mobileip(2), l2tp(3), proxymobileip(4), ipinip(5), gre(6), ipv6inipv4(7)  

starSessSub1CarrierID 1.1.8164.1.34.25
Carrier ID
Status: current Access: read-only
OBJECT-TYPE    
  OCTET STRING Size(0..6)  

starSessSub1ESN 1.1.8164.1.34.26
Electronic Serial Number
Status: current Access: read-only
OBJECT-TYPE    
  OCTET STRING Size(0..15)  

starSessSub1GMTTimezoneOffset 1.1.8164.1.34.27
Timezone offset from GMT, in seconds. This is a signed value
Status: current Access: read-only
OBJECT-TYPE    
  Integer32  

starSessSub1SessMgr 1.1.8164.1.34.28
The instance number of the session manager for this subscriber.
Status: current Access: read-only
OBJECT-TYPE    
  Unsigned32  

starSessSub1RemoteIPAddr 1.1.8164.1.34.29
Remote IP Address
Status: current Access: read-only
OBJECT-TYPE    
  IpAddress  

starSessSub1Card 1.1.8164.1.34.30
The card holding the session manager for this session. Use in combination with starSessSub1CPU
Status: current Access: read-only
OBJECT-TYPE    
  Integer32 1..16  

starSessSub1CPU 1.1.8164.1.34.31
The CPU holding the session manager for this session. Use in combination with starSessSub1Card
Status: current Access: read-only
OBJECT-TYPE    
  Integer32 0..3  

starSessSub1TimeIdleLeft 1.1.8164.1.34.32
The remaining idle time of the call, in seconds. A value of 0xffffffff is used if the call does not have an idle timeout
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starSessSub1TimeLeft 1.1.8164.1.34.33
The remaining session time of the call, in seconds. A value of 0xffffffff is used if the call does not have a session timeout
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starSessSub1TimeLongDurLeft 1.1.8164.1.34.34
The remaining long duration time of the call, in seconds. A value of 0xffffffff is used if the call does not have a long duration timer
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starSessSub1LongDurAction 1.1.8164.1.34.35
The action to take when the long duration timer is reached
Status: current Access: read-only
OBJECT-TYPE    
  StarLongDurTimeoutAction  

starSessSub1AlwaysOn 1.1.8164.1.34.36
Status: current Access: read-only
OBJECT-TYPE    
  INTEGER unknown(0), enabled(1), disabled(2)  

starSessSub1IPPoolName 1.1.8164.1.34.37
Status: current Access: read-only
OBJECT-TYPE    
  OCTET STRING Size(0..31)  

starSessSub1VLANID 1.1.8164.1.34.38
0 is returned if this is not applicable
Status: current Access: read-only
OBJECT-TYPE    
  Unsigned32  

starSessSub1LNSIPAddr 1.1.8164.1.34.39
Only valid if starSessSub1NetworkType is l2tp(3), otherwise 0.0.0.0
Status: current Access: read-only
OBJECT-TYPE    
  IpAddress  

starSessSub1ProxyMIP 1.1.8164.1.34.40
Status: current Access: read-only
OBJECT-TYPE    
  INTEGER unknown(0), enabled(1), disabled(2)  

starSessSub1GGSNMIP 1.1.8164.1.34.41
Status: current Access: read-only
OBJECT-TYPE    
  INTEGER unknown(0), enabled(1), disabled(2)  

starSessSub1HomeAgentIpAddr 1.1.8164.1.34.42
The 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 returned
Status: current Access: read-only
OBJECT-TYPE    
  IpAddress  

starSessSub1LocalIPAddr 1.1.8164.1.34.43
The 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 returned
Status: current Access: read-only
OBJECT-TYPE    
  IpAddress  

starSessSub1FAServiceName 1.1.8164.1.34.44
The 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)
Status: current Access: read-only
OBJECT-TYPE    
  OCTET STRING Size(1..63)  

starSessSub1FAVPNName 1.1.8164.1.34.45
The 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)
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

starSessSub1SourceVPN 1.1.8164.1.34.46
The Source VPN (Context) name.
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

starSessSub1DestVPN 1.1.8164.1.34.47
The Destination VPN (Context) name.
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

starSessSub1AAAVPN 1.1.8164.1.34.48
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

starSessSub1AAADomain 1.1.8164.1.34.49
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

starSessSub1AAAStart 1.1.8164.1.34.50
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starSessSub1AAAStop 1.1.8164.1.34.51
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starSessSub1AAAInterim 1.1.8164.1.34.52
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starSessSub1AcctSessionID 1.1.8164.1.34.53
Status: current Access: read-only
OBJECT-TYPE    
  OCTET STRING Size(0..47)  

starSessSub1AAARadiusGroup 1.1.8164.1.34.54
Status: current Access: read-only
OBJECT-TYPE    
  OCTET STRING Size(0..63)  

starSessSub1AAARadiusAuthServerIPAddr 1.1.8164.1.34.55
Status: current Access: read-only
OBJECT-TYPE    
  IpAddress  

starSessSub1AAARadiusAcctServerIPAddr 1.1.8164.1.34.56
Status: current Access: read-only
OBJECT-TYPE    
  IpAddress  

starSessSub1NASIPAddr 1.1.8164.1.34.57
NAS IP Address (D2)
Status: current Access: read-only
OBJECT-TYPE    
  IpAddress  

starSessSub1NexthopIPAddr 1.1.8164.1.34.58
Status: current Access: read-only
OBJECT-TYPE    
  IpAddress  

starSessSub1ActiveInACL 1.1.8164.1.34.59
Status: current Access: read-only
OBJECT-TYPE    
  OCTET STRING Size(0..79)  

starSessSub1ActiveOutACL 1.1.8164.1.34.60
Status: current Access: read-only
OBJECT-TYPE    
  OCTET STRING Size(0..79)  

starSessSub1ECSRulebase 1.1.8164.1.34.61
Status: current Access: read-only
OBJECT-TYPE    
  OCTET STRING Size(0..63)  

starSessSub1InPlcyGrp 1.1.8164.1.34.62
Status: current Access: read-only
OBJECT-TYPE    
  OCTET STRING Size(0..15)  

starSessSub1OutPlcyGrp 1.1.8164.1.34.63
Status: current Access: read-only
OBJECT-TYPE    
  OCTET STRING Size(0..15)  

starSessSub1DownTrafPolState 1.1.8164.1.34.64
Downlink traffic policing state
Status: current Access: read-only
OBJECT-TYPE    
  INTEGER unknown(0), enabled(1), disabled(2)  

starSessSub1DownCommDataRate 1.1.8164.1.34.65
Downlink committed data rate, in bps. This value is only valid if starSessSub1DownTrafPolState is enabled(1)
Status: current Access: read-only
OBJECT-TYPE    
  Unsigned32  

starSessSub1DownPeakDataRate 1.1.8164.1.34.66
Downlink peak data rate, in bps. This value will be 0 if the value of starSessSub1DownTrafPolState is anything other than enabled(1)
Status: current Access: read-only
OBJECT-TYPE    
  Unsigned32  

starSessSub1DownBurstSize 1.1.8164.1.34.67
Downlink burst size, in bytes. This value will be 0 if the value of starSessSub1DownTrafPolState is anything other than enabled(1)
Status: current Access: read-only
OBJECT-TYPE    
  Unsigned32  

starSessSub1DownExceedAction 1.1.8164.1.34.68
Downlink Exceed Action. This value will be notapplicable(1) if the value of starSessSub1DownTrafPolState is anything other than enabled(1)
Status: current Access: read-only
OBJECT-TYPE    
  StarQOSTPAction  

starSessSub1DownViolateAction 1.1.8164.1.34.69
Downlink Violate Action. This value will be notapplicable(1) if the value of starSessSub1DownTrafPolState is anything other than enabled(1)
Status: current Access: read-only
OBJECT-TYPE    
  StarQOSTPAction  

starSessSub1DownExceed 1.1.8164.1.34.70
Downlink packets exceeded bandwidth parameters
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starSessSub1DownViolate 1.1.8164.1.34.71
Downlink packets violated bandwidth parameters
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starSessSub1UpTrafPolState 1.1.8164.1.34.72
Uplink traffic policing state
Status: current Access: read-only
OBJECT-TYPE    
  INTEGER unknown(0), enabled(1), disabled(2)  

starSessSub1UpCommDataRate 1.1.8164.1.34.73
Uplink committed data rate, in bps. This value is only valid if starSessSub1UpTrafPolState is enabled(1)
Status: current Access: read-only
OBJECT-TYPE    
  Unsigned32  

starSessSub1UpPeakDataRate 1.1.8164.1.34.74
Uplink peak data rate, in bps. This value will be 0 if the value of starSessSub1UpTrafPolState is anything other than enabled(1)
Status: current Access: read-only
OBJECT-TYPE    
  Unsigned32  

starSessSub1UpBurstSize 1.1.8164.1.34.75
Uplink burst size, in bytes. This value will be 0 if the value of starSessSub1UpTrafPolState is anything other than enabled(1)
Status: current Access: read-only
OBJECT-TYPE    
  Unsigned32  

starSessSub1UpExceedAction 1.1.8164.1.34.76
Uplink Exceed Action. This value will be notapplicable(1) if the value of starSessSub1UpTrafPolState is anything other than enabled(1)
Status: current Access: read-only
OBJECT-TYPE    
  StarQOSTPAction  

starSessSub1UpViolateAction 1.1.8164.1.34.77
Uplink Violate Action. This value will be notapplicable(1) if the value of starSessSub1UpTrafPolState is anything other than enabled(1)
Status: current Access: read-only
OBJECT-TYPE    
  StarQOSTPAction  

starSessSub1UpExceed 1.1.8164.1.34.78
Uplink packets exceeded bandwidth parameters
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starSessSub1UpViolate 1.1.8164.1.34.79
Uplink packets violated bandwidth parameters
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starSessSub1L3TunnelingState 1.1.8164.1.34.80
Identifies if L3 tunneling is enabled. This value should be enabled(1) if starSessSub1NetworkType is ipinip(5) or gre(6)
Status: current Access: read-only
OBJECT-TYPE    
  INTEGER unknown(0), enabled(1), disabled(2)  

starSessSub1L3TunLocalIPAddr 1.1.8164.1.34.81
L3 tunnel local address. This value is valid only if starSessSub1L3TunnelState is enabled(1), other it will be 0.0.0.0
Status: current Access: read-only
OBJECT-TYPE    
  IpAddress  

starSessSub1L3TunRemoteIPAddr 1.1.8164.1.34.82
L3 tunnel remote address. This value is valid only if starSessSub1L3TunnelState is enabled(1), other it will be 0.0.0.0
Status: current Access: read-only
OBJECT-TYPE    
  IpAddress  

starSessSub1AddrViaDHCP 1.1.8164.1.34.83
Status: current Access: read-only
OBJECT-TYPE    
  INTEGER unknown(0), enabled(1), disabled(2)  

starSessSub1DHCPServName 1.1.8164.1.34.84
DHCP service name. This value is only valid if starSessSub1DHCPAddrViaDHCP is enabled(1)
Status: current Access: read-only
OBJECT-TYPE    
  OCTET STRING Size(0..63)  

starSessSub1DHCPServIPAddr 1.1.8164.1.34.85
DHCP service IP address. This value is only valid if starSessSub1DHCPAddrViaDHCP is enabled(1), otherwise it will be 0.0.0.0
Status: current Access: read-only
OBJECT-TYPE    
  IpAddress  

starSessSub1AccessLinkIPFrag 1.1.8164.1.34.86
Status: current Access: read-only
OBJECT-TYPE    
  INTEGER unkwnown(0), normal(1), dfignore(2), dffragandicmp(3)  

starSessSub1IgnoreDFBit 1.1.8164.1.34.87
Ignore DF-bit data-tunnel
Status: current Access: read-only
OBJECT-TYPE    
  INTEGER unknown(0), enabed(1), disabled(2)  

starSessSub1MIPGratARPMode 1.1.8164.1.34.88
This field is only applicable if starSessSub1AccessType is hamobileip(3) or haipsec(8)
Status: current Access: read-only
OBJECT-TYPE    
  INTEGER unkwnown(0), notapplicable(1), aggressive(2), normal(3)  

starSessSub1ExtInlSrvrProc 1.1.8164.1.34.89
The state of external inline server processing
Status: current Access: read-only
OBJECT-TYPE    
  INTEGER unknown(0), enabled(1), disabled(2)  

starSessSub1ExtInlSrvrIngrIPAddr 1.1.8164.1.34.90
The external inline server ingress IP address. This value is only valid if starSessSub1ExtInlSrvrProc is enabled(1)
Status: current Access: read-only
OBJECT-TYPE    
  IpAddress  

starSessSub1ExtInlSrvrIngrVLANTag 1.1.8164.1.34.91
The external inline server ingress VLAN tag. This value is only valid if starSessSub1ExtInlSrvrProc is enabled(1)
Status: current Access: read-only
OBJECT-TYPE    
  Unsigned32  

starSessSub1ExtInlSrvrEgrIPAddr 1.1.8164.1.34.92
The external inline server egress IP address. This value is only valid if starSessSub1ExtInlSrvrProc is enabled(1)
Status: current Access: read-only
OBJECT-TYPE    
  IpAddress  

starSessSub1ExtInlSrvrEgrVLANTag 1.1.8164.1.34.93
The external inline server egress VLAN tag. This value is only valid if starSessSub1ExtInlSrvrProc is enabled(1)
Status: current Access: read-only
OBJECT-TYPE    
  Unsigned32  

starSessSub1ExtInlSrvrVPNName 1.1.8164.1.34.94
The external inline server context (VPN). This value is only valid if starSessSub1ExtInlSrvrProc is enabled(1)
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

starSessSub1RadAcctMode 1.1.8164.1.34.95
Radius Accounting Mode
Status: current Access: read-only
OBJECT-TYPE    
  INTEGER unknown(0), flowbasedaux(1), flowbasedall(2), flowbasednone(3), sessionbased(4)  

starSessSub1InBytesDropped 1.1.8164.1.34.96
The count of incoming bytes dropped for the subscriber, in kilobytes, rounded down (i.e. 1023 bytes = 0 kilobytes
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starSessSub1OutBytesDropped 1.1.8164.1.34.97
The count of outgoing bytes dropped for the subscriber, in kilobytes, rounded down (i.e. 1023 bytes = 0 kilobytes
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starSessSub1PeakBPSTx 1.1.8164.1.34.98
Peak rate from user, in bytes per second
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starSessSub1PeakBPSRx 1.1.8164.1.34.99
Peak rate to user, in bytes per second
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starSessSub1AveBPSTx 1.1.8164.1.34.100
Average rate from user, in bytes per second
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starSessSub1AveBPSRx 1.1.8164.1.34.101
Average rate to user, in bytes per second
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starSessSub1SustBPSTx 1.1.8164.1.34.102
Sustained rate from user, in bytes per second
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starSessSub1SustBPSRx 1.1.8164.1.34.103
Sustained rate to user, in bytes per second
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starSessSub1PeakPPSTx 1.1.8164.1.34.104
Peak rate from user, in packets per second
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starSessSub1PeakPPSRx 1.1.8164.1.34.105
Peak rate to user, in packets per second
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starSessSub1AvePPSTx 1.1.8164.1.34.106
Average rate from user, in packets per second
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starSessSub1AvePPSRx 1.1.8164.1.34.107
Average rate to user, in packets per second
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starSessSub1SustPPSTx 1.1.8164.1.34.108
Sustained rate from user, in packets per second
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starSessSub1SustPPSRx 1.1.8164.1.34.109
Sustained rate to user, in packets per second
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starSessSub1ActivePct 1.1.8164.1.34.110
Link online/active percentage
Status: current Access: read-only
OBJECT-TYPE    
  Integer32 0..100  

starSessSub1IPv4BadHdr 1.1.8164.1.34.111
IPv4 Bad Headers
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starSessSub1IPv4TtlExceeded 1.1.8164.1.34.112
IPv4 Total Exceeded
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starSessSub1IPv4FragSent 1.1.8164.1.34.113
IPv4 Fragments sent
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starSessSub1IPv4FragFail 1.1.8164.1.34.114
IPv4 Could Not Fragment errors
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starSessSub1IPv4InACLDrop 1.1.8164.1.34.115
IPv4 Input ACL Drops
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starSessSub1IPv4OutACLDrop 1.1.8164.1.34.116
IPv5 Output ACL Drops
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starSessSub1IPv4InCSSDownDrop 1.1.8164.1.34.117
IPv4 Input CSS Down Drops
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starSessSub1IPv4OutCSSDownDrop 1.1.8164.1.34.118
IPv4 Output CSS Down Drops
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starSessSub1IPv4OutXOFFDropPkt 1.1.8164.1.34.119
IPv4 Output XOFF Packets Drop
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starSessSub1IPv4OutXOFFDropByte 1.1.8164.1.34.120
IPv4 Output XOFF Bytes Drop
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starSessSub1IPv4SrcViol 1.1.8164.1.34.121
IPv4 Source Violations
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starSessSub1IPv4ProxyDNSRedir 1.1.8164.1.34.122
IPv4 Proxy-DNS Redirect
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starSessSub1IPv4SrcProxyDNSPThru 1.1.8164.1.34.123
IPv4 Proxy-DNS Pass-Thru
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starSessSub1IPv4ProxyDNSDrop 1.1.8164.1.34.124
IPv4 Proxy-DNS Drop
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starSessSub1IPv4SrcViolNoAcct 1.1.8164.1.34.125
IPv4 Source Violations No Account
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starSessSub1IPv4SrcViolIgnored 1.1.8164.1.34.126
IPv4 Source Violations Ignored
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starSessSub1ExtInlSrvrTxPkt 1.1.8164.1.34.127
Packets transmitted to inline server. This value is valid only if the value of starSessSub1ExtInlSrvrProc is enabled(1)
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starSessSub1ExtInlSrvrRxPkt 1.1.8164.1.34.128
Packets received from inline server. This value is valid only if the value of starSessSub1ExtInlSrvrProc is enabled(1)
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starSessSub1IPv4ICMPDropPkt 1.1.8164.1.34.129
IPv4 ICMP Packets dropped
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starSessSub1TunnelType 1.1.8164.1.34.130
Tunnel Type
Status: current Access: read-only
OBJECT-TYPE    
  INTEGER unknown(0), none(1), pptp(2), l2tp(3), ah(4), ipinip(5), esp(6), gre(7)  

starSessSub1IPSECTunDownDropPkt 1.1.8164.1.34.131
Pool IPSEC tunnel down packets dropped. This value is only valid if the value of starSessSub1TunnelType is esp(6)
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starSessSub1IPSECFlowID 1.1.8164.1.34.132
IP Pool IPSEC flow id. This value is only valid if the value of starSessSub1TunnelType is esp(6)
Status: current Access: read-only
OBJECT-TYPE    
  Integer32  

starSessSub1DormancyTotal 1.1.8164.1.34.133
Dormancy total. This value is not valid if the value of starSessSub1AccessType is ggsnpdptypeipv4(4) or ggsnpdptypeppp(5)
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starSessSub1HandoffTotal 1.1.8164.1.34.134
Handoff total. This value is not valid if the value of starSessSub1AccessType is ggsnpdptypeipv4(4) or ggsnpdptypeppp(5)
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starSessSub1AccessFlows 1.1.8164.1.34.135
Access flows
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starSessSub1TFT 1.1.8164.1.34.136
Number of TFTs
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starSessSub1NASPort 1.1.8164.1.34.137
NAS port
Status: current Access: read-only
OBJECT-TYPE    
  Integer32  

starSessSub1CorrID 1.1.8164.1.34.139
ThreeGPP2-correlation-id (C2)
Status: current Access: read-only
OBJECT-TYPE    
  OCTET STRING Size(0..47)  

starSessSub1L2TPPeerIPAddr 1.1.8164.1.34.140
L2TP Peer address. This value is only valid if the value of starSessSub1NetworkType is l2tp(3)
Status: current Access: read-only
OBJECT-TYPE    
  IpAddress  

starSessSub1IPv4EarlyPDURecv 1.1.8164.1.34.141
IPv4 early PDU received
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starentNwReachServer 1.1.8164.1.35
OBJECT IDENTIFIER    

starNwReachTable 1.1.8164.1.35.1
A table containing Network Reacheable Server information
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    StarNwReachEntry

starNwReachEntry 1.1.8164.1.35.1.1
Information for a specific Ntw Reachable Server
Status: current Access: not-accessible
OBJECT-TYPE    
  StarNwReachEntry  

starNwReachName 1.1.8164.1.35.1.1.1
The Name for this Network Reacheable Server
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  OCTET STRING Size(1..16)  

starNwReachSrvrAddr 1.1.8164.1.35.1.1.2
The IP Address for the Network Reacheable Server
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  IpAddress  

starentIPSEC 1.1.8164.1.36
OBJECT IDENTIFIER    

starIPSECContextName 1.1.8164.1.36.1
The name of a context
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  DisplayString  

starIPSECGroupName 1.1.8164.1.36.2
The name of a crypto group
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  DisplayString  

starIPSECTunLocalIpAddr 1.1.8164.1.36.3
The local IP Address for an IPSEC tunnel
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  DisplayString  

starIPSECTunRemoteIpAddr 1.1.8164.1.36.4
The remote IP Address for an IPSEC tunnel
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  DisplayString  

starIPSECPolicyName 1.1.8164.1.36.5
An IPSEC policy name
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  DisplayString  

starIPSECDynPolicyType 1.1.8164.1.36.6
An IPSEC dynamic policy type. Note that the value test(5) is used only for internal testing
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  INTEGER unknown(0), manual(1), isakmp(2), subscribertemplate(3), subscribertunnel(4), test(5), dynamic(6)  

starIPSECDynPolicyPayloadType 1.1.8164.1.36.7
An IPSEC dynamic policy payload type
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  INTEGER unknown(0), control(1), data(2), ipip(3), gre(4), test(5)  

starIPSECLocalGateway 1.1.8164.1.36.8
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  IpAddress  

starIPSECRemoteGateway 1.1.8164.1.36.9
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  IpAddress  

starentSIPRoute 1.1.8164.1.37
OBJECT IDENTIFIER    

starSIPRouteTable 1.1.8164.1.37.1
A table containing SIPRoute related information
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    StarSIPRouteEntry

starSIPRouteEntry 1.1.8164.1.37.1.1
The statistics for a specific SIPRoute service
Status: current Access: not-accessible
OBJECT-TYPE    
  StarSIPRouteEntry  

starSIPRouteVpnID 1.1.8164.1.37.1.1.1
The internal identification of the VPN (context)
Status: current Access: not-accessible
OBJECT-TYPE    
  Gauge32  

starSIPRouteVpnName 1.1.8164.1.37.1.1.2
The name of this VPN (context)
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

starSIPRouteVmgName 1.1.8164.1.37.1.1.3
The name of this VMG (context)
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

starSIPRouteAsName 1.1.8164.1.37.1.1.4
The name of this AS (context)
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

starSIPRouteDestPartyNum 1.1.8164.1.37.1.1.5
The dest. party number
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

starSIPRouteReqNum 1.1.8164.1.37.1.1.6
The request number
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

starentRPServiceOption 1.1.8164.1.38
OBJECT IDENTIFIER    

starRPServiceOptionTable 1.1.8164.1.38.1
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    StarRPServiceOptionEntry

starRPServiceOptionEntry 1.1.8164.1.38.1.1
Status: current Access: not-accessible
OBJECT-TYPE    
  StarRPServiceOptionEntry  

starRPServiceOptionNum 1.1.8164.1.38.1.1.1
Status: current Access: not-accessible
OBJECT-TYPE    
  Integer32 1..255  

starRPServiceOptionCalls 1.1.8164.1.38.1.1.2
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starentPCFStats 1.1.8164.1.39
OBJECT IDENTIFIER    

starPCFStatTable 1.1.8164.1.39.1
A table of per-PCF statistics
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    StarPCFStatEntry

starPCFStatEntry 1.1.8164.1.39.1.1
The statistics for a specific PCF
Status: current Access: not-accessible
OBJECT-TYPE    
  StarPCFStatEntry  

starPCFStatVpnID 1.1.8164.1.39.1.1.1
Status: current Access: not-accessible
OBJECT-TYPE    
  Gauge32  

starPCFStatIpAddr 1.1.8164.1.39.1.1.2
Status: current Access: not-accessible
OBJECT-TYPE    
  IpAddress  

starPCFStatVpnName 1.1.8164.1.39.1.1.3
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

starPCFStatRxPkts 1.1.8164.1.39.1.1.4
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPCFStatTxPkts 1.1.8164.1.39.1.1.5
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPCFStatRxBytes 1.1.8164.1.39.1.1.6
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPCFStatTxBytes 1.1.8164.1.39.1.1.7
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPCFStatTotalSessions 1.1.8164.1.39.1.1.8
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPCFStatCurrentSessions 1.1.8164.1.39.1.1.9
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starPCFStatCurrentActiveSessions 1.1.8164.1.39.1.1.10
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starPCFStatCurrentDormantSessions 1.1.8164.1.39.1.1.11
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starPCFStatCurrentSIPConnected 1.1.8164.1.39.1.1.12
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starPCFStatCurrentMIPConnected 1.1.8164.1.39.1.1.13
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starPCFStatCurrentPMIPConnected 1.1.8164.1.39.1.1.14
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starPCFStatCurrentL2TPLACConnected 1.1.8164.1.39.1.1.15
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starPCFStatCurrentOtherConnected 1.1.8164.1.39.1.1.16
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starPCFTable 1.1.8164.1.39.2
A table of per service PCF statistics
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    StarPCFEntry

starPCFEntry 1.1.8164.1.39.2.1
The statistics for a specific PCF per service
Status: current Access: not-accessible
OBJECT-TYPE    
  StarPCFEntry  

starPCFSvcID 1.1.8164.1.39.2.1.1
The 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
Status: current Access: not-accessible
OBJECT-TYPE    
  StarShortID  

starPCFIpAddr 1.1.8164.1.39.2.1.2
The PCF IP address
Status: current Access: not-accessible
OBJECT-TYPE    
  IpAddress  

starPCFVpnID 1.1.8164.1.39.2.1.3
The internal identification of the VPN (context)
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starPCFVpnName 1.1.8164.1.39.2.1.4
The VPN (context) name
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

starPCFServName 1.1.8164.1.39.2.1.5
The name of this service
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

starPCFRrqRcvd 1.1.8164.1.39.2.1.6
Number of rrq received
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPCFRrqAccepted 1.1.8164.1.39.2.1.7
Number of rrq accepted
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPCFRrqDenied 1.1.8164.1.39.2.1.8
Number of rrq denied
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPCFRrqDiscarded 1.1.8164.1.39.2.1.9
Number of rrq discarded
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPCFInitialRrqRcvd 1.1.8164.1.39.2.1.10
Initial rrq received
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPCFInitialRrqAccepted 1.1.8164.1.39.2.1.11
Initial rrq accepted
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPCFIntraPDSNActiveHORrqAccepted 1.1.8164.1.39.2.1.12
Intra PDSN active handoff rrq accepted
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPCFIntraPDSNDormantHORrqAccepted 1.1.8164.1.39.2.1.13
Intra PDSN dormant handoff rrq accepted
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPCFInterPDSNHORrqAccepted 1.1.8164.1.39.2.1.14
Inter PDSN handoff rrq accpted
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPCFInitialRrqDenied 1.1.8164.1.39.2.1.15
Intial rrq denied
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPCFInitialRrqDiscarded 1.1.8164.1.39.2.1.16
Intial rrq discarded
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPCFRenewRrqRcvd 1.1.8164.1.39.2.1.17
Renew rrq received
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPCFRenewRrqAccepted 1.1.8164.1.39.2.1.18
Renew rrq accepted
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPCFRenewActiveRrqAccepted 1.1.8164.1.39.2.1.19
Renew active rrq accepted
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPCFRenewDormantRrqAccepted 1.1.8164.1.39.2.1.20
Renew dormant rrq accepted
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPCFRenewRrqDenied 1.1.8164.1.39.2.1.21
Renew rrq denied
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPCFRenewRrqDiscarded 1.1.8164.1.39.2.1.22
Renew rrq discarded
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPCFDeregRrqRcvd 1.1.8164.1.39.2.1.23
Deregistration rrq received
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPCFDeregRrqAccepted 1.1.8164.1.39.2.1.24
Deregistration rrq accepted
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPCFDeregDormantRrqAccepted 1.1.8164.1.39.2.1.25
Deregistration dormant rrq accepted
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPCFDeregRrqDenied 1.1.8164.1.39.2.1.26
Deregistration rrq denied
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPCFDeregRrqDiscarded 1.1.8164.1.39.2.1.27
Deregistration rrq discarded
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPCFIntraPDSNActiveAnidHORrqAccepted 1.1.8164.1.39.2.1.28
Intra PDSN active anid handoff rrq accepted
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPCFIntraPDSNDormantAnidHORrqAccepted 1.1.8164.1.39.2.1.29
Intra PDSN dormant anidhandoff rrq accepted
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPCFDeniedUnSpeReason 1.1.8164.1.39.2.1.30
Denied unspecified reason
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPCFDeniedAdmProh 1.1.8164.1.39.2.1.31
Denied admin prohibited
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPCFDeniedInsufResource 1.1.8164.1.39.2.1.32
Denied insufficient resources
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPCFDeniedMobNodeAuthFail 1.1.8164.1.39.2.1.33
Denied mobile node authentication failure
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPCFDeniedIdentMismatch 1.1.8164.1.39.2.1.34
Denied identification mismatch
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPCFDeniedPoorFormedReq 1.1.8164.1.39.2.1.35
Denied poor formed request
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPCFDeniedUnknownPDSNAddr 1.1.8164.1.39.2.1.36
Denied unknown PDSN address
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPCFDeniedRevTunnelUnavail 1.1.8164.1.39.2.1.37
Denied rev tunnel unavilable
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPCFDeniedRevTunnelRequire 1.1.8164.1.39.2.1.38
Denied rev tunnel required
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPCFDeniedUnrecogVendorId 1.1.8164.1.39.2.1.39
Denied unrecognized vendor id
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPCFDeniedSessionClosed 1.1.8164.1.39.2.1.40
Denied session closed
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPCFDeniedBsnSessionInfoUnavail 1.1.8164.1.39.2.1.41
Denied bsn session information unavilable
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPCFRegUpdTransmitted 1.1.8164.1.39.2.1.42
Registration updates transmitted
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPCFRegUpdAccepted 1.1.8164.1.39.2.1.43
Registration updates accepted
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPCFRegUpdateRpLifetimeExpiry 1.1.8164.1.39.2.1.44
Registration update rp life time expiry
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPCFRegUpdateUpperLayerIntiated 1.1.8164.1.39.2.1.45
Registration update upper layer intiated
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPCFRegUpdateOtherReason 1.1.8164.1.39.2.1.46
Registration update other reason
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPCFRegUpdateHORelease 1.1.8164.1.39.2.1.47
Registration update handoff release
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPCFRegUpdateSessmgrDied 1.1.8164.1.39.2.1.48
Registration update sessmgr denied
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPCFAuxA10ConnectionsSetup 1.1.8164.1.39.2.1.49
Aux a10 connections setup
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPCFSessionsDenied 1.1.8164.1.39.2.1.50
Number of sessions denied
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPCFSessionsInit 1.1.8164.1.39.2.1.51
Number of sessions initiated
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPCFSessionsReneg 1.1.8164.1.39.2.1.52
Number of PCF sessions renegotiated
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPCFDiscLcpRemote 1.1.8164.1.39.2.1.53
Disconnect reason lcp remote
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPCFDiscRpRemote 1.1.8164.1.39.2.1.54
Disconnect reason rp remote
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPCFDiscRpLocal 1.1.8164.1.39.2.1.55
Disconnect reason rp local
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPCFDiscMaxIpcpRetr 1.1.8164.1.39.2.1.56
Disconnect reason ppp maximum ipcp retries
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPCFDiscMaxIpv6cpRetr 1.1.8164.1.39.2.1.57
Disconnect reason max ipv6cp retries
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPCFDiscMaxLcpRetr 1.1.8164.1.39.2.1.58
Disconnect reason max lcp retries
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPCFDiscAuthFail 1.1.8164.1.39.2.1.59
Disconnect reason authentication failure
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPCFDiscSessSetupTimeout 1.1.8164.1.39.2.1.60
Disconnect reason session setup timeout
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPCFDiscFlowAddFail 1.1.8164.1.39.2.1.61
Disconnect reason flow add failure
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPCFDiscInvDestContext 1.1.8164.1.39.2.1.62
Disconnect reason invalid destination context
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPCFDiscLcpOptFail 1.1.8164.1.39.2.1.63
Disconnect reason lcp option failure
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPCFDiscIpcpOptFail 1.1.8164.1.39.2.1.64
Disconnect reason lcp option failure
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPCFDiscIpv6cpOptFail 1.1.8164.1.39.2.1.65
Disconnect reason ipv6cp option failure
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPCFDiscNoRemIpAddr 1.1.8164.1.39.2.1.66
Disconnect reason no ip remote ip address
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPCFDiscDetectionFail 1.1.8164.1.39.2.1.67
Disconnect reason detection failure
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPCFDiscMisc 1.1.8164.1.39.2.1.68
Disconnect reason misallaneous
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPCFCurrentSessions 1.1.8164.1.39.2.1.69
Current sessions
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starPCFSessionsSetup 1.1.8164.1.39.2.1.70
Session setup
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPCFSessionsRelsese 1.1.8164.1.39.2.1.71
Sessions release
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPCFCurrentRevaSessions 1.1.8164.1.39.2.1.72
Current reva sessions
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starPCFRevaSessionsSetup 1.1.8164.1.39.2.1.73
Reva session setup
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPCFRevaSessionsRelsese 1.1.8164.1.39.2.1.74
Reva session release
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starentSIPRouteServer 1.1.8164.1.40
OBJECT IDENTIFIER    

starSIPRouteServerTable 1.1.8164.1.40.1
A table containing SIPRouteServer related information
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    StarSIPRouteServerEntry

starSIPRouteServerEntry 1.1.8164.1.40.1.1
The statistics for a specific SIPRouteServer
Status: current Access: not-accessible
OBJECT-TYPE    
  StarSIPRouteServerEntry  

starSIPRouteServerVpnID 1.1.8164.1.40.1.1.1
The internal identification of the VPN (context)
Status: current Access: not-accessible
OBJECT-TYPE    
  Gauge32  

starSIPRouteServerVpnName 1.1.8164.1.40.1.1.2
The name of this VPN (context)
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

starSIPRouteServerVmgName 1.1.8164.1.40.1.1.3
The name of this VMG (context)
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

starSIPRouteServerAsName 1.1.8164.1.40.1.1.4
The name of this AS (context)
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

starSIPRouteServerIpAddr 1.1.8164.1.40.1.1.5
The Sip Route Server IP Address
Status: current Access: read-only
OBJECT-TYPE    
  IpAddress  

starentVIMService 1.1.8164.1.41
OBJECT IDENTIFIER    

starVIMServiceTable 1.1.8164.1.41.1
A table containing VIM's Service related information
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    StarVIMServiceEntry

starVIMServiceEntry 1.1.8164.1.41.1.1
The statistics for a specific VIM's Service
Status: current Access: not-accessible
OBJECT-TYPE    
  StarVIMServiceEntry  

starVIMServiceVpnID 1.1.8164.1.41.1.1.1
The internal identification of the VPN (context)
Status: current Access: not-accessible
OBJECT-TYPE    
  Gauge32  

starVIMServiceVpnName 1.1.8164.1.41.1.1.2
The name of this VPN (context)
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

starVIMServiceInstanceId 1.1.8164.1.41.1.1.3
The VIM Instance ID
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Unsigned32  

starVIMServiceFMDMaxCallRate 1.1.8164.1.41.1.1.4
Configured FMD max call rate
Status: current Access: read-only
OBJECT-TYPE    
  Unsigned32  

starVIMServiceFMDContinuousLoadCount 1.1.8164.1.41.1.1.5
Configured FMD continuous load count
Status: current Access: read-only
OBJECT-TYPE    
  Unsigned32  

starentGSS 1.1.8164.1.42
OBJECT IDENTIFIER    

starGSSClusterName 1.1.8164.1.42.1
The name of the Storage Server Cluster
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  DisplayString  

starGSSClusterNodeName 1.1.8164.1.42.2
The name of a node within a Storage Server Cluster
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  DisplayString  

starGSSClusterRgName 1.1.8164.1.42.3
Resource Group
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  DisplayString  

starGSSClusterRsName 1.1.8164.1.42.4
Resource Name
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  DisplayString  

starGSSClusterNodeState 1.1.8164.1.42.5
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  DisplayString  

starGSSClusterPrevOnlineNode 1.1.8164.1.42.6
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  DisplayString  

starGSSClusterFromNode 1.1.8164.1.42.7
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  DisplayString  

starGSSClusterToNode 1.1.8164.1.42.8
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  DisplayString  

starGSSDiskPath 1.1.8164.1.42.9
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  DisplayString  

starGSSTransportPath 1.1.8164.1.42.10
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  DisplayString  

starGSSIPMPGroupName 1.1.8164.1.42.11
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  DisplayString  

starGSSInterfaceName 1.1.8164.1.42.12
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  DisplayString  

starentPDIFSys 1.1.8164.1.43
OBJECT IDENTIFIER    

starPDIFSysStatus 1.1.8164.1.43.1
The 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 configured
Status: current Access: read-only
OBJECT-TYPE    
  INTEGER unknown(0), noservice(1), active(2), temporary(3), outofservice(4)  

starPDIFSysNumService 1.1.8164.1.43.2
The number of PDIF services configured
Status: current Access: read-only
OBJECT-TYPE    
  Unsigned32  

starPDIFSysSessCurrent 1.1.8164.1.43.3
The number of current PDIF sessions for this chassis
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starPDIFSysSessCurrActive 1.1.8164.1.43.4
The number of currently active PDIF sessions for this chassis
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starPDIFSysSessCurrDormant 1.1.8164.1.43.5
The number of currently dormant PDIF sessions for this chassis
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starPDIFSysSessTtlSetup 1.1.8164.1.43.6
The cumulative total number of PDIF sessions that has been setup
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPDIFSysChildSACurrent 1.1.8164.1.43.7
The number of current PDIF child SAs for this chassis
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starentPDIFService 1.1.8164.1.44
OBJECT IDENTIFIER    

starPDIFTable 1.1.8164.1.44.1
A table of per-service PDIF information
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    StarPDIFEntry

starPDIFEntry 1.1.8164.1.44.1.1
The information for a PDIF service
Status: current Access: not-accessible
OBJECT-TYPE    
  StarPDIFEntry  

starPDIFSvcID 1.1.8164.1.44.1.1.1
The service identification is made up from first 8 chars of context name and first 8 chars of service name separated by (:)
Status: current Access: not-accessible
OBJECT-TYPE    
  StarShortID  

starPDIFVpnID 1.1.8164.1.44.1.1.2
The 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)
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starPDIFVpnName 1.1.8164.1.44.1.1.3
The VPN (context) name
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

starPDIFServName 1.1.8164.1.44.1.1.4
The name of this service
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

starPDIFStatus 1.1.8164.1.44.1.1.5
The 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.
Status: current Access: read-only
OBJECT-TYPE    
  INTEGER unknown(0), inservice(1), outofservice(2)  

starPDIFSessCurrent 1.1.8164.1.44.1.1.6
The number of current sessions for this PDIF service.
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starPDIFSessRemain 1.1.8164.1.44.1.1.7
A 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.
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starPDIFSessCurrentActive 1.1.8164.1.44.1.1.8
The number of currently active sessions for this PDIF service
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starPDIFSessCurrentDormant 1.1.8164.1.44.1.1.9
The 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.
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starPDIFSessCurrentIpv6Active 1.1.8164.1.44.1.1.10
The 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.
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starPDIFSessCurrentIpv6Dormant 1.1.8164.1.44.1.1.11
The 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.
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starPDIFSessCurrentIpv4Active 1.1.8164.1.44.1.1.12
The 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.
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starPDIFSessCurrentIpv4Dormant 1.1.8164.1.44.1.1.13
The 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.
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starPDIFBindIpAddress 1.1.8164.1.44.1.1.14
The bind IP address for this PDIF service
Status: current Access: read-only
OBJECT-TYPE    
  IpAddress  

starPDIFBindIpPort 1.1.8164.1.44.1.1.15
The bind IP port for this PDIF service
Status: current Access: read-only
OBJECT-TYPE    
  Integer32  

starPDIFBindSlot 1.1.8164.1.44.1.1.16
The physical slot number for the physical port which holds the interface bound to the starPDIFBindIpAddress address.
Status: current Access: read-only
OBJECT-TYPE    
  Integer32  

starPDIFBindPort 1.1.8164.1.44.1.1.17
The physical port number for the physical port which holds the interface bound to the starPDIFBindIpAddress address.
Status: current Access: read-only
OBJECT-TYPE    
  Integer32  

starentPDGSys 1.1.8164.1.62
OBJECT IDENTIFIER    

starPDGSysStatus 1.1.8164.1.62.1
The 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 configured
Status: current Access: read-only
OBJECT-TYPE    
  INTEGER unknown(0), noservice(1), active(2), temporary(3), outofservice(4)  

starPDGSysNumService 1.1.8164.1.62.2
The number of PDG services configured
Status: current Access: read-only
OBJECT-TYPE    
  Unsigned32  

starPDGSysSessCurrent 1.1.8164.1.62.3
The number of current PDG sessions for this chassis
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starPDGSysSessCurrActive 1.1.8164.1.62.4
The number of currently active PDG sessions for this chassis
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starPDGSysSessCurrDormant 1.1.8164.1.62.5
The number of currently dormant PDG sessions for this chassis
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starPDGSysSessTtlSetup 1.1.8164.1.62.6
The cumulative total number of PDG sessions that has been setup
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starPDGSysChildSACurrent 1.1.8164.1.62.7
The number of current PDG child SAs for this chassis
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starentPDGService 1.1.8164.1.63
OBJECT IDENTIFIER    

starPDGTable 1.1.8164.1.63.1
A table of per-service PDG information
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    StarPDGEntry

starPDGEntry 1.1.8164.1.63.1.1
The information for a PDG service
Status: current Access: not-accessible
OBJECT-TYPE    
  StarPDGEntry  

starPDGSvcID 1.1.8164.1.63.1.1.1
The service identification is made up from first 8 chars of context name and first 8 chars of service name separated by (:)
Status: current Access: not-accessible
OBJECT-TYPE    
  StarShortID  

starPDGVpnID 1.1.8164.1.63.1.1.2
The 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)
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starPDGVpnName 1.1.8164.1.63.1.1.3
The VPN (context) name
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

starPDGServName 1.1.8164.1.63.1.1.4
The name of this service
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

starPDGStatus 1.1.8164.1.63.1.1.5
The 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.
Status: current Access: read-only
OBJECT-TYPE    
  INTEGER unknown(0), inservice(1), outofservice(2)  

starPDGSessCurrent 1.1.8164.1.63.1.1.6
The number of current sessions for this PDG service.
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starPDGSessRemain 1.1.8164.1.63.1.1.7
A 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.
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starPDGSessCurrentActive 1.1.8164.1.63.1.1.8
The number of currently active sessions for this PDG service
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starPDGSessCurrentDormant 1.1.8164.1.63.1.1.9
The number of currently dormant sessions for this PDG service
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starPDGSessCurrentIpv6Active 1.1.8164.1.63.1.1.10
The 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.
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starPDGSessCurrentIpv6Dormant 1.1.8164.1.63.1.1.11
The 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.
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starPDGSessCurrentIpv4Active 1.1.8164.1.63.1.1.12
The 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.
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starPDGSessCurrentIpv4Dormant 1.1.8164.1.63.1.1.13
The 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.
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starPDGBindIpAddress 1.1.8164.1.63.1.1.14
The bind IP address for this PDG service
Status: current Access: read-only
OBJECT-TYPE    
  IpAddress  

starPDGBindIpPort 1.1.8164.1.63.1.1.15
The bind IP port for this PDG service
Status: current Access: read-only
OBJECT-TYPE    
  Integer32  

starPDGBindSlot 1.1.8164.1.63.1.1.16
The physical slot number for the physical port which holds the interface bound to the starPDGBindIpAddress address.
Status: current Access: read-only
OBJECT-TYPE    
  Integer32  

starPDGBindPort 1.1.8164.1.63.1.1.17
The physical port number for the physical port which holds the interface bound to the starPDGBindIpAddress address.
Status: current Access: read-only
OBJECT-TYPE    
  Integer32  

starentHNBGWService 1.1.8164.1.65
OBJECT IDENTIFIER    

starHNBGWServTable 1.1.8164.1.65.1
A table containing HNBGW related information
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    StarHNBGWServEntry

starHNBGWServEntry 1.1.8164.1.65.1.1
The statistics for a specific HNBGW service
Status: current Access: not-accessible
OBJECT-TYPE    
  StarHNBGWServEntry  

starHNBGWServVpnID 1.1.8164.1.65.1.1.1
The internal identification of the VPN (context)
Status: current Access: not-accessible
OBJECT-TYPE    
  Gauge32  

starHNBGWServSvcID 1.1.8164.1.65.1.1.2
The internal identification of this service; unique within a specific context
Status: current Access: not-accessible
OBJECT-TYPE    
  Gauge32  

starSessHNBGWVpnName 1.1.8164.1.65.1.1.3
The name of this VPN (context)
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

starSessHNBGWServName 1.1.8164.1.65.1.1.4
The name of this Service
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

starSessHNBGWCsNwName 1.1.8164.1.65.1.1.5
The name of the CS NW
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

starSessHNBGWPsNwName 1.1.8164.1.65.1.1.6
The name of the PS NW
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

starSessHNBGWSgsnPtCd 1.1.8164.1.65.1.1.7
SGSN Point Code
Status: current Access: read-only
OBJECT-TYPE    
  Integer32  

starSessHNBGWMscPtCd 1.1.8164.1.65.1.1.8
MSC Point Code
Status: current Access: read-only
OBJECT-TYPE    
  Integer32  

starentALCAPService 1.1.8164.1.66
OBJECT IDENTIFIER    

starALCAPServTable 1.1.8164.1.66.1
A table containing ALCAP relate information
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    StarALCAPServEntry

starALCAPServEntry 1.1.8164.1.66.1.1
The statistics for a specific ALCAP service
Status: current Access: not-accessible
OBJECT-TYPE    
  StarALCAPServEntry  

starALCAPSerVpnID 1.1.8164.1.66.1.1.1
The internal identification of the VPN (context)
Status: current Access: not-accessible
OBJECT-TYPE    
  Gauge32  

starALCAPSerSvcID 1.1.8164.1.66.1.1.2
The internal identification of this service; unique within a specific context
Status: current Access: not-accessible
OBJECT-TYPE    
  Gauge32  

starSessALCAPVpnName 1.1.8164.1.66.1.1.3
The name of this VPN (context)
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

starSessALCAPServName 1.1.8164.1.66.1.1.4
The name of this Service
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

starSessALCAPAAL2NodeName 1.1.8164.1.66.1.1.5
The name of the AAL2 Node
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

starSessALCAPPathId 1.1.8164.1.66.1.1.6
The path id of AAL2 path
Status: current Access: read-only
OBJECT-TYPE    
  Integer32  

starentFNGSys 1.1.8164.1.60
OBJECT IDENTIFIER    

starFNGSysStatus 1.1.8164.1.60.1
The 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 configured
Status: current Access: read-only
OBJECT-TYPE    
  INTEGER unknown(0), noservice(1), active(2), temporary(3), outofservice(4)  

starFNGSysNumService 1.1.8164.1.60.2
The number of FNG services configured
Status: current Access: read-only
OBJECT-TYPE    
  Unsigned32  

starFNGSysSessCurrent 1.1.8164.1.60.3
The number of current FNG sessions for this chassis
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starFNGSysSessCurrActive 1.1.8164.1.60.4
The number of currently active FNG sessions for this chassis
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starFNGSysSessCurrDormant 1.1.8164.1.60.5
The number of currently dormant FNG sessions for this chassis
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starFNGSysSessTtlSetup 1.1.8164.1.60.6
The cumulative total number of FNG sessions that has been setup
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

starFNGSysChildSACurrent 1.1.8164.1.60.7
The number of current FNG child SAs for this chassis
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starentFNGService 1.1.8164.1.61
OBJECT IDENTIFIER    

starFNGTable 1.1.8164.1.61.1
A table of per-service FNG information
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    StarFNGEntry

starFNGEntry 1.1.8164.1.61.1.1
The information for a FNG service
Status: current Access: not-accessible
OBJECT-TYPE    
  StarFNGEntry  

starFNGSvcID 1.1.8164.1.61.1.1.1
The service identification is made up from first 8 chars of context name and first 8 chars of service name separated by (:)
Status: current Access: not-accessible
OBJECT-TYPE    
  StarShortID  

starFNGVpnID 1.1.8164.1.61.1.1.2
The 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)
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starFNGVpnName 1.1.8164.1.61.1.1.3
The VPN (context) name
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

starFNGServName 1.1.8164.1.61.1.1.4
The name of this service
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

starFNGStatus 1.1.8164.1.61.1.1.5
The 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.
Status: current Access: read-only
OBJECT-TYPE    
  INTEGER unknown(0), inservice(1), outofservice(2)  

starFNGSessCurrent 1.1.8164.1.61.1.1.6
The number of current sessions for this FNG service.
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starFNGSessRemain 1.1.8164.1.61.1.1.7
A 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.
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starFNGSessCurrentActive 1.1.8164.1.61.1.1.8
The number of currently active sessions for this FNG service
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starFNGSessCurrentDormant 1.1.8164.1.61.1.1.9
The number of currently dormant sessions for this FNG service
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starFNGSessCurrentIpv6Active 1.1.8164.1.61.1.1.10
The 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.
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starFNGSessCurrentIpv6Dormant 1.1.8164.1.61.1.1.11
The 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.
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starFNGSessCurrentIpv4Active 1.1.8164.1.61.1.1.12
The 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.
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starFNGSessCurrentIpv4Dormant 1.1.8164.1.61.1.1.13
The 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.
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starFNGBindIpAddress 1.1.8164.1.61.1.1.14
The bind IP address for this FNG service
Status: current Access: read-only
OBJECT-TYPE    
  IpAddress  

starFNGBindIpPort 1.1.8164.1.61.1.1.15
The bind IP port for this FNG service
Status: current Access: read-only
OBJECT-TYPE    
  Integer32  

starFNGBindSlot 1.1.8164.1.61.1.1.16
The physical slot number for the physical port which holds the interface bound to the starFNGBindIpAddress address.
Status: current Access: read-only
OBJECT-TYPE    
  Integer32  

starFNGBindPort 1.1.8164.1.61.1.1.17
The physical port number for the physical port which holds the interface bound to the starFNGBindIpAddress address.
Status: current Access: read-only
OBJECT-TYPE    
  Integer32  

starentSGSNService 1.1.8164.1.45
OBJECT IDENTIFIER    

starSGSNSerTable 1.1.8164.1.45.1
A table containing SGSN related information
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    StarSGSNSerEntry

starSGSNSerEntry 1.1.8164.1.45.1.1
The statistics for a specific SGSN service
Status: current Access: not-accessible
OBJECT-TYPE    
  StarSGSNSerEntry  

starSGSNSerVpnID 1.1.8164.1.45.1.1.1
The internal identification of the VPN (context)
Status: current Access: not-accessible
OBJECT-TYPE    
  Gauge32  

starSGSNSerSvcID 1.1.8164.1.45.1.1.2
The internal identification of this service; unique within a specific context
Status: current Access: not-accessible
OBJECT-TYPE    
  Gauge32  

starSessSGSNVpnName 1.1.8164.1.45.1.1.3
The name of this VPN (context)
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

starSessSGSNServName 1.1.8164.1.45.1.1.4
The name of this service
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

starSessSGSNMcc 1.1.8164.1.45.1.1.5
Mobile Country Code
Status: current Access: read-only
OBJECT-TYPE    
  OCTET STRING Size(1..3)  

starSessSGSNMnc 1.1.8164.1.45.1.1.6
Mobile Network Code
Status: current Access: read-only
OBJECT-TYPE    
  OCTET STRING Size(1..3)  

starSessSGSNRncId 1.1.8164.1.45.1.1.7
The Id of the RNC
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starSessSGSNHlrNum 1.1.8164.1.45.1.1.8
The Id of the HLR
Status: current Access: read-only
OBJECT-TYPE    
  OCTET STRING Size(1..16)  

starentSS7Rd 1.1.8164.1.46
OBJECT IDENTIFIER    

starSS7RdTable 1.1.8164.1.46.1
A table containing SS7Rd related information
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    StarSS7RdEntry

starSS7RdEntry 1.1.8164.1.46.1.1
The statistics for a specific ss7rd
Status: current Access: not-accessible
OBJECT-TYPE    
  StarSS7RdEntry  

starSS7rdId 1.1.8164.1.46.1.1.1
SS7 Routing Domain identification
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Gauge32  

starSS7Pc 1.1.8164.1.46.1.1.2
Point Code
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starSS7M3UAPsId 1.1.8164.1.46.1.1.3
Peer Server identification
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starSS7M3UAPspId 1.1.8164.1.46.1.1.4
Peer Server process identification
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starSS7MTP3LinkSetId 1.1.8164.1.46.1.1.5
MTP3 LinkSet Identifier
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starSS7MTP3LinkId 1.1.8164.1.46.1.1.6
MTP3 Link Identifier
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starSS7SCTPSelfAddr 1.1.8164.1.46.1.1.7
The self end point IP Address
Status: current Access: read-only
OBJECT-TYPE    
  IpAddress  

starSS7SCTPPeerAddr 1.1.8164.1.46.1.1.8
The IP Address of the PeerNode
Status: current Access: read-only
OBJECT-TYPE    
  IpAddress  

starSS7SCTPSelfPort 1.1.8164.1.46.1.1.9
The self end point sctp port
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starSS7SCTPPeerPort 1.1.8164.1.46.1.1.10
The peer end point sctp port
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starSS7CongLevel 1.1.8164.1.46.1.1.11
Congestion Level Value
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starSS7LocalCong 1.1.8164.1.46.1.1.12
Local Congestion Value
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starSS7CauseString 1.1.8164.1.46.1.1.13
Cause string for failure
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

starentSccpNw 1.1.8164.1.47
OBJECT IDENTIFIER    

starSccpNwTable 1.1.8164.1.47.1
A table containing Sccp Network related information
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    StarSccpNwEntry

starSccpNwEntry 1.1.8164.1.47.1.1
The statistics for a specific Sccp Network
Status: current Access: not-accessible
OBJECT-TYPE    
  StarSccpNwEntry  

starSccpNwId 1.1.8164.1.47.1.1.1
SCCP Network Id
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Gauge32  

starSccpSsn 1.1.8164.1.47.1.1.2
Sub System Number
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starentSGTPService 1.1.8164.1.48
OBJECT IDENTIFIER    

starSGTPSerTable 1.1.8164.1.48.1
A table containing SGTP Service related information
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    StarSGTPSerEntry

starSGTPSerEntry 1.1.8164.1.48.1.1
The statistics for a specific SGTP service
Status: current Access: not-accessible
OBJECT-TYPE    
  StarSGTPSerEntry  

starSGTPSerVpnID 1.1.8164.1.48.1.1.1
The internal identification of the VPN (context)
Status: current Access: not-accessible
OBJECT-TYPE    
  Gauge32  

starSGTPSerSvcID 1.1.8164.1.48.1.1.2
The internal identification of this service; unique within a specific context
Status: current Access: not-accessible
OBJECT-TYPE    
  Gauge32  

starSGTPVpnName 1.1.8164.1.48.1.1.3
The name of this VPN (context)
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

starSGTPServName 1.1.8164.1.48.1.1.4
The name of this service
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

starSGTPSelfAddr 1.1.8164.1.48.1.1.5
The IP Address of the SGSN
Status: current Access: read-only
OBJECT-TYPE    
  IpAddress  

starSGTPPeerAddr 1.1.8164.1.48.1.1.6
The IP Address of the PeerNode
Status: current Access: read-only
OBJECT-TYPE    
  IpAddress  

starSGTPSelfPort 1.1.8164.1.48.1.1.7
The self end point sgtp port
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starSGTPPeerPort 1.1.8164.1.48.1.1.8
The peer end point sgtp port
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starentIPMSServer 1.1.8164.1.49
OBJECT IDENTIFIER    

starIPMSServerTable 1.1.8164.1.49.1
A table containing information on IPMS Servers
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    StarIPMSServerEntry

starIPMSServerEntry 1.1.8164.1.49.1.1
Information about a particular IPMS Server
Status: current Access: not-accessible
OBJECT-TYPE    
  StarIPMSServerEntry  

starIPMSServerVpnID 1.1.8164.1.49.1.1.1
The internal identification of the VPN (context)
Status: current Access: not-accessible
OBJECT-TYPE    
  Gauge32  

starIPMSServerAddr 1.1.8164.1.49.1.1.2
The IP address of the IPMS server within this VPN (context)
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  IpAddress  

starIPMSServerVpnName 1.1.8164.1.49.1.1.3
The name of this VPN (context)
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

starentCert 1.1.8164.1.50
OBJECT IDENTIFIER    

starCertTable 1.1.8164.1.50.1
A table containing information on X.509 Certificates
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    StarCertEntry

starCertEntry 1.1.8164.1.50.1.1
Information about a particular X.509 Certificate
Status: current Access: not-accessible
OBJECT-TYPE    
  StarCertEntry  

starCertSerialNumber 1.1.8164.1.50.1.1.1
The serial number for the certificate
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  DisplayString  

starCertExpiryTime 1.1.8164.1.50.1.1.2
The Certificate expiration date/time
Status: current Access: read-only
OBJECT-TYPE    
  DateAndTime  

starCertIssuer 1.1.8164.1.50.1.1.3
The Certificate issuer
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

starentFile 1.1.8164.1.51
OBJECT IDENTIFIER    

starFileTable 1.1.8164.1.51.1
A table of files stored on a mass storage device
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    StarFileEntry

starFileEntry 1.1.8164.1.51.1.1
Information about a particular file on a mass storage device
Status: current Access: not-accessible
OBJECT-TYPE    
  StarFileEntry  

starFileName 1.1.8164.1.51.1.1.1
The name (full path) of the file
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  DisplayString  

starFileApplication 1.1.8164.1.51.1.1.2
The application that owns this file
Status: current Access: read-only
OBJECT-TYPE    
  INTEGER unknown(0), systemfile(1), cdrmod(2)  

starentFTPServ 1.1.8164.1.52
OBJECT IDENTIFIER    

starFTPServTable 1.1.8164.1.52.1
A table of FTP servers configured
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    StarFTPServEntry

starFTPServEntry 1.1.8164.1.52.1.1
Information about a particular FTP Server
Status: current Access: not-accessible
OBJECT-TYPE    
  StarFTPServEntry  

starFTPServVpnID 1.1.8164.1.52.1.1.1
The internal identification of the VPN (context) used to reach this FTP server
Status: current Access: not-accessible
OBJECT-TYPE    
  Unsigned32  

starFTPServIpAddr 1.1.8164.1.52.1.1.2
The IP address of the FTP server
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  IpAddress  

starFTPServVpnName 1.1.8164.1.52.1.1.3
The name of the VPN (context)
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

starentCSCFPeerServer 1.1.8164.1.53
OBJECT IDENTIFIER    

starCSCFPeerServerTable 1.1.8164.1.53.1
A table containing PeerServer related information
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    StarCSCFPeerServerEntry

starCSCFPeerServerEntry 1.1.8164.1.53.1.1
The statistics for a specific CSCF service
Status: current Access: not-accessible
OBJECT-TYPE    
  StarCSCFPeerServerEntry  

starCSCFPeerServerVpnID 1.1.8164.1.53.1.1.1
The internal identification of the VPN (context)
Status: current Access: not-accessible
OBJECT-TYPE    
  Gauge32  

starCSCFPeerServerSvcID 1.1.8164.1.53.1.1.2
The internal identification of this CSCF service; unique within a specific context
Status: current Access: not-accessible
OBJECT-TYPE    
  Gauge32  

starCSCFPeerServerVpnName 1.1.8164.1.53.1.1.3
The name of this VPN (context)
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

starCSCFPeerServerSvcName 1.1.8164.1.53.1.1.4
The name of this CSCF-service
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

starCSCFPeerServerListName 1.1.8164.1.53.1.1.5
The name of the cscf-peer-server
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

starCSCFPeerServerName 1.1.8164.1.53.1.1.6
The name of the cscf-peer-server
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

starCSCFPeerServerState 1.1.8164.1.53.1.1.7
The state of the cscf-peer-server
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

starentSDH 1.1.8164.1.54
OBJECT IDENTIFIER    

starSDHTable 1.1.8164.1.54.1
A table ...
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    StarSDHEntry

starSDHEntry 1.1.8164.1.54.1.1
Information about a specific ...
Status: current Access: not-accessible
OBJECT-TYPE    
  StarSDHEntry  

starSDHSlot 1.1.8164.1.54.1.1.1
The slot number for this port
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Integer32 17..48  

starSDHPort 1.1.8164.1.54.1.1.2
The port number within this slot
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Integer32 1..8  

starSDHOperState 1.1.8164.1.54.1.1.3
A bitmask indicating the state of SDH layer SCT. 0x0000 Good 0x0001 lais 0x0002 linesd 0x0004 linesf 0x0010 lof 0x0020 los 0x0040 msrdi
Status: current Access: read-only
OBJECT-TYPE    
  Integer32  

starentSDHPath 1.1.8164.1.55
OBJECT IDENTIFIER    

starSDHPathTable 1.1.8164.1.55.1
A table ...
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    StarSDHPathEntry

starSDHPathEntry 1.1.8164.1.55.1.1
Information about a specific ...
Status: current Access: not-accessible
OBJECT-TYPE    
  StarSDHPathEntry  

starSDHPathSlot 1.1.8164.1.55.1.1.1
The slot number for this port
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Integer32 17..48  

starSDHPathPort 1.1.8164.1.55.1.1.2
The port number within this slot
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Integer32 1..8  

starSDHPathNum 1.1.8164.1.55.1.1.3
The path number
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Integer32 1..3  

starSDHPathOperState 1.1.8164.1.55.1.1.4
A bitmask indicating the state of SDH Path HOP. 0x0000 Good 0x0001 hopathsd 0x0002 hopathsf 0x0020 ppdi 0x0040 prdi 0x0080 perdi 0x0100 perdival 0x0200 perdivaloff
Status: current Access: read-only
OBJECT-TYPE    
  Integer32  

starentE1Trib 1.1.8164.1.56
OBJECT IDENTIFIER    

starE1TribTable 1.1.8164.1.56.1
A table ...
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    StarE1TribEntry

starE1TribEntry 1.1.8164.1.56.1.1
Information about a specific ...
Status: current Access: not-accessible
OBJECT-TYPE    
  StarE1TribEntry  

starE1TribSlot 1.1.8164.1.56.1.1.1
The slot number for this port
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Integer32 17..48  

starE1TribPort 1.1.8164.1.56.1.1.2
The port number within this slot
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Integer32 1..8  

starE1TribPath 1.1.8164.1.56.1.1.3
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Integer32 1..3  

starE1TribTug2 1.1.8164.1.56.1.1.4
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Integer32 1..7  

starE1TribTu12 1.1.8164.1.56.1.1.5
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Integer32 1..3  

starE1TribOperStateLOP 1.1.8164.1.56.1.1.6
A bitmask indicating the state of SDH layer LOP. 0x0000 Good 0x0001 lopathsd 0x0002 lopathsf 0x0100 erdi 0x0200 rdi 0x0400 lop 0x0800 ais 0x1000 lom
Status: current Access: read-only
OBJECT-TYPE    
  Integer32  

starE1TribOperState 1.1.8164.1.56.1.1.7
A 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 ts16aisd
Status: current Access: read-only
OBJECT-TYPE    
  Integer32  

starentFractE1Trib 1.1.8164.1.58
OBJECT IDENTIFIER    

starFractE1TribTable 1.1.8164.1.58.1
A table ...
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    StarFractE1TribEntry

starFractE1TribEntry 1.1.8164.1.58.1.1
Information about a specific ...
Status: current Access: not-accessible
OBJECT-TYPE    
  StarFractE1TribEntry  

starFractE1TribSlot 1.1.8164.1.58.1.1.1
The slot number for this port
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Integer32 17..48  

starFractE1TribPort 1.1.8164.1.58.1.1.2
The port number within this slot
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Integer32 1..8  

starFractE1TribPath 1.1.8164.1.58.1.1.3
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Integer32 1..3  

starFractE1TribTug2 1.1.8164.1.58.1.1.4
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Integer32 1..7  

starFractE1TribTu12 1.1.8164.1.58.1.1.5
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Integer32 1..3  

starFractE1TribBundNum 1.1.8164.1.58.1.1.6
Status: obsolete Access: not-accessible
OBJECT-TYPE    
  Integer32 0..31  

starFractE1TribTimeslots 1.1.8164.1.58.1.1.7
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  


starGPRSLinkTable 1.1.8164.1.57.1
A table containing GPRSService Link related information
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    StarGPRSLinkEntry

starGPRSLinkEntry 1.1.8164.1.57.1.1
The link statistics for a specific GPRS service
Status: current Access: not-accessible
OBJECT-TYPE    
  StarGPRSLinkEntry  

starGPRSNsei 1.1.8164.1.57.1.1.1
Network Service Entity Indentifier
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Gauge32  

starGPRSNsvci 1.1.8164.1.57.1.1.2
Network Service Virtual Circuit Identifier
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starGPRSBvci 1.1.8164.1.57.1.1.3
Base Station System GPRS(General Packet Radio Service) Protocl Virtual Circuit Identifier
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starentStorage 1.1.8164.1.59
OBJECT IDENTIFIER    

starStorageTable 1.1.8164.1.59.1
A table of mass storage devices
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    StarStorageEntry

starStorageEntry 1.1.8164.1.59.1.1
Information about a particular file on a mass storage device
Status: current Access: not-accessible
OBJECT-TYPE    
  StarStorageEntry  

starStorageSlot 1.1.8164.1.59.1.1.1
The slot number of the card holding this storage device
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Integer32 1..16  

starStorageName 1.1.8164.1.59.1.1.2
The name of the storage device
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  DisplayString  

starStorageDeviceType 1.1.8164.1.59.1.1.3
The 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 array
Status: current Access: read-only
OBJECT-TYPE    
  INTEGER unknown(0), independent(1), raid(2), raidmember(3)  

starentMMES1Assoc 1.1.8164.1.67
OBJECT IDENTIFIER    

starMMES1AssocTable 1.1.8164.1.67.1
A table of MME S1 Associations
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    StarMMES1AssocEntry

starMMES1AssocEntry 1.1.8164.1.67.1.1
Information about a particular MME S1 Association
Status: current Access: not-accessible
OBJECT-TYPE    
  StarMMES1AssocEntry  

starMMES1AssocSvcID 1.1.8164.1.67.1.1.1
The 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 (:)
Status: current Access: not-accessible
OBJECT-TYPE    
  StarMediumID  

starMMES1AssocENBID 1.1.8164.1.67.1.1.2
The identification of the eNodeB
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  StarENBID  

starMMES1AssocVpnName 1.1.8164.1.67.1.1.3
The name of this VPN (context)
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

starMMES1AssocServName 1.1.8164.1.67.1.1.4
The name of this MME Service
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

starentMMES1Path 1.1.8164.1.70
OBJECT IDENTIFIER    

starMMES1PathTable 1.1.8164.1.70.1
A table of MME S1 Path
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    StarMMES1PathEntry

starMMES1PathEntry 1.1.8164.1.70.1.1
Information about a particular MME S1 Pathiation
Status: current Access: not-accessible
OBJECT-TYPE    
  StarMMES1PathEntry  

starMMES1PathSvcID 1.1.8164.1.70.1.1.1
The 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 (:)
Status: current Access: not-accessible
OBJECT-TYPE    
  StarMediumID  

starMMES1PathENBID 1.1.8164.1.70.1.1.2
The identification of the eNodeB
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  StarENBID  

starMMES1PathVpnName 1.1.8164.1.70.1.1.3
The name of this VPN (context)
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

starMMES1PathServName 1.1.8164.1.70.1.1.4
The name of this MME Service
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

starMMES1PathSelfAddr 1.1.8164.1.70.1.1.5
Interface IP Address
Status: current Access: read-only
OBJECT-TYPE    
  IpAddress  

starMMES1PathSelfPort 1.1.8164.1.70.1.1.6
Self port number
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starMMES1PathPeerAddr 1.1.8164.1.70.1.1.7
Interface IP Address
Status: current Access: read-only
OBJECT-TYPE    
  IpAddress  

starMMES1PathPeerPort 1.1.8164.1.70.1.1.8
Peer port number
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

starentTraps 1.1.8164.2
OBJECT IDENTIFIER    

starCardTempOverheat 1.1.8164.2.1
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starCardTempOK 1.1.8164.2.2
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starCardReset 1.1.8164.2.3
A reset operation has been invoked on the card. This trap is obsolete.
Status: obsolete Access: read-only
NOTIFICATION-TYPE    

starCardRebootRequest 1.1.8164.2.4
A 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starCardUp 1.1.8164.2.5
The card is up (operational)
Status: current Access: read-only
NOTIFICATION-TYPE    

starCardVoltageFailure 1.1.8164.2.6
A 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starCardRemoved 1.1.8164.2.7
A 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starCardInserted 1.1.8164.2.8
A card has been inserted into the chassis.
Status: current Access: read-only
NOTIFICATION-TYPE    

starCardBootFailed 1.1.8164.2.9
A 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starCardFailed 1.1.8164.2.10
The card has failed and is no longer operational. This trap is obsolete and has been replaced with more specific traps to identify specific failures.
Status: obsolete Access: read-only
NOTIFICATION-TYPE    

starCardSWFailed 1.1.8164.2.11
A unrecoverable software error has occured on the card. This trap is obsolete and has been replaced with more specific traps to identify specific failures.
Status: obsolete Access: read-only
NOTIFICATION-TYPE    

starCardRCCFailed 1.1.8164.2.12
The RCC has failed. Probable Cause: A hardware failure on the RCC card. This trap is obsolete.
Status: obsolete Access: read-only
NOTIFICATION-TYPE    

starCardMismatch 1.1.8164.2.13
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starCardFailureLEDOn 1.1.8164.2.14
The failure LED is illuminated on the card. This trap is obsolete and has been replaced with more specific traps for specific failures.
Status: obsolete Access: read-only
NOTIFICATION-TYPE    

starCardFailureLEDOff 1.1.8164.2.15
The 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.
Status: obsolete Access: read-only
NOTIFICATION-TYPE    

starCardPACMigrateStart 1.1.8164.2.16
A 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 completed
Status: deprecated Access: read-only
NOTIFICATION-TYPE    

starCardPACMigrateComplete 1.1.8164.2.17
A 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.
Status: deprecated Access: read-only
NOTIFICATION-TYPE    

starCardPACMigrateFailed 1.1.8164.2.18
A 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.
Status: deprecated Access: read-only
NOTIFICATION-TYPE    

starCardSPCSwitchoverStart 1.1.8164.2.19
An 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.
Status: deprecated Access: read-only
NOTIFICATION-TYPE    

starCardSPCSwitchoverComplete 1.1.8164.2.20
An 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.
Status: deprecated Access: read-only
NOTIFICATION-TYPE    

starCardSPCSwitchoverFailed 1.1.8164.2.21
An 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.
Status: deprecated Access: read-only
NOTIFICATION-TYPE    

starFanFailed 1.1.8164.2.22
One 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starFanRemoved 1.1.8164.2.23
A 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starFanInserted 1.1.8164.2.24
A fan tray has been inserted
Status: current Access: read-only
NOTIFICATION-TYPE    

starLogThreshold 1.1.8164.2.25
A system log has reached its maximum size. This trap is obsolete.
Status: obsolete Access: read-only
NOTIFICATION-TYPE    

starCPUBusy 1.1.8164.2.26
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starCPUMemoryLow 1.1.8164.2.27
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starCPUMemoryFailed 1.1.8164.2.28
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starCPUFailed 1.1.8164.2.29
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starCPUWatchDogExpired 1.1.8164.2.30
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starNPUARPPoolExhausted 1.1.8164.2.31
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starPowerFilterUnitFailed 1.1.8164.2.32
A 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.
Status: deprecated Access: read-only
NOTIFICATION-TYPE    

starPowerFilterUnitUnavail 1.1.8164.2.33
A 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starPowerFilterUnitAvail 1.1.8164.2.34
A 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starAlertsDisabled 1.1.8164.2.37
The 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starAlertsEnabled 1.1.8164.2.38
The sending of SNMP Traps has been reenabled
Status: current Access: read-only
NOTIFICATION-TYPE    

starAAAAuthServerUnreachable 1.1.8164.2.39
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starAAAAuthServerReachable 1.1.8164.2.40
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starAAAAuthServerMisconfigured 1.1.8164.2.41
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starAAAAccServerUnreachable 1.1.8164.2.42
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starAAAAccServerReachable 1.1.8164.2.43
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starAAAAccServerMisconfigured 1.1.8164.2.44
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starLogMsg 1.1.8164.2.45
A log message. This trap is used only for debugging.
Status: current Access: read-only
NOTIFICATION-TYPE    

starPDSNServiceStart 1.1.8164.2.46
A PDSN Service has started Action to be Taken: No action required
Status: current Access: read-only
NOTIFICATION-TYPE    

starPDSNServiceStop 1.1.8164.2.47
A 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starHAServiceStart 1.1.8164.2.48
An HA Service has started Action to be Taken: No action required
Status: current Access: read-only
NOTIFICATION-TYPE    

starHAServiceStop 1.1.8164.2.49
An 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starFAServiceStart 1.1.8164.2.50
An FA Service has started Action to be Taken: No action required
Status: current Access: read-only
NOTIFICATION-TYPE    

starFAServiceStop 1.1.8164.2.51
An 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starCLISessionStart 1.1.8164.2.52
An interactive CLI session has started A starCLISessionEnd notification will be sent when the CLI session is terminated.
Status: current Access: read-only
NOTIFICATION-TYPE    

starCLISessionEnd 1.1.8164.2.53
An 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starCritTaskFailed 1.1.8164.2.54
A 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starCardActive 1.1.8164.2.55
The card is now active.
Status: current Access: read-only
NOTIFICATION-TYPE    

starLACServiceStart 1.1.8164.2.56
A LAC Service has started Action to be Taken: No action required
Status: current Access: read-only
NOTIFICATION-TYPE    

starLACServiceStop 1.1.8164.2.57
A 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starLNSServiceStart 1.1.8164.2.58
A LNS Service has started Action to be Taken: No Action Required
Status: current Access: read-only
NOTIFICATION-TYPE    

starLNSServiceStop 1.1.8164.2.59
A 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starCardDown 1.1.8164.2.60
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starGGSNServiceStart 1.1.8164.2.63
A GGSN Service has started Action to be Taken: No action required
Status: current Access: read-only
NOTIFICATION-TYPE    

starGGSNServiceStop 1.1.8164.2.64
A 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starLicenseExceeded 1.1.8164.2.65
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starSubscriberLimit 1.1.8164.2.66
The 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starSessionRejectNoResource 1.1.8164.2.67
A 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starLongDurTimerExpiry 1.1.8164.2.68
The 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starClosedRPServiceStart 1.1.8164.2.69
Closed RP Service has started Action to be Taken: No action required
Status: current Access: read-only
NOTIFICATION-TYPE    

starClosedRPServiceStop 1.1.8164.2.70
Closed 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starGtpcPathFailure 1.1.8164.2.71
GTP Control Path Failure.
Status: current Access: read-only
NOTIFICATION-TYPE    

starGtpuPathFailure 1.1.8164.2.72
GTP Data Path Failure.
Status: current Access: read-only
NOTIFICATION-TYPE    

starManagerFailure 1.1.8164.2.73
Software 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starEISServerAlive 1.1.8164.2.74
EIS Server alive
Status: current Access: read-only
NOTIFICATION-TYPE    

starEISServerDead 1.1.8164.2.75
EIS 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starCgfAlive 1.1.8164.2.76
GTPP CGF Server Alive.
Status: current Access: read-only
NOTIFICATION-TYPE    

starCgfDead 1.1.8164.2.77
GTPP 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starStorageServerAlive 1.1.8164.2.78
GTPP Storage Server is Alive.
Status: current Access: read-only
NOTIFICATION-TYPE    

starStorageServerDead 1.1.8164.2.79
GTPP 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starGgsnInitiatedUpdtFailed 1.1.8164.2.80
GGSN 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starCongestion 1.1.8164.2.81
A 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starCongestionClear 1.1.8164.2.82
A congestion condition has cleared
Status: current Access: read-only
NOTIFICATION-TYPE    

starServiceLossPTACs 1.1.8164.2.83
A 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starServiceLossLC 1.1.8164.2.84
A 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starServiceLossSPIO 1.1.8164.2.85
A 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starIPSPAllAddrsFree 1.1.8164.2.86
All 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starPCFUnreachable 1.1.8164.2.87
A 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starDhcpAlive 1.1.8164.2.88
DHCP Server Alive.
Status: current Access: read-only
NOTIFICATION-TYPE    

starDhcpDead 1.1.8164.2.89
DHCP 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starNTPPeerUnreachable 1.1.8164.2.90
NTP 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starNTPSyncLost 1.1.8164.2.91
NTP 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starL2TPTunnelDownPeerUnreachable 1.1.8164.2.92
L2TP 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starCardStandby 1.1.8164.2.93
The card is now standby.
Status: current Access: read-only
NOTIFICATION-TYPE    

starLicenseUnderLimit 1.1.8164.2.94
Usage is now under the licensed session limit.
Status: current Access: read-only
NOTIFICATION-TYPE    

starIPSECPriTunDown 1.1.8164.2.95
IPSEC Primary Tunnel Down
Status: current Access: read-only
NOTIFICATION-TYPE    

starIPSECPriTunUp 1.1.8164.2.96
IPSEC Primary Tunnel Up
Status: current Access: read-only
NOTIFICATION-TYPE    

starIPSECSecTunDown 1.1.8164.2.97
IPSEC Secondary Tunnel Down
Status: current Access: read-only
NOTIFICATION-TYPE    

starIPSECSecTunUp 1.1.8164.2.98
IPSEC Secondary Tunnel Up
Status: current Access: read-only
NOTIFICATION-TYPE    

starIPSECTunSwitchFail 1.1.8164.2.99
IPSEC Tunnel Switchover failed or unable to be attempted
Status: current Access: read-only
NOTIFICATION-TYPE    

starIPSECTunSwitchComplete 1.1.8164.2.100
IPSEC Tunnel Switchover complete
Status: current Access: read-only
NOTIFICATION-TYPE    

starNwReachServerAlive 1.1.8164.2.101
Nw Reacheable Server alive
Status: current Access: read-only
NOTIFICATION-TYPE    

starNwReachServerDead 1.1.8164.2.102
Nw 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starStorageServerUnackedGcdrVolPurge 1.1.8164.2.103
GTPP 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starStorageServerUnackedGcdrFileGen 1.1.8164.2.104
GTPP 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starNTPPeerReachable 1.1.8164.2.105
NTP 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starNTPSyncEstablished 1.1.8164.2.106
NTP 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starSIPServiceStart 1.1.8164.2.107
A SIP service has started Action to be Taken: No action required
Status: current Access: read-only
NOTIFICATION-TYPE    

starSIPServiceStop 1.1.8164.2.108
A SIP service has stopped Action to be Taken: No action required
Status: current Access: read-only
NOTIFICATION-TYPE    

starVIMServiceStart 1.1.8164.2.109
A VIM service has started Action to be taken: No action required
Status: current Access: read-only
NOTIFICATION-TYPE    

starVIMServiceStop 1.1.8164.2.110
A 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starCHATCONFServiceStart 1.1.8164.2.111
A CHAT/CONF service has started Action to be taken: No action required
Status: current Access: read-only
NOTIFICATION-TYPE    

starCHATCONFServiceStop 1.1.8164.2.112
A 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starSIPRouteNomatch 1.1.8164.2.113
SIP 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starL3AddrUnreachable 1.1.8164.2.114
A L3 Address is unreachable through the specific slot and port. Action to be taken: No action required
Status: current Access: read-only
NOTIFICATION-TYPE    

starSWUpgradeStart 1.1.8164.2.115
An operator has begun to upgrade the software on the chassis.
Status: current Access: read-only
NOTIFICATION-TYPE    

starSWUpgradeComplete 1.1.8164.2.116
An operator-initiated software upgrade has been completed.
Status: current Access: read-only
NOTIFICATION-TYPE    

starSWUpgradeAborted 1.1.8164.2.117
An operator-initiated software upgrade has been aborted.
Status: current Access: read-only
NOTIFICATION-TYPE    

starBGPPeerSessionUp 1.1.8164.2.118
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starBGPPeerSessionDown 1.1.8164.2.119
The 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starSRPActive 1.1.8164.2.120
The SRP Chassis Status is now Active. Action to be Taken: No action is required.
Status: current Access: read-only
NOTIFICATION-TYPE    

starSRPStandby 1.1.8164.2.121
The SRP Chassis Status is now Standby. Action to be Taken: No action is required.
Status: current Access: read-only
NOTIFICATION-TYPE    

starBGPPeerReachable 1.1.8164.2.122
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starBGPPeerUnreachable 1.1.8164.2.123
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starSRPAAAReachable 1.1.8164.2.124
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starSRPAAAUnreachable 1.1.8164.2.125
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starSRPSwitchoverInitiated 1.1.8164.2.126
An SRP (ICSR) Switchover operation has been initiated by an operator. Action to be Taken: Verify that the switchover was a planned operator action.
Status: current Access: read-only
NOTIFICATION-TYPE    

starSRPCheckpointFailure 1.1.8164.2.127
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starSRPConfigOutOfSync 1.1.8164.2.128
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starSRPConfigInSync 1.1.8164.2.129
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starGESwitchFailure 1.1.8164.2.130
A 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starSIPRouteServerAvailable 1.1.8164.2.131
SIP route server is available Action to be taken: None
Status: current Access: read-only
NOTIFICATION-TYPE    

starSIPRouteServerUnavailable 1.1.8164.2.132
SIP 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starFMDMaxCallRateReached 1.1.8164.2.133
FMD 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starFMDCallRateUnderControl 1.1.8164.2.134
FMD call rate under control Action to be taken: None
Status: current Access: read-only
NOTIFICATION-TYPE    

starStorageServerCPUBusy 1.1.8164.2.135
GTPP 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starStorageServerCPUNormal 1.1.8164.2.136
GTPP Storage Server CPU usage has returned to a normal range. Note that this is an external server, not part of the ST16.
Status: current Access: read-only
NOTIFICATION-TYPE    

starStorageServerDiskSpaceLow 1.1.8164.2.137
GTPP 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starStorageServerDiskSpaceOK 1.1.8164.2.138
GTPP Storage Server available disk space to a normal range. Note that this is an external server, not part of the ST16.
Status: current Access: read-only
NOTIFICATION-TYPE    

starCardSPOFAlarm 1.1.8164.2.139
The 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starCardSPOFClear 1.1.8164.2.140
The identified card is no longer a Single Point of Failure (SPOF)
Status: current Access: read-only
NOTIFICATION-TYPE    

starStorageServerOldGcdrPending 1.1.8164.2.141
GTPP 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starStorageServerOldGcdrCleared 1.1.8164.2.142
GCDR 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starLoginFailure 1.1.8164.2.143
A login failure occurred attempting to establish a CLI or FTP session.
Status: current Access: read-only
NOTIFICATION-TYPE    

starIPSGServiceStart 1.1.8164.2.144
A IP Services Gateway (IPSG) Service has started Action to be Taken: No action required
Status: current Access: read-only
NOTIFICATION-TYPE    

starIPSGServiceStop 1.1.8164.2.145
A 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starHAUnreachable 1.1.8164.2.146
A monitored HA is unreachable from the identified FA Service. Condition Clear Alarm: A starHAReachable notification will be generated when the HA becomes reachable
Status: current Access: read-only
NOTIFICATION-TYPE    

starHAReachable 1.1.8164.2.147
A monitored HA is now reachable. A starHAReachable notification is only generated for monitored HA's which previously were marked unreachable.
Status: current Access: read-only
NOTIFICATION-TYPE    

starASNGWServiceStart 1.1.8164.2.148
A WiMAX ASN Gateway (ASNGW) Service has started Action to be Taken: No action required
Status: current Access: read-only
NOTIFICATION-TYPE    

starASNGWServiceStop 1.1.8164.2.149
A 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starTaskFailed 1.1.8164.2.150
A 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starTaskRestart 1.1.8164.2.151
A non-critical task has restarted after an earlier failure. Actions to be Taken: None
Status: current Access: read-only
NOTIFICATION-TYPE    

starCSCFServiceStart 1.1.8164.2.152
An CSCF Service has started Action to be Taken: No action required
Status: current Access: read-only
NOTIFICATION-TYPE    

starCSCFServiceStop 1.1.8164.2.153
An 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starDhcpServiceStarted 1.1.8164.2.154
A DHCP Service has started Action to be Taken: No action required
Status: current Access: read-only
NOTIFICATION-TYPE    

starDhcpServiceStopped 1.1.8164.2.155
A 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starContFiltDBError 1.1.8164.2.156
The 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starContFiltDBErrorClear 1.1.8164.2.157
The Content Filtering OPTCMDB file error removed. Action to be Taken: No action required
Status: current Access: read-only
NOTIFICATION-TYPE    

starBLDBError 1.1.8164.2.158
The 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starBLDBErrorClear 1.1.8164.2.159
The Blacklisting OPTBLDB file error removed. Action to be Taken: No action required
Status: current Access: read-only
NOTIFICATION-TYPE    

starContFiltDBUpgradeError 1.1.8164.2.160
The 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starContFiltDBUpgradeErrorClear 1.1.8164.2.161
The Content Filtering OPTCMDB file error removed. Action to be Taken: No action required
Status: current Access: read-only
NOTIFICATION-TYPE    

starBLDBUpgradeError 1.1.8164.2.162
The 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starBLDBUpgradeErrorClear 1.1.8164.2.163
The Blacklisting OPTBLDB file error removed. Action to be Taken: No action required
Status: current Access: read-only
NOTIFICATION-TYPE    

starIPSECDynTunUp 1.1.8164.2.164
IPSEC Dynamic Tunnel Up. Action to be Taken: No action required
Status: current Access: read-only
NOTIFICATION-TYPE    

starIPSECDynTunDown 1.1.8164.2.165
IPSEC 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starHeartbeat 1.1.8164.2.166
Periodic 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starOverloadSystem 1.1.8164.2.167
A 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starOverloadSystemClear 1.1.8164.2.168
A system-wide congestion overload condition has cleared
Status: current Access: read-only
NOTIFICATION-TYPE    

starOverloadService 1.1.8164.2.169
A 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starOverloadServiceClear 1.1.8164.2.170
A service-specific congestion overload condition has cleared
Status: current Access: read-only
NOTIFICATION-TYPE    

starStorageServerClusterStateChange 1.1.8164.2.171
GTPP 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starStorageServerClusSwitchOver 1.1.8164.2.172
GTPP 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starStorageServerClusPathFail 1.1.8164.2.173
GTPP 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starStorageServerClusPathOK 1.1.8164.2.174
GTPP Storage Server cluster disk path failure has been restored to ok state. Note that this is an external server, not part of the ST16
Status: current Access: read-only
NOTIFICATION-TYPE    

starStorageServerClusInterCFail 1.1.8164.2.175
GTPP 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starStorageServerClusInterCOK 1.1.8164.2.176
GTPP 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starStorageServerClusIntfFail 1.1.8164.2.177
GTPP 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starStorageServerClusIntfOK 1.1.8164.2.178
GTPP 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starStorageServerMemLow 1.1.8164.2.179
GTPP 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starStorageServerMemNormal 1.1.8164.2.180
GTPP Storage Server Memory usage has returned to a normal range. Note that this is an external server, not part of the ST16.
Status: current Access: read-only
NOTIFICATION-TYPE    

starPDIFServiceStart 1.1.8164.2.181
A PDIF Service has started Action to be Taken: No action required
Status: current Access: read-only
NOTIFICATION-TYPE    

starPDIFServiceStop 1.1.8164.2.182
A 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starSessMgrRecoveryComplete 1.1.8164.2.183
A Sess Mgr Recovery Complete Probable Cause: This is typically caused by session manager task fails and successfully completed recovery. Action to be Taken: None
Status: current Access: read-only
NOTIFICATION-TYPE    

starDiameterPeerDown 1.1.8164.2.184
A 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starDiameterPeerUp 1.1.8164.2.185
A diameter peer is up. This notification is only generated for peers which have previously been declared down.
Status: current Access: read-only
NOTIFICATION-TYPE    

starDiameterServerUnreachable 1.1.8164.2.186
A 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starDiameterServerReachable 1.1.8164.2.187
A diameter server is up. This notification is only generated for servers which have previously been declared unreachable.
Status: current Access: read-only
NOTIFICATION-TYPE    

starCDRFileRemoved 1.1.8164.2.188
A 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starCSCFPeerServerReachable 1.1.8164.2.189
A peer server is reachable
Status: current Access: read-only
NOTIFICATION-TYPE    

starCSCFPeerServerUnreachable 1.1.8164.2.190
A peer server is unreachable
Status: current Access: read-only
NOTIFICATION-TYPE    

starCLIConfigMode 1.1.8164.2.192
An 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starSGSNServiceStart 1.1.8164.2.194
A SGSN Service has started Action to be Taken: No action required
Status: current Access: read-only
NOTIFICATION-TYPE    

starSGSNServiceStop 1.1.8164.2.195
A 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starM3UAPCUnavailable 1.1.8164.2.196
M3UA 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starM3UAPCAvailable 1.1.8164.2.197
M3UA 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshCPUUtilization 1.1.8164.2.200
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearCPUUtilization 1.1.8164.2.201
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshCPUMemory 1.1.8164.2.202
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearCPUMemory 1.1.8164.2.203
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshLicense 1.1.8164.2.204
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearLicense 1.1.8164.2.205
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshSubscriberTotal 1.1.8164.2.206
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearSubscriberTotal 1.1.8164.2.207
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshSubscriberActive 1.1.8164.2.208
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearSubscriberActive 1.1.8164.2.209
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshPortRxUtil 1.1.8164.2.210
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearPortRxUtil 1.1.8164.2.211
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshPortTxUtil 1.1.8164.2.212
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearPortTxUtil 1.1.8164.2.213
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshPortHighActivity 1.1.8164.2.214
High 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearPortHighActivity 1.1.8164.2.215
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshAAAAuthFail 1.1.8164.2.216
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearAAAAuthFail 1.1.8164.2.217
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshAAAAuthFailRate 1.1.8164.2.218
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearAAAAuthFailRate 1.1.8164.2.219
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshAAAAcctFail 1.1.8164.2.220
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearAAAAcctFail 1.1.8164.2.221
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshAAAAcctFailRate 1.1.8164.2.222
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearAAAAcctFailRate 1.1.8164.2.223
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshAAARetryRate 1.1.8164.2.224
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearAAARetryRate 1.1.8164.2.225
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshCallSetup 1.1.8164.2.226
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearCallSetup 1.1.8164.2.227
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshCallSetupFailure 1.1.8164.2.228
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearCallSetupFailure 1.1.8164.2.229
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshCallRejectNoResource 1.1.8164.2.230
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearCallRejectNoResource 1.1.8164.2.231
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshPacketsFilteredDropped 1.1.8164.2.232
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearPacketsFilteredDropped 1.1.8164.2.233
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshPacketsForwarded 1.1.8164.2.234
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearPacketsForwarded 1.1.8164.2.235
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshSessCPUThroughput 1.1.8164.2.236
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearSessCPUThroughput 1.1.8164.2.237
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshIPPoolAvail 1.1.8164.2.238
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearIPPoolAvail 1.1.8164.2.239
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshCPUUtilization10Sec 1.1.8164.2.240
The CPU utilization of 10 second measurement for the identified processor has exceeded for configured threshold value for the current monitoring period.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearCPUUtilization10Sec 1.1.8164.2.241
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshCPULoad 1.1.8164.2.242
The CPU load for the identified processor has exceeded for configured threshold value for the current monitoring period.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearCPULoad 1.1.8164.2.243
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshCPUMemUsage 1.1.8164.2.244
The CPU mem usage for the identified processor has exceeded for configured threshold value for the current monitoring period.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearCPUMemUsage 1.1.8164.2.245
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshPDSNSessions 1.1.8164.2.246
The total number of PDSN sessions is above the configured threshold value.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearPDSNSessions 1.1.8164.2.247
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshGGSNSessions 1.1.8164.2.248
The total number of GGSN sessions is above the configured threshold value.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearGGSNSessions 1.1.8164.2.249
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshHASessions 1.1.8164.2.250
The total number of HA sessions is above the configured threshold value.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearHASessions 1.1.8164.2.251
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshLNSSessions 1.1.8164.2.252
The total number of L2TP LNS sessions is above the configured threshold value.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearLNSSessions 1.1.8164.2.253
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshPerServicePDSNSessions 1.1.8164.2.254
The total number of PDSN sessions in a service is above the configured threshold value.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearPerServicePDSNSessions 1.1.8164.2.255
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshPerServiceGGSNSessions 1.1.8164.2.256
The total number of GGSN sessions in a service is above the configured threshold value.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearPerServiceGGSNSessions 1.1.8164.2.257
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshPerServiceHASessions 1.1.8164.2.258
The total number of HA sessions in a service is above the configured threshold value.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearPerServiceHASessions 1.1.8164.2.259
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshPerServiceLNSSessions 1.1.8164.2.260
The total number of L2TP LNS sessions in a service is above the configured threshold value.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearPerServiceLNSSessions 1.1.8164.2.261
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshIPPoolHold 1.1.8164.2.262
The percentage IP pool addresses in HOLD state in a context has gone above the configured threshold
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearIPPoolHold 1.1.8164.2.263
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshIPPoolUsed 1.1.8164.2.264
The percentage IP pool addresses in USED state in a context has gone above the configured threshold
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearIPPoolUsed 1.1.8164.2.265
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshIPPoolRelease 1.1.8164.2.266
The percentage IP pool addresses in RELEASE state in a context has gone above the configured threshold
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearIPPoolRelease 1.1.8164.2.267
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshIPPoolFree 1.1.8164.2.268
The percentage IP pool addresses in HOLD state in a context has gone below the configured threshold
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearIPPoolFree 1.1.8164.2.269
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshAAAAcctArchive 1.1.8164.2.270
The AAA accounting archive size has gone above the configured threshold
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearAAAAcctArchive 1.1.8164.2.271
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshPortSpecRxUtil 1.1.8164.2.272
The 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.
Status: deprecated Access: read-only
NOTIFICATION-TYPE    

starThreshClearPortSpecRxUtil 1.1.8164.2.273
The threshold condition is now clear.
Status: deprecated Access: read-only
NOTIFICATION-TYPE    

starThreshPortSpecTxUtil 1.1.8164.2.274
The 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.
Status: deprecated Access: read-only
NOTIFICATION-TYPE    

starThreshClearPortSpecTxUtil 1.1.8164.2.275
The threshold condition is now clear.
Status: deprecated Access: read-only
NOTIFICATION-TYPE    

starThreshHACallSetupRate 1.1.8164.2.276
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearHACallSetupRate 1.1.8164.2.277
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshHASvcCallSetupRate 1.1.8164.2.278
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearHASvcCallSetupRate 1.1.8164.2.279
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshHASvcRegReplyError 1.1.8164.2.280
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearHASvcRegReplyError 1.1.8164.2.281
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshHASvcReregReplyError 1.1.8164.2.282
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearHASvcReregReplyError 1.1.8164.2.283
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshHASvcDeregReplyError 1.1.8164.2.284
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearHASvcDeregReplyError 1.1.8164.2.285
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshFASvcRegReplyError 1.1.8164.2.286
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearFASvcRegReplyError 1.1.8164.2.287
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshPDSNCallSetupRate 1.1.8164.2.288
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearPDSNCallSetupRate 1.1.8164.2.289
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshPDSNSvcCallSetupRate 1.1.8164.2.290
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearPDSNSvcCallSetupRate 1.1.8164.2.291
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshPDSNSvcA11RRPFailure 1.1.8164.2.292
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearPDSNSvcA11RRPFailure 1.1.8164.2.293
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshPDSNSvcA11RRQMsgDiscard 1.1.8164.2.294
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearPDSNSvcA11RRQMsgDiscard 1.1.8164.2.295
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshPDSNSvcA11RACMsgDiscard 1.1.8164.2.296
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearPDSNSvcA11RACMsgDiscard 1.1.8164.2.297
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshPDSNSvcA11PPPSendDiscard 1.1.8164.2.298
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearPDSNSvcA11PPPSendDiscard 1.1.8164.2.299
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshAAAMgrQueue 1.1.8164.2.300
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearAAAMgrQueue 1.1.8164.2.301
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshAAAAcctArchiveQueue1 1.1.8164.2.505
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearAAAAcctArchiveQueue1 1.1.8164.2.506
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshAAAAcctArchiveQueue2 1.1.8164.2.507
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearAAAAcctArchiveQueue2 1.1.8164.2.508
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshAAAAcctArchiveQueue3 1.1.8164.2.509
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearAAAAcctArchiveQueue3 1.1.8164.2.510
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshDnsLookupSrvFailure 1.1.8164.2.511
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearDnsLookupSrvFailure 1.1.8164.2.512
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshCPUOrbsWarn 1.1.8164.2.302
The ORBs task has exceeding the CPU usage configured as a warning
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearCPUOrbsWarn 1.1.8164.2.303
The threshold condition is now clear
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshCPUOrbsCritical 1.1.8164.2.304
The ORBs task has exceeded the CPU usage configured as a critical error
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearCPUOrbsCritical 1.1.8164.2.305
The threshold condition is now clear
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshRPSetupFailRate 1.1.8164.2.306
The RP call setup failure rate has exceeded the configured threshold
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearRPSetupFailRate 1.1.8164.2.307
The threshold condition is now clear
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshPPPSetupFailRate 1.1.8164.2.308
The PPP call setup failure rate has exceeded the configured threshold
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearPPPSetupFailRate 1.1.8164.2.309
The threshold condition is now clear
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshStorageUtilization 1.1.8164.2.310
The utilization of a mass storage device has exeeded the configured threshold
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearStorageUtilization 1.1.8164.2.311
The threshold condition is now clear
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshDCCAProtocolErrors 1.1.8164.2.312
The number of DCCA Protocol Errors has exceeded the configured threshold
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearDCCAProtocolErrors 1.1.8164.2.313
The threshold condition is now clear
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshDCCABadAnswers 1.1.8164.2.314
The number of DCCA BadAnswers has exceeded the configured threshold
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearDCCABadAnswers 1.1.8164.2.315
The threshold condition is now clear
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshDCCAUnknownRatingGroup 1.1.8164.2.316
The number of DCCA UnknownRatingGroup has exceeded the configured threshold
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearDCCAUnknownRatingGroup 1.1.8164.2.317
The threshold condition is now clear
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshDCCARatingFailed 1.1.8164.2.318
The number of DCCA RatingFailed has exceeded the configured threshold
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearDCCARatingFailed 1.1.8164.2.319
The threshold condition is now clear
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshIPSECIKERequests 1.1.8164.2.320
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearIPSECIKERequests 1.1.8164.2.321
The threshold condition is now clear
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshIPSECIKEFailures 1.1.8164.2.322
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearIPSECIKEFailures 1.1.8164.2.323
The threshold condition is now clear
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshIPSECIKEFailRate 1.1.8164.2.324
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearIPSECIKEFailRate 1.1.8164.2.325
The threshold condition is now clear
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshIPSECTunSetup 1.1.8164.2.326
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearIPSECTunSetup 1.1.8164.2.327
The threshold condition is now clear
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshIPSECTunEstabl 1.1.8164.2.328
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearIPSECTunEstabl 1.1.8164.2.329
The threshold condition is now clear
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshIPSECCallReqRej 1.1.8164.2.330
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearIPSECCallReqRej 1.1.8164.2.331
The threshold condition is now clear
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshCSCFSvcRouteFailure 1.1.8164.2.332
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearCSCFSvcRouteFailure 1.1.8164.2.333
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshContFiltRating 1.1.8164.2.334
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearContFiltRating 1.1.8164.2.335
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshContFiltBlock 1.1.8164.2.336
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearContFiltBlock 1.1.8164.2.337
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshCDRFileSpace 1.1.8164.2.338
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearCDRFileSpace 1.1.8164.2.339
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshEDRFileSpace 1.1.8164.2.340
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearEDRFileSpace 1.1.8164.2.341
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshPDIFCurrSess 1.1.8164.2.342
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearPDIFCurrSess 1.1.8164.2.343
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshPDIFCurrActSess 1.1.8164.2.344
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearPDIFCurrActSess 1.1.8164.2.345
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshCDRFlowControl 1.1.8164.2.346
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearCDRFlowControl 1.1.8164.2.347
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshASNGWSessTimeout 1.1.8164.2.348
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearASNGWSessTimeout 1.1.8164.2.349
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshASNGWSessSetupTimeout 1.1.8164.2.350
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearASNGWSessSetupTimeout 1.1.8164.2.351
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshASNGWAuthFail 1.1.8164.2.352
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearASNGWAuthFail 1.1.8164.2.353
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshASNGWR6InvNai 1.1.8164.2.354
The 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.
Status: obsolete Access: read-only
NOTIFICATION-TYPE    

starThreshClearASNGWR6InvNai 1.1.8164.2.355
The threshold condition is now clear. This trap is obsolete.
Status: obsolete Access: read-only
NOTIFICATION-TYPE    

starThreshASNGWMaxEAPRetry 1.1.8164.2.356
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearASNGWMaxEAPRetry 1.1.8164.2.357
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshASNGWNWEntryDenial 1.1.8164.2.358
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearASNGWNWEntryDenial 1.1.8164.2.359
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshASNGWHandoffDenial 1.1.8164.2.360
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearASNGWHandoffDenial 1.1.8164.2.361
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshSGSNSessions 1.1.8164.2.362
The total number of SGSN sessions is above the configured threshold value.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearSGSNSessions 1.1.8164.2.363
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshPerServiceSGSNSessions 1.1.8164.2.364
The total number of SGSN sessions in a service is above the configured threshold value.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearPerServiceSGSNSessions 1.1.8164.2.365
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshSGSNPdpSessions 1.1.8164.2.366
The total number of SGSN PDP sessions is above the configured threshold value.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearSGSNPdpSessions 1.1.8164.2.367
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshPerServiceSGSNPdpSessions 1.1.8164.2.368
The total number of SGSN PDP sessions in a service is above the configured threshold value.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearPerServiceSGSNPdpSessions 1.1.8164.2.369
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshFWDosAttack 1.1.8164.2.370
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearFWDosAttack 1.1.8164.2.371
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshFWDropPacket 1.1.8164.2.372
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearFWDropPacket 1.1.8164.2.373
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshFWDenyRule 1.1.8164.2.374
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearFWDenyRule 1.1.8164.2.375
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshFWNoRule 1.1.8164.2.376
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearFWNoRule 1.1.8164.2.377
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshPHSGWSessTimeout 1.1.8164.2.378
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearPHSGWSessTimeout 1.1.8164.2.379
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshPHSGWSessSetupTimeout 1.1.8164.2.380
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearPHSGWSessSetupTimeout 1.1.8164.2.381
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshPHSGWAuthFail 1.1.8164.2.382
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearPHSGWAuthFail 1.1.8164.2.383
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshPHSGWMaxEAPRetry 1.1.8164.2.384
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearPHSGWMaxEAPRetry 1.1.8164.2.385
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshPHSGWNWEntryDenial 1.1.8164.2.386
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearPHSGWNWEntryDenial 1.1.8164.2.387
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshPHSGWHandoffDenial 1.1.8164.2.388
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearPHSGWHandoffDenial 1.1.8164.2.389
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshASNGWSessions 1.1.8164.2.390
The total number of ASNGW sessions is above the configured threshold value.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearASNGWSessions 1.1.8164.2.391
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshPerServiceASNGWSessions 1.1.8164.2.392
The total number of ASNGW sessions in a service is above the configured threshold value.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearPerServiceASNGWSessions 1.1.8164.2.393
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshPHSPCSessSetupTimeout 1.1.8164.2.394
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearPHSPCSessSetupTimeout 1.1.8164.2.395
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshPHSPCSleepModeTimeout 1.1.8164.2.396
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearPHSPCSleepModeTimeout 1.1.8164.2.397
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshPHSPCSmEntryDenial 1.1.8164.2.398
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearPHSPCSmEntryDenial 1.1.8164.2.399
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshSGWSessions 1.1.8164.2.408
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearSGWSessions 1.1.8164.2.409
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshPGWSessions 1.1.8164.2.410
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearPGWSessions 1.1.8164.2.411
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshLMASessions 1.1.8164.2.412
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearLMASessions 1.1.8164.2.413
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshMAGSessions 1.1.8164.2.414
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearMAGSessions 1.1.8164.2.415
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshFNGCurrSess 1.1.8164.2.416
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearFNGCurrSess 1.1.8164.2.417
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshFNGCurrActSess 1.1.8164.2.418
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearFNGCurrActSess 1.1.8164.2.419
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshPHSGWEAPOLAuthFailure 1.1.8164.2.420
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearPHSGWEAPOLAuthFailure 1.1.8164.2.421
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshPHSGWMaxEAPOLRetry 1.1.8164.2.422
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearPHSGWMaxEAPOLRetry 1.1.8164.2.423
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshHSGWSessions 1.1.8164.2.424
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearHSGWSessions 1.1.8164.2.425
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshPDGCurrSess 1.1.8164.2.426
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearPDGCurrSess 1.1.8164.2.427
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshPDGCurrActSess 1.1.8164.2.428
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearPDGCurrActSess 1.1.8164.2.429
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshNATPortChunks 1.1.8164.2.430
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearNATPortChunks 1.1.8164.2.431
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshGPRSSessions 1.1.8164.2.432
The total number of GPRS sessions is above the configured threshold value.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearGPRSSessions 1.1.8164.2.433
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshPerServiceGPRSSessions 1.1.8164.2.434
The total number of GPRS sessions in a service is above the configured threshold value.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearPerServiceGPRSSessions 1.1.8164.2.435
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshGPRSPdpSessions 1.1.8164.2.436
The total number of GPRS PDP sessions is above the configured threshold value.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearGPRSPdpSessions 1.1.8164.2.437
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshPerServiceGPRSPdpSessions 1.1.8164.2.438
The total number of GPRS PDP sessions in a service is above the configured threshold value.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearPerServiceGPRSPdpSessions 1.1.8164.2.439
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshMMESessions 1.1.8164.2.440
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearMMESessions 1.1.8164.2.441
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshMMEAuthFail 1.1.8164.2.442
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearMMEAuthFail 1.1.8164.2.443
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshMMEAttachFail 1.1.8164.2.444
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearMMEAttachFail 1.1.8164.2.445
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshCSCFSvcRegRcvdRate 1.1.8164.2.446
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearCSCFSvcRegRcvdRate 1.1.8164.2.447
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshCSCFSvcTotalActiveReg 1.1.8164.2.448
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearCSCFSvcTotalActiveReg 1.1.8164.2.449
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshCSCFSvcInviteRcvdRate 1.1.8164.2.450
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearCSCFSvcInviteRcvdRate 1.1.8164.2.451
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshCSCFSvcTotalActiveCalls 1.1.8164.2.452
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearCSCFSvcTotalActiveCalls 1.1.8164.2.453
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshCSCFSvcTotalCallFailure 1.1.8164.2.454
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearCSCFSvcTotalCallFailure 1.1.8164.2.455
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshCSCFSvcErrorNoResource 1.1.8164.2.456
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearCSCFSvcErrorNoResource 1.1.8164.2.457
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshCSCFSvcErrorTcp 1.1.8164.2.458
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearCSCFSvcErrorTcp 1.1.8164.2.459
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshCSCFSvcErrorPresence 1.1.8164.2.460
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearCSCFSvcErrorPresence 1.1.8164.2.461
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshCSCFSvcErrorRegAuth 1.1.8164.2.462
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearCSCFSvcErrorRegAuth 1.1.8164.2.463
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshBGPRoutes 1.1.8164.2.464
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearBGPRoutes 1.1.8164.2.465
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshPCCPolicySessions 1.1.8164.2.466
The total number of PCC-Policy sessions is above the configured threshold value.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearPCCPolicySessions 1.1.8164.2.467
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshPerServicePCCPolicySessions 1.1.8164.2.468
The total number of PCC-Policy sessions in a service is above the configured threshold value.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearPerServicePCCPolicySessions 1.1.8164.2.469
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshPCCQuotaSessions 1.1.8164.2.470
The total number of PCC-Quota sessions is above the configured threshold value.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearPCCQuotaSessions 1.1.8164.2.471
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshPerServicePCCQuotaSessions 1.1.8164.2.472
The total number of PCC-Quota sessions in a service is above the configured threshold value.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearPerServicePCCQuotaSessions 1.1.8164.2.473
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshPCCAFSessions 1.1.8164.2.474
The total number of PCC-AF sessions is above the configured threshold value.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearPCCAFSessions 1.1.8164.2.475
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshPerServicePCCAFSessions 1.1.8164.2.476
The total number of PCC-AF sessions in a service is above the configured threshold value.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearPerServicePCCAFSessions 1.1.8164.2.477
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshNPUUtilization 1.1.8164.2.478
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearNPUUtilization 1.1.8164.2.479
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshDnsLookupFailure 1.1.8164.2.480
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearDnsLookupFailure 1.1.8164.2.481
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshDiameterRetryRate 1.1.8164.2.482
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearDiameterRetryRate 1.1.8164.2.483
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshHNBGWHnbSess 1.1.8164.2.484
The chassis-wide count of current HNBGW HNB sessions has gone above the configured threshold
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearHNBGWHnbSess 1.1.8164.2.485
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshHNBGWUeSess 1.1.8164.2.486
The chassis-wide count of current HNBGW UE sessions has gone above the configured threshold
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearHNBGWUeSess 1.1.8164.2.487
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshHNBGWIuSess 1.1.8164.2.488
The chassis-wide count of current HNBGW IU sessions has gone above the configured threshold
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearHNBGWIuSess 1.1.8164.2.489
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshPerServicePDGSessions 1.1.8164.2.491
The total number of PDG sessions in a service is above the configured threshold value.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearPerServicePDGSessions 1.1.8164.2.492
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshSystemCapacity 1.1.8164.2.493
The System resource capacity has exceeded the configured threshold
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearSystemCapacity 1.1.8164.2.494
The threshold condition is now clear for system capacity.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshTpoRtoTimeout 1.1.8164.2.495
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearTpoRtoTimeout 1.1.8164.2.496
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshTpoDnsFailure 1.1.8164.2.497
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearTpoDnsFailure 1.1.8164.2.498
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshTpoLowCompressionGain 1.1.8164.2.499
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearTpoLowCompressionGain 1.1.8164.2.500
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshEPDGCurrSess 1.1.8164.2.501
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearEPDGCurrSess 1.1.8164.2.502
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshCardTemperatureNearPowerOffLimit 1.1.8164.2.503
On 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearCardTemperaturePowerOffLimit 1.1.8164.2.504
On the certain card, the distance between the poweroff/reset point and current temperature on card is larger than the setted clear point.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshHENBGWHenbSessions 1.1.8164.2.513
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearHENBGWHenbSessions 1.1.8164.2.514
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshHENBGWUeSessions 1.1.8164.2.515
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearHENBGWUeSessions 1.1.8164.2.516
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshHENBGWPagingMessages 1.1.8164.2.517
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearHENBGWPagingMessages 1.1.8164.2.518
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshPerServiceSAMOGSessions 1.1.8164.2.519
The total number of SAMOG sessions in a service is above the configured threshold value.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearPerServiceSAMOGSessions 1.1.8164.2.520
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshNATPktDrop 1.1.8164.2.521
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearNATPktDrop 1.1.8164.2.522
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshFabricEGQDiscards 1.1.8164.2.523
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearFabricEGQDiscards 1.1.8164.2.524
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starGILANServiceStart 1.1.8164.2.525
A GILAN Service has started Action to be Taken: No action required
Status: current Access: read-only
NOTIFICATION-TYPE    

starGILANServiceStop 1.1.8164.2.526
A 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshEPDGIKEV2SetupAttempts 1.1.8164.2.527
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearEPDGIKEV2SetupAttempts 1.1.8164.2.528
The threshold condition is now clear
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshEPDGIKEV2AuthFailures 1.1.8164.2.529
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearEPDGIKEV2AuthFailures 1.1.8164.2.530
The threshold condition is now clear
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshEPDGIKEV2SetupSuccess 1.1.8164.2.531
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearEPDGIKEV2SetupSuccess 1.1.8164.2.532
The threshold condition is now clear
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshEPDGIKEV2SetupFailure 1.1.8164.2.533
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearEPDGIKEV2SetupFailure 1.1.8164.2.534
The threshold condition is now clear
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshEPDGIKEV2SetupFailureRate 1.1.8164.2.535
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearEPDGIKEV2SetupFailureRate 1.1.8164.2.536
The threshold condition is now clear
Status: current Access: read-only
NOTIFICATION-TYPE    

starOSPFNeighborDown 1.1.8164.2.1001
An OSPF neighbor is down. Condition Clear Alarm: A starOSPFNeighborFull notification will be generated when the neighbor is restored.
Status: current Access: read-only
NOTIFICATION-TYPE    

starOSPFNeighborFull 1.1.8164.2.1002
An OSPF neighbor is full. A starOSPFNeighborFull notification is only sent for neighbors which had previous been declared down via a starOSPFNeighborDown notification.
Status: current Access: read-only
NOTIFICATION-TYPE    

starM3UAPSDown 1.1.8164.2.1004
The 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starM3UAPSActive 1.1.8164.2.1005
Peer 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starM3UAPSPDown 1.1.8164.2.1006
An 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starM3UAPSPUp 1.1.8164.2.1007
An 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starSCCPSspRcvd 1.1.8164.2.1008
Subsystem 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starSCCPSspClear 1.1.8164.2.1009
Susbsystem 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starSGSNRNCReset 1.1.8164.2.1010
SGSN 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starSGSNHLRReset 1.1.8164.2.1011
Home 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starSGSNGtpcPathFailure 1.1.8164.2.1012
No 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starSGSNGtpcPathFailureClear 1.1.8164.2.1013
The 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starSGSNGtpuPathFailure 1.1.8164.2.1014
No 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starSGSNGtpuPathFailureClear 1.1.8164.2.1015
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starMTP3LinkOutOfService 1.1.8164.2.1016
Message 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starMTP3LinkInService 1.1.8164.2.1017
Message Transfer Part(MTP3) link is in service.
Status: current Access: read-only
NOTIFICATION-TYPE    

starMTP3LinkSetUnAvailable 1.1.8164.2.1018
Message 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starMTP3LinkSetAvailable 1.1.8164.2.1019
Message Transfer Part(MTP3) linkset Available. A starMTP3LinkSetAvailable notification is only generated for linksets which previously generated a starMTP3LinkSetUnavailable notification
Status: current Access: read-only
NOTIFICATION-TYPE    

starSCTPAssociationFail 1.1.8164.2.1020
M3UA 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starSCTPAssociationEstablished 1.1.8164.2.1021
M3UA 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starSCTPPathDown 1.1.8164.2.1022
Stream 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starSCTPPathUp 1.1.8164.2.1023
Stream Control Transmission Protocol(SCTP) path up. A starSCTPPathUp notification is only generated for peers which had previously generated a starSCTPPathDown notification
Status: current Access: read-only
NOTIFICATION-TYPE    

starPortDown 1.1.8164.2.1024
Port 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starPortUp 1.1.8164.2.1025
Port 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starBSReachable 1.1.8164.2.1026
The Base Station is reachable now. This can be result of Base Station Startup, etc. Action to be Taken: No Action Required
Status: current Access: read-only
NOTIFICATION-TYPE    

starBSUnreachable 1.1.8164.2.1027
A 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starSystemStartup 1.1.8164.2.1028
The system has completed a reboot/startup
Status: current Access: read-only
NOTIFICATION-TYPE    

starMTP3PCUnavailable 1.1.8164.2.1029
Message 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starMTP3PCAvailable 1.1.8164.2.1030
Message 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starSS7PCUnavailable 1.1.8164.2.1031
SS7 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starSS7PCAvailable 1.1.8164.2.1032
SS7 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starASNPCServiceStart 1.1.8164.2.1033
A WiMAX ASN Paging Controller (ASNPC) Service has started Action to be Taken: No action required
Status: current Access: read-only
NOTIFICATION-TYPE    

starASNPCServiceStop 1.1.8164.2.1034
A 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starDiameterCapabilitiesExchangeFailure 1.1.8164.2.1035
Capability 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starDiameterCapabilitiesExchangeSuccess 1.1.8164.2.1036
A diameter server is up. This notification is only generated for servers which have previously been declared unreachable.
Status: current Access: read-only
NOTIFICATION-TYPE    

starSRPConnDown 1.1.8164.2.1037
The 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starSRPConnUp 1.1.8164.2.1038
The connection to the standby SRP system is now up. This notification is only generated if a starSRPConnDown had previously been generated.
Status: current Access: read-only
NOTIFICATION-TYPE    

starDiameterIpv6PeerDown 1.1.8164.2.1039
A 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starDiameterIpv6PeerUp 1.1.8164.2.1040
A 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starIPMSServerUnreachable 1.1.8164.2.1041
An 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starIPMSServerReachable 1.1.8164.2.1042
An IPMS server is reachable. A starIPMSServerReachable notification is only generated for servers which had previously been declared unreachable.
Status: current Access: read-only
NOTIFICATION-TYPE    

starCertShortLifetime 1.1.8164.2.1043
A 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starCertExpired 1.1.8164.2.1044
A 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starCertValid 1.1.8164.2.1045
A valid certificate has been configured. This notification is only generated if a starCertExpired had been previously generated.
Status: current Access: read-only
NOTIFICATION-TYPE    

starFTPPushFail 1.1.8164.2.1046
An FTP push operation has failed for the specified file to the specified server.
Status: current Access: read-only
NOTIFICATION-TYPE    

starFTPServSwitch 1.1.8164.2.1047
An 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starSDHSectionDown 1.1.8164.2.1048
The 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,
Status: current Access: read-only
NOTIFICATION-TYPE    

starSDHSectionUp 1.1.8164.2.1049
The SDH interface on this port is now up. A starSDHSectionUp notification is only generated if a starSDHSectionDown was previously generated for this port.
Status: current Access: read-only
NOTIFICATION-TYPE    

starSDHPathHopDown 1.1.8164.2.1050
The identified SDH Path is down. The value of starSDHPathOperState identifies the specific failure bits.
Status: current Access: read-only
NOTIFICATION-TYPE    

starSDHPathHopUp 1.1.8164.2.1051
The identified SDH Path is up.
Status: current Access: read-only
NOTIFICATION-TYPE    

starSDHLopDown 1.1.8164.2.1052
The 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,
Status: current Access: read-only
NOTIFICATION-TYPE    

starSDHLopUp 1.1.8164.2.1053
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starSS7PCCongested 1.1.8164.2.1056
SS7 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starSS7PCCongestionCleared 1.1.8164.2.1057
SS7 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starPHSGWServiceStart 1.1.8164.2.1058
A PHS-GW Service has started Action to be Taken: No action required
Status: current Access: read-only
NOTIFICATION-TYPE    

starPHSGWServiceStop 1.1.8164.2.1059
A 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starGPRSServiceStart 1.1.8164.2.1060
A GPRS Service has started Action to be Taken: No action required
Status: current Access: read-only
NOTIFICATION-TYPE    

starGPRSServiceStop 1.1.8164.2.1061
A 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starGPRSNseDown 1.1.8164.2.1062
Network 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starGPRSNseUp 1.1.8164.2.1063
Network 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starGPRSNsvcDown 1.1.8164.2.1064
Network 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starGPRSNsvcUp 1.1.8164.2.1065
An Network Service Entity Virtual Circuit (NSVC) comes up An starGPRSNsvcUp trap is generated only when a previous starGPRSNsvcDown was generated
Status: current Access: read-only
NOTIFICATION-TYPE    

starGPRSBvcDown 1.1.8164.2.1066
Base 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starGPRSBvcUp 1.1.8164.2.1067
Base 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starSDHE1TribDown 1.1.8164.2.1068
The 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,
Status: current Access: read-only
NOTIFICATION-TYPE    

starSDHE1TribUp 1.1.8164.2.1069
The identified E1 Tributary on this port is up.
Status: current Access: read-only
NOTIFICATION-TYPE    

starSDHFractE1LMIDown 1.1.8164.2.1070
The identified fractional E1 Tributary on this port is down.
Status: current Access: read-only
NOTIFICATION-TYPE    

starSDHFractE1LMIUp 1.1.8164.2.1071
The identified fractional E1 Tributary on this port is up.
Status: current Access: read-only
NOTIFICATION-TYPE    

starPHSPCServiceStart 1.1.8164.2.1072
A PHS-PC Service has started Action to be Taken: No action required
Status: current Access: read-only
NOTIFICATION-TYPE    

starPHSPCServiceStop 1.1.8164.2.1073
A 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starM3UAPSPCongested 1.1.8164.2.1074
Peer 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starM3UAPSPCongestionCleared 1.1.8164.2.1075
Peer 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starStorageFailed 1.1.8164.2.1076
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starRaidFailed 1.1.8164.2.1077
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starRaidStarted 1.1.8164.2.1078
The specific raid array has resumed operation. This notification is only generated if a starRaidFailed notification was previously generated for this array.
Status: current Access: read-only
NOTIFICATION-TYPE    

starRaidDegraded 1.1.8164.2.1079
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starRaidRecovered 1.1.8164.2.1080
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starPGWServiceStart 1.1.8164.2.1081
A Packet Data Network Gateway (PGW) Service has started. Action to be Taken: No action required
Status: current Access: read-only
NOTIFICATION-TYPE    

starPGWServiceStop 1.1.8164.2.1082
A 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starSGWServiceStart 1.1.8164.2.1083
A Serving Gateway (SGW) Service has started. Action to be Taken: No action required
Status: current Access: read-only
NOTIFICATION-TYPE    

starSGWServiceStop 1.1.8164.2.1084
A 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starEGTPServiceStart 1.1.8164.2.1085
An Evolved GPRS Tunneling Protocol (EGTP) Service has started. Action to be Taken: No action required
Status: current Access: read-only
NOTIFICATION-TYPE    

starEGTPServiceStop 1.1.8164.2.1086
An 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starLMAServiceStart 1.1.8164.2.1087
A Local Mobility Anchor (LMA) Service has started. Action to be Taken: No action required
Status: current Access: read-only
NOTIFICATION-TYPE    

starLMAServiceStop 1.1.8164.2.1088
A 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starMAGServiceStart 1.1.8164.2.1089
A Mobile Access Gateway (MAG) Service has started. Action to be Taken: No action required
Status: current Access: read-only
NOTIFICATION-TYPE    

starMAGServiceStop 1.1.8164.2.1090
A 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starMMEServiceStart 1.1.8164.2.1091
A Mobility Management Entity (MME) Service has started. Action to be Taken: No action required
Status: current Access: read-only
NOTIFICATION-TYPE    

starMMEServiceStop 1.1.8164.2.1092
A 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starHSGWServiceStart 1.1.8164.2.1093
A HRPD Serving Gateway (HSGW) Service has started. Action to be Taken: No action required
Status: current Access: read-only
NOTIFICATION-TYPE    

starHSGWServiceStop 1.1.8164.2.1094
A 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starCPUBusyClear 1.1.8164.2.1095
The CPU is no longer busy.
Status: current Access: read-only
NOTIFICATION-TYPE    

starCPUMemoryLowClear 1.1.8164.2.1096
The CPU is no longer experiencing a low memory condition.
Status: current Access: read-only
NOTIFICATION-TYPE    

starFNGServiceStart 1.1.8164.2.1097
A FNG Service has started Action to be Taken: No action required
Status: current Access: read-only
NOTIFICATION-TYPE    

starFNGServiceStop 1.1.8164.2.1098
A 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starManagerRestart 1.1.8164.2.1099
The identified manager task has been restarted.
Status: current Access: read-only
NOTIFICATION-TYPE    

starConfigurationUpdate 1.1.8164.2.1100
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starPDGServiceStart 1.1.8164.2.1101
A PDG Service has started Action to be Taken: No action required
Status: current Access: read-only
NOTIFICATION-TYPE    

starPDGServiceStop 1.1.8164.2.1102
A 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starDynPkgLoadError 1.1.8164.2.1103
The 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starDynPkgLoadErrorClear 1.1.8164.2.1104
The Dynamic rater package error removed. Action to be Taken: No action required
Status: current Access: read-only
NOTIFICATION-TYPE    

starDynPkgUpgradeError 1.1.8164.2.1105
The 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starDynPkgUpgradeErrorClear 1.1.8164.2.1106
The Dynamic Rater package error removed. Action to be Taken: No action required
Status: current Access: read-only
NOTIFICATION-TYPE    

starCSCFPeerServerUnavailable 1.1.8164.2.1107
Peer server is unavailable
Status: current Access: read-only
NOTIFICATION-TYPE    

starCSCFPeerServerOutofService 1.1.8164.2.1108
Peer server is out-of-service
Status: current Access: read-only
NOTIFICATION-TYPE    

starCSCFPeerServerInService 1.1.8164.2.1109
Peer server unavailable and/or out of service condition cleared
Status: current Access: read-only
NOTIFICATION-TYPE    

starServiceLossPTACsClear 1.1.8164.2.1110
Service Loss condition is no longer valid for PAC/PSC/TACs.
Status: current Access: read-only
NOTIFICATION-TYPE    

starServiceLossLCClear 1.1.8164.2.1111
Service Loss condition is no longer valid for LC.
Status: current Access: read-only
NOTIFICATION-TYPE    

starEgtpcPathFailure 1.1.8164.2.1112
EGTP 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starEgtpcPathFailureClear 1.1.8164.2.1113
EGTP Control Path Failure condition is no longer valid.
Status: current Access: read-only
NOTIFICATION-TYPE    

starCscfSessResourceCongestion 1.1.8164.2.1114
A 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starCscfSessResourceCongestionClear 1.1.8164.2.1115
A congestion condition has cleared at Session Manager for Cscf service
Status: current Access: read-only
NOTIFICATION-TYPE    

starOSPFv3NeighborDown 1.1.8164.2.1116
An OSPFv3 neighbor is down. Condition Clear Alarm: A starOSPFv3NeighborFull notification will be generated when the neighbor is restored.
Status: current Access: read-only
NOTIFICATION-TYPE    

starOSPFv3NeighborFull 1.1.8164.2.1117
An OSPFv3 neighbor is full. A starOSPFv3NeighborFull notification is only sent for neighbors which had previous been declared down via a starOSPFv3NeighborDown notification.
Status: current Access: read-only
NOTIFICATION-TYPE    

starServiceLossSPIOClear 1.1.8164.2.1118
Service Loss condition is no longer valid for SPIO.
Status: current Access: read-only
NOTIFICATION-TYPE    

starEgtpuPathFailure 1.1.8164.2.1119
No 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starEgtpuPathFailureClear 1.1.8164.2.1120
The 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starStorageServerCDRLoss 1.1.8164.2.1121
GTPP 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starHNBGWServiceStart 1.1.8164.2.1122
A Home Node B Gateway (HNB GW) Service has started. Action to be Taken: No action required
Status: current Access: read-only
NOTIFICATION-TYPE    

starHNBGWServiceStop 1.1.8164.2.1123
A 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starSystemReboot 1.1.8164.2.1124
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starLicenseAboutToExpire 1.1.8164.2.1125
A 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starLicenseExpired 1.1.8164.2.1126
A 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starPCCPolicyServiceStart 1.1.8164.2.1127
A PCC-Policy Service has started Action to be Taken: No action required
Status: current Access: read-only
NOTIFICATION-TYPE    

starPCCPolicyServiceStop 1.1.8164.2.1128
A 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starPCCQuotaServiceStart 1.1.8164.2.1129
A PCC-Quota Service has started Action to be Taken: No action required
Status: current Access: read-only
NOTIFICATION-TYPE    

starPCCQuotaServiceStop 1.1.8164.2.1130
A 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starPCCAFServiceStart 1.1.8164.2.1131
A PCC-AF Service has started Action to be Taken: No action required
Status: current Access: read-only
NOTIFICATION-TYPE    

starPCCAFServiceStop 1.1.8164.2.1132
A 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starSPRServerUnreachable 1.1.8164.2.1133
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starSPRServerReachable 1.1.8164.2.1134
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starGSServiceStart 1.1.8164.2.1135
A GS Service has started Action to be Taken: No action required
Status: current Access: read-only
NOTIFICATION-TYPE    

starGSServiceStop 1.1.8164.2.1136
A 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starMAPServiceStart 1.1.8164.2.1137
A MAP Service has started Action to be Taken: No action required
Status: current Access: read-only
NOTIFICATION-TYPE    

starMAPServiceStop 1.1.8164.2.1138
A 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starIUPSServiceStart 1.1.8164.2.1139
An IUPS Service has started Action to be Taken: No action required
Status: current Access: read-only
NOTIFICATION-TYPE    

starIUPSServiceStop 1.1.8164.2.1140
An 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starSGTPServiceStart 1.1.8164.2.1141
A SGTP Service has started Action to be Taken: No action required
Status: current Access: read-only
NOTIFICATION-TYPE    

starSGTPServiceStop 1.1.8164.2.1142
A 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starEPDGServiceStart 1.1.8164.2.1143
A EPDG Service has started Action to be Taken: No action required
Status: current Access: read-only
NOTIFICATION-TYPE    

starEPDGServiceStop 1.1.8164.2.1144
A 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starApsCommandSuccess 1.1.8164.2.1145
APS Command Success Status.
Status: current Access: read-only
NOTIFICATION-TYPE    

starApsCommandFailure 1.1.8164.2.1146
APS Command Failure Status.
Status: current Access: read-only
NOTIFICATION-TYPE    

starApsSwitchSuccess 1.1.8164.2.1147
APS Switch Success Status.
Status: current Access: read-only
NOTIFICATION-TYPE    

starApsSwitchFailure 1.1.8164.2.1148
APS Switch Failure Status.
Status: current Access: read-only
NOTIFICATION-TYPE    

starApsModeMismatch 1.1.8164.2.1149
APS Mode Mismatch Status.
Status: current Access: read-only
NOTIFICATION-TYPE    

starApsChannelMismatch 1.1.8164.2.1150
APS Channel Mismatch Status.
Status: current Access: read-only
NOTIFICATION-TYPE    

starApsByteMismatch 1.1.8164.2.1151
APS Byte Mismatch Status.
Status: current Access: read-only
NOTIFICATION-TYPE    

starApsFeProtLineFailure 1.1.8164.2.1152
APS FE Protocol Line Failure Status.
Status: current Access: read-only
NOTIFICATION-TYPE    

starApsLossOfRedundancy 1.1.8164.2.1153
APS Loss of Redundancy Status.
Status: current Access: read-only
NOTIFICATION-TYPE    

starApsLossOfRedundancyClear 1.1.8164.2.1154
APS Loss of Redundancy Clear Status.
Status: current Access: read-only
NOTIFICATION-TYPE    

starHNBGWSGSNRanapReset 1.1.8164.2.1155
RANAP Reset Received from SGSN
Status: current Access: read-only
NOTIFICATION-TYPE    

starHNBGWMSCRanapReset 1.1.8164.2.1156
RANAP Reset Received from MSC
Status: current Access: read-only
NOTIFICATION-TYPE    

starALCAPNodeReset 1.1.8164.2.1157
ALCAP Node Reset Received from MGW
Status: current Access: read-only
NOTIFICATION-TYPE    

starALCAPPathReset 1.1.8164.2.1158
ALCAP Path Reset Received from MGW
Status: current Access: read-only
NOTIFICATION-TYPE    

starALCAPPathBlock 1.1.8164.2.1159
ALCAP Block Received from MGW
Status: current Access: read-only
NOTIFICATION-TYPE    

starALCAPPathUnBlock 1.1.8164.2.1160
ALCAP Un Block Received from MGW
Status: current Access: read-only
NOTIFICATION-TYPE    

starSGSServiceStart 1.1.8164.2.1161
A SGS Service has started Action to be Taken: No action required
Status: current Access: read-only
NOTIFICATION-TYPE    

starSGSServiceStop 1.1.8164.2.1162
A 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starSgsnGnMsgDelay 1.1.8164.2.1163
Messaging Dealy seen towards GGSN as many messages sent to that GGSN did not receive response within a certain time
Status: current Access: read-only
NOTIFICATION-TYPE    

starSgsnGnMsgDelayClear 1.1.8164.2.1164
The delay seen towards GGSN is no longer seen as message responses are received in time as expected
Status: current Access: read-only
NOTIFICATION-TYPE    

starBNGServiceStart 1.1.8164.2.1165
A BNG Service has started Action to be Taken: No action required
Status: current Access: read-only
NOTIFICATION-TYPE    

starBNGServiceStop 1.1.8164.2.1166
A 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starMMES1AssocFail 1.1.8164.2.1167
An 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starMMES1AssocSetup 1.1.8164.2.1168
An 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starMVGPeerDown 1.1.8164.2.1169
A 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starMVGPeerUp 1.1.8164.2.1170
A MVG peer is up. This notification is only generated for peers which have previously been declared down.
Status: current Access: read-only
NOTIFICATION-TYPE    

starPCCNtfyIntfPeerUnreachable 1.1.8164.2.1173
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starPCCNtfyIntfPeerReachable 1.1.8164.2.1174
The Notification Interface peer can be reached.? Action to be Taken: No Action Required.
Status: current Access: read-only
NOTIFICATION-TYPE    

starIPSecNodePeerDown 1.1.8164.2.1175
A 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starIPSecNodePeerUp 1.1.8164.2.1176
A Node Service peer is back online Action to be Taken: No action required
Status: current Access: read-only
NOTIFICATION-TYPE    

starApsRemoteResponseFail 1.1.8164.2.1177
APS Remote Response Fail.
Status: current Access: read-only
NOTIFICATION-TYPE    

starCdrPurged 1.1.8164.2.1178
CDRs purged
Status: current Access: read-only
NOTIFICATION-TYPE    

starLocalUserAdded 1.1.8164.2.1180
A 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starLocalUserRemoved 1.1.8164.2.1181
A 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starLocalUserPrivilegeChanged 1.1.8164.2.1182
A 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starOsShellAccessed 1.1.8164.2.1183
A 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starTestModeEntered 1.1.8164.2.1184
A 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starLicenseFeaturesModified 1.1.8164.2.1185
A 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starHiddenAccessEnabled 1.1.8164.2.1186
An 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starHiddenAccessDisabled 1.1.8164.2.1187
An 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starLawfulInterceptChanged 1.1.8164.2.1188
Original Lawful Intercept configured by Admin: %s is changed by Admin: %s
Status: current Access: read-only
NOTIFICATION-TYPE    

starMMES1PathFail 1.1.8164.2.1189
An 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starMMES1PathSetup 1.1.8164.2.1190
An 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starSAEGWServiceStart 1.1.8164.2.1191
A SAEGW Service has started Action to be Taken: No action required
Status: current Access: read-only
NOTIFICATION-TYPE    

starSAEGWServiceStop 1.1.8164.2.1192
A 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starHenbgwAccessServiceStart 1.1.8164.2.1193
A HENBGW Access Service has started Action to be Taken: No action required
Status: current Access: read-only
NOTIFICATION-TYPE    

starHenbgwAccessServiceStop 1.1.8164.2.1194
A 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starHenbgwNetworkServiceStart 1.1.8164.2.1195
A HENBGW Network Service has started Action to be Taken: No action required
Status: current Access: read-only
NOTIFICATION-TYPE    

starHenbgwNetworkServiceStop 1.1.8164.2.1196
A 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starAAAArchiveStarted 1.1.8164.2.1197
Archive started
Status: current Access: read-only
NOTIFICATION-TYPE    

starECSTotalDNSLearntIPv4Threshold 1.1.8164.2.1198
DNS 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starECSTotalDNSLearntIPv4ThresholdClear 1.1.8164.2.1199
DNS Learnt IPv4 entries reach below the threshold limit (lower water mark) configured.
Status: current Access: read-only
NOTIFICATION-TYPE    

starECSTotalDNSLearntIPv6Threshold 1.1.8164.2.1200
DNS 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starECSTotalDNSLearntIPv6ThresholdClear 1.1.8164.2.1201
DNS Learnt IPv6 entries reach below the threshold limit (lower water mark) configured.
Status: current Access: read-only
NOTIFICATION-TYPE    

starIPSecNodeIpv6PeerDown 1.1.8164.2.1202
A 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starIPSecNodeIpv6PeerUp 1.1.8164.2.1203
A 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starLAGGroupDown 1.1.8164.2.1204
LAG 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starLAGGroupUp 1.1.8164.2.1205
LAG group status is up. This notification is only generated for master physical port. Action to be Taken: No action required
Status: current Access: read-only
NOTIFICATION-TYPE    

starVLRAssocDown 1.1.8164.2.1206
A 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starVLRAssocUp 1.1.8164.2.1207
A VLR Association is up. This notification is only generated for Association which have previously been declared down.
Status: current Access: read-only
NOTIFICATION-TYPE    

starVLRAllAssocDown 1.1.8164.2.1208
All 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starVLRAllAssocDownClear 1.1.8164.2.1209
VLR at least one association is up. This notification is only generated for all the Association which have previously been declared down.
Status: current Access: read-only
NOTIFICATION-TYPE    

starEnhancedCongestion 1.1.8164.2.1210
A 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starEnhancedCongestionClear 1.1.8164.2.1211
A congestion condition has cleared.
Status: current Access: read-only
NOTIFICATION-TYPE    

starSGSNRNCNoResetAck 1.1.8164.2.1212
SGSN 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshSAEGWSessions 1.1.8164.2.1213
The 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshClearSAEGWSessions 1.1.8164.2.1214
The threshold condition is now clear.
Status: current Access: read-only
NOTIFICATION-TYPE    

starSGSNRMCPUWarn 1.1.8164.2.1215
The 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starSGSNRMCPUWarnClear 1.1.8164.2.1216
The CPU usage is coming back to normal once warned. This event is generated when current CPU usage reaches 50% of allocated limit after warning.
Status: current Access: read-only
NOTIFICATION-TYPE    

starSGSNRMMemWarn 1.1.8164.2.1217
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starSGSNRMMemWarnClear 1.1.8164.2.1218
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starRMCPUOver 1.1.8164.2.1219
The 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starRMCPUOverClear 1.1.8164.2.1220
The CPU usage is going back to normal level. This event is generated when current CPU usage reaches 50% of allocated limit after over.
Status: current Access: read-only
NOTIFICATION-TYPE    

starSGSNRMMemOver 1.1.8164.2.1221
The Memory usage of the task is going in Overload level. This event is generated when current Memory usage reached twice allocated limit.
Status: current Access: read-only
NOTIFICATION-TYPE    

starSGSNRMMemOverClear 1.1.8164.2.1222
The Memory usage for a proclet reached normal after overload. This event is generated when current Memory usage reaches 95% of allocated limit once overloaded.
Status: current Access: read-only
NOTIFICATION-TYPE    

starSessMgrFlowCount 1.1.8164.2.1223
Session 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starSessMgrFlowCountClear 1.1.8164.2.1224
Clear 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starStorageFound 1.1.8164.2.1225
The 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starStorageNotFound 1.1.8164.2.1226
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starHENBGWMMESCTPAssocDown 1.1.8164.2.1227
A 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starHENBGWMMESCTPAssocUp 1.1.8164.2.1228
A 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starHENBGWMMESCTPAllAssocDown 1.1.8164.2.1229
All 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starHENBGWMMESCTPAllAssocDownClear 1.1.8164.2.1230
HENBGW MME SCTP at least one association is up. This notification is only generated for all the Association which have previously been declared down.
Status: current Access: read-only
NOTIFICATION-TYPE    

starNPDBConnectionDown 1.1.8164.2.1231
A 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starNPDBConnectionUp 1.1.8164.2.1232
A NPDB connection is up. Action to be Taken: No action required
Status: current Access: read-only
NOTIFICATION-TYPE    

starNPUMissedARPFrames 1.1.8164.2.1233
This 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starNPUMissedARPFramesClear 1.1.8164.2.1234
This 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starChassisCrashListFull 1.1.8164.2.1235
Chassis 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starSessMgrCSCFServiceRecoveryComplete 1.1.8164.2.1236
Indicates 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starECSreaddressServerDown 1.1.8164.2.1237
Server from readdress server list is detected down This notification is generated when there are consecutive failures for server.
Status: current Access: read-only
NOTIFICATION-TYPE    

starECSreaddressServerUp 1.1.8164.2.1238
Server from readdress server list is detected up This notification is generated when after deadtime server is detected up.
Status: current Access: read-only
NOTIFICATION-TYPE    

starCdrHDDStart 1.1.8164.2.1239
CDRs are being written to the HDD
Status: current Access: read-only
NOTIFICATION-TYPE    

starCdrStreamingStart 1.1.8164.2.1240
CDR streaming is started
Status: current Access: read-only
NOTIFICATION-TYPE    

starCdrStreamingComplete 1.1.8164.2.1241
CDR streaming is Completed
Status: current Access: read-only
NOTIFICATION-TYPE    

starVLRDown 1.1.8164.2.1242
A 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starVLRUp 1.1.8164.2.1243
A VLR is up. This notification is only generated for VLRs which have previously been declared down.
Status: current Access: read-only
NOTIFICATION-TYPE    

starPCFReachable 1.1.8164.2.1244
A PCF that the IMG communication is reachable.
Status: current Access: read-only
NOTIFICATION-TYPE    

starLIRcvryError 1.1.8164.2.1245
This 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starLIRcvryComplete 1.1.8164.2.1246
This trap will be raised when Lawful Intercepts are successfully recovered
Status: current Access: read-only
NOTIFICATION-TYPE    

starCGWServiceStart 1.1.8164.2.1247
A Serving Gateway (CGW) Service has started. Action to be Taken: No action required
Status: current Access: read-only
NOTIFICATION-TYPE    

starCGWServiceStop 1.1.8164.2.1248
A 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starMMENewConnectionsDisallowed 1.1.8164.2.1249
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starMMENewConnectionsAllowed 1.1.8164.2.1250
The MME chassis is now accepting new connections again. All conditions causing MME to disallow new connections have cleared.
Status: current Access: read-only
NOTIFICATION-TYPE    

starSAMOGServiceStart 1.1.8164.2.1251
A SAMOG Service has started Action to be Taken: No action required
Status: current Access: read-only
NOTIFICATION-TYPE    

starSAMOGServiceStop 1.1.8164.2.1252
A 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starCardSwitchoverStart 1.1.8164.2.1253
A 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starCardSwitchoverComplete 1.1.8164.2.1254
A 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starCardSwitchoverFailed 1.1.8164.2.1255
A 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starCardMigrateStart 1.1.8164.2.1256
A 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starCardMigrateComplete 1.1.8164.2.1257
A 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starCardMigrateFailed 1.1.8164.2.1258
A 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starTechSuppPasswdChanged 1.1.8164.2.1259
A 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starPMIPPathFailure 1.1.8164.2.1260
PMIP Path Failure. Possibe reason: This trap will be triggered by MAGMGR/HAMGR when path failure or node restart is detected.
Status: current Access: read-only
NOTIFICATION-TYPE    

starPMIPPathFailureClear 1.1.8164.2.1261
PMIP Control Path Failure condition is no longer valid.
Status: current Access: read-only
NOTIFICATION-TYPE    

starHENBGWMMESCTPAssocDestAddrDown 1.1.8164.2.1262
A 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starHENBGWMMESCTPAssocDestAddrUp 1.1.8164.2.1263
A HENBGW MME SCTP Association Destination Address is up. This notification is only generated for Association Destination Address which have previously been declared down.
Status: current Access: read-only
NOTIFICATION-TYPE    

starMRMEServiceStart 1.1.8164.2.1264
A Multi Radio Management (MRME) Service has started. Action to be Taken: No action required
Status: current Access: read-only
NOTIFICATION-TYPE    

starMRMEServiceStop 1.1.8164.2.1265
A 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starSLSServiceStart 1.1.8164.2.1266
An SLS Service has started Action to be Taken: No action required
Status: current Access: read-only
NOTIFICATION-TYPE    

starSLSServiceStop 1.1.8164.2.1267
An 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starESMLCAssocDown 1.1.8164.2.1268
An 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starESMLCAssocUp 1.1.8164.2.1269
An ESMLC Association is up. This notification is only generated for Association which have previously been declared down.
Status: current Access: read-only
NOTIFICATION-TYPE    

starESMLCAllAssocDown 1.1.8164.2.1270
All 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starESMLCAllAssocDownClear 1.1.8164.2.1271
At least one ESMLC associations is up. This notification is only generated for all the Association which have previously been declared down.
Status: current Access: read-only
NOTIFICATION-TYPE    

starSBCServiceStart 1.1.8164.2.1272
An SBc Service has started Action to be Taken: No action required
Status: current Access: read-only
NOTIFICATION-TYPE    

starSBCServiceStop 1.1.8164.2.1273
An 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starCBCAssocDown 1.1.8164.2.1274
A 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starCBCAssocUp 1.1.8164.2.1275
A CBC Association is up.
Status: current Access: read-only
NOTIFICATION-TYPE    

starBFDSessUp 1.1.8164.2.1276
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starBFDSessDown 1.1.8164.2.1277
The 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starSRPSwitchoverOccured 1.1.8164.2.1278
An 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starHENBGWMMEOverloadStart 1.1.8164.2.1279
A HENBGW MME Overload Start message received. Condition Clear Alarm: A starHENBGWMMEOverloadStop notification will be generated when the HENBGW MME overload stop message received.
Status: current Access: read-only
NOTIFICATION-TYPE    

starHENBGWMMEOverloadStop 1.1.8164.2.1280
A 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starNpudriverECCError 1.1.8164.2.1281
A double bit ECC error occured. Action to be taken - RMA this card.
Status: current Access: read-only
NOTIFICATION-TYPE    

starGTPCRLFOverThreshold 1.1.8164.2.1282
GTP RLF Status update - GTP RLF Over Threshold.
Status: current Access: read-only
NOTIFICATION-TYPE    

starGTPCRLFOverLimit 1.1.8164.2.1283
GTP RLF Status update - GTP RLF Over Limit.
Status: current Access: read-only
NOTIFICATION-TYPE    

starGTPCRLFOverThresholdClear 1.1.8164.2.1284
GTP RLF Status update - GTP RLF Over Threshold Cleared.
Status: current Access: read-only
NOTIFICATION-TYPE    

starGTPCRLFOverLimitClear 1.1.8164.2.1285
GTP RLF Status update - GTP RLF Over Limit Cleared.
Status: current Access: read-only
NOTIFICATION-TYPE    

starS102ServiceStart 1.1.8164.2.1286
An S102 Service has started Action to be Taken: No action required
Status: current Access: read-only
NOTIFICATION-TYPE    

starS102ServiceStop 1.1.8164.2.1287
An 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starBGPPeerSessionIPv6Up 1.1.8164.2.1288
The 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starBGPPeerSessionIPv6Down 1.1.8164.2.1289
The 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starMMEEMBMSServiceStart 1.1.8164.2.1290
An MME-EMBM Service has started Action to be Taken: No action required
Status: current Access: read-only
NOTIFICATION-TYPE    

starMMEEMBMSServiceStop 1.1.8164.2.1291
An 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.
Status: current Access: read-only
NOTIFICATION-TYPE    

starMCEAssocDown 1.1.8164.2.1292
An 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starMCEAssocUp 1.1.8164.2.1293
A MCE Association is up.
Status: current Access: read-only
NOTIFICATION-TYPE    

starIuBcTcpConnDown 1.1.8164.2.1294
A 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
Status: current Access: read-only
NOTIFICATION-TYPE    

starIuBcTcpConnUp 1.1.8164.2.1295
A TCP Connection is up.
Status: current Access: read-only
NOTIFICATION-TYPE    

starSessCapReached 1.1.8164.2.1298
Session manager will start rejecting new calls as the capacity reached.
Status: current Access: read-only
NOTIFICATION-TYPE    

starSerdesLanePermDown 1.1.8164.2.1303
A 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..
Status: current Access: read-only
NOTIFICATION-TYPE    


starThreshAllFramedRoutes 1.1.8164.2.1304
All framed routes crosses user defined threshold.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshAllFramedRoutesClear 1.1.8164.2.1305
All framed routes crosses user defined threshold cleared.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshAllTotalRoutes 1.1.8164.2.1306
All total routes crosses user defined threshold.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshAllTotalRoutesClear 1.1.8164.2.1307
All total routes crosses user defined threshold cleared.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshVRFFramedRoutes 1.1.8164.2.1308
Total number of VRF framed routes crosses user defined threshold.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshVRFFramedRoutesClear 1.1.8164.2.1309
Total number of VRF framed routes crosses user defined threshold cleared.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshVRFTotalRoutes 1.1.8164.2.1310
Total number of VRF total routes crosses user defined threshold.
Status: current Access: read-only
NOTIFICATION-TYPE    

starThreshVRFTotalRoutesClear 1.1.8164.2.1311
Total number of VRF total routes crosses user defined threshold cleared.
Status: current Access: read-only
NOTIFICATION-TYPE    

starStatFilesizeExceeded 1.1.8164.2.1312
Actual Bulkstat filesize crosses 80% user defined Bulkstat filesize.
Status: current Access: read-only
NOTIFICATION-TYPE    

starStatFilesizeClear 1.1.8164.2.1313
Actual Bulkstat filesize crosses 80% user defined Bulkstat filesize condition cleared.
Status: current Access: read-only
NOTIFICATION-TYPE    

starentMIBConformance 1.1.8164.3
OBJECT IDENTIFIER    

starentMIBGroups 1.1.8164.3.1
OBJECT IDENTIFIER    

starentMIBCompliances 1.1.8164.3.2
OBJECT IDENTIFIER    

starentMIBCompliance2 1.1.8164.3.2.2
The compliance statement for ...
Status: current Access: read-only
MODULE-COMPLIANCE    

starChassisGroup 1.1.8164.3.1.1
A collection of objects providing information about a chassis
Status: current Access: read-only
OBJECT-GROUP    

starAlertGroup 1.1.8164.3.1.3
A collection of objects to control the rate at which traps can be generated
Status: current Access: read-only
OBJECT-GROUP    

starAlertTrapGroup 1.1.8164.3.1.4
A collection of traps related to trap thresholding
Status: current Access: read-only
NOTIFICATION-GROUP    

starTrapGroup 1.1.8164.3.1.5
A collection of objects which represent required notifications.
Status: current Access: read-only
NOTIFICATION-GROUP    

starTrapObsoleteGroup 1.1.8164.3.1.6
A collection of objects which represent obsolete notifications.
Status: obsolete Access: read-only
NOTIFICATION-GROUP    

starChassisObsoleteGroup 1.1.8164.3.1.7
A collection of objects which are obsolete.
Status: obsolete Access: read-only
OBJECT-GROUP