USR-VHA-MIB: View SNMP OID List / Download MIB

The commWorks enterprise defined MIB objects for VHA

This is the A10 connection registration Lifetime timer. The timer is started at the time of establishment of an A10 connection and updated during periodic re-registrations of the A10 connection. The A10 connection is cleared on expiry of this timer. The default value of the timer is 1800 seconds. When this value is equal to 65535, then the timer has infinite lifetime. If this value is equal to zero, then A10 connection has been released.

Number of seconds to wait for the Registration Acknowledge message from the PCF.

UDP port number used by the RP interface to communicate with the PCF. The default value for this parameter is 699.

Toggle for controlling Service Option 7 on the RP interface. Obsolete: This object is no longer used.

Toggle for controlling Service Option 15 on the RP interface. Obsolete: This object is no longer used.

Toggle for controlling Service Option 22 on the RP interface. Obsolete: This object is no longer used.

Toggle for controlling Service Option 23 on the RP interface. Obsolete: This object is no longer used.

Toggle for controlling Service Option 24 on the RP interface. Obsolete: This object is no longer used.

Toggle for controlling Service Option 25 on the RP interface. Obsolete: This object is no longer used.

Toggle for controlling Service Option 33 on the RP interface. Obsolete: This object is no longer used.

Maximum number of active sessions that this PDSN is allowed to process on its RP interface port. This value is MAX_SIMULTANEOUS_USERS + 1 and is dependent on the component being built

Number of times to retransmit the Registration Update message if the PCF does not send a Registration Acknowledge message or a Registration Request message (with accounting related information and Lifetime set to zero). The current implementation only supports the range 1..20

Toggle to enable or disable monitoring of raw data over RP Interface

Number in bytes displayed by R-P Protocol monitor

Resets VHA Statistics to zero. 1: Resets all the statistics. 2: Resets Connection statistics. 3: Resets GRE statistics. 4: Resets Registration statistics. 5: Resets Registration Denied statistics. 6: Resets Update statistics. 7: Resets Update Denied statistics. 8: Resets Security Violations statistics. **NOTE: this object is deprecated and replaced by usrVHAStatsResetTime. Behaviour: setting usrVHAResetStats to any value 1..8 will result in the same behaviour as setting usrVHAStatsResetTime to 0: All stats will be reset.

This MIB Object is Deprecated

Reading: Time the VHA statistics counters were last reset. The VHA statistics are valid from usrVHAStatsResetTime until present. Resetting counters causes a discontinuity in the monotonically increasing value of counters. Management stations that sample these counters need also to sample this object so that they can know that a discontinuity occurred with respect to the previous sample. Its value is number of seconds since EPOCH. EPOCH is seconds since 00:00:00 UTC, Jan 1, 1970. Writing: Writing 0 causes update of usrVHAStatsResetTime and the VHA counters to be reset to 0: usrVHAConnStats group scalars usrVHARegReqStats group scalars usrVHARegUpdStats group scalars usrVHASecurViolStats group scalars This object replaces usrVHAResetStats

Fragment size used by GRE to fragment data pkts

The VHA module will use GRE fragmentation based on this flag and the GRE Fragment Size

THis setting will determine if the Accounting feature (IMSI Encoding) for Motorola is enabled

Toggle to enable or disable sending out DAI CVSE in RP_REG_REPLY

The configurable parameter ranged at 1-10 seconds would utilized to control the working timing window size for the call events flow regulation for non-turbo mode

Allow a dynamic RNN key value to be used in place of the configured shared secret and SPI

The dynamic SPI value obtained from the FACN

This is for setting the filter access for all the VHA interfaces.

The name of the input filter for all VHA interfaces.

The name of the output filter for all VHA interfaces.

Determines whether or not the VHA module will support Sync PPP protocol (0x880B)

Will put the PDSN VHA interface in the SoftBusy state (ENABLE) or get the VHA out of the SoftBusy state (DISABLE)

Total number of A10/A11 connections initiated. Counter epoch is indicated by usrVHAStatsResetTime.

Number of A10/A11 connections released since the last counter reset. usrVHATotalConnReleas is the sum of the following values: [usrVHATotalConnReleas] = [usrVHATotalRPConnDeRegistered] + [usrVHATotalConnExps] + [usrVHATotalRPConnOther] Counter epoch is indicated by usrVHAStatsResetTime.

Total number of A10/A11 connections cleared due to expiry of Trp without receiving a periodic Registration Request with lifetime greater than zero. Counter epoch is indicated by usrVHAStatsResetTime.

Total number of Ingress Filtering Caused Releases. Counter epoch is indicated by usrVHAStatsResetTime. Obsolete: This object is not supported.

A table of all existings A10/A11 connections between PCF and PDSN.

An entry in the RP Connection Statistics Table. Counter epoch is indicated by usrVHAStatsResetTime.

PDSNs RP interface can support up to 4000 sessions. This value indicates the session number assigned to the connection by the PDSN.

This four octet value, along with the PCF-IP- Address and the PDSN-IP-Address, identifies the A10 connection on behalf of a packet data session. This value is set to the MN-Proxy-Id assigned to a packet data session by the PCF. This Key value is also inserted in the Key field of every GRE frame containing user data sent over the A10/A11 connection.

This four octet value identifies the IP address of the PCF that terminates the A10 connection.

This two octet field is used to differentiate multiple sessions at a mobile node. MN Connection ID is determined by the PCF.

The International Mobile Subscriber Identifier.

The number of seconds granted before registration is considered expired. A value of zero indicates a request for deregistration. A value of 65535 indicates infinity.

The number of seconds remaining before registration is considered expired.

The number of GRE encapsulated packets received from IP.

The number of GRE encapsulated packets delivered to IP for transmission.

The number of GRE encapsulated bytes received from IP. The GRE header bytes are not counted.

The number of GRE encapsulated bytes delivered to IP for transmission. The GRE header bytes are not counted

The RP session is considered active when an Airlink Record Identifier, inside the Vendor/Organization Specific Extension of the Registration Request, is set to RP ACTIVE START.

Ipaddress associated with this connection

User name associated with this connection

Call Type for this connection

Time when the PPP was reset. This is NTP time, it will give number of seconds since Jan 1, 1900.

Time when the PPP was first established This is NTP time, it will give number of seconds since Jan 1, 1900.

The number of seconds remaining before PPP session is considered expired.

The duration in seconds of the current session.

The value of service option recieved by PDSN over A11 interface.

Total Number of RP connections Obsolete: This was a value that went up and down. A syntax of Counter32 is invalid for this behavior. This object has been replaced by usrVHASessionsCurrent.

Total Number of RP connections released, due to a valid deregistration request. Counter epoch is indicated by usrVHAStatsResetTime.

Total Number of RP connections released, cause: PPP Layer Command Counter epoch is indicated by usrVHAStatsResetTime. Obsolete: This object is not supported.

Total Number of RP connections released, cause: other reasons

A table of all existings calls with their IMSI values.

An entry in the IMSI Association Table.

PDSNs RP interface can support up to 4000 sessions. This value indicates the session number assigned to the connection by the PDSN.

The International Mobile Subscriber Identifier in Decoded ASCII format.

The International Mobile Subscriber Identifier in Encoded ASCII format.

Current number of RP sessions (sum of active and dormant)

Current number of active RP sessions

A table of Access Network Identifiers(ANIDs) received by PDSN.

An entry in the VHA Access Network Identifier(ANID) Table.

Access Network Identifier(ANID) of the PCF received by PDSN over A11.

Ipaddress of the PCF that holds this ANID

Total number of RP Registration Requests received. Counter epoch is indicated by usrVHAStatsResetTime.

Total number of Registration Replies accepted. The code information element inside the Registration Accept message is equal to zero. Counter epoch is indicated by usrVHAStatsResetTime. Obsolete: This object has been replaced by usrVHARegReqAccept

Total number of valid Registration Requests received with a Lifetime of zero (requests to deregister). Deprecated - This counter is replaced by usrVHADeRegReqAccept Counter epoch is indicated by usrVHAStatsResetTime.

Total number of Registration Replies accepted in response to a deregistration request. The code information element inside the Registration Accept message is equal to zero. Counter epoch is indicated by usrVHAStatsResetTime. Obsolete: This object has been replaced by usrVHADeRegReqAccept

Total number of RP Registration Requests denied due to an unspecified reason. The code information element inside the Registration Accept message is equal to 128. Counter epoch is indicated by usrVHAStatsResetTime.

Total number of RP Registration Requests denied due to an administrative decision. The code information element inside the Registration Accept message is equal to 129. Counter epoch is indicated by usrVHAStatsResetTime.

Total number of RP Registration Requests denied due to insufficient resources. The code information element inside the Registration Accept message is equal to 130. Counter epoch is indicated by usrVHAStatsResetTime.

Total number of RP Registration Requests denied due to mobile nodes failed authentication. The code information element inside the Registration Accept message is equal to 131. Counter epoch is indicated by usrVHAStatsResetTime.

Total number of RP Registration Requests denied due to an identification mismatch. The code information element inside the Registration Accept message is equal to 133. Counter epoch is indicated by usrVHAStatsResetTime.

Total number of RP Registration Requests denied due to a poorly formed request. The code information element inside the Registration Accept message is equal to 134. Counter epoch is indicated by usrVHAStatsResetTime.

Total number of RP Registration Requests denied due to an unknown PDSN address. The code information element inside the Registration Accept message is equal to 136. Counter epoch is indicated by usrVHAStatsResetTime.

Total number of RP Registration Requests denied due to unavailability of requested reverse tunnel. The code information element inside the Registration Accept message is equal to 137. Counter epoch is indicated by usrVHAStatsResetTime.

Total number of RP Registration Requests denied due to T bit not set. This bit is part of the Flags information element inside the Registration Request message. The code information element inside the Registration Accept message is equal to 138. Counter epoch is indicated by usrVHAStatsResetTime.

Total number of RP Registration Requests denied due to an unrecognized Vendor ID field that is inside the Vendor/Organization Specific Extension information element. The code information element inside the Registration Accept message is equal to 141. Counter epoch is indicated by usrVHAStatsResetTime.

Total number of Registration Requests denied usrVHARegReqDenied is the sum of these values: [usrVHARegReqDenied] = [usrVHARegReqInitDenied] + [usrVHAReRegReqDenied] + [usrVHADeRegReqDenied] Counter epoch is indicated by usrVHAStatsResetTime.

Total number of Registration Requests from the PCF silently discarded without being processed by the PDSN Counter epoch is indicated by usrVHAStatsResetTime.

Number of Initial Registration Requests accepted from the PCF. Counter epoch is indicated by usrVHAStatsResetTime.

Number of Initial Registration Requests denied from the PCF. Counter epoch is indicated by usrVHAStatsResetTime.

Number of Re-Registration Requests accepted from the PCF. Counter epoch is indicated by usrVHAStatsResetTime.

Number of Re-Registration Requests denied from the PCF. Counter epoch is indicated by usrVHAStatsResetTime.

Number of De-Registration Requests denied from the PCF. Counter epoch is indicated by usrVHAStatsResetTime.

Total number of Registration Requests accepted from the PCF. usrVHARegReqAccept is the sum of these values: [usrVHARegReqAccept] = [usrVHARegReqInitAccept] + [usrVHAReRegReqAccept] + [usrVHADeRegReqAccept] Counter epoch is indicated by usrVHAStatsResetTime.

Total number of DeRegistration Requests accepted from the PCF. Counter epoch is indicated by usrVHAStatsResetTime.

Total number of valid Registration Updates transmitted to PCF. Counter epoch is indicated by usrVHAStatsResetTime.

Total number of Registration Acknowledgements received from the PCF with status code of zero. Counter epoch is indicated by usrVHAStatsResetTime.

Total number of Registration Acknowledgements received from the PCF with status code of 128 (reason unspecified). Counter epoch is indicated by usrVHAStatsResetTime.

Total number of Registration Acknowledgements received from the PCF with status code of 129 (administratively prohibited). Counter epoch is indicated by usrVHAStatsResetTime.

Total number of Registration Acknowledgements received from the PCF with status code of 131 (sending node - PDSN - failed authentication). Counter epoch is indicated by usrVHAStatsResetTime.

Total number of Registration Acknowledgements received from the PCF with status code of 133 (identification mismatch). Counter epoch is indicated by usrVHAStatsResetTime.

Total number of Registration Acknowledgements received from the PCF with status code of 134 (poorly formed Registration Update). Counter epoch is indicated by usrVHAStatsResetTime.

Total number of Registration Updates denied by the RAN. usrVHATotalRegUpdateDenied is the sum of these values: [usrVHATotalRegUpdateDenied] = [usrVHARegAckUnspecified] + [usrVHARegAckAdmProhibited] + [usrVHARegAckFailedAuth] + [usrVHARegAckIDMismatch] + [usrVHARegAckPoorlyFormed] + [usrVHARegAckDeniedOther] Counter epoch is indicated by usrVHAStatsResetTime.

usrVHATotalRegUpdateNotAck is incremented if the expected registration acknowledge is not received from the PCF within the time Tregupd. Counter epoch is indicated by usrVHAStatsResetTime.

Total number of Initial Registration Updates transmitted to PCF. Counter epoch is indicated by usrVHAStatsResetTime.

Total number of Registration Updates re-transmitted to PCF. Counter epoch is indicated by usrVHAStatsResetTime.

Total number of Registration Updates discarded Counter epoch is indicated by usrVHAStatsResetTime.

Number of Registration Updates transmitted, due to RP lifetime expiration Counter epoch is indicated by usrVHAStatsResetTime.

Number of Registration Updates transmitted, due to PPP layer command Counter epoch is indicated by usrVHAStatsResetTime. OBSOLETE: This object is not supported.

Number of Registration Updates transmitted, due to other reasons Counter epoch is indicated by usrVHAStatsResetTime.

Total number of Registration Acknowledgements received from the PCF. Counter epoch is indicated by usrVHAStatsResetTime.

Total number of Registration Acknowledgements received from PCF with a status code that is currently not further speficied by the PDSN. Counter epoch is indicated by usrVHAStatsResetTime.

A table for configuring mobility security associations between the Radio Node and the PDSN.

An entry in the PDSN Security Configuration Table.

RP interface can support up to 512 mobility security associations. - The range has been changed from 1-100 to 1-512 for PDSN Rel 4.0

The IP Address of the Radio Node with which this RP interface shares the mobility security association.

The SPI is the 4-byte opaque index within the Mobility Security Association which selects the specific security parameters to be used to authenticate the Radio Node.

The shared secret key for the security associations. Reading this object will always return zero length value for SNMP.

The value represents how close the timestamp, contained in the Identification information element of the Registration Request or the Registration Acknowledge message, should be to the PDSNs time of day clock. This time tolerance is used in conjunction with timestamp replay protection against replay attacks.

This object is used to add, modify, and delete rows for the security association table.

Toggle to enable or disable authentication of A11 messages over RP Interface

This setting will determine whether to zero pad secrets of less than 16

Total number of RP security violations encountered by this PDSN. usrVHASecurTotalViolations is the sum of these values: [usrVHASecurTotalViolations] = [usrVHASecurMissingMSA] + [usrVHASecurBadAuthenticator] + [usrVHASecurBadSPI] + [usrVHASecurMissingMHAuthExt] + [usrVHASecurMissingRUAuthExt] Counter epoch is indicated by usrVHAStatsResetTime.

Total number of RP security violations due to missing or improper Mobility Security Association (MSA) between the PCF and the PDSN. Counter epoch is indicated by usrVHAStatsResetTime.

Total number of RP security violations due to bad Authenticator field. This field is part of either Mobile-Home Authentication Extension information element or the Registration Update Authentication Extension information element. Counter epoch is indicated by usrVHAStatsResetTime.

Total number of security violations due to bad Identification information element. This eight octet element is used by the PCF and the PDSN for matching the Registration Requests with Registration Replies and Registration Updates with Registration Acknowledge messages. It also protects against the replay attacks (section 5.6, RFC 2002). Counter epoch is indicated by usrVHAStatsResetTime. Deprecated: This object is a duplicate of usrVHARegDenIDMismatch.

Total number of RP security violations due to bad SPI field. This field is part of either Mobile-Home Authentication Extension information element or the Registration Update Authentication Extension information element. Counter epoch is indicated by usrVHAStatsResetTime.

Total number of RP security violations due to missing Mobile-Home Authentication Extension inside the Registration Request message. Counter epoch is indicated by usrVHAStatsResetTime.

Total number of RP security violations due to missing Registration Update Authentication Extension inside the Registration Acknowledge message. Counter epoch is indicated by usrVHAStatsResetTime.

A table containing information about security violations.

Information about a particular security violation.

PDSN can store up to 100 entries for a particular security violation based on the violators IP address.

Violators IP address. This address may not be in the Mobility Security Association table.

Total number of security violations coming from the this violators IP address.

SPI of the most recent security violation coming from this IP address. If the security violation is due to an identification mismatch, then this is the SPI from the Mobile-Home Authentication Extension. If the security violation is due to an invalid authenticator, then this is the SPI from the offending authentication extension. In all other cases, it should be set to zero.

Time of the most recent security violation coming from this IP address. This is NTP time, it will give number of seconds since Jan 1, 1900.

Low-order 32 bits of identification used in Registration Request or Registration Acknowledge of the most recent security violation coming from this IP address.

High-order 32 bits of identification used in Registration Request or Registration Acknowledge of the most recent security violation coming from this IP address.

Reason for the most recent security violation coming from this IP address.

Total number of GRE encapsulated packets received from IP. Counter epoch is indicated by usrVHAStatsResetTime.

Total number of GRE encapsulated packets delivered to IP for transmission. Counter epoch is indicated by usrVHAStatsResetTime.

Total number of GRE encapsulated bytes received from IP. The GRE header bytes are not counted. Counter epoch is indicated by usrVHAStatsResetTime.

Total number of GRE encapsulated bytes delivered to IP for transmission. The GRE header bytes are not counted. Counter epoch is indicated by usrVHAStatsResetTime.

The name of the configuration file for VHA. If this value is empty, then the default file name is @file://VHAProcess.cfg.

The Configuration File Manager Flag for saving VHA configurable parameters.

The events for VHA traps

This trap is generated when authentication fails on the Registration Request message.

This trap is generated when authentication fails on the Registration Acknowledge message.

The SNMP trap that is generated when usrVHASessionsAlarmsState goes to critical and usrVHASessionsAlarmsEnabled is true This alarm occurs when the sum of active and dormant RP session reaches or exceeds the critical threshold.

The SNMP trap that is generated when usrVHASessionsAlarmsState goes to major and usrVHASessionsAlarmsEnabled is true This alarm occurs when the sum of active and dormant RP session reaches or exceeds the major threshold while state is clear but does not reach or exceed the critical threshold.

The SNMP trap that is generated when usrVHASessionsAlarmsState goes to clear and usrVHASessionsAlarmsEnabled is true This alarm occurs when the sum of active and dormant RP session falls to or below the clear threshold after a major or critical alarm has been declared.

The SNMP trap that is generated when usrVHAActiveSessionsAlarmsState goes to critical and usrVHAActiveSessionsAlarmsEnabled is true This alarm occurs when the number of active RP session reaches or exceeds the critical threshold.

The SNMP trap that is generated when usrVHAActiveSessionsAlarmsState goes to major and usrVHAActiveSessionsAlarmsEnabled is true This alarm occurs when the number of active RP session reaches or exceeds the major threshold while state is clear but does not reach or exceed the critical threshold.

The SNMP trap that is generated when usrVHAActiveSessionsAlarmsState goes to clear and usrVHAActiveSessionsAlarmsEnabled is true This alarm occurs when the number of active RP session falls to or below the clear threshold after a major or critical alarm has been declared.

The SNMP trap that is generated when usrVHAFailedSessionsAlarmsState goes to clear and usrVHAFailedSessionsAlarmsEnabled is true This alarm occurs when the RP Failed Sessions as measured number of RP Reg Req Denied in the last measurement interval falls to or below the clear threshold after a major or critical alarm has been declared.

The SNMP trap that is generated when usrVHAFailedSessionsAlarmsState goes to major and usrVHAFailedSessionsAlarmsEnabled is true This alarm occurs when the RP Failed Sessions as measured number of RP Reg Req Denied in the last measurement interval reaches or exceeds the major threshold while state is clear but does not reach or exceed the critical threshold.

The SNMP trap that is generated when usrVHAFailedSessionsAlarmsState goes to major and usrVHAFailedSessionsAlarmsEnabled is true This alarm occurs when the RP Failed Sessions as measured number of RP Reg Req Denied in the last measurement interval falls to or below the clear threshold after a major or critical alarm has been declared.

The SNMP trap that is generated when usrVHAPktThroughputAlarmsState goes to clear and usrVHAPktThroughputAlarmsEnabled is true This alarm occurs when the RP Packet Throughput as measured number of RP packets sent or received in last interval falls to or below the clear threshold after a major or critical alarm has been declared.

The SNMP trap that is generated when usrVHAPktThroughputAlarmsState goes to major and usrVHAPktThroughputAlarmsEnabled is true This alarm occurs when the RP Packet Throughput as measured number of RP packets sent or received in last interval reaches or exceeds the major threshold while state is clear but does not reach or exceed the critical threshold.

The SNMP trap that is generated when usrVHAPktThroughputAlarmsState goes to clear and usrVHAPktThroughputAlarmsEnabled is true This alarm occurs when the RP Packet Throughput as measured number of RP packets sent or received in last interval falls to or below the clear threshold after a major or critical alarm has been declared.

The critical alarm threshold for usrVHASessionsCurrent gauge. The value of this object will be automatically set to the lesser of usrVHAMaxSessions or the internal VHA Max session limit, whichever is less. IF usrVHASessionsAlarmState is not critical and the current gauge value is equal or greater than this threshold, THEN usrVHASessionsAlarmState will change to critical. See usrVHASessionsAlarmState for TRAP generation details.

