5-41
Cisco SCE 2000 and SCE 1000 Software Configuration Guide
OL-7827-12
Chapter 5 Configuring the Management Interface and Security
Configuring and Managing the SNMP Interface
• pcubeProducts subtree — contains the OIDs of Cisco Service Control products.
• pcubeModules subtree — provides a root object identifier under which MIB modules can be defined.
• pcubeMgmt subtree — the root for pcube MIBs that are relevant to multiple products.
–
pcubeConfigCopyMIB — a subset of the Cisco Config-Copy-MIB that supports local copying
of running config to startup config.
• pcubeWorkgroups subtree — contains the actual MIBs for Cisco Service Control devices and
sub-devices.
• pcubeSeMIB — comprises two branches:
–
pcubeSeEvents — Contains the OIDs used for sending enterprise-specific notifications.
–
pcubeSEObjs — Contains the OIDs that belong to the SCE platform, divided into groups
according to functionality.
Loading the MIB Files
The Service Control proprietary MIB uses definitions that are defined in other MIBs, such as pcube MIB
(pcube.mib ), and the SNMPv2.mib. Therefore, the order in which the MIBs are loaded is important. To
avoid errors, the MIBs must be loaded in the proper order.
1. Load SNMPv2.my.
2. Load SNMP-FRAMEWORK-MIB.my.
3. Load PCUBE-SMI.my.
4. Load PCUBE-SE-MIB.my.
Note Information and proprietary MIB files supported by the SCOS can be downloaded from www.cisco.com
under Cisco Service Routing Products section.
Configuration via SNMP
SCE platform supports a limited set of variables that may be configured via SNMP (read-write
variables). Setting a variable via SNMP (as via the CLI) takes effect immediately and affects only the
running-configuration. To make this configuration stored for next reboots (startup-configuration) the
user must specify it explicitly via CLI or via SNMP using the Cisco enterprise MIB objects (see
Figure 5-1pcube Enterprise MIB Structure, page 5-40).
It should be noted also that the SCE platform takes the approach of a single configuration database with
multiple interfaces that may change this database. Therefore, executing the copy running-config
startup-config command via CLI or SNMP makes permanent all the changes made by either SNMP or
CLI.
To Next Page
Loading...
