Oracle® Enterprise Manager System Monitoring Plug-in Installation Guide for Juniper Networks NetScreen Firewall 10g Release 2 (10.2) Part Number B28041-01 |
|
|
View PDF |
System Monitoring Plug-in Installation Guide for Juniper Networks NetScreen Firewall
10g Release 2 (10.2)
B28041-01
January 2006
This document provides a brief description about the Oracle System Monitoring Plug-in for Juniper Networks NetScreen Firewall, details on the versions the plug-in supports, prerequisites for installing the plug-in, and step-by-step instructions on how to download, install, verify, and validate the plug-in.
The System Monitoring Plug-in for Juniper Networks NetScreen Firewall extends Oracle Enterprise Manager Grid Control to add support for managing NetScreen Firewalls. By deploying the plug-in in your Grid Control environment, you gain the following management features:
Monitor Juniper Networks NetScreen Firewall devices.
Gather configuration data and track configuration changes for Juniper Networks NetScreen Firewall instances.
Raise alerts and violations based on thresholds set on monitoring and configuration data.
Provide rich out-of-box reports for the user interface based on the gathered data.
Support monitoring by a remote Agent. For remote monitoring, the Agent does not need to be on the same computer as NetScreen Firewall.
This plug-in supports the following versions of products:
Enterprise Manager Grid Control 10g Release 2 or higher Management Service and Agent
Juniper Networks NetScreen Firewalls that have ScreenOS version 5.0.0 or higher, and that are backward-compatible with ScreenOS version 5.0.0. The following versions of NetScreen Firewall are supported:
NetScreen-5 Series
NetScreen-25/50
NetScreen-204/208
NetScreen-500
NetScreen-5200/5400
ISG Series
The following prerequisites must be installed before you can deploy the plug-in:
Oracle Enterprise Manager Grid Control 10g Release 2 or higher system and Agent
NetScreen Firewall instance
The Agent's IP address must be added to any configured SNMP community on the NetScreen Firewall. See "Adding the Agent's IP Address" for procedures.
For Linux, the firewall SNMP daemon must be running on the NetScreen Firewall device
For Windows, the standard Windows SNMP agent must be installed, and the SNMP Service must be running
After you ensure that the prerequisites are met, follow these steps to deploy the plug-in:
Download the Juniper Networks NetScreen Firewall Plug-in archive to your desktop or computer on which the browser is launched. You can download the archive from the Oracle Technology Network (OTN).
Log in to Enterprise Manager Grid Control as a Super Administrator.
Click the Setup link in the upper right corner of the Grid Control Home page, then click the Management Plug-ins link on the left side of the Setup page.
Click Import.
Click Browse and select the plug-in archive.
Click List Archive.
Select the plug-in and click OK.
Verify that you have set preferred credentials on all Agents where you want to deploy the plug-in.
In the Management Plug-ins page, click the icon in the Deploy column for the NetScreen Firewall plug-in. The Deploy Management Plug-in wizard appears.
Click Add Agents, then select one or more Agents to which you want to deploy the plug-in. The wizard reappears and displays the Agent you selected.
Click Next, then click Finish.
If you see an error message stating that the preferred credential is not set up, go to the Preferences page and add the preferred credentials for the Agent target type and host target type on which the Agent resides.
After successfully deploying the plug-in, follow these steps to add the plug-in target to Grid Control for central monitoring and management:
From the Agent Home page where the Juniper Networks NetScreen Firewall Plug-in was deployed, select the NetScreen Firewall target type from the Add drop-down list, then click Go. The Add Juniper NetScreen Firewall page appears.
Provide the following information for the properties:
Name — A name for the plug-in, such as My Juniper 1
Firewall Hostname or IP Address — The name or IP address of the NetScreen Firewall to be monitored
Host SNMP Daemon Port — The port number on the NetScreen Firewall where the native OS SNMP domain is running. The default is 161.
You can determine the port number by using the command get snmp settings on the NetScreen Firewall command line interface, or by doing the following from the Web interface of the firewall:
Click on the Configuration link.
Click on the Report Settings link.
Click on the SNMP link.
The value specified on the listen port on the Web UI is the SNMP daemon port.
SNMP Community — The SNMP community name to which the Agent's IP address is added. The default is Public.
You can determine the community name by using the command get snmp settings on the NetScreen Firewall command line interface, or by doing the following from the Web interface of the firewall:
Click on the Configuration link.
Click on the Report Settings link.
Click on the SNMP link.
Select the community to which you have added the Enterprise Manager Agent's IP address.
SNMP Timeout — The timeout value at which the SNMP call should be terminated. The default value is 5 seconds.
Telnet Enabled (y/n) — If telnet is enabled on the Netscreen Firewall device, specify the default of y. Otherwise, leave this field blank.
Click Test Connection to make sure the parameters you entered are correct.
Reenter the encrypted parameters from step 2 if the connection test was successful, then click OK.
Note: After you deploy and set up the plug-in to monitor one or more targets in the environment, you can customize the plug-in monitoring settings to alter the collection intervals and threshold settings of the metrics to meet the particular needs of your environment. If you decide to disable one or more metric collections, this could impact the reports that the metric is a part of. |
After waiting a few minutes for the plug-in to start collecting data, use the following steps to verify and validate that Enterprise Manager is properly monitoring the plug-in target:
Click the Juniper NetScreen Firewall target link from the Agent home page Monitored Targets table. The Juniper NetScreen Firewall home page appears.
Verify that no metric collection errors are reported in the Metrics table.
Ensure that reports can be seen and no errors are reported by clicking the Reports subtab.
Ensure that configuration data can be seen by clicking the View Configuration link in the Configuration section. If configuration data does not immediately appear, click Refresh in the View Configuration page.
To add the Agent's IP address to an existing SNMP community on the Juniper Networks NetScreen Firewall, do the following:
Go to the Web interface of the target NetScreen Firewall.
Click the Configuration link.
Click the Report Settings link.
Click the SNMP link.
Click Edit for the community to which you want to add the Agent.
Enter the following information for the properties, then click Go:
Permissions — Select from Write, Trap, and Including Traffic Alarms.
Write — Select to assign read-write privileges for MIB II data to the SNMP community. Otherwise, clear to assign read-only privileges.
Trap — Select to send notifications or 'traps' to the community. The NetScreen device sends Cold Start/Link Up/Link Down traps to all hosts in communities that you set to receive traps.
Including Traffic Alarms — Select to send traffic alarms to the SNMP community.
Version — Select V1.
Host IP Address/Netmask — Enter the IP addresses and netmask of the Agent.
Source Interface — Indicate the interface from which SNMP messages originate.
To alternatively add a new SNMP community, do the following:
Go to the Web interface of the target NetScreen Firewall.
Click the Configuration link.
Click the Report Settings link.
Click the SNMP link.
Click the New Community link.
The New Community link is not found if three SNMP communities are already configured on the firewall. The NetScreen device administrator can create up to three SNMP communities with up to eight hosts in each community. In this case, edit any of the existing SNMP communities as explained at the beginning of this section.
Enter the following information for the properties, then click Go:
Community Name — Enter the name of the group, or 'community,' of administrators permitted to view the data gathered by the SNMP agent and receive SNMP notification of system events.
Permissions —
Write — Select to assign read-write privileges for MIB II data to the SNMP community. Otherwise, clear to assign read-only privileges.
Trap — Select to send notifications or 'traps' to the community. The NetScreen device sends Cold Start/Link Up/Link Down traps to all hosts in communities that you set to receive traps.
Including Traffic Alarms — Select to send traffic alarms to the SNMP community.
Version — Select V1.
Hosts IP Address/Netmask — Enter the IP addresses and netmasks of the hosts (workstations or subnets) that you want to define as members of the community.
Trap Version — Select V1.
Source Interface — Indicate the interface from which SNMP messages originate.
Follow these steps to undeploy the plug-in from an Agent:
Log in to Enterprise Manager Grid Control as a Super Administrator.
Select the Targets tab, then the All Targets subtab. The All Targets page appears.
Select the Juniper NetScreen Firewall Plug-in target and click Remove. You must do this step for all targets of the plug-in.
Make sure that the preferred credentials are set on the Agents where the plug-in is deployed.
Click the Setup link in the upper right corner of the All Targets page, then click the Management Plug-ins link on the left side of the Setup page. The Management Plug-ins page appears.
Click the icon in the Undeploy column for the NetScreen Firewall plug-in. The Undeploy Management Plug-in page appears.
Check all the Agents that are currently deployed with the NetScreen Firewall Plug-in and click OK.
You must undeploy the plug-in from every Agent in the system to completely remove it from the enterprise.
Select the Juniper NetScreen Firewall plug-in on the Management Plug-ins page and click Delete.
Our goal is to make Oracle products, services, and supporting documentation accessible, with good usability, to the disabled community. To that end, our documentation includes features that make information available to users of assistive technology. This documentation is available in HTML format, and contains markup to facilitate access by the disabled community. Accessibility standards will continue to evolve over time, and Oracle is actively engaged with other market-leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers. For more information, visit the Oracle Accessibility Program Web site at http://www.oracle.com/accessibility/
.
Accessibility of Code Examples in Documentation
Screen readers may not always correctly read the code examples in this document. The conventions for writing code require that closing braces should appear on an otherwise empty line; however, some screen readers may not always read a line of text that consists solely of a bracket or brace.
Accessibility of Links to External Web Sites in Documentation
This documentation may contain links to Web sites of other companies or organizations that Oracle does not own or control. Oracle neither evaluates nor makes any representations regarding the accessibility of these Web sites.
TTY Access to Oracle Support Services
Oracle provides dedicated Text Telephone (TTY) access to Oracle Support Services within the United States of America 24 hours a day, seven days a week. For TTY support, call 800.446.2398.
System Monitoring Plug-in Installation Guide for Juniper Networks NetScreen Firewall, Release 2 (10.2)
B28041-01
Copyright © 2006, Oracle. All rights reserved.
The Programs (which include both the software and documentation) contain proprietary information; they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly, or decompilation of the Programs, except to the extent required to obtain interoperability with other independently created software or as specified by law, is prohibited.
The information contained in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. This document is not warranted to be error-free. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose.
If the Programs are delivered to the United States Government or anyone licensing or using the Programs on behalf of the United States Government, the following notice is applicable:
U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the Programs, including documentation and technical data, shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement, and, to the extent applicable, the additional rights set forth in FAR 52.227-19, Commercial Computer Software—Restricted Rights (June 1987). Oracle Corporation, 500 Oracle Parkway, Redwood City, CA 94065
The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. It shall be the licensee's responsibility to take all appropriate fail-safe, backup, redundancy and other measures to ensure the safe use of such applications if the Programs are used for such purposes, and we disclaim liability for any damages caused by such use of the Programs.
Oracle, JD Edwards, PeopleSoft, and Retek are registered trademarks of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.
The Programs may provide links to Web sites and access to content, products, and services from third parties. Oracle is not responsible for the availability of, or any content provided on, third-party Web sites. You bear all risks associated with the use of such content. If you choose to purchase any products or services from a third party, the relationship is directly between you and the third party. Oracle is not responsible for: (a) the quality of third-party products or services; or (b) fulfilling any of the terms of the agreement with the third party, including delivery of products or services and warranty obligations related to purchased products or services. Oracle is not responsible for any loss or damage of any sort that you may incur from dealing with any third party.