CISCO-ITP-ACL-MIB

CItpTcAclIdAn numeric Identifier used to specify an access list used to permit and deny packets based on MTP3 information. Either the value 0 or the value of access list identifier. A value of zero indicates that an access list is not specified. (0 | 2700..2999) · Unsigned32

The identifier used to select a list of access list entries. The administrator will select an valid identifier within the specified range defined for SS7 access lists.

INTEGER1 = comment2 = entry · Integer32

The list of possible entry types. 'comments' : A statement used to describe and document access list entries. 'entry' : A access list entry.

Unsigned32 (1..65535)

An numeric value assigned to each access list entry. The entries of the same type must be unique. Entries will be tested in ascending order.

CItpAclAction1 = accept2 = discardThe list of possible actions to be performed on a packet when information in message matches an access control entry . 'accept' : The matching packet is accepted for further processing. 'discard' : The matching packet is to be discarded without any further processing on this packet. · Integer32

The action to be performed on the packet that matched this access control.

BITS

The cItpAclType object indicates which types of tests will be processed on the each access list entry. Each may contain one or more filters. The filter will be processed ascending order(si,dpc...all). Each test is evaluated and if true the packet is processed according to cItpAclAction. 'si' : The cItpAclSi is the relevant column. The packet is compared to cItpAclSi to determine if the packet matches this filter. 'dpc' : The cItpAclDpc and cItpAclDpcMask are the relevant columns. The packet is compared to cItpAclDpc in conjunction with cItpAclDpcMask to determine if the packet matches this access control. The mask is first negated (~mask) and bitwise AND is perform with mask and dpc. 'dpcMask' : Indicates that a mask is to be applied when the dpc filter is specified. If the mask is not specified then the mask is assumed to be all zeros. 'opc' : cItpAclOpc and cItpAclOpcMask are the relevant columns. The packet is compared to cItpAclOpc in conjunction with cItpAclOpcMask to determine if the packet matches this access control. The mask is first negated (~mask) and bitwise AND is perform with mask and opc. 'opcMask' : Indicates that a mask is to be applied when the opc filter is specified. If the mask is not specified then the mask is assumed to be all zeros. 'pattern' : cItpAclPattern and cItpAclOffset are the relevant columns. The matching criteria is based on matching the pattern specified by cItpAclPattern at offset cItpAclOffset from the start of the packet. 'comment' : The cItpAclComment object provides an entry that can be used to describe filters. 'cgpa' : The cItpAclCgpa, cItpAclCgpaMask, cItpAclCgpaSsn and cItpAclCgpaSsnMask are the relevant columns. The Calling Party Point code is compare with cItpAclCgpaPC using the ItpAclCgpaMask. Also, the cItpAclCgpaSsn and cItpAclCgpaSsnMask are compared if specified. 'cgpaMask': Indicates that a mask is to be applied when the cgpa filter is specified. If the mask is not specified then the mask is assumed to be all zeros. 'cgpaSsn' : Indicates that a Subsystem Number(SSN) is to be checked when the cgpa filter is specified. 'cgpaSsnMask': Indicates that SSN mask is to be applied when checking the SSN number for the cgpa filter is specified. If the mask is not specified then the mask is assumed to be all zeros. 'cdpa' : The cItpAclCdpa, cItpAclCdpaMask, cItpAclCdpaSsn and cItpAclCdpaSsnMask are the relevant columns. The Called Party Point code is compared with cItpAclCcpa using the ItpAclCcpaMask. Also, the cItpAclCcpaSsn and cItpAclCcpaSsnMask are compared if specified. 'cdpaMask': Indicates that a mask is to be applied when the cdpa filter is specified. If the mask is not specified then the mask is assumed to be all zeros. 'cdpaSsn' : Indicates that a SSN is to be checked when the cdpa filter is specified. 'cdpaSsnMask': Indicates that SSN mask is to be applied when checking the SSN number for the cdpa filter is specified. If the mask is not specified then the mask is assumed to be all zeros. 'selector': The Global Title Selector is used to select which objects will be tested and in what order the tests will be applied as follows. x The types of translations are different based on the variant. In both, variants the translation type and other parameters are used to provide the following types of translations. - Intermediate GTT resulting in MSUs routed to a solitary point code - Intermediate GTT resulting in MSUs load balanced across two or more point codes - Final GTT routed to a solitary point code - Final GTT routed to a primary and backup point-code and SSN (dominant mode) - Final GTT load balanced across a group of point-codes and subsystems For ANSI the translation types are defined in TABLE B.1/T1.112.3 of TR-NWT-000246. The ANSI selector table may be a simple flat table/array of 256 Translation Types(0-255). In this method of translation tables can be directly accessed using the translation type from the Called Party Point Code. For ITU section 2.4.5 of ITU-T Q.714, defines the use of the Global Tile Indicator(GTI), along with Translation Type(TT), Network Plan(NP), and Nature of Address Indicator(NAI), as selectors for the table to perform the Global Title Translation(GTT). In this cae the selector table must be searched using a combination oF GTI, TT, NP and NAI. The objects cItpAclGtiSelector, cItpAclGtiTranslateType, cItpAclGtiNumberingPlan, cItpAclGtiNai, and cItpAclGtiEsv are the relevant columns. These object will be used in the following order based on variant and translation type. 1 => cItpAclGtiNai 2 => cItpAclGtiTranslateType 3 => cItpAclGtiTranslateType cItpAclGtiNumberingPlan cItpAclGtiEsv 4 => cItpAclGtiTranslateType cItpAclGtiNumberingPlan cItpAclGtiNai cItpAclGtiEsv 'aft' : The cItpAclAft, cItpAclAftMask, cItpAclAftSsn and cItpAclAftSsnMask are the relevant columns. The affected point code is compared with cItpAclAftPC using the ItpAclAftMask. Also, the cItpAclAftSsn and cItpAclAftSsnMask are compared if specified. 'aftMask': Indicates that a mask is to be applied when the aft filter is specified. If the mask is not specified then the mask is assumed to be all zeros. 'all' : Used in conjunction with cItpAclAction to specify defaults for packet that did not match any specified access list entry.

