11.10.2005

NetApp Filer :: Troubleshooting Cheat Sheet

---------- ---------- ----------
Packet Tracing on a NetApp Filer ::

Login to the CLI (console), and follow these steps -

1. pktt start e0 -b 1m -i 192.168.136.130
2. pktt status e0 ( should show some traces )
3. pktt dump e0 -f/mytrace.trc
4. pktt stop all
5. File is created at C$ of filer
6. Make a CIFS connection to the Filer from a Windows box, and point to \\\C$
7. Obtain the file "mytrace.trc"
8. Open "mytrace.trc" with either ethereal or packetizer

Be sure that step #4 is done, or pktt will fill up the C$ vol.


---------- ---------- ----------
NFS Troubleshooting ::


Wcc -u ---------- UNIX-type Credentials

>exportfs -c host pathname ro|rw|root #Checks access cache for host permission
>exportfs -s pathname #Verifies the path to which a wol is exported
>exportfs -f #Flush cache access entries and reload
>exportfs -r #Ensures only persistent exports are loaded


NFS error 70 - stale file handle --

>vol read_fsid

# mount --- Will display what protocol being used for mounting ( in a unix host )
# mount -o tcp < >


Out of inodes --

1. Check % used of inodes by:
Filer> df -i
2. To increase:
Filer> maxfiles < vol name >

> df -i /vol/vol0
OR
>maxfiles #This will display the number of usable inodes on the vol

To change:
>maxfiles


---------- ---------- ----------
CIFS Troubleshooting ::


Wcc -s domain\name -----windows - match with /etc/lclgroups.cfg file - ANY changes here will require a reboot
Wcc -u username --------------unix
Cifs domaininfo - Provides the Filer DNS entry
Rdfile /etc/rc --------- Will have further DNS info

Options wafl
Should see unix Pcuser

/etc/usermap
/etc/passwd these two files are read at the first time


Cannot Ping DNS server --

A.
1. Enter the host address in DNS
2. Make sure that there is no deny/untrusted entry in /etc/rc file
3. Check the filer view - > Networking -> DNS entry
4. If the qtree is created and shared for CIFS access, make sure that the qtree settings are correct, otherwise we may get an "access denied" error.

B.
1. Check DNS servers, must point to itself and must have at least "4,5" services - AD

C.
1. Check where the Filer is currently pointing to (DNS)
Filer> priv set diag
Filer> registry walk auth

If required to rerun cifs setup, the old registry can be deleted, as -

Filer> registry deltree auth

D.
Net view \\filername should show all shares from the Windows side and cifs shares should show from the Filer side

But, when the share is accessed from a Windows machine, we may get "No Network Provider Present". Ping works, drives are OK - can access. But, the cifs shares may not work. In the Filer side we see ‘Called name not present ( 0x82)". Cifs resetdc also gives the same message.

Check :
1. If the Filer and the Windows DC are rebooted at the same time (due to, say, a power failure) failure this is seen. The Filer needs to boot first, and then DC
2. Make sure that there are no virus-scan related activities running on that host. A Virus scan on a Windows host or Filer can also make this happen.


Trust Relationships - Multi-domain --

When a trust is newly established, "No Logon Server Available" may popup upon accessing the Filer.

Cifs resetdc #This makes it work. I don't know why.


Disable WINS on interface e0 (if the site requirement is to go by DNS only) --

Filer> ifconfig e0 -WINS (the Filer will now no longer communicate with the WINS server)


---------- ---------- ----------
Common CIFS Errors ::

LSAOpenPolicy2 : Exception rpc_s_assoc_grp_max exceeded --

Veritas Backup Exec 9.1 : mycomputer -> shares -> sessions shows Veritas Backup Exec Administrative account connections for every share in filer. One connection per share and it grows each and every day as well as stays there each and everyday. This must be wiped out.

Clock Skew --
Time Not synchronizing/+5/-5 min skewed ahead

Options timed
Timed.enable on
Timed.servers ntp2.usno.navy.mil:
Rdate

The above sets the Filer to Timed.servers ntp2.usno.navy.mil. The DC clock for a CIFS domain must be within 5 minutes (+/-) of the NetApp Filer.


---------- ---------- ----------
ONTAP upgrade process ::


1. Download the software to a Windows client
2. Create a cifs shares to /etc
3. Double click thedownloaded .exe file
4. Extract the files on the top of /etc
5. RUN the downloaded command

No comments: