Sun Microsystems Sun Enterprise 10000 IDN Error Messages

Sun Enterprise 10000 IDN Error

Messages

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

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

Send comments about this document to: [e-mail]

Copyright 2001Sun Microsystems,Inc., 901San AntonioRoad, PaloAlto, California 94303-4900U.S.A. Allrights reserved.
This product ordocument isprotected bycopyright anddistributed underlicenses restrictingits use, copying,distribution, anddecompilation.

No partof thisproduct ordocument maybe reproducedin anyform byany means withoutprior writtenauthorization ofSun and itslicensors,
if any.Third-partysoftware, includingfont technology,is copyrighted andlicensed fromSun suppliers.

Parts ofthe productmay bederived fromBerkeley BSDsystems, licensedfrom theUniversity of California.UNIX isa registeredtrademark in
the U.S.and othercountries, exclusivelylicensed throughX/Open Company,Ltd.

Sun, SunMicrosystems, theSun logo,AnswerBook2, docs.sun.com,Sun Enterprise,OpenBoot, and Solarisare trademarks,registered
trademarks, orservice marksof SunMicrosystems, Inc.in theU.S. and othercountries. AllSPARCtrademarks areused underlicense and are
trademarks orregisteredtrademarks of SPARCInternational, Inc.in theU.S. and other countries. Productsbearing SPARCtrademarks are
based uponan architecturedeveloped bySun Microsystems,Inc.

The OPENLOOK andSun™ GraphicalUser Interfacewas developed bySun Microsystems,Inc. forits usersand licensees. Sunacknowledges
the pioneeringefforts ofXerox inresearchingand developing theconcept ofvisual orgraphical user interfaces for thecomputer industry.Sun
holds anon-exclusive licensefrom Xeroxto theXerox GraphicalUser Interface,which licensealso covers Sun’slicensees whoimplement OPEN
LOOK GUIsand otherwisecomply withSun’s writtenlicense agreements.

Federal Acquisitions:Commercial Software—GovernmentUsers Subjectto StandardLicense Termsand Conditions.
DOCUMENTATIONIS PROVIDED“AS IS”AND ALL EXPRESSOR IMPLIEDCONDITIONS, REPRESENTATIONSAND WARRANTIES,

INCLUDING ANYIMPLIED WARRANTYOF MERCHANTABILITY,FITNESS FOR A PARTICULARPURPOSE OR NON-INFRINGEMENT,
ARE DISCLAIMED,EXCEPT TOTHE EXTENTTHATSUCH DISCLAIMERSARE HELD TOBE LEGALLYINVALID.

Copyright 2001Sun Microsystems,Inc., 901San AntonioRoad, PaloAlto, Californie 94303Etats-Unis. Tousdroits réservés.
Ce produit oudocument estdistribué avecdes licencesqui en restreignent l’utilisation,la copie,la distribution,et ladécompilation. Aucune

partie dece produitou documentne peutêtre reproduitesous aucuneforme, parquelque moyenque ce soit,sans l’autorisationpréalable et
écrite deSun etde sesbailleurs delicence, s’il yen a.Le logicieldétenu par des tiers, etqui comprendla technologierelative auxpolices de
caractères,est protégépar un copyrightet licenciépar desfournisseurs deSun.

Des partiesde ceproduit pourrontêtre dérivéesdes systèmesBerkeley BSDlicenciés parl’Université de Californie.UNIX estune marque
déposée auxEtats-Unis etdans d’autrespays etlicenciée exclusivementpar X/Open Company,Ltd.

Sun, SunMicrosystems, lelogo Sun,AnswerBook2, docs.sun.com,Sun Enterprise,OpenBoot, et Solarissont desmarques defabrique oudes
marquesdéposées, ou marquesde service,de SunMicrosystems, Inc.aux Etats-Uniset dansd’autres pays. Toutes les marques SPARCsont
utilisées souslicence etsont desmarques defabrique oudes marquesdéposées de SPARCInternational, Inc.aux Etats-Uniset dans d’autres
pays. Lesproduits portantles marquesSPARCsont baséssur unearchitecture développéepar SunMicrosystems, Inc.

L’interfaced’utilisation graphiqueOPEN LOOKet Sun™a été développéepar SunMicrosystems, Inc.pour sesutilisateurs et licenciés. Sun
reconnaîtles effortsde pionniers deXerox pourla rechercheet ledéveloppement duconcept desinterfaces d’utilisation visuelle ou graphique
pour l’industriede l’informatique.Sun détientune licencenon exclusive deXerox surl’interface d’utilisationgraphique Xerox,cette licence
couvrant égalementles licenciésde Sunqui mettenten place l’interfaced’utilisation graphiqueOPEN LOOKet quien outre se conforment aux
licences écritesde Sun.

LA DOCUMENTATIONEST FOURNIE“EN L’ETAT”ET TOUTESAUTRES CONDITIONS, DECLARATIONSET GARANTIESEXPRESSES
OU TACITESSONT FORMELLEMENTEXCLUES, DANSLA MESURE AUTORISEE PAR LALOI APPLICABLE,Y COMPRISNOTAMMENT
TOUTEGARANTIE IMPLICITE RELATIVEA LAQUALITE MARCHANDE,A L’APTITUDEA UNEUTILISATIONPARTICULIEREOU A
L’ABSENCEDE CONTREFAÇON.

Please

Recycle

Sun Enterprise10000 SSPAttributions:
This software iscopyrighted bythe Regentsof theUniversity of California, SunMicrosystems, Inc.,and otherparties. Thefollowing terms

apply toall filesassociated withthe softwareunless explicitly disclaimedin individual files.
The authorshereby grantpermission touse, copy,modify,distribute, and licensethis softwareand itsdocumentation forany purpose,

provided thatexisting copyrightnotices areretained inall copies andthat thisnotice isincluded verbatim inanydistributions. Nowritten
agreement, license,or royaltyfee isrequired forany ofthe authorizeduses. Modifications tothis softwaremay be copyrightedby theirauthors
and neednot followthe licensingterms describedhere, providedthat the newterms areclearly indicated onthe firstpage ofeach filewhere
they apply.

IN NOEVENT SHALLTHE AUTHORSOR DISTRIBUTORSBE LIABLETO ANYPARTY FOR DIRECT, INDIRECT,SPECIAL, INCIDENTAL,
OR CONSEQUENTIALDAMAGES ARISING OUTOF THEUSE OFTHIS SOFTWARE, ITS DOCUMENTATION,OR ANYDERIVATIVES
THEREOF, EVENIF THEAUTHORS HAVEBEEN ADVISEDOF THE POSSIBILITYOF SUCH DAMAGE.

THE AUTHORSAND DISTRIBUTORSSPECIFICALLYDISCLAIM ANYWARRANTIES, INCLUDING, BUTNOT LIMITED TO,THE
IMPLIED WARRANTIESOF MERCHANTABILITY, FITNESS FOR APARTICULARPURPOSE, AND NON-INFRINGEMENT. THIS
SOFTWARE ISPROVIDED ON AN"AS IS"BASIS, ANDTHE AUTHORS AND DISTRIBUTORS HAVE NOOBLIGATION TOPROVIDE
MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS,OR MODIFICATIONS.

RESTRICTED RIGHTS:Use, duplicationor disclosureby thegovernment is subjectto the restrictions as setforth insubparagraph (c)(1) (ii) of
the Rightsin Technical Dataand ComputerSoftware Clauseas DFARS 252.227-7013 andFAR 52.227-19.

This isscotty, asimple tclinterpreter withsome specialcommands toget information aboutTCP/IP networks.Copyright (c)1993, 1994, 1995,J.
Schoenwaelder,TU Braunschweig,Germany,Institute forOperating Systemsand ComputerNetworks. Permission touse, copy, modify, and
distribute thissoftware andits documentationfor anypurpose andwithout fee ishereby granted,provided thatthis copyrightnotice appears
in allcopies. The Universityof Braunschweigmakes norepresentations aboutthe suitabilityof this software forany purpose. It isprovided “as
is" withoutexpress orimplied 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
TABLE 2-3 IDN Domain-Specific Messages, 200 through 242 13
TABLE 2-4 IDN Domain-Specific Messages, 300 through 307 20
TABLE 2-5 IDN Domain-Specific Messages, 400 through 450 21
TABLE 2-6 IDN Domain-Specific Messages, 500 through 516 22

vii

viii Sun Enterprise 10000 IDN Error Messages • January 2001

Preface

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

Before You Read This Book

This book is intended for the Sun Enterprise 10000 server system administrator who
has a working knowledge of UNIX® systems, particularly those based on the
Solaris™ operating environment. If you do not have such knowledge, first read the
Solaris user and system administrator books in AnswerBook2™ format provided
with this system and consider UNIX system administration training.

How This Book Is Organized

This 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 Commands

This document may not contain information on basic UNIX commands and
procedures such as shutting down the system, booting the system, and configuring
devices.

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 or
Symbol

AaBbCc123 The names of commands, files,

AaBbCc123 What you type, when

AaBbCc123 Book titles, new words or terms,

Meaning Examples

and directories; on-screen
computer output

contrasted with on-screen
computer output

words to be emphasized

Command-line variable; replace
with a real name or value

Edit your .login file.
Use ls -a to list all files.

% You have mail.
% su

Password:

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

To delete a file, type rm filename.

x Sun Enterprise 10000 IDN Error Messages • January 2001

Shell Prompts

Shell Prompt

C shell machine_name%
C shell superuser machine_name#
Bourne shell and Korn shell $
Bourne shell and Korn shell superuser #

Related Documentation

Application Title Part Number

User Sun Enterprise 10000 IDN Configuration

Guide
Sun Enterprise 10000 IDN User Guide 806-4131

806-5230

Accessing Sun Documentation Online

The docs.sun.comSMweb site enables you to access Sun technical documentation
on the Web. You can browse the docs.sun.com archive or search for a specific book
title or subject at:

http://docs.sun.com

Preface xi

Ordering Sun Documentation

Fatbrain.com, an Internet professional bookstore, stocks select product
documentation from Sun Microsystems, Inc.

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

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

Sun Welcomes Your Comments

We are interested in improving our documentation and welcome your comments
and suggestions. You can email your comments to us at:

[e-mail]

Please include the part number (806-5231-10) of your document in the subject line of
your 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 the
domain.

Note – If you do not find the error message in this book, refer to the error messages

in the Sun Enterprise 10000 InterDomain Networks User Guide in the SSP 3.4
Answerbook collection.

Searching the Tables in This Book

Before you use the tables in this book, take time to read the following list of search
tips 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 by

the type of error or failure. The contents of the tables is sorted alphabetically in
decending order.

1

Online Searching

You can use the search engine provided in the AnswerBook2™ environment or the
search engine in your browser to find a specific string of characters from an error
message. Before you construct the search string, keep in mind that this appendix
contains special typographical conventions. In addition, you may need to search all
of the tables individually. If you know the error type (that is, where the error was
encountered), use the hypertext links in “IDN Error Messages on the Domain” on
page 2 to start your search.

Special Typographical Conventions

The tables in this appendix contain special typographical conventions for the names
of words and values that change, depending on the type of error. When you search
for an error message, keep in mind that these names appear as generic
representations in italic font. The following list contains the commonly used
representations 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 Domain

This book contains the IDN messages that occur on the domain from which the IDN
command was executed.
IDN errno numbers. This table describes some of the message conventions that are
used in the message tables.
InterDomain 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 the
error, and suggested action. For notifications, the list contains the text of the notice
and 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 • Januar y 2001

TABLE 2-1 contains the name, number, and description of

TABLE 2-2 through TABLE 2-6 contain the common

TABLE 2-2 on page 7, which contains messages 100 through 142.
TABLE 2-3 on page 13, which contains messages 200 through 242.
TABLE 2-4 on page 20, which contains messages 300 through 307.
TABLE 2-5 on page 21, which contains messages 400 through 450.
TABLE 2-6 on page 22, which contains messages 500 through 516.

Chapter 1 IDN Errors Introduction 3

4 Sun Enterprise 10000 IDN Error Messages • Januar y 2001

CHAPTER

2

IDN Error Messages, Notifications,
and Panics on the Domain

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

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

