Monitoring: SNMP, syslog, Call Home, remote support

DS8000 Call Home is the storage system phoning IBM on its own when a part fails, often before you’ve noticed anything. Around it sit the other ways a DS8000 tells people what’s going on: SNMP traps to your monitoring tool, email, syslog for your security team, and remote support so IBM can connect in and help.

You’ll find out what each channel carries and who sets it up, the IBM SSR on the HMC or you with the DS CLI. In the lab you’ll switch on SNMP traps and email notification with chsp, check them with showsp and read the HMC access settings with lsaccess, and you’ll also see the syslog and data offload commands you’ll use on a real system.

You need the practice shell, and Lesson 4 on HMC networking will help.

TimeYou needBy the end you can
60 minutesThe SaatVedha practice shell and the IP address of your monitoring server (any test IP is fine in the lab)Explain Call Home, heartbeat, SNMP, syslog and remote support, and set and check SNMP and email notification

What it is, in one line

Call Home reports hardware problems to IBM, SNMP and email warn your own team, syslog feeds logs to your security tools, and remote support lets IBM connect in when you allow it.

In Simple Words

A school with a watchman, a bell and a diary

At night a watchman walks round the school, and if he finds a broken window he phones the repair company straight away; that’s Call Home. He also rings the bell in the teachers’ room so the head teacher knows too, which is SNMP or email, the alarm for your own people.

Every morning he rings the repair company to say “all fine, I’m still here”, and if one morning he doesn’t call, the company sends someone round to check. That’s the heartbeat. Everything he sees goes into a diary kept by the school office, which is syslog and the audit log, and if the repair company needs to look inside, the head teacher can open the gate for them, but only when she says so. That’s remote support access.

Engineer's View

Who sends what, and to where

Call Home (outbound). The HMC reports serviceable events to IBM and opens a case automatically, and it also sends machine-reported product data (installed hardware, configuration, features).

The IBM SSR sets it up at install time from your worksheets and places a test call. It connects over the internet using TLS, optionally through your proxy.

Heartbeat. A small regular message, sent every 1 to 7 days, that proves Call Home works. If a heartbeat doesn’t arrive, IBM sends a service action to check the connection.

Data offload. Diagnostic bundles called PEPackages, often over 100 MB, go to IBM over the same TLS path, and inbound remote access is never used to send data out.

SNMP traps. The DS8000 sends SNMPv1 traps, but it has no SNMP agent you can poll. Serviceable events go out as generic trap 6, specific trap 3, at the same time as the Call Home, and repeat every 8 hours while the event stays open.

Hardware traps are configured per HMC in the Service Web UI (each HMC separately). Copy Services, thin provisioning and encryption traps are set with chsp -snmp on -snmpaddr ip1,ip2, which takes at most two addresses, separated by a comma with no spaces, on port 162 with community public. Load the DS8000 MIB file into your monitoring tool.

You won’t find a mksnmp command.

Syslog. mksyslogserver -addr IP sends audit, message and event records over TCP or TLS, on port 514 by default. Every server has to use the same protocol, and the first TLS server needs -cacert, -hmccert and -hmckey. Check it with lssyslogserver -l.

Remote support (inbound). This is either Assist On-site (AOS, embedded on the HMC or through your own AOS Gateway), secured with TLS 1.3, or IBM Remote Support Center (RSC) over SSH. Both start as outbound connections from the HMC, and you control them with lsaccess and chaccess or the GUI.

Every remote login is written to the audit log, which you export with offloadauditlog or offloadfile -auditlog.

How it works, step by step

Picture a power supply failing at 2 a.m. in a DS8000 at a bank, and follow what happens, step by step, when everything has been set up properly.

1The DS8000 detects the fault

The failing part logs an error, but the storage keeps running on the redundant power supply and the hosts notice nothing. The HMC turns the error into a serviceable event with a reference code and the location of the part.

2Call Home opens a case at IBM

The HMC sends the event to IBM over TLS and IBM’s system opens a case, so support can start looking at the data straight away, often before your team is even awake.

DS8000 Call Home flow from a failed part to IBM case, traps and repair

3Your team hears about it

At the same moment the HMC sends an SNMP trap (generic 6, specific 3) to your monitoring server, plus an email if you’ve configured one, and your night operator sees “power supply failed” in the monitoring console.

4IBM asks for more data

If support needs logs, the HMC offloads a PEPackage over the same outbound TLS path, and if they need to look inside, they’ll ask you to allow a remote session through AOS or RSC.

5You open the door, then close it

You (or an operator) start the AOS session from the GUI, or confirm it’s enabled with lsaccess. IBM connects, and the session goes into the audit log, along with the challenge key for higher access.

6The part is replaced

An IBM SSR arrives with the new part and replaces it concurrently. The event closes and the trap that was repeating every 8 hours stops.

Where Call Home, trap 3, chsp traps and syslog are configured

7Your security team sees all of it

With syslog switched on, the audit records of who logged in, what they changed and when the remote session started all land in your SIEM, which is what the auditors ask to see every year.

DS8000 HMC Manage Serviceable Event Notification with an SNMP trap destination and Test SNMP Trap
Illustration: HMC Service Web UI, Service Management, Manage Serviceable Event Notification. Add the trap server, select Trap 3, then Test SNMP Trap (reference code BEB20010). Do it on each HMC.

Hands-on lab: set up and check notifications

Before you run any command, double-check it

Read every command twice before you press Enter. Check the target: the system or account, the IDs, the names and the sizes. These commands are for learning and were tested in our lab, not on your system. At work, run the read-only list commands first, follow your change process, make sure a backup exists, and ask a second person to check anything that changes or deletes data. You run them at your own risk.

Your bank has a pair of monitoring servers at 10.20.30.40 and 10.20.30.41, plus a storage team mailbox. You’ll switch on the notifications the DS CLI controls, check them and look at the remote support settings, and then see the real commands for the parts the practice shell doesn’t cover.

Practice shell note: the practice shell is our own teaching tool, not IBM software. Real DS CLI output looks very close to this but isn’t identical. The shell supports chsp, showsp and lsaccess, while syslog, offload and the HMC Service Web UI are shown as real commands you’d run on a real system. CMUN03060E is a practice shell message.

1Start clean

You don’t need a setup script for this lab.

Run this:

python ds8sim.py
dscli> simctl reset

✅ Checkpoint: the shell prints SIM0100I.

2Look at the storage complex settings

Run this:

showsp

You should see this:

dscli> showsp
Date/Time: 24 October 2026 11:14:53 UTC IBM DSCLI Version: 7.10.10.348 DS: IBM.2107-78SV001
Name           IbmStoragePlex
desc           -
acct           -
SNMP           Disabled
SNMPadd        -
emailnotify    Disabled
emailaddr      -
emailrelay     Disabled
emailrelayaddr -
emailrelayhost -
numkssupported 4
loginprompt    Disabled
promptmessage  -
guisuggestions show

SNMP and email both show Disabled, which is how most new systems look until somebody does this job.

✅ Checkpoint: SNMP Disabled, SNMPadd -.

3Turn on SNMP traps to two servers

Two addresses, one comma, and no space.

Run these:

chsp -snmp on -snmpaddr 10.20.30.40,10.20.30.41
showsp

You should see this:

dscli> chsp -snmp on -snmpaddr 10.20.30.40,10.20.30.41
CMUC00040I chsp: Storage complex IbmStoragePlex successfully modified.
dscli> showsp
Date/Time: 24 October 2026 11:14:53 UTC IBM DSCLI Version: 7.10.10.348 DS: IBM.2107-78SV001
Name           IbmStoragePlex
desc           -
acct           -
SNMP           Enabled
SNMPadd        10.20.30.40,10.20.30.41
emailnotify    Disabled
emailaddr      -
emailrelay     Disabled
emailrelayaddr -
emailrelayhost -
numkssupported 4
loginprompt    Disabled
promptmessage  -
guisuggestions show

SNMP is now Enabled with both addresses, covering the operational traps (Copy Services, thin provisioning, encryption). Hardware traps (trap 3) are set up separately on each HMC, either by the IBM SSR or by you in the Service Web UI.

✅ Checkpoint: SNMPadd shows 10.20.30.40,10.20.30.41.

Practice shell: chsp turns on SNMP traps, showsp confirms
SNMP traps on, checked with showsp.

4Add email notification

Run this:

chsp -emailnotify on -emailaddr storage-team@saatbank.example

You should see this:

dscli> chsp -emailnotify on -emailaddr storage-team@saatbank.example
CMUC00040I chsp: Storage complex IbmStoragePlex successfully modified.

Use a team mailbox, never one person’s address, because people go on leave and mailboxes don’t.

✅ Checkpoint: chsp prints CMUC00040I.

5Check remote support access

Run this:

lsaccess -l

You should see this:

dscli> lsaccess -l
Date/Time: 24 October 2026 11:14:53 UTC IBM DSCLI Version: 7.10.10.348 DS: IBM.2107-78SV001
hmc  cmdline wui     modem    cim      aos     rsc     vpn
===============================================================
hmc1 enabled enabled disabled disabled enabled enabled disabled
hmc2 enabled enabled disabled disabled enabled enabled disabled

aos and rsc are enabled on both HMCs, which means IBM can be let in through Assist On-site or Remote Support Center, and cmdline and wui are the DS CLI and Service Web UI access. Agree with your security team which of these stay on, and change them with chaccess, for example chaccess -aos enable -hmc 1.

✅ Checkpoint: you can name what aos and rsc control.

6Confirm both HMCs are up

Run this:

lshmc

You should see this:

dscli> lshmc
Date/Time: 24 October 2026 11:14:53 UTC IBM DSCLI Version: 7.10.10.348 DS: IBM.2107-78SV001
Name          State  Role         Release                  Management-IP Location-Code    Machine-Type Machine-Model Memory Disk
================================================================================================================================
DS8A50-1A.LAB Online Primary(1)   R10.1 bundle 10.10.106.0 10.0.0.1      U7063CR2.78SV1DD 7063         CR2           33GB   1TB
DS8A50-1B.LAB Online Secondary(2) R10.1 bundle 10.10.106.0 10.0.0.2      U7063CR2.78SV2DD 7063         CR2           33GB   1TB

Call Home and traps come from the HMCs, so if an HMC is down its notifications stop. That’s why each HMC is configured separately and you need to monitor both.

✅ Checkpoint: both HMCs Online.

7On a real system: send audit and events to syslog

Your security team wants every login and change to show up in their SIEM. On a real DS8000 (not in the practice shell), using IBM’s syntax, the commands look like this:

dscli> mksyslogserver -addr 10.20.30.50 -protocol tls -cacert ca.pem -hmccert hmc.pem -hmckey hmc.key -type all soc-siem1
dscli> lssyslogserver -l

You should see something like this:

CMUC00508I mksyslogserver: The syslog server soc-siem1 has been created.
name      IP address  port state  access protocol type                HMC
=========================================================================
soc-siem1 10.20.30.50 514  active online tls      audit,message,event 1

The default port is 514. Every syslog server has to use the same protocol, and you can’t run this from the embedded DS CLI in the GUI.

✅ Checkpoint: you know the flags: -addr, -protocol, -cacert, -hmccert, -hmckey, -type.

8On a real system: offload data for IBM or an audit

dscli> offloadfile -config c:\dscli_offload
dscli> offloadauditlog -logaddr smc1 c:\temp\audit.txt

You should see something like this:

CMUC00428I offloadfile: The config file has been offloaded to c:\dscli_offload\productSettings.
CMUC00243I offloadauditlog: Audit log was successfully offloaded from smc1 to c:\temp\audit.txt.

offloadfile takes exactly one data set per command, such as -config, -auditlog, -perfdata or -pepackage. The audit log holds about 50 MB and trims the oldest entries first, so if you need a long history, offload it regularly.

✅ Checkpoint: you can name two offloadfile data sets.

9On a real system: test the whole chain

