cwSctFileMgmtEntry

CISCO-WAN-SCT-MGMT-MIB · .1.3.6.1.4.1.9.9.236.1.1.1

MIB view Table view

Object

row

An entry in the SCT file Management Table. This represents a
unique SCT file in the node. Each entry contains the configuration
and status information of a specific SCT in the node.

Context

MIB: CISCO-WAN-SCT-MGMT-MIB
OID: .1.3.6.1.4.1.9.9.236.1.1.1
Type: row
Status: current
Parent: cwSctFileMgmtTable
Table: cwSctFileMgmtTable
Children: 10

Syntax

No syntax metadata recorded.

Values & Constraints

No enumerated values or constraints recorded.

Related Objects

Child Objects

Object	Type	Syntax	OID
cwSctCardType This represents service modules in a node that require the use of a SCT. The content of the SCT varies depending on the specific hardware used. Hence there is a different SCT for…	column	Enumeration	`.1.3.6.1.4.1.9.9.236.1.1.1.1`
cwSctFileRowStatus * To create a row, the manager needs to perform a SET operations with a 'CreateAndGo' option. The agent would validate the file specified by the indices if found valid woul…	column	SNMPv2-TCRowStatus	`.1.3.6.1.4.1.9.9.236.1.1.1.10`
cwSctType There are several types of SCTs. The portSct (1) specifies traffic parameters that are applicable to a logical port within a card. The cardSct (2) specifies traffic parameters th…	column	Enumeration	`.1.3.6.1.4.1.9.9.236.1.1.1.2`
cwSctId Each logical port on a service module could need different 'class of service' characteristics. This can be achieved by applying different SCTs on different ports. Thus for a given…	column	Unsigned32	`.1.3.6.1.4.1.9.9.236.1.1.1.3`
cwSctMajorVersion The SCT file consists of several tables. The number of tables depend on the service module card type. Both the contents and the row/column size of a table are subject to change. …	column	Unsigned32	`.1.3.6.1.4.1.9.9.236.1.1.1.4`
cwSctFileName This object specifies the absolute path name of the file corresponding to the SCT indices. After the agent accepts a SET operation and creates a new row in the SCT…	column	OctetString	`.1.3.6.1.4.1.9.9.236.1.1.1.5`
cwSctFileMinorVersion The SCT file consists of several tables. The number of tables depend on the service module card type. Both the contents and the row/column size of a table are subject to change. …	column	Unsigned32	`.1.3.6.1.4.1.9.9.236.1.1.1.6`
cwSctFileChecksum The manager specifies this checksum when trying to add a SCT on the node. The agent while acting on the SET operation would perform a checksum computation on the FTPed file and c…	column	SNMPv2-SMIUnsigned32	`.1.3.6.1.4.1.9.9.236.1.1.1.7`
cwSctFileDescription A description string can be associated with a specific SCT index and in turn the SCT file. This may be used for associating customized filenames.	column	OctetString	`.1.3.6.1.4.1.9.9.236.1.1.1.8`
cwSctFileOperStatus Reflects the operational status of the SCT file. The agent sets the value to valid(1) if the computed checksum of the SCT file matches the provisioned checksum. …	column	Enumeration	`.1.3.6.1.4.1.9.9.236.1.1.1.9`

Indexes

Object	Type	Syntax	OID
cwSctCardType This represents service modules in a node that require the use of a SCT. The content of the SCT varies depending on the specific hardware used. Hence there is a different SCT for…	column	Enumeration	`.1.3.6.1.4.1.9.9.236.1.1.1.1`
cwSctType There are several types of SCTs. The portSct (1) specifies traffic parameters that are applicable to a logical port within a card. The cardSct (2) specifies traffic parameters th…	column	Enumeration	`.1.3.6.1.4.1.9.9.236.1.1.1.2`
cwSctId Each logical port on a service module could need different 'class of service' characteristics. This can be achieved by applying different SCTs on different ports. Thus for a given…	column	Unsigned32	`.1.3.6.1.4.1.9.9.236.1.1.1.3`
cwSctMajorVersion The SCT file consists of several tables. The number of tables depend on the service module card type. Both the contents and the row/column size of a table are subject to change. …	column	Unsigned32	`.1.3.6.1.4.1.9.9.236.1.1.1.4`