EZ5 MIB Catalog

CISCO-FIREPOWER-AP-CALLHOME-MIB

2023-01-25

MIB representation of the Cisco Firepower CALLHOME management information model package

Download CISCO-FIREPOWER-AP-CALLHOME-MIB.txt Open CISCO-FIREPOWER-AP-CALLHOME-MIB.txt in a new tab

TABLES (13)

Tables (13)

NameOID
cfprApCallhomeAnonymousReportingTable1.3.6.1.4.1.9.9.826.2.1.7.1
cfprApCallhomeDestTable1.3.6.1.4.1.9.9.826.2.1.7.2
cfprApCallhomeEpTable1.3.6.1.4.1.9.9.826.2.1.7.3
cfprApCallhomeEpFsmTable1.3.6.1.4.1.9.9.826.2.1.7.4
cfprApCallhomeEpFsmStageTable1.3.6.1.4.1.9.9.826.2.1.7.5
cfprApCallhomeEpFsmTaskTable1.3.6.1.4.1.9.9.826.2.1.7.6
cfprApCallhomeHttpProxyTable1.3.6.1.4.1.9.9.826.2.1.7.7
cfprApCallhomePeriodicSystemInventoryTable1.3.6.1.4.1.9.9.826.2.1.7.8
cfprApCallhomePolicyTable1.3.6.1.4.1.9.9.826.2.1.7.9
cfprApCallhomeProfileTable1.3.6.1.4.1.9.9.826.2.1.7.10
cfprApCallhomeSmtpTable1.3.6.1.4.1.9.9.826.2.1.7.11
cfprApCallhomeSourceTable1.3.6.1.4.1.9.9.826.2.1.7.12
cfprApCallhomeTestAlertTable1.3.6.1.4.1.9.9.826.2.1.7.13

END OF TOC

Table details

cfprApCallhomeAnonymousReportingTable

1.3.6.1.4.1.9.9.826.2.1.7.1

Index: cfprApCallhomeAnonymousReportingInstanceId

Cisco Firepower callhome:AnonymousReporting managed object table

cfprApCallhomeAnonymousReportingInstanceId

1.3.6.1.4.1.9.9.826.2.1.7.1.1.1

CfprApManagedObjectIdA unique identifier for this managed object. Objects in FPR Manager are stored in a Management Information Tree (MIT). The MIT is a repository of all Managed Object (MO) instances, indexed by their Distinguished Name (DN). The MIT somewhat resembles a file structure - going from main folder to the next lowest folder, and so on, until the full path to a MO is established. Every object in FPR Manager has two unique identifiers: 1) A distinguished name (DN). A DN provides a fully-qualified path from the top of the object tree. It is built as an ordered sequence of relative names separated by the '/' character. The DN is used to identify objects in the XML API. 2) A CfprApManagedObjectId, which is an integer uniquely identifying an object. The CfprApManagedObjectId is used to identify objects and traverse tables when using the SNMP protocol. For example, an object representing a network adaptor on a blade might be identified with its DN set to 'sys/chassis-5/blade-2/adaptor-1' and its CfprApManagedObjectId set to '13203'. · Unsigned32 · hint d

Instance identifier of the managed object.

cfprApCallhomeAnonymousReportingDn

1.3.6.1.4.1.9.9.826.2.1.7.1.1.2

CfprApManagedObjectDnAn immutable property of all Managed Objects (MO) that provides a fully qualified and unambiguous name for the MO. A DN provides a fully-qualified path from the top of the object tree. It is built as an ordered sequence of relative names separated by the '/' character. For example, an object representing a network adaptor on a blade might be identified with its DN set to 'sys/chassis-5/blade-2/adaptor-1'. · OCTET STRING

Cisco Firepower callhome:AnonymousReporting:dn managed object property

cfprApCallhomeAnonymousReportingRn

1.3.6.1.4.1.9.9.826.2.1.7.1.1.3

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

Cisco Firepower callhome:AnonymousReporting:rn managed object property

cfprApCallhomeAnonymousReportingAdminState

1.3.6.1.4.1.9.9.826.2.1.7.1.1.4

CfprApCallhomeAnonymousReportingAdminState0 = off1 = on · Integer32

Cisco Firepower callhome:AnonymousReporting:adminState managed object property

cfprApCallhomeAnonymousReportingCount

1.3.6.1.4.1.9.9.826.2.1.7.1.1.5

Gauge32

Cisco Firepower callhome:AnonymousReporting:count managed object property

cfprApCallhomeAnonymousReportingSleepInterval

1.3.6.1.4.1.9.9.826.2.1.7.1.1.6

Gauge32

Cisco Firepower callhome:AnonymousReporting:sleepInterval managed object property

cfprApCallhomeAnonymousReportingUserAcknowledged

1.3.6.1.4.1.9.9.826.2.1.7.1.1.7

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

Cisco Firepower callhome:AnonymousReporting:userAcknowledged managed object property

cfprApCallhomeDestTable

1.3.6.1.4.1.9.9.826.2.1.7.2

Index: cfprApCallhomeDestInstanceId

Cisco Firepower callhome:Dest managed object table

cfprApCallhomeDestInstanceId

1.3.6.1.4.1.9.9.826.2.1.7.2.1.1

CfprApManagedObjectIdA unique identifier for this managed object. Objects in FPR Manager are stored in a Management Information Tree (MIT). The MIT is a repository of all Managed Object (MO) instances, indexed by their Distinguished Name (DN). The MIT somewhat resembles a file structure - going from main folder to the next lowest folder, and so on, until the full path to a MO is established. Every object in FPR Manager has two unique identifiers: 1) A distinguished name (DN). A DN provides a fully-qualified path from the top of the object tree. It is built as an ordered sequence of relative names separated by the '/' character. The DN is used to identify objects in the XML API. 2) A CfprApManagedObjectId, which is an integer uniquely identifying an object. The CfprApManagedObjectId is used to identify objects and traverse tables when using the SNMP protocol. For example, an object representing a network adaptor on a blade might be identified with its DN set to 'sys/chassis-5/blade-2/adaptor-1' and its CfprApManagedObjectId set to '13203'. · Unsigned32 · hint d

Instance identifier of the managed object.

cfprApCallhomeDestDn

1.3.6.1.4.1.9.9.826.2.1.7.2.1.2

CfprApManagedObjectDnAn immutable property of all Managed Objects (MO) that provides a fully qualified and unambiguous name for the MO. A DN provides a fully-qualified path from the top of the object tree. It is built as an ordered sequence of relative names separated by the '/' character. For example, an object representing a network adaptor on a blade might be identified with its DN set to 'sys/chassis-5/blade-2/adaptor-1'. · OCTET STRING

Cisco Firepower callhome:Dest:dn managed object property

cfprApCallhomeDestRn

1.3.6.1.4.1.9.9.826.2.1.7.2.1.3

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

Cisco Firepower callhome:Dest:rn managed object property

cfprApCallhomeDestAddress

1.3.6.1.4.1.9.9.826.2.1.7.2.1.4

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

