Functional Restrictions for the Avaya P580 and P882 Multiservice

Functional Restrictions for the Avaya P580 and P882 Multiservice
Functional Restrictions for the Avaya P580 and P882
Multiservice Switches, Software Version 6.2
Overview
This document lists functional restrictions of Avaya P580 and P882 Multiservice switches that
are running version 6.2 application software. Version 6.2 application software is supported only
by the M8000R-SUP supervisor module.
Functional restrictions are issues that restrict the functionality of a particular feature. For most of
these issues a workaround exists. This document is periodically updated with more current
information.
For detailed information about your product, see the following documents:
●
User Guide for the Avaya P580 and P882 Multiservice Switches, Software Version 6.2
●
Command Reference Guide for the Avaya P580 and P882 Multiservice Switches,
Software Version 6.2
●
Release Notes for the Avaya P580 and P882 Multiservice Switches, Software Version 6.2
●
Avaya Multiservice Switch Error Messages
To download software, the latest release notes, and other documentation, see
http://support.avaya.com.
!
Important:
Important:
Avaya strongly recommends that you run the latest version of application
software on your switch.
This document includes the following topics:
●
Functional Restrictions and Workarounds on page 2
●
Technical Support on page 31
●
Documentation Feedback on page 31
Issue 1 February 2005
1
Functional Restrictions for the Avaya P580 and P882 Multiservice Switches, Software Version 6.2
Functional Restrictions and Workarounds
The following functional restrictions and workarounds apply to Avaya P580 and P882
Multiservice switches that are running application software, version 6.2:
●
24-Port, 100BASE-FX Module
●
●
50-Series, 48-Port, 10/100 Base-TX
Module
Point-to-Point Protocol (PPP) and
Telnet
●
Fabric Mode 1 Port Mirroring
●
Access Control Lists
●
Fabric Mode 2 Port Mirroring
●
Address Forwarding Table
●
Port Redundancy
●
AppleTalk
●
80-Series QoS
●
Configuration Files
●
RADIUS
●
CPU Redundancy
●
Resetting the Switch
●
Custom Access Types
●
RIP
●
DNS
●
set module notes Command
●
DVMRP
●
show port status Command
●
Flood Rate Limiting
●
Slot 2 of P580 and P882 Chassis
●
Gigabit Modules
●
SNMP
●
Hunt Groups
●
Spanning Tree
●
Intelligent Multicasting
●
Static Routes
●
IP Source Routing
●
80-Series Supervisor Module
●
IRDP
●
Switch Elements
●
Layer 3 Forwarding Cache
●
Upgrading the Application Software
●
NEDR
●
VLANs
●
Online Help
●
VRRP
●
OSPF
2 Doc No. 10-300513
Functional Restrictions and Workarounds
24-Port, 100BASE-FX Module
Issue
(RN000151) The Physical Port Configuration Web page and show port physical CLI command
inaccurately display a connector of Fiber SC for the 80-series, 24-port, 100BASE-FX module.
The correct connector type is MT-RJ.
Workaround
Not applicable.
50-Series, 48-Port, 10/100 Base-TX Module
Issue
(RN000241) The Physical Port Configuration Web page for 50-Series, 48-port 10/100 Base-TX
modules with Telco connectors (model number M5548E-100TC) displays Unknown in the Type
column.
Workaround
Use the CLI or SNMP MIB files to view the correct port type.
Issue 1 February 2005
3
Functional Restrictions for the Avaya P580 and P882 Multiservice Switches, Software Version 6.2
Access Control Lists
Issue
(RN000265) The layer 3 forwarding cache incorrectly displays a priority of 0 for packets that
match an ACL rule specifying one of the following actions:
●
Deny
●
Forward with no change in priority
●
Forward and change the priority to 1
This issue is a display issue only. The switch applies the ACL rule correctly.
Workaround
Not applicable.
Address Forwarding Table
Issue
(RN000287) When using the show aft entry CLI command, you cannot search for an AFT entry
by port for a port that is part of a hunt group. The CLI returns “No Entries matched search
criteria.”
Workaround
Search for a port with other methods in the CLI, such as by MAC address or VLAN.
Alternatively, search the switch’s AFT by port with the Web Agent.
Issue
(RN000290) When searching the AFT by port on a 10-Gigabit module (model numbers
M8001R-10000LR and M8001R-10000ER), only the first 20 table entries are displayed in the
Web Agent.
Workaround
Use the CLI to search AFT.
4 Doc No. 10-300513
Functional Restrictions and Workarounds
AppleTalk
Issue
(RN000274) If more than 20 AppleTalk interfaces are set up on the switch, you cannot delete an
AppleTalk interface by using the Web Agent.
Workaround
Use the no interface <intf-name> CLI command to delete AppleTalk interfaces.
Issue
(RN000247) If you use the ping appletalk command to ping a local AppleTalk interface, the
ping times out. However, remote AppleTalk interfaces reply to the command.
Workaround
Use the show appletalk interface command to determine the status of local AppleTalk
interfaces.
Issue
(RN000153) When multiple zones are set up on an AppleTalk interface, the no appletalk zone
<zone-name> CLI command does not delete a single zone.
Workaround
Use the Web Agent to delete a single AppleTalk zone. Alternately, you can use the no appletalk
zone command to delete all zones on the interface and then reassign zones to the interface.
Issue 1 February 2005
5
Functional Restrictions for the Avaya P580 and P882 Multiservice Switches, Software Version 6.2
Configuration Files
Issue
(RN000300) If you attempt to copy the startup configuration to the running configuration, the
switch may stop responding. The switch does not support this activity.
Workaround
Restart the switch to reapply the startup configuration.
CPU Redundancy
Issue
(RN000313) If you use a console connection to synchronize the active and standby supervisor
modules, and event messages are displayed during the synchronization, a stack trace is also
displayed. The supervisors do synchronize correctly, however, and you can disregard the error
messages.
This issue occurs more frequently if you synchronize the supervisor modules immediately after
starting the switch.
Workaround
Not applicable.
Issue
(RN000302) If you insert a redundant supervisor that has application software version 5.4 into a
chassis where the active supervisor is running 6.0 or later application software, the following
messages are displayed in the event log:
●
Warning (40) Redundant CPU Status Synchronization completed with an error at <date>
<time> Synched: nothing.
●
Warning (40) Redundant CPU Status Synchronization at <date> <time> errors: SNMPV3
Configuration.
Workaround
Not applicable.
6 Doc No. 10-300513
Functional Restrictions and Workarounds
Custom Access Types
Issue
(RN000272) The Web Agent and CLI have different default settings for custom access types.
When you create a new custom access type:
●
The Web Agent, by default, assigns read-write permission for all features.
●
The CLI, by default, assigns no access to any features.
Workaround
Not applicable.
Issue
(RN000246) Users who are assigned read-only permission for module and port management
have read-write permission for all ATM Uplink modules in the chassis.
Workaround
Not applicable.
DNS
Issue
(RN000254) The switch does not resolve partial domain name suffixes. For example, if
documentation.support.avaya.com, support.avaya.com, and avaya.com are set as domain
name suffixes on the switch, and you enter ping documentation.support, the switch does not
resolve the domain name.
Workaround
Always enter the fully qualified domain name.
Issue 1 February 2005
7
Functional Restrictions for the Avaya P580 and P882 Multiservice Switches, Software Version 6.2
DVMRP
Issue
(RN000296) If multicast data is being forwarded to a hunt group, and the flood port fails, the
routes that were learned through the hunt group are placed in hold-down. This issue causes a
loss of multicast data for a period of time no greater than the Route Hold Down Time, which is
120 seconds by default.
Workaround
Not applicable.
Issue
(RN000229) If the switch is forwarding a multicast flow to multiple destinations in the network,
two of which are reached by DVMRP tunnel, the switch may forward incorrect multicast packets
to the destinations that are not reached by DVMRP tunnel.
For example if the switch is forwarding a multicast flow to destinations A, B, and C, and
destinations A and B are being reached by DVMRP tunnel, destination C may receive incorrect
multicast packets.
Workaround
Some possible workarounds:
●
Use only one DVMRP tunnel per switch.
●
Use DVMRP tunnels for other destinations also.
This problem exist only when active multicast sessions simultaneously exist for broadcast
interfaces and two DVMRP tunnels.
8 Doc No. 10-300513
Functional Restrictions and Workarounds
Issue
(RN000130) The mtrace CLI command does not work. If you enter the command, no
information is displayed.
Workaround
You can obtain mtrace information by conducting an mtrace from another device in the multicast
path. If you use this workaround, make sure that mtrace support is enabled on all routers in the
path of the multicast flow.
You can enable mtrace support on Avaya Multiservice switches by using either the IGMP Global
Configuration Web page or the ip mtrace CLI command.
Issue
(RN000131) The switch advertises DVMRP routes that have a state of DOWN. This issue is
caused by the routing table falsely reporting DOWN interfaces as UP interfaces.
This issue occurs only when you change one of the DVMRP Global Configuration settings,
including enabling DVMRP itself.
Workaround
Set Multicast Routing Protocol to None for interfaces that have a state of DOWN.
Issue
(RN000091) If you use the IP Interfaces Web page to simultaneously change the IP address of
an interface and enable DVMRP on the interface, DVMP will not work correctly, and the
interface will not support multicast routing.
Symptoms of this issue include:
●
The interface does not accept IGMP membership reports.
●
The CLI does not display the interface when you enter the show ip igmp interface
command.
●
The IGMP Interfaces Web page does not display the interface.
Issue 1 February 2005
9
Functional Restrictions for the Avaya P580 and P882 Multiservice Switches, Software Version 6.2
Workaround
To change the IP address of an interface and enable DVMRP on the interface:
1. Change the IP address of the interface.
2. Click Apply.
3. Enable DVMRP for the interface.
4. Click Apply.
Flood Rate Limiting
Issue
(RN000004) The options for the Rate Limit Rate parameter do not work correctly on:
●
80-series, 10/100 Ethernet modules
●
80-series, 100 Base-FX Ethernet modules
These options do not work correctly regardless of whether you set them by using the Web
Agent or CLI. The default setting of 20% provides no rate limiting during broadcast storms.
Workaround
Use the following table to determine the option that corresponds to the rate that you want to set.
Avaya recommends that you enter a rate of 2%, which corresponds to the default setting of
20%.
Table 1: Flood Rate Limiting on 80-Series 10/100 Modules
10 Doc No. 10-300513
Desired Rate
Web or CLI Setting
80%
10%
40%
5%
20%
2%
10%
1%
Functional Restrictions and Workarounds
Gigabit Modules
Issue
(RN000303) If you remove a link from a copper gigabit port, the statistics for the port are
cleared.
Workaround
Not applicable.
Issue
(RN000304) When you connect a link to a copper gigabit port, the statistics for the port may be
greatly inflated.
Workaround
Clear the port statistics after you connect a link to a copper gigabit port.
Hunt Groups
Issue
(RN000314) If you attempt to add two 10-gigabit ports to the same hunt group by using one
command, the command fails for the second port. For example, if you enter set port
huntgroup 4-5/1, 6-7/1 hg1, the switch displays the following messages:
Port huntgroup set successful: 4-5/1.
Port 6-7/1 may only join an hunt group with an exclusive 10Gig port
membership.
Port huntgroup set failed: 6-7/1.
Workaround
Reenter the command.
Issue 1 February 2005
11
Functional Restrictions for the Avaya P580 and P882 Multiservice Switches, Software Version 6.2
Issue
(RN000308) If 10-gigabit ports participate in a hunt group and the two switches are running
Spanning Tree (RSTP or STP), traffic interruptions may occur.
Workaround
Use an alternate configuration, for example port redundancy.
Issue
(RN000260) When you assign a static MAC address to the base port of a hunt group, the hunt
group link stops transmitting. When you assign a static MAC address to a nonbase port, the
switch functions correctly.
Workaround
Do not assign a static MAC address to the base port of a hunt group.
Issue
(RN000094) If you remove the module that has the base port for a hunt group, a loss of traffic
will occur for approximately eight seconds. This problem occurs only if:
●
The base port is on a licensed, 80-series module that is in an 80-series chassis
AND
●
All other ports on the switch that are participating in the hunt group are on licensed,
80-series modules.
During this 8-second period, VRRP mastership may change to the backup router and then back
to the original active router. This changing of VRRP mastership may cause OSPF adjacencies
and routes to be lost.
Workaround
Set the VRRP advertisement timer to 4 seconds or greater, and set OSPF timers so that the
Dead interval is 12 seconds or greater. Alternatively, remove modules from the chassis only
during a maintenance period.
12 Doc No. 10-300513
Functional Restrictions and Workarounds
Intelligent Multicasting
Issue
(RN000014) Layer 2 multicast data is not forwarded on slot 17 in the P882 chassis.
Note:
This issue occurs only in Fabric Mode 2.
Note:
Workaround
Use slots 2 through 16.
Issue
(RN000157) If you set up a piggyback port to mirror a router port for intelligent multicast, the
switch deletes the router port, and then:
●
If the switch learned the router port dynamically, the piggyback port is displayed as the
router port when the switch relearns the router port.
The Router Port Display/Configuration Web page and show intelligent-multicast
router-port CLI command incorrectly display the piggyback port, not the router port, in the
Port field.
●
If you set up the router port manually, you must set up the router port again.
You can use the Router Port Display/Configuration Web page or set intelligent-multicast
router-port vlan CLI command to set up a static router port.
Workaround
Do not set up a piggyback port to mirror an intelligent multicast router port.
Issue
(RN000158) If you assign port 1 of a module to a hunt group and the module is in slot 9 of a
P882 or P880, intelligent multicast traffic is not forwarded.
This issue occurs regardless of whether port 1 of the module is physically connected to the hunt
group. Merely assigning the port to the hunt group causes the issue to occur.
Workaround
Do not assign port 1 of a module to a hunt group if the module is in slot 9 of a P882 or P880.
Issue 1 February 2005
13
Functional Restrictions for the Avaya P580 and P882 Multiservice Switches, Software Version 6.2
Issue
(RN000097) If an LGMP server and LGMP client are participating in a hunt group and the flood
link fails, multicast traffic stops on the LGMP client for approximately 4 to 6 minutes. As soon as
the current IGMP session expires and the LGMP server receives another IGMP membership
report from the LGMP client, multicast traffic resumes.
Workaround
Not applicable.
Issue
(RN000016) Intelligent Multicasting can block protocols to nonmulticast routers. If you have
enabled Intelligent Multicasting and have configured a VLAN to one or more nonmulticast
routers or multicast-capable end stations, Intelligent Multicasting configures router ports where
multicast-enabled routers reside. These multicast router ports allow all multicast packets to the
adjacent multicast routers. Ports connected to nonmulticast-enabled routers are not considered
router ports and do not receive multicast traffic. The issue can occur when multiple IP multicast
addresses are mapped to the same multicast MAC address, resulting in protocol packets not
being sent to the adjacent non-multicast enabled routers.
Example:
The unicast routing protocol in use on all connected routers is OSPF, and all ports are on the
same VLAN. An end station joins the IP multicast group 226.128.0.5 on port 1. The MAC
address for the group is 01:00:5E:00:00:05. IGMP snooping creates a session for this MAC
address, with port 1 as the client port. There is a non-multicast OSPF router attached to port 2.
OSPF uses the IP multicast link scoped group 224.0.0.5, which also maps to a MAC address of
01:00:5E:00:00:05. Because port 2 is not considered a router port, and it is not part of the
01:00:5E:00:00:05 session, the switch only passes OSPF messages out port 1. Other
protocols, such as the Service Location Protocol (RFC 2608), use 224.0.1.22 and 224.0.1.35,
which can be blocked by end stations joining sessions that map to the same MAC address.
Note:
Note:
This is the same issue that is discussed in the Microsoft Product Support Article
Q223136 involving RRAS setup. This specific issue, however, should not break
routing protocols as suggested in this article because the Avaya multiservice
switches ignore joins for local multicast groups (224.0.0.x).
14 Doc No. 10-300513
Functional Restrictions and Workarounds
Workaround
Check that all ports that are connected to the router are configured as router ports. This
prevents all router-to-router messages from being blocked.
If other non-router protocols, such as the Server Location Service, are in use, create static
sessions as needed. Do not create static sessions that conflict with the protocols used on your
network.
See the following Web site for a complete list of internet multicast addresses recognized by the
IANA: http://www.iana.org/assignments/multicast-addresses.
Note:
Note:
Enable is the default setting for Rate Limiting on 10/100 Mbps ports. Multicast
traffic and broadcast traffic is rate-limited (to 20%) on 10/100 Mbps ports.
Multicast traffic is rate-limited unless Intelligent Multicasting is enabled. Multicast traffic for
which the Intelligent Multicast session was created is not subject to rate limiting unless the rate
limiting state is set to Enable (all multicasts included).
IP Source Routing
Issue
(RN000161) If you disable IP source routing, the switch continues to allow source routing.
Workaround
Not applicable.
IRDP
Issue
(RN000315) The switch allows you to set the maximum advertisement interval to greater than
the advertisement life time. However, the advertisement life time must always be greater than or
equal to the maximum advertisement interval.
Workaround
Always set the advertisement life time to greater than or equal to the maximum advertisement
interval.
Issue 1 February 2005
15
Functional Restrictions for the Avaya P580 and P882 Multiservice Switches, Software Version 6.2
Issue
(RN000309) If you use the CLI to modify the IRDP configuration of an interface and you then
refresh the display of the ICMP Router Discovery Protocol Web page, the IRDP settings revert
to their previous values. This problem occurs only when the Web Agent is displaying the ICMP
Router Discovery Protocol Web page when you use the CLI to modify the IRDP configuration.
Workaround
Do not use the CLI to modify an IRDP configuration while the Web Agent is displaying the ICMP
Router Discovery Protocol Web page. Either use the Web Agent to modify the IRDP
configuration, or log out of the Web Agent and use the CLI.
Layer 3 Forwarding Cache
Issue
(RN000273) The Frame Forwarding Statistics Web page does not display statistics for the first
two fabric ports that a 10-Gigabit modules uses. For example, if a 10-Gigabit module is installed
in slots 7 and 8, the Frame Forwarding Statistics Web page displays statistics only for the two
fabric ports that are associated with slot 8. Statistics for the fabric ports that are associated with
slot 7 are not available.
The Frame Statistics Web page displays statistics by fabric port number and chip index
(forwarding engine) number. Slots 2 through 7 of the P580 and slots 2 through 17 of the P882
have 2 fabric ports per slot. The 10-Gigabit module has 8 forwarding engines (2 per fabric port).
For a complete explanation of fabric port numbers and chip indexes, see “Identify the Ports” in
Chapter 13, “Configuring Access Lists.”
Workaround
Not applicable.
16 Doc No. 10-300513
Functional Restrictions and Workarounds
NEDR
Issue
(RN000267) Occasionally, if you use the set port network-error-detection command to
enable network error detection (NEDR) on a 10-Gigabit port, the following error message is
displayed:
Set port network-error-detection failed: <10-Gigabit port number>.
Workaround
NEDR is successfully enabled regardless of the error message. Ignore the error message.
Issue
(RN000268) The set port network-error-detection all action off CLI command does not turn
off NEDR on 10-Gigabit ports.
Workaround
To turn off network error detection for specific 10-Gigabit ports, use the set port
network-error-detection <mod-port-range> action off command.
Online Help
Issue
(RN000317) If you install the online help files in the root directory of the Web server, the Web
Agent does not display the online help files when you click the help icons.
Workaround
Install the online help files in a subdirectory.
Issue 1 February 2005
17
Functional Restrictions for the Avaya P580 and P882 Multiservice Switches, Software Version 6.2
OSPF
Issue
(RN000316) If you use the show ip ospf neighbor <interface-name> command to view
neighbors of an NBMA interface, the Type field for the neighbors displays BROADCAST instead
of NBMA.
Workaround
View neighbors by the neighbor ID (use the [<neighbor-id>] option) or view the complete list of
neighbors.
Issue
(RN000170) If you disable the advertisement setting for an OSPF summary, the switch does not
retain the setting. When you reset the switch, it enables the advertisement setting.
Workaround
Use the OSPF Summaries Web page to delete the summary if you do not want the IP network
address that is defined in the summary to be advertised.
Issue
(RN000171) The no area <area-id> range <ip-address> <mask> CLI command does not
delete an OSPF summary.
Workaround
Use the OSPF Summaries Web page in the Web Agent to delete OSPF summaries.
18 Doc No. 10-300513
Functional Restrictions and Workarounds
Point-to-Point Protocol (PPP) and Telnet
Issue
(RN000023) A Telnet session to the serial port by means of PPP may time out during attempts
to transfer large files, such as executable images, to a Trivial File Transfer Protocol (TFTP)
server. However, this issue does not terminate the file transfer. An in-progress TFTP file transfer
ends only after the file transfer is completed.
Workaround
Not applicable.
Issue
(RN000024) If you enter the baud rate change command more than once, the new baud rate
may take effect before the current PPP connection is terminated. This results in the termination
of the PPP connection.
Workaround
Reestablish the PPP connection.
Issue
(RN000288) A Telnet session is lost if a PCMCIA card is initialized from the session, or if an
uninitialized PCMCIA card is introduced into the supervisor while a Telnet session is open.
Workaround
Reconnect the telnet session.
Issue 1 February 2005
19
Functional Restrictions for the Avaya P580 and P882 Multiservice Switches, Software Version 6.2
Fabric Mode 1 Port Mirroring
Issue
(RN000231) When you use Fabric mode 1 port mirroring to mirror a port range on an 80-series,
10/100 module, the last port in the range is not mirrored.
The switch allows you to enter a complete port range, for example ports 1 through 12 on a
24-port module. However only ports 1 through 11 are actually mirrored.
Workaround
Not applicable.
Issue
(RN000233) If you change the configuration of a port that is participating in a port mirror with a
piggyback port, a topology change occurs. The port may lose connectivity for the duration of this
topology change (approximately 30 to 45 seconds).
Workaround
If you need to change the configuration of a port and want the port to participate in a port mirror,
change the port configuration before you enable the port mirror.
Issue
(RN000177) If you set up a port mirror on a 50-series switch that is operating in Fabric mode 1,
and you monitor transmit traffic through a piggyback port, the frames that are received on the
mirror port from the piggyback port are all tagged with a VLAN identification of ten. This issue
occurs regardless of which VLAN number is bound to the source port. This issue is a display
issue only. It has no effect on traffic patterns or flow.
Workaround
Not applicable.
20 Doc No. 10-300513
Functional Restrictions and Workarounds
Fabric Mode 2 Port Mirroring
Issue
(RN000331) Fabric mode 2 port mirroring does not monitor transmitted (egress) broadcast
packets.
Workaround
You can monitor broadcast packets by placing a network analyzer on the VLAN that the source
port is assigned to.
Issue
(RN000174) Fabric mode 2 port mirroring does not monitor transmitted (egress) packets that
have a multicast destination address.
Workaround
You can monitor multicast packets by placing a network analyzer on the VLAN that the source
port is assigned to because the multicast packets are flooded on the VLAN.
Issue
(RN000245) All traffic that is received on a Fabric Mode 2 mirrored port is tagged with a priority
of three, regardless of what the actual priority of the traffic is. This is a display problem and does
not affect the actual flow or priority of the traffic.
Workaround
Ignore the incorrectly displayed priority tags on the Fabric Mode 2 mirrored port traffic.
Issue
(RN000175) If you hot swap a module on which you have a port mirror set up, the port mirror is
lost. The switch may retain some settings for the port mirror. However, the port mirror does not
function.
Workaround
After hot swapping the module, set up the port mirror again.
Issue 1 February 2005
21
Functional Restrictions for the Avaya P580 and P882 Multiservice Switches, Software Version 6.2
Port Redundancy
Issue
(RN000301) For 50-series, 48-port modules, the Create Port Redundancy Pair Web page
displays port numbers 49 through 54, not 1 through 48.
Workaround
Use the CLI to create a port redundancy pair on 50-series, 48-port modules.
80-Series QoS
Issue
(RN000259) If you use the Web Agent to configure an address forwarding table entry with a
high or low priority setting on an 80-series module, the switch appears to accept the setting.
Eighty-series modules support eight priority queues, which you can currently use only the CLI to
configure. Although 80-Series modules do not support high and low priority settings, the
command is saved to the running configuration and the startup configuration files. When the
switch runs the command, an error message is displayed in the event log file.
Workaround
Use the CLI to set the QoS priority settings for 80-Series modules.
RADIUS
Issue
(RN0000321) There is no CLI command to clear the realm that is authorized to log in to the
switch. However, you can change the realm.
Workaround
Use the Web Agent to clear the realm that is authorized to log in to the switch.
22 Doc No. 10-300513
Functional Restrictions and Workarounds
Resetting the Switch
Issue
(RN000319) If your Web browser is configured to use a Squid proxy server, you may be unable
to reset the switch from the Web Agent.
Workaround
Configure the Web browser to bypass the proxy server when you connect to the switch or use
the CLI to reset the switch.
RIP
Issue
(RN000310) If you enable authentication on a RIP interface but do not specify a password or
key chain, the interface does not receive RIP updates from the RIP routers to which it is
connected.
Workaround
Always specify a password or key chain when you enable authentication on a RIP interface.
Issue
(RN000305) If authentication is enabled on a RIP interface, and you disable it, the Auth
Key/MD5 Key Chain field on the RIP Interfaces Web page is not cleared. This issue occurs
only in the Web Agent and is only a display issue. Enabling and disabling of authentication
works correctly.
Workaround
Not applicable.
Issue 1 February 2005
23
Functional Restrictions for the Avaya P580 and P882 Multiservice Switches, Software Version 6.2
Issue
(RN000264) If you use the network command to enable RIP on an IP interface and
inadvertently enter an IP interface that does not exist, the switch may enable RIP on an
interface that does exist and on which RIP is disabled.
Workaround
Not applicable.
Issue
(RN000033) If you set an interface to use RIP V1/V2 and connect the interface to a RIP V1
interface, the RIP V1/V2 interface sends V2 packets to the V1 interface.
Workaround
Set the interface to RIP V1 if it is connected to a RIP V1 interface.
set module notes Command
Issue
(RN000266) If you use the set module notes command to add note text for a module and later
delete the note text, the show module command, running configuration file, and Module Details
Web page display corrupt data in the module notes.
Workaround
Use the Web Agent to delete module notes.
24 Doc No. 10-300513
Functional Restrictions and Workarounds
show port status Command
Issue
(RN000311) The show port status command does not show the speed of Gigabit or 10-Gigabit
modules.
Workaround
View the Speed State field on the Physical Port Configuration Web page for the module.
Slot 2 of P580 and P882 Chassis
Issue
(RN000015) P580 and P882 switches that are operating in Fabric mode 2 do not route inbound
multicast traffic that is received on an unlicensed 80-series module that is installed in slot 2.
Workaround
Use slots 3 through 17 on the P882 or slots 3 through 7 on the P580.
SNMP
Issue
(RN000244) If you use the CajunOSPF.mib to set the number of Equal Cost Multi Path (ECMP)
routes on the switch, you are permitted to set it to an unlimited number. The switch supports a
maximum of eight ECMP routes.
Workaround
The number of ECMP routes on the switch is set to eight, by default. It is highly recommended
that you do not change this setting.
Issue 1 February 2005
25
Functional Restrictions for the Avaya P580 and P882 Multiservice Switches, Software Version 6.2
Issue
(RN000190) The promLogTableMaxSize object and promShutdownLogTableMaxSize object in
the ProminetMIB.txt allow you to enter invalid values. If you enter invalid values, however, the
settings revert to the default settings when you reset the switch.
Valid values for the promLogTableMaxSize object are 128, 512, 1024, and 2048.Valid values for
the promShutdownLogTableMaxSize object are 16, 32, and 64.
Workaround
Use the General Event Management Web page or following CLI commands to set the size of
the event log and shutdown log:
●
logging history size for the event log
●
logging shutdown size for the shutdown log
Issue
(RN000192) If you use the ProminetMIB.txt to configure SNMP trap logging, you are allowed to
enable logging for certain event classes that you are prevented from enabling when you use the
Web Agent and the CLI. When you reset the switch after saving the running configuration file to
the startup configuration file, the invalid settings are lost, and the defaults are restored.
Workaround
To configure SNMP trap log settings, use the Web Agent or the CLI.
Issue
(RN000137) You cannot use SNMP to create an IPX static route. If you attempt to use SNMP to
create an IPX static route, the IPX static route is not created.
Workaround
Use either the Web Agent or CLI to create an IPX static route.
Issue
(RN000286) Start traps continue to be sent after issuing the no logging traps start command.
Workaround
Not Applicable.
26 Doc No. 10-300513
Functional Restrictions and Workarounds
Spanning Tree
Issue
(RN000307) The switch generates a syntax error if you attempt to set the edge-port state for a
module by using the set port edge admin state <module> {edge-port | non-edge-port}
command.
All other set port commands allow you to issue the command for a module.
Workaround
Specify a port or port range when you use the set port edge admin state command.
Issue
(RN000306) If the administrative path cost for a 10-gigabit port is set to 0, the operational path
cost of the port is incorrect. If the default path cost is set to:
●
Rapid Spanning Tree, the operational path cost should be 2000, but is 2500.
●
Common Spanning Tree, the operational path cost should be 2, but is 3.
For information on how the operational path cost is calculated, see “Configuring a Bridge Port”
in Chapter 7, “Configuring Rapid Spanning Tree,” of the User Guide for the Avaya P580 and
P882 Multiservice Switches, Software Version 6.2.
Workaround
Set the administrative path cost for 10-gigabit ports to the correct value.
Issue
(RN000275) The Name field on the Spanning Tree Bridge Port Information Web page does not
display port names for ports on ATM Uplink modules.
Workaround
Use the Switch Port Configuration Web page to view port names for ports on ATM Uplink
modules.
Issue 1 February 2005
27
Functional Restrictions for the Avaya P580 and P882 Multiservice Switches, Software Version 6.2
Static Routes
Issue
(RN000139) You cannot use the CLI to modify a static route. If you attempt to use the ip route
<ip-address> <mask> <next-hop> <cost> [{high | low}] CLI command to modify a static
route, the routing table will not reflect the change that you make.
Workaround
Either use the Web Agent to modify the static route or, if you want to use the CLI, delete the
static route and then create a new one with the new settings.
80-Series Supervisor Module
Issue
(RN000106) When you manually push the Reset button on the 80-series supervisor module, it
stops responding and does not fully reset.
Workaround
Remove and reinsert the module to reset it.
Switch Elements
Issue
(RN000211) If you use the Switch Fabric Status Web page or set fabric
enable-redundant-element command to change the redundant element to an element other
than the default setting, the active supervisor module loses contact with the standby supervisor
module. The default setting is normal.
Workaround
Do not change the redundant switch element to an element other than the default setting of
normal.
28 Doc No. 10-300513
Functional Restrictions and Workarounds
Upgrading the Application Software
Issue
(RN000271) If RAM usage exceeds 30 MB and you synchronize the active and standby
supervisor modules to upgrade the application software, the synchronization fails.
To view current RAM usage, use the RAM Contents Web page or show system ram command.
Current RAM usage is displayed in the Used field for dynamically allocated memory.
Workaround
Upgrade the application software during a maintenance period.
VLANs
Issue
(RN000249) If a 10-Gigabit port is bound to a VLAN, but nothing is physically connected to the
port, the following Web page and CLI display the 10-Gigabit port number incorrectly:
●
The VLAN Switch Ports Web page displays <slot N>-<slot N+1>.8 instead of <slot
N>-<slot N+1>.1.
●
The show vlan CLI command displays <slot N>-<slot N+1>/8 instead of <slot N>-<slot
N+1>/1.
For example, if 10-Gigabit port 7-8.1 is bound to VLAN 10, but nothing is connected to the port:
●
The VLAN Switch Ports Web page displays 7-8.8 instead of 7-8.1.
●
The show vlan 10 command displays 7-8/8 instead of 7-8/1.
Workaround
Not applicable.
Issue
(RN000212) If you change the VLAN binding setting from Bind to All to Bind to Receive for a
trunk port, a loss of connectivity may occur in the network.
Issue 1 February 2005
29
Functional Restrictions for the Avaya P580 and P882 Multiservice Switches, Software Version 6.2
Workaround
After changing the VLAN binding setting from Bind to All to Bind to Receive, delete the AFT
entries for the VLANs that are bound to the trunk port.
To delete the AFT entries for a specific VLAN:
1. Open the VLAN Configuration Web page (L2Switching > VLANs > Configuration).
2. In the Table Index field, click the index number that is associated with the VLAN for which
you want to delete AFT entries. The Address Table Instance Web page is displayed.
3. Click Delete All Learned Entries.
Issue
(RN000226) If you want a port to use both the VLAN auto-learning feature and VLAN binding
type of Bind to Received or Bind to All, the port may not be automatically added to the VLAN
if you do not set the VLAN binding type first.
Workaround
If you want a port to use both the VLAN auto-learning feature and VLAN binding type of Bind to
Received or Bind to All, set the VLAN binding type before you set Auto-learn to Enable.
VRRP
Issue
(RN000235) The switch does not support both Proxy ARP and VRRP on the same IP interface.
Workaround
Not applicable.
30 Doc No. 10-300513
Technical Support
Technical Support
To contact Avaya Technical Support:
●
From the United States:
1-800-237-0016
●
From North America:
1-800-242-2121
●
Outside North America:
Contact your distributor
Documentation Feedback
If you have comments about the technical accuracy or general quality of this document, please
send us an e-mail message at techpubs@avaya.com.
Please cite the document title, part number, and page reference, if appropriate.
Issue 1 February 2005
31
Functional Restrictions for the Avaya P580 and P882 Multiservice Switches, Software Version 6.2
32 Doc No. 10-300513
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertising