...
To create and schedule a new Jobjob, perform the following:
- At the top right of the page, click New. The Fill Out Job Details Wizard opens.
- Enter a Job Name.
Click the Approved option if your user account allows it. (A job cannot be scheduled until approved. Another admin account may need to approve the scheduled job.) - Type a Job Description of the job.
...
- In the Actions column, click the icon and choose Edit from the menu. The Job Wizard opens to the Summary of Job screen.
- Click Edit. The Fill out Job Details screen appears.
- Edit the job as needed. Use the Next –> and <– and Previous buttons to navigate the wizard.
- Navigate to the Review and Save screen, and then click Save
.Anchor bookmark572 bookmark572
...
To run a script as a job immediately, perform the following:
- Go to Config Management –>> Job Management –>> Scripts tab.
- Hover the mouse over the Action menu for your desired script, and choose Run Now from the Action menu.
The Script Run Now window appears. You can choose to run a script (the default) or a template as a job. Templates support a push mode; scripts do not. - If any input is required by the selected script, enter it in the right panel and click Next. (Note that in this step, the selected script is highlighted in the left pane of the window, listed with all other scripts in the library.)
- If you have custom fields for data entry, add that information and click Next. If not, simply click Next.
- Select the Device Groups or Devices to run the job against from their respective tabs and click the (–>) button to add them to the job, and then click Next.
Click the -> and <- buttons to navigate pages of the Device Groups and Devices lists.
In the Devices list, use the Device Groups drop-down menu to choose the device group for device selection.
In the Devices list, use the Search box and type in a string of any length to search for a device name or an IP address. You can also search by the values shown in the Network View field. - On the Review and Run page, review your settings. If necessary, use the <- Previous button to return to previous steps to make changes. When you are finished, click Run Now to begin the script or template execution.
...
| Note | ||
|---|---|---|
| ||
A new variable is available for use in script templates: the $NetMRI_ipaddress variable, whose data is formatted in standard dotted-quad format. It sets a variable for the IP address of the device. |
The Config Templates tab (Config Management –> > Job Management tab –> > Config Templates) provides an editing environment to develop standard configuration files. This feature is required for provisioning network devices using the Automation Change Manager's Bare Metal Provisioning (BMP) task, specifically for Cisco and Juniper routers and switches.
...
The Config File Template window (Config Management –> > Job Management –> > Config Templates –> > New) provides a Template Variables field as part of creating a template. As previously noted, variables are optional in template definition, but knowing their format is useful.
Defining variables for config templates uses the same format as for script variables, in which three entries are provided for each vari
| Anchor | ||||
|---|---|---|---|---|
|
...
To import a list onto the NetMRI Lists page, perform the following:
- On the Config Management –> > Job Management –> > Lists page, choose Import.
- Click Browse and locate the CSV file in the file selector. Click Open after selecting the file.
- Click Import to import the file onto the Lists page.
...
In some cases, a switch type may not be defined in the LIsts page. To define a new list entry:
- Go to Config Management –> > Job Management –> > Lists.
- Select the ACM BMP Switch Model Interface Defs list in the left pane.
- Click Add Row.
Under Vendor Model, enter the desired model name (Cisco or Juniper). Example: cisco_catalyst6500.
Note title Note
...
The name cited here must match that for a Config Template.
- Enter the slot/port values, including port ranges, separated by commas, in the Interfaces column.
- Click Save.
...
You create and manage triggered jobs in the Config Management –> > Job Management –> > Triggered Jobs tab. You define triggered jobs using a Triggered Jobs Wizard. The table of jobs includes the following columns of information:
...
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
| Note | ||
|---|---|---|
|
...
An example of a triggering event is: NetMRI discovers a new Cisco switch on the network. This event is embodied in a bit of data called a Trigger Source, which defines the nature of the event. |
...
For more information, see Automation Change Manager (ACM) Triggering Sources |
...
. |
As part of the triggered job definition, you specify the triggering event, the time periods over which
| Anchor | ||||
|---|---|---|---|---|
|
For triggering events, a job's settings, such as script and variable input, define a template for new jobs to perform remedial actions, gather further information from the device, and other actions. The triggered job runs once per affected device, when NetMRI detects an issue or policy rule violation on that device. If the condition clears, and subsequently occurs again, the triggered job runs again.
...
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
| Note | ||
|---|---|---|
|
...
The NT-1400, NT-2200 and NT-4000 appliances, NetMRI 1102-A, and Virtual appliances with sufficient CPU and memory support the Automation Change Manager. |
This procedure encompasses configurations from both NetMRI and Infoblox NIOS systems. A number of assumptions are made for purposes of brevity:
- The user has the proper admin or superuser access to both the Automation Change Manager and to the NIOS system;
- The correct ACM license is installed on both the Automation Change Manager and on the NIOS Grid Master. A separate ACM license must be installed for both the NetMRI appliance, and for the NIOS appliance that will communicate with NetMRI.
- If the NetMRI appliance is based on a virtual machine, you must also set up a second VM as the NetMRI sandbox for job operation. See Using the NetMRI Sandbox and Setting up a Remote Sandbox for complete information on Sandbox setup and operation.
| Note | ||
|---|---|---|
|
...
To ensure that the proper license is installed in the NetMRI system, go to the Settings icon |
...
> Setup > Settings Summary and read the Module Settings list. Automation Change Manager should read Enabled. |
The administrator admiistrator can use the Automation Change Manager with a NIOS Grid by meeting the prerequisites below.
- Set the NIOS DHCP appliances to serve DHCP Options 66 for Cisco devices and DHCP Option 68 for Juniper devices. Each setting, if used, also requires entry of the IP address for NetMRI. This is further described in the topic Notes on DHCP Configuration for ACM Operation;.
- Set the NetMRI inactivity timeout (60 minutes by default; In NetMRI, go to the Settings icon –>Setup –> > Setup > Advanced Settings –> > User Interface category –> > Inactivity Timer), and set this value to a higher time duration than for any NIOS system (in NIOS, go to Grid –> > Grid Properties);.
- Register the NetMRI appliance with NIOS, with or without a certificate for secure HTTPS communication (for information, see ACM Registration and Certificate Usage Between NetMRI and NIOS);.
- Obtain the factory MAC address for each of the new devices to be installed into the network, plus the initial IP address to be assigned to the devices;.
The admin account running ACM jobs on NIOS, and performing ACM setup on the NetMRI system, must be properly defined on both systems. The user name must be the same on both systems. Access privileges must be equivalent on both sides of the configuration; the account Roles/Privileges defined in NetMRI determine the ACM features to which the user has access in NIOS
;.
Note title Note
...
The ACM system supports single sign-on between the NIOS and NetMRI appliances When you sign on to one appliance in ACM, the other appliance automatically recognizes the login. For information, see Creating a Single-Sign-On Admin Account.
- Set the admin accounts to be notified when ACM Issues and events pop up. The best location to view event information is the Task Viewer in NIOS' Automation Tasks Dashboard. Triggering issues and events are reported on NetMRI's main Issues page in Network Analysis –> > Issues. Additional configuration may be needed to ensure notifications are sent to the right people.
You may need to define NetMRI Issue notifications in on the Settings icon –> > Notifications section –> > Subscriptions page. Notifications are sent in three ways: Syslog messages, email, e-mail and SNMP traps. For information, see Managing Issue Notifications , and Defining a Job Notification for specific configuration. - All NIOS appliances running DHCP services must be configured to forward Syslog messages to NetMRI. This ensures the Automation Change Manager detects the correct events for triggering jobs (you perform this task in the topic Deployment for Bare Metal Provisioning, Pt. 1;.
- Activate a TFTP server with configuration stub files and full configuration files for the device types to be supported. NetMRI has a built-in TFTP server that is always running by default and is accessible by the same methods as any TFTP server. For information, see Notes on TFTP Service for ACM Operation.
...
To define the required ACM admin account on both NIOS and NetMRI, do the following:
- In NetMRI, go to the Settings icon –>General > General Settings –> > Advanced Settings and go to the NIOS Administration section.
- Under NIOS User Name (on Page 2 of Advanced Settings), click the gear icon and choose Edit.
- Enter the user name of a NIOS admin account with privileges to validate DHCP servers located on the network by NetMRI. Click OK when finished.
- Under NIOS Password (on Page 2 of Advanced Settings), click the gear icon and choose Edit.
- Enter the password for the admin account you entered in Step 3, re-enter it to confirm; click OK when finished.
...