5-4 Sun Fire™ B1600 Chassis and B100s, B100x, and B200x Blade Product Notes • May 2004
5.3 System Controller Software Issues

5.3.1 System Controller Firmware 1.2

The following known problems apply to the currentrelease of the System Controller
firmware for this product:
4879114:System Controller sometimes resets or fails over if its netmask is invalid:
If you have an invalid netmask configuredfor the System Controller, you may see
thefollowing or a similar error message in response to ARP requests generated by
the System Controller:
where xxxxxxxx is the hexadecimal representation of an IP address.If you see an
error message like this, it will be followed by a reset of the System Controller(if
you are operating the chassis with a single System Controller) or a failover to the
standby System Controller (if you are operating a chassis containing a redundant
System Controller).
Toavoid this problem make sure you configure the System Controller with a
netmask that is valid for your network. If you are using DHCP to allocate IP
addresses, make sure your DHCP server is configuredto provide a netmask that
is valid for your network.
4885940: Poweron of Standby SSC fails due to spurious environmental errors: If
you run the removefru command followed by the poweron command on the
standby System Controller without physically removing the SSC module
containing the standby System Controller,you may see spurious environmental
errors being notified for the standby SC. These errors do not indicate any real
problem with the SC hardware and the problemcan be cleared by issuing a
poweron command for the standby SC. Alternatively,physically removing and
re-inserting that SC will also clear the problem.

5.3.2 System Controller Firmware 1.1

The following known problems applied to release 1.1 of the System Controller
firmware (they are fixedin release 1.2):
arptnew failed on xxxxxxxx