CISCO-BULK-FILE-CAPABILITY device MIB details by Cisco
CISCO-BULK-FILE-CAPABILITY file content
The SNMP protocol is used to for conveying information and commands between agents and managing entities. SNMP uses the User Datagram Protocol (UDP) as the transport protocol for passing data between managers and agents. The reasons for using UDP for SNMP are, firstly it has low overheads in comparison to TCP, which uses a 3-way hand shake for connection. Secondly, in congested networks, SNMP over TCP is a bad idea because TCP in order to maintain reliability will flood the network with retransmissions.
Management information (MIB) is represented as a collection of managed objects. These objects together form a virtual information base called MIB. An agent may implement many MIBs, but all agents must implement a particular MIB called MIB-II [16]. This standard defines variables for things such as interface statistics (interface speeds, MTU, octets sent, octets received, etc.) as well as various other things pertaining to the system itself (system location, system contact, etc.). The main goal of MIB-II is to provide general TCP/IP management information.
Use ActiveXperts Network Monitor 2024 to import vendor-specific MIB files, inclusing CISCO-BULK-FILE-CAPABILITY.
Vendor: | Cisco |
---|---|
Mib: | CISCO-BULK-FILE-CAPABILITY [download] [view objects] |
Tool: | ActiveXperts Network Monitor 2024 [download] (ships with advanced SNMP/MIB tools) |
-- ***************************************************************** -- CISCO-BULK-FILE-CAPABILITY.my: CISCO-BULK-FILE-MIB AGENT-CAPABILITIES -- -- November, 2003, Yizhong Shen -- -- Copyright (c) 2000, 2002, 2003 by cisco Systems, Inc. -- All rights reserved. -- -- ***************************************************************** CISCO-BULK-FILE-CAPABILITY DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY FROM SNMPv2-SMI AGENT-CAPABILITIES FROM SNMPv2-CONF DisplayString FROM SNMPv2-TC ciscoAgentCapability FROM CISCO-SMI; ciscoBulkFileCapability MODULE-IDENTITY LAST-UPDATED "200311130000Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO " Cisco Systems Customer Service Postal: 170 West Tasman Drive San Jose, CA 95134 USA Tel: +1 800 553-NETS E-mail: cs-snmp@cisco.com" DESCRIPTION "Agent capabilities for CISCO-BULK-FILE-MIB" REVISION "200311130000Z" DESCRIPTION "Added VXSM 5.0.0 PRODUCT-RELEASE of ciscoBulkFileCapabilityV3R00" REVISION "200202170000Z" DESCRIPTION "Added following capabilities for MGX8850/SES Products: - ciscoBulkFileCapabilityV2R00 - ciscoBulkFileCapabilityV3R00." REVISION "200012040000Z" DESCRIPTION "Initial version of this MIB module." ::= { ciscoAgentCapability 188 } ciscoBulkFileCapabilityV1R0 AGENT-CAPABILITIES PRODUCT-RELEASE "Cisco IOS mc 1.0" STATUS current DESCRIPTION "Cisco Bulk File MIB capabilities" SUPPORTS CISCO-BULK-FILE-MIB INCLUDES { ciscoBulkFileDefineGroup } VARIATION cbfDefineFileFormat SYNTAX INTEGER { standardBER(1), bulkBinary(2), bulkASCII(3) } DESCRIPTION "standardBER(1) is not supported" VARIATION cbfDefineFileStorage SYNTAX INTEGER { volatile(2) } DESCRIPTION "ephemeral(1) and permanent(3) are not supported" VARIATION cbfDefineFileName SYNTAX DisplayString (SIZE (1..255)) DESCRIPTION "The files can only be stored in the '/tmp' directory. The implementation attaches '/tmp' to the start of the NMS specified file name. Therefore, if the NMS specifies the file name as 'xyz', it'll be stored in '/tmp/xyz' and if its 'xyz/pqr', it'll be stored in '/tmp/xyz/pqr'. But if the name is '/tmp/xyz', the file will be created in '/tmp/xyz' and not '/tmp/tmp/xyz'" ::= { ciscoBulkFileCapability 1 } ciscoBulkFileCapabilityV2R00 AGENT-CAPABILITIES PRODUCT-RELEASE "MGX8850 Release 2.00, BPX SES Release 1.00." STATUS current DESCRIPTION "CISCO-BULK-FILE-MIB Capabilities." SUPPORTS CISCO-BULK-FILE-MIB INCLUDES { ciscoBulkFileDefineGroup, ciscoBulkFileStatusGroup } VARIATION cbfDefineMaxFiles ACCESS not-implemented DESCRIPTION "Not supported." VARIATION cbfDefineFiles ACCESS not-implemented DESCRIPTION "Not supported." VARIATION cbfDefineHighFiles ACCESS not-implemented DESCRIPTION "Not supported." VARIATION cbfDefineFilesRefused ACCESS not-implemented DESCRIPTION "Not supported." VARIATION cbfDefineMaxObjects ACCESS not-implemented DESCRIPTION "Not supported." VARIATION cbfDefineObjects ACCESS not-implemented DESCRIPTION "Not supported." VARIATION cbfDefineHighObjects ACCESS not-implemented DESCRIPTION "Not supported." VARIATION cbfDefineObjectsRefused ACCESS not-implemented DESCRIPTION "Not supported." VARIATION cbfDefineFileName ACCESS read-only DESCRIPTION "Write operation is not supported." VARIATION cbfDefineFileStorage ACCESS read-only DESCRIPTION "Write operation is not supported." VARIATION cbfDefineFileFormat SYNTAX INTEGER { standardBER(1), bulkBinary(2) } ACCESS read-only DESCRIPTION "Write operation is not supported. Do not support bulkASCII(3)." VARIATION cbfDefineFileEntryStatus ACCESS read-only DESCRIPTION "Write operation is not supported." VARIATION cbfDefineObjectClass ACCESS not-implemented DESCRIPTION "Not supported." VARIATION cbfDefineObjectID ACCESS not-implemented DESCRIPTION "Not supported." VARIATION cbfDefineObjectEntryStatus ACCESS not-implemented DESCRIPTION "Not supported." VARIATION cbfStatusMaxFiles ACCESS not-implemented DESCRIPTION "Not supported." VARIATION cbfStatusFiles ACCESS not-implemented DESCRIPTION "Not supported." VARIATION cbfStatusHighFiles ACCESS not-implemented DESCRIPTION "Not supported." VARIATION cbfStatusFilesBumped ACCESS not-implemented DESCRIPTION "Not supported." VARIATION cbfStatusFileEntryStatus ACCESS read-only DESCRIPTION "Write operation is not supported." ::= { ciscoBulkFileCapability 2 } ciscoBulkFileCapabilityV3R00 AGENT-CAPABILITIES PRODUCT-RELEASE "MGX8850 Release 3.00, BPX SES Release 3.00, VXSM Release 5.0.0." STATUS current DESCRIPTION "CISCO-BULK-FILE-MIB Capabilities." SUPPORTS CISCO-BULK-FILE-MIB INCLUDES { ciscoBulkFileDefineGroup, ciscoBulkFileStatusGroup } VARIATION cbfDefineMaxFiles ACCESS not-implemented DESCRIPTION "Not supported." VARIATION cbfDefineFiles ACCESS not-implemented DESCRIPTION "Not supported." VARIATION cbfDefineHighFiles ACCESS not-implemented DESCRIPTION "Not supported." VARIATION cbfDefineFilesRefused ACCESS not-implemented DESCRIPTION "Not supported." VARIATION cbfDefineMaxObjects ACCESS not-implemented DESCRIPTION "Not supported." VARIATION cbfDefineObjects ACCESS not-implemented DESCRIPTION "Not supported." VARIATION cbfDefineHighObjects ACCESS not-implemented DESCRIPTION "Not supported." VARIATION cbfDefineObjectsRefused ACCESS not-implemented DESCRIPTION "Not supported." VARIATION cbfDefineFileName ACCESS read-only DESCRIPTION "Write operation is not supported." VARIATION cbfDefineFileStorage ACCESS read-only DESCRIPTION "Write operation is not supported." VARIATION cbfDefineFileFormat SYNTAX INTEGER { variantBERWithCksum(4), variantBinWithCksum(5) } ACCESS read-only DESCRIPTION "Write operation is not supported. Do not support standardBER(1), bulkBinary(2),bulkASCII(3)." VARIATION cbfDefineFileEntryStatus ACCESS read-only DESCRIPTION "Write operation is not supported." VARIATION cbfDefineObjectClass ACCESS not-implemented DESCRIPTION "Not supported." VARIATION cbfDefineObjectID ACCESS not-implemented DESCRIPTION "Not supported." VARIATION cbfDefineObjectEntryStatus ACCESS not-implemented DESCRIPTION "Not supported." VARIATION cbfStatusMaxFiles ACCESS not-implemented DESCRIPTION "Not supported." VARIATION cbfStatusFiles ACCESS not-implemented DESCRIPTION "Not supported." VARIATION cbfStatusHighFiles ACCESS not-implemented DESCRIPTION "Not supported." VARIATION cbfStatusFilesBumped ACCESS not-implemented DESCRIPTION "Not supported." VARIATION cbfStatusFileEntryStatus ACCESS read-only DESCRIPTION "Write operation is not supported." ::= { ciscoBulkFileCapability 3 } END