Table of Contents

Release Notes for the Catalyst 8540 Cisco IOS Release 12.1(5)EY22

Release Notes for the Catalyst 8540 Cisco IOS Release 12.1(5)EY22

February 14, 2002

Catalyst 8540 CSR Cisco IOS Release 12.1(5)EY2

Text Part Number: 78-12261-01, C0

This document describes the features and caveats for Cisco IOS Release 12.1(5)EY2 for the Catalyst 8540 multiservice ATM switch router (MSR), the Catalyst 8540 campus switch router (CSR). For relevant features, we've provided some information on Cisco IOS Releases 12.0.

Note   All information pertains to both the Catalyst 8540 MSR and Catalyst 8540 CSR platforms, unless differences between the platforms are noted in the text.

Contents

This document includes the following sections:

• Introduction
  
  
• System Requirements
  
  
• New and Changed Information
  
  
• Caveats for the Catalyst 8540 MSR
  
  
• Caveats for the Catalyst 8540 CSR
  
  
• Caveat Symptoms and Workarounds
  
  
• Restrictions
  
  
• Route Processor and Switch Module Redundancy
  
  
• Autonegotiation (Catalyst 8540 CSR)
  
  
• Interoperability
  
  
• Incompatibility
  
  
• Y2K Compliance
  
  
• Related Documentation
  
  
• Obtaining Documentation
  
  
• Obtaining Technical Assistance
  
  

Introduction

The Catalyst 8540 is a 13-slot, modular chassis with optional dual, fault-tolerant, load-sharing AC or DC power supplies.

The Catalyst 8540 MSR switch router provides a 20-Gbps full-duplex nonblocking switch fabric with switched ATM connections to individual workstations, servers, LAN segments, or other ATM switches and routers using fiber-optic, unshielded twisted-pair (UTP), and coaxial cable.

The Catalyst 8540 CSR switch router belongs to a class of high-performance Layer 3 switch routers and is optimized for the campus LAN or the intranet. The Catalyst 8540 CSR switch router provides both wirespeed Ethernet routing and switching services.

System Requirements

This section describes the system requirements for Cisco IOS Release 12.1(5)EY2 and includes the following sections:

• Memory Defaults and Upgrade Options
  
  
• Hardware Supported on the Catalyst 8540 MSR
  
  
• Hardware Supported for Catalyst 8540 CSR
  
  
• Software Release Requirements
  
  

Memory Defaults and Upgrade Options

Table 1 lists the default Flash and DRAM memory for the Catalyst 8540, as well as memory upgrade options.

To check that your system has a 16-MB boot Flash SIMM, enter the show hardware EXEC command. The part numbers for Catalyst 8540 switch router route processors with a default 16-MB boot Flash SIMM follow:

• 73-2644-06 Rev. A0 for the Catalyst 8540 MSR
  
  
• 73-3775-03 Rev. A0 for the Catalyst 8540 CSR
  
  

If you have an 8-MB boot Flash SIMM, and have no additional memory installed, we recommend that you order a spare Flash PC card programmed with the latest version of the system image.

Note   We recommend that you use a San Disk 48-MB PC Card to download and store a copy of the switch router software image. This allows you to store two or more images at the same time.

A Flash PC Card must be ordered as a spare part. See Table 1 for part numbers. For information on upgrading a Flash PC Card, see the "Upgrading a PC Card" section. For more detailed information on Flash PC Cards, refer to the "Configuring the Route Processor " chapter of the Layer 3 Switching Software Feature and Configuration Guide.

Alternatively, you can use one of the following options to accommodate the larger image:

• Option 1 - If you already have a Flash PC card, download the system image to the Flash PC card.
  
  

  ---

  Note   If you have a Smart Modular, Sharp, or Intel 2+ Flash PC card that was formatted using a Cisco IOS software release prior to 12.0(4a)W5(11a), reformat it with Cisco IOS Release 12.1(5)EY2 prior to downloading the image (you might need to boot the image from a TFTP server to format the PC Flash card). Do not erase the system image on the boot Flash SIMM. If the procedure fails, you will need it to recover. (See caveat CSCdm47012 later in these release notes for more information.)

  ---

Then do the following:

• Option 2—Download the system image to a TFTP server and boot the system image from the TFTP server. Enter the boot system tftp filename ip-address global configuration command to boot the system image from the TFTP server, instead of booting from the system-code SIMM (default).
  
  

An example follows:

Switch(config)# boot system tftp cat8540m-wp-mz.121-x.e 172.20.52.3

---

Note   You can boot only the primary route processor from a TFTP server, not the secondary.

---

---

Note   The boot ROM on the Catalyst 8540 MSR can be field-upgraded via the reprogram command. For more information about upgrading the boot ROM, see the ATM  and Layer 3 Switch Router Command Reference.

---

For more information about downloading system images and changing the default boot image, refer to the "File Management" chapter of the Configuration Fundamentals Configuration Guide in the Cisco IOS software documentation set.

Upgrading a PC Card

This section describes how to upgrade to a SanDisk 48-MB PC card. PC upgrade cards are available in 48-MB.

Note   You need Cisco IOS Release version 12.1(5)EY or higher and rommon version 12.0(14)W5(20) or higher to upgrade to the SanDisk PC card. If you do not meet these minimum version requirements, the SanDisk PC card will not work.

To upgrade the PC card, follow these steps:

Step 2   Once the switch is up and running, use the copy command to copy the rommon image to the boot Flash SIMM.

Step 3   Reprogram the rommon image using the reprogram command.

Example

The following example shows the rommon being reprogrammed:

switch# reprogram bootflash:<rommon-image-name> rommon 
 

Step 4   Load the switch with the latest Cisco IOS release image again.

Step 5   Enter the format command to format the PC card. It is now ready for use.

Example

The following example shows the format command being entered on slot 0:

switch# format disk0:

 

Hardware Supported on the Catalyst 8540 MSR

Table 2 lists the hardware modules supported on the Catalyst 8540 MSR in Cisco IOS Release 12.1(5)EY2.

Note   Although minimum software versions are listed, we strongly recommend that you use the latest available software release for all Catalyst 8540 hardware.

1The T1/E1 IMA port adapters also require carrier module FPGA image version 1.8 or later, and IMA port adapter functional image version 3.2 or later. Hardware Supported for Catalyst 8540 CSR Table 3 lists the hardware modules supported on the Catalyst 8540 CSR in the Cisco IOS Release 12.1(5)EY2. Note   Although minimum software versions are listed, we strongly recommend that you use the latest available software release for all Catalyst 8540 hardware.

Software Release Requirements

Note   We strongly recommend that you use the latest available software release for all Catalyst 8540 hardware.

To determine the version of Cisco IOS software currently running on a Catalyst 8540, log in to the switch router and enter the show version EXEC command. The following sample output is from the show version command. The version number is indicated on the second line as shown below:

Cisco Internetwork Operating System Software

IOS (tm) PNNI Software (cat8540m-WP-M), Version 12.1(5)EY2
 

Most of the interface modules supported on the Catalyst 8540 have upgradeable FPGA and functional images. The FPGA and functional images include caveat fixes, but in most cases, it is not necessary to upgrade. The release notes that describe the caveats from the FPGA and functional images are available on the World Wide Web at the following URL:

http://www.cisco.com/univercd/cc/td/doc/product/atm/c8540/fpga_rel/index.htm

For more information describing the firmware update process, refer to the section "Maintaining Functional Images (Catalyst 8540 MSR)" in the chapter "Managing Configuration Files, System Images, and Functional Images" in the ATM Switch Router Software Configuration Guide .

Feature Set Table For Catalyst 8540 MSR

The Cisco IOS software is packaged in feature sets (also called software images) depending on the platform. Each feature set contains a specific set of Cisco IOS features. Table 4 lists the software features available for the Catalyst 8540 MSR.

Release Names, Versions, and Part Numbers

Table 6 lists the release names, versions, and part numbers used with the Catalyst 8540 MSR and CSR switch routers.

.

New and Changed Information

This section lists new features that appear in this and previous releases of Cisco IOS Release 12.1. The new features are sorted by release number.

New Features in Release 12.1(5)EY2

Catalyst 8540 MSR

The following new features are available for the Catalyst 8540 MSR in Cisco IOS Release 12.1(5)EY2:

• CES Soft PVC Per Interface State.
  
  
• Catalyst 8540 Enhanced ATM Router Module.
  
  

See the "Related Documentation" section for a list of documents that describe these features.

Catalyst 8540 CSR

The following new feature is available for the Catalyst 8540 CSR in Cisco IOS Release 12.1(5)EY2:

• Port aggregation protocol (PAgP) on EtherChannels.
  
  

See the "Related Documentation" section for a list of documents that describe this feature.

New Features in Release 12.0(13)W5(19c)

Catalyst 8540 MSR

The following new features are available for the Catalyst 8540 MSR in Cisco IOS Release 12.0(13)W5(19c):

• Online diagnostic test:
  
  
  • Accessibility tests between the route processor and the interface modules and the route processor and the switch processor.
    
    
  • Online insertion and removal (OIR) diagnostic tests.
    
    
  • Snake tests through the switch router to ensure connectivity between the ports.
    
    

See the "Related Documentation" section for a list of documents that describe these features.

Catalyst 8540 CSR

The following new features are available for the Catalyst 8540 CSR in Cisco IOS Release 12.0(13)W5(19c):

• Online diagnostics on the route processor, providing the following types of tests:
  
  
  • Access tests between the route processor and the ports.
    
    
  • Online insertion and removal (OIR) diagnostic tests.
    
    
  • Snake tests throughout the switch router to ensure connectivity between the ports.
    
    

See the "Related Documentation" section for a list of documents that describe these features.

Caveats for the Catalyst 8540 MSR

Resolved Caveats - Cisco IOS Release 12.1(5)EY2

Cisco IOS Release 12.1(5)EY2 is a rebuild of Cisco IOS Release 12.1(5)EY. All the caveats listed in this section are resolved in Cisco IOS Release 12.1(5)EY2 but may be open in previous releases.

• CSCdw65903
  
  

An error can occur with management protocol processing. Please use the following URL for further information:

http://www.cisco.com/pcgi-bin/bugtool/onebug.pl?bugid=CSCdw65903

This section lists caveats for the Catalyst 8540 MSR by tracking number (DDTS #) and release number, and indicates whether the caveat has been corrected. An "O" indicates that the caveat is open in that release; a "C" indicates that the caveat is closed in that release. To find caveats for the Catalyst 8540 CSR see the "Caveats for the Catalyst 8540 CSR" section.

Table 7 lists caveats for the Catalyst 8540 MSR:

Caveats for the Catalyst 8540 CSR

Resolved Caveats - Cisco IOS Release 12.1(5)EY2

Cisco IOS Release 12.1(5)EY2 is a rebuild of Cisco IOS Release 12.1(5)EY. All the caveats listed in this section are resolved in Cisco IOS Release 12.1(5)EY2 but may be open in previous releases.

• CSCdw65903
  
  

An error can occur with management protocol processing. Please use the following URL for further information:

http://www.cisco.com/pcgi-bin/bugtool/onebug.pl?bugid=CSCdw65903

This section lists caveats for the Catalyst 8540 CSR by tracking number (DDTS #) and release number, and indicates whether the caveat has been corrected. An "O" indicates that the caveat is open in that release; a "C" indicates that the caveat is closed in that release. For information on Catalyst 8540 MSR see "Caveats for the Catalyst 8540 MSR" section.

Table 8 lists caveats for the Catalyst 8540 CSR:

Caveat Symptoms and Workarounds

This section summarizes caveat symptoms and suggested workarounds for the Catalyst 8540.

• CSCdt53814
  

An ARM port might forward certain frames.

Symptom: An ARM port configured for transparent bridging and in blocking state might

forward certain frames.

Workaround: Depending on topology, a work-around might be to ensure that a non-ARM port

is in blocking state. Where this is not feasible, power cycle the ARM port that is in blocking state.

• CSCdt43218
  

Packets destined to the below adjacency might disappear.

Symptom: If SVC is configured on the ARM or the Enhanced ARM and an OIR is performed on the module, the adjacency available across the SVC will remain 'Valid' on the Ethernet port interface or Gigabit Processor interface cam. This will cause packets destined to that adjacency to go into a disappear.

Workaround: Before performing an OIR on the ARM or the Enhanced ARM module, remove any sub-interfaces that have SVC configurations on them.

• CSCdt28324
  

00:45:25: %LINK-5-CHANGED: Interface ATM11/0/ima1, changed state to going down
 00:45:29: %LINK-3-UPDOWN: Interface ATM11/0/ima1, changed state to up 
 00:48:56: wrong response present for the cmd given cmd: 0x35 resp : 0x3D
 00:49:37: %SUNI622: Read diagnostics for ATM3/0/1 failed(1)
 

Symptom: After performing a route processor switchover several times, and then reloading only the secondary route processor and booting up again, the primary route processor might display the following error messages:

 00:45:25: %LINK-5-CHANGED: Interface ATM11/0/ima1, changed state to going down
 00:45:29: %LINK-3-UPDOWN: Interface ATM11/0/ima1, changed state to up 
 00:48:56: wrong response present for the cmd given cmd: 0x35 resp : 0x3D
 00:49:37: %SUNI622: Read diagnostics for ATM3/0/1 failed(1)
 

This does not impact functionality.

Workaround: None.

• CSCdt24822
  

Under the following circumstances, IP packets coming into the POS interface will not be hardware switched.

Symptom: The IP routing flag is set to off in IF-entry for a POS interface when encapsulation is changed from ppp to hdlc or when hdlc is changed to ppp. Since the IP routing flag is set to off, IP packets coming into the POS interface will not be hardware switched

Workaround: Enter the shutdown command, followed by the no shutdown command on the POS interface.

• CSCdt21568
  

The ARM1 interface shuts down after entering the epc portstuck-manual-reload command with IP traffic.

Symptom: The ARM1 interface shuts down after entering the epc portstuck-manual-reload command with IP traffic.

Workaround: None.

• CSCdt20610
  

If an 8-port Gigabit Ethernet interface module is hot swapped after configuring PAgP between two Catalyst 8540 CSRs, members on the hot swapped side of the port channel move out of the port channel.

Symptom: If an 8-port Gigabit Ethernet interface module is hot swapped after configuring PAgP port channel between two Catalyst 8540 CSRs, members on the hot swapped side of the port channel move out of it while the members on the side that was not hot swapped remain in the port channel. This happens only with the 8-port Gigabit Ethernet interface module.

Workaround: After some time, PAgP might add the hot swapped interface back to the port channel. If this does not happen, configure the ports manually.

• CSCdt17850
  

The static ARP entry remains associated with the original interface instead of with the sub-interface under the following circumstances.

Symptom: If a static ARP is configured for one interface and then the IP address for that interface is moved to a sub-interface, the static ARP entry remains associated with the original interface instead of with the sub-interface.

Workaround: When the IP address is reconfigured to a sub-interface off of the original interface, delete and reconfigure the ARP address also.

• CSCdt17296
  

The OC48 might generate the following error messages:

%ATMCORE-3-INTERNAL_ERROR: connAllocateHalfLeg: tag neighbor leg present
%ATMCORE-3-INTERNAL_ERROR: atmCore_connSetupUniDirXconn: i/p Connection Leg Exists

Symptom: After performing an online insertion and removal of an OC48 port adapter, entering the show command and the no show commands on the OC48 might generate the following error messages:

%ATMCORE-3-INTERNAL_ERROR: connAllocateHalfLeg: tag neighbor leg present
%ATMCORE-3-INTERNAL_ERROR: atmCore_connSetupUniDirXconn: i/p Connection Leg Exists

Workaround: Perform one more online insertion and removal and ensure that at least two minutes elapse between any two online insertions and removals.

• CSCdt15169
  

The Catalyst 8540 MSR displays old buffers detected messages.

Symptom: After configuring an ipx network between a Catalyst 8540 MSR and a Router 7500, the Catalyst 8540 MSR displays old buffers detected messages. This does not impact functionality.

Workaround: None.

• CSCdt13310
  

An active Fast Ethernet interface might become administratively down after the route processor automatically switches over following the entry of the test crash command.

Symptom: An active Fast Ethernet interface might become administratively down after the route processor automatically switches over following entry of the test crash command.

Workaround: None.

• CSCdt10401
  

  imapam_send_stored_config: config_status is UNI
  imapam_send_stored_config: config_status is UNI
  imapam_send_stored_config: config_status is UNI
 

Symptom: After switching over the route processor several times, the following message might display:

  imapam_send_stored_config: config_status is UNI
  imapam_send_stored_config: config_status is UNI
  imapam_send_stored_config: config_status is UNI
 

This happens when an IMA port adapter is present in the chassis. Once the switch router boots up no functionality impact is seen.

Workaround: None.

• CSCdt04810
  

00:58:16: %SYS-3-MGDTIMER: Uninitialized timer, timer stop, timer = 644B0550.
 -Process= "ATM ARP INPUT", ipl= 0, pid= 30
 -Traceback= 600CE1BC 600CF2A4 60792B0C 60796850 60797744 600BBA64 600BBA50shut
Enter hex value: 600CE1BC 600CF2A4 60792B0C 60796850 60797744 600BBA64 600BBA50
  0x600CE1BC:mgd_timer_complain_uninit(0x600ce190)+0x2c
  0x600CF2A4:mgd_timer_stop(0x600cf26c)+0x38
  0x60792B0C:atm_arp_stampvc(0x60792ad4)+0x38
  0x60796850:atm_inarp_rcvdreq(0x6079620c)+0x644
  0x60797744:atm_arp_process(0x60796f30)+0x814
  0x600BBA64:r4k_process_dispatch(0x600bba50)+0x14

0x600BBA50:r4k_process_dispatch(0x600bba50)+0x0

Symptom: After entering the shutdown command and no shutdown command repeatedly on an ARM interface with a large number of CLIP clients (more than 32), the following error message appears:

 00:58:16: %SYS-3-MGDTIMER: Uninitialized timer, timer stop, timer = 644B0550.
 -Process= "ATM ARP INPUT", ipl= 0, pid= 30
 -Traceback= 600CE1BC 600CF2A4 60792B0C 60796850 60797744 600BBA64 600BBA50shut
Enter hex value: 600CE1BC 600CF2A4 60792B0C 60796850 60797744 600BBA64 600BBA50
  0x600CE1BC:mgd_timer_complain_uninit(0x600ce190)+0x2c
  0x600CF2A4:mgd_timer_stop(0x600cf26c)+0x38
  0x60792B0C:atm_arp_stampvc(0x60792ad4)+0x38
  0x60796850:atm_inarp_rcvdreq(0x6079620c)+0x644
  0x60797744:atm_arp_process(0x60796f30)+0x814
  0x600BBA64:r4k_process_dispatch(0x600bba50)+0x14
  0x600BBA50:r4k_process_dispatch(0x600bba50)+0x0 

This does not impact functionality.

Workaround: The shutdown command, followed by a no shutdown command after a wait for a few minutes recovers this scenario.

• CSCdt04015
  

When entering the shutdown command on the OC48 interface, the following traceback might be displayed with spurious memory access at snmp_trap:

 601BABD8 60AE7404 60AE7448 60AE76B0 60AE7F38 60AEEAAC 60AF0398 60AE0D30 60096D1C 
608C4924 608C5344 608C8C00 608E3380 60D06C8C 608E29DC

Symptom: When issuing the shut down command on the OC48 interface, the following traceback might be displayed with spurious memory access at snmp_trap:

601BABD8 60AE7404 60AE7448 60AE76B0 60AE7F38 60AEEAAC 60AF0398 60AE0D30 60096D1C 
608C4924 608C5344 608C8C00 608E3380 60D06C8C 608E29DC

This does not affect functionality.

Workaround: None.

• CSCds95813
  

A system running PNNI might reject an ATM call SETUP.

Symptom: A system running PNNI with Cisco IOS Release 12.0(7)W5(15c) will reject an ATM call SETUP if the setup includes the 5a information element coded with associated signaling, explicit VPCI, and any VCI.

If another ATM switch sends a setup that includes the 5a information element coded with associated signaling, explicit VPCI, and any VCI, the system will release the call with cause code 35: requested VPCI/VCI not available.

Call setups that include the 5a information element coded with the associated signalling, explicit VPCI, and explicit VCI signaling, including those made by Cisco ATM switches, are not affected by this problem. This interoperability issue exists between Cisco ATM switches and other vendor switches that do not explicitly request the VCI value in the call setup.

Workaround: None.

• CSCds90383
  

Spurious memory access at pim_igmp_new_dr_querier might be seen when running PIM-SM with multicast traffic on ARM interfaces.

Symptom: Spurious memory access at pim_igmp_new_dr_querier might be seen when running PIM-SM with multicast traffic on ARM interfaces. This happens when DR changes are seen. This does not impact functionality.

Workaround: None.

• CSCds49175
  

The show hardware detail command does not show the actual version of FPGA for any of the daughter cards.

Symptom: The show hardware detail command does not show the actual version of the FPGA for any of the daughter cards. This shows the version of the FPGA motherboard which is misleading.

Workaround: None.

• CSCds48921
  

The atm arp-server nsap command is removed from the running configuration upon reloading the switch.

Symptom: The atm arp-server nsap command is removed from the running configuration upon reloading the switch.

Workaround: The copy startup-config running-config command will restore the original configuration.

• CSCds44607
  

An error might occur when you save the running configuration.

Symptom: If you save the running configuration, you may see the following error:

ROUTER# copy run start

Destination filename [startup-config]?
startup-config file open failed (File table overflow)
 

This happens when you enter a write mem command or a copy running-config startup-config command. Enter a show file command to show the 127 entries of private configuration.

Workaround: Save the running configuration in a file, reload the router, and then enter a write mem command or copy running-config startup-config command.

• CSCds43859
  

The show interface atm command indicates 0 bits/sec output even when packets are being sent out from an ATM OC-12 interface module.

Symptom: Although packets are being sent out from an ATM OC-12 interface module, the 5-minute output rate shown using the show interface atm command indicates 0 bits per second output. This is not consistent with the output rate shown when the show atm traffic command is entered.

Workaround: None.

• CSCds40705
  

The Xconnect setup fails for unidirectional TVC if there is another one with a different direction and the same vpi/vci on particular interface of the Catalyst 8540 MSR.

Symptom: The Xconnect setup fails for unidirectional TVC if there is another one with a different direction and the same vpi/vci on a particular interface of the Catalyst 8540 MSR. This can be seen only if VC merge is disabled.

Workaround: None.

• CSCds40640
  

ARP timer setting is set to default after replacing card.

Symptom: If you set the ARP timers on an interface and replace the module, the startup-configuration is not loaded into the card. All ARP timers are reset to default.

Workaround: None.

• CSCds30803
  

Output queue on BVI interface keeps growing.

Symptom: Under certain conditions, the BVI output queue might get stuck when queueing outgoing packets but not dispatching them to hardware. This causes the output queue on the BVI interface to grow constantly.

Workaround: Create another BVI interface and move all the traffic over to the new BVI interface.

• CSCds29865
  

HSRP connectivity might be disrupted on the eight-port Gigabit Ethernet interface.

Symptom: When HSRP is running on the interface of the eight-port Gigabit Ethernet interface module, after remote link failure followed by link restoration HSRP connectivity might be disrupted.

Workaround: Configure another HSRP group with a higher number and move standby configuration to that new group.

• CSCds29781
  

Incorrect output error counters on the Gigabit Ethernet interface.

Symptom: The output errors counter is incorrect on Gigabit Ethernet show interface command. They have a high value 4xxxxxxxxx and a clear counter command does not change it back to 0. This value can increase or decrease over time.

Workaround: None

• CSCds28912
  

IP traffic is not sent over PVC if aal5mux encapsulation is used on a point-to-point subinterface on the Catalyst 8540 MSR.

Symptom: IP traffic is not sent over a PVC if aal5mux encapsulation is used on a point-to-point subinterface on the Catalyst 8540 MSR. If the deb atm errors command is enabled, the following error messages will appear:

point-to-point interface does not have a VCD
 

Workaround: None.

• CSCds28286
  

The route processor redundancy might fail when you have both PVC and bridging configured on the ARM sub-interface.

Symptom: The route processor redundancy might fail if you have both PVC and bridging configured on the ARM sub-interface.

Workaround: None.

• CSCds13037
  

Route processor redundancy fails with a remove_conn_from_fabric error.

Symptom: A Catalyst 8540, which correctly boots as a fully redundant system, does not complete a route processor failover. The secondary route processor, as it resumes function as the primary after a failover, displays the following error:

%Secondary route processor Detected

remove_conn_from_fabric: Error close party failed for ... 

Workaround: None.

• CSCds09323
  

IP packets are sent over ATM router module to ATM with padding.

Symptom: Currently the ATM router module does not strip the Ethernet pad when switching data from Ethernet to ATM. This might occasionally lead to connectivity issues since some end systems do not expect to see the pad.

Workaround: None.

• CSCds08999
  

Output error counter on the egress port might increase.

Symptom: When an enhanced Gigabit Ethernet interface module sends out ISL packets with packet sizes 1531 to 1548, the output error counter on the egress port increases.

Workaround: None.

• CSCds08870
  

IP fragmentation by the enhanced two-port Gigabit Ethernet interface module is not working for some packet sizes.

Symptom: When the packets come into the Gigabit Ethernet interface modules and then sent out the POS interface, certain packet sizes on the POS are not handled by the uCode on the interface module. This is seen on packet sizes set to 1000 on POS.

Workaround: None.

• CSCds08237
  

The hierarchical VP tunnel configuration fails on a WAI-OC3-1S3M mixed mode port adapter module when it is in slot 0 subslot 1 of the C85MS-SCAM-2P carrier module.

Symptom: The hierarchical VP tunnel configuration fails on a WAI-OC3-1S3M mixed mode port adapter module when it is in slot 0 subslot 1 of the C85MS-SCAM-2P carrier module. Slot 0 subslot 0 of the carrier module can either be empty or have another card in it, and hierarchical VP tunnel configuration will still fail. However, if the mixed mode pam is inserted in slot 0 subslot 0 of the carrier module, then the hierarchical VP tunnel can be configured.

Workaround: None.

• CSCds00193
  

The show interfaces command shows BW 100000 KB after auto negotiating to 10 Mb.

Symptom: The ifSpeed is reported as 100MB even when the auto-negotiation results in 10MBit.

Workaround: None.

• CSCdr86386
  

BVI interface does not receive EIGRP hello packets.

Symptom: When a Catalyst 5500 connected to a Catalyst 8540 CSR is powered down, the BVI interface does not receive EIGRP and ospf multicast hello packets.

Workaround: None.

• CSCdr81329
  

When the network clock module quality is not accurate the NCDP will automatically disable.

Symptom: When the network clock module quality is not accurate the NCDP will automatically disable. It is normal behavior of ncdp.

You can check the ncdp status with the following:

 switch#sh ncdp port atm2/0/0
  port data --(35)-----ATM2/0/0--------------
  port_id                           : 35
  state                             : disabled 
                                       ^^^^^^^^
 

Workaround: None.

• CSCdr77057
  

The ATM router module microcode for RFC1483 does not have the ability to understand CLNS topology updates forcing the card to drop packets.

Symptom: The ATM router module microcode for RFC1483 did not have the ability to understand CLNS topology updates, forcing the card to drop packets. This also effected the IS-IS routing updates.

Workaround: Upgrade to the Cisco IOS release 12.0(11)W5(19).

• CSCdr76566
  

There is no support for SONET MIB objects in ATM uplink module.

Symptom: There is no support for SONET MIB objects in ATM uplink module.

Workaround: None.

• CSCdr74119
  

The router reloads when handling internetworking packet exchange (IPX) access-logging-messages.

Symptom: The router reloads when handling internetworking packet exchange (IPX) access-logging-messages. This situation may still occur if access-logging is not enabled.

You may exceed the 200 IPX network limit when the hardware is activated after being removed. When the hardware is reactivated, the interfaces that were not counted while the hardware was removed cause the limit to be exceeded.

Workaround: None.

• CSCdr69004
  

Enhanced two-port Gigabit Ethernet interface is up when no GBIC is present.

Symptom: When auto negotiation is disabled on an enhanced two-port Gigabit Ethernet port, it is up even if the GBIC is not present.

Workaround: None.

• CSCdr65079
  

When the module is removed from the switch, the interfaces continue to show as inserted, and the IDBs are not deleted.

Symptom: When the module is removed from the switch, the interfaces continue to show as inserted and also the IDB's are not deleted. This is not seen when time is given between the act of insertion and removal of the modules.

Workaround: Wait two minutes after OIR before inserting a new interface module into the switch.

• CSCdr58521
  

IP packets routed on point-to-point subinterfaces on the ATM uplink interface module are routed by the route processor.

Symptom: On the ATM uplink any packet routed on a point-to-point interface will be routed by the route processor.

Workaround: Do not configure point-to-point subinterfaces on the ATM uplink.

• CSCdr56326
  

epc rel on the enhanced two-port Gigabit Ethernet interface module causes the ATM uplink enhanced Gigabit interface to hang.

Symptom: When reloading a new image into the enhanced two-port Gigabit Ethernet interface module the ATM uplink enhanced Gigabit interface appears to have been reset. The enhanced two-port Gigabit Ethernet interface module download shows no effect on the ATM uplink.

Workaround: None.

• CSCdr52527
  

There is no instance of ACL card in the MIB table.

Symptom: There is no instance of ACL card in the MIB table.

Workaround: None.

• CSCdr46754
  

Fast Ethernet interface modules are not sending packets after encapsulation changes.

Symptom: With an encapsulation change on a two-port Gigabit Ethernet interface module, the interface no longer sends packets. It seems that it is receiving packets and sending packets to the route processor when necessary, but the packets are not sent.

Workaround: None.

• CSCdr45513
  

The shutdown/no shutdown command has to be entered on the CBR ports to activate the CBR ports when the 8540 is powered-up or power cycled.

Symptom: When the 8540 is powered-up or power cycled, the shutdown/no shutdown command has to be entered on the CBR ports to activate the CBR ports.

Workaround: None.

• CSCdr43610
  

When two 8540 CSR switch routers are directly connected by a two-port Gigabit Ethernet interface module, a reset of one switch router does not cause the remote switch router's interfaces to go down too.

Symptom: When two 8540 CSR switch routers are directly connected by a two-port Gigabit Ethernet interface module, a reset of one switch router does not cause the remote switch router's interfaces to go down too. The problem is caused by the reset switch router's interfaces not going down, so remote interfaces do not go down.

Workaround: Physically remove the cable from the ports or enter the shutdown command.

• CSCdr40560
  

An ATM interface on a Catalyst 8540 MSR might get stuck in a going down state.

Symptom: In some instances, an ATM interface on a Catalyst 8540 MSR might get stuck in a going down state.

Workaround: None.

• CSCdr38540
  

High route processor utilization on shutdown/no shutdown with a large numbers of VCs.

Symptom: When entering the shutdown/no shutdown command on an ATM interface with a large number of VCs, the route processor utilization stays high for a long period of time. For example, for an 8K VC, the route processor stays high for approximately 720 seconds, and for 4K VCs, approximately 300 seconds.

Workaround: None.

• CSCdr34241
  

Sync does not update the hostname or prompt on the redundant route processor.

Symptom: The prompt on the secondary route processor does not reflect the hostname of the switch router after a sync.

Workaround: None.

Workaround: None.

• CSCdr32957
  

Enhanced two-port Gigabit Ethernet interface module ACL: Configuration allows MinAcl+AllOtherRegions > TotalTcam.

Symptom: When configuring region sizes you are not considering the ACL region size when checking for the total size. Configuration allows regions sizes exceeding total Tcam size. No error message is printed at the time of configuration but upon next boot you get the following error messages:

ACL cannot be enabled on GigabitEthernet0/0/0 - insufficient TCAMAvailable: 24 
Configured for ACL: 2048 Use sdm access-list command to reconfig

Workaround: None.

• CSCdr30765
  

The ip cef command does not re-enable the CEF switching on the Catalyst 8540 when it was previously disabled due to lack of memory.

Symptom: The ip cef command does not re-enable the CEF switching on the Catalyst 8540 when it was previously disabled due to lack of memory. The Catalyst 8540 requires CEF switching but this can become disabled if insufficient memory is available. When insufficient memory is available, the following message appears:

"%FIB-2-FIBDOWN: CEF has been disabled due to a low memory condition.
 

Workaround: None.

• CSCdr29169
  

Corrupt block prevents Catalyst 8540 CSR from booting.

Symptom: After upgrading from Cisco IOS Release 12.0(5)W5(13) to Cisco IOS Release 12.0(5)W5(13b) code, CSR no longer boots. Restoring the older code corrects the problem. The crash occurs after the file is read. Removing the configuration text file from the TFTP server prevents the router from crashing. If the router is booted from the nvram configuration and the command copy tftp running then is issued, the router will crash. copy startup running does not crash the system.

Workaround: None.

• CSCdr25535
  

An ima_failure_trap might not be generated when an IMA group gets deleted and the group state change might not be sensed by the switch processor.

Symptom: An ima_failure_trap might not be generated when an IMA group gets deleted and the group state change might not be sensed by the switch processor.

Workaround: None.

• CSCdp55616
  

After changing the port speed from 10 to 100, the change does not get updated until the shutdown and no shutdown commands are issued.

Symptom: When you change the port speed from 10 to 100 on a Catalyst 8540 CSR running 12.0(5)W5(13), issue the shutdown and no shutdown commands for the new setting to take effect.

Workaround: None.

• CSCdp54731
  

Catalyst 8540 CSR Fast Ethernet ports that are in a shutdown state have incrementing packet output.

Symptom: Fast Ethernet interfaces that are in shutdown mode have packet output and bytes incrementing in the show interface command.

Workaround: Issue the clear counters command.

• CSCdp39811
  

HSRP configuration not removed on the enhanced two-port Gigabit Ethernet interface module after a card removal.

Symptom: The root cause of this is that the HSRP specific structures are not properly updated when an interface goes down or when a card is removed.

Workaround: Remove HSRP from the configuration before removing the card.

• CSCdp30288
  

Received malformed TLV.

Symptom: The above message is sometimes received. This message is can be ignored.

Workaround: None.

• CSCdm60257
  

The secondary route processor will become the primary route processor after reload.

Symptom: When you reload a Catalyst 8540 MSR with a redundant route processor, the secondary route processor will become the primary route processor after the reload.

The uptime shown when you issue the show version command is the uptime of the boot image. This should be the uptime of the running IOS software.

Workaround: None.

• CSCdm41015
  

15:28:43: %LANE-3-LEC_CONTROL_MSG: Received bad control message on interface 
ATM11/0/0.14Cant find ARM bound VC, port = 102, vci=0
 

Symptom: The above messages may appear on the console. They are not reproducible. The message appears on subinterface ATM11/0/0.14 on the ATM router module port.

Workaround: None.

• CSCdm23149
  

Removing a few subinterfaces or many several times can result in a crash.

Symptom: Under extreme low memory conditions, if a switch is configured with lots of hierarchical tunnels and LANE components are configured on the cpu port of the switch (or ATM interface of a router), removing a few subinterfaces or many several times can result in a crash. This removal without first cleaning up LANE configuration results in the loss of 6400 bytes of memory.

Workaround: Delete LANE configuration on a subinterface before deleting the subinterface itself.

Restrictions

This section describes the following Catalyst 8540 restrictions:

• ACL Daughter Card Restrictions
  
  
• AppleTalk Restrictions
  
  
• VLAN Encapsulation Restrictions
  
  
• EtherChannel Restrictions
  
  
• Maximum Path Restriction for EIGRP or OSPF
  
  
• Port Snooping Restrictions
  
  
• 8-Port Gigabit Ethernet Restrictions (Catalyst 8540 CSR)
  
  
• Restrictions on the Online Insertion and Removal of Interface Modules
  
  
• FPGA Upgrade Restriction
  
  
• 1000BASE-ZX GBIC Restriction
  
  

ACL Daughter Card Restrictions

The following restrictions apply to the ACL daughter card supported on the Catalyst 8540:

• The 8-port Gigabit Ethernet interface does not support an ACL daughter card.
  
  
• UDP flooding is disabled on routers with an ACL daughter card.
  
  
• The following ACLs are not supported with the ACL daughter card:
  
  
  • ACL for GEC, FEC, or BVI
    
    
  • Dynamic ACL
    
    
  • Reflexive ACL
    
    
  • IPX extended ACL
    
    
  • ACL logging
    
    

AppleTalk Restrictions

We recommend that you evaluate the level of CPU utilization and performance in your switch router before turning on AppleTalk. Unlike IP and IPX, AppleTalk routing and processing in the Catalyst 8540 is accomplished by the switch processor, not the interface module. This means that routing AppleTalk packets consumes more processing time than routing other protocol packets. In a switch with a sustained high CPU utilization, turning on AppleTalk could result in longer convergence times for routing protocols like EIGRP. AppleTalk packet throughput is dependent on the amount of available CPU processing power.

VLAN Encapsulation Restrictions

The four adjacent ports (such as 0-3 or 4-7) on a 10/100 Fast Ethernet interface must all use the same VLAN encapsulation, that is, either 802.1Q and native, or ISL and native.

Enhanced ATM Router Module Restrictions

The Catalyst 8540 MSR enhancedATM router module does not support the following features:

Note   This section is applicable to the Catalyst 8540 MSR switch router only.

• Appletalk is not supported on the enhanced ATM router module
  
  
• The switch router needs a minimum of 256-MB DRAM
  
  
• Point-to-point subinterfaces. Only point-to-multipoint subinterfaces are supported
  
  
• Tag-edged router functionality
  
  
• Fast Simple Server Redundancy Protocol (SSRP)
  
  
• Bridging for multiplexing device encapsulation
  
  
• Protocol Independent Multicast (PIM) IP multipoint signaling
  
  
• PIM nonbroadcast multiaccess (NBMA)
  
  
• PIM over ATM multipoint signaling
  
  
• Translation from IP quality of service (QoS) to ATM QoS Resource Reservation Protocol (RSVP) to ATM SVC
  
  
• PVC management using ILMI
  
  
• IP Multicast over RFC 1483 SVCs
  
  
• Layer 2 ACLs
  
  
• Half-bridge devices
  
  

EtherChannel Restrictions

When assigning Ethernet interfaces to an EtherChannel, all interfaces must be either Fast Ethernet or Gigabit Ethernet. You cannot mix Fast Ethernet and Gigabit Ethernet interfaces within a single EtherChannel.

Maximum Path Restriction for EIGRP or OSPF

Catalyst 8500 interface modules support a maximum of two paths. To improve EIGRP or OSPF convergence, set the maximum-paths for the router to two, using the following command:

8500(config)# router eigrp 109

8500(config-router)# maximum-paths 2

Port Snooping Restrictions

• The snooping source port and destination port cannot be the same port.
  
  
• You can only snoop with one source port and one destination port.
  
  
• Snooping configuration information is not saved in NVRAM.
  
  
• You cannot snoop a port that is part of a bridge group.
  
  

8-Port Gigabit Ethernet Restrictions (Catalyst 8540 CSR)

The 8-port Gigabit Ethernet interface module is supported on the Catalyst 8540 CSR only. This section describes limitations of the 8-port Gigabit Ethernet interface module.

Ports Per Bridge Group Restrictions

The 8-port Gigabit Ethernet interface module installed in a Catalyst 8540 CSR can support a maximum of 128 ports per bridge group.

Port Channel Restrictions

If your Catalyst 8540 CSR has an 8-port Gigabit Ethernet interface module, you cannot create a port channel that has some members on that module and some on other modules. All port channel members must reside on the same Gigabit Ethernet interface module.

Also, if your switch router has an 8-port Gigabit Ethernet interface module, port channel IDs 57 to 64 are reserved, and cannot be assigned to other external interfaces. If you assign a port channel ID number greater than 56, the system will respond with the following message:

Port channel with ID > 56 cannot be created.
 

If you have already assigned port channel IDs 57 to 64, you must reassign them before installing an 8-port Gigabit Ethernet interface module.

If your switch router does not have an 8-port Gigabit Ethernet interface module, you can assign port channel ID numbers up to 64.

Restrictions on the Online Insertion and Removal of Interface Modules

The following restrictions apply to the online insertion and removal (OIR), also known as hot swapping, of interface modules on the Catalyst 8540:

• Wait at least one minute after removing an interface module before inserting a new one.
  
  
• Do not remove more than one interface module at a time while the device is operational.
  
  
• OIR of the 8-port Gigabit Ethernet interface module is supported in Cisco IOS Release 12.0(5)W5.13 and later releases.
  
  

FPGA Upgrade Restriction

On an 8540, the reprogram command for upgrading the FPGA on the switch processor requires power cycling the box after completing the FPGA download.

1000BASE-ZX GBIC Restriction

The Catalyst 8540 switch routers support extra long haul (1000BASE-ZX) GBICs. It supports a maximum of 12 1000BASE-ZX GBICs per system to comply with FCC Class A emissions (CFR 47 Part 15), or 8 1000BASE-ZX GBICs per system to comply with EN55022 Class B emissions (CISPR22 Class B).

Route Processor and Switch Module Redundancy

The Catalyst 8540 supports the use of redundant route processors and switch modules. The second route processor would be installed in slot 8, and an additional switch module would be installed in slot 6.

Route Processor

There are some precautions that need to be taken before removing a route processor module from a chassis that is powered-up. If a route processor module that is currently running IOS is removed from the chassis in a skewed manner such that the left side of the processor comes out before the right side does, the traffic flowing through the device might stop flowing.

To avoid this, make sure the route processor module that is being removed is currently at the ROM monitor prompt; it is then safe to remove it from the chassis. One way to get the system into ROM monitor from IOS is to enter the reload command. This will work if the system is not configured to auto-boot. If the system is configured to auto-boot, it starts booting IOS again.

Since you need to ensure that a route processor is in ROM monitor before removing it, the redundancy prepare-for-cpu-removal command has been added to take the system to the ROM monitor prompt. Execute this command on the route processor being removed before removing it. Once this command is issued, the route processor will go to the ROM monitor prompt and stay there even if the system is configured to auto-boot. At this point it is safe to remove the route processor from the system.

Switch Modules

If a Catalyst 8540 has three switch modules, then by default the switch modules in slots 5 and 7 come up as active, and the one in slot 6 comes up as the standby. If you wish to change this default, there is a command that lets you select the "preferred" switch module slots. This command is a privileged exec level command with the following format:

redundancy preferred-switch-card-slot slot#1 slot#2

Two unique preferred slots must be specified. The range of the slot value is 5 to 7. If one of the preferred slots is not a currently active switch module, you are informed of this and asked if the system should change the active switch modules to the preferred switch modules. If such a switch-over occurs, all the active connections in the system will be reinitialized. If you wish to continue, then the preferred switch modules become active, and the other switch module becomes the standby. This configuration will remain in effect until either one of the active switch modules is removed.

The preferred switch module configuration is preserved across route processor switch-overs. However, the preferred switch modules setting will be lost if the system is power-cycled or if both route processors are reloaded to the ROM monitor.

Autonegotiation (Catalyst 8540 CSR)

The autonegotiation feature for speed and duplex on 10/100BASE-T Ethernet ports defaults to "on." This means that for each port, the Catalyst 8500 CSR automatically detects the port speed (10 Mbps or 100 Mbps) and duplex of the peer port, if that port also autonegotiates.

To override autonegotiation and set a port to 10 Mbps operation, issue the following command:

(config-if)# speed 10

 

To set a port to 100 Mbps operation, issue the following command:

(config-if)# speed 100

 

To set the duplex value for a port to full-duplex, issue the following command:

(config-if)# duplex full

 

To set the duplex value for a port to half-duplex, issue the following command:

(config-if)# duplex half

Caution   If you connect a Catalyst 8540 CSR switch router running Cisco IOS Release 12.0(5)W5(13) software to a router or switch running in forced full-duplex mode, you might encounter symptoms such as high collision rate or reduced throughput, as the Catalyst 8540 CSR unsuccessfully tries to autonegotiate with the other device. When autonegotiation fails, the Catalyst 8540 defaults to half-duplex operation, which causes a mismatch between it and the other device. Possible workarounds include forcing the Catalyst 8540 CSR to operate in full-duplex mode or removing the full-duplex command from the other device.

Interoperability

You can use Catalyst 8540 CSR interface modules in a Catalyst 8540 MSR chassis with an MSR route processor and switch modules. Use only CSR (Ethernet) interface modules, and load the CSR software image on the MSR.

Incompatibility

When you connect a Catalyst 8540 CSR to a Catalyst 5000 100BASE-FX MM Ethernet interface module using ISL, ensure that the hardware version on the Catalyst 5000 interface module is 1.3 or higher. You might experience connectivity problems between the Catalyst 8540 CSR and the Catalyst 5000 if the hardware version on the Catalyst 5000 Ethernet interface module is lower than 1.3.

Y2K Compliance

The Catalyst 8540 MSR and 8540 CSR systems have been certified as Y2K Compliant. For more information, see the following URL: http://www.cisco.com/warp/public/752/2000/.

Related Documentation

The following documents provide information related to Catalyst 8540 switch routers.

• Catalyst 8540 Interactive Quick Star t
  
  
• Quick Reference Catalyst 8540 Hardware Information
  
  
• Hardware and Software Compatibility Matrix
  
  
• Catalyst 8540 Chassis Installation Guide
  
  
• ATM and Layer 3 Module Installation Guide
  
  
• Guide to ATM Technology
  
  
• ATM and Layer 3 Switch Router Quick Software Configuration Guide
  
  
• ATM Switch Router Software Configuration Guide
  
  
• ATM and Layer 3 Switch Router Command Reference
  
  
• Layer 3 Switching Software Feature and Configuration Guide
  
  

Obtaining Documentation

The following sections provide sources for obtaining documentation from Cisco Systems.

World Wide Web

You can access the most current Cisco documentation on the World Wide Web at the following sites:

• http://www.cisco.com
  
• http://www-china.cisco.com
  
• http://www-europe.cisco.com
  

Documentation CD-ROM

Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM is updated monthly and may be more current than printed documentation. The CD-ROM package is available as a single unit or as an annual subscription.

Ordering Documentation

Cisco documentation is available in the following ways:

• Registered Cisco Direct Customers can order Cisco Product documentation from the Networking Products MarketPlace:
  
  

http://www.cisco.com/public/ordsum.html

• Registered Cisco.com users can order the Documentation CD-ROM through the online Subscription Store:
  
  

http://www.cisco.com/go/subscription

• Nonregistered CCO users can order documentation through a local account representative by calling Cisco corporate headquarters (California, USA) at 408 526-7208 or, in North America, by calling 800 553-NETS(6387).
  
  

Documentation Feedback

If you are reading Cisco product documentation on the World Wide Web, you can submit technical comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco.

You can e-mail your comments to bug-doc@cisco.com.

To submit your comments by mail, for your convenience many documents contain a response card behind the front cover. Otherwise, you can mail your comments to the following address:

Cisco Systems, Inc.
Document Resource Connection
170 West Tasman Drive
San Jose, CA 95134-9883

We appreciate your comments.

Obtaining Technical Assistance

Cisco provides Cisco.com as a starting point for all technical assistance. Customers and partners can obtain documentation, troubleshooting tips, and sample configurations from online tools. For Cisco.com registered users, additional troubleshooting tools are available from the TAC website.

Cisco.com

Cisco.com is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information and resources at anytime, from anywhere in the world. This highly integrated Internet application is a powerful, easy-to-use tool for doing business with Cisco.

Cisco.com provides a broad range of features and services to help customers and partners streamline business processes and improve productivity. Through Cisco.com, you can find information about Cisco and our networking solutions, services, and programs. In addition, you can resolve technical issues with online technical support, download and test software packages, and order Cisco learning materials and merchandise. Valuable online skill assessment, training, and certification programs are also available.

Customers and partners can self-register on Cisco.com to obtain additional personalized information and services. Registered users can order products, check on the status of an order, access technical support, and view benefits specific to their relationships with Cisco.

To access Cisco.com, go to the following website:

http://www.cisco.com

Technical Assistance Center

The Cisco TAC website is available to all customers who need technical assistance with a Cisco product or technology that is under warranty or covered by a maintenance contract.

Contacting TAC by Using the Cisco TAC Website

If you have a priority level 3 (P3) or priority level 4 (P4) problem, contact TAC by going to the TAC website:

http://www.cisco.com/tac

P3 and P4 level problems are defined as follows:

• P3—Your network performance is degraded. Network functionality is noticeably impaired, but most business operations continue.
  
  
• P4—You need information or assistance on Cisco product capabilities, product installation, or basic product configuration.
  
  

In each of the above cases, use the Cisco TAC website to quickly find answers to your questions.

To register for Cisco.com, go to the following website:

http://www.cisco.com/register/

If you cannot resolve your technical issue by using the TAC online resources, Cisco.com registered users can open a case online by using the TAC Case Open tool at the following website:

http://www.cisco.com/tac/caseopen

Contacting TAC by Telephone

If you have a priority level 1(P1) or priority level 2 (P2) problem, contact TAC by telephone and immediately open a case. To obtain a directory of toll-free numbers for your country, go to the following website:

http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml

P1 and P2 level problems are defined as follows:

• P1—Your production network is down, causing a critical impact to business operations if service is not restored quickly. No workaround is available.
  
  
• P2—Your production network is severely degraded, affecting significant aspects of your business operations. No workaround is available.
  
  

.