If you dont hv the package, please download the latest package from My Oracle Support:

1. login to support.oracle.com
2. click on “Patches & Updates” in the top menu
3. in the search window (located on the right) click “Product or Family (Advanced)”
4. in the updated search window type “Sun Remote” in the “Product” box, then select “Sun Remote System Control”
5. Click the “Release” box (which says “Select up to 10″, in that box click “Sun Remote System Control” and then select the version “Sun Remote System Control 2.2.3″.
6. In the new window you can now download RSC 2.2.3 (called p10264451_223.zip) by marking it and clicking “download”.

[reset RSC password:

Login with root privilege, install the package, then run rscadm command.

Prefix >> #/usr/platform/<platform>/rsc/rscadm userpassword <username>

[example for v890:
# /usr/platform/SUNW,Sun-Fire-V890/rsc/rscadm userpassword admin
Password:
Re-enter Password:

You can also reset the whole configuration by running “rsc-config” command.

Clear fmadm log, Example :
———————————-
For each fault listed in the ‘fmadm faulty’ run:
# fmadm repair <uuid>   (OR if the components are listed instead, e.g.:)
# fmadm repair 568a9180-7308-4535-92e6-a7c17ef1bfef

[Clear ereports and resource cache:
# cd /var/fm/fmd
# rm e* f* c*/eft/* r*/*

[Clearing out FMA files with no reboot needed:
svcadm disable -s svc:/system/fmd:default
cd /var/fm/fmd
find /var/fm/fmd -type f -exec ls {} \;
find /var/fm/fmd -type f -exec rm {} \;
svcadm enable svc:/system/fmd:default

[Reset the fmd serd modules:
# fmadm reset cpumem-diagnosis
# fmadm reset cpumem-retire
# fmadm reset eft
# fmadm reset io-retire

The disk has intermittently undetected from host, tried to upgrade the OBP firmware from 4.13 to 4.30, found the amber light with below error messages:

“Host Power-On Failed: System Power OK, Open Boot not responding”

————–
sc> poweron
SC Alert: Host System has Reset
sc>
SC Alert: Host Power-On Failed: System Power OK, Open Boot not responding
sc>
SC Alert: Host System has Reset
————-

found related KB while searching on MOS:

“On V440/N440 2P systems with OBP 4.22.19 firmware and ALOM firmware 1.5.4 may encounter a host power on failure. (Doc ID 1000080.1)”

Root Cause

The root cause was determined to be the OBP probe timeout value of 2.5 seconds set in ALOM 1.5.4.

Deviation WO_35484 was issued to Celestica (CMX) to rework V440/N440 systems by loading ALOM 1.6.3 FW.

Document 1000080.1 can be found at:

https://support.us.oracle.com/oip/faces/secure/km/DocumentDisplay.jspx?id=1000080.1

So, there is a bug on current ALOM. the OBP firmware is upgraded to the latest already, now what I need to do is to upgrade the ALOM firmware. Patch id/name is 10263984

• Install patch ID 10263984, its contains 2 file. For V440, use “ALOM_1.6.10_fw_hw0.tar.gz”.

• Copy and extract file “ALOM_1.6.10_fw_hw0.tar.gz” to “/usr/platform/SUNW,Sun-Fire-V440/lib/images” directory.

• Then, run command: “scadm download boot alombootfw”

bash-3.00# pwd
/usr/platform/SUNW,Sun-Fire-V440/lib/images
bash-3.00# gzcat ALOM_1.6.10_fw_hw0.tar.gz | tar xf -
bash-3.00# /usr/platform/`uname -i`/sbin/scadm download boot alombootfw
……………….. (100%)
Download completed successfully
Please wait for verification
..
Complete
bash-3.00# /usr/platform/`uname -i`/sbin/scadm download alommainfw
…………………………………. (6%)
…………………………………. (12%)
…………………………………. (18%)
…………………………………. (25%)
…………………………………. (31%)
…………………………………. (37%)
…………………………………. (44%)
…………………………………. (50%)
…………………………………. (56%)
…………………………………. (63%)
…………………………………. (69%)
…………………………………. (75%)
…………………………………. (81%)
…………………………………. (88%)
…………………………………. (94%)
……………………………. (100%)
Download completed successfully
Please wait for verification
……
Complete
bash-3.00# exit

Reboot the machine, then you will see the amber light will gone.

In my case, this problem occurred since customer tried to change the date and time on server but wrong syntax; the year move ahead to 2023. The worst, he didn’t stop the NBU services, so suddenly a few backup policy are running also the image cleanup.

The image cleanup that ran on that day cleaned up most..if not all the images..around 966 images:

log.101923:12:48:48.825 [7854] <4> delete_expired_backups: image delete 45970 ms, image verify 0 ms, tir_info_remove 0 ms, copies delete 0 ms
log.101923:12:48:48.831 [7854] <4> delete_expired_backups: compression 0 ms, # of bptm calls 0
log.101923:12:48:48.831 [7854] <4> delete_expired_backups: deleted 966 expired records, compressed 0, tir removed 0, deleted 0 expired copies
log.101923:12:48:49.561 [7854] <2> delete_expired_backups: OVsystem(/usr/openv/netbackup/bin/admincmd/nbdelete -allvolumes -jobid 62120) successful
log.101923:12:48:49.573 [7854] <4> delete_expired_backups: Exiting

The date and time fixed on that day, but till last week, there are no image cleanup job was ran.

Tried to follow this guide but still no luck:
http://98.129.119.162/connect/pt-br/forums/image-cleanup-job
http://www.symantec.com/business/support/index?page=content&id=TECH63221

[GENERAL ERROR: The VERITAS NetBackup (tm) image database does not clean up expired images on the expiration date:
http://www.symantec.com/business/support/index?page=content&id=TECH10828

[GENERAL ERROR: Image cleanup is no longer running:
http://www.symantec.com/docs/TECH125429

The case was solved by today ^_^, if you got the same problem, what you need to do are:

1) Stop NBU
2) rm /usr/openv/netbackup/bin/cleanup.lock
3) rm /usr/openv/netbackup/bin/bpsched.d/lastClean
4) rm /usr/openv/netbackup/bin/bpsched.d/last_time_expired_media
5) rm /usr/openv/netbackup/bin/bpsched.d/cleanup (if exists)
6) rm /usr/openv/netbackup/db/jobs/pempersist
7) Restart NBU
8) Check if cleanup job runs by itself.

