This MIB defines a SCT file management table in which each row
corresponds to a unique SCT file.
When the NMS needs to add a SCT to a node, it transfers the SCT
file to a transient storage area on the node. The NMS then
performs a SET operation requesting the agent to accept the
transferred file. The agent validates the integrity of the
file and if valid, transfers the file to a secure area. It
would then create a new row in the SCT file management table. This
newly added row is then advertised to all NMS in the network using
appropriate traps (refer CISCO-WAN-SCT-MGMT-TRAPS-MIB).
Once a row is created, the agent keeps track of the operational
status of the corresponding SCT file. The NMS can query the status
of a SCT file by performing a GET operation on the row.
The NMS can delete a SCT file and its corresponding row in the SCT
file management table by performing a SET operation with the
appropriate RowStatus. The agent, upon successful deletion
of the row would advertise this configuration change to all the
NMS using appropriate traps.
The NMS could also perform a GETNEXT operation to discover all the
configured SCTs on a node.
Parsed from file CISCO-WAN-SCT-MGMT-MIB.mib
Module: CISCO-WAN-SCT-MGMT-MIB
This MIB defines a SCT file management table in which each row
corresponds to a unique SCT file.
When the NMS needs to add a SCT to a node, it transfers the SCT
file to a transient storage area on the node. The NMS then
performs a SET operation requesting the agent to accept the
transferred file. The agent validates the integrity of the
file and if valid, transfers the file to a secure area. It
would then create a new row in the SCT file management table. This
newly added row is then advertised to all NMS in the network using
appropriate traps (refer CISCO-WAN-SCT-MGMT-TRAPS-MIB).
Once a row is created, the agent keeps track of the operational
status of the corresponding SCT file. The NMS can query the status
of a SCT file by performing a GET operation on the row.
The NMS can delete a SCT file and its corresponding row in the SCT
file management table by performing a SET operation with the
appropriate RowStatus. The agent, upon successful deletion
of the row would advertise this configuration change to all the
NMS using appropriate traps.
The NMS could also perform a GETNEXT operation to discover all the
configured SCTs on a node.
This MIB defines a SCT file management table in which each row
corresponds to a unique SCT file.
When the NMS needs to add a SCT to a node, it transfers the SCT
file to a transient storage area on the node. The NMS then
performs a SET operation requesting the agent to accept the
transferred file. The agent validates the integrity of the
file and if valid, transfers the file to a secure area. It
would then create a new row in the SCT file management table. This
newly added row is then advertised to all NMS in the network using
appropriate traps (refer CISCO-WAN-SCT-MGMT-TRAPS-MIB).
Once a row is created, the agent keeps track of the operational
status of the corresponding SCT file. The NMS can query the status
of a SCT file by performing a GET operation on the row.
The NMS can delete a SCT file and its corresponding row in the SCT
file management table by performing a SET operation with the
appropriate RowStatus. The agent, upon successful deletion
of the row would advertise this configuration change to all the
NMS using appropriate traps.
The NMS could also perform a GETNEXT operation to discover all the
configured SCTs on a node.
Parsed from file CISCO-WAN-SCT-MGMT-MIB.my.txt
Company: None
Module: CISCO-WAN-SCT-MGMT-MIB
This MIB defines a SCT file management table in which each row
corresponds to a unique SCT file.
When the NMS needs to add a SCT to a node, it transfers the SCT
file to a transient storage area on the node. The NMS then
performs a SET operation requesting the agent to accept the
transferred file. The agent validates the integrity of the
file and if valid, transfers the file to a secure area. It
would then create a new row in the SCT file management table. This
newly added row is then advertised to all NMS in the network using
appropriate traps (refer CISCO-WAN-SCT-MGMT-TRAPS-MIB).
Once a row is created, the agent keeps track of the operational
status of the corresponding SCT file. The NMS can query the status
of a SCT file by performing a GET operation on the row.
The NMS can delete a SCT file and its corresponding row in the SCT
file management table by performing a SET operation with the
appropriate RowStatus. The agent, upon successful deletion
of the row would advertise this configuration change to all the
NMS using appropriate traps.
The NMS could also perform a GETNEXT operation to discover all the
configured SCTs on a node.
cwSctFileMgmtTable OBJECT-TYPE SYNTAX SEQUENCE OF CwSctFileMgmtEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This MIB defines a SCT file management table in which each row corresponds to a unique SCT file. When the NMS needs to add a SCT to a node, it transfers the SCT file to a transient storage area on the node. The NMS then performs a SET operation requesting the agent to accept the transferred file. The agent validates the integrity of the file and if valid, transfers the file to a secure area. It would then create a new row in the SCT file management table. This newly added row is then advertised to all NMS in the network using appropriate traps (refer CISCO-WAN-SCT-MGMT-TRAPS-MIB). Once a row is created, the agent keeps track of the operational status of the corresponding SCT file. The NMS can query the status of a SCT file by performing a GET operation on the row. The NMS can delete a SCT file and its corresponding row in the SCT file management table by performing a SET operation with the appropriate RowStatus. The agent, upon successful deletion of the row would advertise this configuration change to all the NMS using appropriate traps. The NMS could also perform a GETNEXT operation to discover all the configured SCTs on a node." ::= { ciscoWanSctMgmtMIBObjects 1 }
cwSctFileMgmtTable OBJECT-TYPE SYNTAX SEQUENCE OF CwSctFileMgmtEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "This MIB defines a SCT file management table in which each row corresponds to a unique SCT file. When the NMS needs to add a SCT to a node, it transfers the SCT file to a transient storage area on the node. The NMS then performs a SET operation requesting the agent to accept the transferred file. The agent validates the integrity of the file and if valid, transfers the file to a secure area. It would then create a new row in the SCT file management table. This newly added row is then advertised to all NMS in the network using appropriate traps (refer CISCO-WAN-SCT-MGMT-TRAPS-MIB). Once a row is created, the agent keeps track of the operational status of the corresponding SCT file. The NMS can query the status of a SCT file by performing a GET operation on the row. The NMS can delete a SCT file and its corresponding row in the SCT file management table by performing a SET operation with the appropriate RowStatus. The agent, upon successful deletion of the row would advertise this configuration change to all the NMS using appropriate traps. The NMS could also perform a GETNEXT operation to discover all the configured SCTs on a node." ::= { ciscoWanSctMgmtMIBObjects 1 }
Vendor: Cisco
Module: CISCO-WAN-SCT-MGMT-MIB
[Automatically extracted from oidview.com]
cwSctFileMgmtTable OBJECT-TYPE SYNTAX SEQUENCE OF CwSctFileMgmtEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This MIB defines a SCT file management table in which each row corresponds to a unique SCT file. When the NMS needs to add a SCT to a node, it transfers the SCT file to a transient storage area on the node. The NMS then performs a SET operation requesting the agent to accept the transferred file. The agent validates the integrity of the file and if valid, transfers the file to a secure area. It would then create a new row in the SCT file management table. This newly added row is then advertised to all NMS in the network using appropriate traps (refer CISCO-WAN-SCT-MGMT-TRAPS-MIB). Once a row is created, the agent keeps track of the operational status of the corresponding SCT file. The NMS can query the status of a SCT file by performing a GET operation on the row. The NMS can delete a SCT file and its corresponding row in the SCT file management table by performing a SET operation with the appropriate RowStatus. The agent, upon successful deletion of the row would advertise this configuration change to all the NMS using appropriate traps. The NMS could also perform a GETNEXT operation to discover all the configured SCTs on a node." ::= { ciscoWanSctMgmtMIBObjects 1 }
cwSctFileMgmtTable OBJECT-TYPE SYNTAX SEQUENCE OF CwSctFileMgmtEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This MIB defines a SCT file management table in which each row corresponds to a unique SCT file. When the NMS needs to add a SCT to a node, it transfers the SCT file to a transient storage area on the node. The NMS then performs a SET operation requesting the agent to accept the transferred file. The agent validates the integrity of the file and if valid, transfers the file to a secure area. It would then create a new row in the SCT file management table. This newly added row is then advertised to all NMS in the network using appropriate traps (refer CISCO-WAN-SCT-MGMT-TRAPS-MIB). Once a row is created, the agent keeps track of the operational status of the corresponding SCT file. The NMS can query the status of a SCT file by performing a GET operation on the row. The NMS can delete a SCT file and its corresponding row in the SCT file management table by performing a SET operation with the appropriate RowStatus. The agent, upon successful deletion of the row would advertise this configuration change to all the NMS using appropriate traps. The NMS could also perform a GETNEXT operation to discover all the configured SCTs on a node." ::= { ciscoWanSctMgmtMIBObjects 1 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.9.236.1.1.1 | cwSctFileMgmtEntry | 10 | 10 | An entry in the SCT file Management Table. This represents a unique SCT file in the node. Each entry contains the configuration a… |