Avaya Cajun P580 Installation and operating instructions

© 2002 Avaya, Inc. December 2, 2002 1
User Guide Addendum for the Avaya
P580 and P882 Multiservice Switches,
Software Version 5.4
Overview
This addendum provides information and procedures that will be
added to later versions of the user documentation. Version 5.4 of the
application software is supported only by the M8000R-SUP
supervisor module.
This addendum is updated periodically with new information. To
download the most current version of this document, see http://
support.avaya.com. Click Product Documentation.
This addendum includes the following topics:
■New Hardware Features on page 2
■New Software Features on page 2
■Updated CLI Commands on page 4
■Logging ACL Activity on page 4
■Configuring Custom Access Types on page 9
■Configuring Utilization Monitoring on page 17
■Configuring Short-Lived IP Protocol Filters on page 22
■Documentation Updates and Corrections on page 26
■Technical Support on page 37
■Documentation Feedback on page 37

User Guide Addendum for the Avaya P580 and P882, v5.4
2 December 2, 2002 Part No. 610-0211-094
New Hardware Features
Version 5.4 provides support for the following new hardware:
■10-Gigabit Uplink module.
For information about how to install the 10-Gigabit Uplink
module, see Installing the Avaya 10-Gigabit Uplink Module. For
information about how to configure the module, see
Appendix A, "Configuring the Avaya 10-Gigabit Uplink
Module."
New Software Features
Version 5.4 provides support for the following new software
features:
Security Features ■ACL Logging. This feature logs information about a sampling
of packets that match specific rules in the active access
control list. For information on how to use the ACL Logging
feature, see Logging ACL Activity on page 4.
■Ability to select read-only permission or read-write
permission for custom access types. For information on how
to specify these permissions when you create a custom access
type, see Configuring Custom Access Types on page 9.
Performance
Features ■Utilization Monitoring. This feature makes it possible for you
to monitor utilization of the:
—CPU—the number of packets per second that the CPU on
the supervisor module routes (slow path).
—Forwarding engine—the number of packets per second
that the 80-series forwarding engines route. This statistic
includes packets routed by the forwarding engines on 80-
series media modules (FIRE) and on the supervisor
module (FORE).
For more information about the slow path and FIRE and
FORE paths, see “Routing Overview” in Chapter 1,
“Introduction,” of the Avaya P550R, P580, P880, and P882
Multiservice Switch User Guide.

Doc. No. 650-100-701
Part No. 610-0211-094 December 2, 2002 3
For each of these statistics, you can set a high threshold. If
this threshold is exceeded, the switch logs the event in the
event log. For information on how to configure utilization
monitoring, see "Configuring Utilization Monitoring" on
page 17.
■Short-lived protocol filters. This feature helps conserve the
forwarding engine resources of the switch. By using a short-
lived protocol filter, you can set the switch to use the slow
path to route packets of a specific short-lived protocol. And
by using the slow path to route short-lived protocol traffic,
you conserve the resources of the forwarding engines.
For information on how to configure short-lived protocol
filters, see "Configuring Short-Lived IP Protocol Filters" on
page 22.
MIB Support ■The following groups and objects in the RMON2 MIB,
documented in RFC 2021:
—Protocol Directory (protocolDir) Group
• Protocol Directory Last Change
(protocolDirLastChange) object
• Protocol Directory Table (protocolDirTable)
The following protocols are supported in this table:
Ethernet II, SNAP, IP, IPX, TCP, and UDP.
—Address Map (addressMap) Group:
• Address Map Table (addressMapTable)
—Probe Configuration (probeConfig) Group
• Probe Capabilities (probeCapabilities) object
• Network Configuration Table (netConfigTable)
• Network Default Gateway (netDefaultGateway) object
■The following table in the HCRMON MIB (draft-ietf-
rmonmib-hcrmon-10.mib), documented in RFC 3273:
—Ethernet Statistics High Capacity Table
(etherStatsHighCapacityTable)