The major alarm threshold for usrVHASessionsCurrent gauge. The allowed range of this object is 0 to usrVHAMaxSessions. The object is also constrained to be less than or equal to usrVHASessionsCriticalAlarmThresh. If usrVHAMaxSessions is reduced below the value of this object, this object will automatically reduced so that this constraint holds. Value of 0 disables this threshold. IF this object is set to a non-zero value equal or less than the current value of usrVHASessionsClearAlarmThresh, THEN usrVHASessionsClearAlarmThresh will be automatically reduced to a valid value. This value is set indirectly by setting usrVHASessionsMajorAlarmThreshPct Changing threshold values causes the alarm state to be re-evaluated. IF usrVHASessionsAlarmState is clear and the current gauge value is equal or greater than this threshold, and the current gauge value is less than non-zero usrVHASessionsCriticalAlarmThresh, and the threshold is not 0, THEN usrVHASessionsAlarmState will change to major. See usrVHASessionsAlarmState for TRAP generation details.

The alarm clear threshold for usrVHASessionsCurrent gauge. The allowed range of this object is 0 to usrVHAMaxSessions. This object must also be less than non-zero usrVHASessionsMajorAlarmThresh and usrVHASessionsCricalAlarmThresh. IF usrVHASessionsMajorAlarmThresh is non zero, THEN object must be less than usrVHASessionsMajorAlarmThresh. This value is set indirectly by setting usrVHASessionsClearAlarmThreshPct Changing the threshold value causes the alarm state to be re-evaluated. IF usrVHASessionsAlarmState is not clear and the current gauge value is equal or less than this threshold, THEN usrVHASessionsAlarmState will change to clear. See usrVHASessionsAlarmState for TRAP generation details.

The major alarm threshold for usrVHASessionsCurrent gauge expressed as a percentage of usrVHAMaxSessions. The allowed range of this object is 0 to 100. Writing this object causes usrVHASessionsMajorAlarmThresh to be re-calculated. Writing usrVHASessionsMajorAlarmThresh causes this object to be re-calculated. See usrVHASessionsMajorAlarmThresh for effects of changing threshold value such as causing the alarm state to be re-evaluated.

The clear alarm threshold for usrVHASessionsCurrent gauge expressed as a percentage of usrVHAMaxSessions. The allowed range of this object is 0 to 100. Writing this object causes usrVHASessionsClearAlarmThresh to be re-calculated. Writing usrVHASessionsClearAlarmThresh causes this object to be re-calculated. See usrVHASessionsClearAlarmThresh for effects of changing threshold value such as causing the alarm state to be re-evaluated.

This object controls trap generation when usrVHASessionAlarmState changes. See usrVHASessionsAlarmState for alarm details.

Alarm state is maintained by PDSN by comparing usrVHASessionsCurrent with critical, major, and clear alarm thresholds. IF alarm state changes to critical, AND usrVHASessionsTrapsEnabled is true THEN usrVHASessionsCriticalAlarm TRAP will be sent. IF alarm state changes to major, AND usrVHASessionsTrapsEnabled is true THEN usrVHASessionsMajorAlarm TRAP will be sent. IF alarm state changes to clear, AND usrVHASessionsTrapsEnabled is true THEN usrVHASessionsCriticalAlarm TRAP will be sent. IF alarm state changes, THEN usrVHASessionsAlarmTime is updated with the current time regardless of usrVHASessionsTrapsEnabled and usrVHASessionsAlarmChanges is incremented. This allows alarm state and time information to be retrieved by SNMP management stations that dont support SNMP traps or when traps are intentionally disabled to reduce trap processing load on the SNMP management station. Writing a clear value will force the alarm state to go to clear. This will count as a state change and cause a trap if the state was major or critical. This step conceptually occurs before comparing the alarm thresholds. If major or critical thresholds are exceeded, the appropriate state change and trap occur. This means that writing clear may cause 0, 1, or 2 alarm state changes and traps.

The time of the last usrVHASessionsAlarmState state change. If the state has never changed, this value will be zero.

Count of usrVHASessionsAlarmState changes.

The critical alarm threshold for usrVHAActiveSessionsCurrent gauge. The allowed range of this object is 0 to usrVHAMaxSessions. If usrVHAMaxSessions is reduced below the value of this object, this object will automatically reduced so that this constraint holds. Object value of 0 disables this alarm and threshold.. IF this object is set to a non-zero value equal or less than the current value of usrVHAActiveSessionsMajorAlarmThresh, THEN usrVHAActiveSessionsMajorAlarmThresh will be automatically reduced to a valid value. IF this object is set to a non-zero value equal or less than the current value of usrVHAActiveSessionsClearAlarmThresh, THEN usrVHAActiveSessionsClearAlarmThresh will be automatically reduced to a valid value. This value is set indirectly by setting usrVHAActiveSessionsCriticalAlarmThreshPct Changing threshold values causes the alarm state to be re-evaluated. IF usrVHAActiveSessionsAlarmState is not critical and the current gauge value is equal or greater than this critical threshold, and this critical threshold is non-zero, THEN usrVHAActiveSessionsAlarmState will change to critical. See usrVHAActiveSessionsAlarmState for TRAP generation details.

