CISCO-GPRS-ACC-PT-MIB

Unsigned32 (1..65535)

A locally unique identifier for this access point on this Gateway.

RowStatus1 = active2 = notInService3 = notReady4 = createAndGo5 = createAndWait6 = destroyThe RowStatus textual convention is used to manage the creation and deletion of conceptual rows, and is used as the value of the SYNTAX clause for the status column of a conceptual row (as described in Section 7.7.1 of [2].) The status column has six defined values: - `active', which indicates that the conceptual row is available for use by the managed device; - `notInService', which indicates that the conceptual row exists in the agent, but is unavailable for use by the managed device (see NOTE below); 'notInService' has no implication regarding the internal consistency of the row, availability of resources, or consistency with the current state of the managed device; - `notReady', which indicates that the conceptual row exists in the agent, but is missing information necessary in order to be available for use by the managed device (i.e., one or more required columns in the conceptual row have not been instanciated); - `createAndGo', which is supplied by a management station wishing to create a new instance of a conceptual row and to have its status automatically set to active, making it available for use by the managed device; - `createAndWait', which is supplied by a management station wishing to create a new instance of a conceptual row (but not make it available for use by the managed device); and, - `destroy', which is supplied by a management station wishing to delete all of the instances associated with an existing conceptual row. Whereas five of the six values (all except `notReady') may be specified in a management protocol set operation, only three values will be returned in response to a management protocol retrieval operation: `notReady', `notInService' or `active'. That is, when queried, an existing conceptual row has only three states: it is either available for use by the managed device (the status column has value `active'); it is not available for use by the managed device, though the agent has sufficient information to attempt to make it so (the status column has value `notInService'); or, it is not available for use by the managed device, and an attempt to make it so would fail because the agent has insufficient information (the state column has value `notReady'). NOTE WELL This textual convention may be used for a MIB table, irrespective of whether the values of that table's conceptual rows are able to be modified while it is active, or whether its conceptual rows must be taken out of service in order to be modified. That is, it is the responsibility of the DESCRIPTION clause of the status column to specify whether the status column must not be `active' in order for the value of some other column of the same conceptual row to be modified. If such a specification is made, affected columns may be changed by an SNMP set PDU if the RowStatus would not be equal to `active' either immediately before or after processing the PDU. In other words, if the PDU also contained a varbind that would change the RowStatus value, the column in question may be changed if the RowStatus was not equal to `active' as the PDU was received, or if the varbind sets the status to a value other than 'active'. Also note that whenever any elements of a row exist, the RowStatus column must also exist. To summarize the effect of having a conceptual row with a status column having a SYNTAX clause value of RowStatus, consider the following state diagram: STATE +--------------+-----------+-------------+------------- | A | B | C | D | |status col.|status column| |status column | is | is |status column ACTION |does not exist| notReady | notInService| is active --------------+--------------+-----------+-------------+------------- set status |noError ->D|inconsist- |inconsistent-|inconsistent- column to | or | entValue| Value| Value createAndGo |inconsistent- | | | | Value| | | --------------+--------------+-----------+-------------+------------- set status |noError see 1|inconsist- |inconsistent-|inconsistent- column to | or | entValue| Value| Value createAndWait |wrongValue | | | --------------+--------------+-----------+-------------+------------- set status |inconsistent- |inconsist- |noError |noError column to | Value| entValue| | active | | | | | | or | | | | | | | |see 2 ->D|see 8 ->D| ->D --------------+--------------+-----------+-------------+------------- set status |inconsistent- |inconsist- |noError |noError ->C column to | Value| entValue| | notInService | | | | | | or | | or | | | | | |see 3 ->C| ->C|see 6 --------------+--------------+-----------+-------------+------------- set status |noError |noError |noError |noError ->A column to | | | | or destroy | ->A| ->A| ->A|see 7 --------------+--------------+-----------+-------------+------------- set any other |see 4 |noError |noError |see 5 column to some| | | | value | | see 1| ->C| ->D --------------+--------------+-----------+-------------+------------- (1) goto B or C, depending on information available to the agent. (2) if other variable bindings included in the same PDU, provide values for all columns which are missing but required, and all columns have acceptable values, then return noError and goto D. (3) if other variable bindings included in the same PDU, provide legal values for all columns which are missing but required, then return noError and goto C. (4) at the discretion of the agent, the return value may be either: inconsistentName: because the agent does not choose to create such an instance when the corresponding RowStatus instance does not exist, or inconsistentValue: if the supplied value is inconsistent with the state of some other MIB object's value, or noError: because the agent chooses to create the instance. If noError is returned, then the instance of the status column must also be created, and the new state is B or C, depending on the information available to the agent. If inconsistentName or inconsistentValue is returned, the row remains in state A. (5) depending on the MIB definition for the column/table, either noError or inconsistentValue may be returned. (6) the return value can indicate one of the following errors: wrongValue: because the agent does not support notInService (e.g., an agent which does not support createAndWait), or inconsistentValue: because the agent is unable to take the row out of service at this time, perhaps because it is in use and cannot be de-activated. (7) the return value can indicate the following error: inconsistentValue: because the agent is unable to remove the row at this time, perhaps because it is in use and cannot be de-activated. (8) the transition to D can fail, e.g., if the values of the conceptual row are inconsistent, then the error code would be inconsistentValue. NOTE: Other processing of (this and other varbinds of) the set request may result in a response other than noError being returned, e.g., wrongValue, noCreation, etc. Conceptual Row Creation There are four potential interactions when creating a conceptual row: selecting an instance-identifier which is not in use; creating the conceptual row; initializing any objects for which the agent does not supply a default; and, making the conceptual row available for use by the managed device. Interaction 1: Selecting an Instance-Identifier The algorithm used to select an instance-identifier varies for each conceptual row. In some cases, the instance- identifier is semantically significant, e.g., the destination address of a route, and a management station selects the instance-identifier according to the semantics. In other cases, the instance-identifier is used solely to distinguish conceptual rows, and a management station without specific knowledge of the conceptual row might examine the instances present in order to determine an unused instance-identifier. (This approach may be used, but it is often highly sub-optimal; however, it is also a questionable practice for a naive management station to attempt conceptual row creation.) Alternately, the MIB module which defines the conceptual row might provide one or more objects which provide assistance in determining an unused instance-identifier. For example, if the conceptual row is indexed by an integer-value, then an object having an integer-valued SYNTAX clause might be defined for such a purpose, allowing a management station to issue a management protocol retrieval operation. In order to avoid unnecessary collisions between competing management stations, `adjacent' retrievals of this object should be different. Finally, the management station could select a pseudo-random number to use as the index. In the event that this index was already in use and an inconsistentValue was returned in response to the management protocol set operation, the management station should simply select a new pseudo-random number and retry the operation. A MIB designer should choose between the two latter algorithms based on the size of the table (and therefore the efficiency of each algorithm). For tables in which a large number of entries are expected, it is recommended that a MIB object be defined that returns an acceptable index for creation. For tables with small numbers of entries, it is recommended that the latter pseudo-random index mechanism be used. Interaction 2: Creating the Conceptual Row Once an unused instance-identifier has been selected, the management station determines if it wishes to create and activate the conceptual row in one transaction or in a negotiated set of interactions. Interaction 2a: Creating and Activating the Conceptual Row The management station must first determine the column requirements, i.e., it must determine those columns for which it must or must not provide values. Depending on the complexity of the table and the management station's knowledge of the agent's capabilities, this determination can be made locally by the management station. Alternately, the management station issues a management protocol get operation to examine all columns in the conceptual row that it wishes to create. In response, for each column, there are three possible outcomes: - a value is returned, indicating that some other management station has already created this conceptual row. We return to interaction 1. - the exception `noSuchInstance' is returned, indicating that the agent implements the object-type associated with this column, and that this column in at least one conceptual row would be accessible in the MIB view used by the retrieval were it to exist. For those columns to which the agent provides read-create access, the `noSuchInstance' exception tells the management station that it should supply a value for this column when the conceptual row is to be created. - the exception `noSuchObject' is returned, indicating that the agent does not implement the object-type associated with this column or that there is no conceptual row for which this column would be accessible in the MIB view used by the retrieval. As such, the management station can not issue any management protocol set operations to create an instance of this column. Once the column requirements have been determined, a management protocol set operation is accordingly issued. This operation also sets the new instance of the status column to `createAndGo'. When the agent processes the set operation, it verifies that it has sufficient information to make the conceptual row available for use by the managed device. The information available to the agent is provided by two sources: the management protocol set operation which creates the conceptual row, and, implementation-specific defaults supplied by the agent (note that an agent must provide implementation-specific defaults for at least those objects which it implements as read-only). If there is sufficient information available, then the conceptual row is created, a `noError' response is returned, the status column is set to `active', and no further interactions are necessary (i.e., interactions 3 and 4 are skipped). If there is insufficient information, then the conceptual row is not created, and the set operation fails with an error of `inconsistentValue'. On this error, the management station can issue a management protocol retrieval operation to determine if this was because it failed to specify a value for a required column, or, because the selected instance of the status column already existed. In the latter case, we return to interaction 1. In the former case, the management station can re-issue the set operation with the additional information, or begin interaction 2 again using `createAndWait' in order to negotiate creation of the conceptual row. NOTE WELL Regardless of the method used to determine the column requirements, it is possible that the management station might deem a column necessary when, in fact, the agent will not allow that particular columnar instance to be created or written. In this case, the management protocol set operation will fail with an error such as `noCreation' or `notWritable'. In this case, the management station decides whether it needs to be able to set a value for that particular columnar instance. If not, the management station re-issues the management protocol set operation, but without setting a value for that particular columnar instance; otherwise, the management station aborts the row creation algorithm. Interaction 2b: Negotiating the Creation of the Conceptual Row The management station issues a management protocol set operation which sets the desired instance of the status column to `createAndWait'. If the agent is unwilling to process a request of this sort, the set operation fails with an error of `wrongValue'. (As a consequence, such an agent must be prepared to accept a single management protocol set operation, i.e., interaction 2a above, containing all of the columns indicated by its column requirements.) Otherwise, the conceptual row is created, a `noError' response is returned, and the status column is immediately set to either `notInService' or `notReady', depending on whether it has sufficient information to (attempt to) make the conceptual row available for use by the managed device. If there is sufficient information available, then the status column is set to `notInService'; otherwise, if there is insufficient information, then the status column is set to `notReady'. Regardless, we proceed to interaction 3. Interaction 3: Initializing non-defaulted Objects The management station must now determine the column requirements. It issues a management protocol get operation to examine all columns in the created conceptual row. In the response, for each column, there are three possible outcomes: - a value is returned, indicating that the agent implements the object-type associated with this column and had sufficient information to provide a value. For those columns to which the agent provides read-create access (and for which the agent allows their values to be changed after their creation), a value return tells the management station that it may issue additional management protocol set operations, if it desires, in order to change the value associated with this column. - the exception `noSuchInstance' is returned, indicating that the agent implements the object-type associated with this column, and that this column in at least one conceptual row would be accessible in the MIB view used by the retrieval were it to exist. However, the agent does not have sufficient information to provide a value, and until a value is provided, the conceptual row may not be made available for use by the managed device. For those columns to which the agent provides read-create access, the `noSuchInstance' exception tells the management station that it must issue additional management protocol set operations, in order to provide a value associated with this column. - the exception `noSuchObject' is returned, indicating that the agent does not implement the object-type associated with this column or that there is no conceptual row for which this column would be accessible in the MIB view used by the retrieval. As such, the management station can not issue any management protocol set operations to create an instance of this column. If the value associated with the status column is `notReady', then the management station must first deal with all `noSuchInstance' columns, if any. Having done so, the value of the status column becomes `notInService', and we proceed to interaction 4. Interaction 4: Making the Conceptual Row Available Once the management station is satisfied with the values associated with the columns of the conceptual row, it issues a management protocol set operation to set the status column to `active'. If the agent has sufficient information to make the conceptual row available for use by the managed device, the management protocol set operation succeeds (a `noError' response is returned). Otherwise, the management protocol set operation fails with an error of `inconsistentValue'. NOTE WELL A conceptual row having a status column with value `notInService' or `notReady' is unavailable to the managed device. As such, it is possible for the managed device to create its own instances during the time between the management protocol set operation which sets the status column to `createAndWait' and the management protocol set operation which sets the status column to `active'. In this case, when the management protocol set operation is issued to set the status column to `active', the values held in the agent supersede those used by the managed device. If the management station is prevented from setting the status column to `active' (e.g., due to management station or network failure) the conceptual row will be left in the `notInService' or `notReady' state, consuming resources indefinitely. The agent must detect conceptual rows that have been in either state for an abnormally long period of time and remove them. It is the responsibility of the DESCRIPTION clause of the status column to indicate what an abnormally long period of time would be. This period of time should be long enough to allow for human response time (including `think time') between the creation of the conceptual row and the setting of the status to `active'. In the absence of such information in the DESCRIPTION clause, it is suggested that this period be approximately 5 minutes in length. This removal action applies not only to newly-created rows, but also to previously active rows which are set to, and left in, the notInService state for a prolonged period exceeding that which is considered normal for such a conceptual row. Conceptual Row Suspension When a conceptual row is `active', the management station may issue a management protocol set operation which sets the instance of the status column to `notInService'. If the agent is unwilling to do so, the set operation fails with an error of `wrongValue' or `inconsistentValue'. Otherwise, the conceptual row is taken out of service, and a `noError' response is returned. It is the responsibility of the DESCRIPTION clause of the status column to indicate under what circumstances the status column should be taken out of service (e.g., in order for the value of some other column of the same conceptual row to be modified). Conceptual Row Deletion For deletion of conceptual rows, a management protocol set operation is issued which sets the instance of the status column to `destroy'. This request may be made regardless of the current value of the status column (e.g., it is possible to delete conceptual rows which are either `notReady', `notInService' or `active'.) If the operation succeeds, then all instances associated with the conceptual row are immediately removed. · Integer32

This object is used to create or delete conceptual row in this table. To create a row, set this object to 'createAndGo'. There are no mandatory objects in a create request. To delete a row, set this object to 'destroy'.

SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form. To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279]. Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited. The use of control codes should be avoided. When it is necessary to represent a newline, the control code sequence CR LF should be used. The use of leading or trailing white space should be avoided. For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided. For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding. UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding. Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416]. Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (0..100) · OCTET STRING · hint 255t

Reference: GSM 03.03: Digital cellular telecommunication system (Phase 2+); General Packet Radio Service (GPRS); Service description; Stage 1.

The Access Point Name. It is composed of two parts: - The APN Network Identifier is mandatory and is a fully qualified domain name according to the DNS naming conventions, e.g., 'company.com.'. - The APN Operator Identifier is optional. It is a fully qualified domain name according to the DNS naming convention, and consists of three labels, the last of which must be '.gprs'. For example, 'mncyyyy.mcczzzz.gprs'. An example of a full APN name with both the Network and operator identifiers is 'company.com.mncyyyy.mcczzzz.gprs'.

INTEGER1 = transparent2 = nontransparent · Integer32

Specifies the type of access allowed to the PDN through this access point. - 'transparent', indicates that users can access without authentication. - 'nontransparent', indicates that users must be authenticated by the Gateway.

INTEGER1 = global2 = dhcp3 = radius4 = disable5 = local · Integer32

Specifies a dynamic address allocation method for this access point. - 'global', which indicates that no method is defined specifically to this access point and the DHCP or radius server configured for this Gateway 'globally' will be used to allocation a dynamic IP address to the user. - 'dhcp', which indicates that the DHCP server will be used. - 'radius', which indicates that the radius server will be used. - 'disable', which indicates that dynamic address allocation is disabled. - 'local', indicates that local address pool configured on the Gateway is going to be used. cgprsAccPtIpAddrLocalPoolName denotes the name of the corresponding address pool.

IpAddress SIZE (4)

This object specifies the IP address of the primary DHCP server from which a mobile subscriber can request an IP address assignment for the access of this APN. In case this DHCP server is not available, the secondary DHCP server is used.

IpAddress SIZE (4)

The IP address of the secondary DHCP server. The secondary DHCP server is used if the primary DHCP server is not available. This object can be set after configuring primary DHCP server.

IpAddress SIZE (4)

This object specifies the DHCP Gateway address that is used in the 'giaddr' field of the DHCP request. It is used by DHCP to determine from which pool the IP address will be allocated. If no DHCP Gateway is specified, the IP address associated with the Gn interface is used.

