Monitor LVM with the following commands: bdf Similar to a Solaris style "df -k" output. pvdisplay Display PV Information (PV = phys volume) vgdisplay Display VG Information (VG = volume group) lvdisplay Display LV Information (LV = logical volume
Simple Network Management Protocol (SNMP) is used in network management systems to monitor network-attached devices for conditions that warrant administrative attention. SNMP is a component of the Internet Protocol Suite as defined by the Internet Engineering Task Force (IETF). It consists of a set of standards for network management, including an application layer protocol, a database schema, and a set of data objects.
SNMP exposes management data in the form of variables on the managed systems, which describe the system configuration. These variables can then be queried (and sometimes set) by managing applications.
In typical SNMP usage, there are a number of systems to be managed, and one or more systems managing them. A software component called an agent (see below) runs on each managed system and reports information via SNMP to the managing systems. Essentially, SNMP agents expose management data on the managed systems as variables (such as "free memory", "system name", "number of running processes", "default route"). But the protocol also permits active management tasks, such as modifying and applying a new configuration. The managing system can retrieve the information through the GET, GETNEXT and GETBULK protocol operations or the agent will send data without being asked using TRAP or INFORM protocol operations. Management systems can also send configuration updates or controlling requests through the SET protocol operation to actively manage a system. Configuration and control operations are used only when changes are needed to the network infrastructure. The monitoring operations are usually performed on a regular basis.
The variables accessible via SNMP are organized in hierarchies. These hierarchies, and other metadata (such as type and description of the variable), are described by Management Information Bases (MIBs).
SNMP basic components
An SNMP-managed network consists of three key components:
A managed device is a network node that contains an SNMP agent and that resides on a managed network. Managed devices collect and store management information and make this information available to NMSs using SNMP. Managed devices, sometimes called network elements, can be any type of device including, but not limited to, routers, access servers, switches, bridges, hubs, IP telephones, computer hosts, and printers.
An agent is a network-management software module that resides in a managed device. An agent has local knowledge of management information and translates that information into a form compatible with SNMP.
A network management system (NMS) executes applications that monitor and control managed devices. NMSs provide the bulk of the processing and memory resources required for network management. One or more NMSs may exist on any managed network.
SNMP Community Strings
An SNMP community string is a text string that acts as a password. It is used to authenticate messages that are sent between the management station (the SNMP manager) and the device (the SNMP agent). The community string is included in every packet that is transmitted between the SNMP manager and the SNMP agent.
After receiving an SNMP request, the SNMP agent compares the community string in the request to the community strings that are configured for the agent. The requests are valid under these circumstances:
Only SNMP Get and Get-next requests are valid if the community string in the request matches the read-only community. SNMP Get, Get-next, and Set requests are valid if the community string in the request matches the agent's read-write community.
To check if there are community strings on a system - check the /etc/snmpd.conf file. If community strings are used, they will be uncommented as shown below;
#contact: # enter contact person for agent #location: # enter location of agent #max-trap-dest: # enter max no. of trap-dest entries to be maintained. #trap-dest: # enter trap destination get-community-name: Madeupname_mgt_read set-community-name: Madeupname_mgt_write trap-dest: perfhost trap-dest: DSMHOST
LLT and GAB Commands | Port Membership | Daemons | Log Files | Dynamic Configuration | Users | Resources | Resource Agents | Service Groups | Clusters | Cluster Status | System Operations | Sevice Group Operations | Resource Operations | Agent Operations | Starting and Stopping
LLT and GRAB
VCS uses two components, LLT and GAB to share data over the private networks among systems. These components provide the performance and reliability required by VCS.
LLT LLT (Low Latency Transport) provides fast, kernel-to-kernel comms and monitors network connections. The system admin configures the LLT by creating a configuration file (llttab) that describes the systems in the cluster and private network links among them. The LLT runs in layer 2 of the network stack GAB GAB (Group membership and Atomic Broadcast) provides the global message order required to maintain a synchronised state among the systems, and monitors disk comms such as that required by the VCS heartbeat utility. The system admin configures GAB driver by creating a configuration file ( gabtab). LLT and GAB files
/etc/llthosts
The file is a database, containing one entry per system, that links the LLT system ID with the hosts name. The file is identical on each server in the cluster.
/etc/llttab
The file contains information that is derived during installation and is used by the utility lltconfig.
/etc/gabtab
The file contains the information needed to configure the GAB driver. This file is used by the gabconfig utility.
/etc/VRTSvcs/conf/config/main.cf
The VCS configuration file. The file contains the information that defines the cluster and its systems.
Gabtab Entries
/sbin/gabdiskconf - i /dev/dsk/c1t2d0s2 -s 16 -S 1123 /sbin/gabdiskconf - i /dev/dsk/c1t2d0s2 -s 144 -S 1124 /sbin/gabdiskhb -a /dev/dsk/c1t2d0s2 -s 16 -p a -s 1123 /sbin/gabdiskhb -a /dev/dsk/c1t2d0s2 -s 144 -p h -s 1124 /sbin/gabconfig -c -n2
gabdiskconf -i Initialises the disk region -s Start Block -S Signature
gabdiskhb (heartbeat disks) -a Add a gab disk heartbeat resource -s Start Block -p Port -S Signature
gabconfig -c Configure the driver for use -n Number of systems in the cluster.
LLT and GAB Commands
Verifying that links are active for LLT lltstat -n verbose output of the lltstat command lltstat -nvv | more open ports for LLT lltstat -p display the values of LLT configuration directives lltstat -c lists information about each configured LLT link lltstat -l List all MAC addresses in the cluster lltconfig -a list stop the LLT running lltconfig -U start the LLT lltconfig -c verify that GAB is operating gabconfig -a
Note: port a indicates that GAB is communicating, port h indicates that VCS is started
stop GAB running gabconfig -U start the GAB gabconfig -c -n override the seed values in the gabtab file gabconfig -c -x GAB Port Memberbership
List Membership gabconfig -a
Unregister port f /opt/VRTS/bin/fsclustadm cfsdeinit Port Function a gab driver b I/O fencing (designed to guarantee data integrity) d ODM (Oracle Disk Manager) f CFS (Cluster File System) h VCS (VERITAS Cluster Server: high availability daemon) o VCSMM driver (kernel module needed for Oracle and VCS interface) q QuickLog daemon v CVM (Cluster Volume Manager) w vxconfigd (module for cvm) Cluster daemons
High Availability Daemon had Companion Daemon hashadow Resource Agent daemon Agent Web Console cluster managerment daemon CmdServer Cluster Log Files
Log Directory /var/VRTSvcs/log primary log file (engine log file) /var/VRTSvcs/log/engine_A.log Starting and Stopping the cluster
"-stale" instructs the engine to treat the local config as stale "-force" instructs the engine to treat a stale config as a valid one
hastart [-stale|-force] Bring the cluster into running mode from a stale state using the configuration file from a particular server
hasys -force stop the cluster on the local server but leave the application/s running, do not failover the application/s hastop -local stop cluster on local server but evacuate (failover) the application/s to another node within the cluster hastop -local -evacuate stop the cluster on all nodes but leave the application/s running
hastop -all -force Cluster Status
display cluster summary hastatus -summary continually monitor cluster hastatus verify the cluster is operating hasys -display Cluster Details
information about a cluster haclus -display value for a specific cluster attribute haclus -value modify a cluster attribute haclus -modify Enable LinkMonitoring haclus -enable LinkMonitoring Disable LinkMonitoring haclus -disable LinkMonitoring Users
add a user hauser -add modify a user hauser -update delete a user hauser -delete display all users hauser -display System Operations
add a system to the cluster hasys -add delete a system from the cluster hasys -delete Modify a system attributes hasys -modify list a system state hasys -state Force a system to start hasys -force Display the systems attributes hasys -display [-sys] List all the systems in the cluster hasys -list Change the load attribute of a system hasys -load Display the value of a systems nodeid (/etc/llthosts) hasys -nodeid Freeze a system (No offlining system, No groups onlining) hasys -freeze [-persistent][-evacuate]
Note: main.cf must be in write mode
Unfreeze a system ( reenable groups and resource back online) hasys -unfreeze [-persistent]
Note: main.cf must be in write mode
Dynamic Configuration
The VCS configuration must be in read/write mode in order to make changes. When in read/write mode the configuration becomes stale, a .stale file is created in $VCS_CONF/conf/config. When the configuration is put back into read only mode the .stale file is removed.
Change configuration to read/write mode haconf -makerw Change configuration to read-only mode haconf -dump -makero Check what mode cluster is running in haclus -display |grep -i 'readonly'
0 = write mode 1 = read only mode
Check the configuration file hacf -verify /etc/VRTS/conf/config
Note: you can point to any directory as long as it has main.cf and types.cf
convert a main.cf file into cluster commands hacf -cftocmd /etc/VRTS/conf/config -dest /tmp convert a command file into a main.cf file hacf -cmdtocf /tmp -dest /etc/VRTS/conf/config
Service Groups
add a service group haconf -makerw hagrp -add groupw hagrp -modify groupw SystemList sun1 1 sun2 2 hagrp -autoenable groupw -sys sun1 haconf -dump -makero delete a service group haconf -makerw hagrp -delete groupw haconf -dump -makero change a service group haconf -makerw hagrp -modify groupw SystemList sun1 1 sun2 2 sun3 3 haconf -dump -makero
Note: use the "hagrp -display " to list attributes
list the service groups hagrp -list list the groups dependencies hagrp -dep list the parameters of a group hagrp -display display a service group's resource hagrp -resources display the current state of the service group hagrp -state clear a faulted non-persistent resource in a specific grp hagrp -clear [-sys] Change the system list in a cluster # remove the host hagrp -modify grp_zlnrssd SystemList -delete
# add the new host (don't forget to state its position) hagrp -modify grp_zlnrssd SystemList -add 1
# update the autostart list hagrp -modify grp_zlnrssd AutoStartList
Service Group Operations
Start a service group and bring its resources online hagrp -online -sys Stop a service group and takes its resources offline hagrp -offline -sys Switch a service group from system to another hagrp -switch to Enable all the resources in a group hagrp -enableresources Disable all the resources in a group hagrp -disableresources Freeze a service group (disable onlining and offlining) hagrp -freeze [-persistent]
note: use the following to check "hagrp -display | grep TFrozen"
Unfreeze a service group (enable onlining and offlining) hagrp -unfreeze [-persistent]
note: use the following to check "hagrp -display | grep TFrozen"
Enable a service group. Enabled groups can only be brought online haconf -makerw hagrp -enable [-sys] haconf -dump -makero
Note to check run the following command "hagrp -display | grep Enabled"
Disable a service group. Stop from bringing online haconf -makerw hagrp -disable [-sys] haconf -dump -makero
Note to check run the following command "hagrp -display | grep Enabled"
Flush a service group and enable corrective action. hagrp -flush -sys Resources
change a resource attribute to be globally wide hares -global change a resource attribute to be locally wide hares -local list the parameters of a resource hares -display list the resources hares -list list the resource dependencies hares -dep Resource Operations
Online a resource hares -online [-sys] Offline a resource hares -offline [-sys] display the state of a resource( offline, online, etc) hares -state display the parameters of a resource hares -display Offline a resource and propagate the command to its children hares -offprop -sys Cause a resource agent to immediately monitor the resource hares -probe -sys Clearing a resource (automatically initiates the onlining) hares -clear [-sys] Resource Types
Add a resource type hatype -add Remove a resource type hatype -delete List all resource types hatype -list Display a resource type hatype -display List a partitcular resource type hatype -resources Change a particular resource types attributes hatype -value Resource Agents
add a agent pkgadd -d . remove a agent pkgrm change a agent n/a list all ha agents haagent -list Display agents run-time information i.e has it started, is it running ? haagent -display Display agents faults haagent -display |grep Faults Resource Agent Operations
Start an agent haagent -start [-sys] Stop an agent haagent -stop [-sys]
Maintains system configuration in the kernel & disk (private region). If the daemon is stopped it does not disable any configuration state loaded into the kernel, it only affects the ability to make configuration changes until vxconfigd is restarted.
It can be in three states: Enabl = Normal mode Disable = Most operations cannot be be used Booted = Normal startup while using boot disk group
vxrelocd Monitors for failure events and relocates failed subdisks
vxconfigbackupd Used to backup configuration chnages, the files created can be used with vxmake to restored lost groups.
vxnotify Display vertias volume manager events used with the vxconfigd daemon Kernel Info Kernel States The kernel can be in three states:
Enabled - both private and public regions are accessible Disabled - no private or public regions are accessible Detached - only private regions are accessible
VM utilities
VxVM debug vxconfigd -k -m enable -x
-x log log to /var/vxvm/vxconfigd.log -x logfile = log to filename -x syslog log to syslog -x timestamp date and timestamp every entry -x tracefile=name log all possible tracing to file
vxiod The vxiod utility starts, stops, or reports on VERITAS Volume Manager (VxVM) I/O daemons. An I/O daemon provides a process context for performing I/O in VxVM.Manage extended disk i/o & handles dirty regions, logging
vxiod set = set number of runnning viod daemon
Note: when run on its own it displays # of vxiod daemons that are running.
vxdctl [option] The vxdctl utility manages aspects of the state of the volume configuration daemon vxconfigd and also manages aspects of configuration for bootstrapping the rootdg disk group.
mode = what mode the vxconfigd is running in enable = enable the vxconfigd daemon (reread the db) disable = disable the vxconfigd daemon stop = kill the vxconfigd daemon (Use 'vxconfigd -k -m disable' to start again) license [init] = print out license info or reread licenses support = display version and components list = display entries in /etc/vx/volboot init [dmp] = recreate /etc/vx/volboot
Note: when is disabled or stop mode no VX commands will be able to run
vxinstall Install volume manger (use /etc/vx/disk to exclude any disks or controllers)
Disk Regions
Private This is were veritas holds the meta data regarding the disk. A copy of the configuration database is copied to each private region within the disk group. Veritas will try and keep 5 copies of the configuration database.
Normally configured as slice 3
Public This is the area that will store the users data.
Normally configured as slice 4.
Disk Layouts Sliced Disk layout private region and public region slices are on seprate partitions (3 & 4), tis type of disk is not suitable for moving between different O/S's but are suitable for boot partitions
Can be converted to CDS
CDS (Cross-platform Data Sharing) private and public regions are one slice (slice 7) , this type is suitable for moving between different O/S's but not suitable for boot parttions. Simple Private and public are the same partition but continuous (slice 3)
DB size vxdg list | grep permlen - the size of the configuration db DB location vxdisk list | grep -i configs - db location File Locations
vxinstall has not be run /etc/vx/reconfig.d/state.d/install-db Host ID's /etc/vx/volboot backup config files (vxconfigbackupd) /etc/vx/cbr/bk delete or deported disk group config files /etc/vx/dgcfg/deport All commands logs /var/adm/vx/veacmdlog Licenses /etc/vx/licenses/lic Imported disk groups info /var/vxvm/tempdb
Note: to clear the tempdb file: vxconfigd -k -x cleartempdir - clear the /var/vxvm/tempdb
# either one of the below after the precommit vxconfigrestore -d vxconfigrestore -c
Note: -p = when you want to check that the restore is correct (use vxprint to check) -d = abort the precommit -c = commit the precommit
Disks
Initialize disk vxdisksetup -i c2t0d0 privlen=768 vxdisksetup -i format=sliced - initialized a disk as a sliced disk
Note: format can be either sliced, simple, cdsdisk or none (see above - Disk Regions)
Uninitialize disk vxdiskunsetup -C c2t0d0 Disk Information vxdisk -g list vxdisk -s list Resize a LUN vxdisk -g resize length=8G Add a disk slice to volboot vxdctl add disk type=simple Add a disk slice vxdisk –f type=simple Add a disk vxdiskadd c1t0d0 or c1 (all disk on controller) vxdisksetup -i Remove a disk totally from VM vxdisk rm Remove a disk from a volume vxdg -g rmdisk Remove a disk slice from VM vxdctl rm disk Clear any host ID flags vxdisk clearimport Renaming a disk vxedit -g rename Move disk to different disk group vxdg move Offline a disk vxdisk offline
Note: disk must not be in a disk group
Online a disk vxdisk online
Note: disk must have a private region otherwise you need to initialise the disk
Hot spare vxedit –g set spare=on NoHotUse vxedit –g set nohotuse=on Turn off failing flag vxedit -g set failing=off Encapsulate a disk vxdisk define c0t0d0s0 type=nopriv Reattach disk (SAN) vxreattach [-br | -c]
-b = Background process -r = Recover volumes -c = Checks to see if reattach is possible
Discover new disks vxdisk scandisks [new | fabric ] Disk Comment vxedit -g set comment="......."
Disk Group
Create a disk group vxdg init group = vxdg init = cds=off - initialize a non-cds disk group Remove a group vxdg destroy Add a disk to a group vxdg –g adddisk = Remove a disk from a group vxdg –g rmdisk Replace failed disk vxdg -k -g adddisk =
-k = forces vxvm to take media name of the failed disk & assign it to the new disk
Import a group vxdg import vxdg -n import vxdg -C import Import group (clear any flags) vxdg import -C
-C - clears any exist host flags
Depot a group vxdg deport vxdg -n deport List no hot use on disk vxdg –g nohotuse List spare space on disk vxdg –g spare Display free space vxdg –g free Backup disk group (vxvm 4.0) vxconfigbackup Restore disk group (vxvm 4.0) vxconfigrestore [-p|-d|-c] Diskgroup Version vxdg list | grep -i version Upgrade disk version vxdg upgrade - upgrade to current version vxdg -T 50 upgrade - upgrade to version 50 vxdg -T 50 init = - creater new group @ version 50 Boot/Default DG vxdg bootdg vxdg defaultdg
vxdctl defaultdg - set defaultdg
Volume
Adding mirror to root /etc/vx/bin/vxrootmir create rootvol, swap vol, Create a simple volume vxassist make vxassist -g make !ctrl:c2 - don't use controller 2
vxassist make layout=[stripe-mirror|concat-mirror|mirror-concat|mirror-stripe]
# Display the relayout operation vxrelayout -g [status|reverse|start] vxtask list
Starting a volume vxvol start Start a disabled volume vxrecover –sb
-s = start volume after recovery -b = background the recovery task
Disable a volume vxvol -g stop Evacuate a volume vxevac -g Maintenance mode vxvol maint Not clean vxmend mirror clean No kernel state vxplex att Extending a volume size vxresize vxresize -g +100m - increase the volume by 100Mb Shrinking a volume size vxresize vxresize -g -100m - decrease the volume by 100Mb add a DRL log to a volume vxassist addlog remove a DRL log from a volume vxassist remove log Extending log size vxvol set loglen = 2m Detering volume size vxassit -g maxsize layout=mirror - the maximum size you can create a mirror vxassist -g maxgrow - the maximum size the volume can grow too Recover a volume Vxmend fix clean
Change volumes permissions vxedit -g set owner= group= mode=
Plexs
Creating a plex vxmake plex sd = Remove a plex vxplex –o rm dis vxplex -g dis vxedit -g -rf rm Moving a plex vxplex mv Copying a plex vxplex cp Attaching a plex vxplex att Detaching a plex vxplex det Offlining a plex vxmend off vol01-02
Sub-disks
Creating sub-disk vxmake sd , offset, len Removing sub-disk vxedit rm Moving sub-disk vxsd mv Associating with a plex vxmake plex sd=, … i.e vxmake plex home-1 sd= disk02-01, disk02-00, disk02-02 Dissociating vxsd dis Splitting vxsd –s split sd Joining vxsd join relocating a sub disk vxassist -g move !disk05 disk02 relocating a whole disk sub disks vxprint -g rootdg -se 'sd_orig_dmname="disk02"' vxunreloc -g rootdg disk02
Volume Manager Information
Disks Display all the physical disks vxdisk list vxdisk -o alldgs list
Display detailed disk info vxdisk list Check for disk failures vxstat –g –ff –d Disk Group Display group properties vxdg list Display detailed group info vxdg list vxinfo -p -g Volume Display volume info vxprint –Aht Display volume properties vxprint –vl Display unstartable volume vxinfo -g Check for volume failures vxstat –g –ff -v Plex Display plex properties vxprint –vp Check for plex failures vxstat –g –ff -p Sub-Disks Display sub-disk properties vxprint –st Veritas Tasks Display tasks vxtask list vxtask monitor - continuously monitor
States: r = running p = pause a = aborting
Statistics and Tracing Iostats vxstat -g -r –d - reset all stats on disk vxstat -g -d - display stats vxstat -g -i 1 -d - display stats every 1 sec intervals for volume vxstat -g -i 10 -c 5 -d - display 5 sets @ 10 secs intervals Tracing vxtrace -d -o dev,disk vxtrace -f -o dev,disk | more Licensing
Logging help in recovery and can speed it up dramatically, the main form of logging in veritas is the DRL (dirty region log) which performs the following
log keeps track of changed regions if system fails only the changed regions of the volume are recovered Add vxassist -g addlog logtype=drl vxassist -g addlog - used for raid logs (no type) Remove vxassist -g remove log [nlog=n] Volume Read Policy
Policies can be used if you have slower disks within a volume and you wish to use the faster disks.
Veritas have created some scripots that can check the integrity of the vxvm setup i.e mirrored volumes, spares, etc. The scripts are based on rules and there are a number of differents rules veritas has set, look in the rules directory to see all of them.
Display Description vxse_raid5log1 info Check rules vxse_raid5log1 -g check List spare rules vxse_spares list Run spare run vxse_spares run
Note: you need to run "/etc/init.d/isisd start" to start the necessary daemons first
/etc/exports ~file controls which file systems are exported to remote hosts and specify options
/exported/directory example.emc.com ~Exports directory to host example.emc.com (found in /etc/exports)
exportfs –a ~command to read /etc/export and export filesystem
mount shadowman.example.com:/misc/export /misc/local ~mount an NFS export
redhat-config-nfs ~RedHat NFS tool
Linux Filesystem commands http://linux.about.com/od/commands/l/blcmdl_8m.htm
pvcreate /dev/emcpowerX ~ initializes PhysicalVolume for later use by the Logical Volume Manager
vgcreate VG_Name /dev/emcpowerX ~ creates a new volume group
lvcreate --size 2000m --name LV_Name /dev/VG_Name ~creates 2000MB logical volume mkfs -t ext2 /dev/VG_Name/LV_Name ~ Make a file system on a logical volume
mount -t ext2 /dev/VG_Name/LV_Name /mnt/FS_MountPoint ~ mount File system
df –a ~display filesystems
Fdisk /dev/sda ~ partition table manipulation
pvdisplay ~ allows you to see the attributes of one or more physical volumes
pvscan ~ scans all supported LVM block devices in the system for physical volumes
vgdisplay ~display attributes of volume groups
vgextend ~ allows you to add one or more initialized physical volumes
vgscan ~ scan physical volumes for LVM volume groups
vgexport ~make volume groups unknown to the system
vgimport ~make volume groups known to the system
lvdisplay ~display attributes of a logical volume
lvextend ~ Extend logigal volume
e2fsadm ~ resizing of a logical volume
fsck ~Command used to check and repair a Linux filesystem
fcinfo remote-port -p 10000000c937694f –ls ~ Lists the remote-port information
Solaris NFS Commands
share -F nfs -d "Cartman dir" / share2
mount -F nfs cartman:/share2 /cartman
share -F nfs -o ro=sun.ucs.indiana.edu,rw=teak.uwsg.indiana.edu /reports ~ export (share) /reports à read only to sun.ucs.indiana.edu, read,write to teak.uwsg.indiana.edu
/etc/dfs/dfstab ~ file to edit to make a share permanent
shareall –F nfs ~ command to excute that will read /etc/dfs/dfstab and share to the network SOLARIS Filesystem Commands
*** Format and lable all devices before using zpool ***
zpool create spoon c3t6d9 ~create & mounts storage pool named spoon and mounts it at /spoon (no slice #)
zpool create spoon mirror emcpower3c emcpower4c ~create a RAID1 storage pool mounted at /spoon
zpool destroy –f spoon ~destroy a zpool
zfs create spoon/fs ~creates ZFS file system spoon/fs, automatically mounted at /spoon/fs.
zpool list ~list pools
format ~ Disk partitioning and maintenance program
sysdef ~ Device Listing
prtvtoc ~ Disk Label
metadevadm ~ Checks device ID configuration.
metainit ~ Configures volumes.
metastat ~ Displays the status of volumes or hot spare pools.
metaset ~ Administers disk sets.
newfs –v ~ makes a UFS filesystem on disk drive or partition within a diskdrive
:: SOLUTIONS ENABLER COMMANDS :: Commands to see devices
syminq ~ list all devides seen by host OS
syminq -cids ~ list Clariion devices
syminq hba –fibre ~ list HBA
syminq –pdevfile ~List the location of devices
sympd list ~ lists the Symmetrix devices that the host OS can see
sympd list –vcm ~ lists all the physical device name in the device masking database
symdev list pd ~ lists the Symmetrix devices that the host OS can see
symdisk
Symdev Commands
symdev list ~ list all devices on symm
symdev –sa –p list ~ list devices maped to that one FA
symdev list –bcv or –rdf1 ~ list all bcv or rdf1 volumes
symdev list –noport ~ list devices not mapped to any FE ports
symdev list –clariion
symdev show 0123 -v ~ vebose listing of one device
symdev list -RANGE 0001:0123 –v ~ vebose listing of a rage of devices
symdev list pd ~ list devices this host can see
Symcfg Commands
symcfg discover ~ discover the storage environment
symcfg list ~ list local and remote symmetrixes
symcfg list –clariion ~ list clariions
symcfg list –v ~ lists whether the Symmetrix director has device masking turned on
symcfg list –FA all list ~ lists all fibre directors in a Symmetrix system
symcfg list -dir all -address -sid 6196 ~ identify the address information for devices
symcfg list -dir all -address -available ~ sid 6196 ~ returns the next available LUN address
symcfg list -lockn all ~ list of visible Symm exclusive locks
symcfg -sid 098712341357 -lockn 15 release ~ release a lock on a Symmetrix array.
Symconfigure Commands
symconfigure –sid -f preview ~ checks file to make sure it is ok to exe
symconfigure –sid -f commit ~ makes the changes from file
symconfigure –sid -f prepare
Symmaskdb Commands
symmaskdb list devs ~ lists all devices accessible to an HBA on a specified Symmetrix system
symmaskdb remove ~ removes the meta member devices
symmaskdb restore ~ restores a database from a specified file
symmaskdb backup ~ backs up a database to a specified file
symmaskdb init ~ deletes and creates a new VCMDB
symmaskdb list assignment ~lists deives already assigned
symmaskdb list no_assignment ~lists deives not yet assigned
Symmask Commands
symmask add devs ~ adds a device to the list of devices that a WWN can access in the database
symmask remove devs ~ removes a device from the list of devices that a WWN can access in the database
symmask delete ~ deletes all access rights for a WWN in the database
symmask replace ~ allows one HBA to replace another
symmask refresh ~ refresh vcmdb to all FA ports
symmask login ~ lists for each Fibre director which hosts and HBA’s are logged in to a Symmetrix system
symmask list HBA’s ~ lists the WWN of the Fibre HBAs on this host
symmask -sid 381 -wwn 50060B000024F9F6 -dir 16C -p 1 set heterogeneous on HP_UX
symmask -sid SymmID set lunoffset on offset base \ -awwn awwn -dir # -p # ~ offset high lun numbers
Other SYMCLI Commands
symsan ~list ports and LUN WWNs seen from a specific Symmetrix director and port
symdg ~ creates/deletes/renames device groups
symld ~ addes & removes devices to a deivce group
symbcv ~ associates/disassociate BCV with device groups
symmir ~ performs (split/establish/restore) BCV mirror commands against device groups
Make sure the printer name resolves (use nslookup and also do a ping test) – if that is the case you can assume that the initial printer config has been set up and the printer is on the network (ie the initial jetadmin setup etc)
Confirm that there is /etc/printcap present
su to root
then run the following;
redhat-config-printer
or
system-config-printer
you get a TUI (text user interface)
set up your printer
you can then send a test print and then you can run an
