Manager agent will not register host with CX

Source: Internet
Author: User
Tags failover ftp site

Manager agent will not register host with clariion Array


Primus self-service

EMC Knowledgebase

"Manager agent will not register host with clariion array"
ID: Emc125015
Usage: 70
Date created: 12/30/2005
Last modified: 06/13/2006
Status: Approved
Audience: Customer
   
Knowledgebase Solution  
Question: How to register a host in manager with manager agent
Environment: Product: clariion CX-Series
Environment: OS: Solaris
Environment: OS: HP-UX
Environment: OS: IBM AIX
Environment: OS: Microsoft Windows
Environment: OS: Linux
Environment: Host adapter: Emulex
Environment: Host adapter: Qlogic
Problem: Hbas log in to connectivity status but do not register with the host name.
Problem: Host does not register with clariion array.
Problem: Restarting the manager agent does not register the host. See
Emc95542
("How to restart manager agent ").
Root cause: Host
Registration to a clariion array is done in band, that is, through
Fibre channel connection. In order for a host to register successfully
A lunz device must be successfully presented to the host for every path
That is zoned to the array. A lunz is a logical device that allows
Host software, that is, the manager agent to pass commands to
Array. lunz takes the place of Hlu 0 until real physical storage is
Allocated. The lunz devices are created based on the arraycommp ATH
Setting in manager. See Solution

Emc65060
("What Is lun_z or lunz ").
Fix: All host platforms

  1. Verify the agent. config file has the following entries. 
    See
    Emc101128
    For host location.
     
    • Device auto
    • User System @ <Ip_spa
      >
    • User System @ <Ip_spb
      >
       
  2. Verify that the manager agent release running on the host
    Is within two revisions of the flare code release running on the array.
  3. In order for the host to be a managed host on the clariion array it
    Must be in the same subnet as the clariion array. See Solution
    Emc69147
    For a list of TCP Service ports required for manager agent and SP agent communication.

Sun Solaris

Emulex hbas

Verify the following conditions have been met:

  • Persistent bindings have been set up in the lpfc. conf file. See Solution
    Emc53265
    ("How to set up persistent bindings with lputil ").
     
    • FCP-bind-wwpn = "5006016023e4578a: lpfc0t16 ",
    • "5006016823e4578a: lpfc0t17 ";
       
  • The SD. conf file has been set up to reflect the lpfc. conf file.
     
    • Luns for lpfc0 Target 16
    • Name = "SD" class = "lpfc" target = 16 Lun = 0;
    • Name = "SD" class = "lpfc" target = 16 Lun = 1;
    • Etc ....
    • Luns for lpfc0 Target 17
    • Name = "SD" class = "lpfc" target = 17 Lun = 0;
    • Name = "SD" class = "lpfc" target = 17 Lun = 1;
    • Etc ....

What is important is making sure that you have a lun 0 set up
The targets established in the lpfc. conf file. If the above is true,
TheFormat
Command shocould show some devices listed
"Drive type unknown." These are the lunz devices. At this point
Restarting the agent shocould register the host. If you do not see
Lunz devices, check the zoning or the host may needReboot ---R
Or both.

Sun-branded Qlogic cards (Leadville ):

Apply the following procedure:

Add the required system variable in the/etc/system file.

  1. Set FCP: ssfcp_enable_auto_configuration = 1
  2. Reboot ---R

If this variable is already in place, follow these steps:

  1. Check manager connectivity status to make sure all paths are maid in.
  2. On the Solaris host runCfgadm.
  3. On the Solaris host runDevfsadm.
  4. CheckFormat
    To make sure that the lunz devices are now available.
  5. Restart the manager agent on the host.

Linux

Emulex or Qlogic hbas:

The following must be verified on the host:

  • The/Etc/hostfile
    Has only one entry: The Host Name and IP address
  • TheHostidfile.txt
    Shows the correct IP address followed by a date stamp
  • A lunz device is seen on every path to the array in/Proc/SCSI
    File. If it is not, check zoning and reboot the host.