IpAddress SIZE (4)

This object specifies the IP address of the primary RADIUS server used by this access point to authenticate and/or authorize mobile users to access the PDN. In case this RADIUS server is not available, the secondary will be used. Obsoleted by cgprsAccPtAaaAuthServerGroup and cgprsAccPtAaaAccountServerGroup.

IpAddress SIZE (4)

Specifies a secondary RADIUS server. The secondary RADIUS server will be used if the primary RADIUS server is not available. Obsoleted by cgprsAccPtAaaAuthServerGroup and cgprsAccPtAaaAccountServerGroup.

AccessControlListIdAccess Control List (ACL) specifies criteria by which packets are evaluated as matching or non-matching. The ACL also specifies an action which is applied to packets which match. Objects which use this textual convention identify ACLs. ACLs are configured/defined outside the scope of this MIB. The value of an object with this syntax associates to an ACL with the same ACL number. (1..2699) · Integer32

This object specifies the ACL against which to compare packets received at this Access Point from the PDN for forwarding towards an MS. Access list at the access point level is used to control which packets are allowed access between the APN and the MS. Access violations by a packet according to the rules in this ACL could cause this packet to be dropped or its PDP or Bearer session terminated. Which of these treatments is taken is specified by the object cgprsAccPtAccessViolation. This object is ignored if cgprsAccPtIPAccListInEnable is set to 'false'.

AccessControlListIdAccess Control List (ACL) specifies criteria by which packets are evaluated as matching or non-matching. The ACL also specifies an action which is applied to packets which match. Objects which use this textual convention identify ACLs. ACLs are configured/defined outside the scope of this MIB. The value of an object with this syntax associates to an ACL with the same ACL number. (1..2699) · Integer32

This object specifies the ACL against which to compare packets originated by an MS and received by at this Access Point for forwarding to the PDN. Access list at the access point level is used to control which packets are allowed access between the APN and the MS. Access violations by a packet according to the rules in this ACL could cause this packet to be dropped or its PDP or Bearer session terminated. Which of these treatments is taken is specified by the object cgprsAccPtAccessViolation. This object is ignored if cgprsAccPtIPAccListOutEnable is set to 'false'.

InterfaceIndexOrZeroEither the value 0, or the ifIndex value of an interface in the ifTable. (0..2147483647) · Integer32

Specifies an interface to be used by GGSN on Gi interface. The value zero indicates that no interface is specified. The cgprsAccPtIfNextHop must be specified if this object is set to the Gi associated interface.

IpAddress SIZE (4)

Specifies the IP address of the next hop for the Gi interface, specified by cgprsAccPtIfIndex. This value is mandatory if the value of cgprsAccPtIfIndex is non-zero. Setting the cgprsAccPtIfIndex object to zero will reset this object to the value of '00000000'H, which means it is not used.

INTEGER1 = discardPacket2 = terminateSession · Integer32

Specifies how access violation should be treated. An access violation occurs if the IP packets violates any rules in ACL as specified by either cgprsAccPtIPAccListGroupIn or cgprsAccPtIPAccListGroupOut. - 'discardPacket', packets are discarded. - 'terminateSession', the user's session is terminated.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

This object indicates if a user needs to subscribe to this access point before accessing it.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

This object indicates whether network (PDN) initiated PDP or Bearer sessions are allowed for this access point. The more common case, is false, which indicates that the PDP or Bearer is initiated by the MS.

Gauge32

Indicates the number of IP addresses allocated to MS's. Trigger Condition: This gauge is incremented/decremented by successful completion of create/delete dynamic PDP or Bearer context request message respectively.

Gauge32

The number of mobile subscribers currently accessing this APN. Obsoleted by cgprsAccPtActivePdps.

Unsigned32 (0..168) · hours

This object indicates maximum idle connection time allowed to the PDP or Bearer context before termination of the GTP session. A value of 0 means session idle timer is not used.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

This object indicates whether access to a roaming MS needs to be blocked for this APN.

SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form. To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279]. Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited. The use of control codes should be avoided. When it is necessary to represent a newline, the control code sequence CR LF should be used. The use of leading or trailing white space should be avoided. For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided. For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding. UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding. Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416]. Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (0..255) · OCTET STRING · hint 255t

Reference: GSM 03.03: Digital cellular telecommunication system (Phase 2+); General Packet Radio Service (GPRS); Service description; Stage 1.

This object specifies the anonymous user name, which is used when a MS tries to access a non-transparent APN without supplying user name and password.

SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form. To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279]. Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited. The use of control codes should be avoided. When it is necessary to represent a newline, the control code sequence CR LF should be used. The use of leading or trailing white space should be avoided. For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided. For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding. UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding. Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416]. Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (0..255) · OCTET STRING · hint 255t

Reference: GSM 03.03: Digital cellular telecommunication system (Phase 2+); General Packet Radio Service (GPRS); Service description; Stage 1.

This object specifies the password corresponding to cgprsAccPtAnonymousUserName. For security reasons, retrieving this object returns a zero-length string.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

Reference: GSM 09.02: Digital cellular telecommunication system (Phase 2+); Mobile Application Part (MAP) specification.

This object specifies whether the ISDN ID used by the MS, when authenticating with a radius server, needs to be suppressed or not. When set to 'true', the ISDN ID attribute will not be sent by the Gateway. When set to 'false', the ISDN ID attribute will be sent by the Gateway. To set this object to 'true', AAA radius group for authentication should have been configured on the Gateway(either at global or APN level).

DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..20) · OCTET STRING · hint 255a

Reference: GSM 09.02: Digital cellular telecommunication system (Phase 2+); Mobile Application Part (MAP) specification.

This object specifies the value that will be transmitted to the radius server in place of mobile stations ISDN ID. This object can only be set if cgprsAccPtMsIsdnSuppressed is 'true'. Valid characters for this object are 0..9, a, b, c, * and #. If no value is set, no MS-ISDN ID will be sent to the radius server.

SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form. To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279]. Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited. The use of control codes should be avoided. When it is necessary to represent a newline, the control code sequence CR LF should be used. The use of leading or trailing white space should be avoided. For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided. For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding. UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding. Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416]. Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (0..255) · OCTET STRING · hint 255t

This object specifies the AAA radius server group that is used for authentication by this APN.

SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form. To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279]. Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited. The use of control codes should be avoided. When it is necessary to represent a newline, the control code sequence CR LF should be used. The use of leading or trailing white space should be avoided. For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided. For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding. UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding. Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416]. Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (0..255) · OCTET STRING · hint 255t

This object specifies the AAA radius server group that is used for accounting by this APN. If no group is specified for accounting, cgprsAccPtAaaAuthServerGroup will be used.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

This object is used to enable accounting when the APN is in 'transparent' mode. When the object is set to 'true', cgprsAccPtAaaAccountServerGroup is used for accounting. If cgprsAccPtAaaAccountServerGroup is not specified, cgprsAccPtAaaAuthServerGroup will be used. When the APN is in 'non-transparent' mode, the accounting will always be enabled i.e., this object will be 'true' by default.

INTEGER1 = real2 = virtual3 = virtualPreAuth · Integer32

This object specifies the type of APN. 'virtual' - Specifies an APN type that is not associated with any specific physical target network on the Gateway. When this object is set to 'virtual', all other APN parameters are ignored. 'real' - Specifies an APN type that corresponds to a physical interface to an external network on the Gateway. 'virtualPreAuth' - Specifies an APN type that is not associated with any specific physical target network on the Gateway. It applies a pre-authentication phase for any create PDP or Bearer request that includes a virtual APN. During pre-authentication, an Access-Request message is sent to an AAA server and the AAA server then returns a target APN encoded in a Radius attribute in the Access-Accept message.

SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form. To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279]. Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited. The use of control codes should be avoided. When it is necessary to represent a newline, the control code sequence CR LF should be used. The use of leading or trailing white space should be avoided. For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided. For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding. UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding. Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416]. Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (0..255) · OCTET STRING · hint 255t

This object specifies the name of the VRF with which this APN is associated.

INTEGER1 = global2 = vrf · Integer32

This object specifies the address space used by the dhcp server. This object can only be set if cgprsAccPtDHCPServerPri is set.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

This object is used to enable Gateway to regenerate a PPP session for each IP PDP or Bearer context on this APN.

Integer32 (1..65535)

This object specifies the maximum number of regenerated PPP sessions allowed for this access-point. This object can only be set if cgprsAccPtPppRegenEnable is set to 'true'. The maximum value that can be held by this object depends on the Gateway's platform.

Integer32 (1..65535) · seconds

This object specifies the maximum tolerance time within which a regenerated PPP session has to fully come up. This object can only be set if cgprsAccPtPppRegenEnable is set to 'true'.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

This object is used to enable auto aggregation on this APN. When a user tries to configure entries in cgprsAccPtAggregTable, this object will automatically be set to 'false'. When this object is set to 'true', the entries in cgprsAccPtAggregTable, if any, will be deleted.

SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form. To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279]. Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited. The use of control codes should be avoided. When it is necessary to represent a newline, the control code sequence CR LF should be used. The use of leading or trailing white space should be avoided. For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided. For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding. UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding. Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416]. Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (0..100) · OCTET STRING · hint 255t

This object represents the Proxy-CSCF server group that will be used by this APN. The Proxy-CSCF server group contains a list of Proxy-CSCF addresses which will be provided to the MS(UE) in response to a PDP or Bearer contexts for which the P-CSCF address request field is set in PCO.

InetAddressType0 = unknown1 = ipv42 = ipv63 = ipv4z4 = ipv6z16 = dnsA value that represents a type of Internet address. unknown(0) An unknown address type. This value MUST be used if the value of the corresponding InetAddress object is a zero-length string. It may also be used to indicate an IP address that is not in one of the formats defined below. ipv4(1) An IPv4 address as defined by the InetAddressIPv4 textual convention. ipv6(2) An IPv6 address as defined by the InetAddressIPv6 textual convention. ipv4z(3) A non-global IPv4 address including a zone index as defined by the InetAddressIPv4z textual convention. ipv6z(4) A non-global IPv6 address including a zone index as defined by the InetAddressIPv6z textual convention. dns(16) A DNS domain name as defined by the InetAddressDNS textual convention. Each definition of a concrete InetAddressType value must be accompanied by a definition of a textual convention for use with that InetAddressType. To support future extensions, the InetAddressType textual convention SHOULD NOT be sub-typed in object type definitions. It MAY be sub-typed in compliance statements in order to require only a subset of these address types for a compliant implementation. Implementations must ensure that InetAddressType objects and any dependent objects (e.g., InetAddress objects) are consistent. An inconsistentValue error must be generated if an attempt to change an InetAddressType object would, for example, lead to an undefined InetAddress value. In particular, InetAddressType/InetAddress pairs must be changed together if the address type changes (e.g., from ipv6(2) to ipv4(1)). · Integer32

This object specifies the type of Internet address denoted by cgprsAccPtAggregIpAddr.

InetAddressDenotes a generic Internet address. An InetAddress value is always interpreted within the context of an InetAddressType value. Every usage of the InetAddress textual convention is required to specify the InetAddressType object that provides the context. It is suggested that the InetAddressType object be logically registered before the object(s) that use the InetAddress textual convention, if they appear in the same logical row. The value of an InetAddress object must always be consistent with the value of the associated InetAddressType object. Attempts to set an InetAddress object to a value inconsistent with the associated InetAddressType must fail with an inconsistentValue error. When this textual convention is used as the syntax of an index object, there may be issues with the limit of 128 sub-identifiers specified in SMIv2, STD 58. In this case, the object definition MUST include a 'SIZE' clause to limit the number of potential instance sub-identifiers; otherwise the applicable constraints MUST be stated in the appropriate conceptual row DESCRIPTION clauses, or in the surrounding documentation if there is no single DESCRIPTION clause that is appropriate. SIZE (0..255) · OCTET STRING

This object specifies the IP address whose network prefix is going to be defined by cgprsAccPtAggregIpMask. When this object is set, cgprsAccPtAggregIpMask must be specified.

CiscoInetAddressMaskDenotes a generic Internet subnet address mask. The Internet subnet address mask is represented as the number of contiguous 1-bit from MSB (most significant bit) of the Internet subnet address mask. A CiscoInetAddressMask value is always interpreted within the context of an InetAddressType value. The InetAddressType only object or InetAddressType with InetAddress objects which define the context must be registered immediately before the object which uses the CiscoInetAddressMask textual convention. In other words, the object identifiers for the InetAddressType object and the CiscoInetAddressMask object MUST have the same length and the last sub-identifier of the InetAddressType object MUST be 1 less than the last sub-identifier of the CiscoInetAddressMask object and MUST be 2 less than the last sub-identifier of the CiscoInetAddressMask object if an InetAddress object is defined between InetAddressType and CiscoInetAddressMask objects. The maximum value of the CiscoInetAddressMask TC is 32 for the value 'ipv4(1)' in InetAddressType object and 128 for the value 'ipv6(2)' in InetAddressType object. The value zero is object-specific and must therefore be defined as part of the description of any object which uses this syntax. Examples of the usage of zero might include situations where Internet subnet mask was unknown, or when none subnet masks need to be referenced.Reference: RFC2851, Textual Conventions for Internet Network Addresses. (0..128) · Unsigned32

This object specifies the net-mask pertaining to cgprsAccPtAggregIpAddr.