Domain IDN Messages

IDN 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.

TABLE2-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) is

misaligned between the IDN driver and the SSP (P0
represents the length).

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

5

TABLE2-1 IDN Domain-Specific Error Numbers (Continued)

Message Number Description

IDNKERR_INVALID_DOMAIN 0x103 An invalid domain ID was specified (P0 represents the

domain ID, and P1 represents the CPU ID).

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

option).

IDNKERR_INVALID_CMD 0x105 An invalid IDN command was requested (P0 represents

command).

IDNKERR_INVALID_WTIME 0x106 An invalid wait time was specified for the IDN operation (P0

represents the wait time).

IDNKERR_SMR_CORRUPTED 0x107 SMR memory was found corrupted (P0 represents the

domain ID, against which the corruption was found).

IDNKERR_CPU_CONFIG 0x108 Domain ID is not configured properly for an IDN. Each

system 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 hardware

to support an IDN connection to domain ID (P0 represents
the domain ID)

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

locked.

IDNKERR_SIGBINTR_BUSY 0x10b The signature block interrupt handler thread is currently

active.

IDNKERR_SIGBINTR_NOTRDY 0x10c The signature block interrupt handler thread has not been

initialized.

IDNKERR_CONFIG_FATAL 0x10d An error occurred during the exchange of configuration

information with domain ID, specifically it was missing
information (P0 represents the domain ID).

IDNKERR_CONFIG_MULTIPLE 0x10e Multiple conflicts were found between the configuration

parameters exchanged during the connection establishment
(P0 represents the domain ID).

IDNKERR_CONFIG_MTU 0x10f The MTU sizes of the domains do not match (P0 represents

the domain ID; P1 represents the expected value, and P2
represents the actual value).

IDNKERR_CONFIG_BUF 0x110 The values of the idn_smr_bufsize variable conflict

among the domains (P0 represents the domain ID; P1
presents the expected value, and P2 represents the actual
value).

IDNKERR_CONFIG_SLAB 0x111 The values of the SMR slab sizes conflict among the domains

(P0 represents the domain ID; P1 represents the expected
value, and P2 represents the actual value).

6 Sun Enterprise 10000 IDN Error Messages • Januar y 2001

TABLE2-1 IDN Domain-Specific Error Numbers (Continued)

Message Number Description

IDNKERR_CONFIG_NWR 0x112 The values of the idn_nwr_size variables conflict among

the domains (P0 represents the domain ID; P1 represents the
expected value, and P2 represents the actual value).

IDNKERR_CONFIG_NETS 0x113 The values of the idn_max_nets variables conflict between

domains (P0 represents the domain ID; P1 represents the
expected value, and P2 represents the actual value).

IDNKERR_CONFIG_MBOX 0x114 The values of the idn_mbox_per_nets variables conflict

between domains (P0 represents the domain ID; P1
represents the expected value, and P2 represents the actual
value).

IDNKERR_CONFIG_NMCADR 0x115 The number of MCADRs received does not match the

number of MCADRs that the domain had reported to exist
(P0 represents the domain ID; P1 represents the expected
value, and P2 represents the actual value).

IDNKERR_CONFIG_MCADR 0x116 Received an MCADR for a board that the remote domain did

not report to exist (P0 represents the domain ID; P1
represents the expected value, and P2 represents the actual
value).

IDNKERR_CONFIG_CKSUM 0x117 The values of the idn_checksum parameter is not consistent

among the domains (P0 represents the domain ID; P1
represents the expected value, and P2 represents the actual
value).

IDNKERR_CONFIG_SMR 0x118 The master domain SMR is too large for the slave domain

(P0 represents the domain ID; P1 represents the expected
value, and P2 represents the actual value).

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

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

Error Description Recovery

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

WARNING:IDN:101: not in
expected OFFLINE state
for DDI_RESUME

This message indicates a
mismatch between the version of

Unlink the domains, then recreate the

IDN.
the sigblock data structure in the
IDN driver and the region of the
signature block that is reserved for
the IDN.

The IDN driver is not in the

Unlink the domain, then relink it.
expected state for the DR driver to
perform the DDI_RESUME
operation.

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

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

Error Description Recovery

NOTICE: IDN: 102 driver
disabled - check OBP
environment (idn-smr­size)

The IDN driver was not
initialized.

Check the OpenBoot PROM (OBP)
variable idn-smr-size to ensure
that it is set properly. Refer to the Sun

Enterprise 10000 IDN Configuration
Guide for more information about this

variable.

WARNING: IDN: 103:
unable to reference
sigblock area

The

sgnblk_poll_reference()

routine failed to initialize. The

Reload the module after the
operating system boots.

IDN driver may have been loaded
too early in the boot sequence.

WARNING: IDN: 104:
cannot suspend while
active (state = GSTATE)

The IDN driver cannot be
suspended while it is in use.

Wait for the driver to complete the
current transmission, or unlink the
domain from the IDN before you
initiate a DR operation.

WARNING: IDN: 105:
driver parameter
(parameter) specified
(number) out of range

The value for the specified
parameter is outside of the range
of values that can be used for the
IDN.

Reset the parameter with a value that
is within the allowed range.

[low_value - high_value]
WARNING: IDN: 106:

idn_nwr_size (Mbytes)>
idn_smr_size(Mbytes)­Limiting to number MB

The value of idn_nwr_size
variable is greater than the value
of idn_smr_size variable. The
value of idn_nwr_size cannot
be larger than the value of
idn_smr_size.

The IDN driver reduces the size of
the network region (NWR) to the
total size of the shared memory
region (SMR). If the IDN must have a
NWR that is larger than the current
size of the SMR, increase the size of
the SMR so that the size of the NWR
can be increased to the appropriate
value.

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

The value of the idn_nwr_size
variable is less than the size of one
of the slabs within the SMR.

Increase the value of idn_smr_size
or idn_nwr_size to a value that is
larger than the smallest buffer size in
the SMR. Or, reset other tunables,
such as idn_slab_bufcount, until
the size of each slab within the IDN
is smaller than the value of

idn_nwr_size.

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

The specified values for the low­water and high-water marks for
IDN STREAMS are not set
properly.

Lower the value of idn_lowat or
increase the value of idn_hiwat as
appropriate. Refer to the Sun

Enterprise 10000 IDN Configuration
Guide for more information about the

appropriate values for these
parameters.

8 Sun Enterprise 10000 IDN Error Messages • Januar y 2001

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

Error Description Recovery

WARNING: IDN: 109:
mailbox area(bytes) + slab
size(bytes) > nwr
region(bytes)

The specified values for the
mailbox area, idn_mbox_size,
and the slab size,
idn_slab_size, variables are
not set properly.

Increase the size of the NWR or the

SMR so that the size of the NWR can

be increased. You can also decrease

the size of other variables, such as the

number of mailboxes per channel,

idn_mbox_per_channel, or the

number of I/O buffers per slab,

idn_slab_bufcount.

WARNING: IDN: 110:
maximum number of
slabs(number) < minimum
required(number)

The value of the
idn_slab_maxtotal variable is
less than the required minimum.
The value of this variable is
calculated by the IDN driver. The
driver returns this warning if the
value is less than the minimum
value for nominal usage of the

Lower the value of the

idn_slab_mintotal variable, or

increase the value of the SMR so that

it can hold more slabs. You may need

to adjust the value of other driver

parameters, such as

idn_slab_bufcount, to recover

from this error.
IDN.

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

WARNING: IDN: 112:
idn_smr_bufsize(bytes) not
a power of 2

The value of the
idn_smr_bufsize variable must
be a multiple of 64.

The value of the
idn_smr_buffsize variable
must be set to a value that is a

Reset the idn_smr_bufsize

variable to a multiple of 64.

Reset the idn_smr_bufsize

variable to a power of two.

power of two.

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

WARNING: IDN: 115:
idn_netsvr_wait_min
(seconds) cannot be
greater than

For proper hashing, the value of
the idn_mbox_per_net variable
must be an odd number.

The minimum wait time for the
IDN net server cannot be greater
than the maximum wait time.

Reset the idn_mbox_per_net

variable to an odd number.

Decrease the value of

idn_netsvr_wait_min, or increase

the value of

idn_netsvr_wait_max.

idn_netsvr_wait_max
(seconds)

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

The operating system failed to
allocate pages number of the
virtual address space for the

Reboot the domain, then attempt to

link the domain to the IDN.

mapping of the SMR.

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

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

Error Description Recovery

WARNING: IDN: 117: IDN
not enabled

The IDN driver failed to initialize
the IDN because the IDN was not
enabled (that is, idn-smr-size is
set to zero).

At the OBP prompt, use the ndd(1M)
command to check the value of the
idn-smr-size variable. If it is set to
zero, reset it to the appropriate value
to enable the IDN and to set the size
of the SMR. You must reboot the
domain if you change the value of
this variable.

WARNING: IDN: 118:
hardware config not
appropriate

The hardware configuration
within the domain that you are
trying to link is not appropriate
for an IDN, or the IDN driver

Ensure that each system board that
contains memory has at least one
CPU and that SSP 3.2 is running on

the SSP.
could not determine the hardware
configuration.
The hardware configuration
within a domain could cause this
error if it consists of one of the
following configurations:
A system board that hosts
memory does not host a CPU.
System boards in domains must
host at least one CPU for the
domain to be considered eligible
for linking to an IDN. See option

no_non_proc_boards in the
postrc(4) man page on the SSP

for information on how to prevent
system boards without a CPU
from being included in the
domain.
The shared memory mask on the
CIC is not enabled to allow the
IDN driver to manipulate the
registers.

WARNING: IDN: 119:
failed to initialize
number protocol servers

The IDN driver failed to start up
the number protocol servers that
manage the IDN connections.
Typically, a strain on kernel

Reload the IDN driver. If this error

occurs repeatedly, reduce the

memory usage by other applications,

if possible.
resources causes this error.

WARNING: IDN: 120:
cannot deinit while
active (state = GSTATE)

The DR operation tried to
deinitialize the IDN driver while
it was still in use (that is, not
offline).

Ensure that the domain is completely

unlinked from all IDNs before you

initiate a DR operation on the

domain.

10 Sun Enterprise 10000 IDN Error Messages • Januar y 2001

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

Error Description Recovery

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

This error displays the IDN state
of each domain connection. This
error message occurs in

See error messages 104 and 120.

conjunction with messages 104
and 120.

WARNING: IDN: 123:
unexpected M_DATA
packets for q_stream

VADDR

The STREAMS read procedure in
the IDN driver received an
unexpected data packet on the
respective stream queue. The

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

packet is discarded.

WARNING: IDN: 124:
sigblk for cpuid CPUID
is NULL

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

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

An attempted IDN operation
(link, unlink, or info) failed. In the
message, errno equals the error
number, IDNERR equals the IDN
error, and EPARAM2 represents

Unload, then reload, the IDN driver.
If that does not work, unlink the
domain, then reboot it. Relink the
domain after it has booted
successfully.

Ensure that you used the correct
parameters. If not, retry the operation
with the correct parameters.

the parameters that are dependent
on this type of IDN error.

WARNING: IDN: 126:
sighandler thread
already exists (VADDR)

WARNING: IDN: 127:
cannot change parameter
while IDN connected

WARNING: IDN: 128:
cannot change parameter
while DLPI attached

WARNING: IDN: 129: IDNOP
operation timed out

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

The IDN tunable parameter that
you tried to change cannot be
changed while the domain is
linked to an IDN.

The IDN tunable parameter that
you tried to change cannot be
changed while the IDN interface
(idnX) is plumbed under
TCP/IP.

An IDN operation (link, unlink, or
info) exceeded the specified wait­time before it successfully
completed.

You can safely ignore this message.

Unlink the domain before you
attempt to change the parameter
settings for the specified parameter
(parameter).

Unplumb all of the IDN interfaces
that are under TCP/IP control before
you attempt to change the parameter
settings for the specified parameter
(parameter).

Check for AWOL domains in the
IDN. If present, unlink the AWOL
domain before you attempt to unlink
the local domain. You can use the
force option, -f or -F; however, you
must use the force option with
caution.

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

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

Error Description Recovery

WARNING: IDN: 130: IDN
DMV handler already
initialized

