Wednesday, May 18, 2011

Netapp upgrade 8.0.1 7 mode

So the upgrade to 8.0.1, why would you want to goto 8.0.1 (general) here is a list. Please check other sources besides Netapp as well.

https://now.netapp.com/NOW/knowledge/docs/ontap/rel801/html/ontap/rnote/GUID-5A3E2A88-F6FA-4473-8127-81ED0C39FE89.html


If already at a 8.0 (like an RC) this should be easy enough, but run the upgrade adivisor.

Step 1: 
-Download 801_q_image.tgz (from link above) and copy to the netapp filers in /etc/software. Use CIFS to mount /etc$ from the netapp
-On netapp run sofware list to confirm that the filer sees the new image
Step 2:
-Check netapp syslog messages for errors or issues on filers, stop and confirm it is ok to go ahead with upgrade with Netapp support. Suggestion is to replace failed HDDs before starting upgrade.
Step 3:
-Generate autosupport with non-disruptive as syntax:  options autosupport.doit starting_NDU
Step 4:
From the filer backup to a machine other than the netapp filer
/etc/hosts
/etc/rc 
Step 5:
On filer run 'version -b', which will show the current firmwares and ontap version on the cfcard:

/cfcard/x86_64/diag/diag.krn:  5.4.7
/cfcard/x86_64/firmware/excelsio/firmware.img: Firmware 1.7.0
/cfcard/x86_64/firmware/DrWho/firmware.img: Firmware 2.4.0
/cfcard/x86_64/firmware/SB_XV/firmware.img: Firmware 4.3.0
/cfcard/x86_64/firmware/SB_XVI/firmware.img: Firmware 5.0.0
/cfcard/x86_64/firmware/SB_XVIII/firmware.img: Firmware 7.0.1
/cfcard/boot/loader: Loader 1.7
/cfcard/common/firmware/zdi/zdi_fw.zpk: PAM II Firmware 1.8 (Build )
/cfcard/common/firmware/zdi/zdi_fw.zpk: X1936A FPGA Configuration PROM 1.0 (Build 0x201558)

Step 6 (Do this on both filers):

We start the upgrade. Cifs will break and NFS may or may not.
netappA*> software update 801_q_image.tgz -r
software: You can cancel this operation by hitting Ctrl-C in the next 6 seconds.
software: Depending on system load, it may take many minutes
software: to complete this operation. Until it finishes, you will
software: not be able to use the console.
cmd = ngsh -c system image update -node local -package file://localhost/mroot/etc/software/801_q_image.tgz -setdefault true
Software update started on node calnetapp1a. Updating image2 package: file://localhost/mroot/etc/software/801_q_image.tgz current image: image1
Listing package contents.
Untarring package contents.
Invoking script (validation phase).
INSTALL running in check only mode
Mode of operation is UPDATE
Current image is image1
Alternate image is image2
Available space on boot device is 594 MB
Required  space on boot device is 379 MB
Kernel binary matches install machine type
Package MD5 checksums pass
Versions are compatible
Invoking script (install phase). This may take up to 30 minutes.
Mode of operation is UPDATE
Current image is image1
Alternate image is image2
Available space on boot device is 594 MB
Required  space on boot device is 379 MB

Package MD5 checksums pass
Versions are compatible
Getting ready to install image
Directory /cfcard/x86_64/freebsd/image2 created
Syncing device...
Extracting to /cfcard/x86_64/freebsd/image2...
x BUILD
x CHECKSUM
x COMPAT.TXT
x INSTALL
x README.TXT
x VERSION
x cap.xml
x diags.tgz
x kernel
x perl.tgz
x platform.ko
x platfs.img
x rootfs.img
Installed MD5 checksums pass
Installing diagnostics and firmware files
Installation complete. image2 updated on node calnetapp1a
image2 has been set as the default
software: installation of 801_q_image.tgz completed.
Please type "reboot" for the changes to take effect.


Step 7: 
After installing the above on both filers
netappA> cf takeover [netappB will reboot at this time]
---------cut---------------
Wed Apr 13 22:24:55 PDT [netappA (takeover): cf.fm.takeoverComplete:notice]: Failover monitor: takeover completed
Wed Apr 13 22:24:55 PDT [netappA (takeover): cf.fm.takeoverDuration:info]: Failover monitor: takeover duration time is 6 seconds
Wed Apr 13 22:25:01 PDT [netappA (takeover): monitor.globalStatus.critical:CRITICAL]: This node has taken over netappB.
--------cut----------------