RowStatus1 = active2 = notInService3 = notReady4 = createAndGo5 = createAndWait6 = destroyThe RowStatus textual convention is used to manage the creation and deletion of conceptual rows, and is used as the value of the SYNTAX clause for the status column of a conceptual row (as described in Section 7.7.1 of [2].) The status column has six defined values: - `active', which indicates that the conceptual row is available for use by the managed device; - `notInService', which indicates that the conceptual row exists in the agent, but is unavailable for use by the managed device (see NOTE below); 'notInService' has no implication regarding the internal consistency of the row, availability of resources, or consistency with the current state of the managed device; - `notReady', which indicates that the conceptual row exists in the agent, but is missing information necessary in order to be available for use by the managed device (i.e., one or more required columns in the conceptual row have not been instanciated); - `createAndGo', which is supplied by a management station wishing to create a new instance of a conceptual row and to have its status automatically set to active, making it available for use by the managed device; - `createAndWait', which is supplied by a management station wishing to create a new instance of a conceptual row (but not make it available for use by the managed device); and, - `destroy', which is supplied by a management station wishing to delete all of the instances associated with an existing conceptual row. Whereas five of the six values (all except `notReady') may be specified in a management protocol set operation, only three values will be returned in response to a management protocol retrieval operation: `notReady', `notInService' or `active'. That is, when queried, an existing conceptual row has only three states: it is either available for use by the managed device (the status column has value `active'); it is not available for use by the managed device, though the agent has sufficient information to attempt to make it so (the status column has value `notInService'); or, it is not available for use by the managed device, and an attempt to make it so would fail because the agent has insufficient information (the state column has value `notReady'). NOTE WELL This textual convention may be used for a MIB table, irrespective of whether the values of that table's conceptual rows are able to be modified while it is active, or whether its conceptual rows must be taken out of service in order to be modified. That is, it is the responsibility of the DESCRIPTION clause of the status column to specify whether the status column must not be `active' in order for the value of some other column of the same conceptual row to be modified. If such a specification is made, affected columns may be changed by an SNMP set PDU if the RowStatus would not be equal to `active' either immediately before or after processing the PDU. In other words, if the PDU also contained a varbind that would change the RowStatus value, the column in question may be changed if the RowStatus was not equal to `active' as the PDU was received, or if the varbind sets the status to a value other than 'active'. Also note that whenever any elements of a row exist, the RowStatus column must also exist. To summarize the effect of having a conceptual row with a status column having a SYNTAX clause value of RowStatus, consider the following state diagram: STATE +--------------+-----------+-------------+------------- | A | B | C | D | |status col.|status column| |status column | is | is |status column ACTION |does not exist| notReady | notInService| is active --------------+--------------+-----------+-------------+------------- set status |noError ->D|inconsist- |inconsistent-|inconsistent- column to | or | entValue| Value| Value createAndGo |inconsistent- | | | | Value| | | --------------+--------------+-----------+-------------+------------- set status |noError see 1|inconsist- |inconsistent-|inconsistent- column to | or | entValue| Value| Value createAndWait |wrongValue | | | --------------+--------------+-----------+-------------+------------- set status |inconsistent- |inconsist- |noError |noError column to | Value| entValue| | active | | | | | | or | | | | | | | |see 2 ->D|see 8 ->D| ->D --------------+--------------+-----------+-------------+------------- set status |inconsistent- |inconsist- |noError |noError ->C column to | Value| entValue| | notInService | | | | | | or | | or | | | | | |see 3 ->C| ->C|see 6 --------------+--------------+-----------+-------------+------------- set status |noError |noError |noError |noError ->A column to | | | | or destroy | ->A| ->A| ->A|see 7 --------------+--------------+-----------+-------------+------------- set any other |see 4 |noError |noError |see 5 column to some| | | | value | | see 1| ->C| ->D --------------+--------------+-----------+-------------+------------- (1) goto B or C, depending on information available to the agent. (2) if other variable bindings included in the same PDU, provide values for all columns which are missing but required, and all columns have acceptable values, then return noError and goto D. (3) if other variable bindings included in the same PDU, provide legal values for all columns which are missing but required, then return noError and goto C. (4) at the discretion of the agent, the return value may be either: inconsistentName: because the agent does not choose to create such an instance when the corresponding RowStatus instance does not exist, or inconsistentValue: if the supplied value is inconsistent with the state of some other MIB object's value, or noError: because the agent chooses to create the instance. If noError is returned, then the instance of the status column must also be created, and the new state is B or C, depending on the information available to the agent. If inconsistentName or inconsistentValue is returned, the row remains in state A. (5) depending on the MIB definition for the column/table, either noError or inconsistentValue may be returned. (6) the return value can indicate one of the following errors: wrongValue: because the agent does not support notInService (e.g., an agent which does not support createAndWait), or inconsistentValue: because the agent is unable to take the row out of service at this time, perhaps because it is in use and cannot be de-activated. (7) the return value can indicate the following error: inconsistentValue: because the agent is unable to remove the row at this time, perhaps because it is in use and cannot be de-activated. (8) the transition to D can fail, e.g., if the values of the conceptual row are inconsistent, then the error code would be inconsistentValue. NOTE: Other processing of (this and other varbinds of) the set request may result in a response other than noError being returned, e.g., wrongValue, noCreation, etc. Conceptual Row Creation There are four potential interactions when creating a conceptual row: selecting an instance-identifier which is not in use; creating the conceptual row; initializing any objects for which the agent does not supply a default; and, making the conceptual row available for use by the managed device. Interaction 1: Selecting an Instance-Identifier The algorithm used to select an instance-identifier varies for each conceptual row. In some cases, the instance- identifier is semantically significant, e.g., the destination address of a route, and a management station selects the instance-identifier according to the semantics. In other cases, the instance-identifier is used solely to distinguish conceptual rows, and a management station without specific knowledge of the conceptual row might examine the instances present in order to determine an unused instance-identifier. (This approach may be used, but it is often highly sub-optimal; however, it is also a questionable practice for a naive management station to attempt conceptual row creation.) Alternately, the MIB module which defines the conceptual row might provide one or more objects which provide assistance in determining an unused instance-identifier. For example, if the conceptual row is indexed by an integer-value, then an object having an integer-valued SYNTAX clause might be defined for such a purpose, allowing a management station to issue a management protocol retrieval operation. In order to avoid unnecessary collisions between competing management stations, `adjacent' retrievals of this object should be different. Finally, the management station could select a pseudo-random number to use as the index. In the event that this index was already in use and an inconsistentValue was returned in response to the management protocol set operation, the management station should simply select a new pseudo-random number and retry the operation. A MIB designer should choose between the two latter algorithms based on the size of the table (and therefore the efficiency of each algorithm). For tables in which a large number of entries are expected, it is recommended that a MIB object be defined that returns an acceptable index for creation. For tables with small numbers of entries, it is recommended that the latter pseudo-random index mechanism be used. Interaction 2: Creating the Conceptual Row Once an unused instance-identifier has been selected, the management station determines if it wishes to create and activate the conceptual row in one transaction or in a negotiated set of interactions. Interaction 2a: Creating and Activating the Conceptual Row The management station must first determine the column requirements, i.e., it must determine those columns for which it must or must not provide values. Depending on the complexity of the table and the management station's knowledge of the agent's capabilities, this determination can be made locally by the management station. Alternately, the management station issues a management protocol get operation to examine all columns in the conceptual row that it wishes to create. In response, for each column, there are three possible outcomes: - a value is returned, indicating that some other management station has already created this conceptual row. We return to interaction 1. - the exception `noSuchInstance' is returned, indicating that the agent implements the object-type associated with this column, and that this column in at least one conceptual row would be accessible in the MIB view used by the retrieval were it to exist. For those columns to which the agent provides read-create access, the `noSuchInstance' exception tells the management station that it should supply a value for this column when the conceptual row is to be created. - the exception `noSuchObject' is returned, indicating that the agent does not implement the object-type associated with this column or that there is no conceptual row for which this column would be accessible in the MIB view used by the retrieval. As such, the management station can not issue any management protocol set operations to create an instance of this column. Once the column requirements have been determined, a management protocol set operation is accordingly issued. This operation also sets the new instance of the status column to `createAndGo'. When the agent processes the set operation, it verifies that it has sufficient information to make the conceptual row available for use by the managed device. The information available to the agent is provided by two sources: the management protocol set operation which creates the conceptual row, and, implementation-specific defaults supplied by the agent (note that an agent must provide implementation-specific defaults for at least those objects which it implements as read-only). If there is sufficient information available, then the conceptual row is created, a `noError' response is returned, the status column is set to `active', and no further interactions are necessary (i.e., interactions 3 and 4 are skipped). If there is insufficient information, then the conceptual row is not created, and the set operation fails with an error of `inconsistentValue'. On this error, the management station can issue a management protocol retrieval operation to determine if this was because it failed to specify a value for a required column, or, because the selected instance of the status column already existed. In the latter case, we return to interaction 1. In the former case, the management station can re-issue the set operation with the additional information, or begin interaction 2 again using `createAndWait' in order to negotiate creation of the conceptual row. NOTE WELL Regardless of the method used to determine the column requirements, it is possible that the management station might deem a column necessary when, in fact, the agent will not allow that particular columnar instance to be created or written. In this case, the management protocol set operation will fail with an error such as `noCreation' or `notWritable'. In this case, the management station decides whether it needs to be able to set a value for that particular columnar instance. If not, the management station re-issues the management protocol set operation, but without setting a value for that particular columnar instance; otherwise, the management station aborts the row creation algorithm. Interaction 2b: Negotiating the Creation of the Conceptual Row The management station issues a management protocol set operation which sets the desired instance of the status column to `createAndWait'. If the agent is unwilling to process a request of this sort, the set operation fails with an error of `wrongValue'. (As a consequence, such an agent must be prepared to accept a single management protocol set operation, i.e., interaction 2a above, containing all of the columns indicated by its column requirements.) Otherwise, the conceptual row is created, a `noError' response is returned, and the status column is immediately set to either `notInService' or `notReady', depending on whether it has sufficient information to (attempt to) make the conceptual row available for use by the managed device. If there is sufficient information available, then the status column is set to `notInService'; otherwise, if there is insufficient information, then the status column is set to `notReady'. Regardless, we proceed to interaction 3. Interaction 3: Initializing non-defaulted Objects The management station must now determine the column requirements. It issues a management protocol get operation to examine all columns in the created conceptual row. In the response, for each column, there are three possible outcomes: - a value is returned, indicating that the agent implements the object-type associated with this column and had sufficient information to provide a value. For those columns to which the agent provides read-create access (and for which the agent allows their values to be changed after their creation), a value return tells the management station that it may issue additional management protocol set operations, if it desires, in order to change the value associated with this column. - the exception `noSuchInstance' is returned, indicating that the agent implements the object-type associated with this column, and that this column in at least one conceptual row would be accessible in the MIB view used by the retrieval were it to exist. However, the agent does not have sufficient information to provide a value, and until a value is provided, the conceptual row may not be made available for use by the managed device. For those columns to which the agent provides read-create access, the `noSuchInstance' exception tells the management station that it must issue additional management protocol set operations, in order to provide a value associated with this column. - the exception `noSuchObject' is returned, indicating that the agent does not implement the object-type associated with this column or that there is no conceptual row for which this column would be accessible in the MIB view used by the retrieval. As such, the management station can not issue any management protocol set operations to create an instance of this column. If the value associated with the status column is `notReady', then the management station must first deal with all `noSuchInstance' columns, if any. Having done so, the value of the status column becomes `notInService', and we proceed to interaction 4. Interaction 4: Making the Conceptual Row Available Once the management station is satisfied with the values associated with the columns of the conceptual row, it issues a management protocol set operation to set the status column to `active'. If the agent has sufficient information to make the conceptual row available for use by the managed device, the management protocol set operation succeeds (a `noError' response is returned). Otherwise, the management protocol set operation fails with an error of `inconsistentValue'. NOTE WELL A conceptual row having a status column with value `notInService' or `notReady' is unavailable to the managed device. As such, it is possible for the managed device to create its own instances during the time between the management protocol set operation which sets the status column to `createAndWait' and the management protocol set operation which sets the status column to `active'. In this case, when the management protocol set operation is issued to set the status column to `active', the values held in the agent supersede those used by the managed device. If the management station is prevented from setting the status column to `active' (e.g., due to management station or network failure) the conceptual row will be left in the `notInService' or `notReady' state, consuming resources indefinitely. The agent must detect conceptual rows that have been in either state for an abnormally long period of time and remove them. It is the responsibility of the DESCRIPTION clause of the status column to indicate what an abnormally long period of time would be. This period of time should be long enough to allow for human response time (including `think time') between the creation of the conceptual row and the setting of the status to `active'. In the absence of such information in the DESCRIPTION clause, it is suggested that this period be approximately 5 minutes in length. This removal action applies not only to newly-created rows, but also to previously active rows which are set to, and left in, the notInService state for a prolonged period exceeding that which is considered normal for such a conceptual row. Conceptual Row Suspension When a conceptual row is `active', the management station may issue a management protocol set operation which sets the instance of the status column to `notInService'. If the agent is unwilling to do so, the set operation fails with an error of `wrongValue' or `inconsistentValue'. Otherwise, the conceptual row is taken out of service, and a `noError' response is returned. It is the responsibility of the DESCRIPTION clause of the status column to indicate under what circumstances the status column should be taken out of service (e.g., in order for the value of some other column of the same conceptual row to be modified). Conceptual Row Deletion For deletion of conceptual rows, a management protocol set operation is issued which sets the instance of the status column to `destroy'. This request may be made regardless of the current value of the status column (e.g., it is possible to delete conceptual rows which are either `notReady', `notInService' or `active'.) If the operation succeeds, then all instances associated with the conceptual row are immediately removed. · Integer32

This object is used to create a new row or delete an existing row in this table. To create a row, set this object to 'createAndGo'. To delete a row, set this object to 'destroy'.

SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form. To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279]. Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited. The use of control codes should be avoided. When it is necessary to represent a newline, the control code sequence CR LF should be used. The use of leading or trailing white space should be avoided. For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided. For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding. UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding. Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416]. Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (0..255) · OCTET STRING · hint 255t

This object specifies the name of the CSG Group. The value must be same as an entry in cgprsAccPtCsgGroupTable identified by cgprsAccPtCsgGroupName.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

When this object is set to 'true', ACL denoted by cgprsAccPtIPAccListGroupIn will be active. When set to 'false', it will become inactive.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

When this object is set to 'true', ACL denoted by cgprsAccPtIPAccListGroupOut will be active. When set to 'false', it will become inactive.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

When this object is set to 'true', Gateway waits for a RADIUS accounting response before sending a create PDP or Bearer context response to the MME or SGSN, for create PDP or Bearer context requests received at a particular APN. When this object is set to 'false', Gateway sends create PDP or Bearer response to MME or SGSN after sending a RADIUS start accounting message to the RADIUS server (without waiting for a response from the RADIUS accounting server).

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

Reference: 3GPP TS 29.061 Release 1999: Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS);Interworking between the Public Land Mobile Network (PLMN) supporting Packet Based services and Packet Data Networks (PDN).

This object specifies whether GGSN will be sending the radius attribute, IMSI value, in any of the radius requests to the radius server or not. When set to 'true', the IMSI attribute will not be sent by the GGSN. When set to 'false', the IMSI attribute will be sent by the GGSN. This object is obsoleted by cgprsAccPtSuppressRadiusAttribs.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

When this object is set to 'true', the Gateway will check the upstream TPDU source address against the address previously assigned to this user. If the addresses are different, the TPDU is dropped, the notification cgprsAccPtSecSrcViolNotif is generated and cgprsAccPtSourceAddrViolTpdus is incremented. This check will enable the Gateway to restrict the users with fake identity. When the object is set to 'false', no checking is performed by the Gateway.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

When this object is set to 'true', Gateway will check the upstream TPDU destination address against the range of IP addresses reserved for PLMN devices. If there is a match, the TPDU is dropped, the notification cgprsAccPtSecDestViolNotif is generated and cgprsAccPtDestAddrViolTpdus is incremented. The configuration of IP address ranges reserved for PLMN device is out of the scope of this MIB. This check would enable the Gateway to protect the GPRS network from some hacker who may try to flood the Gateway and PLMN nodes with intense data traffic. When the object is set to 'false', no checking is performed by the Gateway.

InetAddressType0 = unknown1 = ipv42 = ipv63 = ipv4z4 = ipv6z16 = dnsA value that represents a type of Internet address. unknown(0) An unknown address type. This value MUST be used if the value of the corresponding InetAddress object is a zero-length string. It may also be used to indicate an IP address that is not in one of the formats defined below. ipv4(1) An IPv4 address as defined by the InetAddressIPv4 textual convention. ipv6(2) An IPv6 address as defined by the InetAddressIPv6 textual convention. ipv4z(3) A non-global IPv4 address including a zone index as defined by the InetAddressIPv4z textual convention. ipv6z(4) A non-global IPv6 address including a zone index as defined by the InetAddressIPv6z textual convention. dns(16) A DNS domain name as defined by the InetAddressDNS textual convention. Each definition of a concrete InetAddressType value must be accompanied by a definition of a textual convention for use with that InetAddressType. To support future extensions, the InetAddressType textual convention SHOULD NOT be sub-typed in object type definitions. It MAY be sub-typed in compliance statements in order to require only a subset of these address types for a compliant implementation. Implementations must ensure that InetAddressType objects and any dependent objects (e.g., InetAddress objects) are consistent. An inconsistentValue error must be generated if an attempt to change an InetAddressType object would, for example, lead to an undefined InetAddress value. In particular, InetAddressType/InetAddress pairs must be changed together if the address type changes (e.g., from ipv6(2) to ipv4(1)). · Integer32

This object indicates the type of Internet address by which cgprsAccPtRedirInterMobilAddr is reachable.

InetAddressDenotes a generic Internet address. An InetAddress value is always interpreted within the context of an InetAddressType value. Every usage of the InetAddress textual convention is required to specify the InetAddressType object that provides the context. It is suggested that the InetAddressType object be logically registered before the object(s) that use the InetAddress textual convention, if they appear in the same logical row. The value of an InetAddress object must always be consistent with the value of the associated InetAddressType object. Attempts to set an InetAddress object to a value inconsistent with the associated InetAddressType must fail with an inconsistentValue error. When this textual convention is used as the syntax of an index object, there may be issues with the limit of 128 sub-identifiers specified in SMIv2, STD 58. In this case, the object definition MUST include a 'SIZE' clause to limit the number of potential instance sub-identifiers; otherwise the applicable constraints MUST be stated in the appropriate conceptual row DESCRIPTION clauses, or in the surrounding documentation if there is no single DESCRIPTION clause that is appropriate. SIZE (0..255) · OCTET STRING

This object represents the IP address of the device to which inter-mobile traffic will be re-directed. When this redirection is active on an APN, before downstream packets exit the Gateway, they are screened to see if they come from other GTP tunnels. If so, they won't be GTP-tunneled downstream, but will get redirected to the device specified by this object and cgprsAccPtRedirInterMobilTraffic is incremented. When this object is set to zero value, inter-mobile traffic will not be redirected i.e., the traffic will get switched through Gateway without going through any Gi interface.

BITS

Reference: 3GPP TS 29.061 Release 1999: Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS);Interworking between the Public Land Mobile Network (PLMN) supporting Packet Based services and Packet Data Networks (PDN).