After finished on step number 7, on NBU GUI you will find Cleanup job running on activity monitor. To make sure, you have to wait till next couple hours, depend on the image cleanup interval configuration (default is 12 hours).

*Upgrading server software from version 6.x to 7.0*
NOTE:
-NetBackup 7.0 server software is 64-bit compatible only and cannot be installed on 32-bit systems.
-If you have 32-bit systems with NetBackup 6.x master servers that you want to upgrade, you must first migrate
the NetBackup catalog and databases to a supported 64-bit system.
-Starting with NetBackup 7.0, most of the add-on products and database agents are now installed with the NetBackup
server or the client package. Separate installation for these products is no longer needed.

#To upgrade server software from version 6.x to 7.0:
- back up the existing NetBackup 6.x databases
- Deactivate all NetBackup policies and storage lifecycle policies
- Deactivate disk staging storage units
>Netbackup Management > Storage Unit > Double Click Disk Staging Storage Unit > Staging Schedule > Exclude Dates
-Deactivate all media servers
>Media and Device Management > Devices > Host >select media server > deactivate

- For Solaris servers only, remove the “6.x versions of all add-on products” and database agents
(The script also offers to remove these earlier versions for you and Symantec recommends this method)

-Remove the current NetBackup server package by using the appropriate command:
for version 6.0 : pkgrm VRTSnetbp
for version 6.5    : pkgrm sYMCnetbp

The following prompt appears:
Are you doing this pkgrm as a step in an upgrade process?, enter Y

-Ensure that you have license keys for all of the NetBackup servers, clients, options, and agents that you ordered.
-Insert NBU DVD, then run “./install” script.

-After you have finished the upgrade, you can install and configureNetBackup Access Control (NBAC).

-After all servers are upgraded, reactivate the following in the order as shown:
-All media servers
-All disk staging storage units
-All NetBackup policies
-All storage lifecycle policies

===============================================
Upgrading clients after servers are upgraded:

The “update_clients” installation script lets you push client software to clients.
It does not let you push client software to a remote client that is also a NetBackup media or master server. You cannot push software this way because the server software and client binaries must be of the same version on a single host.
The update_clients installation script can determine the full client list that is configured on the server.When it is run without any parameters, it attempts to update all clients
(as determined by /usr/openv/netbackup/bin/admincmd/bpplclients).