CItpTcPointCodeThe SS7 network node address as specified in the following references. The format of the Point code depends on the variant defined in the CgspSS7Variant object as follows. 33222222222211111111110000000000 10987654321098765432109876543210 ANSI: nnnnnnnn - Network cccccccc - Cluster mmmmmmmm - Member ITU: zzz - Zone aaaaaaaa - Area/Network iii - Identifier NTT: zzzzz - Zone aaaa - Area/Network iiiiiii - Identifier TTC: zzzzz - Zone aaaa - Area/Network iiiiiii - Identifier Note: The China variant has the same format as ANSI. This form of the point-code is not intended for for presentation.Reference: The SS7 network node address as specified in the International Telecommunication Union standard Q.708: Specifications of Signalling System No. 7 - Numbering of International Signalling Point Codes, and by ANSI T1.111.8 Numbering of Signalling Point Codes. GF 001-9001 - Technical Specifications of Signalling System No. 7 for National Telephone Network of China. (0..16777216) · Unsigned32

The destination point code specified for this ACL. The 'dpc' bit in the cItpAclParameters object is used indicate whether this object has been specified.

CItpTcPointCodeMaskA mask used to perform different operations on pointcodes.Reference: The SS7 network node address as specified in the International Telecommunication Union standard Q.708: Specifications of Signalling System No. 7 - Numbering of International Signalling Point Codes, and by ANSI T1.111.8 Numbering of Signalling Point Codes. (0..16777216) · Unsigned32

The mask used to define which part of the point code in the packet is significant when comparing the destination point code with cItpAclDpc. The 'dpcMask' bit in the cItpAclParameters object is used indicate whether this object has been specified.