Cisco Firepower callhome:Dest:address managed object property

cfprApCallhomeDestName

1.3.6.1.4.1.9.9.826.2.1.7.2.1.5

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

Cisco Firepower callhome:Dest:name managed object property

cfprApCallhomeDestProtocol

1.3.6.1.4.1.9.9.826.2.1.7.2.1.6

CfprApCallhomeCallhomeProtocol0 = email1 = https2 = http · Integer32

Cisco Firepower callhome:Dest:protocol managed object property

cfprApCallhomeEpTable

1.3.6.1.4.1.9.9.826.2.1.7.3

Index: cfprApCallhomeEpInstanceId

Cisco Firepower callhome:Ep managed object table

cfprApCallhomeEpInstanceId

1.3.6.1.4.1.9.9.826.2.1.7.3.1.1

CfprApManagedObjectIdA unique identifier for this managed object. Objects in FPR Manager are stored in a Management Information Tree (MIT). The MIT is a repository of all Managed Object (MO) instances, indexed by their Distinguished Name (DN). The MIT somewhat resembles a file structure - going from main folder to the next lowest folder, and so on, until the full path to a MO is established. Every object in FPR Manager has two unique identifiers: 1) A distinguished name (DN). A DN provides a fully-qualified path from the top of the object tree. It is built as an ordered sequence of relative names separated by the '/' character. The DN is used to identify objects in the XML API. 2) A CfprApManagedObjectId, which is an integer uniquely identifying an object. The CfprApManagedObjectId is used to identify objects and traverse tables when using the SNMP protocol. For example, an object representing a network adaptor on a blade might be identified with its DN set to 'sys/chassis-5/blade-2/adaptor-1' and its CfprApManagedObjectId set to '13203'. · Unsigned32 · hint d

Instance identifier of the managed object.

cfprApCallhomeEpDn

1.3.6.1.4.1.9.9.826.2.1.7.3.1.2

CfprApManagedObjectDnAn immutable property of all Managed Objects (MO) that provides a fully qualified and unambiguous name for the MO. A DN provides a fully-qualified path from the top of the object tree. It is built as an ordered sequence of relative names separated by the '/' character. For example, an object representing a network adaptor on a blade might be identified with its DN set to 'sys/chassis-5/blade-2/adaptor-1'. · OCTET STRING

Cisco Firepower callhome:Ep:dn managed object property

cfprApCallhomeEpRn

1.3.6.1.4.1.9.9.826.2.1.7.3.1.3

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

Cisco Firepower callhome:Ep:rn managed object property

cfprApCallhomeEpAdminState

1.3.6.1.4.1.9.9.826.2.1.7.3.1.4

CfprApCallhomeAdminState0 = off1 = on · Integer32

Cisco Firepower callhome:Ep:adminState managed object property

cfprApCallhomeEpAlertThrottlingAdminState

1.3.6.1.4.1.9.9.826.2.1.7.3.1.5

CfprApCallhomeAlertThrottlingAdminState0 = off1 = on · Integer32

Cisco Firepower callhome:Ep:alertThrottlingAdminState managed object property

cfprApCallhomeEpConfigState

1.3.6.1.4.1.9.9.826.2.1.7.3.1.6

CfprApCallhomeEpConfigState0 = ok1 = notApplied · Integer32

Cisco Firepower callhome:Ep:configState managed object property

cfprApCallhomeEpDescr

1.3.6.1.4.1.9.9.826.2.1.7.3.1.7

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

Cisco Firepower callhome:Ep:descr managed object property

cfprApCallhomeEpFsmDescr

1.3.6.1.4.1.9.9.826.2.1.7.3.1.8

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

Cisco Firepower callhome:Ep:fsmDescr managed object property

cfprApCallhomeEpFsmPrev

1.3.6.1.4.1.9.9.826.2.1.7.3.1.9

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

Cisco Firepower callhome:Ep:fsmPrev managed object property

cfprApCallhomeEpFsmProgr

1.3.6.1.4.1.9.9.826.2.1.7.3.1.10

Gauge32

Cisco Firepower callhome:Ep:fsmProgr managed object property

cfprApCallhomeEpFsmRmtInvErrCode

1.3.6.1.4.1.9.9.826.2.1.7.3.1.11

Gauge32

Cisco Firepower callhome:Ep:fsmRmtInvErrCode managed object property

cfprApCallhomeEpFsmRmtInvErrDescr

1.3.6.1.4.1.9.9.826.2.1.7.3.1.12

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

Cisco Firepower callhome:Ep:fsmRmtInvErrDescr managed object property

cfprApCallhomeEpFsmRmtInvRslt

1.3.6.1.4.1.9.9.826.2.1.7.3.1.13

CfprApConditionRemoteInvRslt · BITS

Cisco Firepower callhome:Ep:fsmRmtInvRslt managed object property

cfprApCallhomeEpFsmStageDescr

1.3.6.1.4.1.9.9.826.2.1.7.3.1.14

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

Cisco Firepower callhome:Ep:fsmStageDescr managed object property

cfprApCallhomeEpFsmStamp

1.3.6.1.4.1.9.9.826.2.1.7.3.1.15

DateAndTimeA date-time specification. field octets contents range ----- ------ -------- ----- 1 1-2 year* 0..65536 2 3 month 1..12 3 4 day 1..31 4 5 hour 0..23 5 6 minutes 0..59 6 7 seconds 0..60 (use 60 for leap-second) 7 8 deci-seconds 0..9 8 9 direction from UTC '+' / '-' 9 10 hours from UTC* 0..13 10 11 minutes from UTC 0..59 * Notes: - the value of year is in network-byte order - daylight saving time in New Zealand is +13 For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as: 1992-5-26,13:30:15.0,-4:0 Note that if only local time is known, then timezone information (fields 8-10) is not present. SIZE (8 | 11) · OCTET STRING · hint 2d-1d-1d,1d:1d:1d.1d,1a1d:1d

Cisco Firepower callhome:Ep:fsmStamp managed object property

cfprApCallhomeEpFsmStatus

1.3.6.1.4.1.9.9.826.2.1.7.3.1.16

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

Cisco Firepower callhome:Ep:fsmStatus managed object property

cfprApCallhomeEpFsmTry

1.3.6.1.4.1.9.9.826.2.1.7.3.1.17

Gauge32

Cisco Firepower callhome:Ep:fsmTry managed object property

cfprApCallhomeEpIntId

1.3.6.1.4.1.9.9.826.2.1.7.3.1.18

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

Cisco Firepower callhome:Ep:intId managed object property

cfprApCallhomeEpName

1.3.6.1.4.1.9.9.826.2.1.7.3.1.19

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

Cisco Firepower callhome:Ep:name managed object property

cfprApCallhomeEpPolicyLevel

1.3.6.1.4.1.9.9.826.2.1.7.3.1.20

Gauge32

Cisco Firepower callhome:Ep:policyLevel managed object property

cfprApCallhomeEpPolicyOwner

1.3.6.1.4.1.9.9.826.2.1.7.3.1.21

