Cisco 3520 Guía de instalación descargar pdf (Pagina 18)

Release Notes for the Catalyst 3750 Switch Cisco IOS Release 12.1(14)EA1

OL-4215-01

Limitations and Restrictions

• The egress SPAN data rate might degrade when fallback bridging or multicast routing is enabled.

The amount of degradation depends on the processor loading. Typically, the switch can egress SPAN

up to 40,000 packets per second (64-byte packets). As long as the total traffic being monitored is

below this limit, there is no degradation. However, if the traffic being monitored exceeds the limit,

only a portion of the source stream is spanned. When this occurs, the following console message

appears: Decreased egress SPAN rate. In all cases, normal traffic is not affected; the degradation

limits only how much of the original source stream can be egress spanned. If fallback bridging and

multicast routing are disabled, egress SPAN is not degraded. There is no workaround. If possible,

disable fallback bridging and multicast routing. If possible, use ingress SPAN to observe the same

traffic. (CSCeb01216)

• A Catalyst 3750 switch might not be able to pass Vine (Advanced Research Projects Agency) ARPA

frames over bridge groups. The workaround is to use Subnetwork Access Protocol (SNAP) frames.

(CSCeb10032)

• If a 10/100BASE-T port configured for forced 100 mbps full-duplex mode is connected to a link

partner that is auto-negotiating, the link partner comes up in 100 mbps full-duplex mode. However,

if the same link partner is connected to a Gigabit port configured for forced 100 mbps full-duplex

mode, the link comes up in 100 mbps half-duplex mode. The reason for this inconsistent behavior

is that the 10/100 port auto-negotiates even if both speed and duplex mode are fixed, whereas the

Gigabit port does not. This is a hardware limitation. No workaround is necessary. (CSCeb14068)

• On Catalyst 3750 switches running Cisco IOS 12.1(14)EA1 software, some IGMP report and query

packets with IP options might not be ingress-spanned. Packets that are susceptible to this problem

are IGMP packets containing 4 bytes of IP options (IP header length of 24). An example of such

packets would be IGMP reports and queries having the router alert IP option. Ingress-spanning of

such packets is not accurate and can vary with traffic rate. Typically, very few or none of these

packets are spanned. There is no workaround. (CSCeb23352)

• If the number of VLANs times the number of trunk ports exceeds the recommended limit of 13,000,

the switch can fail. The workaround is to reduce the number of VLANs or trunks. (CSCeb31087)

Cluster Limitations and Restrictions

These limitations apply to cluster configuration:

• When there is a transition from the cluster active command switch to the standby command switch,

Catalyst 1900, Catalyst 2820, and Catalyst 2900 4-MB switches that are cluster members might lose

their cluster configuration. You must manually add these switches back to the cluster.

(CSCds32517, CSCds44529, CSCds55711, CSCds55787, CSCdt70872)

• When a Catalyst 2900 XL or Catalyst 3500 XL cluster command switch is connected to a

Catalyst 3550 or to a Catalyst 3750 switch, the command switch does not find any cluster candidates

beyond the Catalyst 3550 or the Catalyst 3750 switch if it is not a member of the cluster. You must

add the Catalyst 3550 or the Catalyst 3750 switch to the cluster. You can then see any cluster

candidates connected to it. (CSCdt09918)

• If both the active command-switch and the standby command switch fail at the same time, the cluster

is not automatically recreated. Even if there is a third passive command switch, it might not recreate

all cluster members because it might not have all the latest cluster configuration information. You

must manually recreate the cluster if both the active and standby command switches simultaneously

fail. (CSCdt43501)

1 2 ... 13 14 15 16 17 18 19 20 21 22 23 ... 33 34

Comentarios a estos manuales

Sin comentarios

Cisco 3520 Guía de instalación Pagina 18

Comentarios a estos manuales