Configuring the Management Interface and Security

Revised: September 27, 2012, OL-21060-09

Introduction

This chapter describes how to configure the physical management interfaces (ports) as well as the various management interface applications, such as SNMP, SSH, and TACACS+. It also explains how to configure users, passwords, IP configuration, clock and time zone, and domain name settings.

Management Interface and Security

The SCE8000 platform is equipped with two RJ-45 management ports (Port1 and Port2 on the SCE8000-SCM-E module in slot 1). These ports provide access from a remote management console to the SCE platform via a LAN.

The two management ports support management interface redundancy, providing the possibility for a backup management link.

Note The second management port is reflected in all objects related to it in the SNMP interface.

Perform the following tasks to configure the management interface and management interface security:

Entering Management Interface Configuration Mode

When entering Management Interface Configuration Mode, you must indicate the number of the management port to be configured:

•0/1 — Port1

•0/2 — Port2

The following Management Interface commands are applied only to the port specified when entering Management Interface Configuration Mode. Therefore, each port must be configured separately:

•speed

•duplex

The following Management Interface commands are applied to both management ports, regardless of which port had been specified when entering Management Interface Configuration Mode. Therefore, both ports are configured with one command:

•ip address

•auto-fail-over

The GBE management interface is configured as follows:

•mode: MNG Interface configuration mode

•interface designation: 0/1 or 0/2

Step 1 Type configureand press Enter.

Enters Global Configuration mode.

The command prompt changes to SCE(config)#.

Step 2 Type interface mng (0/1 | 0/2) and press Enter.

Enters Management Interface Configuration mode.

The command prompt changes to SCE(config if)#

Configuring the Management Port Physical Parameters

This interface has a transmission rate of 10, 100, or 1000 Mbps and is used for management operations and for transmitting RDRs, which are the output of traffic analysis and management operations.

Setting the IP Address and Subnet Mask of the Management Interface

You must define the IP address of the management interface.

When both management ports are connected, providing a redundant management port, this IP address always acts as a virtual IP address for the currently active management port, regardless of which port is the active port.

Options

The following options are available:

•IP address — The IP address of the management interface.

If both management ports are connected, so that a backup management link is available, this IP address will be act as a virtual IP address for the currently active management port, regardless of which physical port is currently active.

The following IP addresses are used internally by the SCE8000 platform and cannot be assigned to the management interface:

–192.168.207.241 to 192.168.207.255

–192.168.207.145 to 192.168.207.159

•subnet mask — subnet mask of the management interface.

Step 1 On a physically connected local console, access the interface configuration mode for either management interface. The specified IP address is configured for both interfaces.

The command might fail if there is a routing table entry that is not part of the new subnet defined by the new IP address and subnet mask.

Caution Changing the IP address of the management interface via telnet will result in loss of the telnet connection and inability to reconnect with the interface.

Note After changing the IP address, you must reload the SCE platform so that the change will take effect properly in all internal and external components of the SCE platform. (See Rebooting and Shutting Down the SCE Platform.)

Setting the IP Address and Subnet Mask of the Management Interface: Example

The following example shows how to set the IP address of the SCE platform to 10.1.1.1 and the subnet mask to 255.255.0.0.

SCE#config

SCE(config)#interface mng 0/1

SCE(config if)#ip address 10.1.1.1 255.255.0.0

Configuring the Management Interface Speed and Duplex Parameters

This section presents sample procedures that describe how to configure the speed and the duplex of the management interface.

The following example shows how to use this command to configure the management port to half duplex mode.

SCE#config

SCE(config)#interface mng 0/2

SCE(config if)#duplex half

Specifying the Active Management Port

This command explicitly specifies which management port is currently active. Its use varies slightly, depending on whether the management interface is configured as a redundant interface (auto fail-over enabled) or not (auto fail-over disabled).

•auto fail-over enabled (automatic mode) — the specified port becomes the currently active port, in effect forcing a fail-over action even if a failure has not occurred.

•auto fail-over disabled (manual mode) — the specified port should correspond to the cabled Mng port, which is the only functional port and therefore must be and remain the active management port.

Step 1 Access the interface configuration mode for the management interface you want to configure as the active management port.

Management Interface Redundancy

The SCE platform contains two RJ-45 management ports. The two management ports provide the possibility for a redundant management interface, thus ensuring management access to the SCE platform even if there is a failure in one of the management links. If a failure is detected in the active management link, the standby port automatically becomes the new active management port.

Note that both ports must be connected to the management console via a switch. In this way, the IP address of the MNG port is always the same, regardless of which physical port is currently active.

Important information:

•Only one port is active at any time.

•The same virtual IP address and MAC address are assigned to both ports.

•Default:

–Port 1 = active

–Port 2 = standby

•The standby port sends no packets to the network and packets from the network are discarded.

•When a problem in the active port is encountered, the standby port automatically becomes the new active port.

•Link problem, with switch to standby MNG port, is declared after the link is down for 300 msec.

•Service does not revert to the default active port if/when that link recovers. The currently active MNG port remains active until link failure causes a switch to the other MNG port.

Configuring the Management Ports for Redundancy

Step 1 Cable both management ports (Mng 1 and Mng 2), connecting them both to the remote management console via the LAN and via a switch.

Using the switch ensures that the IP address of the MNG port is always the same, regardless of which physical port is currently active

Configuring the Fail-Over Mode

Use the following command to enable automatic fail-over. The automatic mode must be enabled to support management interface redundancy. This mode automatically switches to the backup management link when a failure is detected in the currently active management link.

This parameter can be configured when in management interface configuration mode for either management port, and is applied to both ports with one command.

TACACS+ is a security application that provides centralized authentication of users attempting to gain access to a network element. The implementation of TACACS+ protocol allows customers to configure one or more authentication servers for the SCE platform, providing a secure means of managing the SCE platform, as the authentication server will authenticate each user. This then centralizes the authentication database, making it easier for the customers to manage the SCE platform.

TACACS+ services are maintained in a database on a TACACS+ server running, typically, on a UNIX or Windows NT workstation. You must have access to and must configure a TACACS+ server before the configured TACACS+ features on your network element are available.

The TACACS+ protocol provides authentication between the network element and the TACACS+ ACS, and it can also ensure confidentiality, if a key is configured, by encrypting all protocol exchanges between a network element and a TACACS+ server.

The TACACS+ protocol provides the following three features:

•Login authentication

•Privilege level authorization

•Accounting

Login Authentication

TACACS+ allows an arbitrary conversation to be held between the server and the user until the server receives enough information to authenticate the user. This is usually done by prompting for a username and password combination.

The login and password prompts may be provided by the TACACS+ server, or if the TACACS+ server does not provide the prompts, then the local prompts will be used.

The user log in information (user name and password) is transmitted to the TACACS+ server for authentication. If the TACACS+ server indicates that the user is not authenticated, the user will be re-prompted for the user name and password. The user is re-prompted a user-configurable number of times, after which the failed login attempt is recorded in the SCE platform user log and the telnet session is terminated (unless the user is connected to the console port.)

The SCE platform will eventually receive one of the following responses from the TACACS+ server:

•ACCEPT - The user is authenticated and service may begin.

•REJECT - The user has failed to authenticate. The user may be denied further access, or will be prompted to retry the login sequence depending on the TACACS+ server.

•ERROR - An error occurred at some time during authentication. This can be either at the server or in the network connection between the server and the SCE platform. If an ERROR response is received, the SCE platform will try to use an alternative method\server for authenticating the user.

•CONTINUE - The user is prompted for additional authentication information.

Accounting

•Each executed command (the command must be a valid one) will be logged using the TACACS+ accounting mechanism (including login and exit commands).

•The command is logged both before and after it is successfully executed.

•Each accounting message contains the following:

–User name

–Current time

–Action performed

–Command privilege level

TACACS+ accounting is in addition to normal local accounting using the SCE platform dbg log.

Privilege Level Authorization

After a successful login the user is granted a default privilege level of 0, giving the user the ability to execute a limited number of commands. Changing privilege level is done by executing the "enable" command. This command initiates the privilege level authorization mechanism.

Privilege level authorization in the SCE platform is accomplished by the use of an "enable" command authentication request. When a user requests an authorization for a specified privilege level, by using the "enable" command, the SCE platform sends an authentication request to the TACACS+ server specifying the requested privilege level. The SCE platform grants the requested privilege level only after the TACACS+ server does the following:

•Authenticates the " enable " command password

•Verifies that the user has sufficient privileges to enter the requested privilege level.

Once the user privilege level has been determined, the user is granted access to a specified set of commands according to the level granted.

General AAA Fallback and Recovery Mechanism

The SCE platform uses a fall-back mechanism to maintain service availability in case of an error.

The AAA methods available are:

•TACACS+ - AAA is performed by the use of a TACACS+ server, allows authentication, authorization and accounting.

•Local - AAA is performed by the use of a local database, allows authentication and authorization.

•Enable - AAA is performed by the use of user configured passwords, allows authentication and authorization.

•None - no authentication\authorization\accounting is performed.

In the current implementation, the order of the methods used is not configurable, but you can choose which of the methods are used. The current order is:

•TACACS+

•Local

•Enable

•None

Caution If the server goes to AAA fault, the SCE platform will not be accessible until one of the AAA methods is restored. In order to prevent this, it is advisable to use the "none" method as the last AAA method. If the SCE platform becomes inaccessible, the shell function "AAA_MethodsReset" will allow you to delete the current AAA method settings and set the AAA method used to "enable".
To run the "AAA_MethodsReset" shell function, complete the following steps:
1. Connect to AUX with username "root"
2. Run the debug shell:
scos_xinetd --service debug-shell --on3. Use Telnet to access the shell:
telnet localhost 23014. Run the shell function:
AAA_MethodsReset

About Configuring TACACS+

The following is a summary of the procedure for configuring TACACS+. All steps are explained in detail in the remainder of this section.

1. Configure the remote TACACS+ servers.

Configure the remote servers for the protocols. Keep in mind the following guidelines:

–Configure the encryption key that the server and client will use.

–The maximal user privilege level and enable password (password used when executing the enable command) should be provided.

–The configuration should always include the root user, giving it the privilege level of 15.

–Viewer (privilege level 5) and superuser (privilege level 10) user IDs should be established at this time also.

For complete details on server configuration, refer to the appropriate configuration guide for the particular TACACS+ server that you will be using.

2. Configure the SCE client to work with TACACS+ server:

–hostname of the server

–port number

–shared encryption key (the configured encryption key must match the encryption key configured on the server in order for the client and server to communicate.)

3. (Optional) Configure the local database, if used.

–add new users

If the local database and TACACS+ are both configured, it is recommended to configure the same user names in both TACACS+ and the local database. This will allow the users to access the SCE platform in case of TACACS+ server failure.

Note If TACACS+ is used as the login method, the TACACS+ username is used automatically in the enable command. Therefore, it is important to configure the same usernames in both TACACS+ and the local database so that the enable command can recognize this username.

–specify the password

–define the privilege level

4. Configure the authentication methods on the SCE platform.

–login authentication methods

–privilege level authorization methods

5. Review the configuration.

Use the " show running-config " command to view the configuration.

Configuring the SCE Platform TACACS+ Client

The user must configure the remote servers for the TACACS+ protocol. Then the SCE platform TACACS+ client must be configured to work with the TACACS+ servers. The following information must be configured:

•TACACS+ server hosts definition — a maximum of three servers is supported.

For each sever host, the following information can be configured:

–hostname (required)

–port

–encryption key

–timeout interval

•Default encryption key (optional) — A global default encryption key may be defined. This key is defined as the key for any server host for which a key is not explicitly configured when the server host is defined.

If the default encryption key is not configured, a default of no key is assigned to any server for which a key is not explicitly configured.

•Default timeout interval (optional) — A global default timeout interval may be defined. This timeout interval is defined as the timeout interval for any server host for which a timeout interval is not explicitly configured when the server host is defined.

If the default timeout interval is not configured, a default of five seconds is assigned to any server for which a timeout interval is not explicitly configured.

The procedures for configuring the SCE platform TACACS+ client are explained in the following sections:

Removing a TACACS+ Server Host

Step 1 From the SCE(config)# prompt, type no tacacs-server hosthost-name and press Enter.

Configuring the Global Default Key

Use this command to define the global default key for the TACACS+ server hosts. This default key can be overridden for a specific TACACS+ server host by explicitly configuring a different key for that TACACS+ server host.

Options

The following options are available:

•key-string — default encryption key that all TACACS+ servers and clients will use when communicating with each other. Make sure that the specified key is actually configured on the TACACS+ server hosts.

No global default key is defined. Each TACACS+ server host may still have a specific key defined. However, any server host that does not have a key explicitly defined (uses the global default key) is now configured to use no key.

Configuring the Global Default Timeout

Use this command to define the global default timeout interval for the TACACS+ server hosts. This default timeout interval can be overridden for a specific TACACS+ server host by explicitly configuring a different timeout interval for that TACACS+ server host.

Options

The following options are available:

•timeout interval — default time in seconds that the server waits for a reply from the server host before timing out.

No global default timeout interval is defined. Each TACACS+ server host may still have a specific timeout interval defined. However, any server host that does not have a timeout interval explicitly defined (uses the global default timeout interval) is now configured to a five second timeout interval.

Managing the User Database

TACACS+ maintains a local user database. Up to 100 users can be configured in this local database, which includes the following information for all users:

•Username

•Password — may configured as encrypted or unencrypted

•Privilege level

The procedures for managing the local user database are explained in the following sections:

How to Add a User with an MD5 Encrypted Password Entered as an MD5 Encrypted String

Defining the User Privilege Level

Privilege level authorization in the SCE platform is accomplished by the use of an " enable " command authentication request. When a user requests an authorization for a specified privilege level, by using the " enable " command, the SCE platform sends an authentication request to the TACACS+ server specifying the requested privilege level. The SCE platform grants the requested privilege level only after the TACACS+ server authenticates the " enable " command password and verifies that the user has sufficient privileges the enter the requested privilege level.

Options

The following options are available:

•name — name of the user whose privilege level is set

•level — the privilege level permitted to the specified user. These levels correspond to the CLI authorization levels, which are entered via the enable command:

Configuring AAA Accounting

If TACACS+ accounting is enabled, the SCE platform sends an accounting message to the TACACS+ server after every command execution. The accounting message is logged in the TACACS+ server for the use of the network administrator.

By default, TACACS+ accounting is disabled.

Options

The following options are available:

•level — The privilege level for which to enable the TACACS+ accounting

Configuring Access Control Lists (ACLs)

The SCE platform can be configured with Access Control Lists (ACLs), which are used to globally permit or deny incoming connections on the management interface. An access list is an ordered list of entries, each consisting of an IP address and an optional wildcard "mask" defining an IP address range, and a permit/deny field.

The order of the entries in the list is important. The default action of the first entry that matches the connection is used. If no entry in the Access List matches the connection, or if the Access List is empty, the default action is deny.

Creating an access list is done entry by entry, from the first to the last.

When the system checks for an IP address on an access list, the system checks each line in the access list for the IP address, starting at the first entry and moving towards the last entry. The first match that is detected (that is, the IP address being checked is found within the IP address range defined by the entry) determines the result, according to the permit/deny flag in the matched entry. If no matching entry is found in the access list, access is denied.

You can create up to 99 access lists.

An ACL is enabled by the ip access-class command. If an ACL is enabled, when a request comes in, the SCE platform first checks if there is permission for access from that IP address. If not, the SCE does not respond to the request. The basic IP interface is low-level, blocking the IP packets before they reach the interfaces.

If no ACL is enabled, access is permitted from all IP addresses.

Note The SCE Platform will respond to ping commands only from IP addresses that are allowed access. Pings from a non-authorized address will not receive a response from the SCE platform, as ping uses ICMP protocol.

Options

The following options are available:

•number — the ID number assigned to the Access Control List

•ip-address — the IP address of the interface to be permitted or denied. Enter in x.x.x.x format.

•ip-address/mask — configures a range of addresses in the format x.x.x.x y.y.y.y where x.x.x.x specifies the prefix bits common to all IP addresses in the range, and y.y.y.y is a wildcard-bits mask specifying the bits that are ignored. In this notation, `0' means bits to ignore.

The following keywords are available:

•permit — the specified IP addresses have permission to access the SCE platform.

•deny — the specified IP addresses are denied access to the SCE platform.

Adding Entries to an ACL

Step 1 Type configureand press Enter.

Enables Global Configuration mode.

Step 2 Enter the desired IP address or addresses.

•To configure one IP address type:

access-listnumber permit|deny ip-address and press Enter.

•To configure more than one IP address type:

access-listnumber permit|deny ip-address/mask and press Enter.

When you add a new entry to an ACL, it is always added to the end of the list.

Adding Entries to an ACL: Example

The following example adds an entry to the access list number 1, that permits access only to IP addresses in the range of 10.1.1.0-10.1.1.255.

SCE(config)#access-list 1 permit 10.1.1.0 0.0.0.255

Removing an ACL

Use this command to remove an ACL with all its entries.

Step 1 From the SCE(config)# prompt, type no access-list number and press Enter.

Removes the specified ACL with all its entries.

Enabling an ACL

An ACL permits or denies all traffic to the SCE platform.

Step 1 From the SCE(config)# prompt, type ip access-class number and press Enter.

Applies the specified ACL to all traffic attempting to access the SCE platform.

Configuring the SSH Server

The SSH Server

A shortcoming of the standard telnet protocol is that it transfers password and data over the net unencrypted, thus compromising security. Where security is a concern, using a Secure Shell (SSH) server rather than telnet is recommended.

An SSH server is similar to a telnet server, but it uses cryptographic techniques that allow it to communicate with any SSH client over an insecure network in a manner which ensures the privacy of the communication. CLI commands are executed over SSH in exactly the same manner as over telnet.

The SSH server supports both the SSHv1 and SSHv2 protocols. You can disable SSHv1, so that only SSHv2 is running.

Key Management

Each SSH server should define a set of keys (DSA2, RSA2 and RSA1) to be used when communicating with various clients. The key sets are pairs of public and private keys. The server publishes the public key while keeping the private key in non-volatile memory, never transmitting it to SSH clients. Note that the keys are kept on the tffs0 file system, which means that a person with knowledge of the `enable' password can access both the private and public keys. The SSH server implementation provides protection against eavesdroppers who can monitor the management communication channels of the SCE platform, but it does not provide protection against a user with knowledge of the `enable' password.

Key management is performed by the user via a special CLI command. A set of keys must be generated at least once before enabling the SSH server.

Size of the encryption key is always 2048 bits.

Managing the SSH Server

Use these commands to manage the SSH server. These commands do the following:

•Generate an SSH key set

•Enable/disable the SSH server

•Enable/disable SSHv1. (Disabling SSHv1 allows you to run SSHv2 only.)

•Delete existing SSH keys

Generating a Set of SSH Keys

Remember that you must generate a set of SSH keys before you enable the SSH server.

Deleting the Existing SSH Keys

If the SSH server is currently enabled, it will continue to run, since it only reads the keys from non-volatile memory when it is started. However, if the startup-configuration specifies that the SSH server is enabled, the SCE platform will not be able to start the SSH server on startup if the keys have been deleted. To avoid this situation, after executing this command, always do one of the following before the SCE platform is restarted (using reload ):

•Generate a new set of keys.

•Disable the SSH server and save the configuration.

Monitoring the Status of the SSH Server

Use this command to monitor the status of the SSH sever, including current SSH sessions.

SNMP Protocol

SNMP (Simple Network Management Protocol) is a set of protocols for managing complex networks. SNMP works by sending messages, called protocol data units (PDUs), to different parts of a network. SNMP-compliant devices, called agents, store data about themselves in Management Information Bases (MIBs) and return this data to the SNMP requesters.

SCE platform supports the original SNMP protocol (also known as SNMPv1), and a newer version called Community-based SNMPv2 (also known as SNMPv2C).

•SNMPv1 — is the first version of the Simple Network Management Protocol, as defined in RFCs 1155 and 1157, and is a full Internet standard. SNMPv1 uses a community-based form of security.

•SNMPv2c — is the revised protocol, which includes improvements to SNMPv1 in the areas of protocol packet types, transport mappings, and MIB structure elements but using the existing SNMPv1 administration structure. It is defined in RFC 1901, RFC 1905, and RFC 1906.

SCE platform implementation of SNMP supports all MIB II variables, as described in RFC 1213, and defines the SNMP traps using the guidelines described in RFC 1215.

The SNMPv1 and SNMPv2C specifications define the following basic operations that are supported by SCE platform. Table 5-2 lists the request types and descriptions.

Table 5-2 Request Types

Request Type

Description

Remarks

Set Request

Writes new data to one or more of the objects managed by an agent.

Set operations immediately affect the SCE platform running-config but do not affect the startup config

Get Request

Requests the value of one or more of the objects managed by an agent.

Get Next Request

Requests the Object Identifier(s) and value(s) of the next object(s) managed by an agent.

Get Response

Contains the data returned by an agent.

Trap

Sends an unsolicited notification from an agent to a manager, indicating that an event or error has occurred on the agent system

SCE platform may be configured to send either SNMPv1 or SNMPv2 style traps.

Get Bulk Request