CfprApPolicyPolicyOwner0 = local1 = policy2 = pendingPolicy · Integer32

Cisco Firepower callhome:Ep:policyOwner managed object property

cfprApCallhomeEpFsmTable

1.3.6.1.4.1.9.9.826.2.1.7.4

Index: cfprApCallhomeEpFsmInstanceId

Cisco Firepower callhome:EpFsm managed object table

cfprApCallhomeEpFsmInstanceId

1.3.6.1.4.1.9.9.826.2.1.7.4.1.1

CfprApManagedObjectIdA unique identifier for this managed object. Objects in FPR Manager are stored in a Management Information Tree (MIT). The MIT is a repository of all Managed Object (MO) instances, indexed by their Distinguished Name (DN). The MIT somewhat resembles a file structure - going from main folder to the next lowest folder, and so on, until the full path to a MO is established. Every object in FPR Manager has two unique identifiers: 1) A distinguished name (DN). A DN provides a fully-qualified path from the top of the object tree. It is built as an ordered sequence of relative names separated by the '/' character. The DN is used to identify objects in the XML API. 2) A CfprApManagedObjectId, which is an integer uniquely identifying an object. The CfprApManagedObjectId is used to identify objects and traverse tables when using the SNMP protocol. For example, an object representing a network adaptor on a blade might be identified with its DN set to 'sys/chassis-5/blade-2/adaptor-1' and its CfprApManagedObjectId set to '13203'. · Unsigned32 · hint d

Instance identifier of the managed object.

cfprApCallhomeEpFsmDn

1.3.6.1.4.1.9.9.826.2.1.7.4.1.2

CfprApManagedObjectDnAn immutable property of all Managed Objects (MO) that provides a fully qualified and unambiguous name for the MO. A DN provides a fully-qualified path from the top of the object tree. It is built as an ordered sequence of relative names separated by the '/' character. For example, an object representing a network adaptor on a blade might be identified with its DN set to 'sys/chassis-5/blade-2/adaptor-1'. · OCTET STRING

Cisco Firepower callhome:EpFsm:dn managed object property

cfprApCallhomeEpFsmRn

1.3.6.1.4.1.9.9.826.2.1.7.4.1.3

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

Cisco Firepower callhome:EpFsm:rn managed object property

cfprApCallhomeEpFsmCompletionTime

1.3.6.1.4.1.9.9.826.2.1.7.4.1.4

DateAndTimeA date-time specification. field octets contents range ----- ------ -------- ----- 1 1-2 year* 0..65536 2 3 month 1..12 3 4 day 1..31 4 5 hour 0..23 5 6 minutes 0..59 6 7 seconds 0..60 (use 60 for leap-second) 7 8 deci-seconds 0..9 8 9 direction from UTC '+' / '-' 9 10 hours from UTC* 0..13 10 11 minutes from UTC 0..59 * Notes: - the value of year is in network-byte order - daylight saving time in New Zealand is +13 For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as: 1992-5-26,13:30:15.0,-4:0 Note that if only local time is known, then timezone information (fields 8-10) is not present. SIZE (8 | 11) · OCTET STRING · hint 2d-1d-1d,1d:1d:1d.1d,1a1d:1d

Cisco Firepower callhome:EpFsm:completionTime managed object property

cfprApCallhomeEpFsmCurrentFsm

1.3.6.1.4.1.9.9.826.2.1.7.4.1.5

CfprApCallhomeEpFsmCurrentFsm0 = nop124 = configCallhome · Integer32

Cisco Firepower callhome:EpFsm:currentFsm managed object property

cfprApCallhomeEpFsmDescrData

1.3.6.1.4.1.9.9.826.2.1.7.4.1.6

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

Cisco Firepower callhome:EpFsm:descr managed object property

cfprApCallhomeEpFsmFsmStatus

1.3.6.1.4.1.9.9.826.2.1.7.4.1.7

CfprApFsmFsmStageStatus0 = fail1 = success2 = skip3 = pending4 = inProgress5 = throttled255 = nop · Integer32

Cisco Firepower callhome:EpFsm:fsmStatus managed object property

cfprApCallhomeEpFsmProgress

1.3.6.1.4.1.9.9.826.2.1.7.4.1.8

Gauge32

Cisco Firepower callhome:EpFsm:progress managed object property

cfprApCallhomeEpFsmRmtErrCode

1.3.6.1.4.1.9.9.826.2.1.7.4.1.9

Gauge32

Cisco Firepower callhome:EpFsm:rmtErrCode managed object property

cfprApCallhomeEpFsmRmtErrDescr

1.3.6.1.4.1.9.9.826.2.1.7.4.1.10

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

Cisco Firepower callhome:EpFsm:rmtErrDescr managed object property

cfprApCallhomeEpFsmRmtRslt

1.3.6.1.4.1.9.9.826.2.1.7.4.1.11

CfprApConditionRemoteInvRslt · BITS

Cisco Firepower callhome:EpFsm:rmtRslt managed object property

cfprApCallhomeEpFsmStageTable

1.3.6.1.4.1.9.9.826.2.1.7.5

Index: cfprApCallhomeEpFsmStageInstanceId

Cisco Firepower callhome:EpFsmStage managed object table

cfprApCallhomeEpFsmStageInstanceId

1.3.6.1.4.1.9.9.826.2.1.7.5.1.1

CfprApManagedObjectIdA unique identifier for this managed object. Objects in FPR Manager are stored in a Management Information Tree (MIT). The MIT is a repository of all Managed Object (MO) instances, indexed by their Distinguished Name (DN). The MIT somewhat resembles a file structure - going from main folder to the next lowest folder, and so on, until the full path to a MO is established. Every object in FPR Manager has two unique identifiers: 1) A distinguished name (DN). A DN provides a fully-qualified path from the top of the object tree. It is built as an ordered sequence of relative names separated by the '/' character. The DN is used to identify objects in the XML API. 2) A CfprApManagedObjectId, which is an integer uniquely identifying an object. The CfprApManagedObjectId is used to identify objects and traverse tables when using the SNMP protocol. For example, an object representing a network adaptor on a blade might be identified with its DN set to 'sys/chassis-5/blade-2/adaptor-1' and its CfprApManagedObjectId set to '13203'. · Unsigned32 · hint d

Instance identifier of the managed object.

cfprApCallhomeEpFsmStageDn

1.3.6.1.4.1.9.9.826.2.1.7.5.1.2

CfprApManagedObjectDnAn immutable property of all Managed Objects (MO) that provides a fully qualified and unambiguous name for the MO. A DN provides a fully-qualified path from the top of the object tree. It is built as an ordered sequence of relative names separated by the '/' character. For example, an object representing a network adaptor on a blade might be identified with its DN set to 'sys/chassis-5/blade-2/adaptor-1'. · OCTET STRING

Cisco Firepower callhome:EpFsmStage:dn managed object property

cfprApCallhomeEpFsmStageRn

1.3.6.1.4.1.9.9.826.2.1.7.5.1.3

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