User Guide Addendum for the Avaya P580 and P882, v5.4
4 December 2, 2002 Part No. 610-0211-094
Updated CLI Commands
show custom-access-type
Command Mode User.
Description Displays the custom access types that are currently configured on
the switch.
Syntax show custom-access-type
Sample Output The following example displays the custom access types that are
currently configured on a switch:
Avaya>show custom-access-type
Systems Avaya P580 and P882 Multiservice switches.
Logging ACL Activity
Overview
You can now log information about packets that match specific rules
in the active access control list (ACL). Each log entry contains the
following information:
■Source and destination IP address.
■Protocol ID (RFC 1700 defines these ID numbers).
■Time that the match occurred.
■Index number of the access rule that was matched.
Custom Access Type
Name
----------------
Sys
Cfg.
----
-
Mod
Port
Cfg.
----
-
Event
Mgmt.
-----
L2
Switching
---------
Routing
-------
admin rw rw rw rw rw
CAT1 ro rw -- -- --

Doc. No. 650-100-701
Part No. 610-0211-094 December 2, 2002 5
■Forwarding information:
—The priority of the packet if the ACL assigns it a priority
and forwards it.
—Forward with no change in priority if the ACL
forwards the packet without changing its priority.
—FILTER if the ACL blocks the packet.
To avoid excessive consumption of the switch resources, ACL
matches are logged for slow path traffic at specific time intervals.
You can set the interval at which the matches are logged. The
default setting is two seconds.
ACL matches are not logged for FIRE path or FORE path traffic. For
more information about the slow path and FIRE and FORE paths,
see “Routing Overview” in Chapter 1, “Introduction,” of the Avaya
P550R, P580, P880, and P882 Multiservice Switch User Guide.
This section includes procedures for the following tasks:
■Enabling ACL Logging on page 5
■Setting a Logging Interval on page 7
Enabling ACL Logging
Web Agent
Procedure To enable ACL logging by using the Web Agent:
1. In the navigation pane, expand the Routing > IP >
Configuration folders, and then click Access Lists.
The IP Access List Web page is displayed in the content pane.
See Figure 1.

User Guide Addendum for the Avaya P580 and P882, v5.4
6 December 2, 2002 Part No. 610-0211-094
Figure 1. IP Access List Web page
2. Select the check box next to each rule that you want to
enable ACL logging for.
3. In the Rule Match Logging column, select Enable for each
access rule that you want to enable ACL logging for.
The default setting for ACL logging is disabled.
4. Click Apply.
CLI Command To enable ACL logging, enter Global Configuration mode and use the
following command:
ip acl-logging enable <access-list-name> <rule-number>
The default setting for ACL logging is disabled.
Table 1. Keywords, Arguments, and Options
Keyword, Argument,
or Option Definition
<access-list-name> The access list that contains the access
rule for which you want to enable ACL
logging.
<rule-number> The number of the access rule for which
you want to enable ACL logging.

Doc. No. 650-100-701
Part No. 610-0211-094 December 2, 2002 7
To disable ACL logging, enter Global Configuration mode and use the
following command:
ip acl-logging disable <access-list-name> <rule-number>
Sample Event Log
Entries Figure 2 displays sample ACL matches in the event log.
Figure 2. Sample ACL matches in the event log
Setting a Logging Interval
Web Agent
Procedure To set the interval for ACL logging:
1. In the navigation pane, expand the Routing > IP >
Configuration folders, and then click Access Control.
The IP Access Control Web page is displayed in the content
pane. See Figure 3.

User Guide Addendum for the Avaya P580 and P882, v5.4
8 December 2, 2002 Part No. 610-0211-094
Figure 3. IP Access Control Web page
2. In the Interval between logging of Access Rule Matches
(in seconds) field, enter the interval at which you want ACL
matches logged. Enter an interval from 1 to 60 seconds.
The default setting is 2 seconds.
3. Click Apply.
CLI Command To set the interval for ACL logging, enter Global Configuration mode
and use the following command:
ip acl-logging logging-interval <time-in-seconds>
The default setting is 2 seconds.
Table 2. Keywords, Arguments, and Options
Keyword, Argument,
or Option Definition
<time-in-seconds> The interval at which you want ACL
matches logged. Enter an interval from 1
to 60 seconds.

Doc. No. 650-100-701
Part No. 610-0211-094 December 2, 2002 9
Configuring Custom Access Types
This section contains procedures for the following tasks:
■Creating a Custom Access Type on page 9
■Viewing Custom Access Types on page 13
■Modifying a Custom Access Type on page 14
* Note: To log in to the ATM Uplink module, a user must:
• Have read-write access to the Modules and Ports
Management features.
• Enter Privileged mode or Global Configuration mode to
enter the session <slot number> command.
In earlier versions of application software, you could log
in to the ATM Uplink module from User mode. This
change in functionality prevents unauthorized users from
logging in to the ATM Uplink module.
Creating a Custom Access Type
Web Agent
Procedure To create a custom access type:
1. In the navigation pane, expand the System >
Administration folders, and then click Custom Access
Types.
The Custom Access Types Web page is displayed in the
content pane. See Figure 4.

User Guide Addendum for the Avaya P580 and P882, v5.4
10 December 2, 2002 Part No. 610-0211-094
Figure 4. Custom Access Types Web page
2. On the Custom Access Types Web page, click Create.
The Create Custom Access Type Web page is displayed in the
content pane. See Figure 5.

Doc. No. 650-100-701
Part No. 610-0211-094 December 2, 2002 11
Figure 5. Create Custom Access Type Web page
3. In the Type Name field, enter a name for the custom access
type. You can enter up to 31 characters. Do not use spaces.
4. For each feature in the Accessible Features list, select the
permission that you want to assign the custom access type:
—Read-Write allows users to view and modify settings for
the feature.
—Read-Only allows users only to view settings for the
feature.
—None allows users to neither view or modify settings for
the feature.
5. Click Apply to save the custom access type or Cancel to clear
your entries.

User Guide Addendum for the Avaya P580 and P882, v5.4
12 December 2, 2002 Part No. 610-0211-094
CLI Command To create a custom access type, enter Global Configuration mode
and use the following command:
custom-access-type <catName> [sys-configuration [ro]]
[module-port-mgmt [ro]] [events-mgmt [ro]] [l2-
switching [ro]] [routing [ro]]
Table 3. Keywords, Arguments, and Options
Keyword, Argument,
or Option Definition
<catName> The name of the custom access type. You
can enter up to 31 characters. Do not use
spaces.
[sys-configuration] Allows users to access system
configuration settings.
If you do not enter this option, users who
are assigned to the custom access type
cannot access system configuration
settings.
[ro] Enables read-only permission.
If you do not enter this option, users who
are assigned to the custom access type
have read-write permission for the
feature.
[module-port-mgmt] Allows users to access module and port
settings.
If you do not enter this option, users who
are assigned to the custom access type
cannot access module and port settings.
[events-mgmt] Allows users to access event settings.
If you do not enter this option, users who
are assigned to the custom access type
cannot access event settings.
1 of 2

Doc. No. 650-100-701
Part No. 610-0211-094 December 2, 2002 13
For example, the following command creates a custom access type
that allows users read-only permission for module and port settings
and read-write permission for layer 2 switching settings:
custom-access-type CAT1 module-port-mgmt ro l2-
switching
Users who are assigned to the CAT1 custom access type cannot view
or modify settings for system configuration, events, or routing.
Viewing Custom Access Types
Web Agent
Procedure To view the custom access types that are currently configured on the
switch:
1. In the navigation pane, expand the System >
Administration folders, and then click Custom Access
Types.
The Custom Access Types Web page is displayed in the
content pane. See Figure 4.
CLI Command To view the custom access types that are currently configured on the
switch, use the following command:
show custom-access-type
You can enter this command from User mode.
[l2-switching] Allows users to access layer 2 switching
settings.
If you do not enter this option, users who
are assigned to the custom access type
cannot access layer 2 switching settings.
[routing] Allows users to access routing settings.
If you do not enter this option, users who
are assigned to the custom access type
cannot access routing settings.
Table 3. Keywords, Arguments, and Options
Keyword, Argument,
or Option Definition
2 of 2

