Cisco Gigabit Ethernet Switch Module for HP p-Class BladeSystem Release Notes, Cisco IOS Release 12.2(25)SED

12
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.
• CSCeg09032
Open Shortest Path First (OSPF) routes might not appear in the routing table after a topology change if
incremental SPF (iSPF) is enabled.
The workaround is to disable iSPF.
• 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.
• CSCsb79318
If the re-authentication timer and re-authentication action is downloaded from the RADIUS server using the
Session-Timeout and Termination-Action RADIUS attributes, the switch performs the termination action even
when the port is not configured with the dot1x timeout reauth server global configuration
command and uses the Termination-Action downloaded from a RADIUS server as part of IEEE 802.1x
authorization.
The workaround is to remove the Termination-Action attribute from the IEEE 802.1x policy on the RADIUS
server if dot1x timeout reauth server is not configured on the port.
• CSCsb82422
The switch does not forward an IEEE802.1x request that has null credentials.
There is no workaround.
• CSCsb82459
When a supplicant is IEEE 802.1x-capable and also performs DHCP, the switch might send an interim
update before DHCP is complete but after an EAP-Success message is sent. When this happens, the interim
update might be inaccurate.
There is no workaround.
• CSCsb85552
Enabling link state groups on downstream interfaces before an upstream interface is configured causes
downstream ports to go down.
The workaround is to configure the upstream interfaces into the link state group first. Then configure the
downstream interfaces. The downstream interfaces should recover and be allowed to go link up by the link
state tracking process.
• 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.