Cisco Firepower callhome:EpFsmStage:rn managed object property

cfprApCallhomeEpFsmStageDescrData

1.3.6.1.4.1.9.9.826.2.1.7.5.1.4

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

Cisco Firepower callhome:EpFsmStage:descr managed object property

cfprApCallhomeEpFsmStageLastUpdateTime

1.3.6.1.4.1.9.9.826.2.1.7.5.1.5

DateAndTimeA date-time specification. field octets contents range ----- ------ -------- ----- 1 1-2 year* 0..65536 2 3 month 1..12 3 4 day 1..31 4 5 hour 0..23 5 6 minutes 0..59 6 7 seconds 0..60 (use 60 for leap-second) 7 8 deci-seconds 0..9 8 9 direction from UTC '+' / '-' 9 10 hours from UTC* 0..13 10 11 minutes from UTC 0..59 * Notes: - the value of year is in network-byte order - daylight saving time in New Zealand is +13 For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as: 1992-5-26,13:30:15.0,-4:0 Note that if only local time is known, then timezone information (fields 8-10) is not present. SIZE (8 | 11) · OCTET STRING · hint 2d-1d-1d,1d:1d:1d.1d,1a1d:1d

Cisco Firepower callhome:EpFsmStage:lastUpdateTime managed object property

cfprApCallhomeEpFsmStageName

1.3.6.1.4.1.9.9.826.2.1.7.5.1.6

CfprApCallhomeEpFsmStageName0 = nop124 = configCallhomeBegin125 = configCallhomeSetLocal126 = configCallhomeSetPeer550 = configCallhomeFail551 = configCallhomeSuccess · Integer32

Cisco Firepower callhome:EpFsmStage:name managed object property

cfprApCallhomeEpFsmStageOrder

1.3.6.1.4.1.9.9.826.2.1.7.5.1.7

Gauge32

Cisco Firepower callhome:EpFsmStage:order managed object property

cfprApCallhomeEpFsmStageRetry

1.3.6.1.4.1.9.9.826.2.1.7.5.1.8

Gauge32

Cisco Firepower callhome:EpFsmStage:retry managed object property

cfprApCallhomeEpFsmStageStageStatus

1.3.6.1.4.1.9.9.826.2.1.7.5.1.9

CfprApFsmFsmStageStatus0 = fail1 = success2 = skip3 = pending4 = inProgress5 = throttled255 = nop · Integer32

Cisco Firepower callhome:EpFsmStage:stageStatus managed object property

cfprApCallhomeEpFsmTaskTable

1.3.6.1.4.1.9.9.826.2.1.7.6

Index: cfprApCallhomeEpFsmTaskInstanceId

Cisco Firepower callhome:EpFsmTask managed object table

cfprApCallhomeEpFsmTaskInstanceId

1.3.6.1.4.1.9.9.826.2.1.7.6.1.1

CfprApManagedObjectIdA unique identifier for this managed object. Objects in FPR Manager are stored in a Management Information Tree (MIT). The MIT is a repository of all Managed Object (MO) instances, indexed by their Distinguished Name (DN). The MIT somewhat resembles a file structure - going from main folder to the next lowest folder, and so on, until the full path to a MO is established. Every object in FPR Manager has two unique identifiers: 1) A distinguished name (DN). A DN provides a fully-qualified path from the top of the object tree. It is built as an ordered sequence of relative names separated by the '/' character. The DN is used to identify objects in the XML API. 2) A CfprApManagedObjectId, which is an integer uniquely identifying an object. The CfprApManagedObjectId is used to identify objects and traverse tables when using the SNMP protocol. For example, an object representing a network adaptor on a blade might be identified with its DN set to 'sys/chassis-5/blade-2/adaptor-1' and its CfprApManagedObjectId set to '13203'. · Unsigned32 · hint d

Instance identifier of the managed object.

cfprApCallhomeEpFsmTaskDn

1.3.6.1.4.1.9.9.826.2.1.7.6.1.2

CfprApManagedObjectDnAn immutable property of all Managed Objects (MO) that provides a fully qualified and unambiguous name for the MO. A DN provides a fully-qualified path from the top of the object tree. It is built as an ordered sequence of relative names separated by the '/' character. For example, an object representing a network adaptor on a blade might be identified with its DN set to 'sys/chassis-5/blade-2/adaptor-1'. · OCTET STRING

Cisco Firepower callhome:EpFsmTask:dn managed object property

cfprApCallhomeEpFsmTaskRn

1.3.6.1.4.1.9.9.826.2.1.7.6.1.3

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

Cisco Firepower callhome:EpFsmTask:rn managed object property

cfprApCallhomeEpFsmTaskCompletion

1.3.6.1.4.1.9.9.826.2.1.7.6.1.4

CfprApFsmCompletion0 = scheduled1 = processing2 = completed3 = cancelled · Integer32

Cisco Firepower callhome:EpFsmTask:completion managed object property

cfprApCallhomeEpFsmTaskFlags

1.3.6.1.4.1.9.9.826.2.1.7.6.1.5

CfprApFsmFlags · BITS

Cisco Firepower callhome:EpFsmTask:flags managed object property

cfprApCallhomeEpFsmTaskItem

1.3.6.1.4.1.9.9.826.2.1.7.6.1.6

CfprApCallhomeEpFsmTaskItem0 = nop124 = configCallhome · Integer32

Cisco Firepower callhome:EpFsmTask:item managed object property

cfprApCallhomeEpFsmTaskSeqId

1.3.6.1.4.1.9.9.826.2.1.7.6.1.7

Gauge32

Cisco Firepower callhome:EpFsmTask:seqId managed object property

cfprApCallhomeHttpProxyTable

1.3.6.1.4.1.9.9.826.2.1.7.7

Index: cfprApCallhomeHttpProxyInstanceId

Cisco Firepower callhome:HttpProxy managed object table

cfprApCallhomeHttpProxyInstanceId

1.3.6.1.4.1.9.9.826.2.1.7.7.1.1

CfprApManagedObjectIdA unique identifier for this managed object. Objects in FPR Manager are stored in a Management Information Tree (MIT). The MIT is a repository of all Managed Object (MO) instances, indexed by their Distinguished Name (DN). The MIT somewhat resembles a file structure - going from main folder to the next lowest folder, and so on, until the full path to a MO is established. Every object in FPR Manager has two unique identifiers: 1) A distinguished name (DN). A DN provides a fully-qualified path from the top of the object tree. It is built as an ordered sequence of relative names separated by the '/' character. The DN is used to identify objects in the XML API. 2) A CfprApManagedObjectId, which is an integer uniquely identifying an object. The CfprApManagedObjectId is used to identify objects and traverse tables when using the SNMP protocol. For example, an object representing a network adaptor on a blade might be identified with its DN set to 'sys/chassis-5/blade-2/adaptor-1' and its CfprApManagedObjectId set to '13203'. · Unsigned32 · hint d

Instance identifier of the managed object.

cfprApCallhomeHttpProxyDn