This object indicates the attributes that will be suppressed by the Gateway in its its authorization and accounting requests to the RADIUS server.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

This object is used to enable Interim Accounting for a PDP or Bearer context on this APN. When set to 'true', accounting updates will be triggered whenever a update PDP or Bearer request is received. This object can set to 'true' only when accounting(cgprsAccPtAaaAccountingEnable) is enabled.

BITS

This object indicates the values set in various radius attributes by the Gateway while communicating with RADIUS Server. When set to 'none' - reset the value set by the options below. 'userNameMsisdn' - MSISDN of the mobile is sent in the user-name attribute. 'accSessIdChargingId' - Charging ID is sent in the accounting session ID attribute.

INTEGER0 = inService1 = maintenance · Integer32

This object denotes the operation mode of this APN. Each mode has different PDP or Bearer context activation and deactivation behavior and is given as below: inService - normal operational mode in which all functions are allowed. cgprsAccPtInServiceNotif notification will be sent to indicate the state change. maintenance - No new PDPs or Bearers can be activated in this state. cgprsAccPtMaintenanceNotif notification will be sent to indicate the state change.

Unsigned32 (0 | 30..4294967) · seconds

Absolute session timer is a RADIUS attribute (#27) sent by the AAA server in the Access-Accept packet. The Gateway will deactivate the PDP or Bearer when this timer expires. This object denotes the timer used by the Gateway when the same is not received from the AAA server. Value of '0' denotes that the timer is disabled.

SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form. To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279]. Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited. The use of control codes should be avoided. When it is necessary to represent a newline, the control code sequence CR LF should be used. The use of leading or trailing white space should be avoided. For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided. For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding. UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding. Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416]. Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (0..255) · OCTET STRING · hint 255t

This object denotes the value used as NAS ID in the RADIUS access requests sent by the Gateway on this APN. A zero length string needs to be set to unconfigure the NAS ID value.

SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form. To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279]. Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited. The use of control codes should be avoided. When it is necessary to represent a newline, the control code sequence CR LF should be used. The use of leading or trailing white space should be avoided. For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided. For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding. UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding. Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416]. Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (0..40) · OCTET STRING · hint 255t

Per PDP or Bearer Policy feature on the Gateway ensures that the PDP or Bearer contexts does not exceed bandwidth negotiated as part of PDP or Bearer context activation procedure. A service policy contains classification and policing parameters, details of the same is out of the scope of this MIB. This object denotes the name of the service policy that is applicable to inbound traffic on all the PDP's pertaining to this APN.

SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form. To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279]. Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited. The use of control codes should be avoided. When it is necessary to represent a newline, the control code sequence CR LF should be used. The use of leading or trailing white space should be avoided. For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided. For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding. UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding. Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416]. Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (0..40) · OCTET STRING · hint 255t

This object denotes the name of the service policy that is applicable to outbound traffic on all the PDP's or Bearer's pertaining to this APN.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

When this object is set to 'true', a PPP regen session creation would be rejected if the domain name in PCO field is different than the APN name. This object can only be set when cgprsAccPtPppRegenEnable is 'true'.

SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form. To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279]. Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited. The use of control codes should be avoided. When it is necessary to represent a newline, the control code sequence CR LF should be used. The use of leading or trailing white space should be avoided. For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided. For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding. UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding. Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416]. Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (0..255) · OCTET STRING · hint 255t

This object represents the name of the local address pool used when cgprsAccPtIpAddressPool is set to 'local'.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

This object is to enable service-aware billing (Diameter Credit Control Application [DCCA] support) on the access-point. This object can be set only when the object cGgsnSAServiceAware present in CISCO-GGSN-SERVICE-AWARE-MIB is set to 'true'.

InetAddressType0 = unknown1 = ipv42 = ipv63 = ipv4z4 = ipv6z16 = dnsA value that represents a type of Internet address. unknown(0) An unknown address type. This value MUST be used if the value of the corresponding InetAddress object is a zero-length string. It may also be used to indicate an IP address that is not in one of the formats defined below. ipv4(1) An IPv4 address as defined by the InetAddressIPv4 textual convention. ipv6(2) An IPv6 address as defined by the InetAddressIPv6 textual convention. ipv4z(3) A non-global IPv4 address including a zone index as defined by the InetAddressIPv4z textual convention. ipv6z(4) A non-global IPv6 address including a zone index as defined by the InetAddressIPv6z textual convention. dns(16) A DNS domain name as defined by the InetAddressDNS textual convention. Each definition of a concrete InetAddressType value must be accompanied by a definition of a textual convention for use with that InetAddressType. To support future extensions, the InetAddressType textual convention SHOULD NOT be sub-typed in object type definitions. It MAY be sub-typed in compliance statements in order to require only a subset of these address types for a compliant implementation. Implementations must ensure that InetAddressType objects and any dependent objects (e.g., InetAddress objects) are consistent. An inconsistentValue error must be generated if an attempt to change an InetAddressType object would, for example, lead to an undefined InetAddress value. In particular, InetAddressType/InetAddress pairs must be changed together if the address type changes (e.g., from ipv6(2) to ipv4(1)). · Integer32

This object indicates the type of Internet address of downlink next hop address.

InetAddressDenotes a generic Internet address. An InetAddress value is always interpreted within the context of an InetAddressType value. Every usage of the InetAddress textual convention is required to specify the InetAddressType object that provides the context. It is suggested that the InetAddressType object be logically registered before the object(s) that use the InetAddress textual convention, if they appear in the same logical row. The value of an InetAddress object must always be consistent with the value of the associated InetAddressType object. Attempts to set an InetAddress object to a value inconsistent with the associated InetAddressType must fail with an inconsistentValue error. When this textual convention is used as the syntax of an index object, there may be issues with the limit of 128 sub-identifiers specified in SMIv2, STD 58. In this case, the object definition MUST include a 'SIZE' clause to limit the number of potential instance sub-identifiers; otherwise the applicable constraints MUST be stated in the appropriate conceptual row DESCRIPTION clauses, or in the surrounding documentation if there is no single DESCRIPTION clause that is appropriate. SIZE (0..255) · OCTET STRING

This object advertises the next hop address on the Gateway to which downlink traffic destined for the Gateway is to be routed. The address type is given by the cgprsAccPtAdvDownlinkNextHopAddrType object.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

This object denotes the action to be taken when a COA initiated update request for QOS change fails for a PDP or Bearer context on this Access Point. If the object is set to 'true' and the update response from MME or SGSN (for a update request) is not got after the configured retries or the received response indicates a cause value other than 'request accepted', then the PDP or Bearer context will be deleted by the Gateway.

Unsigned32 (0 | 15..71582) · minutes

This object specifies the periodic accounting timer interval value for the access point. When this object is set to a value, 'interim' type accounting records will be sent at the specified interval for the PDP or Bearer contexts on this APN. When set to '0' the 'interim' type accounting records will not be sent out.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

This object when set to 'true', enables Gateway to receive and use the Accounting Periodic Interval from Radius for the PDP or Bearer contexts on this APN.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

This object when set to 'true', indicates that this APN is Gx enabled.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

The Proxy-CSCF server group represented by the object cgprsAccPtPcscfServerGroupName contains a list of Proxy-CSCF addresses which will be provided to the MS(UE) in the PCO (Protocol Configuration Option) response message. The object cgprsAccPtPcscfLoadBalance when set to 'true', enables Gateway to include the IP address of the least loaded P-CSCF server in the PCO response message. Round Robin algorithm is used for the selection of the least loaded P-CSCF server.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

This object when set to 'true', enables the Gateway to support a network behind the Mobile Station.

Unsigned32 (0..16)

This object indicates the number of subnetworks that can be permitted behind the Mobile station. This object can be set only when the object cgprsAccPtNetworkBehindMsEnable is set to 'true' as this object can take effect only when cgprsAccPtNetworkBehindMsEnable is 'true'. Setting the value of '0' to this object will not take effect. The value of this object will be set to '0' only if the object cgprsAccPtNetworkBehindMsEnable is set to 'false'.

INTEGER0 = noconfig1 = none2 = gcdr3 = egcdr · Integer32

This object denotes the charging record type of this APN. Each type has different PDP or Bearer context behavior and is given as below: noconfig - When no record type is configured. none - when there are no active PDP or Bearer contexts under this APN gcdr - When the derived record type is gcdr, the Gateway indicates CSG2 that gcdr generation is configured for this user, so that CSG2 will generate service level CDRs. egcdr - When the derived record type is egcdr, the Gateway indicates CSG2 that egcdr generation is configured for this user, so that CSG2 will not generate service level CDRs.

Unsigned32 (0..29)

Reference: csgprsCgGroupIndex is defined in CISCO-GPRS-CHARGING-MIB.

This object provides the charging group identifier to which an access point is associated with. By default the value of this object is 0, it indicates that the default charging group is associated with this access point entry. The value of this object must be same as one of the values identified by cgprsCgGroupIndex.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

This object indicates whether route propagation from PCOP to SUP (Supervisor) shall occur. This object can be set/unset only when the object cgprsAccPtIpAddressPool is configured. By default the value of this object is false. Setting it to true does not allow the redistribution of routes from PCOP to the SUP.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

This object when set to 'true' indicates that the APN has dual stack capability.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

This object indicates that the Gateway is programmed to check and reject all downstream packets with same source and destination. When the value is set to 'true', the Gateway check and reject all downstream packets with same source and destination and 'false' means this feature is disabled.

InetAddressType0 = unknown1 = ipv42 = ipv63 = ipv4z4 = ipv6z16 = dnsA value that represents a type of Internet address. unknown(0) An unknown address type. This value MUST be used if the value of the corresponding InetAddress object is a zero-length string. It may also be used to indicate an IP address that is not in one of the formats defined below. ipv4(1) An IPv4 address as defined by the InetAddressIPv4 textual convention. ipv6(2) An IPv6 address as defined by the InetAddressIPv6 textual convention. ipv4z(3) A non-global IPv4 address including a zone index as defined by the InetAddressIPv4z textual convention. ipv6z(4) A non-global IPv6 address including a zone index as defined by the InetAddressIPv6z textual convention. dns(16) A DNS domain name as defined by the InetAddressDNS textual convention. Each definition of a concrete InetAddressType value must be accompanied by a definition of a textual convention for use with that InetAddressType. To support future extensions, the InetAddressType textual convention SHOULD NOT be sub-typed in object type definitions. It MAY be sub-typed in compliance statements in order to require only a subset of these address types for a compliant implementation. Implementations must ensure that InetAddressType objects and any dependent objects (e.g., InetAddress objects) are consistent. An inconsistentValue error must be generated if an attempt to change an InetAddressType object would, for example, lead to an undefined InetAddress value. In particular, InetAddressType/InetAddress pairs must be changed together if the address type changes (e.g., from ipv6(2) to ipv4(1)). · Integer32

This object indicates the type of Internet address by which cgprsAccPtPriDnsServer and cgprsAccPtSecDnsServer are reachable. DNS addresses to be sent to the MS can come from DHCP server or RADIUS server based on IP address allocation scheme chosen by cgprsAccPtIpAddressPool. The IP address configured to cgprsAccPtPriDnsServer and cgprsAccPtSecDnsServer will be sent to MS only when - DHCP/RADIUS servers does not return any DNS address. - local address pool is used for IP address allocation for MS.

InetAddressDenotes a generic Internet address. An InetAddress value is always interpreted within the context of an InetAddressType value. Every usage of the InetAddress textual convention is required to specify the InetAddressType object that provides the context. It is suggested that the InetAddressType object be logically registered before the object(s) that use the InetAddress textual convention, if they appear in the same logical row. The value of an InetAddress object must always be consistent with the value of the associated InetAddressType object. Attempts to set an InetAddress object to a value inconsistent with the associated InetAddressType must fail with an inconsistentValue error. When this textual convention is used as the syntax of an index object, there may be issues with the limit of 128 sub-identifiers specified in SMIv2, STD 58. In this case, the object definition MUST include a 'SIZE' clause to limit the number of potential instance sub-identifiers; otherwise the applicable constraints MUST be stated in the appropriate conceptual row DESCRIPTION clauses, or in the surrounding documentation if there is no single DESCRIPTION clause that is appropriate. SIZE (0..255) · OCTET STRING

This object specifies the IP address of the primary DNS server that will be sent to MS.

InetAddressDenotes a generic Internet address. An InetAddress value is always interpreted within the context of an InetAddressType value. Every usage of the InetAddress textual convention is required to specify the InetAddressType object that provides the context. It is suggested that the InetAddressType object be logically registered before the object(s) that use the InetAddress textual convention, if they appear in the same logical row. The value of an InetAddress object must always be consistent with the value of the associated InetAddressType object. Attempts to set an InetAddress object to a value inconsistent with the associated InetAddressType must fail with an inconsistentValue error. When this textual convention is used as the syntax of an index object, there may be issues with the limit of 128 sub-identifiers specified in SMIv2, STD 58. In this case, the object definition MUST include a 'SIZE' clause to limit the number of potential instance sub-identifiers; otherwise the applicable constraints MUST be stated in the appropriate conceptual row DESCRIPTION clauses, or in the surrounding documentation if there is no single DESCRIPTION clause that is appropriate. SIZE (0..255) · OCTET STRING

This object specifies the IP address of the secondary DNS server that will be sent to MS. A secondary server can be configured only if primary exists.

InetAddressType0 = unknown1 = ipv42 = ipv63 = ipv4z4 = ipv6z16 = dnsA value that represents a type of Internet address. unknown(0) An unknown address type. This value MUST be used if the value of the corresponding InetAddress object is a zero-length string. It may also be used to indicate an IP address that is not in one of the formats defined below. ipv4(1) An IPv4 address as defined by the InetAddressIPv4 textual convention. ipv6(2) An IPv6 address as defined by the InetAddressIPv6 textual convention. ipv4z(3) A non-global IPv4 address including a zone index as defined by the InetAddressIPv4z textual convention. ipv6z(4) A non-global IPv6 address including a zone index as defined by the InetAddressIPv6z textual convention. dns(16) A DNS domain name as defined by the InetAddressDNS textual convention. Each definition of a concrete InetAddressType value must be accompanied by a definition of a textual convention for use with that InetAddressType. To support future extensions, the InetAddressType textual convention SHOULD NOT be sub-typed in object type definitions. It MAY be sub-typed in compliance statements in order to require only a subset of these address types for a compliant implementation. Implementations must ensure that InetAddressType objects and any dependent objects (e.g., InetAddress objects) are consistent. An inconsistentValue error must be generated if an attempt to change an InetAddressType object would, for example, lead to an undefined InetAddress value. In particular, InetAddressType/InetAddress pairs must be changed together if the address type changes (e.g., from ipv6(2) to ipv4(1)). · Integer32

This object indicates the type of Internet address by which cgprsAccPtPriNetbiosServer and cgprsAccPtSecNetbiosServer are reachable. NBNS addresses to be sent to the MS can come from DHCP server or RADIUS server based on IP address allocation scheme chosen by cgprsAccPtIpAddressPool. The IP address configured to cgprsAccPtPriNetbiosServer and cgprsAccPtSecNetbiosServer will be sent to MS only when - DHCP/RADIUS servers does not return any NBNS address. - local address pool is used for IP address allocation for MS.

InetAddressDenotes a generic Internet address. An InetAddress value is always interpreted within the context of an InetAddressType value. Every usage of the InetAddress textual convention is required to specify the InetAddressType object that provides the context. It is suggested that the InetAddressType object be logically registered before the object(s) that use the InetAddress textual convention, if they appear in the same logical row. The value of an InetAddress object must always be consistent with the value of the associated InetAddressType object. Attempts to set an InetAddress object to a value inconsistent with the associated InetAddressType must fail with an inconsistentValue error. When this textual convention is used as the syntax of an index object, there may be issues with the limit of 128 sub-identifiers specified in SMIv2, STD 58. In this case, the object definition MUST include a 'SIZE' clause to limit the number of potential instance sub-identifiers; otherwise the applicable constraints MUST be stated in the appropriate conceptual row DESCRIPTION clauses, or in the surrounding documentation if there is no single DESCRIPTION clause that is appropriate. SIZE (0..255) · OCTET STRING

This object specifies the IP address of the primary NetBIOS name server(NBNS) that will be sent to MS.

