Why Migrate to SMA?

Support for the Solstice Enterprise Agents software might be discontinued in a future Solaris release. For this reason, any Solstice Enterprise Agents subagents that you have created must be migrated to use the SMA. In this Solaris release, you can run the Solstice Enterprise Agents software and associated subagents concurrently with the SMA.

The Solstice Enterprise Agents product includes mibiisa, a subagent that implements MIB-II and the Sun MIB. In SMA, the functionality of mibiisa is implemented by the MIB-II portion of the SMA agent and a new Sun extensions subagent. By default, the mibiisa subagent is disabled in this Solaris release.

Requests for MIB-II are handled by the SMA agent directly. Requests for the extensions in the Sun MIB are handled by the seaExtensions module, if that module has been loaded. Requests for the Solstice Enterprise Agents master agent, which implements the snmpdx.mib, are handled by the seaProxy module if that module has been loaded.

The seaProxy module generates dynamic proxies based on static and dynamic Solstice Enterprise Agents subagent registrations. The proxies are not statically defined in snmpd.conf. Note that the seaProxy module does not generate proxies for the mibiisa subagent itself. After the dynamic proxies are generated, the agent's proxy mechanism handles the forwarding of those requests to the Solstice Enterprise Agents master agent.

Solstice Enterprise Agents subagents can still be used with the Solstice Enterprise Agents master agent, and thus with SMA by using the seaProxy module, as explained in Solaris System Management Agent Administration Guide. However, SMA support of the Solstice Enterprise Agents software is for a limited transitional time. You should migrate any Solstice Enterprise Agents subagents that you have implemented to use the SMA as early as possible.