User Guide Addendum for the Avaya P580 and P882, v5.4
14 December 2, 2002 Part No. 610-0211-094
Modifying a Custom Access Type
Web Agent
Procedure To modify a custom access type:
1. In the navigation pane, expand the System >
Administration folders, and then click Custom Access
Types.
The Custom Access Types Web page is displayed in the
content pane. See Figure 4.
2. In the Type Name field, select the custom access type that you
want to modify.
3. Click Modify.
The Modify Custom Access Type Web page is displayed in the
content pane. See Figure 6.
Figure 6. Modify Custom Access Type Web page
4. In the Accessible Features list, modify the permissions as
necessary:
—Read-Write allows users to view and modify settings for
the feature.

Doc. No. 650-100-701
Part No. 610-0211-094 December 2, 2002 15
—Read-Only allows users only to view settings for the
feature.
—None allows users to neither view or modify settings for
the feature.
5. Click Apply to save the custom access type or Cancel to clear
your entries.
CLI Command To modify a custom access type, enter Global Configuration mode
and use the following command:
set custom-access-type <catName> [sys-configuration {ro | rw |
none}] [module-port-mgmt {ro | rw | none}] [events-mgmt
{ro | rw | none}] [l2-switching {ro | rw | none}] [routing {ro | rw
| none}]
* Note: Unlike the custom-access-type command that you use
to create a custom access type, you must specify read-
only, read-write, or no permission when you use the set
custom-access-type command to modify a custom
access type.
Table 4. Keywords, Arguments, and Options
Keyword, Argument,
or Option Definition
<catName> The name of the custom access type that
you want to modify.
[sys-configuration] Changes the permission for system
configuration settings.
If you do not enter this option, the
current permission is retained.
{ro | rw | none} The permission that the custom access
type has for the feature.
• ro (read-only) allows users only to
view settings for the feature.
• rw (read-write) allows users to
view and modify settings for the
feature.
• none allows users to neither view
or modify settings for the feature.
1 of 2

User Guide Addendum for the Avaya P580 and P882, v5.4
16 December 2, 2002 Part No. 610-0211-094
For example, the following command gives custom access type
CAT1 read-write permission for module and port settings and read-
only permission for system configuration settings:
custom-access-type CAT1 sys-configuration ro
module-port-mgmt rw
The permissions for all other features are unchanged.
[module-port-mgmt] Changes the permission for module and
port settings.
If you do not enter this option, the
current permission is retained.
[events-mgmt] Changes the permission for event
settings.
If you do not enter this option, the
current permission is retained.
[l2-switching] Changes the permission for layer 2
switching settings.
If you do not enter this option, the
current permission is retained.
[routing] Changes the permission for routing
settings.
If you do not enter this option, the
current permission is retained.
Table 4. Keywords, Arguments, and Options
Keyword, Argument,
or Option Definition
2 of 2

Doc. No. 650-100-701
Part No. 610-0211-094 December 2, 2002 17
Configuring Utilization Monitoring
Overview
Utilization monitoring makes it possible for you to monitor
utilization of the:
■CPU—the number of packets per second that the CPU on the
supervisor module routes (slow path).
■Forwarding engine—the number of packets per second that
the 80-series forwarding engines route. This statistic includes
packets routed by the forwarding engines on 80-series media
modules (FIRE) and on the supervisor module (FORE).
For more information about the slow path and FIRE and FORE
paths, see “Routing Overview” in Chapter 1, “Introduction,” of the
Avaya P550R, P580, P880, and P882 Multiservice Switch User Guide.
For each of these statistics, you can set a high threshold. If this
threshold is exceeded, the switch logs the event in the event log,
displays a message in the CLI, and sends an SNMP trap to the Trap
receiver.
This section contains procedures for the following tasks:
■Enabling Utilization Monitoring on page 18
■Enabling Event Logging of Utilization on page 18
■Setting a Utilization Threshold on page 19
■Viewing Utilization Settings on page 20
■Viewing CPU Utilization Statistics on page 21
■Viewing Statistics for Forwarding Engine Utilization on
page 21
You can configure utilization monitoring only by using the CLI. This
feature is not available in the Web Agent.