InetAddressDenotes a generic Internet address. An InetAddress value is always interpreted within the context of an InetAddressType value. Every usage of the InetAddress textual convention is required to specify the InetAddressType object that provides the context. It is suggested that the InetAddressType object be logically registered before the object(s) that use the InetAddress textual convention, if they appear in the same logical row. The value of an InetAddress object must always be consistent with the value of the associated InetAddressType object. Attempts to set an InetAddress object to a value inconsistent with the associated InetAddressType must fail with an inconsistentValue error. When this textual convention is used as the syntax of an index object, there may be issues with the limit of 128 sub-identifiers specified in SMIv2, STD 58. In this case, the object definition MUST include a 'SIZE' clause to limit the number of potential instance sub-identifiers; otherwise the applicable constraints MUST be stated in the appropriate conceptual row DESCRIPTION clauses, or in the surrounding documentation if there is no single DESCRIPTION clause that is appropriate. SIZE (0..255) · OCTET STRING

This object specifies the IP address of the secondary NetBIOS name server(NBNS) that will be sent to MS. A secondary server can be configured only if primary exists.

BITS

This object indicates whether IMS traffic, both signaling and data, is allowed on this APN. When set to disable - IMS traffic is not allowed. enable - IMS traffic is allowed. exclusive - Only IMS traffic is allowed, non-IMS traffic will be rejected. transformPrimary - non IMS traffic will be allowed but all the rules applicable to IMS traffic will also apply, for example. ACL's. The options 'exclusive' and 'transformPrimary' are mutually exclusive and can be set only when IMS is enabled, i.e., when 'enable' is set.

SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form. To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279]. Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited. The use of control codes should be avoided. When it is necessary to represent a newline, the control code sequence CR LF should be used. The use of leading or trailing white space should be avoided. For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided. For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding. UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding. Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416]. Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (0..100) · OCTET STRING · hint 255t

This object represents the Proxy-CSCF server group that will be used by this APN. Proxy-CSCF server group contains list of Proxy-CSCF addresses which will be provided to MS(UE) in response to a PDP contexts for which P-CSCF address request field is set in PCO.

AccessControlListOrZeroAccess Control List (ACL) specifies criteria by which packets are evaluated as matching or non-matching. The ACL also specifies an action which is applied to packets which match. Objects which use this textual convention identify ACLs. ACLs are configured/defined outside the scope of this MIB. The value of an object with this syntax associates to an ACL with the same ACL number. A value of zero indicates no ACL is configured. (0..199 | 1300..2699) · Integer32

This object represents the access list that will be applied to all the IMS signaling PDP context received by this APN from the PDN for forwarding towards a MS. An IMS signaling PDP context will have IMS signaling flag set in the PCO field.

AccessControlListOrZeroAccess Control List (ACL) specifies criteria by which packets are evaluated as matching or non-matching. The ACL also specifies an action which is applied to packets which match. Objects which use this textual convention identify ACLs. ACLs are configured/defined outside the scope of this MIB. The value of an object with this syntax associates to an ACL with the same ACL number. A value of zero indicates no ACL is configured. (0..199 | 1300..2699) · Integer32

This object represents the access list that will be applied to all the IMS signaling PDP context received by this APN from a MS for forwarding towards PDN. An IMS signaling PDP context will have IMS signaling flag set in the PCO field.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

This object represents the action to be taken on a non IMS PDP context, when cgprsAccPtImsEnable is set to 'true' on this APN. When this object is set to 'true', respective PDP context activation will be rejected. When set to 'false', PDP activation will be based on the QoS negotiation.

INTEGER1 = all2 = home3 = roaming4 = roamingTrusted5 = visiting6 = visitingTrusted · Integer32

This object represents the type of MS to which the charging profile selected by cgprsAccPtChgProfile is applied on this APN. Different types of MS - A roaming MS belongs to a MME/SGSN of a different PLMN. A visitor MS is one whose IMSI value belongs to a different PLMN. A home MS is neither roamer nor visitor, i.e., IMSI and MME/SGSN corresponds to same PLMN. A roamer/visitor is said to be Trusted/Friendly if the different PLMN is a trusted/friendly PLMN.

Unsigned32

This object represents the charging profile number to be applied to MS denoted by cgprsAccPtMsType on this APN. Details of charging profile parameters are outside the scope of this MIB and are covered by CISCO-GPRS-CHARGING-MIB. This object is mandatory while creating a row. The current valid values are 1 to 255.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

This object specifies whether charging characteristics value supplied by MME or SGSN will be ignored and the values supplied in this table are used. When this object is set to 'true', the value supplied by MME or SGSN will be ignored.

RowStatus1 = active2 = notInService3 = notReady4 = createAndGo5 = createAndWait6 = destroyThe RowStatus textual convention is used to manage the creation and deletion of conceptual rows, and is used as the value of the SYNTAX clause for the status column of a conceptual row (as described in Section 7.7.1 of [2].) The status column has six defined values: - `active', which indicates that the conceptual row is available for use by the managed device; - `notInService', which indicates that the conceptual row exists in the agent, but is unavailable for use by the managed device (see NOTE below); 'notInService' has no implication regarding the internal consistency of the row, availability of resources, or consistency with the current state of the managed device; - `notReady', which indicates that the conceptual row exists in the agent, but is missing information necessary in order to be available for use by the managed device (i.e., one or more required columns in the conceptual row have not been instanciated); - `createAndGo', which is supplied by a management station wishing to create a new instance of a conceptual row and to have its status automatically set to active, making it available for use by the managed device; - `createAndWait', which is supplied by a management station wishing to create a new instance of a conceptual row (but not make it available for use by the managed device); and, - `destroy', which is supplied by a management station wishing to delete all of the instances associated with an existing conceptual row. Whereas five of the six values (all except `notReady') may be specified in a management protocol set operation, only three values will be returned in response to a management protocol retrieval operation: `notReady', `notInService' or `active'. That is, when queried, an existing conceptual row has only three states: it is either available for use by the managed device (the status column has value `active'); it is not available for use by the managed device, though the agent has sufficient information to attempt to make it so (the status column has value `notInService'); or, it is not available for use by the managed device, and an attempt to make it so would fail because the agent has insufficient information (the state column has value `notReady'). NOTE WELL This textual convention may be used for a MIB table, irrespective of whether the values of that table's conceptual rows are able to be modified while it is active, or whether its conceptual rows must be taken out of service in order to be modified. That is, it is the responsibility of the DESCRIPTION clause of the status column to specify whether the status column must not be `active' in order for the value of some other column of the same conceptual row to be modified. If such a specification is made, affected columns may be changed by an SNMP set PDU if the RowStatus would not be equal to `active' either immediately before or after processing the PDU. In other words, if the PDU also contained a varbind that would change the RowStatus value, the column in question may be changed if the RowStatus was not equal to `active' as the PDU was received, or if the varbind sets the status to a value other than 'active'. Also note that whenever any elements of a row exist, the RowStatus column must also exist. To summarize the effect of having a conceptual row with a status column having a SYNTAX clause value of RowStatus, consider the following state diagram: STATE +--------------+-----------+-------------+------------- | A | B | C | D | |status col.|status column| |status column | is | is |status column ACTION |does not exist| notReady | notInService| is active --------------+--------------+-----------+-------------+------------- set status |noError ->D|inconsist- |inconsistent-|inconsistent- column to | or | entValue| Value| Value createAndGo |inconsistent- | | | | Value| | | --------------+--------------+-----------+-------------+------------- set status |noError see 1|inconsist- |inconsistent-|inconsistent- column to | or | entValue| Value| Value createAndWait |wrongValue | | | --------------+--------------+-----------+-------------+------------- set status |inconsistent- |inconsist- |noError |noError column to | Value| entValue| | active | | | | | | or | | | | | | | |see 2 ->D|see 8 ->D| ->D --------------+--------------+-----------+-------------+------------- set status |inconsistent- |inconsist- |noError |noError ->C column to | Value| entValue| | notInService | | | | | | or | | or | | | | | |see 3 ->C| ->C|see 6 --------------+--------------+-----------+-------------+------------- set status |noError |noError |noError |noError ->A column to | | | | or destroy | ->A| ->A| ->A|see 7 --------------+--------------+-----------+-------------+------------- set any other |see 4 |noError |noError |see 5 column to some| | | | value | | see 1| ->C| ->D --------------+--------------+-----------+-------------+------------- (1) goto B or C, depending on information available to the agent. (2) if other variable bindings included in the same PDU, provide values for all columns which are missing but required, and all columns have acceptable values, then return noError and goto D. (3) if other variable bindings included in the same PDU, provide legal values for all columns which are missing but required, then return noError and goto C. (4) at the discretion of the agent, the return value may be either: inconsistentName: because the agent does not choose to create such an instance when the corresponding RowStatus instance does not exist, or inconsistentValue: if the supplied value is inconsistent with the state of some other MIB object's value, or noError: because the agent chooses to create the instance. If noError is returned, then the instance of the status column must also be created, and the new state is B or C, depending on the information available to the agent. If inconsistentName or inconsistentValue is returned, the row remains in state A. (5) depending on the MIB definition for the column/table, either noError or inconsistentValue may be returned. (6) the return value can indicate one of the following errors: wrongValue: because the agent does not support notInService (e.g., an agent which does not support createAndWait), or inconsistentValue: because the agent is unable to take the row out of service at this time, perhaps because it is in use and cannot be de-activated. (7) the return value can indicate the following error: inconsistentValue: because the agent is unable to remove the row at this time, perhaps because it is in use and cannot be de-activated. (8) the transition to D can fail, e.g., if the values of the conceptual row are inconsistent, then the error code would be inconsistentValue. NOTE: Other processing of (this and other varbinds of) the set request may result in a response other than noError being returned, e.g., wrongValue, noCreation, etc. Conceptual Row Creation There are four potential interactions when creating a conceptual row: selecting an instance-identifier which is not in use; creating the conceptual row; initializing any objects for which the agent does not supply a default; and, making the conceptual row available for use by the managed device. Interaction 1: Selecting an Instance-Identifier The algorithm used to select an instance-identifier varies for each conceptual row. In some cases, the instance- identifier is semantically significant, e.g., the destination address of a route, and a management station selects the instance-identifier according to the semantics. In other cases, the instance-identifier is used solely to distinguish conceptual rows, and a management station without specific knowledge of the conceptual row might examine the instances present in order to determine an unused instance-identifier. (This approach may be used, but it is often highly sub-optimal; however, it is also a questionable practice for a naive management station to attempt conceptual row creation.) Alternately, the MIB module which defines the conceptual row might provide one or more objects which provide assistance in determining an unused instance-identifier. For example, if the conceptual row is indexed by an integer-value, then an object having an integer-valued SYNTAX clause might be defined for such a purpose, allowing a management station to issue a management protocol retrieval operation. In order to avoid unnecessary collisions between competing management stations, `adjacent' retrievals of this object should be different. Finally, the management station could select a pseudo-random number to use as the index. In the event that this index was already in use and an inconsistentValue was returned in response to the management protocol set operation, the management station should simply select a new pseudo-random number and retry the operation. A MIB designer should choose between the two latter algorithms based on the size of the table (and therefore the efficiency of each algorithm). For tables in which a large number of entries are expected, it is recommended that a MIB object be defined that returns an acceptable index for creation. For tables with small numbers of entries, it is recommended that the latter pseudo-random index mechanism be used. Interaction 2: Creating the Conceptual Row Once an unused instance-identifier has been selected, the management station determines if it wishes to create and activate the conceptual row in one transaction or in a negotiated set of interactions. Interaction 2a: Creating and Activating the Conceptual Row The management station must first determine the column requirements, i.e., it must determine those columns for which it must or must not provide values. Depending on the complexity of the table and the management station's knowledge of the agent's capabilities, this determination can be made locally by the management station. Alternately, the management station issues a management protocol get operation to examine all columns in the conceptual row that it wishes to create. In response, for each column, there are three possible outcomes: - a value is returned, indicating that some other management station has already created this conceptual row. We return to interaction 1. - the exception `noSuchInstance' is returned, indicating that the agent implements the object-type associated with this column, and that this column in at least one conceptual row would be accessible in the MIB view used by the retrieval were it to exist. For those columns to which the agent provides read-create access, the `noSuchInstance' exception tells the management station that it should supply a value for this column when the conceptual row is to be created. - the exception `noSuchObject' is returned, indicating that the agent does not implement the object-type associated with this column or that there is no conceptual row for which this column would be accessible in the MIB view used by the retrieval. As such, the management station can not issue any management protocol set operations to create an instance of this column. Once the column requirements have been determined, a management protocol set operation is accordingly issued. This operation also sets the new instance of the status column to `createAndGo'. When the agent processes the set operation, it verifies that it has sufficient information to make the conceptual row available for use by the managed device. The information available to the agent is provided by two sources: the management protocol set operation which creates the conceptual row, and, implementation-specific defaults supplied by the agent (note that an agent must provide implementation-specific defaults for at least those objects which it implements as read-only). If there is sufficient information available, then the conceptual row is created, a `noError' response is returned, the status column is set to `active', and no further interactions are necessary (i.e., interactions 3 and 4 are skipped). If there is insufficient information, then the conceptual row is not created, and the set operation fails with an error of `inconsistentValue'. On this error, the management station can issue a management protocol retrieval operation to determine if this was because it failed to specify a value for a required column, or, because the selected instance of the status column already existed. In the latter case, we return to interaction 1. In the former case, the management station can re-issue the set operation with the additional information, or begin interaction 2 again using `createAndWait' in order to negotiate creation of the conceptual row. NOTE WELL Regardless of the method used to determine the column requirements, it is possible that the management station might deem a column necessary when, in fact, the agent will not allow that particular columnar instance to be created or written. In this case, the management protocol set operation will fail with an error such as `noCreation' or `notWritable'. In this case, the management station decides whether it needs to be able to set a value for that particular columnar instance. If not, the management station re-issues the management protocol set operation, but without setting a value for that particular columnar instance; otherwise, the management station aborts the row creation algorithm. Interaction 2b: Negotiating the Creation of the Conceptual Row The management station issues a management protocol set operation which sets the desired instance of the status column to `createAndWait'. If the agent is unwilling to process a request of this sort, the set operation fails with an error of `wrongValue'. (As a consequence, such an agent must be prepared to accept a single management protocol set operation, i.e., interaction 2a above, containing all of the columns indicated by its column requirements.) Otherwise, the conceptual row is created, a `noError' response is returned, and the status column is immediately set to either `notInService' or `notReady', depending on whether it has sufficient information to (attempt to) make the conceptual row available for use by the managed device. If there is sufficient information available, then the status column is set to `notInService'; otherwise, if there is insufficient information, then the status column is set to `notReady'. Regardless, we proceed to interaction 3. Interaction 3: Initializing non-defaulted Objects The management station must now determine the column requirements. It issues a management protocol get operation to examine all columns in the created conceptual row. In the response, for each column, there are three possible outcomes: - a value is returned, indicating that the agent implements the object-type associated with this column and had sufficient information to provide a value. For those columns to which the agent provides read-create access (and for which the agent allows their values to be changed after their creation), a value return tells the management station that it may issue additional management protocol set operations, if it desires, in order to change the value associated with this column. - the exception `noSuchInstance' is returned, indicating that the agent implements the object-type associated with this column, and that this column in at least one conceptual row would be accessible in the MIB view used by the retrieval were it to exist. However, the agent does not have sufficient information to provide a value, and until a value is provided, the conceptual row may not be made available for use by the managed device. For those columns to which the agent provides read-create access, the `noSuchInstance' exception tells the management station that it must issue additional management protocol set operations, in order to provide a value associated with this column. - the exception `noSuchObject' is returned, indicating that the agent does not implement the object-type associated with this column or that there is no conceptual row for which this column would be accessible in the MIB view used by the retrieval. As such, the management station can not issue any management protocol set operations to create an instance of this column. If the value associated with the status column is `notReady', then the management station must first deal with all `noSuchInstance' columns, if any. Having done so, the value of the status column becomes `notInService', and we proceed to interaction 4. Interaction 4: Making the Conceptual Row Available Once the management station is satisfied with the values associated with the columns of the conceptual row, it issues a management protocol set operation to set the status column to `active'. If the agent has sufficient information to make the conceptual row available for use by the managed device, the management protocol set operation succeeds (a `noError' response is returned). Otherwise, the management protocol set operation fails with an error of `inconsistentValue'. NOTE WELL A conceptual row having a status column with value `notInService' or `notReady' is unavailable to the managed device. As such, it is possible for the managed device to create its own instances during the time between the management protocol set operation which sets the status column to `createAndWait' and the management protocol set operation which sets the status column to `active'. In this case, when the management protocol set operation is issued to set the status column to `active', the values held in the agent supersede those used by the managed device. If the management station is prevented from setting the status column to `active' (e.g., due to management station or network failure) the conceptual row will be left in the `notInService' or `notReady' state, consuming resources indefinitely. The agent must detect conceptual rows that have been in either state for an abnormally long period of time and remove them. It is the responsibility of the DESCRIPTION clause of the status column to indicate what an abnormally long period of time would be. This period of time should be long enough to allow for human response time (including `think time') between the creation of the conceptual row and the setting of the status to `active'. In the absence of such information in the DESCRIPTION clause, it is suggested that this period be approximately 5 minutes in length. This removal action applies not only to newly-created rows, but also to previously active rows which are set to, and left in, the notInService state for a prolonged period exceeding that which is considered normal for such a conceptual row. Conceptual Row Suspension When a conceptual row is `active', the management station may issue a management protocol set operation which sets the instance of the status column to `notInService'. If the agent is unwilling to do so, the set operation fails with an error of `wrongValue' or `inconsistentValue'. Otherwise, the conceptual row is taken out of service, and a `noError' response is returned. It is the responsibility of the DESCRIPTION clause of the status column to indicate under what circumstances the status column should be taken out of service (e.g., in order for the value of some other column of the same conceptual row to be modified). Conceptual Row Deletion For deletion of conceptual rows, a management protocol set operation is issued which sets the instance of the status column to `destroy'. This request may be made regardless of the current value of the status column (e.g., it is possible to delete conceptual rows which are either `notReady', `notInService' or `active'.) If the operation succeeds, then all instances associated with the conceptual row are immediately removed. · Integer32

This object is used to create a new row or delete an existing row in this table. To create a row, set this object to 'createAndGo'. To delete a row, set this object to 'destroy'.

SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form. To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279]. Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited. The use of control codes should be avoided. When it is necessary to represent a newline, the control code sequence CR LF should be used. The use of leading or trailing white space should be avoided. For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided. For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding. UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding. Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416]. Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (0..40) · OCTET STRING · hint 255t

