Cisco Cisco Gigabit Ethernet Switch Module (CGESM) for HP 發佈版本通知

下载
页码 22
 
14
Cisco Gigabit Ethernet Switch Module for HP BladeSystem p-Class Release Notes, Cisco IOS Release 12.2(25)SEE1 and later
459516-002
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.
CSCsd49367
When a switch is running DHCP option 82 and is connected to several other switches by Gigastack 
GBICS, a PC connecting to that switch might fail to obtain an IP address. This connection attempt 
can fail several times. Eventually, the PC might connect to the switch. 
This is an intermittent problem. There is no workaround. 
CSCsd78044
When IGMP snooping is enabled and an EtherChannel member interface goes down, the switch 
might stop forwarding multicast traffic on the EtherChannel. This problem occurs when the 
EtherChannel interface is a member of a multicast group that is not directly connected (that is, the 
multicast group that does not have the C flag set in the show ip mroute privileged EXEC command 
output).
The workaround is to either disable IGMP snooping, or to use the clear ip mroute user EXEC 
command to refresh all the routes.