sun enterprise 10000 idn error messages · 2011. 2. 2. · sunenterprise 10000 sspattributions:...

Send comments about this

Sun Enterprise 10000 IDN ErrorMessages

Part No. 806-5231-10January 2001, Revision A

Sun Microsystems, Inc.901 San Antonio RoadPalo Alto,CA 94303-4900U.S.A. 650-960-1300

document to: [email protected]

Copyright 2001 Sun Microsystems, Inc., 901 San Antonio Road, Palo Alto, California 94303-4900 U.S.A. All rights reserved.

This product or document is protected by copyright and distributed under licenses restricting its use, copying, distribution, and decompilation.No part of this product or document may be reproduced in any form by any means without prior written authorization of Sun and its licensors,if any. Third-party software, including font technology, is copyrighted and licensed from Sun suppliers.

Parts of the product may be derived from Berkeley BSD systems, licensed from the University of California. UNIX is a registered trademark inthe U.S. and other countries, exclusively licensed through X/Open Company, Ltd.

Sun, Sun Microsystems, the Sun logo, AnswerBook2, docs.sun.com, Sun Enterprise, OpenBoot, and Solaris are trademarks, registeredtrademarks, or service marks of Sun Microsystems, Inc. in the U.S. and other countries. All SPARC trademarks are used under license and aretrademarks or registered trademarks of SPARC International, Inc. in the U.S. and other countries. Products bearing SPARC trademarks arebased upon an architecture developed by Sun Microsystems, Inc.

The OPEN LOOK and Sun™ Graphical User Interface was developed by Sun Microsystems, Inc. for its users and licensees. Sun acknowledgesthe pioneering efforts of Xerox in researching and developing the concept of visual or graphical user interfaces for the computer industry. Sunholds a non-exclusive license from Xerox to the Xerox Graphical User Interface, which license also covers Sun’s licensees who implement OPENLOOK GUIs and otherwise comply with Sun’s written license agreements.

Federal Acquisitions: Commercial Software—Government Users Subject to Standard License Terms and Conditions.

DOCUMENTATION IS PROVIDED “AS IS” AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES,INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT,ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID.

Copyright 2001 Sun Microsystems, Inc., 901 San Antonio Road, Palo Alto, Californie 94303 Etats-Unis. Tous droits réservés.

Ce produit ou document est distribué avec des licences qui en restreignent l’utilisation, la copie, la distribution, et la décompilation. Aucunepartie de ce produit ou document ne peut être reproduite sous aucune forme, par quelque moyen que ce soit, sans l’autorisation préalable etécrite de Sun et de ses bailleurs de licence, s’il y en a. Le logiciel détenu par des tiers, et qui comprend la technologie relative aux polices decaractères, est protégé par un copyright et licencié par des fournisseurs de Sun.

Des parties de ce produit pourront être dérivées des systèmes Berkeley BSD licenciés par l’Université de Californie. UNIX est une marquedéposée aux Etats-Unis et dans d’autres pays et licenciée exclusivement par X/Open Company, Ltd.

Sun, Sun Microsystems, le logo Sun, AnswerBook2, docs.sun.com, Sun Enterprise, OpenBoot, et Solaris sont des marques de fabrique ou desmarques déposées, ou marques de service, de Sun Microsystems, Inc. aux Etats-Unis et dans d’autres pays. Toutes les marques SPARC sontutilisées sous licence et sont des marques de fabrique ou des marques déposées de SPARC International, Inc. aux Etats-Unis et dans d’autrespays. Les produits portant les marques SPARC sont basés sur une architecture développée par Sun Microsystems, Inc.

L’interface d’utilisation graphique OPEN LOOK et Sun™ a été développée par Sun Microsystems, Inc. pour ses utilisateurs et licenciés. Sunreconnaît les efforts de pionniers de Xerox pour la recherche et le développement du concept des interfaces d’utilisation visuelle ou graphiquepour l’industrie de l’informatique. Sun détient une licence non exclusive de Xerox sur l’interface d’utilisation graphique Xerox, cette licencecouvrant également les licenciés de Sun qui mettent en place l’interface d’utilisation graphique OPEN LOOK et qui en outre se conforment auxlicences écrites de Sun.

LA DOCUMENTATION EST FOURNIE “EN L’ETAT” ET TOUTES AUTRES CONDITIONS, DECLARATIONS ET GARANTIES EXPRESSESOU TACITES SONT FORMELLEMENT EXCLUES, DANS LA MESURE AUTORISEE PAR LA LOI APPLICABLE, Y COMPRIS NOTAMMENTTOUTE GARANTIE IMPLICITE RELATIVE A LA QUALITE MARCHANDE, A L’APTITUDE A UNE UTILISATION PARTICULIERE OU AL’ABSENCE DE CONTREFAÇON.

PleaseRecycle

Sun Enterprise 10000 SSP Attributions:

This software is copyrighted by the Regents of the University of California, Sun Microsystems, Inc., and other parties. The following termsapply to all files associated with the software unless explicitly disclaimed in individual files.

The authors hereby grant permission to use, copy, modify, distribute, and license this software and its documentation for any purpose,provided that existing copyright notices are retained in all copies and that this notice is included verbatim inany distributions. No writtenagreement, license, or royalty fee is required for any of the authorized uses. Modifications to this software may be copyrighted by their authorsand need not follow the licensing terms described here, provided that the new terms are clearly indicated on the first page of each file wherethey apply.

IN NO EVENT SHALL THE AUTHORS OR DISTRIBUTORS BE LIABLE TO ANY PARTY FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL,OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OF THIS SOFTWARE, ITS DOCUMENTATION, OR ANY DERIVATIVESTHEREOF, EVEN IF THE AUTHORS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

THE AUTHORS AND DISTRIBUTORS SPECIFICALLY DISCLAIM ANY WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THEIMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT. THISSOFTWARE IS PROVIDED ON AN "AS IS" BASIS, AND THE AUTHORS AND DISTRIBUTORS HAVE NO OBLIGATION TO PROVIDEMAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS.

RESTRICTED RIGHTS: Use, duplication or disclosure by the government is subject to the restrictions as set forth in subparagraph (c) (1) (ii) ofthe Rights in Technical Data and Computer Software Clause as DFARS 252.227-7013 and FAR 52.227-19.

This is scotty, a simple tcl interpreter with some special commands to get information about TCP/IP networks. Copyright (c) 1993, 1994, 1995, J.Schoenwaelder, TU Braunschweig, Germany, Institute for Operating Systems and Computer Networks. Permission to use, copy, modify, anddistribute this software and its documentation for any purpose and without fee is hereby granted, provided that this copyright notice appearsin all copies. The University of Braunschweig makes no representations about the suitability of this software for any purpose. It is provided “asis" without express or implied warranty.

