fmadm on an M4000

Hi people,
Hoping someone has maybe done this before?

I'm trying to run fmadm from the xcsf prompt on an M4000 and it won't run, complaining about insufficient privileges, even though the user has supposedly been setup with fieldeng privileges.

Anyone got any ideas?

Cheers

Rgrds

Martin

have you tried a user with more privileges?

Hi Duke,
Were new to these beasts, we setup a user with fieldeng privelidges, thought that was all you needed.

Do you know what others there are?

Thanks

Martin

how about the fine documentation?

XSCF Overview

Looked at the documentation, gave the user platadm and fieldeng privileges and still says insufficient privileges when you run fmadm faulty -a

Does anyone have any more ideas?

Thanks

Martin

for a superadmin i would give:

  • platadm
  • useradm
  • auditadm
  • fieldeng
  • mode

Added those duke and still get insufficient privileges or mode when I try to run fmadm.

I think even god himself with have trouble with this one. lol

what is you FW level?

version -c xcp

---------- Post updated at 15:14 ---------- Previous update was at 15:04 ----------

also note, you give wrong syntax for fmadm command:

NAME fmadm - fault management configuration tool
SYNOPSIS fmadm [-q] config
fmadm -h
DESCRIPTION fmadm (8) can be used to view system configuration parameters related to fault
management.
fmadm can be used to:
 View the set of diagnosis engines and agents that are currently participating in
fault management
 View the list of system components that have been diagnosed as faulty
The Fault Manager attempts to automate as many activities as possible, so use of
fmadm is typically not required. When the Fault Manager needs help from a human
administrator or service representative, it produces a message indicating its needs.
It also refers you to a URL containing the relevant knowledge article. The web site
might ask you to use fmadm or one of the other fault management utilities to gather
more information or perform additional tasks. The documentation for fmdump(8)
describes more about tools to observe fault management activities.
Privileges You must have platop, platadm, or fieldeng privileges to run this command.
Refer to setprivileges(8) for more information.
OPTIONS The following options are supported.
OPERANDS The following operands are supported:
-h Displays usage statement.
When used with other options or operands, an error occurs.
-q Sets quiet mode. fmadm does not produce messages indicating the
result of successful operations to standard output.
config Displays the configuration of the Fault Manager itself, including
the module name, version, and description of each component
module. Fault Manager modules provide services such as
automated diagnosis, self-healing, and messaging for hardware
and software present on the system.

EXAMPLES EXAMPLE 1 Displaying the Fault Manager Configuration
EXIT STATUS The following exit values are returned:
SEE ALSO fmdump(8), fmstat(8)
XSCF> fmadm config
MODULE VERSION STATUS DESCRIPTION
case-close 1.0 active Case-Close Agent
fmd-self-diagnosis 1.0 active Fault Manager Self-Diagnosis
sysevent-transport 1.0 active SysEvent Transport Agent
syslog-msgs 1.0 active Syslog Messaging Agent
0 Successful completion.
>0 An error occurred.

You never stated what command you are trying to run.

There appears to be limited choices in the XSCF for the fmadm command.

fujitsu.com/downloads/SPARCE/manuals/sparc-commone/mx-xscfref-en-03.pdf

it states that " You must have platop, platadm, or fieldeng privileges to run this command. "

I hope I'm not asking a really dumb question :o but after you added the privileges did you log out and log in again?

all is said in his posts... he tries to run fmadm like in solaris, see post #5:

fmadm faulty -a

this is simply NOT possible! the output was:

insufficient privileges or mode

in his case he just used a wrong syntax or mode as the output stated. the only way to run the fmadm command from the xscf is:

fmadm [-q] config
fmadm -h

see post #8 with the output from the xscf manual!