...
- On the Config Management –> Job Management –> Lists page, select the list to export and choose Export.
- The browser prompts to open the data as a new Excel .CSV file or to save the data as a new file.
...
Pre-Defined Lists for ACM Operation
The Automation Change Manager (ACM) relies on a series of lists in the Config Management –> Job Management –> ListsAnchor
- ACM Allowed DHCP Servers – List of any DHCP servers in the enterprise network, that are not to be included in any Rogue DHCP server reports. Defines to NetMRI and to the NIOS system that "these are the established DHCP servers in the network; do not report against these devices." Any router or other device that is not on this list, which offers DHCP-based IP configuration to clients connecting to the network will cause an issue to be fired by the Automation Change Manager.
- ACM BMP Device Provisioning – Bare Metal Provisioning list, to identify each switch to be provisioned. New switches are identified by their MAC address, the management IP address and site settings, including a Site Settings Name which corresponds to a name in the ACM BMP Site Settings list. The MAC address is the hardware MAC address assigned to the device coming out of the factory, and which is usually stamped on the rear of the chassis or on the shipping
Anchor bookmark590 bookmark590 box for the device. (This list is used in the topic Checklist for Running The topic Job Management and Automation Change Manager System .) - ACM BMP Site Settings – Bare Metal Provisioning list to define the default switch port configuration. Consider it a branch office list–to contain the standardized configuration templates for any new devices installed in a given branch office network. This list defines values such as the Management VLAN ID and its VLAN name, the port designated for management VLAN traffic, the domain name, Syslog and Network Time Protocol server information, and VLANs on the provisioned device to be configured on individual access ports or ranges of access ports (VLAN1 Ports and VLAN2 Ports). (This list is used in the topic Checklist for Running The topic Job Management and Automation Change Manager System .)
- ACM BMP Switch Model Interface Defs – Bare Metal Provisioning list defining the interfaces for the device types expected to be provisioned through the job. If the switch model to be provisioned is already in this table, no further information is needed here. The entries follow the standard slot/port designator formats for Cisco and Juniper devices such as Cisco 2950 and 3750 switches and Juniper EX2200 switches. You may need to create your own definitions within this list (or even new lists) to match switch port designators for provisioning other device types. (This list is used in the topic Checklist for Running The topic Job Management and Automation Change Manager System .)
- ACM Script Settings – Defines the VLAN to which any rogue DHCP server, detected and isolated on the network, is placed for remedial action. By default, when this task executes, the isolation VLAN is defined as VLAN 99.
...
Defining Larger Provisioning
...
Configurations
Switch model interface definitions for the ACM BMP Switch Model Interface Defs list merit further description. A column titled Interfaces provides the location for specifying the ranges of ports for initial bare-metal configuration. A simple Cisco 2950 port configuration shows a port range for a single "slot:"
...
In this case, for example, VLAN 100 on the switch to be provisioned is assigned to Fast Ethernet ports 1 through 4, and to a second port range 6 through 10.
...
Configuring a New List Entry
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.
...
- 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.
...
Triggering Jobs Through Events
...
NetMRI triggered jobs allow a script NetMRI triggered jobs allow a script or template with predefined or custom variables to execute against a device when a "triggering source event" occurs. The Automation Change Manager triggered jobsAnchor
...
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:
Actions | Actions are View/Edit and Delete. Choosing View/Edit displays the Triggered Job Wizard showing the current job's Job Summary. |
Click Edit |
to make changes to the job. | |
Name | The defined name for the triggered job. |
Level | The importance level of the job. |
Enabled | Define whether the job is enabled for execution. |
Active Window | The execution time period during which the job will run if executed. |
Trigger Type | The event that causes the job to execute: Issue, or Policy Rule violation. |
Trigger Event | A description of the trigger event, such as Rogue DHCP Server Detected. |
Device Groups | Jobs can also run against All device groups. |
| Action | One of two possible actions can occur when the trigger event takes place: Run Job Immediately/Auto-Run or Schedule Job. The Run Job Immediately option also offers an Auto-approval checkbox, which is available only for the NetMRI admin user. |
| Created On and Updated On | Date and time where the job was created, and the date and time where the job was last updated. |
| Last Run | The last date and time where the job executed. |
| Job Type | The type of job, defined as |
| script or |
| template based on the selection. | |
| Created By and Updated By | The NetMRI user account that created the job and that last edited the job. |
...
Defining Triggered Jobs
...
Note: As part of triggered job definition, you specify the triggering event, the time periods over which you would like this trigger to be active, and the device and interface groups to whose members the trigger applies.
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. Also see the following topic, Automation Change Manager (ACM) Triggering Sources , for more detail.As part of triggered job definition, you specify the triggering event, the time periods over whichAnchor
For triggering events, a job's settings,
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.
...
Once a job is listed in the table, check its Status, Last Run and Result in the Scheduled Jobs tab.
To view job details: Click Edit. The Triggered Job Wizard appears, listing a summary of the job. From this point, click Edit if you wish to edit the job by choosing new trigger sources and other settings.
To delete the job from execution: Click Delete, then confirm the deletion.
...
Automation Change Manager (ACM)
...
Triggering Sources
One category of triggering sources involves the Automation Change Manager. When the ACM license is installed into the NetMRI appliance, specific trigger source types are automaticallyAnchor
...
Two triggering sources support a single ACM task. The Locate Rogue DHCP Server and Isolate Rogue DHCP Server jobs support the NIOS Dashboard Rogue DHCP Server Remediation task. Locate Rogue DHCP Server executes automatically in response to Automation Change Manager detection of a NIOS DHCPACK Syslog messages on the network. Isolate Rogue DHCP Server jobs require authorization by the administrator to execute.
...
Checklist for Running The Automation
...
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.
...
Change Manager System
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 | ||
|---|---|---|
| ||
|
The administrator 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
- Set the NetMRI inactivity timeout (60 minutes by default; In NetMRI, go to Settings icon –>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;
...
- . 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.
...
- 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 the Settings icon –> Notifications section –> Subscriptions page. Notifications are sent in three ways: Syslog messages, 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 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 .
...
Creating a Single-Sign-On Admin Account
...
To define the required ACM admin account on both To define the required ACM admin account on both NIOS and NetMRI, do the following:
- In NetMRI, go to Settings icon –>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.
...
Notes on DHCP Configuration for ACM Operation
Note: Under some circumstances, the Rogue DHCP Server Detected issue may not trigger. NetMRI sends DHCP packets that will obtain responses from DHCP servers that can traverse networks through DHCP relays. Not all DHCP server will respond to DHCP packets sent by NetMRI for detection purposes. Also, some DHCP servers may be undetectable by NetMRI based on their position in the network; for example, DHCP servers that are connected to WAN interfaces and only send DHCP responses downstream will not respond to probes by NetMRI.
The Automation Change Manager acts on NIOS-generated DHCPACK syslog messages for triggering task execution. Part of NIOS configuration to support ACM consists of forwarding the syslog stream to NetMRI. This is typically done on a per-Grid-Member basis. DHCPACK syslog messages are sent whenever a DHCP lease is granted or renewed and contain the IP and MAC address of the end host. Upon receipt of a DHCPACKAnchor
Under some circumstances, the Rogue DHCP Server Detected issue may not trigger. NetMRI sends DHCP packets that will obtain responses from DHCP servers that can traverse networks through DHCP relays. Not all DHCP server will respond to DHCP packets sent by NetMRI for detection purposes. Also, some DHCP servers may be undetectable by NetMRI based on their position in the network; for example, DHCP servers that are connected to WAN interfaces and only send DHCP responses downstream will not respond to probes by NetMRI.
If the discovered device/end host is found to be running a DHCP server, NetMRI raises a Rogue DHCP Server Detected issue and a series of events takes place, further described in the topic Activating Rogue DHCP Server Remediation.
NIOS DHCP configuration intuitively supports custom DHCP options, which follow the RFC 2132 guidelines. DHCP configuration settings can quickly apply across the entire NIOS grid (in NIOS, Grid Manager –> DHCP –> Grid DHCP Properties), or to a specific DHCP range on a specific member. The same guideline applies if NetMRI operates with a standalone NIOS appliance running the DHCP service in the network. You can also create new DHCP rangesAnchor
For Cisco:
- option tftp-server-name code 66 = text (Option 66, uses the IP address of the TFTP server or an FQDN);
...
All NIOS appliances running DHCP service must also forward Syslog syslog messages to NetMRI.
The Automation Change Manager also detects DHCPACK messages automatically through its own Syslog syslog service, and uses them as the triggers for ACM tasks.
Note: For more details on configuring the DHCP service on NIOS systems, see the Infoblox NIOS Administrator Guide, Chapter 19, Infoblox DHCP Services and Chapter 20, Configuring DHCP Properties.
...
Notes on TFTP Service for ACM Operation
...
...
A NIOS appliance can also operate as a TFTP server. The enterprise network may also have an existing public TFTP server. For more information on usAnchor
...
transport input telnet ssh
end
...
If the administrator wants to deviate from the autoconfig string (i.e. for hostname, community string and/or CLI credentials), the following holds true:
...
You can edit the configuration files to contain your own credentials and settings. Access configuration files by using the NetMRI administrative shell and entering an ls tftp command. When finished, run the NetMRI tftpsync command to move these files into the public TFTP server file system.
Note: NetMRI also runs a TFTP service by default and may be used for serving configuration files.
...
ACM Registration and Certificate Usage
...
Between NetMRI and NIOS
Note: The ACM system supports single sign-on between the NIOS and NetMRI appliance. When you sign on to one appliance in ACM, the other appliance automatically recognizes the login.
You can install a CA certificate to secure communications between the NetMRI appliance and the NIOS appliance. The best method is to export a certificate inAnchor
The ACM system supports single sign-on between the NIOS and NetMRI appliance. When you sign on to one appliance in ACM, the other appliance automatically recognizes the login.
- Open the NetMRI Administrative Shell (connect by SSH to the appliance and enter the administrator name and password) and enter:enter
export cert
...
- . The system copies a NetMRI self-
...
- signed certificate suitable for use with the NIOS host, netmri.crt, to the root directory of the NetMRI appliance.
2. Transport the file to a location accessible from your workstation's local file system.
...
11. Click Register. NetMRI registers with the NIOS appliance and the certificate is added to secure HTTPS communications between the hosts.
...
Deployment for Bare Metal Provisioning, Pt. 1
The Provision Bare Metal Device automated task enables automated installation of new switches and routers into the network.
...
- Ensure the DHCP Options configuration is defined for all NIOS DHCP servers/DHCP ranges that will inter-operate with the Automation Change Manager. For more information, See Notes on DHCP Configuration for ACM Operation .
- Configure the NIOS appliance to forward Syslog notifications to NetMRI; on the NIOS appliance, choose Grid –> Grid Manager –> Members –> Grid Properties. Choose UDP as the transport protocol.
- Ensure the NIOS appliance is running the NTP protocol:
- From the Grid tab, select the Grid Manager tab -> Members tab -> Grid_member check box.
- Expand the Toolbar and click NTP -> NTP Member Config. If the Enable this Member as an NTP Server checkbox is enabled, nothing else needs to be done and you continue to Step 4.
- Ensure the TFTP server is up and running with the desired initial configuration files ready for download, and reachable within the network. For more information, see Notes on TFTP Service for ACM Operation .
- The required admin user accounts should receive the appropriate notifications when Bare Metal Provisioning jobs occur. Consult the topic Defining a Job Notification for more information.
- Ensure that the proper license is installed in the NetMRI appliance by going to Settings icon –>Setup –> Settings Summary; check the Module Settings list. Automation Change Manager should read Enabled. (If necessary, also ensure the proper license is already installed in the NIOS system.)
- Register NetMRI with the NIOS system. This is done in NIOS through the following:
- From the Dashboards tab, select the Tasks tab.
- In the Automation Tasks pane, click the down arrow gadget and select ACM Registration.
- Under ACM Settings, do the following:
- Enter the IP address or resolved host name of the Automation Change Manager system supporting the Automation task pack.
...
- Optionally, you can load a CA certificate from NetMRI to NIOS to secure communications between the two systems.
...
- Enter the ACM Admin Password.
d. Click Register to commit settings.
...
13. Also in the SNMPv1/2c page, click New and create a new community string infoblox. Assign it a Priority value of 2 and click Add.
14. Continue to the following topic, Deployment for Bare Metal Provisioning, Pt. 2
...
Deployment for Bare Metal Provisioning,
...
Pt. 2
NetMRI provides Config Templates to support Bare Metal Provisioning for several standard Cisco and Juniper device types.
- If you plan to create any new config templates for different device models beyond the models built in to the Automation Change Manager release, do so now. Note that the set of variables defined in the config templates are fixed. They are set by the values in the columns in the TAE BMP Device Provisioning list or from the TAE BMP Site Settings list. For more information, see Working with Configuration Templates .
- In the TAE BMP Switch Model Interface Defs list: If the switch model to be provisioned is already in the table, no information needs to be entered about interface configuration. If you have new model information, add the Vendor Model Key value and interfaces values for the new device types from Juniper or Cisco. Click Save when done.
...
- The Vendor Model Key must be named identically to the config template referenced by the system. For example, the Config Template
cisco_catalyst295024matches the corresponding Vendor Model Key field in the list.
The TAE BMP Switch Model Interface Defs list maps the device model to the ports available on that type of device. The Model column is the name of the device model as reported by the device. The same model name is also used to select the configuration template to be used for the device.
...
7. Click the Settings icon for the Bare Metal Provisioning task. The NetMRI instance appears in a new browser tab, displaying the Job History page. You track job execution here or in the NIOS Task Dashboard's Task Viewer. For information, see Viewing the Job History and the Job Viewer.
Perl Scripts for Bare Metal Provisioning
A number of read-only scripts are included in the licensed Automation Change Manager package. The Provision Bare Metal Device script is referenced by the Provision Bare Metal Device triggered job. For information, see Triggering Jobs Through Events. This script runs whenever the template job is invoked by NetMRI's detection of a new network device. Explore this NetMRI page for more script examples that can provide ideas for development.
...
Activating Rogue DHCP Server Remediation
All DHCP servers on the network should be under administrative control. If any device offering DHCP leases to clients on the network is not properly administered, it violates many security guidelines and may cause configuration problems throughout the network. Some events may be unwitting or innocuous (an office worker installing a wireless access point in their cube to share a resource), or may be an attempt to hijack clients and steal information. To prevent such issues, the Rogue DHCP Server Remediation task performs detection, location and isolation of such devices.
The Rogue DHCP Server Remediation automated task does not provide NIOS-based settings; configuration for this task is done in the NetMRI user interface. The task is triggered by detection of a network device requiring remediation.
As noted in the Triggering Jobs Through Events topic, two Triggered Jobs Two triggered jobs are associated with rogue DHCP remediation:
...
After any rogue DHCP server is detected and located by the Automation Change Manager, the device is isolated to a designated isolation VLAN for remediation. This job requires approval by the administrator to execute.
...
Rogue DHCP Server Checklist and Process
...
...
Configuration for the ACM Rogue DHCP Server Remediation task is straightforward.
- Rogue DHCP remediation begins with preventing established, legitimate DHCP servers, such as NIOS appliances supporting the DHCP service, from being identified as a rogue server. You compile all legitimate DHCP servers on the network into the ACM Allowed DHCP Servers list (Config Management –> Job Management –> Lists);
- Because the Rogue DHCP jobs are issue-driven, a suspected rogue device may first need to be detected by NetMRI. Ensure fingerprinting is enabled in the NetMRI system (Settings – Setup –> Network Polling –> Fingerprinting checkbox);
- Also ensure that the required user accounts get the appropriate notifications when Rogue DHCP events occur. Consult the topic Defining a Job Notification for specific information.
- NetMRI also scans the standard DHCP TCP and UDP ports (check settings in (Settings – Setup –> Network Polling and enter "bootp" as the search string in the Port Scan List).
- The NIOS administrator account username and password should be added to Advanced Settings (Settings icon –>General Settings –> Advanced Settings –> page to the NIOS Administrator category).
To enable the NetMRI-to-NIOS communication, you also define the NIOS administrator User ID and password that NetMRI will use to check the configuration in NIOS. If this is not yet in place, see Creating a Single-Sign-On Admin Account.
Rogue DHCP Triggering Events
...
- The upstream switch port from which the DHCP messages originated is found, and that upstream port has only a single downstream MAC address connected to it. This downstream MAC address is the culprit.
- A Rogue DHCP Server Located Issue displays in NetMRI's main Issues table (Network Analysis –> Issues) and in the NIOS Task Viewer. Then, after approval, the Isolate Rogue DHCP Server task activates.
Click the Issue name in the Title column; the Issue Viewer appears in a separate browser window. Details of the issue are substantial, including the specific Device IP address, the device MAC and type, the identity of the upstream switch and the upstream interface, and the Last Seen timestamp.
Any previously configured notifications will arrive at the admin's Inbox or through other channels. - Go to the NIOS system and open the Tasks Dashboard.
- Click the Settings icon for the Rogue DHCP Server Remediation task. The NetMRI instance appears in a new browser tab, displaying the Job History page. This is where you track job execution in NetMRI. (For information, see Viewing the Job History and the Job Viewer ). The page lists the Locate and Isolate jobs and their results. You can also open the Task Viewer in the NIOS Task Dashboard.
...
Should any of these four results take place, the Automation Change Manager sends a new Issue, Rogue DHCP Server Cannot be Isolated. The Issue report also provides the specific reason that the device wasn't isolated.
...
that the device wasn't isolated.
Rogue DHCP Issues and Notifications
Whether the match is positive or negative, triggering issues are reported on NetMRI's main Issues page in Network Analysis –> Issues and in the NIOS Task Viewer. NetMRI Issue notifications are created, in the Settings icon –> Notifications section –> Subscriptions page. The system sends notifications in one of three ways: Syslog messages, e-mail and SNMP traps. For more information, see Managing Issue Notifications.
...
Viewing
...
the Job
...
History and the Job Viewer
...
...
The Job History tab (Config Management –> Job Management –> Job History tab) lists all running jobs, scheduled jobs, and jobs that finish with errors. Information displayed in the table includes job status, start and end times, and run count.
...
Click the hyperlink in the Script column. A browser pop-up window appears displaying the script text.
...
Using the Job Viewer
...
...
The Job Viewer (opened fromAnchor
...
- The Files tab lists files created using the ARCHIVE keyword. You can view and download files from within this tab. (If the ARCHIVE keyword is not used in the script, this tab is empty.)
- Click the Cancel icon for that device.Turn auto-refresh On or Off from the Refresh dropdown.
...
- The Cancel icon
...
- appears in the Actions column for a device
...
- only if the job is currently pending or running on that device. The Actions column is empty if the job has been completed for all devices.
- Turn auto-refresh On or Off from the Refresh dropdown.
- Click Cancel All to cancel all running Jobs in the page.
You create Views views by resizing columns, by dragging column headers into different orders in the Viewer, and by adding or removing individual columns in the window.
Save views by using the Views pull-down menu.
You filter Job Details job details based on an expected value or multiple that may appear in any Job Viewer column.
To filter job information, do the following:
...
- Click the Rerun Errors button. The Run... Script dialog appears.
- In the Run... Script dialog, double-click items in the Hosts lists to add them to the Selected list. The Selected list represents the devices against which the job should be re-run.
- Click Run Now.
- Click OK to continue.
...
Viewing Job Details
...
The Job Details Viewer opens from any hyperlink in the Status column in the Job Viewer. A Connections dropdown appears in the top of the Job Details Viewer. For Perl/Python jobs that open simultaneous connections with multiple devices, each device in the job is listed here. Toggling through the devices shows the corresponding job details for the given device in the Job Details Viewer.
- If a script includes the ability to run multiple sessions, you can see the sessions running under the JobDetailsViewer–>Connections drop-down list.
- The Script tab displays the full script run against the device;
- The StatusLog tab shows the results of various internal script operations. Some of the information here may be useful in troubleshooting a failure. A color-coded view of the information in this tab is available in the ProcessLog tab;
- The ProcessLog tab shows individual steps or actions in the job on the device, including which matches occurred and whether an issue was generated (if the script generates an issue). This analysis is limited to 500 lines of output; if more than 500 lines of output were created, you can view the entire analysis in the process.pdf file available in the Files tab;
- The SessionLog tab lists the session details, indicating all CLI events that occurred during the job;
- The Files tab provides links to download any files related to the job for this device. The all.zip file contains copies of all associated files for convenience in downloading.
...
Using Perl Or Python Libraries
...
Note: You store Perl or Python subroutines in NetMRI's dedicated Libraries page. LIbraries provides standard Copy, Export, Edit and Delete options.
Read/write operations on Perl or Python scripts in the Libraries page are limited to user accounts with the Scripts:Level 3 privilege. All other users are limited to read-only operations. Libraries also do not have an associated run level.You store Perl or Python subroutines in NetMRI's dedicated Libraries page. LIbraries provides standard Copy, Export, Edit and Delete options.
To import a new Perl or Python library file, do the following:
...
To delete an existing script: In the Actions column, click the icon and choose Delete from the menu.
...
.
...
Sample Juniper router.conf File
The example below is a Juniper autoconfiguration file for a 48-port EX-class Ethernet switch. This example is edited for brevity. Juniper autoconfig files require the definition of all interfaces of the device, unlike Cisco. Any undeclared interfaces will otherwise be non-functional in the system.
...