Testing with ifconfig

Use the ifconfig command to make sure that the network interface is configured and running correctly. This example output shows all the interfaces that are configured and running:

#ifconfig -a

ba0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 9180 index 1 inet 192.9.201.10 netmask ffffff00 broadcast 192.2.201.255 ether 8:0:20:af:8e:d0

lo0: flags=1000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 8232 index 2 inet 127.0.0.1 netmask ff000000

hme0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 3 inet 192.9.201.124 netmask ffffff00 broadcast 192.9.200.255 ether 8:0:20:8d:f7:2c

lo0: flags=2000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv6> mtu 8252 index 2 inet6 ::1/128

hme0: flags=2000841<UP,RUNNING,MULTICAST,IPv6> mtu 1500 index 3 ether 8:0:20:8d:f7:2c

inet6 fe80::a00:20ff:fe8d:f72c/10

Testing with ping

Use the ping command to verify that the network interfaces can communicate and that IPv4 or IPv6 addressing is being used. Issue this command from the primary host and secondary host to make sure communication is bidirectional. This command also determines whether both hosts are using the same IP protocol (IPv4 or IPv6).

This example checks the communication on host second.atm.:

#ping -s second.atm

PING second.atm: 56 data

bytes

64

bytes from second.atm

(192.9.201.2): icmp_seq=0. time=1. ms

64

bytes from second.atm

(192.9.201.2): icmp_seq=1. time=0. ms

64

bytes

from

second.atm

(192.9.201.2): icmp_seq=2. time=0. ms

64

bytes

from

second.atm

(192.9.201.2): icmp_seq=3. time=0. ms

Testing with snoop and atmsnoop

Use the snoop or atmsnoop utility to make sure that the software is sending and receiving data during a copy or update operation.

Chapter 2 Remote Mirror Software Troubleshooting Tips 11

Page 21
Image 21
Sun Microsystems 3.2 manual Testing with ifconfig

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.