Contents

Preface ix

Before You Read This Book ix

How This Book Is Organized ix

Using UNIX Commands x

Typographic Conventions x

Shell Prompts xi

Related Documentation xi

Accessing Sun Documentation Online xi

Ordering Sun Documentation xii

Sun Welcomes Your Comments xii

1. IDN Errors Introduction 1

Searching the Tables in This Book 1

Online Searching 2

Special Typographical Conventions 2

IDN Error Messages on the Domain 2

2. IDN Error Messages, Notifications, and Panics on the Domain 5

Domain IDN Messages 5

v

vi Sun Enterprise 10000 IDN Error Messages • January 2001

Tables

TABLE 2-1 IDN Domain-Specific Error Numbers 5

TABLE 2-2 IDN Domain-Specific Messages, 100 through 142 7





vii

viii Sun Enterprise 10000 IDN Error Messages • January 2001

Preface

This book contains the InterDomain Network (IDN) error messages that occur onSun Enterprise™ 10000 domains.

Before You Read This BookThis book is intended for the Sun Enterprise 10000 server system administrator whohas a working knowledge of UNIX® systems, particularly those based on theSolaris™ operating environment. If you do not have such knowledge, first read theSolaris user and system administrator books in AnswerBook2™ format providedwith this system and consider UNIX system administration training.

How This Book Is OrganizedThis book contains the following chapters:

Chapter 1 introduces the IDN error messages.

Chapter 2 contains the IDN error messages that occur on the domain.

ix

Using UNIX CommandsThis document may not contain information on basic UNIX commands andprocedures such as shutting down the system, booting the system, and configuringdevices.

Refer to one or more of the following for this information:

■ AnswerBook2 online documentation for the Solaris software environment

■ Other software documentation that you received with your system

Typographic Conventions

Typeface orSymbol

Meaning Examples

AaBbCc123 The names of commands, files,and directories; on-screencomputer output

Edit your .login file.Use ls -a to list all files.% You have mail .

AaBbCc123 What you type, whencontrasted with on-screencomputer output

% suPassword:

AaBbCc123 Book titles, new words or terms,words to be emphasized

Read Chapter 6 in the User’s Guide.These are called class options.You must be superuser to do this.

Command-line variable; replacewith a real name or value

To delete a file, type rm filename.

x Sun Enterprise 10000 IDN Error Messages • January 2001

Shell Prompts

Related Documentation

Accessing Sun Documentation OnlineThe docs.sun.com SM web site enables you to access Sun technical documentationon the Web. You can browse the docs.sun.com archive or search for a specific booktitle or subject at:

http://docs.sun.com

Shell Prompt

C shell machine_name%

C shell superuser machine_name#

Bourne shell and Korn shell $

Bourne shell and Korn shell superuser #

Application Title Part Number

User Sun Enterprise 10000 IDN ConfigurationGuide

806-5230

Sun Enterprise 10000 IDN User Guide 806-4131

Preface xi

Ordering Sun DocumentationFatbrain.com, an Internet professional bookstore, stocks select productdocumentation from Sun Microsystems, Inc.

For a list of documents and how to order them, visit the Sun Documentation Centeron Fatbrain.com at:

http://www.fatbrain.com/documentation/sun

Sun Welcomes Your CommentsWe are interested in improving our documentation and welcome your commentsand suggestions. You can email your comments to us at:

[email protected]

Please include the part number (806-5231-10) of your document in the subject line ofyour email.

xii Sun Enterprise 10000 IDN Error Messages • January 2001

CHAPTER 1

IDN Errors Introduction

This chapter contains an introduction to the IDN error messages that occur on thedomain.

Note – If you do not find the error message in this book, refer to the error messagesin the Sun Enterprise 10000 InterDomain Networks User Guide in the SSP 3.4Answerbook collection.

Searching the Tables in This BookBefore you use the tables in this book, take time to read the following list of searchtips so that you can find a specific message.

■ Search on a specific string of text in the error message.■ Avoid using numeric values. They are treated as replaceable text in this book.■ Avoid using text that is replaceable. In this book, the following names are used to

represent replaceable text in the error messages: descriptive message,errno_description. device_name, target_path, mount_point, interface_name_instance,interface_name, and partition_name.

■ If you are reading this text in hard-copy form, the tables are presented in order bythe type of error or failure. The contents of the tables is sorted alphabetically indecending order.

1

Online SearchingYou can use the search engine provided in the AnswerBook2™ environment or thesearch engine in your browser to find a specific string of characters from an errormessage. Before you construct the search string, keep in mind that this appendixcontains special typographical conventions. In addition, you may need to search allof the tables individually. If you know the error type (that is, where the error wasencountered), use the hypertext links in “IDN Error Messages on the Domain” onpage 2 to start your search.

Special Typographical Conventions

The tables in this appendix contain special typographical conventions for the namesof words and values that change, depending on the type of error. When you searchfor an error message, keep in mind that these names appear as genericrepresentations in italic font. The following list contains the commonly usedrepresentations used in this appendix.

■ domain_ID for the value of the domain ID■ domain_name for the names of all domains■ domain_name_a, domain_name_b, domain_name_c for the names of the domains used

with the IDN commands■ platform_name for the name of the Sun Enterprise™ 10000 platform■ process_id for the value of the process ID (pid number)■ system_board_number for the number of a system board (that is, 1 through 15)■ number for numeric values

IDN Error Messages on the DomainThis book contains the IDN messages that occur on the domain from which the IDNcommand was executed. TABLE 2-1 contains the name, number, and description ofIDN errno numbers. This table describes some of the message conventions that areused in the message tables. TABLE 2-2 through TABLE 2-6 contain the commonInterDomain Network errors, notifications, and panics that can occur on the domain.These tables contain the text of the error, description of the possible cause of theerror, and suggested action. For notifications, the list contains the text of the noticeand a possible cause of the message.

Use one of the following links to start your search.

TABLE 2-1 on page 5, which contains the errno messages.

2 Sun Enterprise 10000 IDN Error Messages • January 2001

TABLE 2-2 on page 7, which contains messages 100 through 142.





Chapter 1 IDN Errors Introduction 3

CHAPTER 2

IDN Error Messages, Notifications,and Panics on the Domain

This chapter contains IDN error numbers that appear on the domain and IDN errormessages, notifications, and panics that occur on the domain

The destination of these messages depends entirely on the location of the individualerror or failure. For some errors, both locations must be used to diagnose the error orfailure.

Domain IDN MessagesIDN messages that occur on the domain are sent to the following locations:

■ netcon (1M) console window■ /var/adm/messages

■ $SSPLOGGER/domain_name/messages

The following table contains the IDN error numbers that are specific to the domain.

TABLE 2-1 IDN Domain-Specific Error Numbers

Message Number Description

IDNKERR_DRV_DISABLED 0x100 The IDN driver is disabled.

IDNKERR_DATA_LEN 0x101 The IDN region in the signature block (BBSRAM) ismisaligned between the IDN driver and the SSP (P0represents the length).

IDNKERR_INFO_FAILED 0x102 SSI_INFO command failed (only in engineering).

5

IDNKERR_INVALID_DOMAIN 0x103 An invalid domain ID was specified (P0 represents thedomain ID, and P1 represents the CPU ID).

IDNKERR_INVALID_FORCE 0x104 An invalid force option was passed (P0 represents the forceoption).

IDNKERR_INVALID_CMD 0x105 An invalid IDN command was requested (P0 representscommand).

IDNKERR_INVALID_WTIME 0x106 An invalid wait time was specified for the IDN operation (P0represents the wait time).

IDNKERR_SMR_CORRUPTED 0x107 SMR memory was found corrupted (P0 represents thedomain ID, against which the corruption was found).

IDNKERR_CPU_CONFIG 0x108 Domain ID is not configured properly for an IDN. Eachsystem board that hosts memory must have at least one CPU(P0 represents the domain ID).

IDNKERR_HW_ERROR 0x109 The domain was unable to properly program the hardwareto support an IDN connection to domain ID (P0 representsthe domain ID)

IDNKERR_SIGBINTR_LOCKED 0x10a The signature block interrupt lock on the host is currentlylocked.

IDNKERR_SIGBINTR_BUSY 0x10b The signature block interrupt handler thread is currentlyactive.

IDNKERR_SIGBINTR_NOTRDY 0x10c The signature block interrupt handler thread has not beeninitialized.

IDNKERR_CONFIG_FATAL 0x10d An error occurred during the exchange of configurationinformation with domain ID, specifically it was missinginformation (P0 represents the domain ID).

IDNKERR_CONFIG_MULTIPLE 0x10e Multiple conflicts were found between the configurationparameters exchanged during the connection establishment(P0 represents the domain ID).

IDNKERR_CONFIG_MTU 0x10f The MTU sizes of the domains do not match (P0 representsthe domain ID; P1 represents the expected value, and P2represents the actual value).

IDNKERR_CONFIG_BUF 0x110 The values of the idn_smr_bufsize variable conflictamong the domains (P0 represents the domain ID; P1presents the expected value, and P2 represents the actualvalue).

IDNKERR_CONFIG_SLAB 0x111 The values of the SMR slab sizes conflict among the domains(P0 represents the domain ID; P1 represents the expectedvalue, and P2 represents the actual value).

TABLE 2-1 IDN Domain-Specific Error Numbers (Continued)



The following table contains the errors, notices, and panics that are specific to thedomain.

IDNKERR_CONFIG_NWR 0x112 The values of the idn_nwr_size variables conflict amongthe domains (P0 represents the domain ID; P1 represents theexpected value, and P2 represents the actual value).

IDNKERR_CONFIG_NETS 0x113 The values of the idn_max_nets variables conflict betweendomains (P0 represents the domain ID; P1 represents theexpected value, and P2 represents the actual value).

IDNKERR_CONFIG_MBOX 0x114 The values of the idn_mbox_per_nets variables conflictbetween domains (P0 represents the domain ID; P1represents the expected value, and P2 represents the actualvalue).

IDNKERR_CONFIG_NMCADR 0x115 The number of MCADRs received does not match thenumber of MCADRs that the domain had reported to exist(P0 represents the domain ID; P1 represents the expectedvalue, and P2 represents the actual value).

IDNKERR_CONFIG_MCADR 0x116 Received an MCADR for a board that the remote domain didnot report to exist (P0 represents the domain ID; P1represents the expected value, and P2 represents the actualvalue).

IDNKERR_CONFIG_CKSUM 0x117 The values of the idn_checksum parameter is not consistentamong the domains (P0 represents the domain ID; P1represents the expected value, and P2 represents the actualvalue).

IDNKERR_CONFIG_SMR 0x118 The master domain SMR is too large for the slave domain(P0 represents the domain ID; P1 represents the expectedvalue, and P2 represents the actual value).

TABLE 2-2 IDN Domain-Specific Messages, 100 through 142

Error Description Recovery

WARNING: IDN: 100:sigblock area misaligned( bytes) != exp ( bytes)

This message indicates amismatch between the version ofthe sigblock data structure in theIDN driver and the region of thesignature block that is reserved forthe IDN.

Unlink the domains, then recreate theIDN.

WARNING:IDN:101: not inexpected OFFLINE statefor DDI_RESUME

The IDN driver is not in theexpected state for the DR driver toperform the DDI_RESUMEoperation.

Unlink the domain, then relink it.

TABLE 2-1 IDN Domain-Specific Error Numbers (Continued)


Chapter 2 IDN Error Messages, Notifications, and Panics on the Domain 7

NOTICE: IDN: 102 driverdisabled - check OBPenvironment (idn-smr-size)

The IDN driver was notinitialized.

Check the OpenBoot PROM (OBP)variable idn-smr-size to ensurethat it is set properly. Refer to the SunEnterprise 10000 IDN ConfigurationGuide for more information about thisvariable.

WARNING: IDN: 103:unable to referencesigblock area

Thesgnblk_poll_reference()routine failed to initialize. TheIDN driver may have been loadedtoo early in the boot sequence.

Reload the module after theoperating system boots.

WARNING: IDN: 104:cannot suspend whileactive (state = GSTATE)

The IDN driver cannot besuspended while it is in use.

Wait for the driver to complete thecurrent transmission, or unlink thedomain from the IDN before youinitiate a DR operation.

WARNING: IDN: 105:driver parameter( parameter) specified( number) out of range[ low_value - high_value]

The value for the specifiedparameter is outside of the rangeof values that can be used for theIDN.

Reset the parameter with a value thatis within the allowed range.

WARNING: IDN: 106:idn_nwr_size ( Mbytes) >idn_smr_size( Mbytes) -Limiting to number MB

The value of idn_nwr_sizevariable is greater than the valueof idn_smr_size variable. Thevalue of idn_nwr_size cannotbe larger than the value ofidn_smr_size .

The IDN driver reduces the size ofthe network region (NWR) to thetotal size of the shared memoryregion (SMR). If the IDN must have aNWR that is larger than the currentsize of the SMR, increase the size ofthe SMR so that the size of the NWRcan be increased to the appropriatevalue.

WARNING: IDN: 107:memory region( bytes) <slab size( bytes)

The value of the idn_nwr_sizevariable is less than the size of oneof the slabs within the SMR.

Increase the value of idn_smr_sizeor idn_nwr_size to a value that islarger than the smallest buffer size inthe SMR. Or, reset other tunables,such as idn_slab_bufcount , untilthe size of each slab within the IDNis smaller than the value ofidn_nwr_size .

WARNING: IDN: 108:idn_lowat( bytes) >=idn_hiwat( bytes)

The specified values for the low-water and high-water marks forIDN STREAMS are not setproperly.

Lower the value of idn_lowat orincrease the value of idn_hiwat asappropriate. Refer to the SunEnterprise 10000 IDN ConfigurationGuide for more information about theappropriate values for theseparameters.

TABLE 2-2 IDN Domain-Specific Messages, 100 through 142 (Continued)



WARNING: IDN: 109:mailbox area( bytes) + slabsize( bytes) > nwrregion( bytes)

The specified values for themailbox area, idn_mbox_size ,and the slab size,idn_slab_size , variables arenot set properly.

Increase the size of the NWR or theSMR so that the size of the NWR canbe increased. You can also decreasethe size of other variables, such as thenumber of mailboxes per channel,idn_mbox_per_channel , or thenumber of I/O buffers per slab,idn_slab_bufcount .

WARNING: IDN: 110:maximum number ofslabs( number) < minimumrequired( number)

The value of theidn_slab_maxtotal variable isless than the required minimum.The value of this variable iscalculated by the IDN driver. Thedriver returns this warning if thevalue is less than the minimumvalue for nominal usage of theIDN.

Lower the value of theidn_slab_mintotal variable, orincrease the value of the SMR so thatit can hold more slabs. You may needto adjust the value of other driverparameters, such asidn_slab_bufcount , to recoverfrom this error.

WARNING: IDN: 111:idn_smr_bufsize( bytes) noton a 64 byte boundary

The value of theidn_smr_bufsize variable mustbe a multiple of 64.

Reset the idn_smr_bufsizevariable to a multiple of 64.

WARNING: IDN: 112:idn_smr_bufsize( bytes) nota power of 2

The value of theidn_smr_buffsize variablemust be set to a value that is apower of two.

Reset the idn_smr_bufsizevariable to a power of two.

WARNING: IDN: 113:idn_mbox_per_net( number)must be an odd number

For proper hashing, the value ofthe idn_mbox_per_net variablemust be an odd number.

Reset the idn_mbox_per_netvariable to an odd number.

WARNING: IDN: 115:idn_netsvr_wait_min( seconds) cannot begreater thanidn_netsvr_wait_max( seconds)

The minimum wait time for theIDN net server cannot be greaterthan the maximum wait time.

Decrease the value ofidn_netsvr_wait_min , or increasethe value ofidn_netsvr_wait_max .

WARNING: IDN: 116:failed rmalloc(kernelmap,number pages)

The operating system failed toallocate pages number of thevirtual address space for themapping of the SMR.

Reboot the domain, then attempt tolink the domain to the IDN.




WARNING: IDN: 117: IDNnot enabled

The IDN driver failed to initializethe IDN because the IDN was notenabled (that is, idn-smr-size isset to zero).

At the OBP prompt, use the ndd (1M)command to check the value of theidn-smr-size variable. If it is set tozero, reset it to the appropriate valueto enable the IDN and to set the sizeof the SMR. You must reboot thedomain if you change the value ofthis variable.

WARNING: IDN: 118:hardware config notappropriate

The hardware configurationwithin the domain that you aretrying to link is not appropriatefor an IDN, or the IDN drivercould not determine the hardwareconfiguration.The hardware configurationwithin a domain could cause thiserror if it consists of one of thefollowing configurations:A system board that hostsmemory does not host a CPU.System boards in domains musthost at least one CPU for thedomain to be considered eligiblefor linking to an IDN. See optionno_non_proc_boards in thepostrc (4) man page on the SSPfor information on how to preventsystem boards without a CPUfrom being included in thedomain.The shared memory mask on theCIC is not enabled to allow theIDN driver to manipulate theregisters.

Ensure that each system board thatcontains memory has at least oneCPU and that SSP 3.2 is running onthe SSP.

WARNING: IDN: 119:failed to initializenumber protocol servers

The IDN driver failed to start upthe number protocol servers thatmanage the IDN connections.Typically, a strain on kernelresources causes this error.

Reload the IDN driver. If this erroroccurs repeatedly, reduce thememory usage by other applications,if possible.

WARNING: IDN: 120:cannot deinit whileactive (state = GSTATE)

The DR operation tried todeinitialize the IDN driver whileit was still in use (that is, notoffline).

Ensure that the domain is completelyunlinked from all IDNs before youinitiate a DR operation on thedomain.




IDN: 121: domain domain_ID(cpu CPUID, name “ host”,state DSTATE)

This error displays the IDN stateof each domain connection. Thiserror message occurs inconjunction with messages 104and 120.

See error messages 104 and 120.

WARNING: IDN: 123:unexpected M_DATApackets for q_streamVADDR

The STREAMS read procedure inthe IDN driver received anunexpected data packet on therespective stream queue. Thepacket is discarded.

If this error persists, report theproblem to your Sun Microsystems,Inc., service representative.

WARNING: IDN: 124:sigblk for cpuid CPUIDis NULL

The CPU in question expected toreceive messages from the SSP;however, the signature block(BBSRAM) data structure for thatCPU is not mapped properly.

Unload, then reload, the IDN driver.If that does not work, unlink thedomain, then reboot it. Relink thedomain after it has bootedsuccessfully.

WARNING: IDN: 125: op( IDNOP) failed,returning ( errno/ IDNERR[ EPARAM0, EPARAM1,EPARAM2])

An attempted IDN operation(link, unlink, or info) failed. In themessage, errno equals the errornumber, IDNERR equals the IDNerror, and EPARAM2 representsthe parameters that are dependenton this type of IDN error.

Ensure that you used the correctparameters. If not, retry the operationwith the correct parameters.

WARNING: IDN: 126:sighandler threadalready exists ( VADDR)

The IDN driver attempted tocreate an unnecessary, duplicate,sigblock-interrupt-handler thread.

You can safely ignore this message.

WARNING: IDN: 127:cannot change parameterwhile IDN connected

The IDN tunable parameter thatyou tried to change cannot bechanged while the domain islinked to an IDN.

Unlink the domain before youattempt to change the parametersettings for the specified parameter(parameter).

WARNING: IDN: 128:cannot change parameterwhile DLPI attached

The IDN tunable parameter thatyou tried to change cannot bechanged while the IDN interface(idn X) is plumbed underTCP/IP.

Unplumb all of the IDN interfacesthat are under TCP/IP control beforeyou attempt to change the parametersettings for the specified parameter(parameter).

WARNING: IDN: 129: IDNOPoperation timed out

An IDN operation (link, unlink, orinfo) exceeded the specified wait-time before it successfullycompleted.

Check for AWOL domains in theIDN. If present, unlink the AWOLdomain before you attempt to unlinkthe local domain. You can use theforce option, -f or -F ; however, youmust use the force option withcaution.




WARNING: IDN: 130: IDNDMV handler alreadyinitialized

The IDN driver attempted toinitialize the interrupt handler toomany times.

Reboot the domain. If this errorpersists, contact your Sun servicerepresentative.

WARNING: IDN: 131;unable to allocate dataarea for DMV handler

The IDN driver was unable toallocate a data area for controlstructures that are used by theDMV handler.

This error typically occurs whenmemory usage levels are too high.Retry the IDN command when theusage level decreases, or removesome of the system activity that iscausing the high usage level.

WARNING: IDN: 132:failed to add IDN DMVhandler

The IDN driver failed to registerits internal interrupt handler withthe DMV-based kernel subsystem.

Reboot the domain, or unload theIDN driver and retry the operation. Ifthis error persists, report the problemto your Sun service representative.

WARNING: IDN: 133:sigblock event areamissing

The signature block event areathat is used between the IDNdriver and the SSP may bemissing or corrupted.

Reboot the domain, or unload theIDN driver and retry the operation. Ifthis error persists, report the problemto your Sun service representative.

IDN: 134: unable to markboardset ( BMASK) AWOL

This error returns a 16-bit boardmask that indicates which boardsin the domain could not bemarked as AWOL so that theycould be handled by the SSP.

Unlink the domain(s) in question,then relink them to the domain. Youmay need to reboot the domain or tounload the IDN driver before youretry the operation.

IDN: 135: idn:kstat_create failed

Unable to create the kstatstructures. Thus, global kernelstatistics for the IDN are notmaintained.

Reboot the domain, and retry thecommand, if necessary.

WARNING: IDN: 136:“ property” property notfound, disabling IDN

The IDN driver failed to initializebecause it did not find thespecified OBP property.

Ensure that the SSP 3.2 software is onthe SSP.

WARNING: IDN: 137: SMRsize is 0, disabling IDN

The IDN driver failed to initializebecause the OBP variable idn-smr-size is set to zero (0).

Reset the idn-smr-size variable tothe appropriate value. The valuemust be the same for all of thedomains in an IDN. Reboot thedomain after you reset the value ofthe variable.

WARNING: IDN: 138: SMRsize ( numberMB) is toobig (max = numberMB),disabling IDN

The IDN driver failed to initializebecause the value of the OBPvariable idn-smr-size is toolarge.





WARNING: IDN: 139: OBPregion for SMR is 0length

The IDN driver failed to initializebecause the OBP variable idn-smr-size is set to zero (0).


WARNING: IDN: 140: OPBregion ( bytes B) smallerthan requested size ( bytesB)

The SMR region allocated by theOBP is smaller than the value ofthe OBP variable idn-smr-size .

Ensure that the SSP 3.2 software isrunning on the SSP, then reset theidn-smr-size variable to theappropriate value. The value must bethe same for all of the domains in anIDN. Reboot the domain after youreset the value of the variable.

WARNING: IDN: 141: OPBregion ( PADDR) not on( hex_number) boundary

The SMR region allocated by OBPis not on the appropriate memoryaddress boundary (64-Kbytes).

Ensure that the SSP 3.2 software isrunning on the SSP, then reboot thedomain and retry the operation.

NOTICE: IDN: 142: link(domain domain_ID, cpuCPUID) connected

The domain has been linked withdomain domain_ID that hosts CPUCPUID.

Notification only



NOTICE: IDN: 200: link(domain domain_ID, cpuCPUID) disconnected

The domain has been unlinkedwith domain domain_ID that hostsCPU CPUID.

Notification only

WARNING: IDN: 201:( IDNOP) invalid cpu-id( CPUID)

During the IDN operation, theIDN driver specified an invalid IDnumber for the CPU.

Retry the IDN operation.

WARNING: IDN: 202:( IDNOP) invalid time-outvalue ( seconds)

An invalid time out value waspassed to the IDN operation(IDNOP = LINK/UNLINK).


WARNING: IDN: 203:( IDNOP) invalid domain-id ( domain_ID)

An invalid domain ID was passedto the IDN operation (IDNOP =LINK/UNLINK).


WARNING: IDN: 204:domain domain_ID state( DSTATE) inappropriate

The domain domain_ID was not inthe closed state when the IDNoperation was executed.

Retry the IDN operation. If this errorpersists, unlink the domain.




WARNING: IDN: 205:( function) failed to open-domain ( domain_ID, CPUID)

The internal IDN function functionfailed to open an IDN domaincontrol structure for managing anIDN connection with domaindomain_ID and CPU CPUID.

Wait a few minutes for theconnection to be resolved. If theconnection cannot be resolved, rebootdomain domain_ID.

WARNING: IDN: 206:cannot link domains withequal votes (L( domain_ID),R( domain_ID), hex_number)

The local domain, domain_ID, hasthe same vote ticket, hex_number,as the domain, domain_ID, towhich it is trying to link. The votetickets are determined internallyand must be unique.

Reboot the local domain, then retrythe operation. If the error occursagain, reboot domain domain_ID, thenretry the operation. If the errorpersists, contact your Sun servicerepresentative.

WARNING: IDN: 207:local/remote master-idconflict( local_domain_ID.lmasterid =domain_ID_a,remote_domain_ID.rmasterid= domain_ID_b)

The local domain, local_domain_ID,has a master ID, domain_ID_a, thatconflicts with the master ID,domain_ID_b, of domainremote_domain_ID.

Retry the operation. If the errorpersists, reboot both of the domains,then retry the operation.

WARNING: IDN: 208:idn_select_master:unknown case ( number)

This is an internal error. Duringthe selection of the masterdomain, the IDN driverencountered an unexpected case,number.

