sun.com | docs.sun.com | How To Buy | My Sun | Worldwide Sites |  |

| Previous Contents Index Next
2. ### Debugging Diskless Nodes With the `snoop` Tool When debugging diskless nodes, use the `snoop` command, as follows. #### To Examine a Diskless Node From the Master Node Using `snoop` Log in to the diskless node that you want to examine. Find the IP address of this node:
       % ifconfig -a
4. The `ifconfig` command returns the IP address, the interface type, and the Ethernet address. Log in to the master node. From a console window, run:
       % snoop -d NIC0 ether diskless-node-NIC0-Ethernet-address
5. The `snoop` command captures packets from the network and displays their contents. From another console window, run:
       % snoop -d NIC1 ether diskless-node-NIC1-Ethernet-address
To exit the `snoop` tool, press Control-C. ## Using Foundation Services Configuration Files in the Cluster Environment The files created during initial cluster configuration can be used during administration to determine the state of the cluster. By default the configuration files are in the `/etc/opt/SUNWcgha/` directory. The following table lists the files created during initial cluster configuration. Table 1-3 Foundation Services Files Created During Initial Cluster Configuration
Configuration File | Description
--- | ---
`cluster_nodes_table` | Contains a list of the peer nodes in a cluster. There is a copy of the file on each master-eligible node. For information, see the `cluster_nodes_table`(4) man page.
`nhfs.conf` | Contains configuration information for the individual Foundation Services. There is a copy of this file on each peer node. For information, see the `nhfs.conf`(4) man page.
`nma.notifs.txt` | Defines types and targets for the trap notifications of the Node Management Agent (NMA) SNMP. For information, see the `nma.notifs.txt`(4) man page.
`nma.params.txt` | Defines the communication, implementation and accessibility configuration of SNMP in the NMA. For information, see the `nma.params.txt`(4) man page.
`nma.properties` | Lists the properties of the NMA on a node. There is a copy of this file on each peer node. For information, see the `nma.properties`(4) man page.
`nma.targets.txt` | Defines the targets to which the NMA sends SNMP traps. For information, see the `nma.targets.txt`(4) man page.
`nma.security` | Configures SNMP security for the NMA. For information, see the `nma.security`(4) man page.
When you reconfigure a cluster, you might need to modify configuration files. Refer to the man page of a configuration file for information about how to change the file. ## Using Solaris Configuration Files in the Cluster Environment This section describes the Solaris configuration files that can help you determine the current configuration of the cluster. For information about how and when to modify a Solaris configuration file, consult the man page for the file and the Solaris documentation set. The following table lists the Solaris configuration files that can be edited during cluster configuration. Table 1-4 Solaris Files Used With the Foundation Services
Configuration File | Description
--- | ---
`/etc/bootparams` | A database of boot parameters. For information, see `bootparams`(4).
`/etc/coreadm.conf` | Parameters for system core file configuration.
`/etc/dfs/dfstab` | Commands for sharing resources across a cluster. Commands for partitions mirrored by Reliable NFS are not located in this file. For information, see `dfstab`(4).
`/etc/hostname.`interface-name`` | Configuration of each network interface on a node. The file contains the host name of the interface specified by interface-name. If you create a network interface, you must create a `/etc/hostname.`interface-name`` file for that interface. For information about network interface configuration, see Examining the Network Configuration Files.
`/etc/hosts` | A local database of host names. For information, see the `hosts`(4) man page. For information about network interface configuration files, see Examining the Network Configuration Files.
`/etc/inet/inetd.conf` | The list of servers that `inetd` invokes when it receives an internet request over a socket. For information, see the `inetd.conf`(4) man page.
`/etc/inittab` | The process dispatching control by the `init` command. This file contains the `rc2` and `rc3` entries. For information, see the `inittab`(4) man page. For information about the Daemon Monitor, see the `nhpmd`(1M) man page.
`/etc/netmasks` | A list of the network masks used to implement IP subnetting and their associated IP network numbers. For information, see the `netmasks`(4) man page. For information about network configuration, see Chapter 4, Examining the Cluster Networking Configuration.
`/etc/nodename` | The local source for the system name. For information, see the `nodename`(4) man page. For information about network interface configuration files, see Examining the Network Configuration Files.
`/etc/notrouter` | A file to specify that a node does not act as a router. This file is used to protect against route mismatch. This file must be configured on each peer node to ensure that the node is not routable.
`/etc/nsswitch.conf` | A configuration file for the name service that provides the sources of database information and their lookup order. For information, see the `nsswitch.conf`(4) man page. For information about using the naming services, see Using the Naming Services.
`/etc/rc2` | A script that executes commands when the system is changing to init state 2. A modified version of this script is used by the Daemon Monitor. For information about the Daemon Monitor, see the `nhpmd`(1M) man page.
`/etc/rc3` | A script that executes commands when the system is changing to init state 3. A modified version of this script is used by the Daemon Monitor. For information about the Daemon Monitor, see the `nhpmd`(1M) man page.
`/etc/services` | A list of the services and aliases available through the Internet. The `/etc/services` file can be changed to modify the Foundation Services ports if, for example, an application is already using the ports configured by default at startup. For information, see the `services`(4) man page. For information about prioritizing the Foundation Services, see Using the Naming Services.
`/etc/syslog.conf` | A file used by the system log daemon, `syslogd`, to forward a system message to the appropriate log files and users. For information, see the `syslog.conf`(4) man page. For information about configuring system log files, see Chapter 2, Accessing and Maintaining Log Files.
`/etc/system` | A file that customizes the operation of the operating system kernel. You should not have to change the `/etc/system` file. If you do change the `/etc/system` file, you must reboot the node for the changes to take effect.
`/etc/vfstab` | A table of file system defaults. For information, see `vfstab`(4).
`.profile` | A file to set up an environment for a user at login time. For information about how to use this file, see the `profile`(4) man page. For examples of the configuration of the `.profile` file, see To Add the Foundation Services Tools to Your Path and To Set `NLSPATH` Permanently.
`.rhosts` | A list of trusted hosts and users. The `.rhosts` file specifies remote trusted hosts and users. Modify this file to change remote access authorization between peer nodes. For information, see `rhosts`(4).
Previous Contents Index Next

Copyright 1994-2004 Sun Microsystems