- DCNM Server
- Management Users
- Performance Setup
- Event Setup
Administration
This section contains context-sensitive Online Help content for the Web Client > Administration tab.
DCNM Server
The DCNM Server menu includes the following submenus:
- Starting, Restarting, and Stopping Services
- Viewing Log Information
- Server Properties
- Configuring SFTP/TFTP Credentials
- Modular Device Support
- Managing Switch Groups
- Managing Custom Port Groups
- Managing Licenses
- Viewing Server Federation
- Native HA
- Multi Site Manager
Starting, Restarting, and Stopping Services
Viewing Log Information
This feature enables you to view the Cisco DCNM Web Client log. These processes have no corresponding GUI that allows you to view information about these log files. If you see errors, preserve these two files for viewing.
 Note | Logs cannot be viewed from a remote server in a federation. |
Server Properties
This page allows you to set common parameters which will be populated as default values in DCNM server.
Specify the parameters in the following fields according to the corresponding description.
| Command or Action | Purpose |
|---|
Configuring SFTP/TFTP Credentials
You can configure the SFTP/TFTP credentials for the file store.
A file server is required to collect device configuration and restoring configurations to the device.
Examples for SFTP Directory Path
Use Case 1:
If Cisco DCNM is installed on Linux platforms (OVA/ISO/Linux), and the test folder is located at /test/sftp/, you must provide the entire path of the SFTP directory. In the SFTP Directory field, enter /test/sftp.
Use Case 2:
If Cisco DCNM is installed on Windows platform, and the test folder is located at C://Users/test/sftp/, you must provide the relative path of the SFTP directory. In the SFTP Directory field, enter /.
For Example:
Modular Device Support
In order to support any new hardware which doesn't require many major changes, a patch can be delivered instead of waiting for the next DCNM release. Modular Device Support helps to deliver and apply the DCNM patch releases. An authorized DCNM administrator can apply the patch to the production setup. Patch releases are applicable for the following scenarios:
| Step 1 | From the menu
bar, choose
Administration > DCNM Server > Modular Device Support to view
the patch details.
You see theDCNM Servers column on the left-hand side of the window and Modular Device support informationwindow on the right-hand side. |
| Step 2 | You can view all the DCNM servers under the DCNM Servers window, as well as the list of patch installed along with the version number, corresponding platforms supported, chassis supported, NX-OS version supported, PID supported, backup directory and the last patch deployment time in the Modular Device support information table. |
| Step 3 | For more details about how to apply and rollback a patch, please go to WWW.cisco.com/go/dcnm for more information. |
Managing Switch Groups
Beginning with Cisco NX-OS Release 6.x, you can configure switch groups by using Cisco DCNM Web Client. You can add, delete, rename or move a switch to a group or move a group of switches to another group.
This section contains the following:
Adding Switch Groups
You can add a switch group from the Cisco DCNM Web Client.
| Step 1 | From the menu bar, choose Administration > DCNM Server > Switch Groups. |
| Step 2 | Click the Add icon, and the Add Group window appears that allows you to enter the name for the switch group. |
| Step 3 | Enter the name
of the switch group and click
Add to complete adding the switch group.
The switch group name validation and the maximum tree depth is 10. If you do not choose a parent group before adding a new switch group, the new group is added on the top of the hierarchy |
Deleting a Group or a Member of a Group
You can delete group(s) and/or member(s) of a group from the Cisco DCNM Web Client. When you delete a group, the associated group(s) are deleted and the fabrics or Ethernet switches of the deleted group(s) are moved back to the default SAN or LAN.
| Step 1 | Choose the switch group or member(s) of a group that you want to remove. |
| Step 2 | Click the
Remove icon or
press the Delete key on your keyboard.
A dialog box prompts you to confirm the deletion of the switch group or the member of the group. |
| Step 3 | Click Yes to delete or No to cancel the action. |
Moving a Switch Group to Another Group
| Step 1 | Click on the switch or switch group and drag the highlighted switch or switch group to another group. To move multi devices or switches across different switch groups, you can select multiple devices using CTRL key or SHIFT key. | ||
| Step 2 | You can see the
switch or switch group Users are not allowed to move multiple items on the
group level under the new group now.
|
Managing Custom Port Groups
Custom port groups aids you to test the performance of the interfaces in the group. You can view the defined custom ports and their configurations from Administration > DCNM Server > Custom Port Groups on the Cisco DCNM Web Client.
This section includes the following topics:
- Adding Custom Port Groups
- Configuring Switch and Interface to the Port Group
- Removing Port Group Member
- Removing Port Group
Adding Custom Port Groups
You can add a custom port group from the Cisco DCNM Web Client.
| Step 1 | From the menu bar, choose Administration > DCNM Server > Custom Port Groups. |
| Step 2 | In the User Defined Groups block, click the Add icon. |
| Step 3 | Enter the name
for the custom port group in the
Add Group Dialog window.
Click Add, and a custom port group is created in the User Defined Groups block. |
Configuring Switch and Interface to the Port Group
You can configure the custom port group to include switches and their interfaces.
| Step 1 | From the menu bar, choose Administration > DCNM Server > Custom Port Groups. |
| Step 2 | In the User Defined Groups block, select the port group for which you need to add the switch and interfaces. |
| Step 3 | In the
Configurations block, click the
Add Member icon.
The Port Configuration window appears for the selected custom port group. |
| Step 4 | In the
Switches tab, select the switch that you need
to include in custom port group.
The list of available Interfaces appears. |
| Step 5 | Select all the interfaces for which you need to check the performance. |
| Step 6 | Click
Submit.
The list of interfaces is added to the custom port group. |
Removing Port Group Member
You can remove or delete the port group member from the Custom Port group.
| Step 1 | From the menu bar, choose Administration > DCNM Server > Custom Port Groups. |
| Step 2 | In the User Defined Groups block, select the port group for which you need to add the switch and interfaces. |
| Step 3 | In the Configuration clock, select the switch name and interface that must be deleted. |
| Step 4 | In the
User Defined Groups block, select the group
for which you which must be deleted. Click
Remove Member
icon.
A confirmation window appears. |
| Step 5 | Click Yes to delete the member from the custom port group . |
Removing Port Group
You can remove or delete the port group from the Cisco DCNM Web Client.
Managing Licenses
This section includes the following topics:
- Viewing Licenses Using the Cisco DCNM Wizard
- Automatic License Assignment
- Adding Cisco DCNM Licenses
- Assigning Licenses
- Unassigning Licenses to a Switch
Viewing Licenses Using the Cisco DCNM Wizard
You can view the existing Cisco DCNM licenses by selecting Administration > DCNM Server > License.
Note | By default, the License Assignments tab appears. |
License Assignments
The following table displays the License Assignments for every switch.
|
Field |
Description |
||
|---|---|---|---|
|
Group |
Displays if it is a fabric or LAN group. |
||
|
Switch Name |
Displays the name of the switch. |
||
|
WWN/Chassis ID |
Displays the World Wide Name or Chassis ID. |
||
|
Model |
Displays the model of the device. For example, DS-C9124 or N5K-C5020P-BF. |
||
|
License State |
Displays the license state of the switch that can be one of the following: |
||
|
License Type |
Displays if the license is a switch-based embedded license or a server-based license. |
||
|
Eval Expiration |
Displays the expiry date of the license.
|
||
|
Assign License |
Select a row and click this option on the tool bar to assign the license. |
||
|
Unassign License |
Select a row and click this option on the tool bar to unassign the license. |
||
|
Assign All |
Click on this option on the tool bar to refresh the table and assign the licenses for all the items in the table. |
||
|
Unassign All |
Click on this option on the tool bar to refresh the table and unassign all the licenses. |
Server License Files
The following table displays the Cisco DCNM server license fields.
|
Field |
Description |
||
|---|---|---|---|
|
Filename |
Specifies the license file name. |
||
|
Feature |
Specifies the licensed feature. |
||
|
PID |
Specifies the product ID. |
||
|
SAN (Free/Total) |
Display the number of free versus total licenses for SAN. |
||
|
LAN (Free/Total) |
Display the number of free versus total licenses for LAN. |
||
|
Eval Expiration |
Displays the expiry date of the license.
|
Automatic License Assignment
When the fabric is first discovered if the switch does not have a valid switch-based license, a license is automatically assigned to the fabric from the file license pool until no more licenses are left in the pool. Also, if you have an existing fabric and a new switch is added to the fabric, the new switch will be assigned a license if one is available in the file license pool and if it does not already have a switch-based license.
Adding Cisco DCNM Licenses
You must have network administrator privileges to complete the following procedure.
| Step 1 | Choose Administration > DCNM Server > License to start the license wizard. | ||
| Step 2 | Choose the
Server License Files tab.
The valid Cisco DCNM-LAN and DCNM-SAN license files appears. Ensure that the security agent is disabled when you load licenses. | ||
| Step 3 | Download the license pack file that you received from Cisco into a directory on the local system. | ||
| Step 4 | Click
Add License
File and then select the license pack file that you saved on the
local machine.
The file will be uploaded to the server machine, saved into the server license directory and then loaded on to the server.
|
Assigning Licenses
You must have network administrator privileges to complete the following procedure.
Unassigning Licenses to a Switch
You must have network administrator privileges to complete the following procedure.
Viewing Server Federation
| Step 1 | From the menu bar, choose Administration > DCNM Server > Federation.
The list of Servers along with its Status, Location, Local Time and Data Sources are displayed. | ||||
| Step 2 | Use the Enable Automatic Failover checkbox to turn on/off the failover functionality. | ||||
| Step 3 | In the Location column, double-click to edit the location.
If the status of one of the servers in the federation is Inactive, then some functionality may not work unless the server status changes to Active in the federation.
|
Native HA
| Step 1 | By default, DCNM is bundled with an embedded database engine PostgreSQL. The native DCNM HA is achieved by two DCNM’s running as Active / Warm Standby, with their embedded databases synchronized in real time. So once the active DCNM is down, the standby will take over with the same database data and resume the operation. The standby host database down scenario is documented after this procedure. |
| Step 2 | From the menu
bar, choose
Administration > DCNM Server > Native HA.
You see the Native HA window. |
| Step 3 | You can allow manual failover of DCNM to the standby host by clicking the Failover button, and then click OK. |
| Step 4 | You can allow manual syncing database and disk files to standby host by clicking Force Sync button, and then click OK. |
| Step 5 | You can test or validate the HA setup by clicking Test and then click OK. |
What to Do Next
Some HA troubleshooting scenarios are noted in this sub section.
-
Enter “ps -ef | grep post”. You should see multiple postgres processes running. If not, it indicates that the database is down.
-
Restore database data from a backup file that is created at the beginning of database synchronization. Change directory to “/usr/local/cisco/dcm/db”
-
Check existence of file replication/ pgsql-standby-backup.tgz. If the file exists, restore database data files: rm -rf data/* tar -zxf replication/ pgsql-standby-backup.tgz data /etc/init.d/postgresql-9.4 start ps -ef | grep post
The active DCNM host will synchronize the two databases.
-
Enter “grep bind /etc/xinetd.d/tftp” to check if the TFTP configuration file has the right bind address. If the displayed IP address is not the eth1 VIP address, then change the bind address to the VIP address. Repeat the procedure for the standby host. Update the bind address to the VIP address.
-
Enter " " /etc/init.d/xinetd restart” on the active host to restart TFTP.
Note | The TFTP server can be started or stopped with the “appmgr start/stop ha-apps” command. |
Multi Site Manager
| Step 1 | Multi-Site-Manager (MsM) provides a single pane for customer to globally search for switches managed by DCNM. MSM can do realtime search to find out which switch globally handle the traffic for a given virtual machine base on IP address, name or mac address, and supporting VXLAN basing on segment ID as well. It provides hyperlink to launch the switch only. This window also plays the role of remote site registration. The registration only allows the current DCNM server to access the remote DCNM server/site. For the remote site to access the current DCNM server, registration is required on the remote site as well. |
| Step 2 | From the menu
bar, choose
Administration > DCNM Server > Multi Site Manager.
The MsM window displays the overall health/status of the remote site and the application health. |
| Step 3 | You can search by Switch, VM IP, VM Name, MAC and Segment ID. |
| Step 4 | You can add new DCNM server by clicking +Add DCNM Server. The Enter Remote DCNM Server Information window opens. Fill in the information required and click OK to save. |
| Step 5 | Click Refresh All Sites to display the updated information. |
Management Users
The Management Users menu includes the following submenus:
Remote AAA
| Step 1 | From the menu
bar, choose
Administration > Management Users > Remote AAA
Properties.
The AAA properties configuration page appears. | ||
| Step 2 | Use the radio
button to select one of the following authentication modes:
| ||
| Step 3 | Click
Apply.
|
Local
Radius
| Step 1 | Use the radio button and select Radius as the authentication mode. |
| Step 2 | Specify the Primary server details and click Test to test the server. |
| Step 3 | (Optional) Specify the Secondary and Tertiary server details and click Test to test the server. |
| Step 4 | Click Apply to confirm the authentication mode. |
TACACS+
| Step 1 | Use the radio button and select TACACS+ as the authentication mode. |
| Step 2 | Specify the Primary server details and click Test to test the server. |
| Step 3 | (Optional) Specify the Secondary and Tertiary server details and click Test to test the server. |
| Step 4 | Click Apply to confirm the authentication mode. |
Switch
| Step 1 | Use the radio
button to select
Switch as the authentication mode.
DCNM also supports LAN switches with IPv6 management interface. |
| Step 2 | Specify the Primary Switch name and click Apply to confirm the authentication mode. |
| Step 3 | (Optional) Specify the Secondary and Tertiary Switch name and click Apply to confirm the authentication mode. |
LDAP
| Step 1 | Use the radio button and select LDAP as the authentication mode. |
| Step 2 | In the Host field, enter DNS address of the host. |
| Step 3 | Click Test to test the AAA server. The Test AAA Server window pops out. |
| Step 4 | Enter a valid
Username and
Password in the
Test AAA Server window.
A dialog box appears confirming the status of the AAA server test. If the test has failed, the LDAP Authentication Failed dialog box appears. |
| Step 5 | In the Port field, enter a port number. |
| Step 6 | (Optional) Select the SSL Enabled check box, if SSL is enabled on the AAA server. |
| Step 7 | In the Base DN field, enter the base domain name. |
| Step 8 | In the Filter field, specify the filter parameters. |
| Step 9 | Choose an option to determine a role by either Attribute or Admin Group Map. |
| Step 10 | In the Role Admin Group field, enter the name of the role. |
| Step 11 | In the Map to DCNM Role field, enter the name of the role to be mapped. |
| Step 12 | In the Access Map field, enter the Role Based Access Control (RBAC) group to be mapped. |
| Step 13 | Click Apply Changes icon on the upper right corner to apply the LDAP configuration. |
Managing Local Users
As an admin user, you can use Cisco DCNM Web Client to create a new user, assign the role and associate one or more groups or scope for the user.
This section contains the following:
Adding Local Users
| Step 1 | From the menu bar, choose Administration > Management Users > Local. You see the Local Users page. | ||
| Step 2 | Click
Add
User.
You see the Add User dialog box. | ||
| Step 3 | Enter the
username in the
User
name field.
| ||
| Step 4 | From the Role drop-down list, select a role for the user. | ||
| Step 5 | In the Password field, enter the password. | ||
| Step 6 | In the Confirm Password field, enter the password again. | ||
| Step 7 | Click Add to add the user to the database. | ||
| Step 8 | Repeat Steps 2 through 7 to continue adding users. |
Deleting Local Users
Editing a User
| Step 1 | From the menu bar, choose Administration > Management Users > Local. |
| Step 2 | Use the checkbox to select a user and click the Edit User icon. |
| Step 3 | In the Edit User window, the User Name and Role is mentioned by default. Specify the Password and Confirm Password. |
| Step 4 | Click Apply to save the changes. |
User Access
You can control the local users to access the specific groups on this page.
Managing Clients
You can use the DCNM Web Client to disconnect DCNM Client Servers.
Performance Setup
The Performance Setup menu includes the following submenus:
- Performance Setup LAN Collections
- Performance Manager SAN Collections
- Performance Setup Thresholds
- Configuring the RRD Database
- Configuring User Defined Statistics
Performance Setup LAN Collections
If you are managing your switches with the Performance Manager, you must set up an initial set of flows and collections on the switch. You can use Cisco DCNM Web Client to add and remove performance collections. The switch has to be licensed and in the Managed Continuously state before a collection for the switch can be created.
To add a collection follow these steps:
| Step 1 | From the menu bar, click Administration > Performance Setup > LAN Collections. |
| Step 2 | For all the licensed LAN switches, use the checkboxes to enable performance data collection for Trunks, Access, Errors & Discards, and Temperature Sensor. |
| Step 3 | Use the checkboxes to select the type(s) of LAN switches for which you want to collect performance data. |
| Step 4 | Click Apply to save the configuration. |
| Step 5 | In the confirmation dialog box, click Yes to restart the performance collector. |
Performance Manager SAN Collections
If you are managing your switches with the Performance Manager, you must set up an initial set of flows and collections on the switch. You can use Cisco DCNM Web Client to add and remove performance collections. The switch has to be licensed and in the Managed Continuously state before a collection for the switch can be created.
To add a collection follow these steps:
| Step 1 | From the menu bar, click Administration > Performance Setup > SAN Collections. |
| Step 2 | Select a fabric and select the Name, ISL/NPV Links, Hosts, Storage, FC Flows and FC Ethernet to enable performance collection for these data types. |
| Step 3 | Click Apply to save the configuration. |
| Step 4 | In the confirmation dialog box, click Yes to restart the performance collector. |
Performance Setup Thresholds
If you are managing your switches with the Performance Manager, you must set up an initial set of flows and collections on the switch. You can use Cisco DCNM Web Client to add and remove performance collections. The switch has to be licensed and in the Managed Continuously state before a collection for the switch can be created.
| Step 1 | From the menu bar, click Administration > Performance Setup > Thresholds. |
| Step 2 | Under Generate a threshold event when traffic exceeds % of capacity, use the checkbox to specify the Critical at and Warning at values. The range for Critical at is from 5 to 95, and the default is 80. The range for Warning at is from 5 to 95, and the default is 60. User can also use the For ISL/Trunk Only checkbox to limit the threshold events generated to ISL and Trunk events only and then click Apply. |
Configuring the RRD Database
Configuring the Round Robin Database (RRD) allows you to set the intervals at which data samples are collected. After applying the configuration, the database storage format is converted to a new format at those intervals. Because database formats are incompatible with each other, you must copy the old data (before the conversion) to the $INSTALLDIR/pm directory. See the Importing the RRD Statistics Index.
| Step 1 | From the menu bar, choose Administration > Performance Setup > Database.
You see the Performance Database (collection interval) page. | ||
| Step 2 | In the top row of the Days column, enter the number of days to collect samples at 5-minute intervals. | ||
| Step 3 | In the second row of the Days column, enter the number of days to collect samples at 30-minute intervals. | ||
| Step 4 | In the third row of the Days column, enter the number of days to collect samples at 2-hour intervals. | ||
| Step 5 | In the bottom row of the Days column, enter the number of days to collect samples at 1-day intervals.
As of Cisco SAN-OS Release 3.1(1) and later releases, you can configure the sampling interval for ISLs. Select a sampling interval from the ISLs drop-down list. | ||
| Step 6 | Click Apply to apply your changes, or click Defaults to reset the file sizes to the default values.
If you are applying new values, or if the current values are not the default values, you see a message indicating that the conversion of the RRD files take a certain amount of time and that the database is unavailable until then. The time it takes depends on the difference between the old and new values.
If you want to perform this procedure, perform it before collecting a lot of data because data conversion can take a long time. |
Importing the RRD Statistics Index
Configuring User Defined Statistics
| Step 1 | From the menu bar, choose Administration > Performance Setup > User Defined.
You see the User Defined page. | ||
| Step 2 | Click Add icon.
You see the Add SNMP Statistic to Performance Collection dialog box. | ||
| Step 3 | From the Switch table, select the switch for which you want to add other statistics. | ||
| Step 4 | From the SNMP OID drop-down list, select the OID.
| ||
| Step 5 | In the Display Name box, enter a new name. | ||
| Step 6 | From the SNMP Type drop-down list, select the type. | ||
| Step 7 | Click Add to add this statistic. |
Event Setup
The Event Setup menu includes the following submenus:
Viewing Events Registration
To enable Send Syslog, Send Traps and Delayed Traps you need to configure the following in the DCNM-SAN client:
-
Enabling Send Syslog — Log into the DCNM-SAN client. In the Physical Attributes pane, Select Events > Syslog > Servers. Click the Create Row icon, provide the required details and click Create.
-
Enabling Send Traps — Log into the DCNM-SAN client. In the Physical Attributes pane, Select Events > SNMP Traps > Destination. Click the Create Row icon, provide the required details and click Create.
-
Enabling Delayed Traps — Log into the DCNM-SAN client. In the Physical Attributes pane, Select Events > SNMP Traps > Delayed Traps. In the Feature Enable column, use the checkboxes to enable delayed traps for the switch and specify the delay in minutes.
| Step 1 | From the menu bar, choose Administration > Event Setup > Registration.
The SNMP and Syslog receivers along with the statistics information are displayed. |
| Step 2 | Select Enable Syslog Receiver checkbox and click Apply to enable the syslog receiver if it is disabled in the server property.
To configure the Event Registration/Syslog properties, select Administration > DCNM Server > Server Properties and follow the on-screen instructions. |
| Step 3 | Select Copy Syslog Messages to DB and click Apply to copy the syslog messages to the database.
If this option is not select, the events will not be displayed in the events page of the Web client. The columns in the second table displays the following: |
Notification Forwarding
You can use Cisco DCNM Web Client to add and remove notification forwarding for system messages.
This section contains the following:
Adding Notification Forwarding
You can use Cisco DCNM Web Client to add and remove notification forwarding for system messages.
Cisco DCNM Web Client forwards fabric events through e-mail or SNMPv1 traps.
Note | Test forwarding will only work for the licensed fabrics. |
| Step 1 | From the menu bar, choose Administration > Event Setup > Forwarding. | ||
| Step 2 | The events forwarding scope, the recipient email address, severity of the event and type of the event is displayed. The description Regex field is applicable only when the forwarding source is selected as Syslog while adding the events forwarder. | ||
| Step 3 | Check the Enable checkbox to enable events forwarding. | ||
| Step 4 | Specify the SMTP Server details and the From e-mail address. | ||
| Step 5 | Click Apply to save the configuration, or in the Apply and Test icon, use the drop-down to select the fabric and click Apply and Testto save and test the configuration. | ||
| Step 6 | In the Event Count Filter, you can add a filter for event count to event forwarder. The forwarding will stop forwarding an event if the event count exceeds the limit specified by the event count filter. In this field you can specify a count limit. Before an event can be forwarded, the Cisco DCNM will check if its occurrence exceeds the count limit. If it does, the event will not be forwarded. | ||
| Step 7 | Select the Snooze checkbox and specify the Start date and time and the End date and time. Click Apply to save the configuration. | ||
| Step 8 | Under the
Event
Forwarder Rules table, click the
+ icon to add an event forwarder rule.
You see the Add Event Forwarder Rule dialog box. | ||
| Step 9 | In the Forwarding Method, choose either E-Mail or Trap. If you choose Trap, a Port field is added to the dialog box. | ||
| Step 10 | If you choose the E-mail forwarding method, enter the IP address in the Email Address field. If you choose the Trap method, enter the trap receiver IP address in the Address field and specify the port number. | ||
| Step 11 | For Forwarding Scope , choose the Fabric/LAN or Port Groups for notification. | ||
| Step 12 | In the
Source field select
DCNM or
Syslog.
If you select
DCNM, then:
The traps sent by Cisco DCNM correspond to the severity type followed by a text description: trap type(s) = 40990 (emergency) 40991 (alert) 40992 (critical) 40993 (error) 40994 (warning) 40995 (notice) 40996 (info) 40997 (debug) textDescriptionOid = 1, 3, 6, 1, 4, 1, 9, 9, 40999, 1, 1, 3, 0 |
Removing Notification Forwarding
You can remove notification forwarding.
Configuring EMC CallHome
Cisco DCNM Release 7.1.x DCNM enhances EMC call home messages. DCNM version information is displayed in with the call home message.
You can configure EMC Call Home from the Cisco DCNM Web Client for EMC supported SAN switches.
| Step 1 | From the menu bar, choose Administration > Event Setup > EMC Call Home. |
| Step 2 | Select the Enable check box to enable this feature. |
| Step 3 | Use the check box to select the fabrics or individual switches. |
| Step 4 | Enter the general e-mail information. |
| Step 5 | Click the Apply to update the e-mail options. |
| Step 6 | Click Apply and Test to update the e-mail options and test the results. |
Event Suppression
Cisco DCNM allows you to suppress the specified events based on the user-specified suppressor rules. Such events will not be displayed on the Cisco DCNM Web Client and SAN Client. The events will neither be persisted to DCNM database, nor forwarded via email/SNMP trap.
You can view, add, modify and delete suppressor rules from the table. You can create a suppressor rule from the existing event table. Select a given event as the template, and invoke the rule dialog window. Event details are automatically ported from the selected event in the event table to the input fields of the rule creation dialog window.
This section includes the following:
Add Event Suppression Rules
To add rules to the Event Suppression, do the following tasks:
| Step 1 | From the menu bar, select Administration > Event Setup > Suppression. | ||||
| Step 2 | Click the Add icon above the Event Suppressors table. | ||||
| Step 3 | In the Add Event Suppressor Rule window, specify the Name for the rule. | ||||
| Step 4 | Select the required Scope for the rule based on the event source.
In the Scope drop-down list, the LAN groups and the port groups are listed separately. You can choose SAN, LAN, Port Groups or Any. For SAN and LAN, select the scope of the event at the Fabric or Group or Switch level. User can only select group(s) for Port Group scope. If use selects Any as the scope, the suppressor rule will be applied globally. | ||||
| Step 5 | Enter the Facility name or choose from the SAN/LAN
Switch
Event
Facility List.
If you do not specify a facility, wild card will be applied. | ||||
| Step 6 | From the drop down list, select the Event Type.
If you do not specify the event type, wild card will be applied. | ||||
| Step 7 | In the Description
Matching field, specify a matching string or regular expression.
The rule matching engine uses regular expression supported by Java Pattern class to find a match against an event description text. | ||||
| Step 8 | (Optional) Check the Active Between box and select a valid time range during which the event will be suppressed.
By default, the time range is not enabled, i.e., the rule will be always active.
|
Delete Event Suppression Rule
To delete event suppressor rules, do the following tasks:
Modify Event Suppression Rule
To modify the event suppressor rules, do the following tasks:
Feedback