If you’ve never tested a notification, you can’t count on it. On each HMC, go to Manage Serviceable Event Notification in the Service Web UI and send a Test SNMP Trap, which creates reference code BEB20010, then check that your monitoring server shows it.

Ask IBM or your SSR to confirm the last heartbeat came through.

snmptrapd on the monitoring server receiving the DS8000 test trap with SRC BEB20010 from both HMCs
Lab capture: the monitoring server logs one test trap per HMC (agents 10.0.0.1 and 10.0.0.2), each with SRC=BEB20010. The trap text follows the trap 3 example in the IBM Redbook.

✅ Checkpoint: a test trap from each HMC reached your monitoring server.

Break It, Then Fix It

Run simctl reset first. Both of these mistakes leave a DS8000 silently unmonitored, the worst kind of problem, because nothing looks broken until the day you need the alert.

1Break it: three trap servers, then a space

The monitoring team asks for three destinations, and then someone types the list with a space after the comma.

Run these:

chsp -snmp on -snmpaddr 10.20.30.40,10.20.30.41,10.20.30.42
chsp -snmp on -snmpaddr 10.20.30.40, 10.20.30.41
showsp

You’ll see this:

dscli> chsp -snmp on -snmpaddr 10.20.30.40,10.20.30.41,10.20.30.42
CMUN03060E chsp: You can specify at most two SNMP trap addresses, separated by a comma with no spaces.
dscli> chsp -snmp on -snmpaddr 10.20.30.40, 10.20.30.41
CMUC00040I chsp: Storage complex IbmStoragePlex successfully modified.
dscli> showsp
Date/Time: 24 October 2026 11:14:53 UTC IBM DSCLI Version: 7.10.10.348 DS: IBM.2107-78SV001
Name           IbmStoragePlex
desc           -
acct           -
SNMP           Enabled
SNMPadd        10.20.30.40,
emailnotify    Disabled
emailaddr      -
emailrelay     Disabled
emailrelayaddr -
emailrelayhost -
numkssupported 4
loginprompt    Disabled
promptmessage  -
guisuggestions show

Why: chsp accepts no more than two trap addresses. The second command looks like it worked, but the space ended the value, so SNMPadd holds only “10.20.30.40,” and the second server gets nothing. A real DS CLI splits arguments at spaces too, so always check showsp after a change.

Fix: use two addresses with no space, and if more tools need the traps, send them to one collector that forwards them on.

Run these:

chsp -snmp on -snmpaddr 10.20.30.40,10.20.30.41
showsp

You should see this:

dscli> chsp -snmp on -snmpaddr 10.20.30.40,10.20.30.41
CMUC00040I chsp: Storage complex IbmStoragePlex successfully modified.
dscli> showsp
Date/Time: 24 October 2026 11:14:53 UTC IBM DSCLI Version: 7.10.10.348 DS: IBM.2107-78SV001
Name           IbmStoragePlex
desc           -
acct           -
SNMP           Enabled
SNMPadd        10.20.30.40,10.20.30.41
emailnotify    Disabled
emailaddr      -
emailrelay     Disabled
emailrelayaddr -
emailrelayhost -
numkssupported 4
loginprompt    Disabled
promptmessage  -
guisuggestions show

✅ Checkpoint: SNMPadd shows both addresses.

Practice shell: too many trap addresses, a space in the list, and mksnmp unknown
The trap address mistakes from this lab.

2Break it: a command from another storage system

An engineer who’s used to another vendor’s array types an SNMP command from memory.

Run this:

mksnmp -addr 10.20.30.40

You’ll get this error:

dscli> mksnmp -addr 10.20.30.40
CMUN00014E mksnmp: Unknown command. Enter "help" for a list of commands.

Why: the DS8000 has no mksnmp. SNMP for operational traps is a property of the storage complex, set with chsp, and hardware traps live on each HMC. There’s no lsproblem or setcontactinfo either; events are on the GUI Events page and contact details are set on the HMC.

Fix: use chsp -snmp on -snmpaddr ... and check it with showsp. If you’re unsure, help -s chsp tells you what a command does.

✅ Checkpoint: you can say where each kind of trap is configured.

This happened at work

A year of traps sent to a server that no longer existed

A government department ran its tax and benefits systems on two DS8000s. At install time the SNMP traps and the HMC trap 3 settings were pointed at the monitoring server of the day, 10.4.1.20, and two years later the monitoring team moved to a new platform with new IPs, switched the old server off, and didn’t tell the storage team.

For about a year the DS8000s kept sending traps to an address with nothing behind it. Call Home still worked, so IBM kept quietly replacing failed parts, and that hid the problem. Then a Global Copy session to the DR site suspended during a network change, and since Copy Services traps don’t go to IBM, only to your SNMP servers, nobody saw it. The DR copy aged for 19 days before an auditor asked for proof of DR readiness and the team ran lspprc.

Root cause: the trap destinations had been set once and never checked again, and the monitoring change process didn’t include storage. Fix: showsp and the HMC notification settings are now on the quarterly checklist, every HMC sends a test trap after any monitoring change, and the monitoring team raises an alert if a DS8000 hasn’t sent a single trap in 30 days.

The lesson: treat notifications as a live system. Test them end to end, and test them again whenever anything along the path changes.

Common mistakes and troubleshooting

SymptomLikely causeWhat to check / fix
Monitoring never shows DS8000 hardware alertsTrap 3 not set on the HMCs, or set on only oneUse the Service Web UI on each HMC and send a Test SNMP Trap (BEB20010).
Copy Services alerts never arrivechsp SNMP off or wrong addressesCheck showsp, then run chsp -snmp on -snmpaddr ip1,ip2 (no spaces).
Traps arrive as unreadable numbersDS8000 MIB file not loadedLoad the latest MIB from the DS CLI image into the monitoring tool.
IBM says the heartbeat stoppedFirewall or proxy change blocked outbound TLSCheck the HMC’s outbound path to IBM, and ask the SSR to test Call Home.
IBM can’t connect for a remote sessionAOS or RSC disabled, or firewallCheck lsaccess -l, then run chaccess -aos enable -hmc 1 if your policy allows it.
Syslog server added but nothing arrivesWrong port, mixed protocols, missing certificatesCheck lssyslogserver -l and use the same protocol everywhere; TLS needs -cacert, -hmccert and -hmckey.
Audit log is missing old entriesThe audit log trims itself at about 50 MBOffload it regularly, or send it to syslog.

Keep every notification target in one table, covering the Call Home path, both HMCs’ trap settings, the chsp addresses, email and syslog, and review it every quarter.

Interview questions

Click a question to open it. Each one is worded the way an interviewer would ask it, and underneath you’ll find why they ask it and one way you could answer in your own words.

Fresher level

1. What is Call Home on a DS8000, and how is it different from SNMP?

Why they ask this: They want to know you understand who gets told what, IBM on one side and your own team on the other.

How you might answer: Call Home is the HMC reporting serviceable events to IBM over a TLS internet connection, so a case opens automatically, while SNMP traps go to our own monitoring server so our team knows as well. Copy Services traps only go to SNMP and never to IBM, so we need both.

2. How do you turn on SNMP traps from the DS CLI?

Why they ask this: It’s a quick check that you know the real command and its limits.

How you might answer: I’d use chsp -snmp on -snmpaddr with up to two IP addresses, separated by a comma with no spaces, and then showsp to check. That covers operational traps like Copy Services, and hardware trap 3 gets set on each HMC in the Service Web UI.

2–5 years experience

3. Your monitoring tool hasn’t shown a single DS8000 alert in months. How do you find out if that’s good news or a problem?

Why they ask this: They want you to check the whole notification chain methodically rather than assume.

How you might answer: I’d look at the settings first, showsp for the trap addresses and the HMC Service Web UI on both HMCs for the trap 3 destinations. Then I’d send a Test SNMP Trap from each HMC and see whether the monitoring server receives reference code BEB20010.

