rfc2940.txt

来自「著名的RFC文档,其中有一些文档是已经翻译成中文的的.」· 文本 代码 · 共 1,516 行 · 第 1/4 页

TXT
1,516
字号
    ::= { copsClientServerCurrentEntry 22 }copsClientErrUnknownCnum OBJECT-TYPE    SYNTAX     Counter32    MAX-ACCESS  read-only    STATUS      current    DESCRIPTION        "A count of the total number of COPS messages that this client        has received from COPS servers marked for this Client-Type that        contained a COPS protocol object C-Num that was unrecognised by        this client. This value is cumulative since agent restart and is        not zeroed on new connections."    ::= { copsClientServerCurrentEntry 23 }copsClientErrBadCtype OBJECT-TYPE    SYNTAX     Counter32    MAX-ACCESS  read-only    STATUS      current    DESCRIPTION        "A count of the total number of COPS messages that this client        has received from COPS servers marked for this Client-Type that        contained a COPS protocol object C-Type that was not defined for        the C-Nums known by this client. This value is cumulative since        agent restart and is not zeroed on new connections."Smith                       Standards Track                    [Page 14]RFC 2940                    COPS Client MIB                 October 2000    ::= { copsClientServerCurrentEntry 24 }copsClientErrBadSends OBJECT-TYPE    SYNTAX     Counter32    MAX-ACCESS  read-only    STATUS      current    DESCRIPTION        "A count of the total number of COPS messages that this client        attempted to send to COPS servers marked for this Client-Type        that resulted in a transmit error. This value is cumulative        since agent restart and is not zeroed on new connections."    ::= { copsClientServerCurrentEntry 25 }copsClientErrWrongObjects OBJECT-TYPE    SYNTAX     Counter32    MAX-ACCESS  read-only    STATUS      current    DESCRIPTION        "A count of the total number of COPS messages that this client        has received from COPS servers marked for this Client-Type that        did not contain a permitted set of COPS protocol objects. This        value is cumulative since agent restart and is not zeroed on new        connections."    ::= { copsClientServerCurrentEntry 26 }copsClientErrWrongOpcode OBJECT-TYPE    SYNTAX     Counter32    MAX-ACCESS  read-only    STATUS      current    DESCRIPTION        "A count of the total number of COPS messages that this client        has received from COPS servers marked for this Client-Type that        had a COPS protocol Op Code that should not have been sent to a        COPS client e.g. Open-Requests. This value is cumulative since        agent restart and is not zeroed on new connections."    ::= { copsClientServerCurrentEntry 27 }copsClientKaTimedoutClients OBJECT-TYPE    SYNTAX     Counter32    MAX-ACCESS  read-only    STATUS      current    DESCRIPTION        "A count of the total number of times that this client has        been shut down for this Client-Type by COPS servers that had        detected a COPS protocol Keepalive timeout. This value is        cumulative since agent restart and is not zeroed on new        connections."    ::= { copsClientServerCurrentEntry 28 }Smith                       Standards Track                    [Page 15]RFC 2940                    COPS Client MIB                 October 2000copsClientErrAuthFailures OBJECT-TYPE    SYNTAX     Counter32    MAX-ACCESS  read-only    STATUS      current    DESCRIPTION        "A count of the total number of times that this client has        received a COPS message marked for this Client-Type which        could not be authenticated using the authentication mechanism        used by this client."    ::= { copsClientServerCurrentEntry 29 }copsClientErrAuthMissing OBJECT-TYPE    SYNTAX     Counter32    MAX-ACCESS  read-only    STATUS      current    DESCRIPTION        "A count of the total number of times that this client has        received a COPS message marked for this Client-Type which did not        contain authentication information."    ::= { copsClientServerCurrentEntry 30 }-- -------------------------------------------------------------copsClientConfigGroup OBJECT IDENTIFIER ::= { copsClientMIBObjects 3 }-- -------------------------------------------------------------copsClientServerConfigTable OBJECT-TYPE     SYNTAX      SEQUENCE OF CopsClientServerConfigEntry    MAX-ACCESS  not-accessible    STATUS      current    DESCRIPTION        "Table of possible COPS servers to try to connect to in order        of copsClientServerConfigPriority. There may be multiple        entries in this table for the same server and client-type which        specify different security mechanisms: these mechanisms will        be attempted by the client in the priority order given. Note        that a server learned by means of PDPRedirect always takes        priority over any of these configured entries."    ::= { copsClientConfigGroup 1 }copsClientServerConfigEntry OBJECT-TYPE    SYNTAX      CopsClientServerConfigEntry    MAX-ACCESS  not-accessible    STATUS      current    DESCRIPTION        "A set of configuration information regarding a singleSmith                       Standards Track                    [Page 16]RFC 2940                    COPS Client MIB                 October 2000        COPS server from the point of view of a COPS client."    INDEX { copsClientServerConfigAddrType,            copsClientServerConfigAddress,            copsClientServerConfigClientType,            copsClientServerConfigAuthType }    ::= { copsClientServerConfigTable 1 }CopsClientServerConfigEntry ::=    SEQUENCE {        copsClientServerConfigAddrType      InetAddressType,        copsClientServerConfigAddress       InetAddress,        copsClientServerConfigClientType    INTEGER,        copsClientServerConfigAuthType      CopsAuthType,        copsClientServerConfigTcpPort       CopsTcpPort,        copsClientServerConfigPriority      Integer32,        copsClientServerConfigRowStatus     RowStatus    }copsClientServerConfigAddrType OBJECT-TYPE    SYNTAX      InetAddressType    MAX-ACCESS  not-accessible    STATUS      current    DESCRIPTION        "The type of address in copsClientServerConfigAddress."    ::= { copsClientServerConfigEntry 1 }copsClientServerConfigAddress OBJECT-TYPE    SYNTAX      InetAddress    MAX-ACCESS  not-accessible    STATUS      current    DESCRIPTION        "The IPv4, IPv6 or DNS address of a COPS Server. Note that,        since this is an index to the table, the DNS name must be        short enough to fit into the maximum length of indices allowed        by the management protocol in use."    REFERENCE        "RFC 2748 section 2.3"    ::= { copsClientServerConfigEntry 2 }copsClientServerConfigClientType OBJECT-TYPE    SYNTAX      INTEGER (0..65535)    MAX-ACCESS  not-accessible    STATUS      current    DESCRIPTION        "The COPS protocol Client-Type for which this entry        applies and for which this COPS server is capable        of serving. Multiple Client-Types can be served by a        single COPS server."Smith                       Standards Track                    [Page 17]RFC 2940                    COPS Client MIB                 October 2000    REFERENCE        "RFC 2748 section 6, IANA"    ::= { copsClientServerConfigEntry 3 }copsClientServerConfigAuthType OBJECT-TYPE    SYNTAX      CopsAuthType    MAX-ACCESS  not-accessible    STATUS      current    DESCRIPTION        "The type of authentication mechanism for this COPS client        to request when negotiating security at the start of a        connection to a COPS server."    REFERENCE        "RFC 2748 section 4."    ::= { copsClientServerConfigEntry 4 }copsClientServerConfigTcpPort OBJECT-TYPE    SYNTAX      CopsTcpPort    MAX-ACCESS  read-create    STATUS      current    DESCRIPTION        "The TCP port number on the COPS server to which the        client should connect."    ::= { copsClientServerConfigEntry 5 }copsClientServerConfigPriority OBJECT-TYPE    SYNTAX      Integer32    MAX-ACCESS  read-create    STATUS      current    DESCRIPTION        "The priority of this entry relative to other entries.        COPS client will attempt to contact COPS servers for the        appropriate Client-Type. Higher numbers are tried first. The        order to be used amongst server entries with the same priority        is undefined. COPS servers that are notified to the client using        the COPS protocol PDP-Redirect mechanism are always used in        preference to any entries in this table."    ::= { copsClientServerConfigEntry 6 }copsClientServerConfigRowStatus OBJECT-TYPE    SYNTAX      RowStatus    MAX-ACCESS  read-create    STATUS      current    DESCRIPTION        "State of this entry in the table."    ::= { copsClientServerConfigEntry 7 }Smith                       Standards Track                    [Page 18]RFC 2940                    COPS Client MIB                 October 2000copsClientServerConfigRetryAlgrm OBJECT-TYPE    SYNTAX      INTEGER {                    other(1),                    sequential(2),                    roundRobin(3)                }    MAX-ACCESS  read-write    STATUS      current    DESCRIPTION        "The algorithm by which the client should retry when it         fails to connect to a COPS server."    DEFVAL { sequential }    ::= { copsClientConfigGroup 2 }copsClientServerConfigRetryCount OBJECT-TYPE    SYNTAX      Unsigned32    MAX-ACCESS  read-write    STATUS      current    DESCRIPTION        "A retry count for use by the retry algorithm.  Each retry         algorithm needs to specify how it uses this value.         For the 'sequential(2)' algorithm, this value is the         number of times the client should retry to connect         to one COPS server before moving on to another.         For the 'roundRobin(3)' algorithm, this value is not used."    DEFVAL { 1 }    ::= { copsClientConfigGroup 3 }copsClientServerConfigRetryIntvl OBJECT-TYPE    SYNTAX      TimeInterval    UNITS       "centi-seconds"    MAX-ACCESS  read-write    STATUS      current    DESCRIPTION        "A retry interval for use by the retry algorithm.  Each retry         algorithm needs to specify how it uses this value.         For the 'sequential(2)' algorithm, this value is the time to         wait between retries of a connection to the same COPS server.         For the 'roundRobin(3)' algorithm, the client always attempts         to connect to each Server in turn, until one succeeds or they         all fail; if they all fail, then the client waits for the value         of this interval before restarting the algorithm."    DEFVAL { 1000 }    ::= { copsClientConfigGroup 4 }Smith                       Standards Track                    [Page 19]RFC 2940                    COPS Client MIB                 October 2000-- --------------------------------------------------------------- Conformance Information-- -------------------------------------------------------------copsClientConformance OBJECT IDENTIFIER ::= { copsClientMIB 2 }copsClientGroups OBJECT IDENTIFIER ::= { copsClientConformance 1 }copsClientCompliances OBJECT IDENTIFIER ::= { copsClientConformance 2 }-- --------------------------------------------------------------- units of conformance-- -------------------------------------------------------------copsDeviceStatusGroup OBJECT-GROUP    OBJECTS {        copsClientCapabilities,        copsClientServerTcpPort, copsClientServerType,        copsClientServerAuthType, copsClientServerLastConnAttempt,        copsClientState, copsClientServerKeepaliveTime,        copsClientServerAccountingTime, copsClientInPkts,        copsClientOutPkts, copsClientInErrs, copsClientLastError,        copsClientTcpConnectAttempts, copsClientTcpConnectFailures,        copsClientOpenAttempts, copsClientOpenFailures,        copsClientErrUnsupportClienttype,        copsClientErrUnsupportedVersion, copsClientErrLengthMismatch,        copsClientErrUnknownOpcode, copsClientErrUnknownCnum,        copsClientErrBadCtype, copsClientErrBadSends,        copsClientErrWrongObjects, copsClientErrWrongOpcode,        copsClientKaTimedoutClients, copsClientErrAuthFailures,        copsClientErrAuthMissing    }    STATUS      current    DESCRIPTION        "A collection of objects for monitoring the status of        connections to COPS servers and statistics for a COPS client."    ::= { copsClientGroups 1 }copsDeviceConfigGroup OBJECT-GROUP    OBJECTS {        copsClientServerConfigTcpPort, copsClientServerConfigPriority,        copsClientServerConfigRowStatus,        copsClientServerConfigRetryAlgrm,        copsClientServerConfigRetryCount,        copsClientServerConfigRetryIntvl    }    STATUS      current    DESCRIPTION        "A collection of objects for configuring COPS serverSmith                       Standards Track                    [Page 20]RFC 2940                    COPS Client MIB                 October 2000        information."    ::= { copsClientGroups 2 }-- --------------------------------------------------------------- compliance statements-- -------------------------------------------------------------copsClientCompliance MODULE-COMPLIANCE    STATUS  current    DESCRIPTION        "The compliance statement for device support of

⌨️ 快捷键说明

复制代码Ctrl + C
搜索代码Ctrl + F
全屏模式F11
增大字号Ctrl + =
减小字号Ctrl + -
显示快捷键?