this page: Network Director Administration
Junos® Space
Network Director Administration Guide
Release
1.6
Published: 2014-06-30
Copyright © 2014, Juniper Networks, Inc.
Juniper Networks, Inc.
1194 North Mathilda Avenue
Sunnyvale, California 94089
USA
408-745-2000
www.juniper.net
Copyright © 2014, Juniper Networks, Inc. All rights reserved.
Juniper Networks, Junos, Steel-Belted Radius, NetScreen, and ScreenOS are registered trademarks of Juniper Networks, Inc. in the United
States and other countries. The Juniper Networks Logo, the Junos logo, and JunosE are trademarks of Juniper Networks, Inc. All other
trademarks, service marks, registered trademarks, or registered service marks are the property of their respective owners.
Juniper Networks assumes no responsibility for any inaccuracies in this document. Juniper Networks reserves the right to change, modify,
transfer, or otherwise revise this publication without notice.
®
Junos Space Network Director Administration Guide
1.6
Copyright © 2014, Juniper Networks, Inc.
All rights reserved.
The information in this document is current as of the date on the title page.
YEAR 2000 NOTICE
Juniper Networks hardware and software products are Year 2000 compliant. Junos OS has no known time-related limitations through the
year 2038. However, the NTP application is known to have some difficulty in the year 2036.
END USER LICENSE AGREEMENT
The Juniper Networks product that is the subject of this technical documentation consists of (or is intended for use with) Juniper Networks
software. Use of such software is subject to the terms and conditions of the End User License Agreement (“EULA”) posted at
http://www.juniper.net/support/eula.html. By downloading, installing or using such software, you agree to the terms and conditions of
that EULA.
ii
Copyright © 2014, Juniper Networks, Inc.
Table of Contents
About the Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Documentation and Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Documentation Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Documentation Feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
Requesting Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii
Self-Help Online Tools and Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . xii
Opening a Case with JTAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii
Part 1
Overview
Chapter 1
Administration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Understanding Network Director User Administration . . . . . . . . . . . . . . . . . . . . . . . 3
Understanding the System Tasks Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Audit Logs Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Part 2
Configuration
Chapter 2
Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Setting Up User and System Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Accessing the Preferences page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Choosing Server Time or Local Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Specifying Search Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Retaining Network Director Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Linking to RingMaster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Changing Monitor Mode Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Disabling Data Collection for Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Changing the Polling Interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Specifying Database History Retention . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Specifying Analytics Engine Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Changing Alarm Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Configuring Global Alarm Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Retaining Alarm History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Specifying Event History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Enabling Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Changing the Severity of Individual Alarms . . . . . . . . . . . . . . . . . . . . . . . 26
Configuring Individual Alarm Notifications . . . . . . . . . . . . . . . . . . . . . . . . 26
Configuring Threshold Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Copyright © 2014, Juniper Networks, Inc.
iii
Network Director Administration Guide
Part 3
Administration
Chapter 3
Audit Logs and Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Viewing Audit Logs From Network Director . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Managing Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Part 4
Troubleshooting
Chapter 4
Collecting Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Collecting Logs for Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
iv
Copyright © 2014, Juniper Networks, Inc.
List of Figures
Part 2
Configuration
Chapter 2
Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Figure 1: Accessing the Preferences Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Copyright © 2014, Juniper Networks, Inc.
v
Network Director Administration Guide
vi
Copyright © 2014, Juniper Networks, Inc.
List of Tables
About the Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Table 1: Notice Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x
Table 2: Text and Syntax Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x
Part 1
Overview
Chapter 1
Administration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Table 3: System Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Part 2
Configuration
Chapter 2
Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Table 4: Monitor Mapping for Data Collectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Table 5: Default Polling Intervals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Table 6: Alarm Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Part 3
Administration
Chapter 3
Audit Logs and Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Table 7: Audit Logs Page Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Table 8: Job Management Page Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Part 4
Troubleshooting
Chapter 4
Collecting Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Table 9: Log Files in the troubleshooting.zip File . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Copyright © 2014, Juniper Networks, Inc.
vii
Network Director Administration Guide
viii
Copyright © 2014, Juniper Networks, Inc.
About the Documentation
•
Documentation and Release Notes on page ix
•
Documentation Conventions on page ix
•
Documentation Feedback on page xi
•
Requesting Technical Support on page xii
Documentation and Release Notes
®
To obtain the most current version of all Juniper Networks technical documentation,
see the product documentation page on the Juniper Networks website at
http://www.juniper.net/techpubs/.
If the information in the latest release notes differs from the information in the
documentation, follow the product Release Notes.
Juniper Networks Books publishes books by Juniper Networks engineers and subject
matter experts. These books go beyond the technical documentation to explore the
nuances of network architecture, deployment, and administration. The current list can
be viewed at http://www.juniper.net/books.
Documentation Conventions
Table 1 on page x defines notice icons used in this guide.
Copyright © 2014, Juniper Networks, Inc.
ix
Network Director Administration Guide
Table 1: Notice Icons
Icon
Meaning
Description
Informational note
Indicates important features or instructions.
Caution
Indicates a situation that might result in loss of data or hardware damage.
Warning
Alerts you to the risk of personal injury or death.
Laser warning
Alerts you to the risk of personal injury from a laser.
Tip
Indicates helpful information.
Best practice
Alerts you to a recommended use or implementation.
Table 2 on page x defines the text and syntax conventions used in this guide.
Table 2: Text and Syntax Conventions
Convention
Description
Examples
Bold text like this
Represents text that you type.
To enter configuration mode, type the
configure command:
user@host> configure
Fixed-width text like this
Italic text like this
Italic text like this
x
Represents output that appears on the
terminal screen.
user@host> show chassis alarms
•
Introduces or emphasizes important
new terms.
•
•
Identifies guide names.
A policy term is a named structure
that defines match conditions and
actions.
•
Identifies RFC and Internet draft titles.
•
Junos OS CLI User Guide
•
RFC 1997, BGP Communities Attribute
Represents variables (options for which
you substitute a value) in commands or
configuration statements.
No alarms currently active
Configure the machine’s domain name:
[edit]
root@# set system domain-name
domain-name
Copyright © 2014, Juniper Networks, Inc.
About the Documentation
Table 2: Text and Syntax Conventions (continued)
Convention
Description
Examples
Text like this
Represents names of configuration
statements, commands, files, and
directories; configuration hierarchy levels;
or labels on routing platform
components.
•
To configure a stub area, include the
stub statement at the [edit protocols
ospf area area-id] hierarchy level.
•
The console port is labeled CONSOLE.
< > (angle brackets)
Encloses optional keywords or variables.
stub <default-metric metric>;
| (pipe symbol)
Indicates a choice between the mutually
exclusive keywords or variables on either
side of the symbol. The set of choices is
often enclosed in parentheses for clarity.
broadcast | multicast
# (pound sign)
Indicates a comment specified on the
same line as the configuration statement
to which it applies.
rsvp { # Required for dynamic MPLS only
[ ] (square brackets)
Encloses a variable for which you can
substitute one or more values.
community name members [
community-ids ]
Indention and braces ( { } )
Identifies a level in the configuration
hierarchy.
; (semicolon)
Identifies a leaf statement at a
configuration hierarchy level.
(string1 | string2 | string3)
[edit]
routing-options {
static {
route default {
nexthop address;
retain;
}
}
}
GUI Conventions
Bold text like this
Represents graphical user interface (GUI)
items you click or select.
> (bold right angle bracket)
Separates levels in a hierarchy of menu
selections.
•
In the Logical Interfaces box, select
All Interfaces.
•
To cancel the configuration, click
Cancel.
In the configuration editor hierarchy,
select Protocols>Ospf.
Documentation Feedback
We encourage you to provide feedback, comments, and suggestions so that we can
improve the documentation. You can provide feedback by using either of the following
methods:
•
Online feedback rating system—On any page at the Juniper Networks Technical
Documentation site at http://www.juniper.net/techpubs/index.html, simply click the
stars to rate the content, and use the pop-up form to provide us with information about
your experience. Alternately, you can use the online feedback form at
https://www.juniper.net/cgi-bin/docbugreport/.
Copyright © 2014, Juniper Networks, Inc.
xi
Network Director Administration Guide
•
E-mail—Send your comments to techpubs-comments@juniper.net. Include the document
or topic name, URL or page number, and software version (if applicable).
Requesting Technical Support
Technical product support is available through the Juniper Networks Technical Assistance
Center (JTAC). If you are a customer with an active J-Care or JNASC support contract,
or are covered under warranty, and need post-sales technical support, you can access
our tools and resources online or open a case with JTAC.
•
JTAC policies—For a complete understanding of our JTAC procedures and policies,
review the JTAC User Guide located at
http://www.juniper.net/us/en/local/pdf/resource-guides/7100059-en.pdf.
•
Product warranties—For product warranty information, visit
http://www.juniper.net/support/warranty/.
•
JTAC hours of operation—The JTAC centers have resources available 24 hours a day,
7 days a week, 365 days a year.
Self-Help Online Tools and Resources
For quick and easy problem resolution, Juniper Networks has designed an online
self-service portal called the Customer Support Center (CSC) that provides you with the
following features:
•
Find CSC offerings: http://www.juniper.net/customers/support/
•
Search for known bugs: http://www2.juniper.net/kb/
•
Find product documentation: http://www.juniper.net/techpubs/
•
Find solutions and answer questions using our Knowledge Base: http://kb.juniper.net/
•
Download the latest versions of software and review release notes:
http://www.juniper.net/customers/csc/software/
•
Search technical bulletins for relevant hardware and software notifications:
http://kb.juniper.net/InfoCenter/
•
Join and participate in the Juniper Networks Community Forum:
http://www.juniper.net/company/communities/
•
Open a case online in the CSC Case Management tool: http://www.juniper.net/cm/
To verify service entitlement by product serial number, use our Serial Number Entitlement
(SNE) Tool: https://tools.juniper.net/SerialNumberEntitlementSearch/
Opening a Case with JTAC
You can open a case with JTAC on the Web or by telephone.
xii
•
Use the Case Management tool in the CSC at http://www.juniper.net/cm/.
•
Call 1-888-314-JTAC (1-888-314-5822 toll-free in the USA, Canada, and Mexico).
Copyright © 2014, Juniper Networks, Inc.
About the Documentation
For international or direct-dial options in countries without toll-free numbers, see
http://www.juniper.net/support/requesting-support.html.
Copyright © 2014, Juniper Networks, Inc.
xiii
Network Director Administration Guide
xiv
Copyright © 2014, Juniper Networks, Inc.
PART 1
Overview
•
Administration Overview on page 3
Copyright © 2014, Juniper Networks, Inc.
1
Network Director Administration Guide
2
Copyright © 2014, Juniper Networks, Inc.
CHAPTER 1
Administration Overview
•
Understanding Network Director User Administration on page 3
•
Understanding the System Tasks Pane on page 4
•
Audit Logs Overview on page 4
Understanding Network Director User Administration
Network Director uses the user administration features of the Junos Space platform on
which it runs. Use Junos Space for tasks such as adding, deleting, and editing user accounts
and roles, and changing user passwords. Refer to the Junos Space documentation for
information about user administration.
When Network Director is installed, some additional user administration options are
available in Junos Space, which are specific to Network Director:
•
In addition to the Super Administrator role, the following predefined roles are available
for Network Director users:
Network Director - Admin—Has complete access to all the Network Director modes and
user and system preferences.
Network Director - Engineer—Has access to all modes except Fault and System modes.
Has access to only user preferences, not system preferences.
Network Director - Monitor—Has access to only Monitor and Report modes. Has access
to only user preferences, not system preferences.
•
You can create custom roles to grant users different access rights to the Network
Director modes. Network Director modes—Report, Deploy, Monitor, Fault, and Build
are available to assign to custom user roles in the list of application workspaces and
associated tasks.
NOTE: The tasks listed under the Network Director modes do not have any
effect. Access is controlled at the mode level, so if you grant a role access
to a mode, the role has access to all tasks in that mode, regardless of which
tasks you select.
Copyright © 2014, Juniper Networks, Inc.
3
Network Director Administration Guide
If you try to log in to Network Director using an account that does not have access rights
to any Network Director modes, you will be redirected to Junos Space instead.
Access to Network Director system preferences is controlled by user access rights. For
more information, see “Setting Up User and System Preferences” on page 9.
Related
Documentation
•
Understanding the Network Director User Interface
•
Setting Up User and System Preferences on page 9
Understanding the System Tasks Pane
The System Tasks pane provides tasks for viewing audit logs of Network Director user
activities, for managing jobs, and for collecting troubleshooting logs.
To access the System Tasks pane, click System in the Network Director banner. The tasks
are described in Table 3 on page 4.
Table 3: System Tasks
Related
Documentation
Task
Description
View Audit Logs
View a history of user activities on Network Director, including log in, log out,
and task initiation and completion.
Manage Jobs
View all jobs that are scheduled to run or have been run by Network Director.
You can cancel jobs that are in progress or scheduled to run in the future.
Collect Jobs for
Troubleshooting
Download a zip file containing logs and troubleshooting data from both
Network Director and Junos Space.
Import RingMaster
Data
Import data and configurations from RimgMaster to Network Director.
•
Viewing Audit Logs From Network Director on page 31
•
Managing Jobs on page 32
•
Collecting Logs for Troubleshooting on page 37
Audit Logs Overview
Audit logs provide a record of login history and user-initiated tasks that are performed
from the user interface. From the Audit Logs page, you can monitor user login–logout
activity over time, track device management tasks, view services that were provisioned
on devices, and so forth. Audit logging does not record non-user initiated activities, such
as device-driven activities, and is not designed for debugging purposes.
Administrators can sort and filter on audit logs to determine which users performed what
actions on what objects at what time. For example, an administrator can use audit log
filtering to track the user accounts that were added on a specific date, track configuration
4
Copyright © 2014, Juniper Networks, Inc.
Chapter 1: Administration Overview
changes across a particular type of device, view services that were provisioned on specific
devices, or monitor user login–logout activity over time.
Over time, Network Director will archive a large volume of log entries. Such log entries
might or might not be reviewed, but they must be retained for a period of time.
The audit logs can be saved to a local server (the server that functions as the active node
for Network Director) or a remote network host or media.
Related
Documentation
•
Viewing Audit Logs From Network Director on page 31
Copyright © 2014, Juniper Networks, Inc.
5
Network Director Administration Guide
6
Copyright © 2014, Juniper Networks, Inc.
PART 2
Configuration
•
Preferences on page 9
Copyright © 2014, Juniper Networks, Inc.
7
Network Director Administration Guide
8
Copyright © 2014, Juniper Networks, Inc.
CHAPTER 2
Preferences
•
Setting Up User and System Preferences on page 9
Setting Up User and System Preferences
Depending on your system authority, Preferences page can display either user settings
or a combination of user settings and system settings. One or more of these preference
tabs appear when you open the Preferences page:
•
User–All users can choose whether monitors and reports display local time or server
time.
•
Search–Administrators can configure options for search indexing.
•
Monitoring–Network Administrators can change the polling interval for data collection
for Monitor mode monitors. This page enables the internal processes used for data
collection to be enabled or disabled. You can also specify the IP address of the Analytics
Engine server, if installed, and the database record retention periods on this tab.
•
Fault–Network Administrators can enable or disable alarms. They can also set the
retention period for alarms and the number of events per alarm.
•
Report–Network Administrators can specify length of time Network Director reports
are retained.
•
General–Network Administrators can specify a RingMaster URL.
•
Topology–Network Administrators can specify a retention period for the deleted links
in Topology.
This topic describes:
•
Accessing the Preferences page on page 10
•
Choosing Server Time or Local Time on page 10
•
Specifying Search Preferences on page 10
•
Retaining Network Director Reports on page 10
•
Linking to RingMaster on page 10
•
Changing Monitor Mode Settings on page 11
•
Changing Alarm Settings on page 14
Copyright © 2014, Juniper Networks, Inc.
9
Network Director Administration Guide
Accessing the Preferences page
To open the Preferences page, click
in the Network Director banner and select
Preferences as shown in Figure 1 on page 10.
Figure 1: Accessing the Preferences Page
The Preferences page opens with User Preferences as the default tab.
Choosing Server Time or Local Time
All users can specify whether Network Director displays local time or the server’s time in
monitors and reports on the User Preferences tab. The default setting is to display local
time. To change the setting to display the server’s time:
1.
In the Preferences page, select Use Server Time from the list.
2. Click OK to save your changes or click Cancel to close Preferences.
Specifying Search Preferences
Network Director indexes the device inventory data periodically to enable users to perform
efficient searches. You can specify a time interval after which Network Director initiates
the next indexing on the Search tab. You can also specify to stop indexing while devices
are imported into Network Director. If you are running short of system memory, selecting
this option can help save some memory and speed up the discovery and import of new
devices. By default this option is selected and the search index update interval is set to
900 seconds.
Retaining Network Director Reports
By default, Network Director keeps reports for 30 days. However, Network Administrators
can change the retention period from 0 to 365 days. To change the setting, move the
slider right or left on the Report tab of Preferences to the new setting. Click OK to save
the setting.
Linking to RingMaster
Sites with RingMaster licenses can launch the RingMaster application from within Network
Director by supplying the RingMaster URL. After typing the URL on the General Settings
tab of Preferences, you can click Launch RingMaster in Build mode to load RingMaster
into the main page. To enable launching RingMaster from within Network Director, simply
type in the URL and click OK to save the setting.
10
Copyright © 2014, Juniper Networks, Inc.
Chapter 2: Preferences
Changing Monitor Mode Settings
The Monitoring tab of Preferences has three tabs under it. These are:
•
Monitor Settings—Enables you to change the default polling interval for data collection
for Monitor mode monitors. You can also disable or re-enable the internal processes
used for data collection on this sub-tab.
•
Client Session History—Enables you to set the retention period for history records and
the frequency that these records are checked for deletion.
•
Analytics Engine—Enables you to specify the IP address of the system where the
Analytics Engine is installed.
This section describes:
•
Disabling Data Collection for Monitors on page 11
•
Changing the Polling Interval on page 13
•
Specifying Database History Retention on page 13
•
Specifying Analytics Engine Settings on page 14
Disabling Data Collection for Monitors
Network Director internally gathers data for monitors by using a set of data collector
processes. You can disable these data collectors if they do not pertain to your installation.
For example, if you do not use Virtual Chassis, you can disable the data collection
processes used for Virtual Chassis.
The data collector processes are divided into the following categories:
•
Client
•
Equipment
•
RF
•
Traffic
One data collector can be used by multiple monitors. Likewise, some monitors can be
supported by multiple data collectors. These data collectors are enabled by default. To
ensure proper data collection, if Equipment data collectors are enabled, ensure the Traffic
collector is also enabled.
To disable or re-enable a data collector:
1.
Determine which monitors are used by the data collectors. Use Table 4 on page 11
to determine the relationship between the data collectors and the monitors.
Table 4: Monitor Mapping for Data Collectors
Monitor
Data Collector
Category
802.11 Packet Error
RFMonitorRadioStatsCollector
RF
Copyright © 2014, Juniper Networks, Inc.
11
Network Director Administration Guide
Table 4: Monitor Mapping for Data Collectors (continued)
Monitor
Data Collector
Category
AP Interference Source
RFMonitorIntSourcesCollector
RF
AP Status
EquipmentMonitorAPCollector
Equipment
Current Sessions
Client Monitor Collector and SessionCountCollector
Client
Error Trend
PortTrafficMonitorCollector
Traffic
Logical Interfaces
EquipmentMonitorLogicalInterfaceStatusCollector
Equipment
Find End Point
EquipmentMonitorEndPointCollector
Equipment
Percentage of Packets Retransmitted
RFMonitorRadioStatsCollector
RF
Port Status (physical)
EquipmentMonitorControllerCollector
Equipment
Radio Status
EquipmentMonitorAPCollector
Equipment
RF Neighborhood
RFMonitorRadioNeighborCollector
RF
RF Throughput or Packet
Retransmitted
RFMonitorRadioStatsCollector
RF
Resource Utilization
EquipmentMonitorControllerCollector
Equipment
Session Trend
ClientMonitorCollector and SessionCountCollector
Client
Switch Status
EquipmentMonitorControllerCollector
Equipment
Traffic Trend
PortTrafficMonitorCollector
Traffic
Top Sessions by MAC Address
ClientMonitorCollector
Client
Top Users
ClientMonitorCollector
Client
Unicast vs Broadcast/Multicast
PortTrafficMonitorCollector
Traffic
Unicast vs Broadcast/Multicast Trend
PortTrafficMonitorCollector
Traffic
Virtual Chassis Topology
EquipmentMonitorVCStatsCollector and
EquipmentMonitorVCCollector
Equipment
Virtual Chassis Protocol
EquipmentMonitorVCStatsCollector and
EquipmentMonitorVCCollector
Equipment
Virtual Chassis Statistics
EquipmentMonitorVCStatsCollector and
EquipmentMonitorVCCollector
Equipment
12
Copyright © 2014, Juniper Networks, Inc.
Chapter 2: Preferences
2. Clear the check box to disable the collector or select to enable the collector.
3. Click Save and Close to save the configuration and to close the window.
Changing the Polling Interval
The frequency at which data is collected is determined by the polling interval.
Table 5 on page 13 shows the default polling intervals vary by data collector.
Table 5: Default Polling Intervals
Collector
Polling Interval
ClientMonitorCollector
10 minutes
SessionCountCollector
10 minutes
EquipmentMonitorVCCollector
30 minutes
EquipmentMonitorVCStatsCollector
30 minutes
EquipmentMonitorLogicalInterfaceStatusCollector
30 minutes
EquipmentMonitorControllerCollector
10 minutes
EquipmentMonitorAPCollector
10 minutes
EquipmentMonitorEndPointCollector
1440 minutes
RFMonitorIntSourcesCollector
15 minutes
RFMonitorRadioNeighborCollector
15 minutes
RFMonitorStatsCollector
10 minutes
PortTrafficMonitorCollector
10 minutes
To change the polling interval:
1.
Select the polling interval for a data collector in the Monitor Settings table.
2. Type the new interval level in whole minutes. For example, do not specify 1.5 minutes.
Recommended intervals are 5, 10, or 20 minutes.
3. Click OK and Yes to verify the change to the configuration.
Specifying Database History Retention
To keep the database manageable, the system periodically checks the age of the records
and retires those that have past an expiration date. By default, Network Director ages
database records off at 90 days and runs a database cleanup every 6 hours.
Copyright © 2014, Juniper Networks, Inc.
13
Network Director Administration Guide
Use the Client Session History sub-tab to change the default values:
1.
Select from the lists new values.
•
Age of history records (in days) from 1 to 365 days.
•
Cleanup job frequency (in hours) from 1 through 24 hours.
2. Click OK to save the changes.
Specifying Analytics Engine Settings
The Network Director Analytics Engine enables Network Director to collect and analyze
high-frequency statistics data from devices. The Analytics Engine can run in integrated
mode (on a Junos Space server) or in external mode (on a separate, dedicated Analytics
Engine server running CentOS). For more information, see the Network Director Quick
Start Guide.
Use the Analytics Engine Settings sub-tab to specify the IP address of the Analytics
Engine server:
1.
Enter the IP address of the Analytics Engine server.
•
If you are running the Analytics Engine in integrated mode, enter the IP address of
the Junos Space server on which you want to run the Analytics Engine.
•
If you are running the Analytics Engine in external mode, enter the IP address of the
Analytics Engine server.
2. Click OK to save the changes.
Changing Alarm Settings
Use the Fault tab to enable individual alarms, set the retention period for alarms, configure
alarm notifications, configure threshold alarms, and to specify the number of events to
keep for each alarm. The Fault tab has multiple sections, which you can expand and
collapse by clicking the arrow next to the section title:
•
Global Settings, for configuring Faults settings such as global alarm notifications and
alarm data retention.
•
Individual Alarms and Threshold Settings, for configuring settings for individual alarms
and threshold alarms.
This section describes the following tasks that you can perform by using the Fault tab:
14
•
Configuring Global Alarm Notifications on page 15
•
Retaining Alarm History on page 15
•
Specifying Event History on page 15
•
Enabling Alarms on page 15
•
Changing the Severity of Individual Alarms on page 26
•
Configuring Individual Alarm Notifications on page 26
•
Configuring Threshold Alarms on page 26
Copyright © 2014, Juniper Networks, Inc.
Chapter 2: Preferences
Configuring Global Alarm Notifications
You can configure global e-mail notifications to be sent when any alarm with notifications
enabled is generated. To configure global e-mail notifications, enter the e-mail addresses
to receive global alarm notifications in the Alarm Notifications Destinations field in the
Global Settings section. Separate addresses with a comma (,). For information about
enabling notification for an alarm, see “Configuring Individual Alarm Notifications” on
page 26.
Retaining Alarm History
Use the No. of days to keep Alarm field in the Global Settings section to specify the number
of days to keep alarm history. The default retention time is 120 days; but you can specify
a period of 7 through 1000 days. Specifying a longer retention time consumes more
database resources. To change the alarm retention duration, type a new value and click
OK and Yes to confirm the change.
Specifying Event History
Use the Events/Alarm field in the Global Settings section to specify the number of event
entries that are kept in the alarm history. The default setting for events is 20. To change
the setting, type a new value and click OK and Yes to confirm the change.
Enabling Alarms
Ensure all devices are configured to send traps to Network Director. This task is performed
for the devices in Deploy mode through Set SNMP Trap Configuration.
Use the Individual Alarms and Threshold Settings section to disable and re-enable
individual alarms or all alarms. Alarms appear on both tabs in the section: Alarm Settings
and Threshold Settings. Fault alarms are preconfigured and initially enabled. To enable
or disable alarms:
1.
(Optional) Sort the alarms. By default, the list of alarms is sorted alphabetically within
each category. You can also sort by description or alarm severity within a category by
clicking a column heading.
2. Review the alarms and either select the check box in the heading to select all of the
alarms or select the check box for the individual alarms you want to enable. For a full
description of each of the alarms, see Table 6 on page 15.
3. Click OK and Yes to confirm the alarm change.
Table 6: Alarm Descriptions
Alarm Name
Description
Device Type
AP and Radio (AP/Radio)
Copyright © 2014, Juniper Networks, Inc.
15
Network Director Administration Guide
Table 6: Alarm Descriptions (continued)
Alarm Name
Description
Device Type
AP License Limit Exceeded
Generated when the number of wireless LAN
access points (WLAs) exceed the number of
licenses configured on a wireless switch. The trap
occurs when a wireless switch receives a packet
from an inactive access point. The switch is unable
to attach the access point without exceeding the
maximum (licensed) number of active access
points.
Wireless LAN
controller
AP Manager Changed Alarm
Generated when the access point’s secondary link
becomes the primary link.
Wireless LAN
controller
AP Status Alarm
Generated when an access point changes state.
Wireless LAN
controller
AP Tunnel Limit Exceeded
Generated when the number of tunnels on an
access point exceeds the maximum number
supported. This alarm is generated by the access
point’s Primary Access Manager (PAM) when the
access point rejects a tunnel creation request
because it has already created the maximum
number of tunnels it can support.
Wireless LAN
controller
M2U Conversion
Generated when multicast to unicast conversion
is enabled on the access point, but cannot be
performed.
Wireless LAN
controllers
Radio Channel Changed
Generated when auto-tune changes a radio's
channel.
Wireless LAN
controller
Radio power changed
Generated when auto-tune changes a radio's
power level.
Wireless LAN
controller
Radio Status Alarm
Generated when a radio changes state. It also
contains aggregate information about the access
point in operational state, its security level and
service availability.
Wireless LAN
controller
WLC Tunnel Limit Exceeded
Generated when the wireless switch rejects a
tunnel creation request because it has reached
the maximum number of tunnels supported. When
the trap event trpzWsTunnelLimitType equals the
platform-tunnel-limit, the wireless switch has
reached the maximum tunnel capacity. The actual
tunnel limit varies by platform. When the trap
trpzWsTunnelLimitType equals
ap-ws-tunnel-limit, the wireless switch has
reached the access point-to-switch tunnel’s limit.
The value of that limit depends on the current
situation of the wireless switch (mobility domain,
network domain, network and resiliency status).
Wireless LAN
controller
BFD
16
Copyright © 2014, Juniper Networks, Inc.
Chapter 2: Preferences
Table 6: Alarm Descriptions (continued)
Alarm Name
Description
Device Type
BfdSessionDetectionTimeAlarm
Generated when the threshold value for detection
time is set and the BFD session detection-time
adapts to a value greater than the threshold.
EX Series Switch
BfdSessionTxAlarm
Generated when the threshold value for transmit
interval (in microseconds) is exceeded.
EX Series Switch
BgpM2BackwardTransitionAlarm
Generated when the BGP FSM moves from a
higher-numbered state to a lower-numbered state.
EX Series Switch
BgpM2EstablishedAlarm
Generated when the BGP Finite State Machine
(FSM) enters the ESTABLISHED state.
EX Series Switch
FanFailureAlarm
Generated when the specified cooling fan or
impeller has failed (is not spinning).
EX Series Switch
FEBSwitchoverAlarm
Generated when the Forwarding Engine Board
(FEB) has switched over.
EX Series Switch
FRUCheckAlarm
Generated when the device has detected that a
field-replaceable unit (FRU), has some operational
errors and has gone into check state.
EX Series Switch
FRUFailedAlarm
Generated when a FRU has failed.
EX Series Switch
FRUInsertionAlarm
Generated when the system detects that the
specified FRU is inserted into the chassis.
EX Series Switch
FRUOfflineAlarm
Generated when the specified FRU goes offline.
EX Series Switch
FRUOnlineAlarm
Generated when the specified FRU goes online.
EX Series Switch
FRUPowerOffAlarm
Generated when the specified FRU is powered off.
EX Series Switch
FRUPowerOnAlarm
Generated when the specified FRU is powered on.
EX Series Switch
FRURemovalAlarm
Generated when the system detects that the
specified FRU was removed from the chassis.
EX Series Switch
HardDiskFailedAlarm
Generated when the hard disk for the specified
routing engine has failed.
EX Series Switch
HardDiskMissingAlarm
Generated when the hard disk in the specified
routing engine is missing from the boot device list.
EX Series Switch
BGP
Chassis
Copyright © 2014, Juniper Networks, Inc.
17
Network Director Administration Guide
Table 6: Alarm Descriptions (continued)
Alarm Name
Description
Device Type
PowerSupplyFailureAlarm
Generated when the specified power supply has
failed (bad DC output).
EX Series Switch
RedundancySwitchOverAlarm
Generated when a graceful Routing Engine
switchover (GRES) occurs on a switch with dual
Routing Engines or on a Virtual Chassis.
EX Series Switch
TemperatureAlarm
Generated when the device has over heated.
EX Series Switch
Client Association Failure
Generated when a client is unable to associate
with an access point.
Wireless LAN
controller
Client Authentication Failure
Generated when a client is unable to authenticate.
Wireless LAN
controller
Client Authorization Failure
Generated when a client fails authorization.
Wireless LAN
controller
Client Authorization Succeeded
Generated when a client authorizes.
Wireless LAN
controller
Client Cleared
Generated when a client session is cleared.
Wireless LAN
controller
Client Connectivity
Generated when a client session connects.
Wireless LAN
controller
Client DeAssociated
Generated when a client de-association occurs.
Wireless LAN
controller
Client DeAuthenticated
Generated when a client de-authenticates.
Wireless LAN
controller
Client Disconnected
Generated when a client session disconnects
administratively.
Wireless LAN
controller
Client dot1x Failure
Generated when a client fails 802.1X.
Wireless LAN
controller
Client Dynamic Authorization Changed
Generated when the authorization attributes for
a user are dynamically changed by a authorized
dynamic authorization client.
Wireless LAN
controller
Client IP Address Changed
Generated when a client’s IP address changes,
normally when the client first connects to the
network.
Wireless LAN
controller
Client and User Session (ClientAndUserSession)
18
Copyright © 2014, Juniper Networks, Inc.
Chapter 2: Preferences
Table 6: Alarm Descriptions (continued)
Alarm Name
Description
Device Type
Client Roamed
Generated when a client roams from one location
to another.
Wireless LAN
controller
Dynamic Authorization Client Alarm
Generated when the authorization attributes for
a user are dynamically changed by an authorized
dynamic authorization client.
Wireless LAN
controller
Cluster Sync Failure
Generated when the cluster configuration failed
to apply.
Wireless LAN
controller
Mobility Domain Failback
Generated when the mobility domain fails back
to the primary seed.
Wireless LAN
controller
Mobility Domain Failover
Generated when the mobility domain fails back
to the secondary seed.
Wireless LAN
controller
Mobility Domain Join
Generated when a member joins the mobility
domain.
Wireless LAN
controller
Mobility Domain Resiliency Status
Generated when a mobility domain seed changes
resilient capacity.
Wireless LAN
controller
Mobility Domain Timeout
Generated when a mobility domain member times
out.
Wireless LAN
controller
CmCfgChangeAlarm
Generated when the jnxCMCfgChgEventTable
records a configuration management event.
EX Series Switch
and wireless LAN
controller
CMRescueChangeAlarm
Generated when a change is made to the rescue
configuration.
EX Series Switch
and wireless LAN
controller
Generated when the device status changes (up
to down or down to up).
EX Series Switch
and wireless LAN
controller
CoSAlmostOutOfDedicatedQueuesAlarm
Generated when only 10% of CoS queues are
available.
EX Series Switch
CoSOutOfDedicatedQueuesAlarm
Generated when there are no more available
dedicated CoS queues.
EX Series Switch
Cluster/Modo
Configuration (Configuration)
Core and controllers (Controllers)
Device alarm
CoS
Copyright © 2014, Juniper Networks, Inc.
19
Network Director Administration Guide
Table 6: Alarm Descriptions (continued)
Alarm Name
Description
Device Type
JdhcpLocalServerDupClientAlarm
Generated when a DHCP client is detected
changing interfaces.
EX Series Switch
JdhcpLocalServerlfLimitExceededAlarm
Generated when the client limit is reached on an
interface.
EX Series Switch
Jdhcpv6LocalServerLimitExceededAlarm
Generated when the client limit is reached on an
interface for DHCPv6.
EX Series Switch
Generated when an interface detects Digital
Optical Monitor (DOM) alarm conditions.
EX Series Switch
CollFlowOverloadAlarm
Generated when a collector PIC detects a hard or
soft flow overload.
EX Series Switch
CollFtpSwitchOverAlarm
Generated when an FTP server switchover occurs.
EX Series Switch
CollMemoryUnavailableAlarm
Generated when a PIC is out of memory or the
memory is unavailable.
EX Series Switch
CollUnavailableDestAlarm
Generated when a file transfer destination is
unavailable.
EX Series Switch
CollUnsuccessfulTransferAlarm
Generated when a collector file is unable to
transfer because the destination is unavailable.
EX Series Switch
Authentication Failure Alarm
Generated when a protocol message is received
that is not properly authenticated.
EX Series Switch
and wireless LAN
controller
Cold Start Alarm
Generated when a device is re-initializing and its
configuration might have changed.
EX Series Switch
and wireless LAN
controller
Link Down Alarm
Generated when a link is down. The trap is
generated when the ifOperStatus object for a
communication link is about to enter the down
state from another state other than notPresent.
This other state is indicated by the included value
of ifOperStatus.
EX Series Switch
and wireless LAN
controller
DHCP
DOM
DomAlertSetAlarm
Flow Collection (FlowCollection)
General
20
Copyright © 2014, Juniper Networks, Inc.
Chapter 2: Preferences
Table 6: Alarm Descriptions (continued)
Alarm Name
Description
Device Type
Link Up Alarm
Generated when a link comes up that was
previously in the down state. The trap is generated
when the ifOperStatus object for a communication
link left the down state and transitioned into
another state other than notPresent state. This
other state is indicated by the included value of
ifOperStatus.
EX Series Switch
and wireless LAN
controller
Warm Start Alarm
Generated when a device is re-initializing and its
configuration has not changed.
EX Series Switch
and wireless LAN
controller
Generated by an Op script or event policies. This
notification can include one or more
attribute-value pairs. The pairs are identified by
the jnxEventAvAttribute and jnxEventAvValue
objects.
EX Series Switch
L2aldGlobalMacLimitAlarm
Generated when the MAC limit is reached for the
entire system. This trap is sent only once, when
the limit is reached.
EX Series Switch
L2aldInterfaceMacLimitAlarm
Generated when the given interface reaches the
MAC limit (jnxl2aldInterfaceMacLimit).
EX Series Switch
L2aldRoutingInstMacLimitAlarm
Generated when the MAC limit is reached for a
given routing instance (jnxl2aldRoutingInst).
EX Series Switch
LacpTimeOutAlarm
Generated when LACP has timed out.
EX Series Switch
PortBpduErrorStatusChangeTrapAlarm
Generated when the port’s BPDU error state
(no-error or detected) changes.
EX Series Switch
PortLoopProtectStateChangeTrapAlarm
Generated when the port’s loop-protect state
(no-error or loop-prevented) changes.
EX Series Switch
PortRootProtectStateChangeTrapAlarm
Generated when the port’s root-protect state
(no-error or root-prevented) changes.
EX Series Switch
Generated when MAC addresses of the monitored
devices are learned or removed from the
forwarding database (FDB).
EX Series Switch
and wireless LAN
controller
Generic (GenericEvent)
GenericEventTrapAlarm
L2ALD
L2CP
MAC Forwarding Database (MACFDB)
MacChangedNotificationAlarm
Copyright © 2014, Juniper Networks, Inc.
21
Network Director Administration Guide
Table 6: Alarm Descriptions (continued)
Alarm Name
Description
Device Type
Counter Measures Alarm
Generated when counter measures are started
against a rogue device.
Wireless LAN
controller
Device Configuration Saved
Generated when the running configuration of the
switch is written to the configuration file.
Wireless LAN
controller
Multimedia Call Failure
Generated when a multimedia call fails.
Wireless LAN
controller
PoE failure
Generated when Power over Ethernet (PoE) has
failed on the indicated port.
EX Series Switch
Generated when an overload condition is detected
on a Passive Monitoring Interface.
EX Series Switch
PingEgressJitterThresholdExceededAlarm
Generated when egress time jitter
(jnxPingMaxEgressUs minus
jnxPingResultsMinEgressUs) exceeds the
configured threshold
(jnxPingCtlEgressJitterThreshold) causing the
egressJitterThreshold bit to be set.
EX Series Switch
and wireless LAN
controller
PingEgressStdDevThresholdExceededAlarm
Generated when the standard deviation of the
egress time (jnxPingResultsStddevEgressUs)
exceeds the configured threshold
(jnxPingCtlEgressTimeThreshold) and causes the
egress bit to be set.
EX Series Switch
and wireless LAN
controller
PingEgressThresholdExceededAlarm
Generated when the egress time
(jnxPingResultsStdevEgressUs) exceeds the
configured threshold
(jnxPingCtlEgressTimeThreshold) and the egress
threshold bit is set in jnxPingCtlTrapGeneration.
EX Series Switch
and wireless LAN
controller
PingIngressJitterThresholdExceededAlarm
Generated when ingress time jitter
(jnxPingResultsMaxIngressUs minus
jnxPingResultsMinIngressUs) exceeds the
configured threshold
(jnxPingCtlIngressJitterThreshold) and the
ingressJitterThreshold bit is set in
jnxPingCtlTrapGeneration.
EX Series Switch
and wireless LAN
controller
Misc.
Passive Monitoring (PassiveMonitoring)
PMonOverloadSetAlarm
Ping
22
Copyright © 2014, Juniper Networks, Inc.
Chapter 2: Preferences
Table 6: Alarm Descriptions (continued)
Alarm Name
Description
Device Type
PingIngressStddevThresholdExceededAlarm
Generated when the standard deviation of the
ingress time (jnxPingResultsStdDevIngressUs)
exceeds the configured threshold
(jnxPingCtlIngressStddevThreshold) and the
ingress StdDevThreshold bit is set in
jnxPingCtlTrapGeneration.
EX Series Switch
and wireless LAN
controller
PingIngressThresholdExceededAlarm
Generated when the ingress time jitter
(jnxPingResultsIngressUs) exceeds the configured
threshold (jnxPingCtlIngressTimeThreshold) and
the ingress threshold bit
(jnxPingIngressThresholdExceeded) is set in
jnxPingCtlTrapGeneration.
EX Series Switch
and wireless LAN
controller
PingRttJitterThresholdExceededAlarm
Generated when the round trip time jitter
(jnxPingResultsMaxRttUs minus
jnxPingResultsMinRttUs) exceeds the configured
threshold (jnxPingCtlRttJitterThreshold) and the
rttJitterThreshold bit is set in
jnxPingCtlTrapGeneration.
EX Series Switch
and wireless LAN
controller
PingRttStdDevThresholdExceededAlarm
Generated when the standard deviation of the
round trip time (jnxPingResultsStdDevRttUs)
exceeds the configured threshold
(jnxPingCtlRTTStdDev) and the
rttStdDevThreshold bit is set in
jnxPingCtlTrapGeneration.
EX Series Switch
and wireless LAN
controller
PingRttThresholdExceededAlarm
Generated when the round trip time
(jnxPingCtlRttThreshold) exceeds the configured
threshold (jnxPingCtlRttThreshold) and the
rttThreshold bit is set in jnxPingCtlTrapGeneration.
EX Series Switch
and wireless LAN
controller
Adhoc user detected
Generated when RF detection sweep finds an ad
hoc user or if a previously found ad hoc user
disappears.
Wireless LAN
controller
Client Blacklisted
Generated when an association, re-association,
or de-association request is detected from a
blacklisted transmitter.
Wireless LAN
controller
DoS Attack Detected
Generated when RF detection finds a
denial-of-service (DoS) attack occurring.
Wireless LAN
controller
DoS Port Detected
Generated when RF detection finds a denial of
service (DoS) attack occurring. This trap collects
port and access point information instead of
information about the listener.
Wireless LAN
controller
RF Detect (RFDetect)
Copyright © 2014, Juniper Networks, Inc.
23
Network Director Administration Guide
Table 6: Alarm Descriptions (continued)
Alarm Name
Description
Device Type
RF Interference Detected
Generated when a new noise source appears. A
given combination of noise source ID, listener, and
channel triggers this trap. It is normally not
triggered more than once every 15 minutes.
Wireless LAN
controller
RF Detect Classification Changed
Generated when the RF detection classification
rules change.
Wireless LAN
controller
Rogue Device Detected
Generated when RF detection finds a rogue device.
Wireless LAN
controller
Rogue Wired WLA Client Detected
Generated when a client is detected that
connected through a rogue access point that is
attached to a wired port.
Wireless LAN
controller
Rogue WLA Client Detected
Generated when RF detection finds a suspect
device.
Wireless LAN
controller
Rogue WLA Interference Detected
Generated when RF detection finds an interfering
rogue access point.
Wireless LAN
controller
Spoofed MAC Detected
Generated when RF detection finds an access
point using the MAC of the listener.
Wireless LAN
controller
Spoofed SSID Detected
Generated when RF detection finds an access
point using the SSID of the listener, and the access
point is not in the mobility domain.
Wireless LAN
controller
Suspected Device Detected
Generated when RF detection finds a suspect
device.
Wireless LAN
controller
Unauthorized AP Detected
Generated when RF detection discovers an
unauthorized access point being used.
Wireless LAN
controller
Unauthorized OUI Detected
Generated when RF detection finds an
unauthorized OUI being used.
Wireless LAN
controller
Unauthorized SSID Detected
Generated when RF detection finds an
unauthorized SSID being used.
Wireless LAN
controller
Generated when a GET request for an alarm
variable returns an error. The specific error is
identified by a varbind in
jnxRmonAlarmGetFailReason.
EX Series Switch
RMon
RmonAlarmGetFailureAlarm
SONET
24
Copyright © 2014, Juniper Networks, Inc.
Chapter 2: Preferences
Table 6: Alarm Descriptions (continued)
Alarm Name
Description
Device Type
SonetAlarmSetAlarm
Generated when there is a notification of a recently
set SONET or SDH alarm on an interface.
EX Series Switch
APSEventChannelMismatchAlarm
Generated when the value of an instance of
apsStatusChannelMismatches increments.
EX Series Switch
APSEventFEPLFAlarm
Generated when the value of an instance of
apsEventFEPLFs increments.
EX Series Switch
APSEventModeMismatchAlarm
Generated when the value of an instance of
apsEventModeMismatch increments.
EX Series Switch
APSEventPSBFAlarm
Generated when the value of an instance of
apsStatusPSBFs increments.
EX Series Switch
APSEventSwitchoverAlarm
Generated when the value of an instance of
apChanStatusSwitchover increments.
EX Series Switch
VccpMemberDownAlarm
Generated when a member is about to enter the
down state.
EX Series Switch
VccpMemberUpAlarm
Generated when a member has completed
transition from the down state to another state.
EX Series Switch
VccpPortDownAlarm
Generated when one of the member’s
communication links is about to enter the down
state.
EX Series Switch
VccpPortUpAlarm
Generated when one of the member’s
communication links has completed transition
from the down state to another state.
EX Series Switch
HostConnectivityLostAlarm
Generated when all the uplink ports of a virtual
switch residing in a host loses network
connectivity.
Host
HostNetworkRedundancyLostAlarm
Generated when some uplink ports of a virtual
switch residing in a host loses network
connectivity. It indicates that there are one or more
ports that still has network connectivity.
Host
VNetworkConnectivityLostAlarm
Generated when Network Director loses network
connectivity with the vCenter server.
Virtual Network
SONET APS (SONETAPS)
Virtual Chassis (VirtualChassis)
VNetwork
Copyright © 2014, Juniper Networks, Inc.
25
Network Director Administration Guide
Changing the Severity of Individual Alarms
You can change the severity of the alarms to match your corporate procedures and
guidelines. For example, at your company a DoS attack might be considered a critical
alarm, while Network Director has a default severity for DoS attacks as a major alarm.
Alarms appear on both tabs in the Individual Alarms and Threshold Settings section:
Alarm Settings and Threshold Settings.
To change the severity of an alarm:
1.
Select the current severity in the Severity column. A list of the severity levels appear.
2. Select the new severity level for the alarm.
3. Click OK and Yes to confirm the change to the severity setting.
Configuring Individual Alarm Notifications
You can configure e-mail notifications to be sent when an individual alarm is generated.
When you enable notification for an alarm, the notifications are sent to the e-mail
addresses configured for the alarm and the addresses configured for global alarm
notifications. Alarms appear on both tabs in the Individual Alarms and Threshold Settings
section: Alarm Settings and Threshold Settings.
To configure e-mail notification for an alarm name:
1.
Select the check box in the alarm’s Notification column.
If you later want to disable notification for the alarm, clear the check box.
2. Click Edit Notification in the Notification column. The Alarm Notification Details window
opens.
3. Enter one or more e-mail addresses in the Notification Email Addresses field. Separate
addresses with a comma (,).
You can later edit the addresses to send notifications to different addresses.
4. (Optional) Enter a comment in the Comments field. This comment is included in the
e-mail notification message.
5. Click Save.
Configuring Threshold Alarms
Threshold alarms are alarms that are generated when a monitored value crosses the
configured threshold. They provide enhanced visibility into potential issues on the network.
You configure and manage threshold alarms the same way as other alarms. You also
have the option of setting the threshold level of individual threshold alarms.
26
Copyright © 2014, Juniper Networks, Inc.
Chapter 2: Preferences
To set threshold alarm thresholds:
1.
Select the Threshold Settings tab in the Individual Alarms and Threshold settings
section of the Fault tab.
2. Click Edit Settings in the Threshold Settings column of the alarm threshold you want
to edit.
3. Set the threshold in the window that opens.
4. Click Save to save the new threshold.
Related
Documentation
•
Understanding the Network Director User Interface
•
Enabling SNMP Categories and Setting Trap Destinations
•
Understanding Fault Mode in Network Director
Copyright © 2014, Juniper Networks, Inc.
27
Network Director Administration Guide
28
Copyright © 2014, Juniper Networks, Inc.
PART 3
Administration
•
Audit Logs and Jobs on page 31
Copyright © 2014, Juniper Networks, Inc.
29
Network Director Administration Guide
30
Copyright © 2014, Juniper Networks, Inc.
CHAPTER 3
Audit Logs and Jobs
•
Viewing Audit Logs From Network Director on page 31
•
Managing Jobs on page 32
Viewing Audit Logs From Network Director
Audit logs are generated for login activity and tasks that are initiated from the Network
Director application. The Audit Logs page displays the logs for all user-initiated activities.
You can do the following on the Audit Logs page:
•
Sort, filter, and search the log entries using the standard table manipulation features
in Network Director.
•
Obtain more information about a log entry by double-clicking the entry or by selecting
the entry and clicking Show Details. The Audit Log Details window is displayed.
•
For a user-initiated task that runs as a job, you can obtain more information about the
job by clicking the job ID in the Job ID column.
To display the Audit Logs page:
1.
Click System in the Network Director banner.
2. Select View Audit Logs from the Tasks pane.
The Audit Logs page is displayed with the fields listed in Table 7 on page 31.
Table 7: Audit Logs Page Fields
Field
Description
User Name
The login ID of the user that initiated the task
User IP
The IP address of the client computer from which the user initiated the task
Task
The name of the task that triggered the audit log
Time
The data and time when the user initiated the task
Copyright © 2014, Juniper Networks, Inc.
31
Network Director Administration Guide
Table 7: Audit Logs Page Fields (continued)
Related
Documentation
Field
Description
Result
The execution result of the task that triggered the audit log:
•
Success—Job completed successfully
•
Failure—Job failed and was terminated
•
Job Scheduled—Job is scheduled but has not yet started
Description
A description of the audit log
Job ID
The job ID for any task that runs as a job
•
Audit Logs Overview on page 4
•
Managing Jobs on page 32
Managing Jobs
Network Director enables you to view and manage jobs. You can view the status of
completed jobs and cancel the jobs that are scheduled to execute at a later time or jobs
that are in progress.
The Job Management page, accessible as a System task, enables you to view and manage
all jobs. In addition, Network Director enables you to view special pre-filtered versions of
this page from various other tasks, such as View Discovery Status or View Image
Deployment Jobs. These pages contain the same fields (although some fields might be
hidden) and have the same functionality as the Job Management page, but they list only
those jobs relevant to particular tasks.
To display the Job Management page:
1.
Click System on the Network Director banner.
2. Select Manage Jobs from the Tasks pane. The Job Management page appears.
3. To view the details of a job, select a row and click Show Details or double-click a row.
4. To cancel a scheduled job, select a job that is scheduled for a later time or a job that
is in progress and click Cancel.
The fields in the Job Management page are described in Table 8 on page 33. To view any
hidden column, keep the mouse on any column heading and select the down arrow and
then click Columns. Select the check box to display the hidden columns.
NOTE: Details of jobs initiated from Network Director will be available only
from Network Director. These jobs will not be listed in the Job Management
pane in Junos Space platform and vice-versa.
32
Copyright © 2014, Juniper Networks, Inc.
Chapter 3: Audit Logs and Jobs
Table 8: Job Management Page Fields
Related
Documentation
Field
Description
Job ID
The unique ID assigned to the job
Name
The name of the job
Percent
The percentage of completion of the job
State
The status of the job:
•
Success—Job completed successfully
•
Failure—Job failed and was terminated
•
Job Scheduled—Job is scheduled but has not yet started
•
In progress—Job is has started, but not completed
•
Cancelled—Job is cancelled
Job Type
The type of the job
Summary
Summary of the job scheduled and executed with status
Scheduled
Start Time
The time when the job is scheduled to start
Actual Start
Time
The actual time when the job started
End Time
The time when the job was completed
User
The login ID of the user that initiated the task
Recurrence
The recurrent time when the job will be restarted.
•
Audit Logs Overview on page 4
•
Viewing Audit Logs From Network Director on page 31
Copyright © 2014, Juniper Networks, Inc.
33
Network Director Administration Guide
34
Copyright © 2014, Juniper Networks, Inc.
PART 4
Troubleshooting
•
Collecting Logs on page 37
Copyright © 2014, Juniper Networks, Inc.
35
Network Director Administration Guide
36
Copyright © 2014, Juniper Networks, Inc.
CHAPTER 4
Collecting Logs
•
Collecting Logs for Troubleshooting on page 37
Collecting Logs for Troubleshooting
Network Director enables you to collect logs and other data from both Network Director
and Junos Space that can assist in managing and monitoring Network Director servers.
Network Director collects the logs and troubleshooting data into a compressed file that
you can download. This file is named troubleshoot_yyyy-mm-dd_hh-mm-ss.zip—for
example, troubleshoot_2012-12-21_11-25-12.zip. The date and time in the file name is the
server Coordinated Universal Time (UTC) date and time.
To retrieve troubleshooting data and log files, follow these steps:
1.
Click System on the Network Director banner.
2. From the Tasks pane, click Collect Logs for Troubleshooting. The Collect Logs for
Troubleshooting page appears.
3. Click the Download troubleshooting data and logs from Network Director and Junos
Space link.
Network Director begins collecting the logs and data. It can take a few minutes for
Network Director to collect the information and create the zip file.
4. When the standard file download window for your browser opens, save the
troubleshoot_yyyy-mm-dd_hh-mm-ss.zip file.
5. When you contact the Juniper Technical Assistance Center, describe the problem you
encountered and provide the JTAC representative with the troubleshoot.zip file.
Table 9 on page 37 lists the files included in the
troubleshoot_yyyy-mm-dd_hh-mm-ss.zip file.
Table 9: Log Files in the troubleshooting.zip File
Description
Location
Jboss log files
/var/log/jboss/servers/server1
MSS OS adapter log files
/home/jmp/mssosadpater/var/errorLog/
Copyright © 2014, Juniper Networks, Inc.
37
Network Director Administration Guide
Table 9: Log Files in the troubleshooting.zip File (continued)
Description
Location
Daemon log files
/opt/opennms/logs/daemon/
Platform log files
/var/log/platform
Access Log Files
/var/log/httpd
Log files for Apache, NMA, Webproxy
/var/log/httpd/
Watchdog log file
/var/log/
Related
Documentation
38
•
Managing Jobs on page 32
•
Audit Logs Overview on page 4
•
Viewing Audit Logs From Network Director on page 31
Copyright © 2014, Juniper Networks, Inc.
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertising