draft-ietf-rap-cops-client-mib-00.txt   draft-ietf-rap-cops-client-mib-01.txt 
Internet Draft A. Smith Internet Draft A. Smith
Expires December 1999 Extreme Networks Expires April 2000 Extreme Networks
draft-ietf-rap-cops-client-mib-00.txt D. Partain draft-ietf-rap-cops-client-mib-01.txt D. Partain
Ericsson Ericsson
J. Seligson J. Seligson
Nortel Networks Nortel Networks
June 1999 October 1999
Definitions of Managed Objects for Common Open Policy Service (COPS) Definitions of Managed Objects for Common Open Policy Service (COPS)
Protocol Clients Protocol Clients
Status of this Memo Status of this Memo
This document is an Internet Draft and is in full conformance with all This document is an Internet Draft and is in full conformance with all
provisions of Section 10 of RFC2026. Internet Drafts are working provisions of Section 10 of RFC2026. Internet Drafts are working
documents of the Internet Engineering Task Force (IETF), its Areas, and documents of the Internet Engineering Task Force (IETF), its Areas, and
its Working Groups. Note that other groups may also distribute working its Working Groups. Note that other groups may also distribute working
skipping to change at page 1, line 33 skipping to change at page 1, line 33
documents at any time. It is not appropriate to use Internet Drafts as documents at any time. It is not appropriate to use Internet Drafts as
reference material or to cite them other than as a "working draft" or reference material or to cite them other than as a "working draft" or
"work in progress." "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
To learn the current status of any Internet-Draft, please check the
"1id-abstracts.txt" listing contained in the Internet-Drafts Shadow
Directories on ftp.ietf.org (US East Coast), nic.nordu.net (Europe),
ftp.isi.edu (US West Coast), or munnari.oz.au (Pacific Rim).
This document is a product of the IETF's RSVP Admission Policy Working This document is a product of the IETF's RSVP Admission Policy Working
Group. Copyright (C) The Internet Society (1999). All Rights Reserved. Group. Copyright (C) The Internet Society (1999). All Rights Reserved.
Abstract Abstract
This memo defines a portion of the Management Information Base (MIB) for This memo defines a portion of the Management Information Base (MIB) for
use with network management protocols in TCP/IP based internets. In use with network management protocols in TCP/IP based internets. In
particular it defines objects for managing a client of the Common Open particular it defines objects for managing a client of the Common Open
Policy Service (COPS) protocol. Policy Service (COPS) protocol.
skipping to change at page 2, line 16 skipping to change at page 2, line 16
The SNMP Management Framework presently consists of five major The SNMP Management Framework presently consists of five major
components: components:
o An overall architecture, described in an Architecture for o An overall architecture, described in an Architecture for
Describing SNMP Management Frameworks [ARCH]. Describing SNMP Management Frameworks [ARCH].
o Mechanisms for describing and naming objects and events for the o Mechanisms for describing and naming objects and events for the
purpose of management. The first version of this Structure of purpose of management. The first version of this Structure of
Management Information (SMI) is called SMIv1 and described in Management Information (SMI) is called SMIv1 and described in
RFC 1155 [V1SMI], RFC 1212 [V1CONCISE] and RFC 1215 [V1TRAPS]. RFC 1155 [V1SMI], STD 16, RFC 1212 [V1CONCISE] and RFC 1215
The second version, called SMIv2, is described in STD 58, RFC [V1TRAPS]. The second version, called SMIv2, is described in
2578 [V2SMI], STD 58, RFC 2579 [V2TC] and STD 58, RFC 2580 STD 58, RFC 2578 [V2SMI], STD 58, RFC 2579 [V2TC] and STD 58,
[V2CONFORM]. RFC 2580 [V2CONFORM].
o Message protocols for transferring management information. The o Message protocols for transferring management information. The
first version of the SNMP message protocol is called SNMPv1 and first version of the SNMP message protocol is called SNMPv1 and
described in RFC 1157 [V1PROTO]. A second version of the SNMP described in STD 15, RFC 1157 [V1PROTO]. A second version of
message protocol, which is not an Internet standards track the SNMP message protocol, which is not an Internet standards
protocol, is called SNMPv2c and described in RFC 1901 track protocol, is called SNMPv2c and described in RFC 1901
[V2COMMUNITY] and RFC 1906 [V2TRANS]. The third version of the [V2COMMUNITY] and RFC 1906 [V2TRANS]. The third version of the
message protocol is called SNMPv3 and described in RFC1906 message protocol is called SNMPv3 and described in RFC1906
[V2TRANS], Message Processing and Dispatching [V3MPC] and User- [V2TRANS], Message Processing and Dispatching [V3MPC] and User-
based Scurity Model [V3USM]. based Scurity Model [V3USM].
o Protocol operations for accessing management information. The o Protocol operations for accessing management information. The
first set of protocol operations and associated PDU formats is first set of protocol operations and associated PDU formats is
described in RFC 1157 [V1PROTO]. A second set of protocol described in STD 15, RFC 1157 [V1PROTO]. A second set of
operations and associated PDU formats is described in RFC 1905 protocol operations and associated PDU formats is described in
[V2PROTO]. RFC 1905 [V2PROTO].
o A set of fundamental applications described in SNMPv3 o A set of fundamental applications described in SNMPv3
Applications [V3APPS] and the view-based access control Applications [V3APPS] and the view-based access control
mechanism described in View-based Access Control Model [V3VACM]. mechanism described in View-based Access Control Model [V3VACM].
A more detailed introduction to the current SNMP Management Framework
can be found in RFC 2570 [V3INTRO].
Managed objects are accessed via a virtual information store, termed the Managed objects are accessed via a virtual information store, termed the
Management Information Base or MIB. Objects in the MIB are defined Management Information Base or MIB. Objects in the MIB are defined
using the mechanisms defined in the SMI. using the mechanisms defined in the SMI.
This memo specifies a MIB module that is compliant to the SMIv2. A MIB This memo specifies a MIB module that is compliant to the SMIv2. A MIB
conforming to the SMIv1 can be produced through the appropriate conforming to the SMIv1 can be produced through the appropriate
translations. The resulting translated MIB must be semantically translations. The resulting translated MIB must be semantically
equivalent, except where objects or events are omitted because no equivalent, except where objects or events are omitted because no
translation is possible (use of Counter64). Some machine readable translation is possible (use of Counter64). Some machine readable
information in SMIv2 will be converted into textual descriptions in information in SMIv2 will be converted into textual descriptions in
SMIv1 during the translation process. However, this loss of machine SMIv1 during the translation process. However, this loss of machine
readable information is not considered to change the semantics of the readable information is not considered to change the semantics of the
MIB. MIB.
2. Overview 2. Overview
The COPS protocol [COPS] is a client-server protocol intended for the The COPS protocol [COPS] is a client-server protocol intended for the
communication of policy requests and decisions between a Policy communication of policy requests and decisions between a Policy
Enforcement Point (PEP) and a Policy Decision Point (PDP). The PEP acts Enforcement Point (PEP) and a Policy Decision Point (PDP). The PEP acts
skipping to change at page 3, line 21 skipping to change at page 3, line 24
The COPS protocol [COPS] is a client-server protocol intended for the The COPS protocol [COPS] is a client-server protocol intended for the
communication of policy requests and decisions between a Policy communication of policy requests and decisions between a Policy
Enforcement Point (PEP) and a Policy Decision Point (PDP). The PEP acts Enforcement Point (PEP) and a Policy Decision Point (PDP). The PEP acts
as a COPS client in this scenario. The model for policy out-sourcing, as a COPS client in this scenario. The model for policy out-sourcing,
of which the COPS protocol provides one part, is described in of which the COPS protocol provides one part, is described in
[FRAMEWORK]. [FRAMEWORK].
2.1. Scope 2.1. Scope
This MIB is intended to provide management of the important This MIB is intended to provide management of the important features of
features of a COPS protocol client module. It does not provide a COPS protocol client module. It does not provide management for a COPS
management for a COPS server - this is outside the scope of the server - this is outside the scope of the current memo. It provides for
current memo. It provides for monitoring of status and protocol monitoring of status and protocol statistics, as well as for
statistics, as well as for configuration of the client, in configuration of the client, in particular for telling it where to
particular for telling it where to locate its servers. Other locate its servers. Other mechanisms for achieving this function without
mechanisms for achieving this function without SNMP configuration SNMP configuration might include use of the Service Location Protocol
might include use of the Service Location Protocol [SRVLOC] [SRVLOC] although this is outside the scope of this memo and are not
although this is outside the scope of this memo and are not
specified by the COPS protocol itself. specified by the COPS protocol itself.
This MIB also does not provide management of specific COPS client- This MIB also does not provide management of specific COPS client-types
types e.g. for use with the RSVP protocol [RSVP][COPSRSVP]. e.g. for use with the RSVP protocol [RSVP][COPSRSVP].
3. Structure of COPS Client MIB 3. Structure of COPS Client MIB
Objects in this MIB are arranged into groups. Each group is organized Objects in this MIB are arranged into groups. Each group is organized
as a set of related objects. The overall structure is described below. as a set of related objects. The overall structure is described below.
3.1. copsClientCapabilitiesGroup 3.1. copsClientCapabilitiesGroup
This group contains objects that represent COPS protocol This group contains objects that represent COPS protocol
capabilities implemented by this COPS client. capabilities implemented by this COPS client.
skipping to change at page 4, line 21 skipping to change at page 4, line 21
restart. restart.
3.3. copsConfigGroup 3.3. copsConfigGroup
This group contains objects that allow for configuration of COPS This group contains objects that allow for configuration of COPS
server addresses and the order to which connections should be server addresses and the order to which connections should be
attempted. attempted.
3.4. Textual Conventions 3.4. Textual Conventions
The datatypes CopsClientState, CopsServerEntryType, CopsErrorCode The datatypes CopsClientState, CopsServerEntryType, CopsErrorCode,
and TcpPort are used as textual conventions in this document. CopsTcpPort and CopsAuthType are used as textual conventions in
These textual conventions have NO effect on either the syntax nor this document. These textual conventions have NO effect on either
the semantics of any managed object. Objects defined using these the syntax nor the semantics of any managed object. Objects
conventions are always encoded by means of the rules that define defined using these conventions are always encoded by means of the
their primitive type. Hence, no changes to the SMI or the SNMP are rules that define their primitive type. Hence, no changes to the
necessary to accommodate these textual conventions which are SMI or the SNMP are necessary to accommodate these textual
adopted merely for the convenience of readers. conventions which are adopted merely for the convenience of
readers.
3.5. Relationship to Other MIBs 3.5. Relationship to Other MIBs
3.5.1. Relationship to the 'system' group 3.5.1. Relationship to the 'system' group
This MIB contains definitions for a single COPS protocol client This MIB contains definitions for a single COPS protocol client
represented by a single SNMP agent and instance of the MIB-2 system represented by a single SNMP agent and instance of the MIB-2 system
group [MIB2]. It does not address the case of multiple co-located group [MIB2]. It does not address the case of multiple co-located
COPS protocol clients. COPS protocol clients.
4. Editorial information 4. Editorial information
<this section will be removed before publication> <this section will be removed before publication>
Owners: JS = John Seligson, AS = Andrew Smith, DP = David Partain
4.1. Open Issues resolved in this draft 4.1. Open Issues resolved in this draft
(2) Addressing of server tables by IP Address is frowned on: should
this be indexed by a client-determined small integer? DONE - added
InetEndpoint indices as recommended by draft-ops-endpoint-
mib-00.txt.
(5) Do we need to be able to configure the security mode for client to
attempt to use to talk to COPS server? DONE - added configuration
object as an index to server configuration table. Added some more
capabilities too.
(9) Added error counters and capabilities associated with security.
4.2. Open Issues resolved in previous drafts
(1) When should per-server counters (e.g. copsClientServerInPkts) be (1) When should per-server counters (e.g. copsClientServerInPkts) be
zeroed? (all) Resolution: see issue (3). zeroed? Resolution: see issue (3).
(3) Should error stats be maintained per-server or is global (3) Should error stats be maintained per-server or is global
sufficient? If per-server then see also issue #1. (all) Resolution: sufficient? If per-server then see also issue #1. Resolution:
everything is per-server but not zero'ed on reconnect. everything is per-server but not zero'ed on reconnect.
(4) Add object to show current security in use (JS). DONE - (4) Add object to show current security in use. DONE -
copsClientServerSecurityMode. copsClientServerSecurityMode.
(6) Add TCP port number to all tables (JS). DONE - (6) Add TCP port number to all tables. DONE - copsClientServerTcpPort,
copsClientServerTcpPort, copsClientServerConfigTcpPort. copsClientServerConfigTcpPort.
(7) Add server retry configuration (JS). DONE - (7) Add server retry configuration. DONE -
copsClientServerConfigRetryCount, copsClientServerConfigRetryCount,
copsClientServerConfigRetryInterval copsClientServerConfigRetryInterval
(8) Add COPS protocol version number capabilities object (JS). DONE - (8) Add COPS protocol version number capabilities object. DONE -
copsClientCapabilities. copsClientCapabilities.
4.2. Still Open Issues 4.3. Still Open Issues
(2) Addressing of server tables by IP Address is frowned on: should
this be indexed by a client-determined small integer? Awaiting
resolution of general SNMP discussion on this topic. (AS)
(5) Do we need to be able to configure the security mode for client to NONE.
attempt to use to talk to COPS server? (AS)
5. Definitions for COPS Client MIB 5. Definitions for COPS Client MIB
COPS-CLIENT-MIB DEFINITIONS ::= BEGIN COPS-CLIENT-MIB DEFINITIONS ::= BEGIN
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- ------------------------------------------------------------- -- -------------------------------------------------------------
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, Counter32, IpAddress, Integer32 MODULE-IDENTITY, OBJECT-TYPE, Counter32, Integer32
FROM SNMPv2-SMI FROM SNMPv2-SMI
TimeStamp, TimeInterval, RowStatus, TEXTUAL-CONVENTION TimeStamp, TimeInterval, RowStatus, TEXTUAL-CONVENTION
FROM SNMPv2-TC FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF; FROM SNMPv2-CONF
InetEndpointType, InetEndpoint
FROM INET-ENDPOINT-MIB;
-- REFERENCE -- REFERENCE
-- "The COPS (Common Open Policy Service) Protocol -- "The COPS (Common Open Policy Service) Protocol
-- draft-ietf-rap-cops-07.txt"
copsClientMIB MODULE-IDENTITY copsClientMIB MODULE-IDENTITY
LAST-UPDATED "9906100000Z" LAST-UPDATED "9910210000Z"
ORGANIZATION "IETF RSVP Admission Policy Working Group" ORGANIZATION "IETF RSVP Admission Policy Working Group"
CONTACT-INFO CONTACT-INFO
" Andrew Smith (WG co-chair) " Andrew Smith (WG co-chair)
Phone: +1 408 579 2821 Phone: +1 408 579 2821
Email: andrew@extremenetworks.com Email: andrew@extremenetworks.com
Tim O'Malley (WG co-chair) Tim O'Malley (WG co-chair)
Phone: +1 617 873 3076 Phone: +1 617 873 3076
Email: timo@bbn.com" Email: timo@bbn.com
Editor: Andrew Smith
Phone: +1 408 579 2821
Email: andrew@extremenetworks.com
Editor: David Partain
Phone: +46 13 28 41 44
Email: David.Partain@ericsson.com
Editor: John Seligson
Phone: +1 408 495 2992
Email: jseligso@nortelnetworks.com"
DESCRIPTION DESCRIPTION
"The COPS Client MIB module" "The COPS Client MIB module"
REVISION "9910210000Z"
DESCRIPTION "This version published as draft-ietf-rap-cops-client-mib-01."
::= { xxx 1 } ::= { xxx 1 }
copsClientMIBObjects OBJECT IDENTIFIER ::= { copsClientMIB 1 } copsClientMIBObjects OBJECT IDENTIFIER ::= { copsClientMIB 1 }
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- Textual Conventions -- Textual Conventions
-- ------------------------------------------------------------- -- -------------------------------------------------------------
CopsClientState ::= TEXTUAL-CONVENTION CopsClientState ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A value indicating the state of a COPS client." "A value indicating the state of a COPS client."
SYNTAX INTEGER { SYNTAX INTEGER {
copsClientInvalid(1), -- default state. copsClientInvalid(1), -- default state.
copsClientTcpconnected(2), -- TCP connection up but COPS copsClientTcpconnected(2), -- TCP connection up but COPS
-- not yet open. -- not yet open.
copsClientAccepted(3), -- COPS server accepted the client copsClientAuthenticating(3), -- TCP connection up but still
copsClientTimingout(4) -- Keepalive timer has expired, -- authenticating.
copsClientSecAccepted(4), -- connection authenticated.
copsClientAccepted(5), -- COPS server accepted the client.
copsClientTimingout(6) -- Keepalive timer has expired,
-- client is in process of tearing -- client is in process of tearing
-- down connection -- down connection.
} }
CopsServerEntryType ::= TEXTUAL-CONVENTION CopsServerEntryType ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A value indicating how a COPS server entry came into existence." "A value indicating how a COPS server entry came into existence."
SYNTAX INTEGER { SYNTAX INTEGER {
copsServerStatic(1), -- configured by manager copsServerStatic(1), -- configured by manager
copsServerRedirect(2) -- notified by COPS server copsServerRedirect(2) -- notified by COPS server
} }
skipping to change at page 7, line 43 skipping to change at page 8, line 20
errorBadMessageFormat(3), errorBadMessageFormat(3),
errorUnableToProcess(4), errorUnableToProcess(4),
errorMandatoryClientSiMissing(5), errorMandatoryClientSiMissing(5),
errorUnsupportedClientType(6), errorUnsupportedClientType(6),
errorMandatoryCopsObjectMissing(7), errorMandatoryCopsObjectMissing(7),
errorClientFailure(8), errorClientFailure(8),
errorCommunicationFailure(9), errorCommunicationFailure(9),
errorUnspecified(10), -- client-type specific subcode errorUnspecified(10), -- client-type specific subcode
errorShuttingDown(11), errorShuttingDown(11),
errorRedirectToPreferredServer(12), errorRedirectToPreferredServer(12),
errorUnknownCopsObject(13) errorUnknownCopsObject(13),
errorAuthenticationFailure(14),
errorAuthenticationMissing(15)
} }
-- REFERENCE -- REFERENCE
-- "COPS section 2.2.8" -- "COPS section 2.2.8"
TcpPort ::= TEXTUAL-CONVENTION CopsTcpPort ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A value indicating a TCP protocol port number." "A value indicating a TCP protocol port number."
SYNTAX INTEGER (0..65535) SYNTAX INTEGER (0..65535)
CopsAuthType ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"A value indicating a type of security authentication mechanism."
SYNTAX INTEGER {
authNone(0),
authOther(1),
authIpSecAh(2),
authIpSecEsp(3),
authTls(4),
authCopsIntegrity(5)
}
-- ------------------------------------------------------------- -- -------------------------------------------------------------
copsClientCapabilitiesGroup OBJECT IDENTIFIER copsClientCapabilitiesGroup OBJECT IDENTIFIER
::= { copsClientMIBObjects 1 } ::= { copsClientMIBObjects 1 }
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- --
-- Capabilities of the COPS client to connect to a COPS server:
-- --
copsClientCapabilities OBJECT-TYPE copsClientCapabilities OBJECT-TYPE
SYNTAX BITS { SYNTAX BITS {
copsClientVersion1(0), -- supports version1 of the COPS protocol copsClientVersion1(0), -- supports version1 of COPS protocol
copsClientIpSec(1) -- supports IP-SEC connections to COPS server copsClientAuthIpSecAh(1) , -- supports IP-SEC Authentication
copsClientAuthIpSecEsp(2), -- supports IP-SEC Encryption
copsClientAuthTls(3), -- supports Transport-Layer Security
copsClientAuthInteg(4) -- supports COPS Integrity
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A list of the optional capabilities that this COPS client "A list of the optional capabilities that this COPS client
supports." supports."
::= { copsClientCapabilitiesGroup 1 } ::= { copsClientCapabilitiesGroup 1 }
-- ------------------------------------------------------------- -- -------------------------------------------------------------
skipping to change at page 9, line 15 skipping to change at page 10, line 9
::= { copsClientStatusGroup 1 } ::= { copsClientStatusGroup 1 }
copsClientServerCurrentEntry OBJECT-TYPE copsClientServerCurrentEntry OBJECT-TYPE
SYNTAX CopsClientServerCurrentEntry SYNTAX CopsClientServerCurrentEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A set of information regarding a single COPS server serving "A set of information regarding a single COPS server serving
a single COPS Client-Type from the point of view of a COPS a single COPS Client-Type from the point of view of a COPS
client." client."
INDEX { copsClientServerIpAddress, copsClientServerClientType } INDEX { copsClientServerAddressType, copsClientServerAddress,
copsClientServerClientType }
::= { copsClientServerCurrentTable 1 } ::= { copsClientServerCurrentTable 1 }
CopsClientServerCurrentEntry ::= CopsClientServerCurrentEntry ::=
SEQUENCE { SEQUENCE {
copsClientServerIpAddress IpAddress, copsClientServerAddressType InetEndpointType,
copsClientServerAddress InetEndpoint,
copsClientServerClientType INTEGER, copsClientServerClientType INTEGER,
copsClientServerTcpPort TcpPort, copsClientServerTcpPort CopsTcpPort,
copsClientServerType CopsServerEntryType, copsClientServerType CopsServerEntryType,
copsClientServerSecurityMode INTEGER, copsClientServerAuthType CopsAuthType,
copsClientServerLastConnectAttempt TimeStamp, copsClientServerLastConnectAttempt TimeStamp,
copsClientState CopsClientState, copsClientState CopsClientState,
copsClientServerKeepaliveTime TimeInterval, copsClientServerKeepaliveTime TimeInterval,
copsClientServerAccountingTime TimeInterval, copsClientServerAccountingTime TimeInterval,
copsClientInPkts Counter32, copsClientInPkts Counter32,
copsClientOutPkts Counter32, copsClientOutPkts Counter32,
copsClientInErrs Counter32, copsClientInErrs Counter32,
copsClientLastError CopsErrorCode, copsClientLastError CopsErrorCode,
copsClientTcpConnectAttempts Counter32, copsClientTcpConnectAttempts Counter32,
copsClientTcpConnectFailures Counter32, copsClientTcpConnectFailures Counter32,
skipping to change at page 9, line 46 skipping to change at page 10, line 42
copsClientOpenFailures Counter32, copsClientOpenFailures Counter32,
copsClientErrUnsupportedClienttype Counter32, copsClientErrUnsupportedClienttype Counter32,
copsClientErrUnsupportedVersion Counter32, copsClientErrUnsupportedVersion Counter32,
copsClientErrLengthMismatch Counter32, copsClientErrLengthMismatch Counter32,
copsClientErrUnknownOpcode Counter32, copsClientErrUnknownOpcode Counter32,
copsClientErrUnknownCnum Counter32, copsClientErrUnknownCnum Counter32,
copsClientErrBadCtype Counter32, copsClientErrBadCtype Counter32,
copsClientErrBadSends Counter32, copsClientErrBadSends Counter32,
copsClientErrWrongObjects Counter32, copsClientErrWrongObjects Counter32,
copsClientErrWrongOpcode Counter32, copsClientErrWrongOpcode Counter32,
copsClientKaTimedoutClients Counter32 copsClientKaTimedoutClients Counter32,
copsClientErrAuthFailures Counter32,
copsClientErrAuthMissing Counter32
} }
copsClientServerIpAddress OBJECT-TYPE copsClientServerAddressType OBJECT-TYPE
SYNTAX IpAddress SYNTAX InetEndpointType
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The address of a COPS Server. It is assumed that the "The type of address in copsClientServerAddress."
COPS service will be provided on the well-known COPS ::= { copsClientServerCurrentEntry 1 }
protocol port number."
copsClientServerAddress OBJECT-TYPE
SYNTAX InetEndpoint
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 REFERENCE
"COPS section 2.3" "COPS section 2.3"
::= { copsClientServerCurrentEntry 1 } ::= { copsClientServerCurrentEntry 2 }
copsClientServerClientType OBJECT-TYPE copsClientServerClientType OBJECT-TYPE
SYNTAX INTEGER (0..65535) SYNTAX INTEGER (0..65535)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The COPS protocol Client-Type for which this entry "The COPS protocol Client-Type for which this entry
applies. Multiple Client-Types can be served by a single applies. Multiple Client-Types can be served by a single
COPS server." COPS server."
REFERENCE REFERENCE
"COPS section 6, IANA" "COPS section 6, IANA"
::= { copsClientServerCurrentEntry 2 } ::= { copsClientServerCurrentEntry 3 }
copsClientServerTcpPort OBJECT-TYPE copsClientServerTcpPort OBJECT-TYPE
SYNTAX TcpPort SYNTAX CopsTcpPort
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The TCP port number on the COPS server to which the "The TCP port number on the COPS server to which the
client is connected." client should connect."
::= { copsClientServerCurrentEntry 3 } ::= { copsClientServerCurrentEntry 4 }
copsClientServerType OBJECT-TYPE copsClientServerType OBJECT-TYPE
SYNTAX CopsServerEntryType SYNTAX CopsServerEntryType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicator of the source of this COPS server information. "Indicator of the source of this COPS server information.
COPS servers may be configured by network management COPS servers may be configured by network management
into copsClientServerConfigTable and appear in this entry into copsClientServerConfigTable and appear in this entry
with type copsServerStatic(1). Alternatively, the may be with type copsServerStatic(1). Alternatively, the may be
notified from another COPS server by means of the COPS notified from another COPS server by means of the COPS
PDP-Redirect mechanism and appear as copsServerRedirect(2)." PDP-Redirect mechanism and appear as copsServerRedirect(2)."
::= { copsClientServerCurrentEntry 4 } ::= { copsClientServerCurrentEntry 5 }
copsClientServerSecurityMode OBJECT-TYPE copsClientServerAuthType OBJECT-TYPE
SYNTAX INTEGER { other(1), unknown(2), noSec(3), ipSec(4) } SYNTAX CopsAuthType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicator of the current security mode in use between "Indicator of the current security mode in use between
client and this COPS server." client and this COPS server."
::= { copsClientServerCurrentEntry 5 } ::= { copsClientServerCurrentEntry 6 }
copsClientServerLastConnectAttempt OBJECT-TYPE copsClientServerLastConnectAttempt OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Timestamp of the last time that this client attempted to "Timestamp of the last time that this client attempted to
connect to this COPS server." connect to this COPS server."
::= { copsClientServerCurrentEntry 6 } ::= { copsClientServerCurrentEntry 7 }
copsClientState OBJECT-TYPE copsClientState OBJECT-TYPE
SYNTAX CopsClientState SYNTAX CopsClientState
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The state of the connection and COPS protocol with respect "The state of the connection and COPS protocol with respect
to this COPS server." to this COPS server."
::= { copsClientServerCurrentEntry 7 } ::= { copsClientServerCurrentEntry 8 }
copsClientServerKeepaliveTime OBJECT-TYPE copsClientServerKeepaliveTime OBJECT-TYPE
SYNTAX TimeInterval SYNTAX TimeInterval
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of the COPS protocol Keepalive timeout, in "The value of the COPS protocol Keepalive timeout, in
centiseconds, currently in use by this client, as centiseconds, currently in use by this client, as
specified by this COPS server in the Client-Accept operation. specified by this COPS server in the Client-Accept operation.
A value of zero indicates no keepalive activity is expected." A value of zero indicates no keepalive activity is expected."
REFERENCE REFERENCE
"COPS section 3.7, 4.4" "COPS section 3.7, 4.4"
::= { copsClientServerCurrentEntry 8 } ::= { copsClientServerCurrentEntry 9 }
copsClientServerAccountingTime OBJECT-TYPE copsClientServerAccountingTime OBJECT-TYPE
SYNTAX TimeInterval SYNTAX TimeInterval
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of the COPS protocol Accounting timeout, in "The value of the COPS protocol Accounting timeout, in
centiseconds, currently in use by this client, as specified centiseconds, currently in use by this client, as specified
by the COPS server in the Client-Accept operation. A value by the COPS server in the Client-Accept operation. A value
of zero indicates no accounting activity is to be performed." of zero indicates no accounting activity is to be performed."
REFERENCE REFERENCE
"COPS section 3.7" "COPS section 3.7"
::= { copsClientServerCurrentEntry 9 } ::= { copsClientServerCurrentEntry 10 }
copsClientInPkts OBJECT-TYPE copsClientInPkts OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A count of the total number of COPS packets that this client has "A count of the total number of COPS packets that this client has
received from this COPS server. This value is cumulative since received from this COPS server. This value is cumulative since
agent restart and is not zeroed on new connections." agent restart and is not zeroed on new connections."
::= { copsClientServerCurrentEntry 10 } ::= { copsClientServerCurrentEntry 11 }
copsClientOutPkts OBJECT-TYPE copsClientOutPkts OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A count of the total number of COPS packets that this client has "A count of the total number of COPS packets that this client has
sent to this COPS server. This value is cumulative since agent sent to this COPS server. This value is cumulative since agent
restart and is not zeroed on new connections." restart and is not zeroed on new connections."
::= { copsClientServerCurrentEntry 11 } ::= { copsClientServerCurrentEntry 12 }
copsClientInErrs OBJECT-TYPE copsClientInErrs OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A count of the total number of COPS packets that this client has "A count of the total number of COPS packets that this client has
received from this COPS server that contained errors in syntax. received from this COPS server that contained errors in syntax.
This value is cumulative since agent restart and is not zeroed on This value is cumulative since agent restart and is not zeroed on
new connections." new connections."
::= { copsClientServerCurrentEntry 12 } ::= { copsClientServerCurrentEntry 13 }
copsClientLastError OBJECT-TYPE copsClientLastError OBJECT-TYPE
SYNTAX CopsErrorCode SYNTAX CopsErrorCode
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The code contained in the last COPS protocol Error Object "The code contained in the last COPS protocol Error Object
received by this client from this COPS server. This value is received by this client from this COPS server. This value is
not zeroed on COPS Client-Open operations." not zeroed on COPS Client-Open operations."
REFERENCE REFERENCE
"COPS section 2.2.8" "COPS section 2.2.8"
::= { copsClientServerCurrentEntry 13 } ::= { copsClientServerCurrentEntry 14 }
copsClientTcpConnectAttempts OBJECT-TYPE copsClientTcpConnectAttempts OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A count of the number of times that this COPS client has tried "A count of the number of times that this COPS client has tried
to open an TCP connection to a COPS server. This value is to open an TCP connection to a COPS server. This value is
cumulative since agent restart and is not zeroed on new cumulative since agent restart and is not zeroed on new
connections." connections."
::= { copsClientServerCurrentEntry 14 } ::= { copsClientServerCurrentEntry 15 }
copsClientTcpConnectFailures OBJECT-TYPE copsClientTcpConnectFailures OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A count of the number of times that this COPS client has failed "A count of the number of times that this COPS client has failed
to open an TCP connection to a COPS server. This value is to open an TCP connection to a COPS server. This value is
cumulative since agent restart and is not zeroed on new cumulative since agent restart and is not zeroed on new
connections." connections."
::= { copsClientServerCurrentEntry 15 } ::= { copsClientServerCurrentEntry 16 }
copsClientOpenAttempts OBJECT-TYPE copsClientOpenAttempts OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A count of the number of times that this COPS client has tried "A count of the number of times that this COPS client has tried
to perform a COPS Client-Open to a COPS server. This value is to perform a COPS Client-Open to a COPS server. This value is
cumulative since agent restart and is not zeroed on new cumulative since agent restart and is not zeroed on new
connections." connections."
::= { copsClientServerCurrentEntry 16 } ::= { copsClientServerCurrentEntry 17 }
copsClientOpenFailures OBJECT-TYPE copsClientOpenFailures OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A count of the number of times that this COPS client has failed "A count of the number of times that this COPS client has failed
to perform a COPS Client-Open to a COPS server. This value is to perform a COPS Client-Open to a COPS server. This value is
cumulative since agent restart and is not zeroed on new cumulative since agent restart and is not zeroed on new
connections." connections."
::= { copsClientServerCurrentEntry 17 } ::= { copsClientServerCurrentEntry 18 }
copsClientErrUnsupportedClienttype OBJECT-TYPE copsClientErrUnsupportedClienttype OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A count of the total number of COPS packets that this client has "A count of the total number of COPS packets that this client has
received from COPS servers that referred to Client-Types that are received from COPS servers that referred to Client-Types that are
unsupported by this client. This value is cumulative unsupported by this client. This value is cumulative
since agent restart and is not zeroed on new connections." since agent restart and is not zeroed on new connections."
::= { copsClientServerCurrentEntry 18 } ::= { copsClientServerCurrentEntry 19 }
copsClientErrUnsupportedVersion OBJECT-TYPE copsClientErrUnsupportedVersion OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A count of the total number of COPS packets that this client has "A count of the total number of COPS packets that this client has
received from COPS servers that had a COPS protocol Version received from COPS servers that had a COPS protocol Version
number that is unsupported by this client. This value is number that is unsupported by this client. This value is
cumulative since agent restart and is not zeroed on new cumulative since agent restart and is not zeroed on new
connections." connections."
::= { copsClientServerCurrentEntry 19 } ::= { copsClientServerCurrentEntry 20 }
copsClientErrLengthMismatch OBJECT-TYPE copsClientErrLengthMismatch OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A count of the total number of COPS packets that this client has "A count of the total number of COPS packets that this client has
received from COPS servers that had a COPS protocol Message received from COPS servers that had a COPS protocol Message
Length that did not match the actual received packet. This value Length that did not match the actual received packet. This value
is cumulative since agent restart and is not zeroed on new is cumulative since agent restart and is not zeroed on new
connections." connections."
::= { copsClientServerCurrentEntry 20 } ::= { copsClientServerCurrentEntry 21 }
copsClientErrUnknownOpcode OBJECT-TYPE copsClientErrUnknownOpcode OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A count of the total number of COPS packets that this client has "A count of the total number of COPS packets that this client has
received from COPS servers that had a COPS protocol Op Code that received from COPS servers that had a COPS protocol Op Code that
was unrecognised by this client. This value is cumulative was unrecognised by this client. This value is cumulative
since agent restart and is not zeroed on new connections." since agent restart and is not zeroed on new connections."
::= { copsClientServerCurrentEntry 21 } ::= { copsClientServerCurrentEntry 22 }
copsClientErrUnknownCnum OBJECT-TYPE copsClientErrUnknownCnum OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A count of the total number of COPS packets that this client has "A count of the total number of COPS packets that this client has
received from COPS servers that contained a COPS protocol object received from COPS servers that contained a COPS protocol object
C-Num that was unrecognised by this client. This value is C-Num that was unrecognised by this client. This value is
cumulative since agent restart and is not zeroed on new cumulative since agent restart and is not zeroed on new
connections." connections."
::= { copsClientServerCurrentEntry 22 } ::= { copsClientServerCurrentEntry 23 }
copsClientErrBadCtype OBJECT-TYPE copsClientErrBadCtype OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A count of the total number of COPS packets that this client has "A count of the total number of COPS packets that this client has
received from COPS servers that contained a COPS protocol object received from COPS servers that contained a COPS protocol object
C-Type that was not defined for the C-Nums known by this client. 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 This value is cumulative since agent restart and is not zeroed on
new connections." new connections."
::= { copsClientServerCurrentEntry 23 } ::= { copsClientServerCurrentEntry 24 }
copsClientErrBadSends OBJECT-TYPE copsClientErrBadSends OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A count of the total number of COPS packets that this client "A count of the total number of COPS packets that this client
attempted to send to COPS servers that resulted in a transmit attempted to send to COPS servers that resulted in a transmit
error. This value is cumulative since agent restart and is not error. This value is cumulative since agent restart and is not
zeroed on new connections." zeroed on new connections."
::= { copsClientServerCurrentEntry 24 } ::= { copsClientServerCurrentEntry 25 }
copsClientErrWrongObjects OBJECT-TYPE copsClientErrWrongObjects OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A count of the total number of COPS packets that this client has "A count of the total number of COPS packets that this client has
received from COPS servers that did not contain a permitted set received from COPS servers that did not contain a permitted set
of COPS protocol objects. This value is cumulative since agent of COPS protocol objects. This value is cumulative since agent
restart and is not zeroed on new connections." restart and is not zeroed on new connections."
::= { copsClientServerCurrentEntry 25 } ::= { copsClientServerCurrentEntry 26 }
copsClientErrWrongOpcode OBJECT-TYPE copsClientErrWrongOpcode OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A count of the total number of COPS packets that this client has "A count of the total number of COPS packets that this client has
received from COPS servers that had a COPS protocol Op Code that received from COPS servers that had a COPS protocol Op Code that
should not have been sent to a COPS client e.g. Open-Requests. should not have been sent to a COPS client e.g. Open-Requests.
This value is cumulative since agent restart and is not zeroed This value is cumulative since agent restart and is not zeroed
on new connections." on new connections."
::= { copsClientServerCurrentEntry 26 } ::= { copsClientServerCurrentEntry 27 }
copsClientKaTimedoutClients OBJECT-TYPE copsClientKaTimedoutClients OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A count of the total number of times that this client has "A count of the total number of times that this client has
been shut down by COPS servers that had detected a COPS protocol been shut down by COPS servers that had detected a COPS protocol
Keepalive timeout. This value is cumulative since agent restart Keepalive timeout. This value is cumulative since agent restart
and is not zeroed on new connections." and is not zeroed on new connections."
::= { copsClientServerCurrentEntry 27 } ::= { copsClientServerCurrentEntry 28 }
copsClientErrAuthFailures 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 packet 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 packet which did not contain authentication
information."
::= { copsClientServerCurrentEntry 30 }
-- ------------------------------------------------------------- -- -------------------------------------------------------------
copsClientConfigGroup OBJECT IDENTIFIER ::= { copsClientMIBObjects 3 } copsClientConfigGroup OBJECT IDENTIFIER ::= { copsClientMIBObjects 3 }
-- ------------------------------------------------------------- -- -------------------------------------------------------------
copsClientServerConfigTable OBJECT-TYPE copsClientServerConfigTable OBJECT-TYPE
SYNTAX SEQUENCE OF CopsClientServerConfigEntry SYNTAX SEQUENCE OF CopsClientServerConfigEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Table of possible COPS servers to try to connect to in order "Table of possible COPS servers to try to connect to in order
of copsClientServerConfigPriority. Note that a PDPRedirect of copsClientServerConfigPriority. There may be multiple
always takes precedence over any locally configured priority." 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 } ::= { copsClientConfigGroup 1 }
copsClientServerConfigEntry OBJECT-TYPE copsClientServerConfigEntry OBJECT-TYPE
SYNTAX CopsClientServerConfigEntry SYNTAX CopsClientServerConfigEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A set of configuration information regarding a single "A set of configuration information regarding a single
COPS server from the point of view of a COPS client." COPS server from the point of view of a COPS client."
INDEX { copsClientServerConfigIpAddress, INDEX { copsClientServerConfigAddressType,
copsClientServerConfigClientType } copsClientServerConfigAddress,
copsClientServerConfigClientType,
copsClientServerConfigAuthType }
::= { copsClientServerConfigTable 1 } ::= { copsClientServerConfigTable 1 }
CopsClientServerConfigEntry ::= CopsClientServerConfigEntry ::=
SEQUENCE { SEQUENCE {
copsClientServerConfigIpAddress IpAddress, copsClientServerConfigAddressType InetEndpointType,
copsClientServerConfigAddress InetEndpoint,
copsClientServerConfigClientType INTEGER, copsClientServerConfigClientType INTEGER,
copsClientServerConfigTcpPort TcpPort, copsClientServerConfigAuthType CopsAuthType,
copsClientServerConfigTcpPort CopsTcpPort,
copsClientServerConfigPriority Integer32, copsClientServerConfigPriority Integer32,
copsClientServerConfigRetryCount Integer32, copsClientServerConfigRetryCount Integer32,
copsClientServerConfigRetryInterval TimeInterval, copsClientServerConfigRetryInterval TimeInterval,
copsClientServerConfigRowStatus RowStatus copsClientServerConfigRowStatus RowStatus
} }
copsClientServerConfigIpAddress OBJECT-TYPE copsClientServerConfigAddressType OBJECT-TYPE
SYNTAX IpAddress SYNTAX InetEndpointType
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The address of a COPS Server. It is assumed that the "The type of address in copsClientServerconfigAddress."
COPS service will be provided on the well-known COPS ::= { copsClientServerConfigEntry 1 }
protocol port number."
copsClientServerConfigAddress OBJECT-TYPE
SYNTAX InetEndpoint
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 REFERENCE
"COPS section 2.3" "COPS section 2.3"
::= { copsClientServerConfigEntry 1 } ::= { copsClientServerConfigEntry 2 }
copsClientServerConfigClientType OBJECT-TYPE copsClientServerConfigClientType OBJECT-TYPE
SYNTAX INTEGER (0..65535) SYNTAX INTEGER (0..65535)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The COPS protocol Client-Type for which this entry "The COPS protocol Client-Type for which this entry
applies and for which this COPS server is capable applies and for which this COPS server is capable
of serving. Multiple Client-Types can be served by a of serving. Multiple Client-Types can be served by a
single COPS server." single COPS server."
REFERENCE REFERENCE
"COPS section 6, IANA" "COPS section 6, IANA"
::= { copsClientServerConfigEntry 2 } ::= { 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
"COPS section 4."
::= { copsClientServerConfigEntry 4 }
copsClientServerConfigTcpPort OBJECT-TYPE copsClientServerConfigTcpPort OBJECT-TYPE
SYNTAX TcpPort SYNTAX CopsTcpPort
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The TCP port number on the COPS server to which the "The TCP port number on the COPS server to which the
client should connect." client should connect."
::= { copsClientServerConfigEntry 3 } ::= { copsClientServerConfigEntry 5 }
copsClientServerConfigPriority OBJECT-TYPE copsClientServerConfigPriority OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The priority of this entry relative to other entries. "The priority of this entry relative to other entries.
COPS client will attempt to contact COPS servers for the COPS client will attempt to contact COPS servers for the
appropriate Client-Type in the order of their priority appropriate Client-Type in the order of their priority
values. The order to be used amongst server entries with values. The order to be used amongst server entries with
the same priority is undefined. COPS servers that are the same priority is undefined. COPS servers that are
notified to the client using the COPS protocol PDP-Redirect notified to the client using the COPS protocol PDP-Redirect
mechanism are always used in preference to any entries in mechanism are always used in preference to any entries in
this table." this table."
::= { copsClientServerConfigEntry 4 } ::= { copsClientServerConfigEntry 6 }
copsClientServerConfigRetryCount OBJECT-TYPE copsClientServerConfigRetryCount OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of times the client should retry to connect "The number of times the client should retry to connect
to this COPS server before moving on to another server." to this COPS server before moving on to another server."
DEFVAL { 1 } DEFVAL { 1 }
::= { copsClientServerConfigEntry 5 } ::= { copsClientServerConfigEntry 7 }
copsClientServerConfigRetryInterval OBJECT-TYPE copsClientServerConfigRetryInterval OBJECT-TYPE
SYNTAX TimeInterval SYNTAX TimeInterval
UNITS "centi-seconds" UNITS "centi-seconds"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The time to wait between retrying to connect to "The time to wait between retrying to connect to
this COPS server." this COPS server."
DEFVAL { 1000 } DEFVAL { 1000 }
::= { copsClientServerConfigEntry 6 } ::= { copsClientServerConfigEntry 8 }
copsClientServerConfigRowStatus OBJECT-TYPE copsClientServerConfigRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"State of this entry in the table." "State of this entry in the table."
::= { copsClientServerConfigEntry 7 } ::= { copsClientServerConfigEntry 9 }
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- Conformance Information -- Conformance Information
-- ------------------------------------------------------------- -- -------------------------------------------------------------
copsClientConformance OBJECT IDENTIFIER ::= { copsClientMIB 2 } copsClientConformance OBJECT IDENTIFIER ::= { copsClientMIB 2 }
copsClientGroups OBJECT IDENTIFIER ::= { copsClientConformance 1 } copsClientGroups OBJECT IDENTIFIER ::= { copsClientConformance 1 }
copsClientCompliances OBJECT IDENTIFIER ::= { copsClientConformance 2 } copsClientCompliances OBJECT IDENTIFIER ::= { copsClientConformance 2 }
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- units of conformance -- units of conformance
-- ------------------------------------------------------------- -- -------------------------------------------------------------
copsDeviceStatusGroup OBJECT-GROUP copsDeviceStatusGroup OBJECT-GROUP
OBJECTS { OBJECTS {
copsClientCapabilities, copsClientCapabilities,
copsClientServerTcpPort, copsClientServerType, copsClientServerTcpPort, copsClientServerType,
copsClientServerSecurityMode, copsClientServerLastConnectAttempt, copsClientServerAuthType, copsClientServerLastConnectAttempt,
copsClientState, copsClientServerKeepaliveTime, copsClientState, copsClientServerKeepaliveTime,
copsClientServerAccountingTime, copsClientInPkts, copsClientServerAccountingTime, copsClientInPkts,
copsClientOutPkts, copsClientInErrs, copsClientLastError, copsClientOutPkts, copsClientInErrs, copsClientLastError,
copsClientTcpConnectAttempts, copsClientTcpConnectFailures, copsClientTcpConnectAttempts, copsClientTcpConnectFailures,
copsClientOpenAttempts, copsClientOpenFailures, copsClientOpenAttempts, copsClientOpenFailures,
copsClientErrUnsupportedClienttype, copsClientErrUnsupportedClienttype,
copsClientErrUnsupportedVersion, copsClientErrLengthMismatch, copsClientErrUnsupportedVersion, copsClientErrLengthMismatch,
copsClientErrUnknownOpcode, copsClientErrUnknownCnum, copsClientErrUnknownOpcode, copsClientErrUnknownCnum,
copsClientErrBadCtype, copsClientErrBadSends, copsClientErrBadCtype, copsClientErrBadSends,
copsClientErrWrongObjects, copsClientErrWrongOpcode, copsClientErrWrongObjects, copsClientErrWrongOpcode,
skipping to change at page 21, line 25 skipping to change at page 23, line 40
DESCRIPTION DESCRIPTION
"Write access is required only if the device supports the "Write access is required only if the device supports the
configuration of COPS server information." configuration of COPS server information."
::= { copsClientCompliances 1 } ::= { copsClientCompliances 1 }
END END
6. Acknowledgments 6. Acknowledgments
This document documents the client side of the COPS protocol which was This document describes instrumentation for the client side of the COPS
defined by the RSVP Admission Policy Working Group. protocol which was defined by the RSVP Admission Policy Working Group.
7. Security Considerations 7. Security Considerations
There are a number of management objects defined in this MIB that have a There are a number of management objects defined in this MIB that have a
MAX-ACCESS clause of read-write and/or read-create. Such objects may be MAX-ACCESS clause of read-create. Such objects may be considered
considered sensitive or vulnerable in some network environments. The
support for SET operations in a non-secure environment without proper sensitive or vulnerable in some network environments. The support for
protection can have a negative effect on network operations. SET operations in a non-secure environment without proper protection can
have a negative effect on network operations.
SNMPv1 by itself is not a secure environment. Even if the network SNMPv1 by itself is not a secure environment. Even if the network
itself is secure (for example by using IPSec), even then, there is no itself is secure (for example by using IPSec), even then, there is no
control as to who on the secure network is allowed to access and GET/SET control as to who on the secure network is allowed to access and GET/SET
(read/change/create/delete) the objects in this MIB. (read/change/create/delete) the objects in this MIB.
It is recommended that the implementers consider the security features It is recommended that the implementers consider the security features
as provided by the SNMPv3 framework. Specifically, the use of the User- as provided by the SNMPv3 framework. Specifically, the use of the User-
based Security Model [USM] and the View-based Access Control Model based Security Model [USM] and the View-based Access Control Model
[VACM] is recommended. [VACM] is recommended.
skipping to change at page 24, line 24 skipping to change at page 26, line 35
1213, March 1991. 1213, March 1991.
[FRAMEWORK] [FRAMEWORK]
Yavatkar, R., Pendarakis, D. and Guerin, R., "A Framework for Yavatkar, R., Pendarakis, D. and Guerin, R., "A Framework for
Policy-based Admission Control", Internet Draft, May 1999. Policy-based Admission Control", Internet Draft, May 1999.
http://www.ietf.org/internet-drafts/draft-ietf-rap-framework-03.txt http://www.ietf.org/internet-drafts/draft-ietf-rap-framework-03.txt
[COPS] [COPS]
Boyle, J., Cohen, R., Durham, D., Herzog, S., Rajan, R. and Sastry, Boyle, J., Cohen, R., Durham, D., Herzog, S., Rajan, R. and Sastry,
A., "The COPS (Common Open Policy Service) Protocol", Internet A., "The COPS (Common Open Policy Service) Protocol", Internet
Draft, February 1999. http://www.ietf.org/internet-drafts/draft- Draft, August 1999. http://www.ietf.org/internet-drafts/draft-
ietf-rap-cops-06.txt ietf-rap-cops-07.txt
[RSVP] [RSVP]
Braden, R. ed. et al., "Resource ReSerVation Protocol (RSVP) Braden, R. ed. et al., "Resource ReSerVation Protocol (RSVP)
Version 1 - Functional Specification", RFC 2205, September 1997. Version 1 - Functional Specification", RFC 2205, September 1997.
[COPSRSVP] [COPSRSVP]
Boyle, J., Cohen, R., Durham, D., Herzog, S., Rajan, R. and Sastry, Boyle, J., Cohen, R., Durham, D., Herzog, S., Rajan, R. and Sastry,
A., "COPS Usage for RSVP", Internet Draft, February 1999. A., "COPS Usage for RSVP", Internet Draft, June 1999.
http://www.ietf.org/internet-drafts/draft-ietf-rap-cops-rsvp-04.txt http://www.ietf.org/internet-drafts/draft-ietf-rap-cops-rsvp-05.txt
[SRVLOC] [SRVLOC]
Guttman, E., Perkins, C., Veizades, J., Day, M., "Service Location Guttman, E., Perkins, C., Veizades, J., Day, M., "Service Location
Protocol, Version 2", Internet Draft, April 1999. Protocol, Version 2", RFC 2608, June 1999.
http://www.ietf.org/internet-drafts/draft-ietf-svrloc-protocol-
v2-15.txt [ENDPOINTMIB]
"Internet Endpoint MIB", Internet Draft, October 1999.
http://www.ietf.org/internet-drafts/draft-ops-endpoint-mib-01.txt
[PROCESS] [PROCESS]
Bradner, S., "The Internet Standards Process -- Revision 3", BCP 9, Bradner, S., "The Internet Standards Process -- Revision 3", BCP 9,
RFC 2026, October 1996. RFC 2026, October 1996.
9. Authors' Addresses 9. Authors' Addresses
Andrew Smith Andrew Smith
Extreme Networks Extreme Networks
3585 Monroe St. 3585 Monroe St.
skipping to change at page 26, line 5 skipping to change at page 27, line 40
EMail: David.Partain@ericsson.com EMail: David.Partain@ericsson.com
John Seligson John Seligson
Nortel Networks, Inc. Nortel Networks, Inc.
4401 Great America Parkway 4401 Great America Parkway
Santa Clara, CA 95054 Santa Clara, CA 95054
USA USA
Phone: +1 408 495 2992 Phone: +1 408 495 2992
EMail: jseligso@nortelnetworks.com EMail: jseligso@nortelnetworks.com
10. Full Copyright 10. Notices
The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to pertain
to the implementation or use of the technology described in this
document or the extent to which any license under such rights might or
might not be available; neither does it represent that it has made any
effort to identify any such rights. Information on the IETF's
procedures with respect to rights in standards-track and standards-
related documentation can be found in BCP-11. Copies of claims of
rights made available for publication and any assurances of licenses to
be made available, or the result of an attempt made to obtain a general
license or permission for the use of such propritary rights by
implementors or users of this specification can be obtained from the
IETF Secretariat.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary rights
which may cover technology that may be required to practice this
standard. Please address the information to the IETF Executive
Director.
11. Full Copyright
Copyright (C) The Internet Society (1999). All Rights Reserved. Copyright (C) The Internet Society (1999). All Rights Reserved.
This document and translations of it may be copied and furnished This document and translations of it may be copied and furnished
to others, and derivative works that comment on or otherwise to others, and derivative works that comment on or otherwise
explain it or assist in its implmentation may be prepared, copied, explain it or assist in its implmentation may be prepared, copied,
published and distributed, in whole or in part, without published and distributed, in whole or in part, without
restriction of any kind, provided that the above copyright notice restriction of any kind, provided that the above copyright notice
and this paragraph are included on all such copies and derivative and this paragraph are included on all such copies and derivative
works. However, this document itself may not be modified in any works. However, this document itself may not be modified in any
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/