WARNING: IDN: 131;
unable to allocate data
area for DMV handler

The IDN driver attempted to
initialize the interrupt handler too
many times.

The IDN driver was unable to
allocate a data area for control
structures that are used by the
DMV handler.

Reboot the domain. If this error

persists, contact your Sun service

representative.

This error typically occurs when

memory usage levels are too high.

Retry the IDN command when the

usage level decreases, or remove

some of the system activity that is

causing the high usage level.

WARNING: IDN: 132:
failed to add IDN DMV
handler

The IDN driver failed to register
its internal interrupt handler with
the DMV-based kernel subsystem.

Reboot the domain, or unload the

IDN driver and retry the operation. If

this error persists, report the problem

to your Sun service representative.

WARNING: IDN: 133:
sigblock event area
missing

IDN: 134: unable to mark
boardset (BMASK) AWOL

IDN: 135: idn:
kstat_create failed

The signature block event area
that is used between the IDN
driver and the SSP may be
missing or corrupted.

This error returns a 16-bit board
mask that indicates which boards
in the domain could not be
marked as AWOL so that they
could be handled by the SSP.

Unable to create the kstat
structures. Thus, global kernel

Reboot the domain, or unload the

IDN driver and retry the operation. If

this error persists, report the problem

to your Sun service representative.

Unlink the domain(s) in question,

then relink them to the domain. You

may need to reboot the domain or to

unload the IDN driver before you

retry the operation.

Reboot the domain, and retry the

command, if necessary.
statistics for the IDN are not
maintained.

WARNING: IDN: 136:
“property” property not
found, disabling IDN

WARNING: IDN: 137: SMR
size is 0, disabling IDN

The IDN driver failed to initialize
because it did not find the
specified OBP property.

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

Ensure that the SSP 3.2 software is on

the SSP.

Reset the idn-smr-size variable to

the appropriate value. The value

must be the same for all of the

domains in an IDN. Reboot the

domain after you reset the value of

the variable.

WARNING: IDN: 138: SMR
size (numberMB) is too
big (max = numberMB),
disabling IDN

The IDN driver failed to initialize
because the value of the OBP
variable idn-smr-size is too
large.

Reset the idn-smr-size variable to

the appropriate value. The value

must be the same for all of the

domains in an IDN. Reboot the

domain after you reset the value of

the variable.

12 Sun Enterprise 10000 IDN Error Messages • Januar y 2001

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

Error Description Recovery

WARNING: IDN: 139: OBP
region for SMR is 0
length

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

Reset the idn-smr-size variable to
the appropriate value. The value
must be the same for all of the
domains in an IDN. Reboot the
domain after you reset the value of
the variable.

WARNING: IDN: 140: OPB
region (bytes B) smaller
than requested size (bytes
B)

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

Ensure that the SSP 3.2 software is
running on the SSP, then reset the
idn-smr-size variable to the
appropriate value. The value must be
the same for all of the domains in an
IDN. Reboot the domain after you
reset the value of the variable.

WARNING: IDN: 141: OPB
region (PADDR) not on
(hex_number) boundary

NOTICE: IDN: 142: link
(domain domain_ID, cpu
CPUID) connected

TABLE2-3 IDN Domain-Specific Messages, 200 through 242

The SMR region allocated by OBP
is not on the appropriate memory
address boundary (64-Kbytes).

The domain has been linked with
domain domain_ID that hosts CPU
CPUID.

Ensure that the SSP 3.2 software is
running on the SSP, then reboot the
domain and retry the operation.

Notification only

Error Description Recovery

NOTICE: IDN: 200: link
(domain domain_ID, cpu
CPUID) disconnected

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

WARNING: IDN: 202:
(IDNOP) invalid time-out
value (seconds)

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

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

The domain has been unlinked

Notification only
with domain domain_ID that hosts
CPU CPUID.

During the IDN operation, the

Retry the IDN operation.
IDN driver specified an invalid ID
number for the CPU.

An invalid time out value was

Retry the IDN operation.
passed to the IDN operation
(IDNOP = LINK/UNLINK).

An invalid domain ID was passed

Retry the IDN operation.
to the IDN operation (IDNOP =
LINK/UNLINK).

The domain domain_ID was not in
the closed state when the IDN

Retry the IDN operation. If this error

persists, unlink the domain.
operation was executed.

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

TABLE2-3 IDN Domain-Specific Messages, 200 through 242 (Continued)

Error Description Recovery

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

The internal IDN function function
failed to open an IDN domain
control structure for managing an
IDN connection with domain

Wait a few minutes for the
connection to be resolved. If the
connection cannot be resolved, reboot
domain domain_ID.

domain_ID and CPU CPUID.

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

WARNING: IDN: 207:
local/remote master-id
conflict
(local_domain_ID.lmasterid =
domain_ID_a,

The local domain, domain_ID, has
the same vote ticket, hex_number,
as the domain, domain_ID,to
which it is trying to link. The vote
tickets are determined internally
and must be unique.

The local domain,local_domain_ID,
has a master ID, domain_ID_a, that
conflicts with the master ID,

domain_ID_b, of domain
remote_domain_ID.

Reboot the local domain, then retry
the operation. If the error occurs
again, reboot domaindomain_ID,then
retry the operation. If the error
persists, contact your Sun service
representative.

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

remote_domain_ID.rmasterid
= domain_ID_b)

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

This is an internal error. During
the selection of the master
domain, the IDN driver

Retry the operation. If the error
persists, reboot both of the domains,

then retry the operation.
encountered an unexpected case,
number.

WARNING: IDN: 209:
remote domain (id
domain_ID, cpu CPUID)
reporting master (id
master_domain_ID) without

During the IDN operation, the
remote domain, domain_ID,
returned the ID of the master to
the local domain, but not the CPU
ID.

Retry the operation. If this error

persists, reboot the remote domain.

cpuid
WARNING: IDN: 210:

failed to init MASTER
context

This is an internal error. The local
domain failed to initialize control
structures that the domain needs

Reboot the local domain, then retry

the operation.

to be a master domain.

WARNING: IDN: 211:
disconnect domain
domain_ID, unexpected
GSTATE (GSTATE)

