EMC VNX not able to see

I am having problems seeing a vnx nodes, the raid groups have been defined, the host has been added, but there is an authentication issue. I would appreciate suggestions. The host is already connected to a older clarion box, from which we look to migrate.


Thanx in advance.

Michael
###########################
# Navisphere agent.config
###########################
#
# This file is used by Navisphere Agent to configure site-specific values.
#
# All entries in this file have this form:
#
# object  value-list
#
# where "object" tells what sort of information is to be configured,
# and "value-list" is a whitespace-separated list of values to be
# configured.  Samples, which should be edited, appear below for all
# permissible types of object.
#
# White space (tabs, space, line-feeds, carriage-returns)
# and blank lines are ignored;
# To continue a line onto the next line, use "\" as
# the last character of that line.  The "\" is dropped
# when the next line is concatenated to the continued line.
#
###########################

#
# Description specification
# -------------------------
#
# The "clarDescr" object takes arbitrary text values intended to
# describe the agent and its location.
#

clarDescr Navisphere Agent

#
# The "clarContact" object takes arbitrary text values intended to
# describe who is responsible for the configured agent, and how to
# reach them.
#

clarContact John Smith, 800-555-1212

#
# Device specification
# --------------------
#
# The format of "device" objects for CLARiiON devices is:
# device	device-spec	name	"description"
#
# where the device-spec is the device name to open to access
# the CLARiiON device.  It can be a SCSI-2 file name.  If this is
# "auto", all attached arrays with bound LUNs will be automatically
# configured.  (Currently, dummy arguments are required for name
# and description, when using auto-configuration.)  This can NOT
# be defaulted.
#
# The name is the per-CLARiiON name that can be used to identify each
# CLARiiON to the manager application.  The name is REQUIRED and cannot
# contain spaces (even if surrounded by quotes).  This can NOT
# be defaulted.
#
# The description is a quoted string that contains a brief description
# of the CLARiiON chassis being managed.  It defaults to "" if not
# specified, and to the device name for auto-configuration.
#

# SAMPLES:
#device sga NAVISPHERE-8 "NAVISPHERE-8"
#device sgb NAVISPHERE-1 "NAVISPHERE-1"
#device sgc NAVISPHERE-2 "NAVISPHERE-2"
#device sgd NAVISPHERE-3 "NAVISPHERE-3"
#device sge NAVISPHERE-4 "NAVISPHERE-4"
#device sgf NAVISPHERE-5 "NAVISPHERE-5"
#device sgg NAVISPHERE-6 "NAVISPHERE-6"
#device sgh NAVISPHERE-7 "NAVISPHERE-7"
#device sg0 NAVISPHERE-0 "NAVISPHERE-0"
#device sg1 NAVISPHERE-1 "NAVISPHERE-1"
#device sg2 NAVISPHERE-2 "NAVISPHERE-2"
#device sg3 NAVISPHERE-3 "NAVISPHERE-3"
#device sg4 NAVISPHERE-4 "NAVISPHERE-4"
#device sg5 NAVISPHERE-5 "NAVISPHERE-5"
#device sg6 NAVISPHERE-6 "NAVISPHERE-6"
#device sg7 NAVISPHERE-7 "NAVISPHERE-7"

# automatically detect manageable devices
device auto auto

#
# User Specification.
# ------------------
#
# The format of "user" objects is:
#       user localUserId
# OR
#       user userId@hostname
#
# These build a list of users who are allowed to perform WRITE
# operations to the CLARiiON devices managed by this agent.  By
# default, as specified below, only root on this machine has WRITE
# access.  Others can be granted access by including their login name
# and host which they can access from.  A null list prevents anyone,
# including admin, from having write access.  In order to get write
# access, this file would have to be modified and the Agent stopped
# and restarted to re-read the configuration file, or an appropriate
# remote configuration request would have to be sent to the agent from
# an already-privileged user.
#

#user root              # only on this machine
#user sblue@picasso    # individual user "sblue" on host "picasso"
#user lgreen@hannibal  # individual user "lgreen" on host "hannibal"

system@192.168.33.150
system@192.168.33.151
system@192.168.33.160
system@192.168.33.161

#
# Poll Specification
# ------------------
#
# The "poll" object takes a numerical count of seconds.
#
# This specifies how often the agent solicits information from the
# array, rather than using cached information.  The minimum is "10".
#

poll 60

