Filter
Top Products
45
Release Notes for 07.8.04 Software Fixes
60916 Traffic is not evenly balanced on the members of a
trunk after you enter the ip net-aggregate
command and configure multislot switch trunks.
IP Routing 07.8.02
60979 If BGP4 is configured and you enter the remove
private-as command on a neighboring device so
that the routing switch receives an update from a
private AS for which it is configured, the BGP
update is sent out with the AS numbers stripped
out.
If the AS numbers are private only, the AS path
attribute will be empty. This causes the neighbor to
reset the BGP peering.
BGP4 07.8.02
61211 If you configure a Gigabit fiber port using the
gigabit auto rfn command, and the port is
physically connected and then disconnected to a
Cisco router, the port does not always come up.
System 07.8.02
61383 When an ACL is configured, the ip access-group
in ethernet <slot/port> command does not correctly
apply the ACL to only the specified port.
ACL 07.8.02
61434 When the STP boundary is changed dynamically,
the new value is not displayed in show superspan
command output.
The workaround is to remove the value by entering
the no stp-boundary <value> command before
configuring a new value.
Spanning Tree 07.8.02
61501 If a spanning tree is configured and a port is tagged
for the default VLAN, the spanning tree state on the
default VLAN is not updated. As a result, the
outbound traffic is forwarded on the blocked port
causing a loop.
Spanning Tree 07.8.02
62071 If OSPF is configured and there are multiple
neighbors on an interface, the OSPF routes are not
learned from the interface unless all the neighbors
are established.
OSPF 07.8.02
62367 If VSRP is configured, port indication on a change
in the port state incorrectly programs forwarding
information. As a result, port 1/1 does not send
outbound traffic.
VSRP 07.8.02
62826 If UDLD is configured, an incorrect error message
may be displayed:
Link-keepalive and trunk-threshold
cannot be enabled.
UDLD 07.8.02
62893 If the primary port of the trunk goes down due to a
port security violation, the other members of the
trunk are displayed incorrectly as “state: Down”.
Port Security 07.8.02
Bug ID Bug Description Protocol/
Feature
Version
Found
Version
Fixed