Note:
If you useQlogic hbas
, Make sure that failover is disabled for those hbas. Make sure thatQl2xfailover
And
Configreguired
Parameters are set to 0 in/Etc/modprobe. conf
File as shown in the following entry:

Options qla2xxx ql2xfailover = 0 configrequired = 0


Try applying the following procedure:

  1. DeleteHostidfile.txt
    And restart the Manager Host agent.
  2. Reboot the host.
  3. Restart management server on the array. (in a browserSp_ip/setup => restart Mgmt Server
    .)

If above fails, follow these steps:

  1. Manually register the host in manager withGroup Edit
    Button inConnectivity status.
  2. Add host and Luns to the storage group.
  3. Restart the manager agent or reboot the host.

When manually registering, the host will show "(manually
Registered) "next to its name in manager. After restarting
Agent on the host the "(manually registered)" entry will disappear and
The host will now be managed.

Also see Solution
Emc115979
("Registering Linux host using Manager Host agent") and Solution
Emc60655
("How to manually register an HbA in Red Hat Linux Server ").

HP-UX

HP hbas

Note:
Even if zoning is correct, unlike other operating systems you will not see the hba wwn logging in to connectivity status.

Apply the following procedure:

  1. Make sure that DNS is enabled in the/etc/nsswitch. conf file!
  2. RunIoscan-FNC Disk
    (Scan the SCSI bus for any SCSI devices)

    Note: Make sure that you see lunz devices. If you do not, verify the zoning.
     

  3. RunInsf-e
    . (Build the special device files for the lunz devices .)
  4. Restart the Manager Host agent. (push the information to the array through the newly built lunz devices .)

Note:
Even when the host registers it will still
Show maid in: No. This is normal for HP-UX. It will turn
Yes When I/O is going to the allocated devices. See Solution
Emc99131
("HP-UX HbA does not appear as 'logged in 'from Manager ").

If using only pvlinks, verify the following:

  • The agent. config file has an "optionssupported autotrespass (uncommented)" entry.
  • The initiator type in Manager shocould be set to "HP auto trespass ."

If using powerpath, verify the following:

  • The agent. config file has an "# optionssupported autotrespass" entry.
  • The initiator type in Manager shocould be set to "HP no-auto trespass ."

IBM AIX

IBM branded Emulex hbas

Caution!
Verify the clariion ODM definitions are installed. They are available on
EMC's FTP site
.

  1. RunCfgmgr
    (You may not see the host logged in until you scan the bus with your Mgr .)
  2. TypeLsdev-CC disk | grep lunz
  3. If there are no lunz devices, check the zoning.
  4. Restart the Manager Host agent to register the host.
  5. Rmdev-DL hdisk
    N

    WhereN
    Is the hdisk # For the lunz Devices
  6. In Manager useTools
    =>Failover Setup Wizard
    To disable arraycommp ath for this host.

Note:
Lunz devices on AIX can fill the error report
With scsi_disk Error 2's. Since arraycommp ATH is the setting that is
Used to present the lunz, it is recommended that you disable this
Setting on the chance the Hlu 0 is removed from the storage group in
The future. See Solution

Emc111635
("How to remove lunz devices ").

Microsoft Windows

Emulex or Qlogic hbas

  1. Check disk management and make sure you see unknown/unreadable devices.
    • If not, check the zoning.
    • If the zoning appears to be perfect, the host may need to be rebooted.
  2. Restart the Manager Host agent (located in Windows Services ).

Note:
If using Emulex cards with the scsi fc port driver, follow these steps:

  1. Open a cmd window and CD intoC:/program files/hbanyware
    Directory.
  2. Type:Elxcmd.exe -- EMC
  3. Highlight the adapter instance and selectConfiguration => set
  4. Select the appropriate setting. (This will require a reboot to take affect .)

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.