This object represents the local policy name that will be used by CAC for the PDP's or Bearer's pertaining to this APN. Details of QoS parameters pertaining to a CAC policy are out of scope of this MIB and are covered in CISCO-GGSN-QOS-MIB. A zero-length string denotes that no policy is configured.

SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form. To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279]. Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited. The use of control codes should be avoided. When it is necessary to represent a newline, the control code sequence CR LF should be used. The use of leading or trailing white space should be avoided. For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided. For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding. UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding. Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416]. Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (0..40) · OCTET STRING · hint 255t

A Bandwidth pool is a user defined pool with bandwidth pre-allocation details like amount of available bandwidth, percent of bandwidth available to a specific traffic class. CAC uses this information during PDP or Bearer context activation and modification procedures. This object represents the name of the bandwidth pool used for upstream traffic. Configuration of the bandwidth pool is covered in CISCO-GGSN-QOS-MIB. A zero-length string denotes that no policy is configured.

SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form. To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279]. Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited. The use of control codes should be avoided. When it is necessary to represent a newline, the control code sequence CR LF should be used. The use of leading or trailing white space should be avoided. For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided. For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding. UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding. Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416]. Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (0..40) · OCTET STRING · hint 255t

This object represents the name of the bandwidth pool used for downstream traffic. Configuration of the bandwidth pool is covered in CISCO-GGSN-QOS-MIB. A zero-length string denotes that no policy is configured.

InetAddressType0 = unknown1 = ipv42 = ipv63 = ipv4z4 = ipv6z16 = dnsA value that represents a type of Internet address. unknown(0) An unknown address type. This value MUST be used if the value of the corresponding InetAddress object is a zero-length string. It may also be used to indicate an IP address that is not in one of the formats defined below. ipv4(1) An IPv4 address as defined by the InetAddressIPv4 textual convention. ipv6(2) An IPv6 address as defined by the InetAddressIPv6 textual convention. ipv4z(3) A non-global IPv4 address including a zone index as defined by the InetAddressIPv4z textual convention. ipv6z(4) A non-global IPv6 address including a zone index as defined by the InetAddressIPv6z textual convention. dns(16) A DNS domain name as defined by the InetAddressDNS textual convention. Each definition of a concrete InetAddressType value must be accompanied by a definition of a textual convention for use with that InetAddressType. To support future extensions, the InetAddressType textual convention SHOULD NOT be sub-typed in object type definitions. It MAY be sub-typed in compliance statements in order to require only a subset of these address types for a compliant implementation. Implementations must ensure that InetAddressType objects and any dependent objects (e.g., InetAddress objects) are consistent. An inconsistentValue error must be generated if an attempt to change an InetAddressType object would, for example, lead to an undefined InetAddress value. In particular, InetAddressType/InetAddress pairs must be changed together if the address type changes (e.g., from ipv6(2) to ipv4(1)). · Integer32

This object indicates the type of Internet address by which cgprsAccPtRpDestAddr is reachable.

InetAddressDenotes a generic Internet address. An InetAddress value is always interpreted within the context of an InetAddressType value. Every usage of the InetAddress textual convention is required to specify the InetAddressType object that provides the context. It is suggested that the InetAddressType object be logically registered before the object(s) that use the InetAddress textual convention, if they appear in the same logical row. The value of an InetAddress object must always be consistent with the value of the associated InetAddressType object. Attempts to set an InetAddress object to a value inconsistent with the associated InetAddressType must fail with an inconsistentValue error. When this textual convention is used as the syntax of an index object, there may be issues with the limit of 128 sub-identifiers specified in SMIv2, STD 58. In this case, the object definition MUST include a 'SIZE' clause to limit the number of potential instance sub-identifiers; otherwise the applicable constraints MUST be stated in the appropriate conceptual row DESCRIPTION clauses, or in the surrounding documentation if there is no single DESCRIPTION clause that is appropriate. SIZE (0..255) · OCTET STRING

This object specifies the destination IP address to which the route probe packet needs to be sent.

INTEGER1 = udp2 = icmp · Integer32

This objects specifies the protocol type of route probe packet. This object can be set only after cgprsAccPtRpDestAddr is being set.

InetPortNumberRepresents a 16 bit port number of an Internet transport layer protocol. Port numbers are assigned by IANA. A current list of all assignments is available from <http://www.iana.org/>. The value zero is object-specific and must be defined as part of the description of any object that uses this syntax. Examples of the usage of zero might include situations where a port number is unknown, or when the value zero is used as a wildcard in a filter.Reference: STD 6 (RFC 768), STD 7 (RFC 793) and RFC 2960 (0..65535) · Unsigned32 · hint d

This object specifies the destination port number of the route probe packet when cgprsAccPtRpProtocol is set to 'udp'. This object can be set only after cgprsAccPtRpDestAddr is being set.

Unsigned32 (1..255) · seconds

This object specifies the TTL value set in the route probe packet. This object can be set only after cgprsAccPtRpDestAddr is being set.

Unsigned32

This object specifies the base virtual template for an APN. To create a sub-interface for each PDP or Bearer, a base virtual-template needs to be configured so that virtual-access interface can be cloned from it. Many APN can share one base virtual-template. But one APN can only use one base virtual-template. This object must be set to appropriate value for IPv6 APN i.e., when the object cgprsAccPtIpv6Enable or cgprsAccPtIpv6Exclusive is set to 'true'.

InetAddressType0 = unknown1 = ipv42 = ipv63 = ipv4z4 = ipv6z16 = dnsA value that represents a type of Internet address. unknown(0) An unknown address type. This value MUST be used if the value of the corresponding InetAddress object is a zero-length string. It may also be used to indicate an IP address that is not in one of the formats defined below. ipv4(1) An IPv4 address as defined by the InetAddressIPv4 textual convention. ipv6(2) An IPv6 address as defined by the InetAddressIPv6 textual convention. ipv4z(3) A non-global IPv4 address including a zone index as defined by the InetAddressIPv4z textual convention. ipv6z(4) A non-global IPv6 address including a zone index as defined by the InetAddressIPv6z textual convention. dns(16) A DNS domain name as defined by the InetAddressDNS textual convention. Each definition of a concrete InetAddressType value must be accompanied by a definition of a textual convention for use with that InetAddressType. To support future extensions, the InetAddressType textual convention SHOULD NOT be sub-typed in object type definitions. It MAY be sub-typed in compliance statements in order to require only a subset of these address types for a compliant implementation. Implementations must ensure that InetAddressType objects and any dependent objects (e.g., InetAddress objects) are consistent. An inconsistentValue error must be generated if an attempt to change an InetAddressType object would, for example, lead to an undefined InetAddress value. In particular, InetAddressType/InetAddress pairs must be changed together if the address type changes (e.g., from ipv6(2) to ipv4(1)). · Integer32

This object specifies the type of cgprsAccPtIpv6DnsPriAddress and cgprsAccPtIpv6DnsSecAddress. DNS addresses to be sent to the MS can come from DHCP server or RADIUS server based on IP address allocation scheme chosen by cgprsAccPtIpv6AddrPool. The IP address configured to cgprsAccPtIpv6DnsPriAddress and cgprsAccPtIpv6DnsSecAddress will be sent to MS only when - DHCP/RADIUS servers does not return any DNS address. - local address pool is used for IP address allocation for MS.

InetAddressDenotes a generic Internet address. An InetAddress value is always interpreted within the context of an InetAddressType value. Every usage of the InetAddress textual convention is required to specify the InetAddressType object that provides the context. It is suggested that the InetAddressType object be logically registered before the object(s) that use the InetAddress textual convention, if they appear in the same logical row. The value of an InetAddress object must always be consistent with the value of the associated InetAddressType object. Attempts to set an InetAddress object to a value inconsistent with the associated InetAddressType must fail with an inconsistentValue error. When this textual convention is used as the syntax of an index object, there may be issues with the limit of 128 sub-identifiers specified in SMIv2, STD 58. In this case, the object definition MUST include a 'SIZE' clause to limit the number of potential instance sub-identifiers; otherwise the applicable constraints MUST be stated in the appropriate conceptual row DESCRIPTION clauses, or in the surrounding documentation if there is no single DESCRIPTION clause that is appropriate. SIZE (0..255) · OCTET STRING

This object specifies the IPv6 address of the primary DNS server that will be sent to MS.

InetAddressDenotes a generic Internet address. An InetAddress value is always interpreted within the context of an InetAddressType value. Every usage of the InetAddress textual convention is required to specify the InetAddressType object that provides the context. It is suggested that the InetAddressType object be logically registered before the object(s) that use the InetAddress textual convention, if they appear in the same logical row. The value of an InetAddress object must always be consistent with the value of the associated InetAddressType object. Attempts to set an InetAddress object to a value inconsistent with the associated InetAddressType must fail with an inconsistentValue error. When this textual convention is used as the syntax of an index object, there may be issues with the limit of 128 sub-identifiers specified in SMIv2, STD 58. In this case, the object definition MUST include a 'SIZE' clause to limit the number of potential instance sub-identifiers; otherwise the applicable constraints MUST be stated in the appropriate conceptual row DESCRIPTION clauses, or in the surrounding documentation if there is no single DESCRIPTION clause that is appropriate. SIZE (0..255) · OCTET STRING

This object specifies the IPv6 address of the secondary DNS server that will be sent to MS. This object can be configured only after configuring the primary DNS address(cgprsAccPtIpv6DnsPriAddress).

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

This object specifies whether the APN supports IPv6 PDP or Bearer. The Gateway supports dual stack APN. Both IPv6 and IPv4 PDP or Bearer can be created for the same APN.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

This object specifies whether the APN supports only IPv6 PDPs or Bearers.

AccessControlListNameAccess Control List (ACL) specifies the criteria by which packets are evaluated as matching or non-matching. The ACL also specifies an action, which is applied to packets which match. Objects which use this textual convention identify ACLs. ACLs are configured/defined outside the scope of this MIB. The name of an object with this syntax associates to an ACL with the same ACL name. SIZE (0..255) · OCTET STRING

This object specifies the name of the access list applied to all the traffic received by this APN from the PDN, for forwarding towards a MS.

AccessControlListNameAccess Control List (ACL) specifies the criteria by which packets are evaluated as matching or non-matching. The ACL also specifies an action, which is applied to packets which match. Objects which use this textual convention identify ACLs. ACLs are configured/defined outside the scope of this MIB. The name of an object with this syntax associates to an ACL with the same ACL name. SIZE (0..255) · OCTET STRING

This object specifies the name of the access list applied to all the traffic received by this APN from a MS, for forwarding towards PDN.

INTEGER1 = global2 = dhcp3 = disable4 = local5 = radius · Integer32

This object specifies a dynamic address allocation method followed by this access point. - 'global', which indicates that no method is defined specifically to this access point and the DHCP or radius server configured for this Gateway under AAA configurations will be used to allocation a dynamic IPv6 address to the user. - 'dhcp', which indicates that the DHCP server will be used. - 'radius', which indicates that the radius server will be used. - 'disable', which indicates that dynamic address allocation is disabled. - 'local', indicates that local address pool configured on the Gateway is going to be used. cgprsAccPtIpv6AddrLocalPoolName denotes the name of the corresponding address pool.

SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form. To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279]. Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited. The use of control codes should be avoided. When it is necessary to represent a newline, the control code sequence CR LF should be used. The use of leading or trailing white space should be avoided. For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided. For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding. UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding. Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416]. Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (0..255) · OCTET STRING · hint 255t

This object specifies the name of the local address pool used when cgprsAccPtIpv6AddrPool is set to 'local'.

INTEGER0 = none1 = all2 = intermobile · Integer32

This object specifies the traffic redirection in an APN. - 'none', indicates that, traffic will not be redirected i.e., the traffic will get switched through the Gateway without going through any Gi interface. - 'intermobile', when this redirection is active on an APN, before downstream packets exit the Gateway, they are screened to see if they come from other GTP tunnels. If so, packets won't be GTP-tunneled downstream, but will get redirected to the device specified by the object cgprsAccPtIpv6RedirectAddr. - 'all', when this redirection is active on an APN, redirect all packets to a specified destination, given by the object cgprsAccPtIpv6RedirectAddr, regardless whether the destination address belongs to a MS on the same Gateway or not.

InetAddressType0 = unknown1 = ipv42 = ipv63 = ipv4z4 = ipv6z16 = dnsA value that represents a type of Internet address. unknown(0) An unknown address type. This value MUST be used if the value of the corresponding InetAddress object is a zero-length string. It may also be used to indicate an IP address that is not in one of the formats defined below. ipv4(1) An IPv4 address as defined by the InetAddressIPv4 textual convention. ipv6(2) An IPv6 address as defined by the InetAddressIPv6 textual convention. ipv4z(3) A non-global IPv4 address including a zone index as defined by the InetAddressIPv4z textual convention. ipv6z(4) A non-global IPv6 address including a zone index as defined by the InetAddressIPv6z textual convention. dns(16) A DNS domain name as defined by the InetAddressDNS textual convention. Each definition of a concrete InetAddressType value must be accompanied by a definition of a textual convention for use with that InetAddressType. To support future extensions, the InetAddressType textual convention SHOULD NOT be sub-typed in object type definitions. It MAY be sub-typed in compliance statements in order to require only a subset of these address types for a compliant implementation. Implementations must ensure that InetAddressType objects and any dependent objects (e.g., InetAddress objects) are consistent. An inconsistentValue error must be generated if an attempt to change an InetAddressType object would, for example, lead to an undefined InetAddress value. In particular, InetAddressType/InetAddress pairs must be changed together if the address type changes (e.g., from ipv6(2) to ipv4(1)). · Integer32

This object specifies the type of cgprsAccPtIpv6RedirectAddr.

InetAddressDenotes a generic Internet address. An InetAddress value is always interpreted within the context of an InetAddressType value. Every usage of the InetAddress textual convention is required to specify the InetAddressType object that provides the context. It is suggested that the InetAddressType object be logically registered before the object(s) that use the InetAddress textual convention, if they appear in the same logical row. The value of an InetAddress object must always be consistent with the value of the associated InetAddressType object. Attempts to set an InetAddress object to a value inconsistent with the associated InetAddressType must fail with an inconsistentValue error. When this textual convention is used as the syntax of an index object, there may be issues with the limit of 128 sub-identifiers specified in SMIv2, STD 58. In this case, the object definition MUST include a 'SIZE' clause to limit the number of potential instance sub-identifiers; otherwise the applicable constraints MUST be stated in the appropriate conceptual row DESCRIPTION clauses, or in the surrounding documentation if there is no single DESCRIPTION clause that is appropriate. SIZE (0..255) · OCTET STRING

