To Migrate From the Sun SNMP Management Agent for Sun Fire and Netra Systems to the SMA

1. As root, stop both the System Management Agent and the masfd agents.

   # svcadm disable svc:/application/management/sma:default # /etc/init.d/masfd stop

   Any other agents that have been configured as subagents of SMA also need to be stopped and restarted after the migration is complete.

2. Perform a test migration to determine the effect of running the migration script.

   A test migration is useful if you have made significant configuration changes to the System Management Agent.

   # cd /usr/sfw/lib/sma_snmp # ./masfcnv --dry-run -i -p enable --select-community=agent

   If this dry run completes successfully, the proposed SMA configuration files are be presented in the standard output. Review this output before proceeding. The configuration of the Sun SNMP Management Agent for Sun Fire and Netra Systems is migrated to the SMA by the ./masfcnv migration script. If a conflict arises in the configuration, see the masfcnv(1M) man page for information on its resolution.

3. Run the migration script.

   # cd /usr/sfw/lib/sma_snmp # ./masfcnv -i -p enable --select-community=agent

4. As root, restart both the System Management Agent and the Sun SNMP Management Agent for Sun Fire and Netra Systems.

   # svcadm enable svc:/application/management/sma:default # /etc/init.d/masfd start

   The Sun SNMP Management Agent for Sun Fire and Netra Systems is then reconfigured to run as a subagent under the System Management Agent. Any other agents that have been configured as subagents of the System Management Agent also need to be restarted after the migration is complete.

   After migration to the SMA from the Sun SNMP Management Agent for Sun Fire and Netra Systems, the Sun Fire hardware instrumentation becomes accessible to SNMP applications through the SMA. The SMA uses the same port that was previously used by the Sun SNMP Management Agent for Sun Fire and Netra Systems.