Administrator Guide

2. In an SMI-S client:
a. Subscribe using the SELECT * FROM CIM_InstCreation WHERE SourceInstance ISA CIM_LogicalFile filter.
b. Subscribe using the SELECT * FROM CIM_InstDeletion WHERE SourceInstance ISA CIM_LogicalFile filter.
For more information about the managed logs feature, see About managed logs.
Testing SMI-S
Use an SMI-S certified client for SMI-S 1.5. Common clients include Microsoft System Center, IBM Tivoli, EMC CommandCenter and CA
Unicenter. Common WBEM CLI clients are Pegasus cimcli and Sblim’s wbemcli.
To certify that the array provider is SMI-S 1.5 compliant, SNIA requires that the providers pass the Conformance Test Program (CTP)
tests.
The reset smis-configuration command enables the restoration of your original SMI-S configuration.
Troubleshooting
Table 38. Troubleshooting
Problem Cause Solution
Unable to connect to the
embedded SMI-S Array provider.
SMI-S protocol is not
enabled.
Log in to the array as manage and type: set protocolsmis
enabled
HTTP Error (Invalid username/
password or 401 Unauthorized).
User preferences are
configurable for each
user on the storage
system.
Check that the user has access to the smis interface and set the user
preferences to support the smis interface, if necessary. See
Adding,modifying,and deleting users for instructions on how to add
users. Also verify the supplied credentials.
Want to connect securely as user
name my_xxxx.
Need to add user. Log in to the array as manage . Type: create user level
manage my_xxxuser and then type: set user my_xxxuser
interfaces wbi,cli,smis
Unable to discover via SLP. SLP multicast has limited
range(known as hops).
Move the client closer to the array or set up a SLP DA server or using
unicast requests.
Unable to determine if SMI-S is
running.
Initial troubleshooting. Use a Common Information Model (CIM) client tool, such as wbemcli,
to troubleshoot.
SMI-S is not responding to client
requests.
SMI-S configuration may
have become corrupted.
Use the CLI command reset smis-configuration. For more
information, see the Dell EMC PowerVault ME4 Series Storage System
CLI Guide.
Using SLP
ME4 Series storage systems support Service Location Protocol (SLP, srvloc), which is a service discovery protocol that allows computers
and other devices to find services in a LAN without prior configuration. SLP is open for use on all operating systems, and does not require
formal licensing.
SLP is based on User Datagram Protocol (UDP) and can use Transmission Control Protocol (TCP) if needed. SLP listens on port 427.
When a client, or User Agent (UA), connects to a network, the client queries for Directory Agents (DA) on the network. If no DA
responds, the client assumes a DA-less network and sends a multicast UDP query. All Service Agents (SA) that contain query matches will
send a UDP answer to the client. If the answer message is too large, the client can repeat the query using TCP.
In a network with DAs, each SA must register all services with a DA. Then the clients will query the DAs, who will respond to the query
with its cached SA information.
Through use of DAs, SLP can also scale beyond the local area network to large enterprise, which is an enterprise IT issue. Consult the IETF
RFC2165.
When SLP is enabled, the storage system will advertise the interfaces shown in Table 39. Interfaces advertised by SLP on page 163 and
populate the configuration attributes shown in Table 40. SLP attributes shown for a storage system on page 163.
162
Other management interfaces