If you do not want to upgrade all clients, you can specify a subset of clients. Use the hardware type and operating system parameters or use the -ClientList parameter.

You can run update_clients from a media server

A Windows host can only push client software toWindows clients.
A NetBackup UNIX server can only push client software to UNIX clients.

===============================================
Listing of Symantec NetBackup ™ 7.0 Manuals:
http://www.symantec.com/docs/TECH126327

Netbackup 7 FAQ
Netbackup 7 Software Compatibility List

OpsCenter is a web based monitoring, alerting, and reporting application which  is capable of providing these services for  the NetBackup platform as well as BackupExec, Enterprise Vault and  (through the  optional OpsCenter Analytics component) other third party data protection products.

OpsCenter 7  is a new product which replaces NOM and VBR,  combining  the features and capabilities both products into a single product together with significant performance and usability improvements.  OpsCenter 7 comes in two options -  OpsCenter and OpsCenter Analytics.

OpsCenter vs OpsCenter Analytics

OpsCenter is a free product which gives you the ability to monitor, alert and do operational reporting on NetBackup, Enterprise Vault, Backup Exec and PureDisk. OpsCenter server is part of NetBackup and can be deployed on master server for managing a single domain, or independently for managing multiple NetBackup Domains.  It also allows you to do minor management tasks such as “upping” tape drives, restarting failed jobs, freezing/unfreezing and other tape functions, restarting services/daemons on Masters etc. The free version limits historical reporting.

OpsCenter Analytics is a licensed option that is unlocked with a key. This gives the customer the ability to display customizable, multi-level views of backup and  archive resources and customizable reports for tracking service usage and expenditures. It also contains tools for defining cost metrics and chargeback formulas or handling alerts as well as allowing reporting beyond 60 days.

OpsCenter Analytics, formerly Backup Reporter, helps enhance backup and archive operations, verify service level compliance with more in depth policy and schedule information, and align backup and archiving with the business. OpsCenter Analytics provides multi product and platform support, business reporting, and complete customization, providing enhanced visibility and control into backup environment and operations.

OpsCenter Analytics can also provide reports on the following third part products in addition to those covered by OpsCenter:
-EMC Legato Networker
-IBM Tivoli Storage Manager

KEY FEATURES AND KEY BENEFITS

Key Features

1. Long term, configurable data retention for trending and analysis.
2. Dynamic job & policy analysis.
3. Reporting on exchange archiving from Enterprise Vault.
4. Easy upgrade from OpsCenter to OpsCenter Analytics.

Key Benefits

1. Better predict backup storage consumption across multiple locations through maintained historical backup and archive job information.
2. Reports can be created around one of the most highly managed areas of NetBackup: the policy and schedule engine.
3. People less removed from day to day operations , and have centralized reporting for backup and archive operations.
4. Business reporting previously available with VBR – including historical trending and predictive forecasting, cost analysis reports, complete report customization and support for 3rd party data protection products – now included in the OpsCenter package.

For more information, watch the video here and go to Symantec OpsCenter website

Other Link:
Symantec NetBackup(tm) 7.0 OpsCenter Administrator’s Guide

The Sun SPARC® Enterprise M-series server line is the newest addition to Sun Microsystem’s mid-range (M4000/M5000) and high-end server (M8000/M9000) families. Designed for the enterprise- class datacenter, all members of the server line offer a great deal of configuration flexibility in addition to high performance and reliability.

#########################################################################
#.  >>switch the prompt from domain console to XSCF console

XSCF>console -d 0    >>swith from XSCF console to domain console
XSCF>console -d 0 -f    >>swith from XSCF console to domain console with force option
XSCF>reset -d 0 xir    >>reset/restart domain 0 console
XSCF>poweroff -d 0    >>power off domain ID 0
XSCF>poweroff -f -d 0    >>forcibly power off domain ID 0

XSCF>poweroff -a    >>power off all domain together
XSCF>poweron -a        >>power on all domain
XSCF>poweron -d 0    >>power on domain ID 0

XSCF>version -c xcp    >>to determine firmware version
XSCF>switchscf -t Standby

XSCF>snapshot -d usb0    >>save/collect log to USB flash disk
XSCF>showlogs power

XSCF> setdomainmode -d 0 -m autoboot=on
XSCF> showdomainmode -d 0
Host-ID             : 85289956
Diagnostic Level    : min
Secure Mode         : on
Autoboot            : on
CPU Mode            : auto