Step 8:
Netapp suggests waiting about 10 minutes between cf takeover and giveback.
netappA> cf giveback -f
--------cut----------------
Wed Apr 13 22:37:04 PDT [netappA: cf.fm.givebackComplete:notice]: Failover monitor: giveback completed
Wed Arp 13 22:37:04 PDT [netappA: cf.fm.givebackDuration:notice]: Failover monitor: giveback duration time is 3 seconds
--------cut----------------
-Run version on the filer that just rebooted and confirm the new version.

Step 9:
Do the same steps for the other filer in the cluster.

Step 10:
Check services, I found CIFS had to be restarted.

Monday, September 20, 2010

Moving Exchange 2007 CCR storage group


Scenario: Certain mail store for needs to be moved to another drive. We will move West21 Users current on D: maibox to the G:\Exchdata\West 21 Users path

Steps required:
1.Suspend storage group copy. Can be done from Exchange Management console.
2.Dismount database
3.Move Database to new path (G:\Exchdata\West 21 Users)
4.From Exchange Management Shell run:

[PS] C:\Windows\System32>move-DatabasePath -ConfigurationOnly -Identity 'west
-cms\West21 Users\West21 Mailbox' -EdbFilePath 'G:\ExchData\West21 Users\West21 Mailbox.edb' 

5. Mount new database
6. Resume storage group copy

Friday, August 6, 2010

Adding EMC SAN LUNs to RHEL 4