CItpTcPointCodeThe SS7 network node address as specified in the following references. The format of the Point code depends on the variant defined in the CgspSS7Variant object as follows. 33222222222211111111110000000000 10987654321098765432109876543210 ANSI: nnnnnnnn - Network cccccccc - Cluster mmmmmmmm - Member ITU: zzz - Zone aaaaaaaa - Area/Network iii - Identifier NTT: zzzzz - Zone aaaa - Area/Network iiiiiii - Identifier TTC: zzzzz - Zone aaaa - Area/Network iiiiiii - Identifier Note: The China variant has the same format as ANSI. This form of the point-code is not intended for for presentation.Reference: The SS7 network node address as specified in the International Telecommunication Union standard Q.708: Specifications of Signalling System No. 7 - Numbering of International Signalling Point Codes, and by ANSI T1.111.8 Numbering of Signalling Point Codes. GF 001-9001 - Technical Specifications of Signalling System No. 7 for National Telephone Network of China. (0..16777216) · Unsigned32

The origin point code specified in this ACL. The 'opc' bit in the cItpAclParameters object is used indicate whether this object has been specified.

CItpTcPointCodeMaskA mask used to perform different operations on pointcodes.Reference: The SS7 network node address as specified in the International Telecommunication Union standard Q.708: Specifications of Signalling System No. 7 - Numbering of International Signalling Point Codes, and by ANSI T1.111.8 Numbering of Signalling Point Codes. (0..16777216) · Unsigned32

The mask used to define which part of the origin point code in the packet is significant when comparing the origin point code with cItpAclDpc. The 'opcMask' bit in the cItpAclParameters object is used indicate whether this object has been specified.

CItpTcServiceIndicator0 = snmm1 = sntm2 = spare23 = sccp4 = tup5 = isup6 = dupc7 = dupf8 = mtup9 = bisup10 = sisup11 = spare1112 = spare1213 = spare1314 = spare1415 = spare15The list of possible Service Indicator values. This identifies the type of SS7 packet. The service indicator codes for the international Signalling network are allocated as follows: 'SNMM' : Signalling network management messages (SNMM) 'SNTM' : Signalling network testing and maintenance messages (SNTM) 'Spare2' : Spare 2 'SCCP' : SCCP 'TUP' : Telephone User Part (TUP) 'ISUP' : ISDN User Part (ISUP) 'DUPC' : Data User Part, call and circuit-related messages (DUPC) 'DUPF' : Data User Part, facility registration and cancellation messages (DUPF) 'MTUP' : Reserved for MTP Testing User Part (MTUP) 'BISUP' : Broadband ISDN User Part (BISUP) 'SISUP' : Satellite ISDN User Part (SISUP) 'Spare11' : Spare 11 'Spare12' : Spare 12 'Spare13' : Spare 13 'Spare14' : Spare 14 'Spare15' : Spare 15Reference: ITU Q.704 Signalling network functions and messages section 14.2.1 Service indicator. · Integer32

The Service Indicator Octet. The 'si' bit in the cItpAclParameters object is used indicate whether this object has been specified.

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

The pattern used to match a packet at offset cItpAclOffset. The 'pattern' bit in the cItpAclParameters object is used indicate whether this object has been specified.

Unsigned32 (0..255)

The offset into the packet were we begin matching the pattern specified by cItpAclPattern is to start. The 'pattern' bit in the cItpAclParameters object is used indicate whether this object has been specified.

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

A brief description used to document access list entries. The 'comment' bit in the cItpAclParameters object is used indicate whether this object has been specified.

CItpTcPointCodeThe SS7 network node address as specified in the following references. The format of the Point code depends on the variant defined in the CgspSS7Variant object as follows. 33222222222211111111110000000000 10987654321098765432109876543210 ANSI: nnnnnnnn - Network cccccccc - Cluster mmmmmmmm - Member ITU: zzz - Zone aaaaaaaa - Area/Network iii - Identifier NTT: zzzzz - Zone aaaa - Area/Network iiiiiii - Identifier TTC: zzzzz - Zone aaaa - Area/Network iiiiiii - Identifier Note: The China variant has the same format as ANSI. This form of the point-code is not intended for for presentation.Reference: The SS7 network node address as specified in the International Telecommunication Union standard Q.708: Specifications of Signalling System No. 7 - Numbering of International Signalling Point Codes, and by ANSI T1.111.8 Numbering of Signalling Point Codes. GF 001-9001 - Technical Specifications of Signalling System No. 7 for National Telephone Network of China. (0..16777216) · Unsigned32