——————————————————————————–
TROUBLESHOOTING COMMAND:
-showhardconf        >>displays information about each FRU
-showlogs
-showstatus        >>Displays the information concerning the units failed or degraded
-fmdump            >>to display the contents of any log files associated with the Solaris fault manager
-fmadm faulty

——————————————————————————–
Command used for ADDING & REMOVING DOMAIN:
setdcl
setupfru
addboard
deleteboard
moveboard

———————————————————————————–

XSCF> set
setaltitude        setdualpowerfeed   setntp             setsnmp
setapcs            setemailreport     setpasswordpolicy  setsnmpusm
setarchiving       sethostname        setpowerupdelay    setsnmpvacm
setaudit           sethttps           setprefetchmode    setssh
setautologout      setldap            setprivileges      setsunmc
setcod             setlocale          setrci             settelnet
setdate            setlocator         setrcic            settimezone
setdcl             setloginlockout    setroute           setupfru
setdomainmode      setlookup          setservicetag      setupplatform
setdomparam        setnameserver      setshutdowndelay   
setdscp            setnetwork         setsmtp            
XSCF> set
setaltitude        setdualpowerfeed   setntp             setsnmp
setapcs            setemailreport     setpasswordpolicy  setsnmpusm
setarchiving       sethostname        setpowerupdelay    setsnmpvacm
setaudit           sethttps           setprefetchmode    setssh
setautologout      setldap            setprivileges      setsunmc
setcod             setlocale          setrci             settelnet
setdate            setlocator         setrcic            settimezone
setdcl             setloginlockout    setroute           setupfru
setdomainmode      setlookup          setservicetag      setupplatform
setdomparam        setnameserver      setshutdowndelay   
setdscp            setnetwork         setsmtp            
XSCF>    
Display all 145 possibilities? (y or n)
addboard            setdate             showdomainmode
addcodlicense       setdcl              showdomainstatus
addfru              setdomainmode       showdscp
adduser             setdomparam         showdualpowerfeed
applynetwork        setdscp             showemailreport
cfgdevice           setdualpowerfeed    showenvironment
clockboard          setemailreport      showfru
confdidr            sethostname         showhardconf
console             sethttps            showhostname
deleteboard         setldap             showhttps
deletecodlicense    setlocale           showldap
deletefru           setlocator          showlocale
deleteuser          setloginlockout     showlocator
disablemodes        setlookup           showloginlockout
disableuser         setnameserver       showlogs
dumpconfig          setnetwork          showlookup
enableescalation    setntp              showmodes
enableservice       setpasswordpolicy   showmonitorlog
enableuser          setpowerupdelay     shownameserver
escalation          setprefetchmode     shownetwork
exit                setprivileges       shownotice
flashupdate         setrci              showntp
fmadm               setrcic             showpasswordpolicy
fmdump              setroute            showpowerupdelay
fmstat              setservicetag       showprefetchmode
getflashimage       setshutdowndelay    showresult
ioxadm              setsmtp             showroute
man                 setsnmp             showservicetag
moveboard           setsnmpusm          showshutdowndelay
nslookup            setsnmpvacm         showsmtp
password            setssh              showsnmp
ping                setsunmc            showsnmpusm
poweroff            settelnet           showsnmpvacm
poweron             settimezone         showssh
prtfru              setupfru            showstatus
rebootxscf          setupplatform       showsunmc
replacefru          showaltitude        showtelnet
reset               showapcs            showtimezone
resetdateoffset     showarchiving       showuser
restoreconfig       showaudit           snapshot
restoredefaults     showautologout      switchscf
sendbreak           showboards          testsb
service             showcod             traceroute
setaltitude         showcodlicense      unlockmaintenance
setapcs             showcodusage        version
setarchiving        showconsolepath     viewaudit
setaudit            showdate            who
setautologout       showdcl             
setcod              showdevices         

-----------------------------------------------------------------------------------

OTHER COMMAND:
adduser
applynetwork         >reset XSCF to reflect information that has been set for the XSCF network
console
exit

cfgdevice                    >connect the CD-RW/DVD-RW drive unit and the tape drive unit to the port, disconnect it from the port, or display the status of the drive
XSCF> cfgdevice -l
XSCF> cfgdevice -c attach -p 0-0
XSCF> cfgdevice -f -c detach -p 0-0    >Disconnects the DVD drive/tape drive unit from the port 0-0.

XSCF> cfgdevice -y -c attach -p 0-0    >Connects the DVD drive/tape drive unit to port 0-0 when the system is being powered on.  Automatically answers “y” to all prompts.
XSCF> cfgdevice -q -y -c attach -p 0-0    >answer ‘y’ to all prompts without displaying message

deleteuser
dumpconfig/restoreconfig            >>save/restore XSCF configuration
XSCF> dumpconfig file:///media/usb_msd/backup-file.txt
XSCF> dumpconfig ftp://server/backup/backup-sca-ff2-16.txt
XSCF> restoreconfig file:///media/usb_msd/backup-file.txt

fmadm
fmadm faulty                >>
fmdump                        >view fault management logs
Exp.
XSCF> fmdump
Sep 29 15:09:25.4335 8cec9a83-e2a3-4dc3-a7cd-de01caef5c63 FMD-8000-4M
Sep 29 15:10:09.6151 5f88d7d5-a107-4435-99c9-7c59479d22ed FMD-8000-58

[Display Very Verbose Event Detail for the Last UUID:
XSCF> fmdump -e -V -u 5f88d7d5-a107-4435-99c9-7c5947 9d22ed

XSCF> fmdump  -m -M            >>Displaying Contents of the Fault Manager syslog Message

flashupdate    >update firmware
getflashimage    >download a firmware image file
XSCF> getflashimage http://imageserver/images/FFXCP1041.tar.gz
XSCF> getflashimage ftp://imageserver/images/FFXCP1041.tar.gz

moveboard    >move XSB from current domain to another
poweron
poweroff
prtfru
XSCF> prtfru -c system-board

rebootxscf        >reset the XSCF

replacefru        >

reset            >reset the specific domain; use this command only for the purpose of recovery, such as if OS hang
senddbreak        >send a break signal to the specified domain
XSCF> sendbreak -d 0
setautologout
setdate
setdate -u -s 012707592006.00    >>Sets “January 27 07:59:00 2006″ of UTC as the current time

setdomainmode
sethostname
sethttps
setnetwork
setntp
setroute
settelnet
setssh
XSCF> setssh -c enable

setprivileges
XSCF> setprivileges aziz filedeng

showconsolepath
showdate
showdevice
showdevice -d 0

showboards        >check the XSB number, domain ID, LSB number, XSB status
XSCF>showboards -a

showdcl            >check domain ID, LSB number, configuration policy
XSCF>showdcl -va

showdomainmode
showdomainstatus -a    >check the power status of the system
showenvironment        >display the intake air temperature and humidity, temperature sensor information, voltage sensor
showfru            >display the hardware settings of specified device
showhardconf        >display information about field replaceable unit (FRU)
showlogs        >display the specific log
XSCF>showlogs event
XSCF>showlogs error -v
XSCF>showlogs power
XSCF>showlogs monitor
XSCF>showlogs console

showstatus
showmonitorlog        >display the contents of monitoring messages in real time
shownetwork -a         >display information of network interfaces for XSCF
showuser
snapshot        >collect and transfer environtment, log, error, and FRUID data
switchscf        >switch the XSCF unit between the active and standby states
testsb             >perform an initial diagnosis of the specified physical system board (PSB

————————————————————————————–
REPLACE INTERNAL TAPE:

1. unconfigure tape drive from OS
# cfgadm -a
c0::rmt/0 tape connected configured unknown
# cfgadm -c unconfigure c0::rmt/0

Stop the connection to the CD-RW/DVD-RW drive unit on the same controller
as the target tape drive unit

#cfgadm -a
c0::dsk/c0t4d0 CD-ROM connected configured unknown
#cfgadm -c unconfigure c0::dsk/c0t4d0
# cfgadm -a
c0::dsk/c0t4d0 CD-ROM connected unconfigured unknown
c0::rmt/0 tape        connected unconfigured unknown

2. Detach the target tape drive unit from the port
XSVF> cfgdevice -c detach -p <port no.> command
3. Confirm that the target tape drive unit is unconfigured from the domain.
cfgdevice -l
4. Remove the tape drive unit
5. Mount the replacement tape drive unit
6. Attach the tape drive unit to the port
XSCF> cfgdevice -c attach -p <port no.>
7. Confirm that the target tape drive unit is configured from the domain.
XSCF> cfgdevice -l

8. from OS, execute command ‘cfgadm -c configure TAPE_Ap_Id’ to configure tape drive
#cfgadm -c configure c0::rmt/0

9. from OS< execute command ‘cfgadm -c configure DVD_Ap_Id’ to configure DVD drive
#cfgadm -c configure c0::dsk/c0t4d0

10. execute ‘cfgadm -al’ to verify the status of tape drive and DVD drive

————————————————————————–
NOTE:
PSB (Physical System Board)
XSB (Extended System Board)

A PSB that is logically divided into one part (no division) is called a Uni-XSB, and a PSB that is logically divided into four parts is called a Quad-XSB. On Quad-XSB configuration; ONE XSB CONTAIN TWO PCI SLOT

——————————————————————————–

UPDATE:
Oracle SPARC M-Series Servers Documentation:

(http://www.oracle.com/technetwork/documentation/sparc-mseries-servers-252709.html)

E19867-01    View Library    Download    Sun SPARC Enterprise M3000 Server Documentation
E19855-01    View Library    Download    Sun SPARC Enterprise M4000 Server Documentation
E19580-01    View Library    Download    Sun SPARC Enterprise M5000 Server Documentation
E19170-01    View Library    Download    Sun SPARC Enterprise M8000 Server Documentation
E19415-01    View Library    Download    Sun SPARC Enterprise M9000 Server Documentation

here are the step-by-step:

• first of all, you need to upload Solaris ISO image to server that will used as Jumpstart server. In this example, my ISO images is “sol-10-u8-ga-sparc-dvd.iso” and I uploaded already to root home directory (/).

• Add your client IP address & hostname to “/etc/hosts”, also the hostname and mac address to “/etc/ethers”.

if your client is Sparc, then you can find the mac address by running “banner” command from OK prompt. For x86, the mac address can be found on BIOS.

# more /etc/hosts
::1     localhost
127.0.0.1       localhost
10.32.16.1      solaris10 solaris10. loghost
192.168.1.2    client1
192.168.1.3    client2
192.168.1.4    client3

# more /etc/ethers
0:0:be:a5:1a:9e client1
0:0:be:a5:1a:9f client2
0:0:be:a5:1a:a0 client3

• mount ISO images using “lofiadm” command to “/mnt” directory:

# lofiadm -a /sol-10-u8-ga-sparc-dvd.iso /dev/lofi/1
# lofiadm
Block Device             File
/dev/lofi/1              /sol-10-u8-ga-sparc-dvd.iso
# mount -F hsfs -o ro /dev/lofi/1 /mnt

• Check the “/mnt” directory, the jumpstart scripts are located at “/Solaris_10/Tools/” directory:

# cd /mnt/Solaris_10/Tools/
# ls
add_install_client    dial                  rm_install_client
Boot                  Installers            setup_install_server

• If you don’t hv enough disk space, then you can run “add_install_client” script directly:

the format is “add_install_client <hostname> <platform>”

#./add_install_client client1 sun4u
saving original /etc/dfs/dfstab in /etc/dfs/dfstab.orig
Adding “share -F nfs -o ro,anon=0 /mnt” to /etc/dfs/dfstab
making /tftpboot
enabling tftp in /etc/inetd.conf
starting rarpd
starting bootparamd
starting nfsd’s
starting nfs mountd
updating /etc/bootparams
copying boot file to /tftpboot/inetboot.SUN4U.Solaris_10-1
#

NOTE: If you want to copy all or part of the install DVD onto a system to set it up as a long term install server with the install media available on local disk, then you can run “setup_install_server” script.

FORMAT: setup_install_server <destination_dir>.

• Check “/etc/bootparams”. The bootparams file contains a list of client  entries  that diskless  clients  use for booting. Make sure your client listed in there..
• Configure Client to boot from Network. for Sparc, run “boot net – install” from OK Prompt. For X86 configure BIOS to boot from Network.
• Follow the installation procedure till finish..

NOTE For X86/i386pc:

1. You need to configure DHCP macro on Jumpstart server, run “/usr/sadm/admin/bin/dhcpmgr” from X Windows / GUI, then click EDIT > NETWORK WIZARD.
2. put “i386pc” as your platform while running add_install_client , exp:

./add_install_client -d -e 0:0:be:a5:1a:9e -s 192.168.1.1:/mnt i86pc

“The NetBackup Support Utility (NBSU) is a Symantec utility used to gather diagnostic information about the system on which the utility is run. By default, NBSU gathers appropriate diagnostic information based on the Operating System and NetBackup environment.  With the availability of many command line options, the diagnostic information gathered can be tuned as desired”.

Actually, if you install Netbackup on Solaris, you can also run the Explorer command using an option “nbu_extended” like this:

/opt/SUNWexplo/bin/explorer -w default,nbu_extended

with “nbu_extended” option, the Explorer will collects Extended NetBackup information. Its not only gather the log, it will also run a few commands, collect the directories and more. see here to know what Explorer with nbu_extended do later on your systems.

Back to NBSU, for more detail about this great tools and to understand well on how to run nbsu commands, please click the link below:

DOCUMENTATION: What is the nbsupport utility and where can it be found?
http://support.veritas.com/docs/264785

DOCUMENTATION AND DOWNLOAD: NetBackup Support Utility (NBSU) Usage and Examples for 6.x. NBSU was released with 6.5, 6.0 MP6, and 5.1 MP7, and replaces what is known as “nbsupport” in previous versions.
http://support.veritas.com/docs/323434

If you have a lot of tape drives connected to your host/server, sometimes its not easy to know the tape drives order between tape library and drive order on host.

Lets say, all tape drive order on tape library and host are starting from 0 (zero).You try to mount cartridge to tape drive number 6 on tape library using the utility (example SL Console or move command). After mounting succeeded, you may guess that the cartridges is mounted to drive order number 6 also on your host/server. You run the command “mt -f /dev/rmt/6cbn status” to check the result, but guess what? the cartridges is not in there..

This is because, cbn number is picked automatically by devfsadm during enumeration of new devices. Every new tape logical unit number (LUN) found by devfsadm gets the next available number in “/dev/rmt”. So, cbn number order its not same with drive number order on tape library.

Since the /dev/rmt name depends on the order in which devices appear in the device tree, it changes from host to host. For a given tape drive that is seen by two or more different hosts, the /dev/rmt link can be different on each of these hosts. Also, if the drive is replaced the links change unless the vendor provides a way to retain the port World-Wide Name (PWWN) of the drive.

So, now what we need to do is just to configure persistent binding for all tape devices. on Solaris, we only need to edit “/etc/devlink.tab” file. First of all, list all tape drives on current configuration:

Example:

# ls -ltr /dev/rmt/*cbn

lrwxrwxrwx 1 root root 75 Mar 1 15:50 /dev/rmt/3cbn -> ../../devices/pci@8,600000/SUNW,emlxs@1,1/fp@0,0/st@w500108f00056a81c,0:cbn
lrwxrwxrwx 1 root root 75 Mar 1 15:50 /dev/rmt/2cbn -> ../../devices/pci@8,600000/SUNW,emlxs@1,1/fp@0,0/st@w500108f00056a81b,0:cbn
lrwxrwxrwx 1 root root 75 Mar 1 15:50 /dev/rmt/1cbn -> ../../devices/pci@8,600000/SUNW,emlxs@1,1/fp@0,0/st@w500108f00056a81a,0:cbn
lrwxrwxrwx 1 root root 75 Mar 1 15:50 /dev/rmt/0cbn -> ../../devices/pci@8,600000/SUNW,emlxs@1,1/fp@0,0/st@w500108f00056a81d,0:cbn

So, there are 4 tape drives, the current config is like this:
drive 0cbn:  w500108f00056a81d,0
drive 1cbn:  w500108f00056a81a,0
drive 2cbn:  w500108f00056a81b,0
drive 3cbn:  w500108f00056a81c,0

If you check on tape library, the drive order is like this:

drive o:  w500108f00056a81a,0
drive 1:  w500108f00056a81b,0
drive 2:  w500108f00056a81c,0
drive 3:  w500108f00056a81d,0

Now, ho to match drives order between tape library and your host? okay, here we go:

1. Edit “/etc/devlink.tab” file.

2. add these line:

type=ddi_byte:tape;addr=w500108f00056a81a,0;    rmt/0\M0
type=ddi_byte:tape;addr=w500108f00056a81b,0;    rmt/1\M0
type=ddi_byte:tape;addr=w500108f00056a81c,0;    rmt/2\M0
type=ddi_byte:tape;addr=w500108f00056a81d,0;    rmt/3\M0

3. Remove existing links from /dev/rmt by running the rm /dev/rmt/* command.

4. run “devfsadm” command. run “reboot — -r” if needed.

5. Finish,

See the result by manualy mounting cartridges and check with “mt -f /dev/rmt/Xcbn status” command.

Type “man devlinks” for more information..