Cisco Gigabit Ethernet Switch Module for HP BladeSystem p-Class Release Notes, Cisco IOS Release 12.2(35)SE and later

14
Cisco Gigabit Ethernet Switch Module for HP BladeSystem p-Class Release Notes, Cisco IOS Release 12.2(35)SE and later
383623-007
Open Caveats
If the service config command does not find the configuration files, these error messages appear:
%Error opening tftp://255.255.255.255/network-confg (Timed out)
%Error opening tftp://255.255.255.255/cisconet.cfg (Timed out)
%Error opening tftp://255.255.255.255/router-confg (Timed out)
%Error opening tftp://255.255.255.255/ciscortr.cfg (Timed out)
These system messages also appear:
00:01:40: %SYS-4-CONFIG_RESOLVE_FAILURE: System config parse from
(tftp://255.255.255.255/network-confg) failed
00:01:40: %SYS-4-CONFIG_RESOLVE_FAILURE: System config parse from
(tftp://255.255.255.255/cisconet.cfg) failed
00:01:40: %SYS-4-CONFIG_RESOLVE_FAILURE: System config parse from
(tftp://255.255.255.255/switch-confg) failed
00:01:40: %SYS-4-CONFIG_RESOLVE_FAILURE: System config parse from
(tftp://255.255.255.255/ciscortr.cfg) failed
These messages are for information only. There is no problem with the switch operation.
Because the switch automatically configures the service config global configuration command, it is
in the switch startup-config file when you save the running-config file. This command runs every
time the switch is restarted, even if a config.text configuration file is in the switch flash memory.
The workaround is to prevent these messages from being generated. To do this, enter the switch
configuration mode, and issue the no service config command. Save the configuration to flash by
using the copy running-config to startup-config command. The preceding error and system
messages no longer appear and do not appear when the switch is restarted.
CSCeg67844
When using SNMP, the CGESM switch returns an incorrect value of 65534 for the
ciscoFlashPartitionFileCount MIB; the switch actually contains 1367 files.
There is no workaround.
CSCsb85001
If traffic is passing through VMPS ports and you perform a shut operation, a dynamic VLAN is not
assigned and a VLAN with a null ID appears.
The workaround is to clear the MAC address table. This forces the VMPS server to correctly
reassign the VLAN.
CSCsc26726
Sometimes interfaces Gi0/23 & Gi0/24 will not link up with another switch when the interface speed
is set to an explicit value instead of autonegotiated. This does not happen when a copper SFP is used
with interfaces Gi0/17 - Gi0/20.
The workaround is to autonegotiate the speed with the other device, or to use a different cable type.
Use a straight through cable for switch to switch connection, or a cross-over cable for switch to any
non switch device connection. If the other device is capable of auto MDIX even with speed not set
to auto, then use that. When an improper cable is used only one side of the connection needs to use
auto MDIX to achieve a link.