1.NFS client is not able to access NFS server? Troubleshooting steps?
@.Verify the connectivity between NFS server & NFS client
@.Check the NFS ports are open in network side.
@.Verify the shares are properly exported to NFS clients
2.If on jumpstart client, boot command "boot net install" doesn't work, what could be the possible reasons?
@.Check the network connectivity using watch-net-all from OK prompt.
@.Verify the MAC address in Jumpstart server.
3.What is /etc/system file gets corrupted? How will system bootup?
If you modify your /etc/system file in Solaris and screw it up or it gets corrupt, when you try to reboot, the server will no longer startup.
To recover from this problem:
1) As the server starts booting, press Stop+A (at the same time)
2) At OK> prompt, type "boot -as"
3) Solaris will now go into an interactive boot and will ask you several things.
4) Answer using all the defaults until it asks for your system file.
5) Either specify the name of a backup system file (if you have one) OR type "/dev/null"
6) It will allow the system to boot with a vanilla kernel so that you can fix the broken /etc/system
7) Fix the /etc/system file
4.What is mean by paging & server average time.
If a disk shows consistently high reads/writes along with , the percentage busy (%b) of the disks is greater than 5 percent, and the average service time (svc_t) is greater than 30 milliseconds, then one of the following action needs to be taken
@.If the LUNS average service time is more than 30 ,then you need to check with SAN team .They will help you with issue. May be they will spread the LUNS to multiple physical disks in the back end.
@.Verify the connectivity between NFS server & NFS client
@.Check the NFS ports are open in network side.
@.Verify the shares are properly exported to NFS clients
2.If on jumpstart client, boot command "boot net install" doesn't work, what could be the possible reasons?
@.Check the network connectivity using watch-net-all from OK prompt.
@.Verify the MAC address in Jumpstart server.
3.What is /etc/system file gets corrupted? How will system bootup?
If you modify your /etc/system file in Solaris and screw it up or it gets corrupt, when you try to reboot, the server will no longer startup.
To recover from this problem:
1) As the server starts booting, press Stop+A (at the same time)
2) At OK> prompt, type "boot -as"
3) Solaris will now go into an interactive boot and will ask you several things.
4) Answer using all the defaults until it asks for your system file.
5) Either specify the name of a backup system file (if you have one) OR type "/dev/null"
6) It will allow the system to boot with a vanilla kernel so that you can fix the broken /etc/system
7) Fix the /etc/system file
If a disk shows consistently high reads/writes along with , the percentage busy (%b) of the disks is greater than 5 percent, and the average service time (svc_t) is greater than 30 milliseconds, then one of the following action needs to be taken
@.If the LUNS average service time is more than 30 ,then you need to check with SAN team .They will help you with issue. May be they will spread the LUNS to multiple physical disks in the back end.
No comments:
Post a Comment