1.3.6.1.4.1.9.9.826.2.1.7.7.1.2

CfprApManagedObjectDnAn immutable property of all Managed Objects (MO) that provides a fully qualified and unambiguous name for the MO. A DN provides a fully-qualified path from the top of the object tree. It is built as an ordered sequence of relative names separated by the '/' character. For example, an object representing a network adaptor on a blade might be identified with its DN set to 'sys/chassis-5/blade-2/adaptor-1'. · OCTET STRING

Cisco Firepower callhome:HttpProxy:dn managed object property

cfprApCallhomeHttpProxyRn

1.3.6.1.4.1.9.9.826.2.1.7.7.1.3

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

Cisco Firepower callhome:HttpProxy:rn managed object property

cfprApCallhomeHttpProxyProxyServerEnable

1.3.6.1.4.1.9.9.826.2.1.7.7.1.4

CfprApCallhomeHttpProxyEnable0 = off1 = on · Integer32

Cisco Firepower callhome:HttpProxy:proxyServerEnable managed object property

cfprApCallhomeHttpProxyProxyServerPort

1.3.6.1.4.1.9.9.826.2.1.7.7.1.5

Gauge32

Cisco Firepower callhome:HttpProxy:proxyServerPort managed object property

cfprApCallhomeHttpProxyProxyServerUrl

1.3.6.1.4.1.9.9.826.2.1.7.7.1.6

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

Cisco Firepower callhome:HttpProxy:proxyServerUrl managed object property

cfprApCallhomePeriodicSystemInventoryTable

1.3.6.1.4.1.9.9.826.2.1.7.8

Index: cfprApCallhomePeriodicSystemInventoryInstanceId

Cisco Firepower callhome:PeriodicSystemInventory managed object table

cfprApCallhomePeriodicSystemInventoryInstanceId

1.3.6.1.4.1.9.9.826.2.1.7.8.1.1

CfprApManagedObjectIdA unique identifier for this managed object. Objects in FPR Manager are stored in a Management Information Tree (MIT). The MIT is a repository of all Managed Object (MO) instances, indexed by their Distinguished Name (DN). The MIT somewhat resembles a file structure - going from main folder to the next lowest folder, and so on, until the full path to a MO is established. Every object in FPR Manager has two unique identifiers: 1) A distinguished name (DN). A DN provides a fully-qualified path from the top of the object tree. It is built as an ordered sequence of relative names separated by the '/' character. The DN is used to identify objects in the XML API. 2) A CfprApManagedObjectId, which is an integer uniquely identifying an object. The CfprApManagedObjectId is used to identify objects and traverse tables when using the SNMP protocol. For example, an object representing a network adaptor on a blade might be identified with its DN set to 'sys/chassis-5/blade-2/adaptor-1' and its CfprApManagedObjectId set to '13203'. · Unsigned32 · hint d

Instance identifier of the managed object.

cfprApCallhomePeriodicSystemInventoryDn

1.3.6.1.4.1.9.9.826.2.1.7.8.1.2

CfprApManagedObjectDnAn immutable property of all Managed Objects (MO) that provides a fully qualified and unambiguous name for the MO. A DN provides a fully-qualified path from the top of the object tree. It is built as an ordered sequence of relative names separated by the '/' character. For example, an object representing a network adaptor on a blade might be identified with its DN set to 'sys/chassis-5/blade-2/adaptor-1'. · OCTET STRING

Cisco Firepower callhome:PeriodicSystemInventory:dn managed object property

cfprApCallhomePeriodicSystemInventoryRn

1.3.6.1.4.1.9.9.826.2.1.7.8.1.3

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

Cisco Firepower callhome:PeriodicSystemInventory:rn managed object property

cfprApCallhomePeriodicSystemInventoryAdminState

1.3.6.1.4.1.9.9.826.2.1.7.8.1.4

CfprApCallhomeAdminState0 = off1 = on · Integer32

Cisco Firepower callhome:PeriodicSystemInventory:adminState managed object property

cfprApCallhomePeriodicSystemInventoryIntervalDays

1.3.6.1.4.1.9.9.826.2.1.7.8.1.5

Gauge32

Cisco Firepower callhome:PeriodicSystemInventory:intervalDays managed object property

cfprApCallhomePeriodicSystemInventoryLastDeadline

1.3.6.1.4.1.9.9.826.2.1.7.8.1.6

DateAndTimeA date-time specification. field octets contents range ----- ------ -------- ----- 1 1-2 year* 0..65536 2 3 month 1..12 3 4 day 1..31 4 5 hour 0..23 5 6 minutes 0..59 6 7 seconds 0..60 (use 60 for leap-second) 7 8 deci-seconds 0..9 8 9 direction from UTC '+' / '-' 9 10 hours from UTC* 0..13 10 11 minutes from UTC 0..59 * Notes: - the value of year is in network-byte order - daylight saving time in New Zealand is +13 For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as: 1992-5-26,13:30:15.0,-4:0 Note that if only local time is known, then timezone information (fields 8-10) is not present. SIZE (8 | 11) · OCTET STRING · hint 2d-1d-1d,1d:1d:1d.1d,1a1d:1d

Cisco Firepower callhome:PeriodicSystemInventory:lastDeadline managed object property

cfprApCallhomePeriodicSystemInventoryMaximumRetryCount

1.3.6.1.4.1.9.9.826.2.1.7.8.1.7

Gauge32

Cisco Firepower callhome:PeriodicSystemInventory:maximumRetryCoun t managed object property

cfprApCallhomePeriodicSystemInventoryMinimumSendNowIntervalSeconds

1.3.6.1.4.1.9.9.826.2.1.7.8.1.8

Gauge32

Cisco Firepower callhome:PeriodicSystemInventory:minimumSendNowIn tervalSeconds managed object property

cfprApCallhomePeriodicSystemInventoryNextDeadline

1.3.6.1.4.1.9.9.826.2.1.7.8.1.9

DateAndTimeA date-time specification. field octets contents range ----- ------ -------- ----- 1 1-2 year* 0..65536 2 3 month 1..12 3 4 day 1..31 4 5 hour 0..23 5 6 minutes 0..59 6 7 seconds 0..60 (use 60 for leap-second) 7 8 deci-seconds 0..9 8 9 direction from UTC '+' / '-' 9 10 hours from UTC* 0..13 10 11 minutes from UTC 0..59 * Notes: - the value of year is in network-byte order - daylight saving time in New Zealand is +13 For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as: 1992-5-26,13:30:15.0,-4:0 Note that if only local time is known, then timezone information (fields 8-10) is not present. SIZE (8 | 11) · OCTET STRING · hint 2d-1d-1d,1d:1d:1d.1d,1a1d:1d

Cisco Firepower callhome:PeriodicSystemInventory:nextDeadline managed object property

cfprApCallhomePeriodicSystemInventoryPollIntervalSeconds

1.3.6.1.4.1.9.9.826.2.1.7.8.1.10

Gauge32

Cisco Firepower callhome:PeriodicSystemInventory:pollIntervalSeco nds managed object property