This object specifies the Internet address of the device to which traffic will be re-directed.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

When this object is set to 'true', the Gateway will check the upstream TPDU source address against the address previously assigned to this user. If the addresses are different, the TPDU is dropped. This check will enable the Gateway to restrict the users with fake identity. When the object is set to 'false', the Gateway will not perform any checking on the upstream TPDU for the source address.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

When this object is set to 'true', the Gateway will check the upstream TPDU destination address against the range of IP addresses reserved for PLMN devices. If there is a match, the TPDU is dropped. This check would enable the Gateway to protect the GPRS network from some hacker who may try to flood the Gateway and PLMN nodes with intense data traffic. When the object is set to 'false', the Gateway will not perform any checking on the upstream TPDU for the destination address.

Gauge32

This object indicates the total number of IPv6 addresses currently allocated to user.

InterfaceIndexOrZeroEither the value 0, or the ifIndex value of an interface in the ifTable. (0..2147483647) · Integer32

The object indicates the interface index, of the interface which is to be used for DHCPv6 request multicasting.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

This object indicates that whether DHCPv6 rapid-commit feature is enabled for this APN.

SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form. To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279]. Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited. The use of control codes should be avoided. When it is necessary to represent a newline, the control code sequence CR LF should be used. The use of leading or trailing white space should be avoided. For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided. For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding. UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding. Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416]. Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (1..255) · OCTET STRING · hint 255t

This object represents the IPV6 DHCP pool-name configured for this APN.

SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form. To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279]. Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited. The use of control codes should be avoided. When it is necessary to represent a newline, the control code sequence CR LF should be used. The use of leading or trailing white space should be avoided. For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided. For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding. UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding. Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416]. Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (0..255) · OCTET STRING · hint 255t

Reference: cGgsnSACsgGroupName is defined in CISCO-GGSN-SERVICE-AWARE-MIB.

This object specifies CSG Group name to use to communicate with the CSG server in an access point configuration. The value must be same as an entry in cGgsnSACsgTable identified by cGgsnSACsgGroupName.

