Sun Microsystems B100X, B1600, AND B100S, B200X BLADE manual System Chassis’s Integrated Switch

Page 53

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 Tree Protocol: 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 from the 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 one day behind the current date on the System Controller. For example, if the date according to the System Controller is Wednesday March 26, 2003, then the datestamp on 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 reset the date on the System Controller.

4804197: AN983 internal loopback test reports false failure

There is 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 resets until 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 a blade 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 response from 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 receive a 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 problem is 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

Chapter 6 The System Chassis’s Integrated Switch 6-5

Image 53
Contents Page Page Contents Sparc Solaris Contents Page Documentation and Miscellaneous Information Before Installing Solaris x86 Onto a Blade Upgrading the Bios on a B200x Server BladeUsing N1 Provisioning Software Miscellaneous InformationDownloading New Firmware for Chassis Components Using the Sun Fire B10n Content Load Balancing BladeDocumentation in this Release Documentation Errata Page Linux Installing Linux Onto a B100x or B200x Blade To Upgrade the Bios Upgrading the Bios on B200x Server BladesBlade prompt returns when the update is complete Issues Affecting the B200x Server Blade Only B100x and B200x Linux Server Blade IssuesIssues Affecting the B100x Server Blade Only Solaris Preparing to Install Solaris x86 Onto a BladeSolaris x86 Drivers and Documentation Overview of the Solaris x86 Installation Process # mkdir -m 755 /var/tmp/blades Proceed to Creating a Network Install Server on Creating a Network Install Server # ./modifyinstallserver -d installdirpath Page Need Support for Soft Poweroff in Solaris Workaround Workaround Page Consconfig complains on servers with no frame buffer Error Messages That Can be Safely IgnoredPage Solaris x86 Acpi Resource Conflicts Unnecessarily Reported Other Issues1The Network Interfaces on a B200x Blade Base MAC + 1, snet1 Solaris x86 Page Sparc Solaris B100s Sparc Solaris Server Blade Issues Installing Sparc Solaris Onto a B100s Server Blade# share -F nfs /cdrom/solaris8hw1202suppcd Installation of SUNWidecr failed System Controller Upgrading the System Controller SC Firmware Set up a new user name and password for yourself System Controller Firmware System Controller Software IssuesScreset -x -y sn Scremovefru -y psn scpoweron psn System Chassis’s Integrated Switch Switch Firmware Issues Console#configure Consoleconfig#vlan database Consoleconfig#no vlan vlanid System Chassis’s Integrated Switch Page Console#configure Page Consoleconfig#no bridge-ext gvrp Aggregated Links Switch-to-switch Tagged Vlan Trunk Connections Setting up a Tagged Vlan Trunk With Cisco Switches