test

Netra j - Release 2.0 Product Notes

Netra j 2.0 Administrator's Guide Updates

This section describes updates to the Netra j 2.0 Administrator's Guide.

DNS Primary Server Administration

Table 1-6 on page 44 should be updated with the following information:

Table 1-6 DNS Primary Server Administration

DNS Primary Server Information 

Description 

Primary Domain Name 

The name of the primary domain. The primary domain name is assumed to be fully qualified (do not use a trailing period). Example: elmo 129.144.79.1

Domains/ DNS Servers 

The domains served by the corresponding DNS name servers. The domain must be a subdomain of the primary domain, unless it is a fully qualified domain name. The host name of the name server must be within this domain, unless it is a fully qualified host name. All DNS servers are treated as authoritative for the listed domain. If a subdomain is entered, authority for that domain is delegated to the listed server. This field must always contain a record for this name server. Enter the name of this primary domain together with the host name of this server. A trailing period is required for the domain name.  

DNS Primary Domains

The domain name should be followed by a trailing dot as shown in the following example: 

mydomain.com.

Adding Records for Name Servers

When adding records for name servers, the first record must contain at least one entry specifying that this server is a name server for the domain. You must also create a second record for the name server of the subdomain within the primary domain.

Example of DNS Primary Server

The example of the DNS Primary Server described on page 44 should be replaced with the following information:

For example, assume that a master database for the domain comedy.tv.net is to be set up. In the Primary Domain Name field, specify: 

comedy.tv.net

In the Host Names/Host Addresses field, type a list of those hosts whose presence are to be broadcast to any machine that can connect to this DNS server. For this example, type ren and stimpy, and for a host called homer located in the DNS subdomain black.comedy.tv.net, type homer.black. 

ren							129.1.1.2
stimpy							129.1.1.3
homer.black							129.2.1.2

The Internet community uses conventional names for hosts that provide certain types of services, in order to make them easy to locate. For instance, the WWW server for a domain is usually known as www.domain, and an anonymous FTP server is typically called ftp.domain. On comedy.tv.net, ren is an FTP and WWW server, while stimpy is a name server. Standard aliases for these machines are added into the Host Aliases/Host Names field. For example: 

www							ren
ftp							ren
ns							stimpy

stimpy is going to handle mail sent to comedy.tv.net, so an MX record needs to be created: 

comedy.tv.net.						5 		stimpy

Finally, records are added for name servers. This field must contain at least one entry specifying that this server is a name server for the domain. Add a second record homer.black, which is the name server for a subdomain of this domain. If a domain contains subdomains, the DNS primary domain server for the domain must know a DNS server for the subdomain. comedy.tv.net has a subdomain called black, whose DNS primary domain server is called homer. homer resides on that domain, so in order for the Netra DNS server to reach homer when it needs to request name services for that domain, it has to know homer's IP address. That is why homer.black was added to the list of known hosts.

Setting JavaOS Properties

The name of the JavaStation serial port is now SerialA. This change affects the setting of the JavaOS property javaos.printservice.local.params.serial-port described under "Printing Properties."

javaos. printservice. local.params. serial-port

null 

The port portion of this property is the name of a serial port (which is always SerialA for the JavaStation). This property sets the communications parameters for the serial port. The syntax of the parameters is baud_rate:data_bits:stop_bit: parity: flow_control. For example: -djavaos.printservice.local.params. serial-SerialA=57600:8:1:none:hh

Valid values for each parameter are as follows: 

  • baud_rate: 1200, 2400, 4800, 9600, 19200, 38400, 57600, 115200

  • data_bits: 5, 6, 7, 8

  • stop_bits: 1, 1.5, 2

  • parity: none, odd, even

  • flow_control: none, {s,h}{s,h} You can disable flow control by specifying none. Otherwise, specify an {input}{output} pair by selecting from Xon/Xoff (s) or RTS/CTS (h) for input and output.

The description of the property javaos.homedir under "General Properties" should be changed to the following:

javaos.homedir

null 

This property specifies the NFS path JavaOS should mount if NIS is not used to find the path based on the user name. The NFS path is specified as hostname:/path.

This property is most often used to determine the directory to use for the properties file that is read by HotJava at startup. If the javaos.login property is set to false, javaos.homedir is not used.

JavaStation User Setup Forms

Information for PPP/modem described in the JavaStation User Setup forms available in Appendix C and from the Netra j Administration Interface should be updated with the following information:

Troubleshooting

TABLE D-5 Additional Error Messages and Known Problems on page 195 should be deleted.

Troubleshooting JavaOS

Add the following section, "Capturing Log Files"," to the Troubleshooting appendix in the Netra j 2.0 Administrator's Guide.

Capturing Log Files

In some cases, if JavaOS fails, it may broadcast an SNMP trap. The trap can be received by any SNMP manager listening on the (sub)net. There is a simple SNMP trap receiver supplied with JavaOS state information in a log file.

To Capture Log Files for JavaOS

  1. Run the following command on any machine in the (sub)net: 

    # /opt/SUNWjsos/bin/snmptrapd -x /opt/SUNWjsos/bin/logdumper&

If failures do occur, they are saved in the /tmp directory of the server machine with the following unique file name: 

/tmp/javaos.log.<IP address of failed client>@<time
in seconds since January 1, 1970>

You can browse the log file to determine errors that may have caused a failure. You may also want to add the snmptrapd command to the Solaris initialization and booting hierarchy. See the README files in /etc/init.d and /etc/rc2.d for details.

Note -

Not all JavaStation client failures will result in a log file creation on the server machine.