Skip to main content

Sun MgmtCard

Connector dependencies​

The following monitoring connectors will be installed when you install the Sun MgmtCard connector through the Configuration > Connectors > Monitoring Connectors menu:

Pack assets​

Templates​

The Monitoring Connector Sun MgmtCard brings 9 host templates:

  • HW-Server-Sun-Alom-TELNET-custom
  • HW-Server-Sun-Alom4v-SSH-custom
  • HW-Server-Sun-Ilom-IPMITOOL-custom
  • HW-Server-Sun-Ilom-SSH-custom
  • HW-Server-Sun-Mseries-SSH-custom
  • HW-Server-Sun-Sf2xx-TELNET-custom
  • HW-Server-Sun-Sfxxxx-TELNET-custom
  • HW-Server-Sun-V4xx-TELNET-custom
  • HW-Server-Sun-V8xx-TELNET-custom

The connector brings the following service templates (sorted by the host template they are attached to):

Service AliasService TemplateService Description
HardwareHW-Sun-MgmtCard-Showenvironment-TELNET-customCheck Sun vXXX (v240, v440, v245,...) Hardware (through ALOM)

The services listed above are created automatically when the HW-Server-Sun-Alom-TELNET-custom host template is used.

Collected metrics & status​

Here is the list of services for this connector, detailing all metrics and statuses linked to each service.

NameUnit
statusN/A

Prerequisites​

You need to install the necessary dependencies based on the chosen communication mode (Telnet, SSH, or IPMI) and configure the access credentials.

Installing the monitoring connector​

Pack​

The installation procedures for monitoring connectors are slightly different depending on whether your license is offline or online.

  1. If the platform uses an online license, you can skip the package installation instruction below as it is not required to have the connector displayed within the Configuration > Connectors > Monitoring Connectors menu. If the platform uses an offline license, install the package on the central server with the command corresponding to the operating system's package manager:
dnf install centreon-pack-hardware-servers-sun-mgmtcards
  1. Whatever the license type (online or offline), install the Sun MgmtCard connector through the Configuration > Connectors > Monitoring Connectors menu.

Plugin​

Since Centreon 22.04, you can benefit from the 'Automatic plugin installation' feature. When this feature is enabled, you can skip the installation part below.

You still have to manually install the plugin on the poller(s) when:

  • Automatic plugin installation is turned off
  • You want to run a discovery job from a poller that doesn't monitor any resource of this kind yet

More information in the Installing the plugin section.

Use the commands below according to your operating system's package manager:

dnf install centreon-plugin-Hardware-Servers-Sun-Mgmtcards

Using the monitoring connector​

Using a host template provided by the connector​

  1. Log into Centreon and add a new host through Configuration > Hosts.
  2. Fill in the Name, Alias & IP Address/DNS fields according to your resource's settings.
  3. Apply the HW-Server-Sun-Alom-TELNET-custom template to the host. A list of macros appears. Macros allow you to define how the connector will connect to the resource, and to customize the connector's behavior.
  4. Fill in the macros you want. Some macros are mandatory.
MacroDescriptionDefault valueMandatory
TELNETUSERNAMEssh username
SSHUSERNAMEssh username
TELNETPASSWORDssh password
SSHPASSWORDssh password
TELNETPORTtelnet port (default: 23)23
TELNETEXTRAOPTIONSAny extra option you may want to add to every command (a --verbose flag for example). All options are listed here.
  1. Deploy the configuration. The host appears in the list of hosts, and on the Resources Status page. The command that is sent by the connector is displayed in the details panel of the host: it shows the values of the macros.

Using a service template provided by the connector​

  1. If you have used a host template and checked Create Services linked to the Template too, the services linked to the template have been created automatically, using the corresponding service templates. Otherwise, create manually the services you want and apply a service template to them.
  2. Fill in the macros you want (e.g. to change the thresholds for the alerts). Some macros are mandatory (see the table below).
MacroDescriptionDefault valueMandatory
EXTRAOPTIONSAny extra option you may want to add to the command (a --verbose flag for example). All options are listed here.--verbose
  1. Deploy the configuration. The service appears in the list of services, and on the Resources Status page. The command that is sent by the connector is displayed in the details panel of the service: it shows the values of the macros.

How to check in the CLI that the configuration is OK and what are the main options for?​

Once the plugin is installed, log into your Centreon poller's CLI using the centreon-engine user account (su - centreon-engine). Test that the connector is able to monitor a resource using a command like this one (replace the sample values by yours):

