A set of configuration information regarding a single COPS
server from the point of view of a COPS client. The entry
is created and deleted by using ccopsServerConfigStatus.
An entry may not exist in the active state unless all
objects in the entry have an appropriate value.
Each client type can have its own COPS servers.
By creating, deleting or modifying an entry in this table,
users can add, delete or modify a COPS server for a particular
client type for the device.
In order to get policies from COPS server for a client type,
user has to create an entry for such client type.
Parsed from file CISCO-COPS-CLIENT-MIB.mib
Module: CISCO-COPS-CLIENT-MIB
A set of configuration information regarding a single COPS
server from the point of view of a COPS client. The entry
is created and deleted by using ccopsServerConfigStatus.
An entry may not exist in the active state unless all
objects in the entry have an appropriate value.
Each client type can have its own COPS servers.
By creating, deleting or modifying an entry in this table,
users can add, delete or modify a COPS server for a particular
client type for the device.
In order to get policies from COPS server for a client type,
user has to create an entry for such client type.
A set of configuration information regarding a single COPS
server from the point of view of a COPS client. The entry
is created and deleted by using ccopsServerConfigStatus.
An entry may not exist in the active state unless all
objects in the entry have an appropriate value.
Each client type can have its own COPS servers.
By creating, deleting or modifying an entry in this table,
users can add, delete or modify a COPS server for a particular
client type for the device.
In order to get policies from COPS server for a client type,
user has to create an entry for such client type.
Parsed from file CISCO-COPS-CLIENT-MIB.my.txt
Company: None
Module: CISCO-COPS-CLIENT-MIB
A set of configuration information regarding a single COPS
server from the point of view of a COPS client. The entry
is created and deleted by using ccopsServerConfigStatus.
An entry may not exist in the active state unless all
objects in the entry have an appropriate value.
Each client type can have its own COPS servers.
By creating, deleting or modifying an entry in this table,
users can add, delete or modify a COPS server for a particular
client type for the device.
In order to get policies from COPS server for a client type,
user has to create an entry for such client type.
ccopsServerConfigEntry OBJECT-TYPE SYNTAX CcopsServerConfigEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A set of configuration information regarding a single COPS server from the point of view of a COPS client. The entry is created and deleted by using ccopsServerConfigStatus. An entry may not exist in the active state unless all objects in the entry have an appropriate value. Each client type can have its own COPS servers. By creating, deleting or modifying an entry in this table, users can add, delete or modify a COPS server for a particular client type for the device. In order to get policies from COPS server for a client type, user has to create an entry for such client type." INDEX { ccopsServerConfigClientType, IMPLIED ccopsServerConfigName } ::= { ccopsServerConfigTable 1 }
ccopsServerConfigEntry OBJECT-TYPE SYNTAX CcopsServerConfigEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "A set of configuration information regarding a single COPS server from the point of view of a COPS client. The entry is created and deleted by using ccopsServerConfigStatus. An entry may not exist in the active state unless all objects in the entry have an appropriate value. Each client type can have its own COPS servers. By creating, deleting or modifying an entry in this table, users can add, delete or modify a COPS server for a particular client type for the device. In order to get policies from COPS server for a client type, user has to create an entry for such client type." INDEX { ccopsServerConfigClientType, IMPLIED ccopsServerConfigName } ::= { ccopsServerConfigTable 1 }
Vendor: Cisco
Module: CISCO-COPS-CLIENT-MIB
[Automatically extracted from oidview.com]
ccopsServerConfigEntry OBJECT-TYPE SYNTAX CcopsServerConfigEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A set of configuration information regarding a single COPS server from the point of view of a COPS client. The entry is created and deleted by using ccopsServerConfigStatus. An entry may not exist in the active state unless all objects in the entry have an appropriate value. Each client type can have its own COPS servers. By creating, deleting or modifying an entry in this table, users can add, delete or modify a COPS server for a particular client type for the device. In order to get policies from COPS server for a client type, user has to create an entry for such client type." INDEX { ccopsServerConfigClientType, IMPLIED ccopsServerConfigName } ::= { ccopsServerConfigTable 1 }
ccopsServerConfigEntry OBJECT-TYPE SYNTAX CcopsServerConfigEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A set of configuration information regarding a single COPS server from the point of view of a COPS client. The entry is created and deleted by using ccopsServerConfigStatus. An entry may not exist in the active state unless all objects in the entry have an appropriate value. Each client type can have its own COPS servers. By creating, deleting or modifying an entry in this table, users can add, delete or modify a COPS server for a particular client type for the device. In order to get policies from COPS server for a client type, user has to create an entry for such client type." INDEX { ccopsServerConfigClientType, IMPLIED ccopsServerConfigName } ::= { ccopsServerConfigTable 1 }
OID | Name | Sub children | Sub Nodes Total | Description |
---|---|---|---|---|
1.3.6.1.4.1.9.9.140.1.1.4.1.1 | ccopsServerConfigClientType | 0 | 0 | The type of policies to be retrieved from this server. |
1.3.6.1.4.1.9.9.140.1.1.4.1.2 | ccopsServerConfigName | 0 | 0 | The IP address or the hostname of a COPS server. If a hostname is used, it will be resolved to an address prior to each attempt t… |
1.3.6.1.4.1.9.9.140.1.1.4.1.3 | ccopsServerConfigPriority | 0 | 0 | The priority of this entry relative to other entries. The COPS client will attempt to contact COPS servers for the appropriate Cl… |
1.3.6.1.4.1.9.9.140.1.1.4.1.4 | ccopsServerConfigPort | 0 | 0 | The destination port number to which COPS server messages should be sent. By default the COPS service will be provided on the we… |
1.3.6.1.4.1.9.9.140.1.1.4.1.5 | ccopsServerConfigStatus | 0 | 0 | The status of COPS server configuration for a client type. An entry may not exist in the active state unless all objects in the e… |