Fujitsu m10sparc m10 systems product notes for xcp

This preview shows page 78 - 81 out of 120 pages.

Fujitsu M10/SPARC M10 Systems Product Notes for XCP Version 2080 • November 201368
Background image
Table 3-7Problems resolved in versions prior to XCP 2050(continued)RTI No.SPARCM10-1SPARCM10-4SPARCM10-4SDescriptionWorkaroundRTIF2-130415-001xxIn SPARC M10-4/M10-4S, if thefirmware version is XCP 2031 orXCP 2032, the initial value ofthe following OpenBoot PROMenvironment variable differsfrom the default.Even if the setting is changed byusing the setpparparam(8)command of the XSCF shell orthe setenv command from theOpenBoot PROM prompt, itwill return to the original value.auto-boot? falsediag-switch? truefcode-debug? truelocal-mac-address? falseThere is no effective workaround.Make a firmware update to XCP2041 or a later version, and thenset the value of the OpenBootPROM environment variableagain.RTIF2-130416-001xxxIf the PCI device in the I/Odomain is deleted (ldm rm-io)or a PCI device is added (ldmadd-io), hypervisor abort mayoccur when the I/O domainstarts./…/…To delete the PCI devicein the I/O domain, delete alldevices under the same routecomplex as that of the PCIdevice to be deleted (whichhave the same xxxx of/[email protected]) and then add thenecessary devices again.Alternatively, do not assignmultiple devices under thesame route complex to a singleI/O domain.RTIF2-130417-001xIf the XSCF mounted in thecrossbar box panics, it may beimpossible to performcommunication between themaster XSCF and non-masterXSCF.There is no effective workaround.[How to restore]If the event occurs, wait for 15minutes or longer, and then userebootxscf -s to reset the masterXSCF.RTIF2-130507-001xxxThere is a case where a RAIDvolume cannot be recognizedafter a power failure occurredwhile using the hardware RAIDfunction.Please run the activate-volumecommand at ok prompt toactivate a hardware RAIDvolume.For the detailed procedure, see"12.2.8 Re-enabling hardwareRAID volume" in theFujitsuM10/SPARC M10 SystemsSystem Operation and AdministrationGuide.Chapter 3Information on Software69
Background image
Table 3-7Problems resolved in versions prior to XCP 2050(continued)RTI No.SPARCM10-1SPARCM10-4SPARCM10-4SDescriptionWorkaroundRTIF2-130515-001xxxWhile the system is operating,the following events may occur:1. The prtpicl command nolonger responds.2. Display data (such as theXCP version) of prtpicl -vand prtdiag -v is not outputas expected.3. For /var/adm/messages, thewarning message, "PICLsnmpplugin: cannot fetchobject value", is output.4. XSCF CMDD processshutdown occurs and anXSCF is reset repeatedly,such that it becomesunusable. At this time,system operation can becontinued.There is no effective workaround.[How to restore]If event 1. occurs, recover withthe following procedure.1. End the prtdiag(1M)command with [Ctrl-C].2. Wait for about 30 minutes,and allow an SNMP timeoutto occur in the XSCF.3. In the control domain,execute the svcadm(1M)command to restart the piclservice.
Background image
Image of page 81

You've reached the end of your free preview.

Want to read all 120 pages?

  • Fall '19
  • Fujitsu, Solaris, Sun Microsystems

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture