User guide

Browser, OS, and Java plug-in support16
HA switch reboot
failure
When a switch reboot or a failover occurs before POST is complete, the HA
resynchronization is disrupted. HA will not resynchronize until POST
completes.
CAUTION: Allow POST to complete before performing a switch reboot or
failover, to avoid disruptive failover.
Invalid gateway IP
address error message
The user will see the following message on the console during startup when
the Ethernet IP and gateway IP addresses are set to the defaults:
SIOCADDRT: Invalid argument
.....
ip.c:311:Invalid gateway IP address 0.0.0.0
This is a display issue only and does not affect the functionality of the
switch.
Logging,
syslog.conf In Fabric OS v4.x, the "kern" facility for syslog is no longer supported. You
must update all
syslog.conf files to support “local7” facilities. There is a
new syslogdFacility command to set the facility level that will be
used.
Logging, Solaris
syslogd local7 users
When using the new syslogdFacility command to set the local7 level, if an
even-numbered facility level is selected (for example, 0, 2, 4 or 6), all
switch Critical system messages will appear in the
odd -numbered .emerg
facility level file on the target Solaris systems: for example,
local6.emerg
will appear in
local7.emerg if syslogd facility level 6 is selected.
This behavior is not observed when selecting an odd-numbered facility
level initially on the switch. The problem also does not occur on Linux
server systems and is currently under investigation with Sun. delete The
immediate workaround is to select an odd-numbered syslogd facility level
when using the syslogdFacility command.
Table 4 Fabric OS area information (continued)
Fabric OS Area Description