Chapter 6 The System Chassis’s Integrated Switch 6-5
The ports NETP0, NETP1, NETP4, NETP5, and SNP8 through SNP15 are on one
switch chip. The ports NETP2, NETP3, NETP6, NETP7 and SNP0 through SNP7
are on the other.
■Multiple Spanning TreeProtocol: the spanning tree mst commands are not
available in the current release of the switch firmware.
■The switch’s DHCP client identifier is set by the System Controller.This means
that, if you set it using the switch’s command-line interface, web GUI, or by using
the SNMP interface to the switch, the setting you specify will be overwritten by
the System Controller next time the switch boots. The command to change the
DHCP client identifier will be removed fromthe next release of the switch
firmware.
■4831855: Date set incorrectly on the switch.
If you set the date on the System Controller (SC) to anything other than the first
of the month, then the datestamp on events logged by the switch afterwards will
oneday behind the current date on the System Controller. For example, if the date
according to the System Controller is WednesdayMarch 26, 2003, then the
datestampon switch event logs will have the datestamp become 3/25/3. The only
workaround for this is to wait until the first of the next month, and resetthe date
on the System Controller.
■4804197: AN983 internal loopback test reports false failure
Thereis a remote possibility that an inaccurate failure report will be generated by
the AN983 internal loopback test performed during a switch reset (including
following execution of the reload command). If the NETMGT port is accessible
from the network, then you can ignore the failure report.The failure will persist
over several resetsuntil the SSC undergoes a hard reset (in other words, until you
power cycle the SSC. If you close down all web, SNMP,and telnet connections to
the switch before you perform the reset, you will not see this problem.
■4799549: Broadcast ping from ablade on the management network will not
receive a response from any external hosts
If you issue a broadcast ping onto the management network from a server blade,
you will not receive any responses from host devices external to the switch (in
other words, you will only receive a responsefrom the switch’s NETMGT port
and from other blades inside the chassis that are also on the management
network). This is a known problem and it will be fixed in the next release.
However,you can ping known hosts individually on the management network.
And if you log into a known host on the management network and issue the
broadcast ping from there, you will receivea response from all the host devices
on the management network (including all the host devices inside the chassis that
are on the management network). Firmware that fixes this problemis now
available from http://sunsolve.sun.com (patch number: 114783-xx).
■The switch’s DHCP client identifier is set by the System Controller.This means
that, if you set it using the switch’s command-line interface, web GUI, or by using
the SNMP interface to the switch, the setting you specify will be overwritten by