I’d also make sure the MIB is loaded and ask IBM when the last heartbeat arrived. If any test fails, I’d trace the path: IP, firewall, port 162, then the receiving server.

4. The security team wants all DS8000 admin activity in their SIEM. How do you do it?

Why they ask this: Syslog and the audit log come up in every audit, so they want to know you’ve worked with them.

How you might answer: I’d point mksyslogserver at the SIEM with -type all, or at least audit, ideally over TLS with the CA cert, HMC cert and HMC key for the first server, and confirm it with lssyslogserver -l. For a one-off export I can run offloadauditlog, and remote IBM sessions show up in the audit log too, challenge key included.

Senior level

5. Your bank’s policy says no inbound vendor access. How do you still get fast IBM support for a DS8000?

Why they ask this: A senior person has to balance security rules against supportability and know how the connections really work.

How you might answer: Call Home and data offload are outbound only, over TLS, so they usually fit a policy like that and still open cases automatically. For remote sessions, AOS and RSC also start as outbound connections from the HMC, and I can keep them disabled with chaccess and switch them on only for an approved incident.

Every session goes into the audit log, which we send to the SIEM. I’d write that process up with the security team so it’s agreed well before the 3 a.m. call.

6. How would you design monitoring for 15 DS8000s across three data centres?

Why they ask this: They’re looking for thinking at scale, meaning standard settings, one place to look, and regular tests.

How you might answer: I’d standardise everything: Call Home and heartbeat on every system, trap 3 on both HMCs, chsp traps to two central collectors, syslog to the SIEM and email to a team mailbox. I’d put all the systems into IBM Storage Insights for a single view of events and cases, keep a config table for each system, and run a quarterly test trap from every HMC, with an alert if any system goes quiet.

Quick quiz

Q1. Who does Call Home notify?

  1. Only your monitoring server
  2. IBM, by opening a support case
  3. Only the storage admin by email
  4. The SAN switch
Show answer

B: Call Home reports serviceable events to IBM over a secure internet connection.

Q2. How many trap addresses can chsp -snmpaddr take?

  1. One
  2. Two
  3. Four
  4. Unlimited
Show answer

B: At most two addresses, separated by a comma with no spaces.

Q3. Which DS CLI command creates an SNMP destination?

  1. mksnmp
  2. chsp -snmp on -snmpaddr
  3. setsnmp
  4. mksyslogserver
Show answer

B: There’s no mksnmp, because SNMP is a storage complex property set with chsp.

Q4. How often can the heartbeat be scheduled?

  1. Every hour
  2. Every 1 to 7 days
  3. Once a month
  4. Only at install
Show answer

B: You can set the heartbeat anywhere from every 1 to every 7 days.

Q5. What is the default syslog port for mksyslogserver?

  1. 162
  2. 443
  3. 514
  4. 8080
Show answer

C: The default port is 514, while SNMP traps use 162.

Quick recap

  • Call Home tells IBM, SNMP and email tell your team, and syslog feeds your security tools.
  • A heartbeat every 1 to 7 days proves Call Home is working.
  • Hardware trap 3 is set on each HMC; operational traps with chsp -snmp on -snmpaddr ip1,ip2.
  • Syslog: mksyslogserver, port 514, same protocol for all, TLS needs three certificate files.
  • Remote support (AOS, RSC) is controlled with lsaccess and chaccess, and logged in the audit log.
  • Test every channel end to end, and test again after any network or monitoring change.

Next lesson

Lesson 22: Performance: metrics, Storage Insights, tuning → You read port, volume and rank metrics and learn what to tune first.

Further reading: DS8000 Call Home

Want to go deeper into DS8000 Call Home? Chapter 12 of the IBM Storage DS8A00 Architecture and Implementation Guide (IBM Redbooks) lists every trap and remote support option. For the HMC network these settings depend on, see Network planning and the Management Console.

You can also see the full plan for this course on the IBM DS8000 Implementation course page.

Scroll to Top

This website uses cookies

We use a few cookies to keep this site working. If you allow it, we also use Google Analytics to count visits so we can improve our lessons. You can accept all, deny the optional ones, or choose what to allow.