The Calling Party Point Code. The 'cgpa' bit in the cItpAclParameters object is used indicate whether this object has been specified.

CItpTcPointCodeMaskA mask used to perform different operations on pointcodes.Reference: The SS7 network node address as specified in the International Telecommunication Union standard Q.708: Specifications of Signalling System No. 7 - Numbering of International Signalling Point Codes, and by ANSI T1.111.8 Numbering of Signalling Point Codes. (0..16777216) · Unsigned32

The Calling Party Point Code mask. The 'cgpaMask' bit in the cItpAclParameters object is used indicate whether this object has been specified.

CItpTcSubSystemNumberThe SCCP Subsystem Number . A value of zero indicates that a subsystem is not specified. (0 | 2..255) · Unsigned32

The Calling Party Point Code subsystem number. The 'cgpa' bit in the cItpAclParameters object is used indicate whether this object has been specified.

CItpTcSubSystemNumberMaskThe SCCP Subsystem Number Mask. (2..255) · Unsigned32

The Calling Party Point Code subsystem number Mask. The 'cgpa' bit in the cItpAclParameters object is used indicate whether this object has been specified.

CItpTcPointCodeThe SS7 network node address as specified in the following references. The format of the Point code depends on the variant defined in the CgspSS7Variant object as follows. 33222222222211111111110000000000 10987654321098765432109876543210 ANSI: nnnnnnnn - Network cccccccc - Cluster mmmmmmmm - Member ITU: zzz - Zone aaaaaaaa - Area/Network iii - Identifier NTT: zzzzz - Zone aaaa - Area/Network iiiiiii - Identifier TTC: zzzzz - Zone aaaa - Area/Network iiiiiii - Identifier Note: The China variant has the same format as ANSI. This form of the point-code is not intended for for presentation.Reference: The SS7 network node address as specified in the International Telecommunication Union standard Q.708: Specifications of Signalling System No. 7 - Numbering of International Signalling Point Codes, and by ANSI T1.111.8 Numbering of Signalling Point Codes. GF 001-9001 - Technical Specifications of Signalling System No. 7 for National Telephone Network of China. (0..16777216) · Unsigned32

The Called Party Point Code. The 'cdpa' bit in the cItpAclParameters object is used indicate whether this object has been specified.

CItpTcPointCodeMaskA mask used to perform different operations on pointcodes.Reference: The SS7 network node address as specified in the International Telecommunication Union standard Q.708: Specifications of Signalling System No. 7 - Numbering of International Signalling Point Codes, and by ANSI T1.111.8 Numbering of Signalling Point Codes. (0..16777216) · Unsigned32

The Called Party Point Code mask. The 'cdpaMask' bit in the cItpAclParameters object is used indicate whether this object has been specified.

CItpTcSubSystemNumberThe SCCP Subsystem Number . A value of zero indicates that a subsystem is not specified. (0 | 2..255) · Unsigned32

The Called Party Point Code subsystem number. The 'cdpa' bit in the cItpAclParameters object is used indicate whether this object has been specified.

CItpTcSubSystemNumberMaskThe SCCP Subsystem Number Mask. (2..255) · Unsigned32

The Called Party Point Code subsystem number Mask. The 'cdpa' bit in the cItpAclParameters object is used indicate whether this object has been specified.

CItpTcGlobalTitleSelector1 = nai2 = tt3 = ttNpEs4 = ttNpNaiEsGlobal Title Selector. 'nai' : Global title translation based on nature of address indicator. 'tt' : Global title translation based on translation type. 'ttNpEs' : Global title translation based on translation type, numbering plan value and Encoding Scheme Value. 'ttNpNaiEs' : Global title translation based on translation type, numbering plan, value, nature of address indicator and encoding scheme value. · Integer32