The major alarm threshold for usrVHAActiveSessionsCurrent gauge. The allowed range of this object is 0 to usrVHAMaxSessions. The object is also constrained to be less than or equal to usrVHAActiveSessionsCriticalAlarmThresh. If usrVHAMaxSessions is reduced below the value of this object, this object will automatically reduced so that this constraint holds. Value of 0 disables this threshold. IF this object is set to a non-zero value equal or less than the current value of usrVHAActiveSessionsClearAlarmThresh, THEN usrVHAActiveSessionsClearAlarmThresh will be automatically reduced to a valid value. This value is set indirectly by setting usrVHAActiveSessionsMajorAlarmThreshPct Changing threshold values causes the alarm state to be re-evaluated. IF usrVHAActiveSessionsAlarmState is clear and the current gauge value is equal or greater than this threshold, and the current gauge value is less than non-zero usrVHAActiveSessionsCriticalAlarmThresh, and the threshold is not zero, THEN usrVHAActiveSessionsAlarmState will change to major. See usrVHAActiveSessionsAlarmState for TRAP generation details.

The alarm clear threshold for usrVHAActiveSessionsCurrent gauge. The allowed range of this object is 0 to usrVHAMaxSessions. This object must also be less than non-zero usrVHAActiveSessionsMajorAlarmThresh and non-zero usrVHAActiveSessionsCricalAlarmThresh. This value is set indirectly by setting usrVHAActiveSessionsClearAlarmThreshPct Changing the threshold value causes the alarm state to be re-evaluated. IF usrVHAActiveSessionsAlarmState is not clear and the current gauge value is equal or less than this threshold, THEN usrVHAActiveSessionsCriticalAlarmState will change to clear. See usrVHAActiveSessionsAlarmState for trap generation details.

The major alarm threshold for usrVHAActiveSessionsCurrent gauge expressed as a percentage of usrVHAMaxSessions. The allowed range of this object is 0 to 100. Writing this object causes usrVHAActiveSessionsMajorAlarmThresh to be re-calculated. Writing usrVHAActiveSessionsMajorAlarmThresh causes this object to be re-calculated. See usrVHAActiveSessionsMajorAlarmThresh for effects of changing threshold value such as causing the alarm state to be re-evaluated.

The major alarm threshold for usrVHAActiveSessionsCurrent gauge expressed as a percentage of usrVHAMaxSessions. The allowed range of this object is 0 to 100. Writing this object causes usrVHAActiveSessionsMajorAlarmThresh to be re-calculated. Writing usrVHAActiveSessionsMajorAlarmThresh causes this object to be re-calculated. See usrVHAActiveSessionsMajorAlarmThresh for effects of changing threshold value such as causing the alarm state to be re-evaluated.

The clear alarm threshold for usrVHAActiveSessionsCurrent gauge expressed as a percentage of usrVHAMaxSessions. The allowed range of this object is 0 to 100. Writing this object causes usrVHAActiveSessionsClearAlarmThresh to be re-calculated. Writing usrVHAActiveSessionsClearAlarmThresh causes this object to be re-calculated. See usrVHAActiveSessionsClearAlarmThresh for effects of changing threshold value such as causing the alarm state to be re-evaluated.

This object controls trap generation when usrVHASActiveSessionsAlarmState changes. See usrVHAActiveSessionsAlarmState for alarm details.

Alarm state is maintained by PDSN by comparing usrVHAActiveSessionsCurrent with critical, major, and clear alarm thresholds. IF alarm state changes to critical, AND usrVHAActiveSessionsTrapsEnabled is true THEN usrVHAActiveSessionsCriticalAlarm TRAP will be sent. IF alarm state changes to major, AND usrVHAActiveSessionsTrapsEnabled is true THEN usrVHAActiveSessionsMajorAlarm TRAP will be sent. IF alarm state changes to clear, AND usrVHAActiveSessionsTrapsEnabled is true THEN usrVHAActiveSessionsCriticalAlarm TRAP will be sent. IF alarm state changes, THEN usrVHAActiveSessionsAlarmTime is updated with the current time regardless of usrVHAActiveSessionsTrapsEnabled and usrVHAActiveSessionsAlarmChanges is incremented. This allows alarm state and time information to be retrieved by SNMP management stations that dont support SNMP traps or when traps are intentionally disabled to reduce trap processing load on the SNMP management station. Writing a clear value will force the alarm state to go to clear. This will count as a state change and cause a trap if the state was major or critical. This step conceptually occurs before comparing the alarm thresholds. If major or critical thresholds are exceeded, the appropriate state change and trap occur. This means that writing clear may cause 0, 1, or 2 alarm state changes and traps.

Time last usrVHAActiveSessionsAlarmState state change. If the state has never changed, this value will be zero.

Count of usrVHAActiveSessionsAlarmState changes.

The critical alarm threshold for usrVHAFailedSessionsValue gauge. Object value of 0 disables this alarm and threshold. IF this object is set to a non-zero value equal or less than the current value of usrVHAFailedSessionsMajorAlarmThresh, THEN usrVHAFailedSessionsMajorAlarmThresh will be automatically reduced to a valid value. IF this object is set to a non-zero value equal or less than the current value of usrVHAFailedSessionsClearAlarmThresh, THEN usrVHAFailedSessionsClearAlarmThresh will be automatically reduced to a valid value. Agent is allowed to either reject a SET which violates these constraints, or adjust the object value such that the constraints hold. Changing threshold values causes the alarm state to be re-evaluated. IF usrVHAFailedSessionsAlarmState is not critical and the current gauge value is equal or greater than this critical threshold, and this critical threshold is non-zero, THEN usrVHAFailedSessionsAlarmState will change to critical. See usrVHAFailedSessionsAlarmState for TRAP generation details.