PANIC: IDN: 212:
disconnect domain
domain_ID, bad GSTATE
(GSTATE)

During the disconnect operation
for domain domain_ID, the local
IDN was in an unexpected global
state, GSTATE.

During the disconnect operation
for domain domain_ID, the local
IDN was in an unexpected global
state, GSTATE.

Reboot the local domain, then retry

the operation.

Reboot the local domain, then retry

the operation.

14 Sun Enterprise 10000 IDN Error Messages • Januar y 2001

TABLE2-3 IDN Domain-Specific Messages, 200 through 242 (Continued)

Error Description Recovery

WARNING: IDN: 213: no
destination specified
(d=domain_ID,c=channel,
n=0xNE)

The local domain attempted to
send a data packet to an
inappropriate destination, domain
ID domain_ID, on channel channel

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

with the network ID NE.

WARNING: IDN: 214:
received message
(MSG[0xM_number]) from
self (domid domain_ID)

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

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

The local domain received an IDN
connection protocol message,

M_number, from domain
domain_ID with an invalid or stale

Reboot the local domain, then retry
the operation.

Retry the operation. If this error
persists, unlink the local domain
and/or remote domain, then relink
the local and/or remote domain.

cookie, cookie.

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

The local domain received an
invalid IDN connection protocol
message or acknowledgement
(M_number/A_number)from

Retry the operation. If this error
persists, unlink the local and/or
remote domain, then relink the local
and/or remote domain.

domain domain_ID.

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

WARNING: IDN: 218:
missing some required
config items from domain

domain_ID

The local domain received an
unexpected type, type,of
configuration message from the
remote domain, domain_ID.

During the connection operation,
the local domain did not receive
all of the configuration
information it expected from

Retry the operation. If this error
persists, unlink the local and/or
remote domain, then relink the local
and/or remote domain.

Retry the operation. If this error
persists, unlink the local and/or
remote domain, then relink the local
and/or remote domain.

domain domain_ID.

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

The MTU size, bytes, received
from domain domain_ID is not
compatible with the MTU size of
the local domain, bytes. The value

Reset the value of the
idn_smr_bufsize parameter on the
local domain or the remote domain

so that the values are the same.
of the IDN tunable parameter
idn_smr_bufsize must be the
same for all of the domains in an
IDN.

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

TABLE2-3 IDN Domain-Specific Messages, 200 through 242 (Continued)

Error Description Recovery

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

The local domain received an SMR
buffer size, bytes, from the remote
domain that is not compatible
with the SMR buffer size of the

Reset the value of the
idn_smr_bufsize parameter on the
local domain or the remote domain

so that the values are the same.
local domain. The value of the
IDN tunable parameter
idn_smr_bufsize must be the
same for all of the domains in an
IDN.

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

The local domain received an SMR
slab size, bytes, from domain
domain_ID that is not compatible
with the SMR slab size of the local

Reset the slab size parameters on the

local and/or remote domain.

domain. The value of the IDN
tunable parameters

idn_slab_bufcount and
idn_smr_bufsize must be the

same for all of the domains in an
IDN.

NOTICE: 222: no IDN
linkage found
(b=BMASK_a,i=BMASK_b)
upgrading unlink FTYPE ­> FORCE_HARD

The SSP requested that the local
domain be unlinked from the
remote domain with boardmask
FTYPE; however, the SSP was
unable to find a hardware link in
the IDN hardware register board
mask BMASK_b. The specified soft
force option, -f, was upgraded to
the hard force option, -F,to

No action is required. The soft force

option, -f, attempts to unlink all of

the specified domains in the standard

manner; however, if a time-out

condition occurs due to the presence

of an AWOL domain within the IDN,

the domain_unlink(1M) command

uses the -F option to remove the link,

forcing the domain to be unlinked.
unlink the domain.

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

The local domain received a value
of the idn_nwr_size variable
from the remote domain that does
not match the value of

Reset the value of the

idn_nwr_size variable for the

remote domain.

idn_nwr_size on the local
domain. The value of the
idn_nwr_size variable must be
the same for all of the domains in
the IDN.

16 Sun Enterprise 10000 IDN Error Messages • Januar y 2001

TABLE2-3 IDN Domain-Specific Messages, 200 through 242 (Continued)

Error Description Recovery

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

The local domain received a value
of the idn_max_nets variable
from the remote domain that does
not match the value of
idn_max_nets on the local

Reset the value of the
idn_max_nets variable for the
remote domain.

domain. The value of the
idn_max_nets variable must be
the same for all of the domains in
the IDN.

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

The local domain received a value
for the idn_mbox_per_net
variable from the remote domain
that does not match the value of
idn_mbox_per_net on the local

Reset the value of the
idn_mbox_per_net variable for the
remote domain.

domain. The value of the
idn_mbox_per_net variable
must be the same for all of the
domains in the IDN.

WARNING: IDN: 226:
remote domain domain_ID
CHECKSUM flag (number)
mismatches local
domain’s (number)

The local domain received a value
for the idn_checksum variable
from the remote domain that does
not match the value of
idn_checksum on the local

Reset the value of the
idn_checksum variable for the
remote domain.

domain. The value of the
idn_checksum variable must be
the same for all of the domains in
the IDN.

WARNING: IDN: 227:
missing some required
config items from domain

domain_ID

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

The local domain did not receive
all of the expected configuration
information from the remote
domain, domain_ID.

The size the SMR for the master
domain is larger than the virtual
space the local domain has
available for the SMR. The OBP
variable idn-smr-size must be

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

Reset the size of the idn-smr-size
variable for the local domain and/or
the remote domains so that the size is
the same. Reboot the domain(s), then

retry the link operation.
the same for all of the domains in
an IDN.

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

TABLE2-3 IDN Domain-Specific Messages, 200 through 242 (Continued)

Error Description Recovery

WARNING: IDN: 229:
remote domain domain_ID
boardset (BMASK)
conflicts with
MCADR(board number)
[MCADR]

The local domain received
conflicting information about the
MCADR register from domain
domain_ID. Board number is
reported to have a MCADR
setting, but it is not present in the

Reboot domain domain_ID, then retry
the operation.

physical board set BMASK of the
remote domain. MCADR
represents the actual MCADR
register value.

WARNING: IDN: 230:
remote domain domain_ID
reported number of
MCADRs (number)
mixmatches received
(number)

The local domain received
conflicting information about the
MCADRs in domain domain_ID.
The number of MCADRs specified
by domain number does not match
the number of MCADRs reported

Reboot domain domain_ID, then retry
the operation.

by that domain.

WARNING: IDN: 231:
domain domain_ID boardset
(BMASK) conflicts with
existing IDN boardset

The set of boards in the board
mask BMASK for domain
domain_ID overlap the existing
boards BMASK in the IDN.

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

(BMASK)
WARNING: IDN: 232:

domain domain_ID cpuset
(CPUSET) conflicts with
existing IDN cpuset

The set of CPUs in the CPU mask
CPUSET for domain domain_ID
overlap the existing CPUs
CPUSET in the IDN.

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

(CPUSET)
WARNING: IDN: 233:

domain domain_ID missing
cpu per memory boardset
(BMASK), cpu boardset
(BMASK)

Each system board in the domain
domain_ID must have at least one
CPU if it hosts memory. Board set
BMASK represents the board that
have memory, and board set

Ensure that the domain you want to
link has system boards that host at
least one CPU on each board that
hosts memory.

BMASK represents the boards that
have at least one CPU.

WARNING: IDN: 234:
failed to program
hardware for domain