Retry the operation. If the errorpersists, reboot both of the domains,then retry the operation.

WARNING: IDN: 209:remote domain (iddomain_ID, cpu CPUID)reporting master (idmaster_domain_ID) withoutcpuid

During the IDN operation, theremote domain, domain_ID,returned the ID of the master tothe local domain, but not the CPUID.

Retry the operation. If this errorpersists, reboot the remote domain.

WARNING: IDN: 210:failed to init MASTERcontext

This is an internal error. The localdomain failed to initialize controlstructures that the domain needsto be a master domain.

Reboot the local domain, then retrythe operation.

WARNING: IDN: 211:disconnect domaindomain_ID, unexpectedGSTATE (GSTATE)

During the disconnect operationfor domain domain_ID, the localIDN was in an unexpected globalstate, GSTATE.


PANIC: IDN: 212:disconnect domaindomain_ID, bad GSTATE( GSTATE)

During the disconnect operationfor domain domain_ID, the localIDN was in an unexpected globalstate, GSTATE.





WARNING: IDN: 213: nodestination specified(d= domain_ID, c= channel,n=0x NE)

The local domain attempted tosend a data packet to aninappropriate destination, domainID domain_ID, on channel channelwith the network ID NE.

Retry the operation. If this errorpersists, unlink the local domain,then relink it and retry the operation.

WARNING: IDN: 214:received message( MSG[0x M_number]) fromself (domid domain_ID)

The local domain received an IDNconnection protocol message,MSG[0xM_number], from itself,domain ID domain_ID.


WARNING: IDN: 215:invalid cookie ( cookie)for message ( M_number)from domain domain_ID

The local domain received an IDNconnection protocol message,M_number, from domaindomain_ID with an invalid or stalecookie, cookie.

Retry the operation. If this errorpersists, unlink the local domainand/or remote domain, then relinkthe local and/or remote domain.

WARNING: IDN: 216:( M_number)msgtype/( A_number)acktype rcvdfrom domain domain_ID

The local domain received aninvalid IDN connection protocolmessage or acknowledgement(M_number/A_number) fromdomain domain_ID.

Retry the operation. If this errorpersists, unlink the local and/orremote domain, then relink the localand/or remote domain.

WARNING: IDN: 217:unknown CFGARG type ( type)from domain domain_ID

The local domain received anunexpected type, type, ofconfiguration message from theremote domain, domain_ID.


WARNING: IDN: 218:missing some requiredconfig items from domaindomain_ID

During the connection operation,the local domain did not receiveall of the configurationinformation it expected fromdomain domain_ID.


WARNING: IDN: 219:remote domain domain_IDMTU (bytes) invalid(local.mtu = bytes)

The MTU size, bytes, receivedfrom domain domain_ID is notcompatible with the MTU size ofthe local domain, bytes. The valueof the IDN tunable parameteridn_smr_bufsize must be thesame for all of the domains in anIDN.

Reset the value of theidn_smr_bufsize parameter on thelocal domain or the remote domainso that the values are the same.




WARNING: IDN: 220:remote domain domain_IDBUFSIZE ( bytes) invalid(local.bufsize = bytes)

The local domain received an SMRbuffer size, bytes, from the remotedomain that is not compatiblewith the SMR buffer size of thelocal domain. The value of theIDN tunable parameteridn_smr_bufsize must be thesame for all of the domains in anIDN.

Reset the value of theidn_smr_bufsize parameter on thelocal domain or the remote domainso that the values are the same.

WARNING: IDN: 221:remote domain domain_IDSLABSIZE ( bytes) invalid(local.slabsize = bytes)

The local domain received an SMRslab size, bytes, from domaindomain_ID that is not compatiblewith the SMR slab size of the localdomain. The value of the IDNtunable parametersidn_slab_bufcount andidn_smr_bufsize must be thesame for all of the domains in anIDN.

Reset the slab size parameters on thelocal and/or remote domain.

NOTICE: 222: no IDNlinkage found(b= BMASK_a, i= BMASK_b)upgrading unlink FTYPE -> FORCE_HARD

The SSP requested that the localdomain be unlinked from theremote domain with boardmaskFTYPE; however, the SSP wasunable to find a hardware link inthe IDN hardware register boardmask BMASK_b. The specified softforce option, -f , was upgraded tothe hard force option, -F , tounlink the domain.

No action is required. The soft forceoption, -f, attempts to unlink all ofthe specified domains in the standardmanner; however, if a time-outcondition occurs due to the presenceof an AWOL domain within the IDN,the domain_unlink(1M) commanduses the -F option to remove the link,forcing the domain to be unlinked.

WARNING: IDN: 223:remote domain domain_IDNWRSIZE (Mbytes) invalid(local.nwrsize = Mbytes)

The local domain received a valueof the idn_nwr_size variablefrom the remote domain that doesnot match the value ofidn_nwr_size on the localdomain. The value of theidn_nwr_size variable must bethe same for all of the domains inthe IDN.

Reset the value of theidn_nwr_size variable for theremote domain.




WARNING: IDN: 224:remote domain domain_IDidn_max_nets ( number)invalid (local.maxnets =number)

The local domain received a valueof the idn_max_nets variablefrom the remote domain that doesnot match the value ofidn_max_nets on the localdomain. The value of theidn_max_nets variable must bethe same for all of the domains inthe IDN.

Reset the value of theidn_max_nets variable for theremote domain.

WARNING: IDN: 225:remote domain domain_IDMBOX_PER_NET (number)invalid (local.mboxpernet= number)

The local domain received a valuefor the idn_mbox_per_netvariable from the remote domainthat does not match the value ofidn_mbox_per_net on the localdomain. The value of theidn_mbox_per_net variablemust be the same for all of thedomains in the IDN.

Reset the value of theidn_mbox_per_net variable for theremote domain.

WARNING: IDN: 226:remote domain domain_IDCHECKSUM flag ( number)mismatches localdomain’s ( number)

The local domain received a valuefor the idn_checksum variablefrom the remote domain that doesnot match the value ofidn_checksum on the localdomain. The value of theidn_checksum variable must bethe same for all of the domains inthe IDN.

Reset the value of theidn_checksum variable for theremote domain.

WARNING: IDN: 227:missing some requiredconfig items from domaindomain_ID

The local domain did not receiveall of the expected configurationinformation from the remotedomain, domain_ID.

Retry the link operation. If this errorpersists, reboot the remote domain,then retry the link operation.

WARNING: IDN: 228:master’s SMR ( bytes)larger than local’s SMR( bytes)

The size the SMR for the masterdomain is larger than the virtualspace the local domain hasavailable for the SMR. The OBPvariable idn-smr-size must bethe same for all of the domains inan IDN.

Reset the size of the idn-smr-sizevariable for the local domain and/orthe remote domains so that the size isthe same. Reboot the domain(s), thenretry the link operation.




WARNING: IDN: 229:remote domain domain_IDboardset ( BMASK)conflicts withMCADR(board number)[ MCADR]

The local domain receivedconflicting information about theMCADR register from domaindomain_ID. Board number isreported to have a MCADRsetting, but it is not present in thephysical board set BMASK of theremote domain. MCADRrepresents the actual MCADRregister value.

Reboot domain domain_ID, then retrythe operation.

WARNING: IDN: 230:remote domain domain_IDreported number ofMCADRs (number)mixmatches received( number)

The local domain receivedconflicting information about theMCADRs in domain domain_ID.The number of MCADRs specifiedby domain number does not matchthe number of MCADRs reportedby that domain.

Reboot domain domain_ID, then retrythe operation.

WARNING: IDN: 231:domain domain_ID boardset( BMASK) conflicts withexisting IDN boardset( BMASK)

The set of boards in the boardmask BMASK for domaindomain_ID overlap the existingboards BMASK in the IDN.

Ensure that the local domain haspassed the power-on self-test (POST).Unlink the domain, then relink it.

WARNING: IDN: 232:domain domain_ID cpuset( CPUSET) conflicts withexisting IDN cpuset( CPUSET)

The set of CPUs in the CPU maskCPUSET for domain domain_IDoverlap the existing CPUsCPUSET in the IDN.

Ensure that the local domain haspassed the power-on self-test (POST).Unlink the domain, then relink it.

WARNING: IDN: 233:domain domain_ID missingcpu per memory boardset( BMASK), cpu boardset( BMASK)

Each system board in the domaindomain_ID must have at least oneCPU if it hosts memory. Board setBMASK represents the board thathave memory, and board setBMASK represents the boards thathave at least one CPU.

Ensure that the domain you want tolink has system boards that host atleast one CPU on each board thathosts memory.