/usr/lib/centreon/plugins/centreon_sun_mgmtcards.pl \
	--plugin=hardware::server::sun::mgmt_cards::plugin \
	--mode=showstatus \
	--hostname=10.0.0.1 \
	--username='' \
	--password=''  \
	--verbose

The expected command output is shown below:

OK: Component 'CPU#1' status is 'Normal'

Troubleshooting​

Please find the troubleshooting documentation for Centreon Plugins typical issues.

Available modes​

In most cases, a mode corresponds to a service template. The mode appears in the execution command for the connector. In the Centreon interface, you don't need to specify a mode explicitly: its use is implied when you apply a service template. However, you will need to specify the correct mode for the template if you want to test the execution command for the connector in your terminal.

All available modes can be displayed by adding the --list-mode parameter to the command:

/usr/lib/centreon/plugins/centreon_sun_mgmtcards.pl \
	--plugin=hardware::server::sun::mgmt_cards::plugin \
	--list-mode

The plugin brings the following modes:

ModeLinked service template
environment-sf2xx [code]HW-Sun-MgmtCard-Environment-Sf2xx-TELNET-custom
environment-v4xx [code]HW-Sun-MgmtCard-Environment-V4xx-TELNET-custom
environment-v8xx [code]HW-Sun-MgmtCard-Environment-V8xx-TELNET-custom
show-faulty [code]HW-Sun-MgmtCard-Show-Faulty-SSH-custom
showboards [code]HW-Sun-MgmtCard-Showboards-TELNET-custom
showenvironment [code]HW-Sun-MgmtCard-Showenvironment-TELNET-custom
showfaults [code]HW-Sun-MgmtCard-Showfaults-SSH-custom
showstatus [code]HW-Sun-MgmtCard-Showstatus-SSH-custom

Available options​

Modes options​

All available options for each service template are listed below:

OptionDescription
--componentWhich component to check (default: '.*'). Can be: 'temperature', 'si', 'disk', 'fan', 'voltage', 'psu', 'sensors'.
--filterExclude the items given as a comma-separated list (example: --filter=fan). You can also exclude items from specific instances: --filter=fan,F1.RS
--absent-problemReturn an error if a component is not 'present' (default is skipping). It can be set globally or for a specific instance: --absent-problem='component_name' or --absent-problem='component_name,instance_value'.
--no-componentDefine the expected status if no components are found (default: critical).
--threshold-overloadUse this option to override the status returned by the plugin when the status label matches a regular expression (syntax: status,regexp). Example: --threshold-overload='UNKNOWN,Normal'
--warningDefine the warning threshold for temperatures (syntax: type,instance,threshold) Example: --warning='temperature,.*,30'
--criticalDefine the critical threshold for temperatures (syntax: type,instance,threshold) Example: --critical='temperature,.*,40'
--warning-count-*Define the warning threshold for the number of components of one type (replace '*' with the component type).
--critical-count-*Define the critical threshold for the number of components of one type (replace '*' with the component type).
--hostnameHostname to query.
--porttelnet port (default: 23).
--usernamessh username.
--passwordssh password.
--timeoutTimeout in seconds for the command (default: 30).
--command-plinkPlink command (default: plink). Use to set a path.
--sshUse ssh (with plink) instead of telnet.
--memcachedMemcached server to use (only one server).
--redis-serverRedis server to use (only one server). Syntax: address[:port]
--redis-attributeSet Redis Options (--redis-attribute="cnx_timeout=5").
--redis-dbSet Redis database index.
--failback-fileFall back on a local file if Redis connection fails.
--memexpirationTime to keep data in seconds (default: 86400).
--statefile-dirDefine the cache directory (default: '/var/lib/centreon/centplugins').
--statefile-suffixDefine a suffix to customize the statefile name (default: '').
--statefile-concat-cwdIf used with the '--statefile-dir' option, the latter's value will be used as a sub-directory of the current working directory. Useful on Windows when the plugin is compiled, as the file system and permissions are different from Linux.
--statefile-formatDefine the format used to store the cache. Available formats: 'dumper', 'storable', 'json' (default).
--statefile-keyDefine the key to encrypt/decrypt the cache.
--statefile-cipherDefine the cipher algorithm to encrypt the cache (default: 'AES').
--memoryReturns new errors (retention file is used by the following option).
--excludeFilter components (multiple) (can be a regexp). Example: --exclude='MEM#2B' --exclude='MBU_A>MEM#0B'.

All available options for a given mode can be displayed by adding the --help parameter to the command:

/usr/lib/centreon/plugins/centreon_sun_mgmtcards.pl \
	--plugin=hardware::server::sun::mgmt_cards::plugin \
	--mode=showstatus \
	--help