Adding EMC clariion LUNs to RHEL 4. EMC powerpath installed. RHEL is using local disk for boot. This SAN is for storage.

))))) Using powerpath software to display devs from SAN. (((((

[root@jasco scsi]# powermt display dev=all
Pseudo name=emcpowerb
CLARiiON ID=APM04344461 [jasco]
Logical device ID=6003534353535062D32D454F11 [LUN 57]
state=alive; policy=CLAROpt; priority=0; queued-IOs=0
Owner: default=SP A, current=SP A       Array failover mode: 1
==============================================================================
---------------- Host ---------------   - Stor -   -- I/O Path -  -- Stats ---
###  HW Path                I/O Paths    Interf.   Mode    State  Q-IOs Errors
==============================================================================
   0 qla2xxx                   sdb       SP A5     active  alive      0      0
   0 qla2xxx                   sdd       SP B4     active  alive      0      0
   1 qla2xxx                   sdf       SP A4     active  alive      0      0
   1 qla2xxx                   sdh       SP B5     active  alive      0      0

Pseudo name=emcpowera
CLARiiON ID=APM04344461 [jasco]
Logical device ID=6003534353535062D32D454F11 [LUN 56]
state=alive; policy=CLAROpt; priority=0; queued-IOs=0
Owner: default=SP B, current=SP B       Array failover mode: 1
==============================================================================
---------------- Host ---------------   - Stor -   -- I/O Path -  -- Stats ---
###  HW Path                I/O Paths    Interf.   Mode    State  Q-IOs Errors
==============================================================================
   0 qla2xxx                   sda       SP A5     active  alive      0      0
   0 qla2xxx                   sdc       SP B4     active  alive      0      0
   1 qla2xxx                   sde       SP A4     active  alive      0      0
   1 qla2xxx                   sdg       SP B5     active  alive      0      0

))))) Fdisk shows the scis disk(a-h) paths on SAN that RHEL knows. none are partitions or have file systems yet.  (((((

[root@jasco scsi]# fdisk -l

Disk /dev/sda: 21.4 GB, 21474836480 bytes
64 heads, 32 sectors/track, 20480 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes

Disk /dev/sda doesn't contain a valid partition table

Disk /dev/sdb: 429.4 GB, 429496729600 bytes
255 heads, 63 sectors/track, 52216 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/sdb doesn't contain a valid partition table

Disk /dev/sdc: 21.4 GB, 21474836480 bytes
64 heads, 32 sectors/track, 20480 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes

Disk /dev/sdc doesn't contain a valid partition table

Disk /dev/sdd: 429.4 GB, 429496729600 bytes
255 heads, 63 sectors/track, 52216 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/sdd doesn't contain a valid partition table

Disk /dev/sde: 21.4 GB, 21474836480 bytes
64 heads, 32 sectors/track, 20480 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes

Disk /dev/sde doesn't contain a valid partition table

Disk /dev/sdf: 429.4 GB, 429496729600 bytes
255 heads, 63 sectors/track, 52216 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/sdf doesn't contain a valid partition table

Disk /dev/sdg: 21.4 GB, 21474836480 bytes
64 heads, 32 sectors/track, 20480 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes

Disk /dev/sdg doesn't contain a valid partition table

Disk /dev/sdh: 429.4 GB, 429496729600 bytes
255 heads, 63 sectors/track, 52216 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/sdh doesn't contain a valid partition table

Disk /dev/emcpowerb: 429.4 GB, 429496729600 bytes
255 heads, 63 sectors/track, 52216 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/emcpowerb doesn't contain a valid partition table

Disk /dev/emcpowera: 21.4 GB, 21474836480 bytes
64 heads, 32 sectors/track, 20480 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes

Disk /dev/emcpowera doesn't contain a valid partition table


))))) Let's create a new partion with fdisk using one of the san paths. We use /dev/sdh for the 
429GB LUN. (((((


[root@jasco scsi]# fdisk  /dev/sdh
Device contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabel
Building a new DOS disklabel. Changes will remain in memory only,
until you decide to write them. After that, of course, the previous
content won't be recoverable.


The number of cylinders for this disk is set to 52216.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
   (e.g., DOS FDISK, OS/2 FDISK)
Warning: invalid flag 0x0000 of partition table 4 will be corrected by w(rite)

Command (m for help): p

Disk /dev/sdh: 429.4 GB, 429496729600 bytes
255 heads, 63 sectors/track, 52216 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System

Command (m for help): n
Command action
   e   extended
   p   primary partition (1-4)
p
Partition number (1-4): 1
First cylinder (1-52216, default 1):
Using default value 1
Last cylinder or +size or +sizeM or +sizeK (1-52216, default 52216):
Using default value 52216

Command (m for help): p

Disk /dev/sdh: 429.4 GB, 429496729600 bytes
255 heads, 63 sectors/track, 52216 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sdh1               1       52216   419424988+  83  Linux

))))) Partition is created. Goto expert mode to align partition. (((((

Command (m for help): x

Expert command (m for help): b
Partition number (1-4): 1
New beginning of data (63-838850039, default 63): 128

Expert command (m for help): w
The partition table has been altered!

Calling ioctl() to re-read partition table.
Syncing disks.

))))) Create ext3 filesystem. After this mount the file system to the path or fstab if required. (((((

[root@jasco etc]# mke2fs -j /dev/emcpowera

Done.

Increasing swap space RHEL 5

This is a Red Hat Enterprise Linux box 5 on HP blade with RAID 1 disk using LVM.

))))) Find the mount for swap (((((

[root@visce proc]# cat /etc/fstab | grep swap
/dev/VolGroup00/LogVol03 swap                    swap    defaults        0 0

))))) Current size of /swap is 8GB (((((

[root@visce proc]# lvdisplay /dev/VolGroup00/LogVol03
  --- Logical volume ---
  LV Name                /dev/VolGroup00/LogVol03
  VG Name                VolGroup00
  LV UUID                q842pi-17-vj5k-ew5F-eEZQ-MgweEb
  LV Write Access        read/write
  LV Status              available
  # open                 1
  LV Size                8.00 GB
  Current LE             256
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           253:3

))))) Turn off swap space. Make sure your server will be ok to do this on. (((((

[root@visce proc]# swapoff /dev/VolGroup00/LogVol03

))))) Increase the size of your /swap partition with LVM to 26GB in this case. Free space must exist on disk. (((((

[root@visce proc]# lvresize /dev/VolGroup00/LogVol03 -L 26000M
  Rounding up size to full physical extent 25.41 GB
  Extending logical volume LogVol03 to 25.41 GB
  Logical volume LogVol03 successfully resized

))))) Make new partition swap ready. (((((

[root@visce proc]# mkswap /dev/VolGroup00/LogVol03

))))) Swap back on. Check /proc/meminfo for new size. (((((

[root@visce proc]# swapon /dev/VolGroup00/LogVol03

Saturday, July 24, 2010

Mail for exchange "Invalid Mail for Exchange credentials. Check credential settings"

Non stop issues with nokia mail for exchange connecting with Exchange server.

1. Check for activesync enabled on the exchange server: https://www.testexchangeconnectivity.com/

2. Under mail for exchange settings, goto mailbox settings. Fill out details as required.
*make sure server name field uses https://webmail.yourserver.com

Wednesday, January 13, 2010

ITIL CSI

Continual Service Improvement:

Baytech Remote site management



DS72 EIA-232 RJ-45 Pin/Signal Definition
Pin EIA-232

1 Handshake Out (DTR) Line Driver Inactive State = High: +12V when power is applied.
Used as a handshake line to enable/disable the receiving of characters.
2 Gnd Signal ground
3 Handshake Out (RTS) Line Driver Inactive State = High: +12 V when power is applied. Not
used to enable/disable.
4 TX Out Transmit Data (data out)
5 RX In Receive Data (data in)
6 Handshake In (DSR) Handshake In. –12V when not used.
7 Gnd Signal ground
8 Handshake In (CTS) Used as a handshake line to enable/disable the receiving of
characters.