RowStatus1 = active2 = notInService3 = notReady4 = createAndGo5 = createAndWait6 = destroyThe RowStatus textual convention is used to manage the creation and deletion of conceptual rows, and is used as the value of the SYNTAX clause for the status column of a conceptual row (as described in Section 7.7.1 of [2].) The status column has six defined values: - `active', which indicates that the conceptual row is available for use by the managed device; - `notInService', which indicates that the conceptual row exists in the agent, but is unavailable for use by the managed device (see NOTE below); 'notInService' has no implication regarding the internal consistency of the row, availability of resources, or consistency with the current state of the managed device; - `notReady', which indicates that the conceptual row exists in the agent, but is missing information necessary in order to be available for use by the managed device (i.e., one or more required columns in the conceptual row have not been instanciated); - `createAndGo', which is supplied by a management station wishing to create a new instance of a conceptual row and to have its status automatically set to active, making it available for use by the managed device; - `createAndWait', which is supplied by a management station wishing to create a new instance of a conceptual row (but not make it available for use by the managed device); and, - `destroy', which is supplied by a management station wishing to delete all of the instances associated with an existing conceptual row. Whereas five of the six values (all except `notReady') may be specified in a management protocol set operation, only three values will be returned in response to a management protocol retrieval operation: `notReady', `notInService' or `active'. That is, when queried, an existing conceptual row has only three states: it is either available for use by the managed device (the status column has value `active'); it is not available for use by the managed device, though the agent has sufficient information to attempt to make it so (the status column has value `notInService'); or, it is not available for use by the managed device, and an attempt to make it so would fail because the agent has insufficient information (the state column has value `notReady'). NOTE WELL This textual convention may be used for a MIB table, irrespective of whether the values of that table's conceptual rows are able to be modified while it is active, or whether its conceptual rows must be taken out of service in order to be modified. That is, it is the responsibility of the DESCRIPTION clause of the status column to specify whether the status column must not be `active' in order for the value of some other column of the same conceptual row to be modified. If such a specification is made, affected columns may be changed by an SNMP set PDU if the RowStatus would not be equal to `active' either immediately before or after processing the PDU. In other words, if the PDU also contained a varbind that would change the RowStatus value, the column in question may be changed if the RowStatus was not equal to `active' as the PDU was received, or if the varbind sets the status to a value other than 'active'. Also note that whenever any elements of a row exist, the RowStatus column must also exist. To summarize the effect of having a conceptual row with a status column having a SYNTAX clause value of RowStatus, consider the following state diagram: STATE +--------------+-----------+-------------+------------- | A | B | C | D | |status col.|status column| |status column | is | is |status column ACTION |does not exist| notReady | notInService| is active --------------+--------------+-----------+-------------+------------- set status |noError ->D|inconsist- |inconsistent-|inconsistent- column to | or | entValue| Value| Value createAndGo |inconsistent- | | | | Value| | | --------------+--------------+-----------+-------------+------------- set status |noError see 1|inconsist- |inconsistent-|inconsistent- column to | or | entValue| Value| Value createAndWait |wrongValue | | | --------------+--------------+-----------+-------------+------------- set status |inconsistent- |inconsist- |noError |noError column to | Value| entValue| | active | | | | | | or | | | | | | | |see 2 ->D|see 8 ->D| ->D --------------+--------------+-----------+-------------+------------- set status |inconsistent- |inconsist- |noError |noError ->C column to | Value| entValue| | notInService | | | | | | or | | or | | | | | |see 3 ->C| ->C|see 6 --------------+--------------+-----------+-------------+------------- set status |noError |noError |noError |noError ->A column to | | | | or destroy | ->A| ->A| ->A|see 7 --------------+--------------+-----------+-------------+------------- set any other |see 4 |noError |noError |see 5 column to some| | | | value | | see 1| ->C| ->D --------------+--------------+-----------+-------------+------------- (1) goto B or C, depending on information available to the agent. (2) if other variable bindings included in the same PDU, provide values for all columns which are missing but required, and all columns have acceptable values, then return noError and goto D. (3) if other variable bindings included in the same PDU, provide legal values for all columns which are missing but required, then return noError and goto C. (4) at the discretion of the agent, the return value may be either: inconsistentName: because the agent does not choose to create such an instance when the corresponding RowStatus instance does not exist, or inconsistentValue: if the supplied value is inconsistent with the state of some other MIB object's value, or noError: because the agent chooses to create the instance. If noError is returned, then the instance of the status column must also be created, and the new state is B or C, depending on the information available to the agent. If inconsistentName or inconsistentValue is returned, the row remains in state A. (5) depending on the MIB definition for the column/table, either noError or inconsistentValue may be returned. (6) the return value can indicate one of the following errors: wrongValue: because the agent does not support notInService (e.g., an agent which does not support createAndWait), or inconsistentValue: because the agent is unable to take the row out of service at this time, perhaps because it is in use and cannot be de-activated. (7) the return value can indicate the following error: inconsistentValue: because the agent is unable to remove the row at this time, perhaps because it is in use and cannot be de-activated. (8) the transition to D can fail, e.g., if the values of the conceptual row are inconsistent, then the error code would be inconsistentValue. NOTE: Other processing of (this and other varbinds of) the set request may result in a response other than noError being returned, e.g., wrongValue, noCreation, etc. Conceptual Row Creation There are four potential interactions when creating a conceptual row: selecting an instance-identifier which is not in use; creating the conceptual row; initializing any objects for which the agent does not supply a default; and, making the conceptual row available for use by the managed device. Interaction 1: Selecting an Instance-Identifier The algorithm used to select an instance-identifier varies for each conceptual row. In some cases, the instance- identifier is semantically significant, e.g., the destination address of a route, and a management station selects the instance-identifier according to the semantics. In other cases, the instance-identifier is used solely to distinguish conceptual rows, and a management station without specific knowledge of the conceptual row might examine the instances present in order to determine an unused instance-identifier. (This approach may be used, but it is often highly sub-optimal; however, it is also a questionable practice for a naive management station to attempt conceptual row creation.) Alternately, the MIB module which defines the conceptual row might provide one or more objects which provide assistance in determining an unused instance-identifier. For example, if the conceptual row is indexed by an integer-value, then an object having an integer-valued SYNTAX clause might be defined for such a purpose, allowing a management station to issue a management protocol retrieval operation. In order to avoid unnecessary collisions between competing management stations, `adjacent' retrievals of this object should be different. Finally, the management station could select a pseudo-random number to use as the index. In the event that this index was already in use and an inconsistentValue was returned in response to the management protocol set operation, the management station should simply select a new pseudo-random number and retry the operation. A MIB designer should choose between the two latter algorithms based on the size of the table (and therefore the efficiency of each algorithm). For tables in which a large number of entries are expected, it is recommended that a MIB object be defined that returns an acceptable index for creation. For tables with small numbers of entries, it is recommended that the latter pseudo-random index mechanism be used. Interaction 2: Creating the Conceptual Row Once an unused instance-identifier has been selected, the management station determines if it wishes to create and activate the conceptual row in one transaction or in a negotiated set of interactions. Interaction 2a: Creating and Activating the Conceptual Row The management station must first determine the column requirements, i.e., it must determine those columns for which it must or must not provide values. Depending on the complexity of the table and the management station's knowledge of the agent's capabilities, this determination can be made locally by the management station. Alternately, the management station issues a management protocol get operation to examine all columns in the conceptual row that it wishes to create. In response, for each column, there are three possible outcomes: - a value is returned, indicating that some other management station has already created this conceptual row. We return to interaction 1. - the exception `noSuchInstance' is returned, indicating that the agent implements the object-type associated with this column, and that this column in at least one conceptual row would be accessible in the MIB view used by the retrieval were it to exist. For those columns to which the agent provides read-create access, the `noSuchInstance' exception tells the management station that it should supply a value for this column when the conceptual row is to be created. - the exception `noSuchObject' is returned, indicating that the agent does not implement the object-type associated with this column or that there is no conceptual row for which this column would be accessible in the MIB view used by the retrieval. As such, the management station can not issue any management protocol set operations to create an instance of this column. Once the column requirements have been determined, a management protocol set operation is accordingly issued. This operation also sets the new instance of the status column to `createAndGo'. When the agent processes the set operation, it verifies that it has sufficient information to make the conceptual row available for use by the managed device. The information available to the agent is provided by two sources: the management protocol set operation which creates the conceptual row, and, implementation-specific defaults supplied by the agent (note that an agent must provide implementation-specific defaults for at least those objects which it implements as read-only). If there is sufficient information available, then the conceptual row is created, a `noError' response is returned, the status column is set to `active', and no further interactions are necessary (i.e., interactions 3 and 4 are skipped). If there is insufficient information, then the conceptual row is not created, and the set operation fails with an error of `inconsistentValue'. On this error, the management station can issue a management protocol retrieval operation to determine if this was because it failed to specify a value for a required column, or, because the selected instance of the status column already existed. In the latter case, we return to interaction 1. In the former case, the management station can re-issue the set operation with the additional information, or begin interaction 2 again using `createAndWait' in order to negotiate creation of the conceptual row. NOTE WELL Regardless of the method used to determine the column requirements, it is possible that the management station might deem a column necessary when, in fact, the agent will not allow that particular columnar instance to be created or written. In this case, the management protocol set operation will fail with an error such as `noCreation' or `notWritable'. In this case, the management station decides whether it needs to be able to set a value for that particular columnar instance. If not, the management station re-issues the management protocol set operation, but without setting a value for that particular columnar instance; otherwise, the management station aborts the row creation algorithm. Interaction 2b: Negotiating the Creation of the Conceptual Row The management station issues a management protocol set operation which sets the desired instance of the status column to `createAndWait'. If the agent is unwilling to process a request of this sort, the set operation fails with an error of `wrongValue'. (As a consequence, such an agent must be prepared to accept a single management protocol set operation, i.e., interaction 2a above, containing all of the columns indicated by its column requirements.) Otherwise, the conceptual row is created, a `noError' response is returned, and the status column is immediately set to either `notInService' or `notReady', depending on whether it has sufficient information to (attempt to) make the conceptual row available for use by the managed device. If there is sufficient information available, then the status column is set to `notInService'; otherwise, if there is insufficient information, then the status column is set to `notReady'. Regardless, we proceed to interaction 3. Interaction 3: Initializing non-defaulted Objects The management station must now determine the column requirements. It issues a management protocol get operation to examine all columns in the created conceptual row. In the response, for each column, there are three possible outcomes: - a value is returned, indicating that the agent implements the object-type associated with this column and had sufficient information to provide a value. For those columns to which the agent provides read-create access (and for which the agent allows their values to be changed after their creation), a value return tells the management station that it may issue additional management protocol set operations, if it desires, in order to change the value associated with this column. - the exception `noSuchInstance' is returned, indicating that the agent implements the object-type associated with this column, and that this column in at least one conceptual row would be accessible in the MIB view used by the retrieval were it to exist. However, the agent does not have sufficient information to provide a value, and until a value is provided, the conceptual row may not be made available for use by the managed device. For those columns to which the agent provides read-create access, the `noSuchInstance' exception tells the management station that it must issue additional management protocol set operations, in order to provide a value associated with this column. - the exception `noSuchObject' is returned, indicating that the agent does not implement the object-type associated with this column or that there is no conceptual row for which this column would be accessible in the MIB view used by the retrieval. As such, the management station can not issue any management protocol set operations to create an instance of this column. If the value associated with the status column is `notReady', then the management station must first deal with all `noSuchInstance' columns, if any. Having done so, the value of the status column becomes `notInService', and we proceed to interaction 4. Interaction 4: Making the Conceptual Row Available Once the management station is satisfied with the values associated with the columns of the conceptual row, it issues a management protocol set operation to set the status column to `active'. If the agent has sufficient information to make the conceptual row available for use by the managed device, the management protocol set operation succeeds (a `noError' response is returned). Otherwise, the management protocol set operation fails with an error of `inconsistentValue'. NOTE WELL A conceptual row having a status column with value `notInService' or `notReady' is unavailable to the managed device. As such, it is possible for the managed device to create its own instances during the time between the management protocol set operation which sets the status column to `createAndWait' and the management protocol set operation which sets the status column to `active'. In this case, when the management protocol set operation is issued to set the status column to `active', the values held in the agent supersede those used by the managed device. If the management station is prevented from setting the status column to `active' (e.g., due to management station or network failure) the conceptual row will be left in the `notInService' or `notReady' state, consuming resources indefinitely. The agent must detect conceptual rows that have been in either state for an abnormally long period of time and remove them. It is the responsibility of the DESCRIPTION clause of the status column to indicate what an abnormally long period of time would be. This period of time should be long enough to allow for human response time (including `think time') between the creation of the conceptual row and the setting of the status to `active'. In the absence of such information in the DESCRIPTION clause, it is suggested that this period be approximately 5 minutes in length. This removal action applies not only to newly-created rows, but also to previously active rows which are set to, and left in, the notInService state for a prolonged period exceeding that which is considered normal for such a conceptual row. Conceptual Row Suspension When a conceptual row is `active', the management station may issue a management protocol set operation which sets the instance of the status column to `notInService'. If the agent is unwilling to do so, the set operation fails with an error of `wrongValue' or `inconsistentValue'. Otherwise, the conceptual row is taken out of service, and a `noError' response is returned. It is the responsibility of the DESCRIPTION clause of the status column to indicate under what circumstances the status column should be taken out of service (e.g., in order for the value of some other column of the same conceptual row to be modified). Conceptual Row Deletion For deletion of conceptual rows, a management protocol set operation is issued which sets the instance of the status column to `destroy'. This request may be made regardless of the current value of the status column (e.g., it is possible to delete conceptual rows which are either `notReady', `notInService' or `active'.) If the operation succeeds, then all instances associated with the conceptual row are immediately removed. · Integer32

This object is used to create a new row or delete an existing row in this table. This object must be set to 'creatAndGo' to create an entry and set to 'destroy' to delete an entry. The value in any column may be modified any time even the value of this entry rowStatus object is 'active'.

Unsigned32 (1..4294967295)

An arbitrary non-zero integer value uniquely identifying each notification previously sent by the GPRS. This value increases monotonically with each notification sent by the Gateway. When it reaches the maximum value, it wraps to 1.

Unsigned32 (1..65535)

This object specifies the access point which has been created, changed or modified.

INTEGER1 = modification2 = creation3 = deletion · Integer32

This object describes the reason of the notification.

Counter32

Reference: GSM 12.04: Digital cellular telecommunications system (Phase 2+); Performance data measurements, Section: B.9.1.1.

This object indicates the total number of PDP or Bearer context activation procedures initiated by any MS on this APN. Trigger Condition: This counter is triggered by create PDP or Bearer request message.

Counter32

Reference: GSM 12.04: Digital cellular telecommunications system (Phase 2+); Performance data measurements, Section: B.9.1.2.

This object indicates the total number of successfully completed PDP or Bearer context activation procedures initiated by MS on this APN. Trigger Condition: This counter is triggered by create PDP or Bearer request message.

Counter32

Reference: GSM 12.04: Digital cellular telecommunications system (Phase 2+); Performance data measurements, Section: B.9.1.3.

This object indicates the total number of dynamic PDP or Bearer context activation procedures initiated by the MS on this APN. When a MS requests dynamic PDP or Bearer address from the PLMN, a dynamic PDP or Bearer context activation procedure is initiated. Trigger Condition: This counter is triggered by a request message to create a PDP or Bearer context.

Counter32

Reference: GSM 12.04: Digital cellular telecommunications system (Phase 2+); Performance data measurements, Section: B.9.1.4.

This object indicates the total number of successfully completed dynamic PDP or Bearer context activation procedures initiated by MS on this APN. Trigger Condition: This counter is triggered by a request message to create a PDP or Bearer context.

Counter32

Reference: GSM 12.04: Digital cellular telecommunications system (Phase 2+); Performance data measurements, Section: B.9.1.5.

This object indicates the total number of PDP or Bearer context deactivation procedures initiated by the MS on this APN. Trigger Condition: This counter is triggered by a request message to delete PDP or Bearer context.

Counter32

Reference: GSM 12.04: Digital cellular telecommunications system (Phase 2+); Performance data measurements, Section: B.9.1.6.

This object indicates the total number of successfully completed PDP or Bearer context deactivation procedures initiated by the MS. Trigger Condition: This counter is triggered by a request message to delete PDP or Bearer context.

Counter32

This object indicates the total number of network initiated PDP or Bearer context activation procedures. Trigger Condition: This counter is triggered by a request message to create PDP or Bearer context.

Counter32

This object indicates the total number of successfully completed network initiated PDP or Bearer context activation procedures. Trigger Condition: This counter is triggered by a request message to create PDP or Bearer context.

Counter32

Reference: GSM 12.04: Digital cellular telecommunications system (Phase 2+); Performance data measurements, Section: B.9.1.7.

This object indicates the total number of PDP context deactivation procedures initiated by the Gateway. Trigger Condition: This counter is triggered by delete PDP request message.

Counter32

Reference: GSM 12.04: Digital cellular telecommunications system (Phase 2+); Performance data measurements, Section: B.9.1.8.

This object indicates the total number of successfully completed PDP context deactivation procedures initiated by the Gateway. Trigger Condition: This counter is triggered by delete PDP request message.

Gauge32

Reference: GSM 12.04: Digital cellular telecommunications system (Phase 2+); Performance data measurements, Section: B.9.1.9.

This object indicates the current number of active PDP or Bearer contexts on this APN. Trigger Condition: This counter is incremented/ decremented by a request message to create/delete PDP or Bearer context respectively.

Counter32 · bytes

This object indicates the total payload volume in upstream traffic. Data flow from MS to PDN is considered to be upstream traffic. This object is deprecated by cgprsAccPtRevUpstreamTrafficVol.

Counter32 · bytes

This object indicates the total payload volume in downstream traffic. Data flow from PDN to MS is considered as downstream traffic. This object is deprecated by cgprsAccPtRevDownstrTrafficVol.

Counter32 · packets

This object indicates the total number of upstream TPDU's that have been dropped due to source address violation as specified by cgprsAccPtVerifyUpStrTpduSrcAddr.

Counter32 · packets

This object indicates the total number of upstream TPDU's that have been dropped due to destination address violation as specified by cgprsAccPtVerifyUpStrTpduDstAddr.

Counter32 · packets

This object represents the total number of packets, pertaining to inter mobile communication, that have been redirected to device specified by cgprsAccPtRedirInterMobilAddr.

Counter64 (0..18446744073709551615) · bytes

This object indicates the total payload volume in upstream traffic. Data flow from MS to PDN is considered to be upstream traffic. Trigger Condition: This counter is triggered when upstream traffic is being routed to PDN.

Counter64 (0..18446744073709551615) · bytes

This object indicates the total payload volume in downstream traffic. Data flow from PDN to MS is considered as downstream traffic. Trigger Condition: This counter is triggered when downstream traffic is being routed to PDN.

Counter32 · packets

This object represents the total number of upstream packets sent on this APN. Data flow from MS to PDN is considered to be upstream traffic. Trigger Condition: This counter is triggered when upstream traffic is being routed to PDN.

Counter32 · packets

This object represents the total number of downstream packets sent on this APN. Data flow from PDN to MS is considered to be downstream traffic. Trigger Condition: This counter is triggered when downstream traffic is being routed to PDN.

Counter32 · packets

This object represents the total number of DHCP address request sent by the Gateway on this APN. Trigger Condition: This counter is triggered by create PDP or Bearer request message.

Counter32 · packets

This object represents the total number of successful DHCP address request sent by the Gateway on this APN. Trigger Condition: This counter is triggered by create PDP or Bearer request message.

Counter32 · packets

This object represents the total number of DHCP address release request sent by the Gateway on this APN. Trigger Condition: This counter is triggered by delete PDP or Bearer request message.

Counter32

This object indicates the total number of IPv6 PDP or Bearer context activation procedures initiated by any MS on this APN. Trigger Condition: This counter is triggered by a request message to create PDP or Bearer context.

Counter32

This object indicates the total number of successfully completed IPv6 PDP or Bearer context activation procedures initiated by MS on this APN. Trigger Condition: This counter is triggered by create PDP or Bearer response message sent by the Gateway.

Counter32

This object indicates the total number of IPv6 PDP or Bearer context deactivation procedures initiated by network. Trigger Condition: This counter is triggered by delete PDP or Bearer request message by network.

Counter32

This object indicates the total number of successfully completed IPv6 PDP or Bearer context deactivation procedures initiated by the network on this APN. Trigger Condition: This counter is triggered by delete PDP or Bearer response message by network.

Counter32

This object indicates the total number of dynamic IPv6 PDP or Bearer context activation procedures initiated by the MS on this APN. When a MS requests dynamic PDP or Bearer address from the PLMN, a dynamic PDP or Bearer context activation procedure is initiated. Trigger Condition: This counter is triggered by create PDP or Bearer request message, received by Gateway from an MS.

Counter32

This object indicates the total number of successfully completed dynamic IPv6 PDP or Bearer context activation procedures initiated by MS on this APN. Trigger Condition: This counter is triggered by create PDP or Bearer response message.

Counter32

This object indicates the total number of IPv6 PDP or Bearer context deactivation procedures initiated by the MS on this APN. Trigger Condition: This counter is triggered by delete PDP or Bearer request message.

Counter32

This object indicates the total number of successfully completed IPv6 PDP or Bearer context deactivation procedures initiated by the MS on this APN. Trigger Condition: This counter is triggered by delete PDP or Bearer context response message.

Counter32

This object indicates the total number of IPv6 PDP context deactivation procedures initiated by the Gateway on this APN. Trigger Condition: This counter is triggered by delete PDP request message, sent by the Gateway to a MME or SGSN.

Counter32

This object indicates the total number of successfully completed IPv6 PDP context deactivation procedures initiated by the Gateway on this APN. Trigger Condition: This counter is triggered by delete PDP response message, received by the Gateway from a MME or SGSN.

Counter64 (0..18446744073709551615) · bytes

This object indicates the total payload volume in upstream traffic sent on this APN. Data flow from MS to PDN is considered to be upstream traffic. Trigger Condition: This counter is triggered when upstream traffic is being routed to PDN.

Counter64 (0..18446744073709551615) · bytes

This object indicates the total payload volume in downstream traffic sent on this APN. Data flow from PDN to MS is considered as downstream traffic. Trigger Condition: This counter is triggered when downstream traffic is being routed to PDN.

Counter32 · packets

This object indicates the total number of upstream packets sent on this APN. Data flow from MS to PDN is considered to be upstream traffic. Trigger Condition: This counter is triggered when upstream traffic is being routed to PDN.

Counter32 · packets

This object represents the total number of downstream packets sent on this APN. Data flow from PDN to MS is considered to be downstream traffic. Trigger Condition: This counter is triggered when downstream traffic is being routed to PDN.

Counter32 · messages

This object represents the total number of PDP or Bearer context update requests sent on this APN. Trigger Condition: This counter is triggered when a PDP or Bearer context update request is initiated.

Counter32 · messages

This object represents the total number of successful PDP or Bearer context update responses received with a cause value 'Request accepted' for the initiated update requests on this APN. Trigger condition: This counter is triggered when a update response with cause value 'Request accepted' is received on this APN.

Counter32 · messages

This object represents the total number of Change of Authorization (COA) messages received on this APN. Trigger condition: This counter is triggered when a COA message is received.

Counter32 · messages

This object represents the number of COA messages that were acknowledged by the Gateway with a COA ACK. Trigger condition: This counter is triggered when a COA ACK is sent by the Gateway.

Counter32 · pdps

This object represents the number of times Direct tunnel is enabled for the PDP contexts on this APN in Gateway.

Counter32

This object indicates the total number of Bearers in this APN.

Counter32

This object indicates the total number of Bearer creation initiated by MME, SGSN or MS.

Counter32

This object indicates the total number of successful Bearer creation initiated by MME, SGSN or MS.

Counter32

This object indicates the total number of Bearer delete initiated by network.

Counter32

This object indicates the total number of Bearer modify initiated by MME or SGSN.

Counter32

This object indicates the total number of successful Bearer modify initiated by MME or SGSN.

Counter32

This object indicates the total number of Bearer update initiated by network.

Counter32

This object indicates the total number of successful Bearer update initiated by network.

Counter32

This object indicates the total number of dedicated Bearer creation initiated by network.

Counter32

This object indicates the total number of successful dedicated Bearer creation initiated by network.

Counter32

This object indicates the total number of IPv6 dedicated Bearer creation initiated by network.

Counter32

This object indicates the total number of IPv6 dedicated Bearer creation initiated by network.

Counter32

This object indicates the total number of IPv4v6 PDP or Bearer context activation procedures initiated by any MS on this APN.

Counter32

This object indicates the total number of successfully completed IPv4v6 PDP or Bearer context activation procedures initiated by MS on this APN.

Counter32

This object indicates the total number of IPv4v6 PDP or Bearer context deactivation procedures initiated by the MS on this APN.

Counter32

This object indicates the total number of successfully completed IPv4v6 PDP or Bearer context deactivation procedures initiated by the MS on this APN.

Counter32

This object indicates the total number of IPv4v6, dedicated Bearer activations that were initiated by the PGW on this APN.

Counter32

This object indicates the total number of IPv4v6 dedicated Bearers that were successfully activated by the PGW.

Counter32

This object represents the number of DHCP Discover messages received by the Gateway. The UE sends this message upon bootup/lease rebinding timer expiry.

Counter32

This object represents the number of DHCP request messages received by the Gateway. The UE may send the DHCP-Request message with Requested-IP-Address option in one of the many following scenarios: UE is rebooting and it has an IPv4-address with unexpired lease. UE is selecting an offer from the DHCP-server. UE is renewing the lease. UE is attempting to rebind the lease.

Counter32

This object represents the number of DHCP decline messages received by the Gateway from UE. The UE may send this message when the IP-address it received is found to be already in use by another device.

Counter32

This object represents the number DHCP - Release messages received by the Gateway. The User Equipment may send this message when the IPv4-session is terminated.

Counter32

This object represents the number of DHCP offer messages sent by the Gateway. The Gateway sends this message on allocating a Requested IP address to the User equipment.

Counter32

This object represents the number of DHCP Acknowledge messages sent by the Gateway. The Gateway sends this message to the User equipment in response to a DHCP-Request message.

Counter32

This object represents the number of DHCP-Negative-Acknowledge messages sent by the Gateway. The Gateway sends DHCP-Negative acknowledge message to the User Equipment in the following cases: If the DHCP-Request contains an IP-address that is different from the address that PGW sent in the DHCP-Offer. If PGW is unable to allocate the offered IP-address

Counter32

This object represents the number of DHCP-Inform message sent by the Gateway. The Gateway shall respond with a DHCP-Acknowledge to the DHCP-Inform message sent by the UE

Counter32

This object represents the number of DHCP-Unknown messages received by the Gateway. DHCP-Control messages, with unknown format are specified as DHCP-uknown message.

Counter32

This object represents the number of times the Gateway has retried to establish a connection with the Proxy server.

Counter32

This object represents the number of times a DHCP proxy server control message is dropped by the Gateway due to some error in the message.

Gauge32 · bearers

This object indicates the current number of active Bearer on this APN.

Counter32

This object represents the number of times an outgoing DHCP proxy server control message is dropped by the Gateway due to some failure in the Gateway.

Counter32

This object represents the number of times an incoming DHCP proxy server control message has been dropped by the Gateway due to IP allocation error in the message.

Counter32

This object represents the total number dedicated bearer deactivation request initiated by the Gateway.

Counter32

This object represents the total number of dedicated bearer modification request with QoS change initiated by the Gateway.

Counter32

This object represents the total number of successful dedicated bearer modification request with QoS change initiated by the Gateway.

Counter32

This object represents the total number of dedicated bearer modification request without QoS change initiated by the Gateway.

Counter32

This object represents the total number of successful dedicated bearer modification request without QoS change initiated by the Gateway.

Counter32

This object indicates the total number of IPv4v6 PDP or Bearer context activation procedures initiated by any MS on this APN.

Counter32

This object indicates the total number of successfully completed IPv4v6 PDP or Bearer context activation procedures initiated by MS on this APN.

Counter32

This object indicates the total number of failed PDP or Bearer context activation procedures initiated by MS on this APN.

Counter32

This object represents the total number of failed PDP or Bearer context update for the initiated update requests on this APN.

Counter32

This object represents the total number of failed PDP or Bearer context update response not received due to the time out for the initiated update requests on this APN.

Counter32

This object represents the total number of DHCPv6 information request message handled by the Gateway's DHCPv6 proxy-client.

Counter32

This object represents the total number of DHCPv6 response message sent by the Gateway's DHCPv6 proxy-client.

Counter32

This object represents the total number of times a local response was sent for the DHCPv6 information request received by the Gateway's DHCPv6 proxy-client.

Counter32

This object represents the total number of times DHCPv6 IP allocation was successful.

Counter32

This object represents the total number of times DHCPv6 IP allocation was failed.

Counter32

This object represents the total number of times an allocated DHCPv6 IP was released.

Counter32

This object represents the total number of times an allocated DHCPv6 IP renewal was failed.

Counter32

This object represents the total number of times an unknown message was handled by the Gateway's DHCPv6 proxy-client.

Counter32

This object represents the total number of times an error has occurred at the Gateway's DHCPv6 proxy-client.

Integer32 (1..65535) · minutes

This object represents the time interval at which the statistics are sampled. Interval configuration is out of the scope of the MIB and are covered in CISCO-GGSN-MIB.

Integer32 (0..65535) · minutes

This object represents the delta value between the time when this data is collected and the time it is been retrieved.

Gauge32 · bytes

This object represents the total payload volume in upstream traffic sent on this APN in the last sampling period specified by cgprsAccPtThruputInterval.

Gauge32 · bytes

This object represents the total payload volume in downstream traffic sent on this APN in the last sampling period specified by cgprsAccPtThruputInterval.

Gauge32 · packets

This object represents the number of upstream packets sent on this APN in the last sampling period specified by cgprsAccPtThruputInterval.

Gauge32 · packets

This object represents the number of downstream packets sent on this APN in the last sampling period specified by cgprsAccPtThruputInterval.