User Guide Addendum for the Avaya P580 and P882, v5.4
18 December 2, 2002 Part No. 610-0211-094
Enabling Utilization Monitoring
To enable utilization monitoring, enter Global Configuration mode
and use the following command:
set utilization monitoring {cpu | forwarding-engine}
The default setting for utilization monitoring is disabled.
To disable utilization monitoring, enter Global Configuration mode
and use the following command:
clear utilization monitoring {cpu | forwarding-engine}
Enabling Event Logging of Utilization
To enable event logging of utilization, enter Global Configuration
mode and use the following command:
set utilization threshold-event {cpu | forwarding-
engine}
The default setting for event logging of utilization is disabled. If you
enable event logging of utilization but do not specify a utilization
threshold, the switch logs an event if the CPU utilization or
forwarding engine utilization exceeds 95 percent.
Table 5. Keywords, Arguments, and Options
Keyword, Argument,
or Option Definition
cpu Enables monitoring of CPU utilization.
forwarding-engine Enables monitoring of 80-series
forwarding engines.
Table 6. Keywords, Arguments, and Options
Keyword, Argument
or Option Definition
cpu Enables event logging for CPU utilization.
forwarding-engine Enables event logging for utilization of
80-series forwarding engines.

Doc. No. 650-100-701
Part No. 610-0211-094 December 2, 2002 19
To disable event logging of utilization, enter Global Configuration
mode and use the following command:
clear utilization threshold-event {cpu | forwarding-
engine}
Setting a Utilization Threshold
To set a utilization threshold, enter Global Configuration mode and
use the following command:
set utilization high-threshold {cpu | FIRE | FORE}
<utilization-percent>
The default setting for the utilization threshold is 95 percent.
Table 7. Keywords, Arguments, and Options
Keyword, Argument
or Option Definition
cpu Sets the high threshold for CPU
utilization.
100% CPU utilization is the total capacity
of the supervisor module to forward slow
path traffic. When 100% utilization is
reached, the performance of the switch
may degrade.
FIRE Sets the high threshold for utilization of
the forwarding engines on 80-series
media modules.
100% FIRE utilization is the total
capacity of the forwarding engines on 80-
series media modules to forward in band
traffic. When 100% utilization is
reached, the performance of the switch
may degrade.
1 of 2

User Guide Addendum for the Avaya P580 and P882, v5.4
20 December 2, 2002 Part No. 610-0211-094
Clearing the utilization threshold resets it to 95 percent, its default
setting. To clear the utilization threshold, enter Global Configuration
mode and use the following command:
clear utilization high-threshold {cpu | FIRE | FORE}
<utilization-percent>
Viewing Utilization Settings
To view the current utilization settings, use the following command:
show utilization settings
You can enter this command from user mode.
A sample of the display is as follows:
CPU monitoring is disabled
Forwarding Engine monitoring is disabled
CPU threshold level is 95 percent
Forwarding Engines:
FIRE threshold level is 95 percent
FORE threshold level is 95 percent
CPU threshold event generation is disabled
Forwarding Engine threshold event generation is
disabled
FORE Sets the high threshold for utilization of
the forwarding engine on the supervisor
module.
100% FORE utilization is the total
capacity of the supervisor module to
forward out-of-band traffic. When 100%
utilization is reached, the performance of
the switch may degrade.
<utilization-percent> The high threshold at which you want
the switch to log an event in the event
log. Enter a value from 50 through 99.
The default setting is 95.
Table 7. Keywords, Arguments, and Options
Keyword, Argument
or Option Definition
2 of 2