NFS is a relatively uncomplicated functionality of any Unix system. However, from time to time you are bound to run in the “permission denied” error while trying to NFS-mount a filesystem. Everything seems to be shared correctly and, yet, the “permission denied” error persists. Here are a few things you may want to do to resolve the problem.

First, the correct syntax for sharing and mounting filesystems. Solaris 8 is used in this example.

1. Assume the Primary Administrator role, or become superuser.

   The Primary Administrator role includes the Primary Administrator profile. To create the role and assign the role to a user, see Chapter 2, Working With the Solaris Management Console (Tasks), in System Administration Guide: Basic Administration.

2. Determine the types of interfaces in use on your system.

Setting up vlan tagging on an interface in solaris 10 is as simple as plumbing an interface.
Eg. to setup the e1000g0 interface for the vlan with id ‘2′, execute the following command.

# ifconfig e1000g2000 plumb

The interface name is the concatenation of the interface name + vlan id * 100 + interface id

e1000g0 vlan 2 = e1000g + 200 + 0 = e1000g2000

You’ll probably want to make this persistant across reboots as well, so you’ll need to create the /etc/hostname.if file

Been getting a lot of questions about directory listing in Sun Java System Web Server 7.0

I have setup a Sun Java System Web Sever 7.0. I am not able see directory contents. I get a popup saying "Authentication Required". Under "Content Handling"->"General"->"Directory Listing", I tried setting "Listing Type" to 'Fancy' & 'Simple'.  But that did not help (I saved and re-deployed the server instance).

Here is the solution. Check in obj.conf configuration file if "index-common" service SAF is present:

If you have three old URIs for which you wish to return 301 redirects back to the client like the following:

http://xyz.com/page.jsp?type=a
http://xyz.com/page.jsp?type=b
http://xyz.com/page.jsp

And you would like them to respectively send redirects to these URIs:

Edit the obj.conf file and add

Output fn=”set-variable” error=”301″ noaction=”true”

after the line.

Now, any redirects you do in your obj.conf will be reported as 301’s.

A couple of other options you can use in the obj.conf:

Lets say you own domain aha.org, then one day your site name was published in USA Today as heart.org. Register heart.org and update the DNS to point to your aha.org web server.

Now you could create a new VS for heart.org but why have a second configuration to manage.

Work Around (webconsole hangs): 

Do the following after upgrade:

#  /usr/share/webconsole/private/bin/wcremove -i console
 
Stopping console process...
 
Removing console instance configuration files...
# ls //var/webconsole/domains/console/conf
//var/webconsole/domains/console/conf: No such file or directory
# svcadm clear system/webconsole:console
# smcwebserver start
Console service is already running
# svcs -vx

Article Contents

This article is presented in the following four parts:

• Part 1 -- Installation and Configuration
• Part 2 -- Client Configurations for the Solaris OS
• Part 3 -- Client Configurations for Red Hat Linux and AIX
• Part 4 -- Post-Configuration Tasks

Note: When you run the commands shown in the procedures of this article, replace COMPANY with a value that is appropriate for your environment.