WARNING: IDN: 234:failed to programhardware for domaindomain_ID (boardset =BMASK

The IDN driver was unable toprogram the hardware for thelocal domain to allow sharedmemory access with domaindomain_ID, which contains theboard set BMASK.

Do not execute additional IDNoperations. When appropriate, haltdomain domain_ID, and run a fulldiagnostic test by using thehpost (1M) command.




WARNING: IDN: 235:[ MBXTYPE] mailbox(domain domain_ID, channelchannel) SMR CORRUPTED -RELINKIDN: 235: [ MBXTYPE]expected (cookie cookie,cksum hex_number), actual(cookie cookie, cksumhex_number)IDN: 235: [ MBXTYPE]activeptr ( VADDR),readyptr ( VADDR)

The local domain detected that thesend and/or receive mailboxMBXTYPE control area iscorrupted for domain domain_ID.These messages indicate theexpected and actual values of thecookie and checksum controlinformation. Depending on thecondition, an additional messageis displayed containing additionalcontrol information that is usedfor synchronization during datatransmissions (activeptr andreadyptr ).

Unlink the master domain, thenrelink it. If this error persists,dismantle the entire IDN, thenreassemble it.

WARNING: IDN: 236:domain ( host) [iddomain_ID] not respondingto IDN_command [# number]WARNING: IDN: 236:domain [id domain_ID, cpuCPUID] not responding toIDN_command [# number]

The local domain attempted toconnect or disconnect domain hostor domain ID domain_ID withCPU ID CPUID; however, thedomain is not responding. numberrepresents the number of detectedAWOL messages.

Unlink domain host, then retry thelink operation.

WARNING: IDN: 237:invalid number ( number)of protocol servers

The specified number of IDNprotocol servers is invalid. Thevalue of the idn.conf (4) tunableparameteridn_protocol_nservers mustbe greater than zero (0).

Reset the value of theidn_protocol_nserversparameter in the idn.conf (4) file toan appropriate number.

WARNING: IDN: 238:kmem_cache_create(jobcache) failed

The kernel failed to create aninternal cache for allocating IDNjob control data structures.

Reboot the local domain, then retrythe link operation. If this errorpersists, remove unused softwarefrom the domain, and retry the linkoperation.

WARNING: IDN: 239:invalid cpuid ( CPUID)specified for IDN netchannel

An invalid CPU ID, CPUID, wasspecified for the local domain.channel represents the networkinterface for the IDN data serverthread.

Retry the operation with a valid CPUID for the local domain.




WARNING: IDN: 240:(channel channel) SMRCORRUPTED - RELINKIDN: 240: (channelchannel) cookie (expectedcookie, actual cookie)IDN: 240: (channelchannel) actv_flg(expected hex_number,actual hex_number)IDN: 240: (channelchannel) ready_flg(expected hex_number,actual hex_number)

The IDN data server for networkinterface channel encounteredcorrupted data in the SMR. Theexpected and actual values forcontrol information that is used bythe data server are included(cookie , actv_flg , andready_flg ). Subsequent datatransmissions are likely to fail.

Unlink the master domain, thenrelink it. If this error persists,dismantle the IDN, then reassembleit.

WARNING: IDN: 241:[ operation] (domaindomain_ID, channelchannel_ID SMR CORRUPTED -RELINK)

The IDN driver attempted totransmit or receive data to or froman IDN mailbox in the SMR;however, the SMR was corrupted.The operation is designated asoperation, send or recv , in themessage. Future datatransmissions are likely to fail.

Unlink the master domain, thenrelink relink it. If this error persists,dismantle the IDN, then relink thedomains.

WARNING: IDN: 242:maximum channels ( number)already open

You cannot plumb more networkinterfaces than the IDN driver isconfigured to support.

Reset the idn.conf (4) tunableidn_max_nets , then retry theoperation.



WARNING: IDN: 300: noslab allocations withouta master

The slave domain attempted toallocate a slab of memory withouta master domain being present.

If this error persists, unlink the localdomain, then relink it.

WARNING: IDN: 301:( SMROP) unknown slabstate ( slab_state) fordomain domain_ID

This is an internal error, indicatingthat a SMR slab was in anunexpected state for domain IDdomain_ID, with respect to slaboperation SMROP.

Unlink the local domain, then relinkit.

WARNING: IDN: 302: noslab free without amaster

The slave domain attempted tofree up a slab of memory withoutthe master domain being present.





WARNING: IDN: 303:buffer len bytes >IDN_DATA_SIZE ( bytes)

The local domain attempted toallocate an SMR buffer with alength greater than the lengthsupported by the IDNconfiguration.

Unlink the local domain, then relinkit.

WARNING: IDN: 304:buffer ( VADDR) fromdomain domain_ID not on ahex_number boundary

An SMR buffer at kernel virtualaddress VADDR was receivedfrom domain ID domain_ID;however, it was not aligned on theexpected boundary hex_number (inbytes).

Unlink the local domain and/ordomain domain_ID, then relink thelocal domain and/or domaindomain_ID.

WARNING: IDN: 305:buffer length ( bytes) fromdomain domain_ID greaterthan IDN_DATA_SIZE ( bytes)

An SMR buffer of length bytes wasreceived from domain IDdomain_ID; however, the lengthwas greater than the length that issupported by the local domain(bytes in bytes).

Unlink the local domain and/ordomain domain_ID, then relink thelocal domain and/or domaindomain_ID.

WARNING: IDN: 306:unknown buffer( hex_number) from domaindomain_ID

The local domain received arequest for a domain ID,domain_ID, that was not in theexpected range of valid domainIDs (that is, 0 to 15).


WARNING: IDN: 307:domain id ( domain_ID)invalid

The SMR subsystem received arequest for a domain IDdomain_ID that was not in theexpected range of valid domainIDs (that is, 0 to 15).




WARNING: IDN: 400:corrupted MAC header(exp hex_number or 0xffff,act hex_number)

The MAC header in the SMR datapacket contained bad data.

Unlink the local domain, then relinkit. If this error persists, dismantle theIDN, and reassemble it.

IDN: 450: idn X:kstat_create failed

Unable to create the kstatstructures. No per-instance kernelstatistics will be maintained forthe IDN.

Reboot the local domain if you needthe per-instance kernel statistics to bemaintained.






WARNING: IDN: 500:failed to write sm_bar(lsb/msb) ( hex_number)

While programming the SMR, thelocal domain failed to write the(lsb /msb) portion of the sharedmemory base-address-registerwith value hex_number.

Do not perform IDN operations.When appropriate, halt the localdomain, and run a full diagnostic testby using the hpost (1M) command.

WARNING: IDN: 501:failed to write sm_lar(lsb/msb) ( hex_number)

While programming access to theSMR, the local domain failed towrite the (lsb /msb) portion of theshared memory limit-address-register with value hex_number.


WARNING: IDN: 502:unable to store data( hex_number) to CIC buffer( PADDR)

While programming access to theSMR, the local domain failed towrite to the CIC (CoherencyInterface Controller) prep bufferwith the data hex_number.


WARNING: IDN: 503:( PCPROG) failed toupdate PC madr (expected0xXXX, actual hex_number)

While programming access to theSMR during the PCPROG(invalidate or validate) phase, thelocal domain failed to write amemory address decoding register(MADR) entry to the portcontroller (PC).


WARNING: IDN: 504:( PCPROG) failed toupdate IOPC madr(expected hex_number,actual hex_number)

While programming access to theSMR during the PCPROG(invalidate or validate) phase, thelocal domain failed to write amemory address decoding register(MADR) entry of the I/O portcontroller (IOPC).


WARNING: IDN: 505: boardnumber mising any validPCs

Board number does not containvalid port controllers (PCs).

Do not perform IDN operations.When appropriate, halt the localdomain to ensure that board XXhosts the appropriate hardware. Youmay need to run a full diagnostic testby using the hpost (1M) command.

WARNING: IDN: 506: cicsm_mask is not writable

The CIC has been programmed byPOST to not let the operatingsystem level software tomanipulate the shared-memorymask register.

Ensure that the SSP 3.2 software isrunning on the SSP. Run a fulldiagnostic test on the board by usingthe hpost (1M) command.


WARNING: IDN: 507:failed to map-inpost2obp structure

The local domain did notsuccessfully map in the POST2OBPdata structure to the address spaceof the kernel.

Halt the local domain, then reboot it.After it reboots, relink it to the IDN.

WARNING: IDN: 508:post2obp checksuminvalid

The POST2OBPdata structure thatwas passed from POST to OBPappeared invalid. The expectedchecksum value did not match thevalue that is reported by the datastructure.


WARNING: IDN: 509: cpuCPUID never responded toCIC update

While programming the SMR foraccess during the parallel updateof the CIC registers phase, CPUCPUID did not respond to theupdate request.


WARNING: IDN: 510:failed write-smregs(bd= number, bs= bus,sm(bar= bar, lar= lar)

The local domain failed to updateall of its shared memory registers.The specific failure occurred onsystem board number, interconnectbus bus, with base/limit-address-register contents of bar/lar,respectively.


WARNING: IDN: 511:update-one (cpu= CPUID,bd=number) time conflict

A stale IDN-hardware updateoperation was encountered duringthe update of the shared memoryregisters across the system.


WARNING: IDN: 512:failed [ add/delete] write-madr (bd= number,rbd= remote_number,madr= hex_number)

The local domain failed to update(to add and/or to delete) the PCmemory address decodingregisters on board number withrespect to the remote board,remote_number. The hex_numbervalue represents the targetedregister contents.


WARNING: IDN: 513: sm-mask error (expected =hex_number, actual =hex_number)

The local domain encounteredinconsistent or unexpected valuesin the shared memory mask of theCIC.


WARNING: IDN: 514: sm-base error (expected =hex_number, actual =hex_number)

The local domain encounteredinconsistent or unexpected valuesin the shared memory baseregister of the CIC.





WARNING: IDN: 515: sm-limit error (expected =hex_number, actual =hex_number)

The local domain encounteredinconsistent or unexpected valuesin the shared memory limitregister of the CIC.


WARNING: IDN: 516: ( local/remote) board number hasmemory, but no cpus -CPU-PER-BOARD REQUIRED

The local domain detected that alocal or remote, local/remote,system board, number, containsmemory, but no CPUs. In an IDN,each system board that hostsmemory must also host at leastone CPU.

Halt the local or remote domain, thencheck its hardware configuration. If itdoes not host a CPU, place it in theblacklist, then relink the domain.




Before You Read This BookHow This Book Is OrganizedUsing UNIX CommandsTypographic ConventionsShell PromptsRelated DocumentationAccessing Sun Documentation OnlineOrdering Sun DocumentationSun Welcomes Your CommentsSearching the Tables in This BookOnline SearchingSpecial Typographical Conventions

IDN Error Messages on the DomainDomain IDN Messages

sun enterprise 10000 idn error messages · 2011. 2. 2. · sunenterprise 10000 sspattributions:...

Documents