cfprApCallhomePeriodicSystemInventoryRetryCount

1.3.6.1.4.1.9.9.826.2.1.7.8.1.11

Gauge32

Cisco Firepower callhome:PeriodicSystemInventory:retryCount managed object property

cfprApCallhomePeriodicSystemInventoryRetryDelayMinutes

1.3.6.1.4.1.9.9.826.2.1.7.8.1.12

Gauge32

Cisco Firepower callhome:PeriodicSystemInventory:retryDelayMinute s managed object property

cfprApCallhomePeriodicSystemInventorySendNow

1.3.6.1.4.1.9.9.826.2.1.7.8.1.13

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

Cisco Firepower callhome:PeriodicSystemInventory:sendNow managed object property

cfprApCallhomePeriodicSystemInventoryTimeOfDayHour

1.3.6.1.4.1.9.9.826.2.1.7.8.1.14

Gauge32

Cisco Firepower callhome:PeriodicSystemInventory:timeOfDayHour managed object property

cfprApCallhomePeriodicSystemInventoryTimeOfDayMinute

1.3.6.1.4.1.9.9.826.2.1.7.8.1.15

Gauge32

Cisco Firepower callhome:PeriodicSystemInventory:timeOfDayMinute managed object property

cfprApCallhomePeriodicSystemInventoryTimeOfLastAttempt

1.3.6.1.4.1.9.9.826.2.1.7.8.1.16

DateAndTimeA date-time specification. field octets contents range ----- ------ -------- ----- 1 1-2 year* 0..65536 2 3 month 1..12 3 4 day 1..31 4 5 hour 0..23 5 6 minutes 0..59 6 7 seconds 0..60 (use 60 for leap-second) 7 8 deci-seconds 0..9 8 9 direction from UTC '+' / '-' 9 10 hours from UTC* 0..13 10 11 minutes from UTC 0..59 * Notes: - the value of year is in network-byte order - daylight saving time in New Zealand is +13 For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as: 1992-5-26,13:30:15.0,-4:0 Note that if only local time is known, then timezone information (fields 8-10) is not present. SIZE (8 | 11) · OCTET STRING · hint 2d-1d-1d,1d:1d:1d.1d,1a1d:1d

Cisco Firepower callhome:PeriodicSystemInventory:timeOfLastAttemp t managed object property

cfprApCallhomePeriodicSystemInventoryTimeOfLastSuccess

1.3.6.1.4.1.9.9.826.2.1.7.8.1.17

DateAndTimeA date-time specification. field octets contents range ----- ------ -------- ----- 1 1-2 year* 0..65536 2 3 month 1..12 3 4 day 1..31 4 5 hour 0..23 5 6 minutes 0..59 6 7 seconds 0..60 (use 60 for leap-second) 7 8 deci-seconds 0..9 8 9 direction from UTC '+' / '-' 9 10 hours from UTC* 0..13 10 11 minutes from UTC 0..59 * Notes: - the value of year is in network-byte order - daylight saving time in New Zealand is +13 For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as: 1992-5-26,13:30:15.0,-4:0 Note that if only local time is known, then timezone information (fields 8-10) is not present. SIZE (8 | 11) · OCTET STRING · hint 2d-1d-1d,1d:1d:1d.1d,1a1d:1d

Cisco Firepower callhome:PeriodicSystemInventory:timeOfLastSucces s managed object property

cfprApCallhomePolicyTable

1.3.6.1.4.1.9.9.826.2.1.7.9

Index: cfprApCallhomePolicyInstanceId

Cisco Firepower callhome:Policy managed object table

cfprApCallhomePolicyInstanceId

1.3.6.1.4.1.9.9.826.2.1.7.9.1.1

CfprApManagedObjectIdA unique identifier for this managed object. Objects in FPR Manager are stored in a Management Information Tree (MIT). The MIT is a repository of all Managed Object (MO) instances, indexed by their Distinguished Name (DN). The MIT somewhat resembles a file structure - going from main folder to the next lowest folder, and so on, until the full path to a MO is established. Every object in FPR Manager has two unique identifiers: 1) A distinguished name (DN). A DN provides a fully-qualified path from the top of the object tree. It is built as an ordered sequence of relative names separated by the '/' character. The DN is used to identify objects in the XML API. 2) A CfprApManagedObjectId, which is an integer uniquely identifying an object. The CfprApManagedObjectId is used to identify objects and traverse tables when using the SNMP protocol. For example, an object representing a network adaptor on a blade might be identified with its DN set to 'sys/chassis-5/blade-2/adaptor-1' and its CfprApManagedObjectId set to '13203'. · Unsigned32 · hint d

Instance identifier of the managed object.

cfprApCallhomePolicyDn

1.3.6.1.4.1.9.9.826.2.1.7.9.1.2

CfprApManagedObjectDnAn immutable property of all Managed Objects (MO) that provides a fully qualified and unambiguous name for the MO. A DN provides a fully-qualified path from the top of the object tree. It is built as an ordered sequence of relative names separated by the '/' character. For example, an object representing a network adaptor on a blade might be identified with its DN set to 'sys/chassis-5/blade-2/adaptor-1'. · OCTET STRING

Cisco Firepower callhome:Policy:dn managed object property

cfprApCallhomePolicyRn

1.3.6.1.4.1.9.9.826.2.1.7.9.1.3

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

Cisco Firepower callhome:Policy:rn managed object property

cfprApCallhomePolicyAdminState

1.3.6.1.4.1.9.9.826.2.1.7.9.1.4

CfprApCallhomePolicyAdminState1 = enabled2 = disabled · Integer32

Cisco Firepower callhome:Policy:adminState managed object property

cfprApCallhomePolicyCause

1.3.6.1.4.1.9.9.826.2.1.7.9.1.5

CfprApConditionCallHomeCause0 = unspecified1 = identityUnestablishable2 = powerProblem3 = equipmentInoperable4 = equipmentInaccessible5 = vifIdsMismatch6 = adaptorMismatch7 = voltageProblem8 = psuInsufficient9 = psuMixedMode10 = connectivityProblem11 = equipmentDisabled12 = thermalProblem13 = configurationFailure14 = associationFailed15 = equipmentOffline16 = equipmentProblem17 = fruProblem18 = healthLedAmberBlinking19 = healthLedAmber20 = licenseGraceperiodExpired21 = equipmentDegraded22 = mgmtifDown23 = arpTargetsConfigError24 = ndiscTargetsConfigError25 = equipmentRemoved26 = limitReached27 = nearMaxLimit28 = inventoryFailed29 = memoryError30 = linkDown31 = electionFailure32 = managementServicesFailure33 = managementServicesUnresponsive34 = versionIncompatible35 = portFailed · Integer32

Cisco Firepower callhome:Policy:cause managed object property

cfprApCallhomePolicyDescr

1.3.6.1.4.1.9.9.826.2.1.7.9.1.6

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

Cisco Firepower callhome:Policy:descr managed object property

cfprApCallhomePolicyName

1.3.6.1.4.1.9.9.826.2.1.7.9.1.7

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

Cisco Firepower callhome:Policy:name managed object property

cfprApCallhomeProfileTable

1.3.6.1.4.1.9.9.826.2.1.7.10

Index: cfprApCallhomeProfileInstanceId

Cisco Firepower callhome:Profile managed object table

cfprApCallhomeProfileInstanceId

1.3.6.1.4.1.9.9.826.2.1.7.10.1.1

CfprApManagedObjectIdA unique identifier for this managed object. Objects in FPR Manager are stored in a Management Information Tree (MIT). The MIT is a repository of all Managed Object (MO) instances, indexed by their Distinguished Name (DN). The MIT somewhat resembles a file structure - going from main folder to the next lowest folder, and so on, until the full path to a MO is established. Every object in FPR Manager has two unique identifiers: 1) A distinguished name (DN). A DN provides a fully-qualified path from the top of the object tree. It is built as an ordered sequence of relative names separated by the '/' character. The DN is used to identify objects in the XML API. 2) A CfprApManagedObjectId, which is an integer uniquely identifying an object. The CfprApManagedObjectId is used to identify objects and traverse tables when using the SNMP protocol. For example, an object representing a network adaptor on a blade might be identified with its DN set to 'sys/chassis-5/blade-2/adaptor-1' and its CfprApManagedObjectId set to '13203'. · Unsigned32 · hint d

Instance identifier of the managed object.

cfprApCallhomeProfileDn

1.3.6.1.4.1.9.9.826.2.1.7.10.1.2

CfprApManagedObjectDnAn immutable property of all Managed Objects (MO) that provides a fully qualified and unambiguous name for the MO. A DN provides a fully-qualified path from the top of the object tree. It is built as an ordered sequence of relative names separated by the '/' character. For example, an object representing a network adaptor on a blade might be identified with its DN set to 'sys/chassis-5/blade-2/adaptor-1'. · OCTET STRING

Cisco Firepower callhome:Profile:dn managed object property

cfprApCallhomeProfileRn

1.3.6.1.4.1.9.9.826.2.1.7.10.1.3

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

Cisco Firepower callhome:Profile:rn managed object property

cfprApCallhomeProfileAlertGroups

1.3.6.1.4.1.9.9.826.2.1.7.10.1.4

CfprApCallhomeAlertGroups · BITS

Cisco Firepower callhome:Profile:alertGroups managed object property

cfprApCallhomeProfileDescr

1.3.6.1.4.1.9.9.826.2.1.7.10.1.5

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

Cisco Firepower callhome:Profile:descr managed object property

cfprApCallhomeProfileFormat

1.3.6.1.4.1.9.9.826.2.1.7.10.1.6

CfprApCallhomeFormat1 = xml2 = fullTxt4 = shortTxt · Integer32

Cisco Firepower callhome:Profile:format managed object property

cfprApCallhomeProfileLevel

1.3.6.1.4.1.9.9.826.2.1.7.10.1.7

CfprApCallhomeLevel0 = debug1 = normal2 = notification3 = warning4 = minor5 = major6 = critical7 = fatal8 = disaster · Integer32

Cisco Firepower callhome:Profile:level managed object property

cfprApCallhomeProfileMaxSize

1.3.6.1.4.1.9.9.826.2.1.7.10.1.8

Gauge32

Cisco Firepower callhome:Profile:maxSize managed object property

cfprApCallhomeProfileName

1.3.6.1.4.1.9.9.826.2.1.7.10.1.9

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

Cisco Firepower callhome:Profile:name managed object property

cfprApCallhomeProfileReporting

1.3.6.1.4.1.9.9.826.2.1.7.10.1.10

CfprApCallhomeReportingType0 = smartLicenseData1 = smartCallHomeData · Integer32

Cisco Firepower callhome:Profile:reporting managed object property

cfprApCallhomeSmtpTable

1.3.6.1.4.1.9.9.826.2.1.7.11

Index: cfprApCallhomeSmtpInstanceId

Cisco Firepower callhome:Smtp managed object table

cfprApCallhomeSmtpInstanceId

1.3.6.1.4.1.9.9.826.2.1.7.11.1.1

CfprApManagedObjectIdA unique identifier for this managed object. Objects in FPR Manager are stored in a Management Information Tree (MIT). The MIT is a repository of all Managed Object (MO) instances, indexed by their Distinguished Name (DN). The MIT somewhat resembles a file structure - going from main folder to the next lowest folder, and so on, until the full path to a MO is established. Every object in FPR Manager has two unique identifiers: 1) A distinguished name (DN). A DN provides a fully-qualified path from the top of the object tree. It is built as an ordered sequence of relative names separated by the '/' character. The DN is used to identify objects in the XML API. 2) A CfprApManagedObjectId, which is an integer uniquely identifying an object. The CfprApManagedObjectId is used to identify objects and traverse tables when using the SNMP protocol. For example, an object representing a network adaptor on a blade might be identified with its DN set to 'sys/chassis-5/blade-2/adaptor-1' and its CfprApManagedObjectId set to '13203'. · Unsigned32 · hint d

Instance identifier of the managed object.

cfprApCallhomeSmtpDn

1.3.6.1.4.1.9.9.826.2.1.7.11.1.2

CfprApManagedObjectDnAn immutable property of all Managed Objects (MO) that provides a fully qualified and unambiguous name for the MO. A DN provides a fully-qualified path from the top of the object tree. It is built as an ordered sequence of relative names separated by the '/' character. For example, an object representing a network adaptor on a blade might be identified with its DN set to 'sys/chassis-5/blade-2/adaptor-1'. · OCTET STRING

Cisco Firepower callhome:Smtp:dn managed object property

cfprApCallhomeSmtpRn

1.3.6.1.4.1.9.9.826.2.1.7.11.1.3

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

Cisco Firepower callhome:Smtp:rn managed object property

cfprApCallhomeSmtpHost

1.3.6.1.4.1.9.9.826.2.1.7.11.1.4

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

Cisco Firepower callhome:Smtp:host managed object property

cfprApCallhomeSmtpPort

1.3.6.1.4.1.9.9.826.2.1.7.11.1.5

Gauge32

Cisco Firepower callhome:Smtp:port managed object property

cfprApCallhomeSourceTable

1.3.6.1.4.1.9.9.826.2.1.7.12

Index: cfprApCallhomeSourceInstanceId

Cisco Firepower callhome:Source managed object table

cfprApCallhomeSourceInstanceId

1.3.6.1.4.1.9.9.826.2.1.7.12.1.1