domain_ID (boardset =
BMASK

The IDN driver was unable to
program the hardware for the
local domain to allow shared
memory access with domain
domain_ID, which contains the

Do not execute additional IDN
operations. When appropriate, halt
domain domain_ID, and run a full
diagnostic test by using the
hpost(1M) command.

board set BMASK.

18 Sun Enterprise 10000 IDN Error Messages • Januar y 2001

TABLE2-3 IDN Domain-Specific Messages, 200 through 242 (Continued)

Error Description Recovery

WARNING: IDN: 235:
[MBXTYPE] mailbox
(domain domain_ID, channel
channel) SMR CORRUPTED ­RELINK
IDN: 235: [MBXTYPE]
expected (cookie cookie,
cksum hex_number), actual
(cookie cookie, cksum
hex_number)
IDN: 235: [MBXTYPE]
activeptr (VADDR),
readyptr (VADDR)

The local domain detected that the
send and/or receive mailbox
MBXTYPE control area is
corrupted for domain domain_ID.
These messages indicate the
expected and actual values of the
cookie and checksum control
information. Depending on the
condition, an additional message
is displayed containing additional
control information that is used
for synchronization during data
transmissions (activeptr and

Unlink the master domain, then

relink it. If this error persists,

dismantle the entire IDN, then

reassemble it.

readyptr).

WARNING: IDN: 236:
domain (host) [id
domain_ID] not responding
to IDN_command [#number]
WARNING: IDN: 236:
domain [id domain_ID, cpu
CPUID] not responding to

The local domain attempted to
connect or disconnect domain host
or domain ID domain_ID with
CPU ID CPUID; however, the
domain is not responding. number
represents the number of detected
AWOL messages.

Unlink domain host, then retry the

link operation.

IDN_command [#number]
WARNING: IDN: 237:

invalid number (number)
of protocol servers

The specified number of IDN
protocol servers is invalid. The
value of the idn.conf(4) tunable
parameter

Reset the value of the

idn_protocol_nservers

parameter in the idn.conf(4) file to

an appropriate number.
idn_protocol_nservers must
be greater than zero (0).

WARNING: IDN: 238:
kmem_cache_create
(jobcache) failed

The kernel failed to create an
internal cache for allocating IDN
job control data structures.

Reboot the local domain, then retry

the link operation. If this error

persists, remove unused software

from the domain, and retry the link

operation.

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

channel

An invalid CPU ID, CPUID, was
specified for the local domain.
channel represents the network
interface for the IDN data server

Retry the operation with a valid CPU

ID for the local domain.

thread.

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

TABLE2-3 IDN Domain-Specific Messages, 200 through 242 (Continued)

Error Description Recovery

WARNING: IDN: 240:
(channel channel) SMR
CORRUPTED - RELINK
IDN: 240: (channel

channel) cookie (expected
cookie, actual cookie)

IDN: 240: (channel
channel) actv_flg
(expected hex_number,

The IDN data server for network
interface channel encountered
corrupted data in the SMR. The
expected and actual values for
control information that is used by
the data server are included
(cookie, actv_flg, and
ready_flg). Subsequent data
transmissions are likely to fail.

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

actual hex_number)
IDN: 240: (channel
channel) ready_flg
(expected hex_number,
actual hex_number)

WARNING: IDN: 241:
[operation] (domain

domain_ID, channel
channel_ID SMR CORRUPTED -

RELINK)

The IDN driver attempted to
transmit or receive data to or from
an IDN mailbox in the SMR;
however, the SMR was corrupted.
The operation is designated as

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

operation, send or recv,inthe
message. Future data
transmissions are likely to fail.

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

You cannot plumb more network
interfaces than the IDN driver is
configured to support.

Reset the idn.conf(4) tunable
idn_max_nets, then retry the
operation.

TABLE2-4 IDN Domain-Specific Messages, 300 through 307

Error Description Recovery

WARNING: IDN: 300: no
slab allocations without
a master

WARNING: IDN: 301:
(SMROP) unknown slab
state (slab_state) for
domain domain_ID

The slave domain attempted to
allocate a slab of memory without
a master domain being present.

This is an internal error, indicating
that a SMR slab was in an
unexpected state for domain ID
domain_ID, with respect to slab

If this error persists, unlink the local
domain, then relink it.

Unlink the local domain, then relink
it.

operation SMROP.

WARNING: IDN: 302: no
slab free without a
master

20 Sun Enterprise 10000 IDN Error Messages • Januar y 2001

The slave domain attempted to
free up a slab of memory without
the master domain being present.

If this error persists, unlink the local
domain, then relink it.

TABLE2-4 IDN Domain-Specific Messages, 300 through 307 (Continued)

Error Description Recovery

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

The local domain attempted to
allocate an SMR buffer with a
length greater than the length

Unlink the local domain, then relink

it.

supported by the IDN
configuration.

WARNING: IDN: 304:
buffer (VADDR) from
domain domain_ID not on a
hex_number boundary

An SMR buffer at kernel virtual
address VADDR was received
from domain ID domain_ID;
however,it was not aligned on the

Unlink the local domain and/or

domain domain_ID, then relink the

local domain and/or domain

domain_ID.
expected boundary hex_number (in
bytes).

WARNING: IDN: 305:
buffer length (bytes) from
domain domain_ID greater
than IDN_DATA_SIZE (bytes)

An SMR buffer of length bytes was
received from domain ID
domain_ID; however, the length
was greater than the length that is

Unlink the local domain and/or

domain domain_ID, then relink the

local domain and/or domain

domain_ID.
supported by the local domain
(bytes in bytes).

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

domain_ID

The local domain received a
request for a domain ID,
domain_ID, that was not in the
expected range of valid domain

If this error persists, unlink the local

domain, then relink it.

IDs (that is, 0 to 15).

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

The SMR subsystem received a
request for a domain ID
domain_ID that was not in the

If this error persists, unlink the local

domain, then relink it.

expected range of valid domain
IDs (that is, 0 to 15).

TABLE2-5 IDN Domain-Specific Messages, 400 through 450

Error Description Recovery

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

The MAC header in the SMR data
packet contained bad data.

Unlink the local domain, then relink

it. If this error persists, dismantle the

IDN, and reassemble it.

act hex_number)
IDN: 450: idnX:

kstat_create failed

Unable to create the kstat
structures. No per-instance kernel
statistics will be maintained for

Reboot the local domain if you need

the per-instance kernel statistics to be

maintained.
the IDN.

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

TABLE2-6 IDN Domain-Specific Messages, 500 through 516

Error Description Recovery

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

While programming the SMR, the
local domain failed to write the
(lsb/msb) portion of the shared
memory base-address-register

Do not perform IDN operations.
When appropriate, halt the local
domain, and run a full diagnostic test
by using the hpost(1M) command.

with value hex_number.

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

While programming access to the
SMR, the local domain failed to
write the (lsb/msb) portion of the
shared memory limit-address-

Do not perform IDN operations.
When appropriate, halt the local
domain, and run a full diagnostic test
by using the hpost(1M) command.

register with value hex_number.

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

While programming access to the
SMR, the local domain failed to
write to the CIC (Coherency
Interface Controller) prep buffer

Do not perform IDN operations.
When appropriate, halt the local
domain, and run a full diagnostic test
by using the hpost(1M) command.

with the data hex_number.

WARNING: IDN: 503:
(PCPROG) failed to
update PC madr (expected
0xXXX, actual hex_number)

While programming access to the
SMR during the PCPROG
(invalidate or validate) phase, the
local domain failed to write a

Do not perform IDN operations.
When appropriate, halt the local
domain, and run a full diagnostic test

by using the hpost(1M) command.
memory addressdecodingregister
(MADR) entry to the port
controller (PC).

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

While programming access to the
SMR during the PCPROG
(invalidate or validate) phase, the
local domain failed to write a
memory addressdecodingregister

Do not perform IDN operations.

When appropriate, halt the local

domain, and run a full diagnostic test

by using the hpost(1M) command.

(MADR) entry of the I/O port
controller (IOPC).

WARNING: IDN: 505: board
number mising any valid
PCs

Board number does not contain
valid port controllers (PCs).

Do not perform IDN operations.

When appropriate, halt the local

domain to ensure that board XX

hosts the appropriate hardware. You

may need to run a full diagnostic test

by using the hpost(1M) command.

WARNING: IDN: 506: cic
sm_mask is not writable

The CIC has been programmed by
POST to not let the operating
system level software to
manipulate the shared-memory

Ensure that the SSP 3.2 software is

running on the SSP. Run a full

diagnostic test on the board by using

the hpost(1M) command.
mask register.

22 Sun Enterprise 10000 IDN Error Messages • Januar y 2001

TABLE2-6 IDN Domain-Specific Messages, 500 through 516 (Continued)

Error Description Recovery

WARNING: IDN: 507:
failed to map-in
post2obp structure

The local domain did not
successfully map in the POST2OBP
data structure to the address space

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

of the kernel.

WARNING: IDN: 508:
post2obp checksum
invalid

The POST2OBP data structure that
was passed from POST to OBP
appeared invalid. The expected

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

checksum value did not match the
value that is reported by the data
structure.

WARNING: IDN: 509: cpu
CPUID never responded to
CIC update

While programming the SMR for
access during the parallel update
of the CIC registers phase, CPU

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

CPUID did not respond to the
update request.

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

The local domain failed to update
all of its shared memory registers.
The specific failure occurred on
system board number, interconnect

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

bus 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 update
operation was encountered during
the update of the shared memory

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

registers 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 PC
memory address decoding
registers on board number with
respect to the remote board,

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

remote_number. The hex_number
value represents the targeted
register contents.

WARNING: IDN: 513: sm­mask error (expected =

hex_number, actual =
hex_number)

WARNING: IDN: 514: sm­base error (expected =

hex_number, actual =
hex_number)

The local domain encountered
inconsistent or unexpected values
in the shared memory mask of the
CIC.

The local domain encountered
inconsistent or unexpected values
in the shared memory base
register of the CIC.

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

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

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

TABLE2-6 IDN Domain-Specific Messages, 500 through 516 (Continued)

Error Description Recovery

WARNING: IDN: 515: sm­limit error (expected =

hex_number, actual =
hex_number)

WARNING: IDN: 516: (local/
remote) board number has

memory, but no cpus ­CPU-PER-BOARD REQUIRED

The local domain encountered
inconsistent or unexpected values
in the shared memory limit
register of the CIC.

The local domain detected that a
local or remote, local/remote,
system board, number, contains
memory, but no CPUs. In an IDN,

Halt the local domain, then reboot it.

After it reboots, relink it to the IDN.

Halt the local or remote domain, then

check its hardware configuration. If it

does not host a CPU, place it in the

blacklist, then relink the domain.
each system board that hosts
memory must also host at least
one CPU.

24 Sun Enterprise 10000 IDN Error Messages • Januar y 2001