#
# Eventlog Specification
# ----------------------
#
# The eventlog object takes a numerical count of log entries.
#
# This defines the maximum number of SP log events received by the
# agent on startup, and received by clients per poll.  A value of 0
# causes the device's entire log to be read at startup.  A minimum
# of 100 events will be read on serial, and 2048 on fibre, overriding
# any lower value configured below.
#

eventlog 100

#
# Baud Rate Specification
# ----------------------
#
# If the agent is using a serial port to manage a device, the next entry can 
# specify either 9600 baud or 19200 baud.
#

baud 9600

#linux currently can't handle this
#nomegapoll

###
# end of configuration file
###

Open in new window

dpoper1Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Duncan MeyersCommented:
Have you got:

user system@<IP address of SPA of the VNX>
user system@<IP address of SPB of the VNX>

I see that you have two arrays in there already - if that's both arrays then you'll need to add the VNX entries to all hosts.
0
dpoper1Author Commented:
Hi Meyerd,

At the moment, I am testing a single node, and I have added the 2 EMC machines .160 & .161. I have updated the agent, restarted and attempted to register the host with:

/opt/Navisphere/bin/navicli -h 192.168.33.160 register

Do you have any other suggestions that I could try out. Please let me know.

Regards,

Michael
0
dpoper1Author Commented:
I am getting this error:

Error returned from Agent
Agent denied request -- Caller not privileged.
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

dpoper1Author Commented:
Also, I am running a very old OS  2.6.9-42.ELsmp Redhat 4.X, and I need to make it work with this software.
0
Duncan MeyersCommented:
Caller not privileged usually refers to issues with inconsistent user entries in agent.config...

Got it. Your system@... Entries are wrong. Add "user" at the start of each line as shown in my previous post so:
user system@...

You've got:
System@...
0
dpoper1Author Commented:
Please find attached the new agent.conf file, and I still get the same authentication error, for the previous system, the system@... works just fine, is the new vnx5300 which is giving me a hard time. I would appreciate any suggestions.

Regards,

Michael
###########################
# Navisphere agent.config
###########################
#
# This file is used by Navisphere Agent to configure site-specific values.
#
# All entries in this file have this form:
#
# object  value-list
#
# where "object" tells what sort of information is to be configured,
# and "value-list" is a whitespace-separated list of values to be
# configured.  Samples, which should be edited, appear below for all
# permissible types of object.
#
# White space (tabs, space, line-feeds, carriage-returns)
# and blank lines are ignored;
# To continue a line onto the next line, use "\" as
# the last character of that line.  The "\" is dropped
# when the next line is concatenated to the continued line.
#
###########################

#
# Description specification
# -------------------------
#
# The "clarDescr" object takes arbitrary text values intended to
# describe the agent and its location.
#

clarDescr Navisphere Agent

#
# The "clarContact" object takes arbitrary text values intended to
# describe who is responsible for the configured agent, and how to
# reach them.
#

clarContact John Smith, 800-555-1212

#
# Device specification
# --------------------
#
# The format of "device" objects for CLARiiON devices is:
# device	device-spec	name	"description"
#
# where the device-spec is the device name to open to access
# the CLARiiON device.  It can be a SCSI-2 file name.  If this is
# "auto", all attached arrays with bound LUNs will be automatically
# configured.  (Currently, dummy arguments are required for name
# and description, when using auto-configuration.)  This can NOT
# be defaulted.
#
# The name is the per-CLARiiON name that can be used to identify each
# CLARiiON to the manager application.  The name is REQUIRED and cannot
# contain spaces (even if surrounded by quotes).  This can NOT
# be defaulted.
#
# The description is a quoted string that contains a brief description
# of the CLARiiON chassis being managed.  It defaults to "" if not
# specified, and to the device name for auto-configuration.
#

# SAMPLES:
#device sga NAVISPHERE-8 "NAVISPHERE-8"
#device sgb NAVISPHERE-1 "NAVISPHERE-1"
#device sgc NAVISPHERE-2 "NAVISPHERE-2"
#device sgd NAVISPHERE-3 "NAVISPHERE-3"
#device sge NAVISPHERE-4 "NAVISPHERE-4"
#device sgf NAVISPHERE-5 "NAVISPHERE-5"
#device sgg NAVISPHERE-6 "NAVISPHERE-6"
#device sgh NAVISPHERE-7 "NAVISPHERE-7"
#device sg0 NAVISPHERE-0 "NAVISPHERE-0"
#device sg1 NAVISPHERE-1 "NAVISPHERE-1"
#device sg2 NAVISPHERE-2 "NAVISPHERE-2"
#device sg3 NAVISPHERE-3 "NAVISPHERE-3"
#device sg4 NAVISPHERE-4 "NAVISPHERE-4"
#device sg5 NAVISPHERE-5 "NAVISPHERE-5"
#device sg6 NAVISPHERE-6 "NAVISPHERE-6"
#device sg7 NAVISPHERE-7 "NAVISPHERE-7"

# automatically detect manageable devices
device auto auto

#
# User Specification.
# ------------------
#
# The format of "user" objects is:
#       user localUserId
# OR
#       user userId@hostname
#
# These build a list of users who are allowed to perform WRITE
# operations to the CLARiiON devices managed by this agent.  By
# default, as specified below, only root on this machine has WRITE
# access.  Others can be granted access by including their login name
# and host which they can access from.  A null list prevents anyone,
# including admin, from having write access.  In order to get write
# access, this file would have to be modified and the Agent stopped
# and restarted to re-read the configuration file, or an appropriate
# remote configuration request would have to be sent to the agent from
# an already-privileged user.
#

user root              # only on this machine
#user sblue@picasso    # individual user "sblue" on host "picasso"
#user lgreen@hannibal  # individual user "lgreen" on host "hannibal"

user system@192.168.33.150
user system@192.168.33.151
user system@192.168.33.160
user system@192.168.33.161

#
# Poll Specification
# ------------------
#
# The "poll" object takes a numerical count of seconds.
#
# This specifies how often the agent solicits information from the
# array, rather than using cached information.  The minimum is "10".
#

poll 60

#
# Eventlog Specification
# ----------------------
#
# The eventlog object takes a numerical count of log entries.
#
# This defines the maximum number of SP log events received by the
# agent on startup, and received by clients per poll.  A value of 0
# causes the device's entire log to be read at startup.  A minimum
# of 100 events will be read on serial, and 2048 on fibre, overriding
# any lower value configured below.
#

eventlog 100

#
# Baud Rate Specification
# ----------------------
#
# If the agent is using a serial port to manage a device, the next entry can 
# specify either 9600 baud or 19200 baud.
#

baud 9600

#linux currently can't handle this
#nomegapoll

###
# end of configuration file
###

Open in new window

0
dpoper1Author Commented:
Now, should I need to create the user system on the EMC machine, because it does not exist.

Thanks
0
Duncan MeyersCommented:
D'oh!!

It's a VNX so running FLARE 30 or 31 which disable access from navicli - you should install and use naviseccli on the box that's connecting
To the VNX. You also need to add the administrator username and password to every command string or you can create a security file for the host.

It's also possible (IIRC) to enable classic navicli access on the VNX but you're better off using naviseccli.
0
Duncan MeyersCommented:
In Unisphere, go to Settings - Security - Security Settings - Enable/Disable Classic CLI
0
dpoper1Author Commented:
I have already tried using

./naviseccli -h 192.168.33.160 -addusersecurity -user system -password password -scope 1,

I did not get anything back, but when I checked the gui, I did not see the recently created userid/password.

I do not see an option to enable/disable the Classic CLI
0
Duncan MeyersCommented:
Try scope 0
0
dpoper1Author Commented:
According to the post:

http://storage.ittoolbox.com/groups/technical-functional/emc-l/error-on-navi-cli-script-4213081

it will explain what 0,1 & 2 are for, I have attempted re-adding the same userid and it will not take it.
0
Duncan MeyersCommented:
You may now need to reset up the domain ad domain security and create a new administrator user.
0
dpoper1Author Commented:
It has 1 global user and 1 local user, the local user is the one that I just created. How would I be able to register using the:

 /opt/Navisphere/bin/navicli -h 192.168.33.160 register

string with password.

Thanks
0
etaljicCommented:
What are you trying to do on that host? Are you trying to run naviseccli commands?

The username is sysadmin and not system. The agent file has nothing to do with naviseccli. If you want to run naviseccli commands from the host you need to create a security file on that host so that you can run the commands. Run this:

./naviseccli -h 192.168.33.160 -addusersecurity -user sysadmin -password sysadmin -scope 0
./naviseccli -h 192.168.33.161 -addusersecurity -user sysadmin -password sysadmin -scope 0

To test and make sure the security file was generated run: ./naviseccli -h 192.168.33.160 getagent
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
dpoper1Author Commented:
My question was never resolved to its fully extend. I do appreciate the input anyways
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Storage

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.