The Global Title Selector. The 'selector' bit in the cItpAclParameters object is used indicate whether this object has been specified.

CItpTcTranslationType1 = tt2 = ssnThe Translation Type for SCCP GTT GTA specifies Title Translation or Subsystem Number (SSN) 'tt' : The GTT GTA has specified Title Translation 'ssn' : The GTT GTA has specified Subsystem Number. · Integer32

The Global Title Translate Type. The 'selector' bit in the cItpAclParameters object is used indicate whether this object has been specified.

CItpTcNumberingPlanThe SCCP GTT Numbering Plan (NP). The following values are generally used: Unknown NP (0), ISDN/Telephony NP (1), Spare (2), Data NP (3), Telex NP (4), Maritime Mobile NP (5), Land Mobile NP (6), ISDN/Mobile NP (7), Private NP (8). Max NP (15), Invalid NP (253), Wild NP (254). (0..255) · Integer32

The Global Title Numbering Plan. The 'selector' bit in the cItpAclParameters object is used indicate whether this object has been specified.

CItpTcNAIThe SCCP GTT Network Address Indicator (NAI). The following values are generally used: Unknown Nature of Address (0), Subscriber Number (1), Reserved for national use (2), National Significant Number (3), International Number (4), Maximum NAI (127), Invalid NAI (253), Wild NAI (254). (0..255) · Integer32

The Global Title nature of address indicator. The 'selector' bit in the cItpAclParameters object is used indicate whether this object has been specified.

CItpTcEncodingSchemeValueThe encoding scheme value. (0..15) · Integer32

The Global Title encoding scheme value. The 'selector' bit in the cItpAclParameters object is used indicate whether this object has been specified.

CItpTcPointCodeThe SS7 network node address as specified in the following references. The format of the Point code depends on the variant defined in the CgspSS7Variant object as follows. 33222222222211111111110000000000 10987654321098765432109876543210 ANSI: nnnnnnnn - Network cccccccc - Cluster mmmmmmmm - Member ITU: zzz - Zone aaaaaaaa - Area/Network iii - Identifier NTT: zzzzz - Zone aaaa - Area/Network iiiiiii - Identifier TTC: zzzzz - Zone aaaa - Area/Network iiiiiii - Identifier Note: The China variant has the same format as ANSI. This form of the point-code is not intended for for presentation.Reference: The SS7 network node address as specified in the International Telecommunication Union standard Q.708: Specifications of Signalling System No. 7 - Numbering of International Signalling Point Codes, and by ANSI T1.111.8 Numbering of Signalling Point Codes. GF 001-9001 - Technical Specifications of Signalling System No. 7 for National Telephone Network of China. (0..16777216) · Unsigned32

The Affected Point Code. The 'aft' bit in the cItpAclParameters object is used indicate whether this object has been specified.

CItpTcPointCodeMaskA mask used to perform different operations on pointcodes.Reference: The SS7 network node address as specified in the International Telecommunication Union standard Q.708: Specifications of Signalling System No. 7 - Numbering of International Signalling Point Codes, and by ANSI T1.111.8 Numbering of Signalling Point Codes. (0..16777216) · Unsigned32

The Affected Point Code mask. The 'aftMask' bit in the cItpAclParameters object is used indicate whether this object has been specified.

CItpTcSubSystemNumberThe SCCP Subsystem Number . A value of zero indicates that a subsystem is not specified. (0 | 2..255) · Unsigned32

The Affected Point Code subsystem number. The 'aft' bit in the cItpAclParameters object is used indicate whether this object has been specified.

CItpTcSubSystemNumberMaskThe SCCP Subsystem Number Mask. (2..255) · Unsigned32

The Affected Point Code subsystem number Mask. The 'aft' bit in the cItpAclParameters object is used indicate whether this object has been specified.

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

The object is used by a management station to create or delete the row entry in cItpAcl following the RowStatus textual convention.