Basic Commands in AIX auditing
http://www.blogger.com/profile/05365174810038891856
|
|
comments (0)
|
Steps to clone OS disks
• Install the REM modules
• Discover the local disks
• Reboot and boot from live CD KNOPPIX
• Use cfdisk to list the san disks layout
• Rebuild the local disk to be the same with the san disks layout using cfdisk. In this case change the FS type to LVM.
• Make boot device bootable by changing the flag type
• Cross check and ensure that both device have the same file system type using cfdisk command as well as fdisks.
• Use dd to copy from san device to local disks ( This should take a while)
• Power off the server and disconnect the san disks
• Power on the server and boot from local disks
This work plan is only for cloning the SAN disks to a local disks
|
|
comments (0)
|
#Display current
powermt display
#Scan in devices
echo '- - -' > /sys/class/scsi_host/host3/scan
echo '- - -' > /sys/class/scsi_host/host4/scan
echo '- - -' > /sys/class/scsi_host/host5/scan
echo '- - -' > /sys/class/scsi_host/host6/scan
#Configure to EMC names
powermt config
powermt save
#Display new
powermt display
|
|
comments (0)
|
627 cd /boot/
628 vim grub/grub.conf (rd_NO_DM rdloaddriver=ql2300_stub)
629 uname -r
630 cat grub/grub.conf
631 lsinitrd initramfs-2.6.32-131.21.1.el6.x86_64.img
632 lsinitrd initramfs-2.6.32-131.21.1.el6.x86_64.img|more
641 dracut -f --omit "lpfc qla4xxx qla2xxx" "initramfs-$(uname -r).image" $(uname -r)
657 mkinitrd -f --with=windrvr6 initramfs-2.6.32-131.21.1.el6.x86_64.img `uname -r`
659 lsinitrd initramfs-2.6.32-131.21.1.el6.x86_64.image|more
660 lsinitrd initramfs-2.6.32-131.21.1.el6.x86_64.image|grep -i ql
662 init 6
666 lsmod |grep -i qla2xxx
|
|
comments (0)
|
addboard -d N SB11
addboard -d N IO11
addboard -d A -c assign SB2 SB4 SB7(any)
deleteboard -c unassign SB2(to delete a board)
deleteboard -c unassign IO3
addtag -d A domainA
deletetag -d domain_id
showkeyswitch -d A
setkeyswitch -d domain_id position (on)
/export/install/SOL_10_0509_SPARC/Solaris_10/Tools
./add_install_client vnl-25k2-b sun4u
boot net - install
|
|
comments (0)
|
|
|
comments (0)
|
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
|
|
comments (0)
|
check the LUN
# /opt/NTAP/SANToolkit/bin/sanlun lun show all|grep Callhistory-Lungrow
Go to format..
Then
# vxdctl enable
# vxdisk scandisks
it will be online status with the number Disk_179
# vxdisksetup -i -f Disk_179 [ -f option for if it assigned previously in any disk group ]
#vxdg init EMC_ESCDG ESCDG01=emcpower1s2
#vxdg -g EMC_ESCDG adddisk ESCDG02=emcpower2s2
# vxdg -g tdwdg adddisk Disk_179=Disk_179
check the mount point primary node
# fsclustadm -v showprimary /ccbs/oradata/u01 2
tabsdb01
check the master node
# vxdctl -c mode
mode: enabled: cluster active - MASTER
master: tabsdb01
vxassist -g EMC_ESCDG make workvol 15g [ alloc="emcpower1s2 emcpower3s2" ]
mkfs -F vxfs /dev/vx/rdsk/EMC_ESCDG/workvol
mount -F vxfs /dev/vx/dsk/EMC_ESCDG/workvol /emc/med/work
Increase the ORAvol01 100g [prev size was 400g, new size will be 500g]
# vxresize -F vxfs -g EMC_ESCDG workvol +100g
check the DG total space
# vxassist -g ORAdg maxsize
Maximum volume size: 209448960 (102270Mb)
#########################################################3
check the LUN
# /opt/NTAP/SANToolkit/bin/sanlun lun show all|grep Callhistory-Lungrow
Go to format..
Then
# vxdctl enable
# vxdisk scandisks
it will be online status with the number Disk_179
# vxdisksetup -i Disk_179 [ -f for force ]
vxdg -g EMC_ESCDG adddisk ESCDG02=emcpower2s2
fsclustadm -v showprimary /ccbs/oradata/u01
vxdctl -c mode [ check the master node ]
vxresize -F vxfs -g EMC_ESCDG workvol +100g
|
|
comments (0)
|
The first thing to do when configuring a quota is to creat a partition
Then make a file system
You can make it parmanet by adding an entry in the fstab
Now create a use for the quota
To verify
|
|
comments (0)
|
You can use the GUI.
/usr/sadm/admin/bin/printmgr &
Please note the gui gives you more simpler way of configuring print in linux, it is explaninatory
Basic commands
#lp -d lloyd >> lloyd is the printer name
#lpadmin -x lloyd >> to remove a printer
#reject printer(printer name)
#enable/disable printer
#lpmove printer1 printer2
#lpadmin -p printer -c >>>> (class)
#lpstat -p printername
#cancel printer
As a system admin you can deny or allow a printer
vi /etc/lp/printer/printername/users-all/deny
lpadmin -p printer -u deny:users
To start and stop a print service
#svcadm enable -t print >>>solaris
#service print start
|
|
comments (0)
|
Zone IntroductionZones are containers to segregate services so that they do notinterfere with each other. One zone, the global zone, isthe locus for system-wide administrative functions. Non-globalzones are not able to interact with each other except throughnetwork interfaces. When using management commands that reference PIDs, only processes in the same zone will be visible from any non-global zone.
Zones requiring network connectivity have at least onededicated IP address. Non-global zones cannot observeeach other's network traffic. Users in the global zone, however,are able to observe the functioning of processes in non-globalzones. It is usually good practice to limit user access tothe global zone to system administrators. Other processes and users should be assigned to a non-global zone.
Each zone is assigned a zone name and a unique numeric zone ID.The global zone always has the name "global" and ID "0."A node name is also assigned to each zone, including global.The node names are independent of the zone names.
Each zone has a path to its root directory relative to theglobal zone's root directory.
A non-global zone's scheduling class is set to be the same as the system's scheduling class. Ifa zone is assigned to a resource pool, its scheduling class can be controlled by controlling the pool's scheduling class.
Non-global zones can have their own zone administrators. Their authority is limited to their home zone.
The separation of the environments allows for bettersecurity, since the security for each zone is independent.Separation also allows for the installation ofenvironments with distinct profiles on the samehardware.
The virtualization of the environment makes it easierto duplicate an environment on different physicalservers.
ZFS is supported in Solaris10 zones from the 6/2006 release and after.
Zone InstallationThe system administrator configures new non-global zonesvia the zonecfg command, administers themviazoneadm and logs into them viazlogin.
Zone StatesZone state information can be viewed withzoneadm list -iv from the global zone.Non-global zones have one of the following states:
configured: Configuration complete and in stable storage.incomplete: Installation or uninstallationunderwayinstalled: Configuration instantiatedon system. Zone has no associated virtual platform.ready: Virtual platform established,zsched started,IPs plumbed, filesystems mounted, zone ID assigned.No zone processes started yet.running:
This state entered when zoneinit process starts.shutting down: Zone being halted.down: Transitional state during zoneshutdown.Zone Control CommandsThe following control commands can be used to manage and monitor transitions between states:
zlogin options
zone-namezoneadm -z zone-name bootzoneadm -z zone-name haltzoneadm -z zone-name installzoneadm -z zone-name readyzoneadm -z zone-name rebootzoneadm -z zone-name uninstallzoneadm -z zone-name verifyzonecfg -z zone-name: Interactive mode;can be used to remove properties of the following types: fs, device, rctl, net, attrzonecfg -z zone-name commitzonecfg -z zone-name createzonecfg -z zone-name deletezonecfg -z zone-name verifyResource ManagementZones can be used to dynamically control resource allocations on a zone basis. This means that an applicationon a zone can be isolated and prevented from throttling other processesin other zones on the same server.
Zone ComponentsThe following components may be included in a zone:
Zone namezonepath: Path to the zone root in the globalzone's file space.autoboot: Whether to start the zone automatically.(Note that the svc:/system/zones:default service needsto be running in SMF for this to work.)pool: Associate the zone with a resource pool; multiple zones may share a pool.net: Zone network interfacefs: File systems from the zone's /etc/vfstab, automounted file systems configured within the zone, manually mounted file systems or ZFS mounts from within the zone.dataset: This allows a non-global zone to manage a ZFS file system.inherit-pkg-dir: In a sparse root zone, representsdirectories containing packaged software that a non-global zoneshares with the global zone. (Should not be used in a whole rootzone.)device: Devices that should be configuredin a non-global zone.rctl: Zone-wide resource controls such as zone.cpu-shares andzone.max-lwpsattr: Zone commentsThe components can be set using the zonecfg command.zonecfg Interactive ModeIn interactive mode, zonecfg can refer to eithera global scope or a specific resource. If no zone is specified inthe original zonecfg command, the scope is globalby default.
If a select or add subcommand isused to specify a resource, the scope limited to that resourceuntil an end or cancel command isissued.
The following subcommands are supported:
(See Resource Management forinformation about what sorts of values to use.)
Zone ModelsThere are two different zone models, sparse and whole root.
Sparse zones only contain a subset of the packages installed intothe root zone. Additional packages can be brought in usingthe inherit-pkg-dirresources. Each sparse zone requires about 100MB of free spacein the global file system. 40MB of free RAM are also recommended.
Whole root zones contain all required packages and also anyoptional Solaris packages that have been selected. The diskspace required for whole root zones is as much as is requiredfor a full installation. Whole root zones allow maximum configurationwithin the zone context.
mkdir zonename
chmod 777 zonename