The major alarm threshold for usrVHAFailedSessionsValue gauge. Value of 0 disables this threshold. IF this object is set to a non-zero value equal or less than the current value of usrVHAFailedSessionsClearAlarmThresh, THEN usrVHAFailedSessionsClearAlarmThresh will be automatically reduced to a valid value. This value is set indirectly by setting usrVHAFailedSessionsMajorAlarmThreshPct Changing threshold values causes the alarm state to be re-evaluated. IF usrVHAFailedSessionsAlarmState is clear and the current gauge value is equal or greater than this threshold, and the current gauge value is less than non-zero usrVHAFailedSessionsCriticalAlarmThresh, and the threshold is not zero, THEN usrVHAFailedSessionsAlarmState will change to major. See usrVHAFailedSessionsAlarmState for TRAP generation details.

The alarm clear threshold for usrVHAFailedSessionsValue gauge. This object must be less than usrVHAFailedSessionsMajorAlarmThresh (if non-zero) usrVHAFailedSessionsCricalAlarmThresh (if non-zero).. This value is set indirectly by setting usrVHAFailedSessionsClearAlarmThreshPct Changing the threshold value causes the alarm state to be re-evaluated. IF usrVHAFailedSessionsAlarmState is not clear and the current gauge value is equal or less than this threshold, THEN usrVHAFailedSessionsCriticalAlarmState will change to clear. See usrVHAFailedSessionsAlarmState for trap generation details.

The major alarm threshold for usrVHAFailedSessionsValue gauge expressed as a percentage of usrVHAFailedSessionsCriticalAlarmThesh. The allowed range of this object is 0 to 100. Writing this object causes usrVHAFailedSessionsMajorAlarmThresh to be re-calculated. Writing usrVHAFailedSessionsMajorAlarmThresh causes this object to be re-calculated. See usrVHAFailedSessionsMajorAlarmThresh for effects of changing threshold value such as causing the alarm state to be re-evaluated.

The clear alarm threshold for usrVHAFailedSessionsValue gauge expressed as a percentage of usrVHAFailedSessionsCriticalAlarmThesh. The allowed range of this object is 0 to 100. Writing this object causes usrVHAFailedSessionsClearAlarmThresh to be re-calculated. Writing usrVHAFailedSessionsClearAlarmThresh causes this object to be re-calculated. See usrVHAFailedSessionsClearAlarmThresh for effects of changing threshold value such as causing the alarm state to be re-evaluated.

This object controls trap generation when usrVHAFailedSessionsAlarmState changes. See usrVHAFailedSessionsAlarmState for alarm details.

The interval in seconds over which the RP Failed Sessions (RP Sessions that failed to establish) are sampled (measured) to determine a packet throughput by making a delta between a previous sample and a new sample. The delta is stored in usrVHAFailedSessionsValue and thresholds are checked. Value of zero disables RP Failed Sessions alarms and forces alarm state to clear.

Alarm state is maintained by PDSN by comparing usrVHAFailedSessionsValue with critical, major, and clear alarm thresholds. IF alarm state changes to critical, AND usrVHAFailedSessionsTrapsEnabled is true THEN usrVHAFailedSessionsCriticalAlarm TRAP will be sent. IF alarm state changes to major, AND usrVHAFailedSessionsTrapsEnabled is true THEN usrVHAFailedSessionsMajorAlarm TRAP will be sent. IF alarm state changes to clear, AND usrVHAFailedSessionsTrapsEnabled is true THEN usrVHAFailedSessionsCriticalAlarm TRAP will be sent. IF alarm state changes, THEN usrVHAFailedSessionsAlarmTime is updated with the current time regardless of usrVHAFailedSessionsTrapsEnabled and usrVHAFailedSessionsAlarmChanges is incremented. This allows alarm state and time information to be retrieved by SNMP management stations that dont support SNMP traps or when traps are intentionally disabled to reduce trap processing load on the SNMP management station. Writing a clear value will force the alarm state to go to clear. This will count as a state change and cause a trap if the state was major or critical. This step conceptually occurs before comparing the alarm thresholds. If major or critical thresholds are exceeded, the appropriate state change and trap occur. This means that writing clear may cause 0, 1, or 2 alarm state changes and traps.

Time of last usrVHAFailedSessionsAlarmState state change. If the state has never changed, this value will be zero.

Count of usrVHAFailedSessionsAlarmState changes.

The value of the statistic during the last measurement interval. usrVHARegReqDenied is sampled at the start and at the end of a measurement interval. This MIB object represents the delta value between these two samples. The interval MIB object is usrVHAFailedSessionsInterval. The value of this MIB object is the value that is compared with the 3 thresholds for alarm generation. The value during the current measurement period is not made available until the measurement period is completed and will remain available until the next period completes.

The critical alarm threshold for usrVHAPktThroughputValue gauge. Object value of 0 disables this alarm and threshold. IF this object is set to a non-zero value equal or less than the current value of usrVHAPktThroughputMajorAlarmThresh, THEN usrVHAPktThroughputMajorAlarmThresh will be automatically reduced to a valid value. IF this object is set to a non-zero value equal or less than the current value of usrVHAPktThroughputClearAlarmThresh, THEN usrVHAPktThroughputClearAlarmThresh will be automatically reduced to a valid value. Agent is allowed to either reject a SET which violates these constraints, or adjust the object value such that the constraints hold. Changing threshold values causes the alarm state to be re-evaluated. IF usrVHAPktThroughputAlarmState is not critical and the current gauge value is equal or greater than this critical threshold, and this critical threshold is non-zero, THEN usrVHAPktThroughputAlarmState will change to critical. See usrVHAPktThroughputAlarmState for TRAP generation details.

The major alarm threshold for usrVHAPktThroughputValue gauge. Value of 0 disables this threshold. IF this object is set to a non-zero value equal or less than the current value of usrVHAPktThroughputClearAlarmThresh, THEN usrVHAPktThroughputClearAlarmThresh will be automatically reduced to a valid value. This value is set indirectly by setting usrVHAPktThroughputMajorAlarmThreshPct Changing threshold values causes the alarm state to be re-evaluated. IF usrVHAPktThroughputAlarmState is clear and the current gauge value is equal or greater than this threshold, and the current gauge value is less than non-zero usrVHAPktThroughputCriticalAlarmThresh, and the threshold is not zero, THEN usrVHAPktThroughputAlarmState will change to major. See usrVHAPktThroughputAlarmState for TRAP generation details.

The alarm clear threshold for usrVHAPktThroughputValue gauge. This object must be less than usrVHAPktThroughputMajorAlarmThresh (if non-zero) usrVHAPktThroughputCricalAlarmThresh (if non-zero).. This value is set indirectly by setting usrVHAPktThroughputMajorAlarmThreshPct. Changing the threshold value causes the alarm state to be re-evaluated. IF usrVHAPktThroughputAlarmState is not clear and the current gauge value is equal or less than this threshold, THEN usrVHAPktThroughputCriticalAlarmState will change to clear. See usrVHAPktThroughputAlarmState for trap generation details.

The major alarm threshold for usrVHAPktThroughputValue gauge expressed as a percentage of usrVHAPktThroughputCriticalAlarmThesh. The allowed range of this object is 0 to 100. Writing this object causes usrVHAPktThroughputMajorAlarmThresh to be re-calculated. Writing usrVHAPktThroughputMajorAlarmThresh causes this object to be re-calculated. See usrVHAPktThroughputMajorAlarmThresh for effects of changing threshold value such as causing the alarm state to be re-evaluated.

The clear alarm threshold for usrVHAPktThroughputValue gauge expressed as a percentage of usrVHAPktThroughputCriticalAlarmThesh. The allowed range of this object is 0 to 100. Writing this object causes usrVHAPktThroughputClearAlarmThresh to be re-calculated. Writing usrVHAPktThroughputClearAlarmThresh causes this object to be re-calculated. See usrVHAPktThroughputClearAlarmThresh for effects of changing threshold value such as causing the alarm state to be re-evaluated.

This object controls trap generation when usrVHASActiveSessionsAlarmState changes. See usrVHAPktThroughputAlarmState for alarm details.

The interval in seconds over which the RP packet counters are sampled (measured) to determine a packet throughput by making a delta between a previous sample and a new sample. The delta is stored in usrVHAPktThroughputValue and thresholds are checked. Value of zero disables RP Packet Throughput alarms and forces alarm state to clear.

Alarm state is maintained by PDSN by comparing usrVHAPktThroughputValue with critical, major, and clear alarm thresholds. IF alarm state changes to critical, AND usrVHAPktThroughputTrapsEnabled is true THEN usrVHAPktThroughputCriticalAlarm TRAP will be sent. IF alarm state changes to major, AND usrVHAPktThroughputTrapsEnabled is true THEN usrVHAPktThroughputMajorAlarm TRAP will be sent. IF alarm state changes to clear, AND usrVHAPktThroughputTrapsEnabled is true THEN usrVHAPktThroughputCriticalAlarm TRAP will be sent. IF alarm state changes, THEN usrVHAPktThroughputAlarmTime is updated with the current time regardless of usrVHAPktThroughputTrapsEnabled and usrVHAPktThroughputAlarmChanges is incremented. This allows alarm state and time information to be retrieved by SNMP management stations that dont support SNMP traps or when traps are intentionally disabled to reduce trap processing load on the SNMP management station. Writing a clear value will force the alarm state to go to clear. This will count as a state change and cause a trap if the state was major or critical. This step conceptually occurs before comparing the alarm thresholds. If major or critical thresholds are exceeded, the appropriate state change and trap occur. This means that writing clear may cause 0, 1, or 2 alarm state changes and traps.

Time of last usrVHAPktThroughputAlarmState state change. If the state has never changed, this value will be zero.

Count of usrVHAPktThroughputAlarmState changes.

Count of RP Packets sent and received. This is the sum of usrVHATotalCREPktsRcvd - A10 Packets received usrVHATotalGREPktsTrans - A10 Packets sent usrVHARegReqRcvd - A11 Packets received (1 of 3) usrVHARegAcknowledge - A11 Packets received (2 of 3) usrVHATotalRegUpdateDenied - A11 Packets received (3 of 3) usrVHARegReqAccept - A11 Packets sent (1 of 3) usrVHARegReqDenied - A11 Packets sent (2 of 3) usrVHARegUpdate - A11 Packets sent (3 of 3)

The value of the statistic during the last measurement interval. usrVHAPktCounts is sampled at the start and at the end of a measurement interval. This MIB object represents the delta value between these two samples. The interval MIB object is usrVHAPktThroughputInterval. The value of this MIB object is the value that is compared with the 3 thresholds for alarm generation. The value during the current measurement period is not made available until the measurement period is completed ahd will remain available until the next period completes.

A table of R-P Registration request stats based on Service Option

An entry in the VHA Service Option Stats Table.

The value of Service Option recived over A11 interface by PDSN.

Total number of valid Registration Requests received for the Service Option.

Total number of Registration Replies accepted with code information element inside the Registration Accept message equal to zero for this service option.

Total number of valid Registration Requests received with a Lifetime of zero (requests to deregister) for this service option.

Total number of Registration Replies accepted in response to a deregistration request with code information element inside the Registration Accept message equal to zero for this service option.