Fabric Lock Override; Database Merge Guidelines; Call Home Communications Test; Testing Call Home Using Fabric Manager - Cisco AP775A - Nexus Converged Network Switch 5010 Configuration Manual

Chapter 62 Configuring Call Home
S e n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a c k - d o c @ c i s c o . c o m

Fabric Lock Override

If you have performed a Call Home task and have forgotten to release the lock by either committing or
discarding the changes, an administrator can release the lock from any switch in the fabric. If the
administrator performs this task, your changes to the pending database are discarded and the fabric lock
is released.
The changes are only available in the volatile directory and are subject to being discarded if the switch
Tip
is restarted.

Database Merge Guidelines

See the
When merging two Call Home databases, follow these guidelines:
•
•

Call Home Communications Test

You can test Call Home communications by sending a test message to the configured destination(s) or
sending a test inventory message to the configured destination(s).

Testing Call Home Using Fabric Manager

To test the Call Home function and simulate a message generation using Fabric Manager, follow these
steps:
Step 1 Select a switch in the Fabric pane.
Step 2 Expand Switches, expand Events, and select Call Home in the Physical Attributes pane.
You see the Call Home information in the Information pane.
Step 3 Click the Test tab.
You see the configured tests for the switch and the status of the last testing.
Select a switch in the Information pane.
Step 4
Select test or testWithInventory from the TestAction drop-down list in the row for that switch.
Step 5
OL-17256-03, Cisco MDS NX-OS Release 4.x
"CFS Merge Support" section on page 13-9
Be aware that the merged database contains the following information:
– A superset of all the destination profiles from the dominant and subordinate switches that take
part in the merge protocol.
– The e-mail addresses and alert groups for the destination profiles.
– Other configuration information (for example, message throttling, periodic inventory) from the
switch that existed in the dominant switch before the merge.
Verify that two destination profiles do not have the same name (even if they have different
configuration information) on the subordinate and dominant switches. If they do contain the same
name, the merge operation will fail. You must then modify or delete the conflicting destination
profile on the required switch.
for detailed concepts.
Cisco MDS 9000 Family Fabric Manager Configuration Guide
Call Home Communications Test
62-19