TABLE 3-1Error Messages for the Sun StorEdge Availability Suite 3.2 Software (Continued)

Error Message

From Meaning

unable to determine hostname: <host>

unable to determine IP addresses for either host <phost> or host <shost>

unable to determine IP addresses for hosts <host1>, <host2>

RM

Could not determine the host name of the system.

RM

The IP address for either the primary host or the

 

secondary host could not be determined.

RM

The IP addresses for the host names specified for the

 

primary or secondary hosts could not be determined.

 

Verify that the host names are in the /etc/hosts file.

unable to determine local hostname PITC

iiadm needed to find out the name of the host it is

 

running on, but was unable to do so.

unable to determine network information for <host>

unable to determin the current Solaris release: <error>

unable to find disk service, <ctag>: <errno>

Unable to find disk service:%s

Unable to find <group> in configuration storage

Unable to find <shost>:<svol> in configuration storage

unable to find SNDR set <shost>:<svol>: in config

Unable to fork

unable to get maxsets value from kernel

unable to get set status before reconfig operation

Unable to initialize the kernel thread set

RM

Network information for the secondary host could not

 

be determined. Verify the settings in the

 

/etc/nsswitch.conf file.

RM

Look at rdc_check_release();

RM

SunCluster could not find the specified disk service.

PITC

iiadm could not determine whether a cluster device

 

group is active on the current host.

RM

Could not find remote mirror group in configuration

 

database while trying to do a diskq operation.

RM

Could not find remote mirror set in configuration

 

database while trying to do a diskq operation.

RM

The remote mirror set is not configured while trying to

 

set autosync, for one of the following reasons:

 

• The set could not be found in the configuration.

 

• The set is not configured in the configuration

 

database.

 

Verify that the set is entered properly and matches a

 

set returned by the sndradm -icommand.

PITC

iiadm ran out of process space.

RM

The remote mirror software failed to read the

 

sndr_max_sets value from the

 

/usr/kernel/drv/rdc.conf file.

RM

The remote mirror software could not get the kernel

 

configuration.

Kernel

The remote mirror software could not initialize a

 

kernel thread. Verify that the system is not running

 

low on memory.

38 Sun StorEdge Availability Suite 3.2 Software Troubleshooting Guide • December 2003

Page 48
Image 48
Sun Microsystems 3.2 Could not determine the host name of the system, IP address for either the primary host or, Database

3.2 specifications

Sun Microsystems 3.2, often referred to as SunOS 3.2, was a notable release of the Sun operating system that emerged during the rapidly evolving landscape of computer technology in the early 1980s. This operating platform was designed specifically for Sun Workstations, utilizing the robust hardware architecture developed by Sun Microsystems. The introduction of SunOS 3.2 marked a significant step forward in the development of UNIX-like operating systems optimized for entrepreneurship and scientific applications.

One of the main features of SunOS 3.2 was its adherence to the Berkeley Software Distribution (BSD) model, which allowed for advanced networking capabilities, enhanced performance, and efficient resource management. BSD's influence provided SunOS 3.2 with TCP/IP networking protocols, allowing users to connect to other devices seamlessly and manage network resources easily. This feature was crucial during a time when networking was becoming increasingly vital for organizations.

The system's support for virtual memory was another innovative characteristic. SunOS 3.2 utilized demand paging, which allowed programs to use more memory than was physically installed on their machines, significantly improving multitasking and overall system responsiveness. This capability was particularly advantageous for enterprises that relied on large-scale computations and data analysis.

SunOS 3.2 also introduced support for the Sun Window System, which meant users could utilize graphical user interfaces for interacting with applications, moving away from purely text-based command interfaces. This transition paved the way for more intuitive user experiences in the realm of computing, making powerful UNIX capabilities more accessible.

The inclusion of software utilities such as the C shell (csh) and a variety of development tools further strengthened SunOS 3.2’s position as a suitable platform for developers. The system provided robust development environments for programming in languages like C and assembly, catering to custom application requirements across different industries.

Lastly, security features were integrated into SunOS 3.2 to safeguard sensitive data and enhance system integrity. Permission settings and user authentication mechanisms were refined, allowing organizations to securely manage their computing resources.

In summary, SunOS 3.2 represented a landmark evolution in operating systems, showcasing a blend of advanced networking, memory management, graphical user interface, development tools, and security—elements that defined a generation of computing within the high-performance ecosystem of Sun Microsystems.