CfprApManagedObjectIdA unique identifier for this managed object. Objects in FPR Manager are stored in a Management Information Tree (MIT). The MIT is a repository of all Managed Object (MO) instances, indexed by their Distinguished Name (DN). The MIT somewhat resembles a file structure - going from main folder to the next lowest folder, and so on, until the full path to a MO is established. Every object in FPR Manager has two unique identifiers: 1) A distinguished name (DN). A DN provides a fully-qualified path from the top of the object tree. It is built as an ordered sequence of relative names separated by the '/' character. The DN is used to identify objects in the XML API. 2) A CfprApManagedObjectId, which is an integer uniquely identifying an object. The CfprApManagedObjectId is used to identify objects and traverse tables when using the SNMP protocol. For example, an object representing a network adaptor on a blade might be identified with its DN set to 'sys/chassis-5/blade-2/adaptor-1' and its CfprApManagedObjectId set to '13203'. · Unsigned32 · hint d

Instance identifier of the managed object.

cfprApCallhomeSourceDn

1.3.6.1.4.1.9.9.826.2.1.7.12.1.2

CfprApManagedObjectDnAn immutable property of all Managed Objects (MO) that provides a fully qualified and unambiguous name for the MO. A DN provides a fully-qualified path from the top of the object tree. It is built as an ordered sequence of relative names separated by the '/' character. For example, an object representing a network adaptor on a blade might be identified with its DN set to 'sys/chassis-5/blade-2/adaptor-1'. · OCTET STRING

Cisco Firepower callhome:Source:dn managed object property

cfprApCallhomeSourceRn

1.3.6.1.4.1.9.9.826.2.1.7.12.1.3

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

Cisco Firepower callhome:Source:rn managed object property

cfprApCallhomeSourceAddr

1.3.6.1.4.1.9.9.826.2.1.7.12.1.4

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

Cisco Firepower callhome:Source:addr managed object property

cfprApCallhomeSourceContact

1.3.6.1.4.1.9.9.826.2.1.7.12.1.5

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

Cisco Firepower callhome:Source:contact managed object property

cfprApCallhomeSourceContract

1.3.6.1.4.1.9.9.826.2.1.7.12.1.6

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

Cisco Firepower callhome:Source:contract managed object property

cfprApCallhomeSourceCustomer

1.3.6.1.4.1.9.9.826.2.1.7.12.1.7

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

Cisco Firepower callhome:Source:customer managed object property

cfprApCallhomeSourceEmail

1.3.6.1.4.1.9.9.826.2.1.7.12.1.8

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

Cisco Firepower callhome:Source:email managed object property

cfprApCallhomeSourceFrom

1.3.6.1.4.1.9.9.826.2.1.7.12.1.9

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

Cisco Firepower callhome:Source:from managed object property

cfprApCallhomeSourcePhone

1.3.6.1.4.1.9.9.826.2.1.7.12.1.10

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

Cisco Firepower callhome:Source:phone managed object property

cfprApCallhomeSourceReplyTo

1.3.6.1.4.1.9.9.826.2.1.7.12.1.11

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

Cisco Firepower callhome:Source:replyTo managed object property

cfprApCallhomeSourceSite

1.3.6.1.4.1.9.9.826.2.1.7.12.1.12

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

Cisco Firepower callhome:Source:site managed object property

cfprApCallhomeSourceUrgency

1.3.6.1.4.1.9.9.826.2.1.7.12.1.13

CfprApCallhomeUrgency0 = emergency1 = alert2 = critical3 = error4 = warning5 = notice6 = info7 = debug · Integer32

Cisco Firepower callhome:Source:urgency managed object property

cfprApCallhomeTestAlertTable

1.3.6.1.4.1.9.9.826.2.1.7.13

Index: cfprApCallhomeTestAlertInstanceId

Cisco Firepower callhome:TestAlert managed object table

cfprApCallhomeTestAlertInstanceId

1.3.6.1.4.1.9.9.826.2.1.7.13.1.1

CfprApManagedObjectIdA unique identifier for this managed object. Objects in FPR Manager are stored in a Management Information Tree (MIT). The MIT is a repository of all Managed Object (MO) instances, indexed by their Distinguished Name (DN). The MIT somewhat resembles a file structure - going from main folder to the next lowest folder, and so on, until the full path to a MO is established. Every object in FPR Manager has two unique identifiers: 1) A distinguished name (DN). A DN provides a fully-qualified path from the top of the object tree. It is built as an ordered sequence of relative names separated by the '/' character. The DN is used to identify objects in the XML API. 2) A CfprApManagedObjectId, which is an integer uniquely identifying an object. The CfprApManagedObjectId is used to identify objects and traverse tables when using the SNMP protocol. For example, an object representing a network adaptor on a blade might be identified with its DN set to 'sys/chassis-5/blade-2/adaptor-1' and its CfprApManagedObjectId set to '13203'. · Unsigned32 · hint d

Instance identifier of the managed object.

cfprApCallhomeTestAlertDn

1.3.6.1.4.1.9.9.826.2.1.7.13.1.2

CfprApManagedObjectDnAn immutable property of all Managed Objects (MO) that provides a fully qualified and unambiguous name for the MO. A DN provides a fully-qualified path from the top of the object tree. It is built as an ordered sequence of relative names separated by the '/' character. For example, an object representing a network adaptor on a blade might be identified with its DN set to 'sys/chassis-5/blade-2/adaptor-1'. · OCTET STRING

Cisco Firepower callhome:TestAlert:dn managed object property

cfprApCallhomeTestAlertRn

1.3.6.1.4.1.9.9.826.2.1.7.13.1.3

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

Cisco Firepower callhome:TestAlert:rn managed object property

cfprApCallhomeTestAlertDescription

1.3.6.1.4.1.9.9.826.2.1.7.13.1.4

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

Cisco Firepower callhome:TestAlert:description managed object property

cfprApCallhomeTestAlertGroup

1.3.6.1.4.1.9.9.826.2.1.7.13.1.5

CfprApCallhomeAlertGroup0 = diagnostic1 = environmental100 = unknown · Integer32

Cisco Firepower callhome:TestAlert:group managed object property

cfprApCallhomeTestAlertLevel

1.3.6.1.4.1.9.9.826.2.1.7.13.1.6

CfprApCallhomeAlertLevel0 = debug1 = normal2 = notify3 = warning4 = minor5 = major6 = critical7 = fatal100 = unknown · Integer32

Cisco Firepower callhome:TestAlert:level managed object property

cfprApCallhomeTestAlertMessageSubtype

1.3.6.1.4.1.9.9.826.2.1.7.13.1.7

CfprApCallhomeAlertMessageSubtype0 = nosubtype1 = test2 = full3 = delta4 = minor5 = major6 = goldnormal7 = goldminor8 = goldmajor100 = unknown · Integer32

Cisco Firepower callhome:TestAlert:messageSubtype managed object property

cfprApCallhomeTestAlertMessageType

1.3.6.1.4.1.9.9.826.2.1.7.13.1.8

CfprApCallhomeAlertMessageType0 = inventory1 = syslog2 = test3 = diag4 = env5 = conf6 = telemetry100 = unknown · Integer32

Cisco Firepower callhome:TestAlert:messageType managed object property

cfprApCallhomeTestAlertSendNow

1.3.6.1.4.1.9.9.826.2.1.7.13.1.9

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

Cisco Firepower callhome:TestAlert:sendNow managed object property

↑ To TOC