Showing posts with label SAN. Show all posts
Showing posts with label SAN. Show all posts

Thursday, November 24, 2016

Brocade SAN incoming SSH authentication not working - ssh login without password: wrong permissions on authorized_keys file

I have faced issue in FOS v7.4.1d that incoming SSH authentication (ssh login without password) did not work, even I have configured regarding to Brocade manual:
http://www.brocade.com/content/html/en/administration-guide/fos-741-adminguide/GUID-6FE6380F-52C8-4C5F-A69E-23EE7DB57E65.html 

The root cause of problem was in permissions on authorized_keys on Brocade SAN SW:

Login as root user:
ssh root@SANSW

Change directory to: /fabos/users/admin/.ssh
SANSW:root> cd /fabos/users/admin/.ssh

and list permisisons
SANSW:root> ls -la
total 32
drwxr-xr-x   2 root     admin        4096 Nov 13 17:27 ./
drwxr-xr-x   3 root     admin        4096 Sep  8 17:30 ../
-rw-r--r--   1 root     admin       10240 Nov 13 17:27 authorizedKeys.tar
-rw-------   1 root     admin         392 Nov 13 17:27 authorized_keys
-rw-------   1 root     admin         392 Nov 13 17:27 authorized_keys.admin
-rw-r--r--   1 root     admin         134 Jul 15 01:09 environment

Change permissions of authorized_keys.admin file for user admin:
SANSW:root> chmod g+r,a+r authorized_keys.admin
SANSW:root> ls -la
total 32
drwxr-xr-x   2 root     admin        4096 Nov 13 17:27 ./
drwxr-xr-x   3 root     admin        4096 Sep  8 17:30 ../
-rw-r--r--   1 root     admin       10240 Nov 13 17:27 authorizedKeys.tar
-rw-------   1 root     admin         392 Nov 13 17:27 authorized_keys
-rw-r--r--   1 root     admin         392 Nov 13 17:27 authorized_keys.admin
-rw-r--r--   1 root     admin         134 Jul 15 01:09 environment




Monday, July 20, 2015

AIX: devscan reporting and diagnostic tool for SAN devices

Are you looking for reporting and diagnostic tool for SAN devices on AIX?

Lets try IBM support tool called devscan which can report for each LUN:

  • ODM name and status
  • PVID, if there is one
  • Device type
  • Capacity and block size
  • SCSI status
  • Reservation status, both SCSI-2 and SCSI-3
  • ALUA status
  • Time to service a SCSI Read

Source and download:
https://www-304.ibm.com/support/docview.wss?uid=aixtoolsc9e095f

Tuesday, August 28, 2012

Severe latency bottleneck detected on ISL / Trunk port

How to troubleshoot error "Severe latency bottleneck detected" on ISL/trunk port?
What can cause this problem and how a root cause can be found?


I faced this problem at one of my customers.
We received this alert on trunk created from two 8Gbit ISL ports between two 5100 switches.

Here is alert message:
Time    Level    Message    Service    Number    Count    Message ID    Switch 
Mon Aug 06 2012 20:32:05 CEST    Warning    Severe latency bottleneck detected at slot 0 port 35.    Switch    1241    1    AN-1010    XSAN01

Thursday, September 15, 2011

How to find port and slot ID by index port ID shown in name server on SAN Brocade Director

When you wanna find out physical port location - slot and port ID by WWN in name server you can see just index port ID and Port# which is not as same ID as physical port ID.

If you know Index port # or port ID gathered in name server you can link it with slot and port ID by using switchshow command:

42 is index port ID, 3 is slot ID and 10 is physical port ID


SAN:admin> switchshow | grep " 42"
Index Slot Port Address Media Speed State     Proto
===================================================
 42    3   10   642a00   id    N4   Online           F-Port  10:00:00:00:00:00:00:01

Saturday, January 15, 2011

HA/Clustered SAN Storage Solution for VMware?

VMware server HA is resolved by "VMware HA" already but what's about HA on storage level?

I mean real storage HA, no single point of failure, switchover without down time, synchronous mirroring between two storages, CDP - continuous data protection.
Have you ever thought about any solution to ensure HA on storage level?
I have spent many hours, days to find out proper solution.

VMware ESX/ESXi hosts can be placed into groups called clusters. A cluster contains 2 to 32 ESX hosts that work cooperatively together to provide features such as VMware HA and DRS. All the virtual machines in this HA cluster are protected by VMware HA. VMware HA detects failures of the ESX hosts, so when an ESX host fails, VMware HA moves and restarts the virtual machines on another unaffected ESX host in the cluster. Shared storage is an important component of the solution. Since the storage array stores the virtual disks of possibly all the virtual machines, even the smallest disruption can create a wide range of effects in a storage array where availability is vital.

I've found solutions: SAN storage cluster or SAN virtualization.
Read more bellow....

Monday, January 10, 2011

IOBlazer - Storage stack micro-benchmark for VMware

How to do stress test and benchmark of storage subsystem in virtual environment?
Here is the answer: IOBlazer is storage / disk benchmark for VMware.

IOBlazer is a multi-platform storage stack micro-benchmark. IOBlazer runs on Linux, Windows and OSX and it is capable of generating a highly customizable workload.

Tuesday, December 21, 2010

Dynamic Tracking of Fibre Channel devices in AIX - PID change in Fibre Channel Fabric

Port identifiers (called PIDs) are used by the routing and zoning services in Fibre Channel fabrics to
identify ports in the network. All devices in a fabric must use the same PID format, so when you add
new equipment to the SAN, you might need to change the PID format on legacy equipment.

Many scenarios cause a device to receive a new PID; for example, unplugging the device from one
port and plugging it into a different port as part of fabric maintenance, or changing the domain ID
of a switch, which might be necessary when merging fabrics, or changing compatibility mode
settings.


AIX® 6.1 and higher supports dynamic tracking of Fibre Channel (FC) devices.
Previous releases of AIX required a user to unconfigure FC storage device and adapter device instances before making changes on the system area network (SAN) that might result in an N_Port ID (SCSI ID) change of any remote storage ports.