Retrieves large amounts of object information in a single Request / response transaction. GetBulk behaves as if many iterations of GetNext request/responses were issued, except that they are all performed in a single request/response.

This is newly defined SNMPv2c message.

Security Considerations

By default, the SNMP agent is disabled for both read and write operations. When enabled, SNMP is supported over the management port only (in-band management is not supported).

In addition, the SCE platform supports the option to configure community of managers for read-write accessibility or for read-only accessibility.

About CLI

The SCE platform supports the CLI commands that control the operation of the SNMP agent. All the SNMP commands are available in Admin authorization level. The SNMP agent is disabled by default and any SNMP configuration command enables the SNMP agent (except where there is an explicit disable command).

CLI Commands for Configuring SNMP

Following is a list of CLI commands available for configuring SNMP. These are Global Configuration mode commands.

•snmp-server enable

•no snmp-server

•[no] snmp-server community [all]

•[no | default] snmp-server enable traps

•[no] snmp-server host [all]

•[no] snmp-server contact

•[no] snmp-server location

CLI Commands for Monitoring SNMP

Following is a list of CLI commands available for monitoring SNMP. These are Viewer mode commands, and are available when the SNMP agent is enabled:

•show snmp (available when SNMP agent is disabled)

•show snmp community

•show snmp contact

•show snmp enabled

•show snmp host

•show snmp location

•show snmp MIB (available when SNMP agent enabled and community was set)

•show snmp traps

About MIBs

MIBs (Management Information Bases) are databases of objects that can be monitored by a network management system (NMS). SNMP uses standardized MIB formats that allow any SNMP tools to monitor any device defined by a MIB.

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.

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.

Enabling the SNMP Interface

Use this command to explicitly enable the SNMP interface.

The SNMP interface is implicitly enabled when any snmp-server command is executed to configure any SNMP parameter. For more information on configuring and managing the SNMP parameters, including hosts, communities, contact, location, and trap destination hosts, see Configuring and Managing the SNMP Interface.

Configuring SNMP Community Strings

To enable SNMP management, you must configure SNMP community strings to define the relationship between the SNMP manager and the agent.

After receiving an SNMP request, the SNMP agent compares the community string in the request to the community strings that are configured for the agent. The requests are valid under the following circumstances:

•SNMP Get , Get-next , and Get-bulk requests are valid if the community string in the request matches the read-only community.

•SNMP Get , Get-next , Get-bulk and Set requests are valid if the community string in the request matches the agent's read-write community.

Defining a Community String

Options

The following options are available:

•community-string — a security string that identifies a community of managers who are permitted to access the SNMP server

Configuring SNMP Notifications

Use these commands to configure:

•The destinations that will receive SNMP notifications (hosts)

•Which types of notifications will be sent (traps)

Notifications are unsolicited messages that are generated by the SNMP agent that resides inside the SCE platform when an event occurs. When the Network Management System receives the notification message, it can take suitable actions, such as logging the occurrence or ignoring the signal.

By default, the SCE platform is not configured to send any SNMP notifications. You must define the Network Management System to which the SCE platform should send notifications. (See the table below, Configurable Notifications, for a list of configurable notifications). Whenever one of the events that trigger notifications occurs in the SCE platform, an SNMP notification is sent from the SCE platform to the list of IP addresses that you define.

SCE platform supports two general categories of notifications:

•Standard SNMP notifications - As defined in RFC1157 and using the conventions defined in RFC1215.

•Proprietary service control enterprise notifications - As defined in the service control proprietary MIB (See Table A-20).

After a host or hosts are configured to receive notifications, by default, the SCE platform sends to the host or hosts all the notifications supported by the SCE platform except for the AuthenticationFailure notification. The SCE platform provides the option to enable or disable the sending of this notification, as well as some of the SCE enterprise notifications, explicitly.

SCE platform can be configured to generate either SNMPv1 style or SNMPv2c style notifications. By default, the SCE platforms sends SNMPv1 notifications.

Following are some sample procedures illustrating how to do the following:

•Configure hosts (NMS) to which the SNMP agent should send notifications

•Remove/disable a host (NMS) from receiving notifications

•Enable the SNMP agent to send authentication-failure notifications

•Enable the SNMP agent to send enterprise notifications

•Reset all notifications to the default setting

Defining SNMP Hosts

Use this command to define the hosts that will receive notifications from the SCE platform.