SNMP Management for the SRC Software - Juniper Networks · PDF file(SNMP)agent ServiceManagementApplications ... (OSS)withtheSRCsoftwaresothattheOSScanbenotifiedofeventsinthelife cycleofSAEsessions.Hostedplug-insonly

SNMPManagement for the SRC Software

Published: 2014-12-10

Copyright © 2014, Juniper Networks, Inc.

Juniper Networks, Inc.1194 North Mathilda AvenueSunnyvale, California 94089USA408-745-2000www.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 UnitedStates and other countries. The Juniper Networks Logo, the Junos logo, and JunosE are trademarks of Juniper Networks, Inc. All othertrademarks, 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.

SNMPManagement for the SRC SoftwareCopyright © 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 theyear 2038. However, the NTP application is known to have some difficulty in the year 2036.

ENDUSER LICENSE AGREEMENT

The Juniper Networks product that is the subject of this technical documentation consists of (or is intended for use with) Juniper Networkssoftware. Use of such software is subject to the terms and conditions of the End User License Agreement (“EULA”) posted athttp://www.juniper.net/support/eula.html. By downloading, installing or using such software, you agree to the terms and conditions ofthat EULA.

Copyright © 2014, Juniper Networks, Inc.ii

http://www.juniper.net/support/eula.html

Table of Contents

About the Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Documentation and Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Supported Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Documentation Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Documentation Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii

Documentation Feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv

Requesting Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv

Self-Help Online Tools and Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . xv

Opening a Case with JTAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv

Part 1 Overview

Chapter 1 Software Features Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

SRC Component Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Chapter 2 Custom SNMP Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

SNMP Monitoring on C Series Controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Chapter 3 SNMP Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

SNMP Traps Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

MIBs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Configuration MIBs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

SNMP Traps and Informs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Performance Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

R/AV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Trap Numbers in Performance Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Event Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Alarm State Transitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Chapter 4 SRC Performance Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

SAE Performance Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Accounting Performance Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Authentication Performance Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

NIC Performance Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Router Driver Performance Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

System Management Performance Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Policy Engine Performance Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

SRC Redirector Performance Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

SRC ACP Performance Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

JPS Performance Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Chassis Performance Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

iiiCopyright © 2014, Juniper Networks, Inc.

Chapter 5 SNMP Chassis Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

SNMP Chassis Alarms on a C Series Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Part 2 Configuration

Chapter 6 Configuration Tasks for SNMP Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Configuring the SRC SNMP Agent (SRC CLI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Configuring the SNMP Agent (C-Web Interface) . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Configuring System Information for the SRC SNMP Agent (SRC CLI) . . . . . . . . . 38

Configuring System Information for the SNMP Agent (C-Web Interface) . . . . . . . 39

Chapter 7 Configuration Tasks for SRC SNMP Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Configuring the SRC SNMP Agent (SRC CLI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Configuring the SRC SNMP Agent (C-Web Interface) . . . . . . . . . . . . . . . . . . . . . . 42

Chapter 8 Configuration Tasks for SRC SNMP Agent Properties . . . . . . . . . . . . . . . . . . 43

Configuring General Properties for the SRC SNMP Agent (SRC CLI) . . . . . . . . . . 43

Configuring General Properties for the SRC SNMP Agent (C-Web Interface) . . . 44

Configuring Initial Properties for the SRC SNMP Agent (SRC CLI) . . . . . . . . . . . . 45

Configuring Initial Properties for the SRC SNMP Agent (C-Web Interface) . . . . . 46

Configuring Directory Connection Properties for the SRC SNMP Agent (SRC

CLI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Configuring Directory Connection Properties for the SRC SNMP Agent (C-Web

Interface) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Configuring Directory Monitoring Properties for the SRC SNMP Agent (SRC

CLI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Configuring Directory Monitoring Properties for the SRC SNMP Agent (C-Web

Interface) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Configuring Logging Destinations for the SRC SNMP Agent (SRC CLI) . . . . . . . . 48

Configuring Logging Destinations for the SRC SNMP Agent (C-Web

Interface) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Configuring JRE Properties (SRC CLI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Configuring JRE Properties (C-Web Interface) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Chapter 9 Configuration Tasks for SNMPv3 Users Access . . . . . . . . . . . . . . . . . . . . . . . . 51

Creating SNMPv3 Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Configuring Access Privileges for SNMPv3 Users (SRC CLI) . . . . . . . . . . . . . . . . . 52

Configuring Access Control for SNMPv3 Users (C-Web Interface) . . . . . . . . . . . . 53

Configuring Authentication for SNMPv3 Users (SRC CLI) . . . . . . . . . . . . . . . . . . . 53

Configuring Authentication (C-Web Interface) . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Configuring Encryption for SNMPv3 Users (SRC CLI) . . . . . . . . . . . . . . . . . . . . . . 54

Configuring Encryption (C-Web Interface) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Chapter 10 Configuration Tasks for Communities Access . . . . . . . . . . . . . . . . . . . . . . . . . 57

Configuring Access Control for Communities (SRC CLI) . . . . . . . . . . . . . . . . . . . . 57

Configuring Access Control for Communities (C-Web Interface) . . . . . . . . . . . . . 58

Configuring Access Control for the VACM (SRC CLI) . . . . . . . . . . . . . . . . . . . . . . . 59

Configuring Access Control for the VACM (C-Web Interface) . . . . . . . . . . . . . . . . 60

Associating Security Names with a Community (SRC CLI) . . . . . . . . . . . . . . . . . . 60

Associating Security Names with a Community (C-Web Interface) . . . . . . . . . . . 62

Copyright © 2014, Juniper Networks, Inc.iv

SNMP Management for the SRC Software

Defining Named Views (SRC CLI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Defining Named Views (C-Web Interface) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Chapter 11 Configuration Tasks for SNMP Groups Access . . . . . . . . . . . . . . . . . . . . . . . . 65

Defining Access Privileges for an SNMP Group (SRC CLI) . . . . . . . . . . . . . . . . . . . 65

Defining Access Privileges for an SNMP Group (C-Web Interface) . . . . . . . . . . . . 67

Assigning Security Names to Groups (SRC CLI) . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Assigning Security Names to Groups (C-Web Interface) . . . . . . . . . . . . . . . . . . . . 68

Chapter 12 Configuration Tasks for SNMP Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Configuring Notification Targets (SRC CLI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Configuring Notification Targets (C-Web Interface) . . . . . . . . . . . . . . . . . . . . . . . . 70

Chapter 13 Configuration Tasks for SNMP Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Configuring Performance Traps (SRC CLI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Configuring Performance Traps (C-Web Interface) . . . . . . . . . . . . . . . . . . . . . . . . 72

Configuring Event Traps (SRC CLI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Configuring Event Traps (C-Web Interface) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Defining SRC ACP Congestion Point Usage Trap Thresholds (SRC CLI) . . . . . . . . 73

Chapter 14 Tasks for Decoding Trap Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Decoding Trap Numbers for Raised Trap Actions . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Decoding Trap Numbers for Clear Trap Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Chapter 15 Configuration Tasks for Custom SNMP Monitors . . . . . . . . . . . . . . . . . . . . . . 79

Configuring SNMP Custom Monitors (C-Web Interface) . . . . . . . . . . . . . . . . . . . . 79

Configuring an SNMP Alarm on a C Series Controller (SRC CLI) . . . . . . . . . . . . . . 80

Defining an Alarm for an SNMP Monitor That Compares Object Values (SRC

CLI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Defining an Alarm to Monitor the Status of an Object (SRC CLI) . . . . . . . . . . . . . 83

Defining an Alarm for an SNMP Monitor That Compares Values Against

Thresholds (SRC CLI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Defining a Discontinuity Check to Validate Delta Values (SRC CLI) . . . . . . . . . . . 84

Configuring an SNMPv3 Security Name for SNMP Monitoring (SRC CLI) . . . . . . . 85

Defining Events for Which SNMP Sends Notifications (SRC CLI) . . . . . . . . . . . . . 85

Defining Events That Set Values for SNMP MIB Objects (SRC CLI) . . . . . . . . . . . 86

Chapter 16 Configuration Tasks for SNMP Chassis Alarms . . . . . . . . . . . . . . . . . . . . . . . . 87

Configuring SNMP Chassis Alarms (SRC CLI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Defining Alarm Thresholds for Battery Voltage Sensors . . . . . . . . . . . . . . . . . . . . 88

Defining Alarm Thresholds for CPU Sensors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Defining Alarm Thresholds for CPU Core Voltage Sensors . . . . . . . . . . . . . . . 89

Defining Alarm Thresholds for CPU DIMM Voltage Sensors . . . . . . . . . . . . . . 89

Defining Alarm Thresholds for CPU Temperature Sensors . . . . . . . . . . . . . . . 90

Defining Alarm Thresholds for Fan Speed Sensors . . . . . . . . . . . . . . . . . . . . . . . . . 91

Defining Alarm Thresholds for System Temperature Sensors . . . . . . . . . . . . . . . . 91

Defining Alarm Thresholds for Voltage Sensors . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Chapter 17 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Example: SNMP Monitoring of Multiple MIB Objects . . . . . . . . . . . . . . . . . . . . . . . 95

vCopyright © 2014, Juniper Networks, Inc.

Table of Contents

Chapter 18 Configuration Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Configuration Statements for the SRC SNMP Agent . . . . . . . . . . . . . . . . . . . . . . . 97

Configuration Statements for the SRC SNMP Agent . . . . . . . . . . . . . . . . . . . . . . . 98

Configuration Statements for the SNMP Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Configuration Statements for Customized SRC SNMP Monitors . . . . . . . . . . . . . 100

Part 3 Administration

Chapter 19 Managing the SRC SNMP Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Operating the SRC SNMP Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Starting the SRC SNMP Agent (SRC CLI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Starting the SRC SNMP Agent (C-Web Interface) . . . . . . . . . . . . . . . . . . . . . . . . 106

Stopping the SRC SNMP Agent (SRC CLI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Stopping the SRC SNMP Agent (C-Web Interface) . . . . . . . . . . . . . . . . . . . . . . . 107

Chapter 20 Monitoring the SRC SNMPAgent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Monitoring the SRC SNMP Agent (SRC CLI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Monitoring the SRC SNMP Agent (C-Web Interface) . . . . . . . . . . . . . . . . . . . . . . 109

Chapter 21 Routine Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Viewing Statistics About the Directory (SRC CLI) . . . . . . . . . . . . . . . . . . . . . . . . . 112

Viewing SNMP Statistics for the Directory (C-Web Interface) . . . . . . . . . . . . . . . . 112

Viewing Statistics for Directory Connections (SRC CLI) . . . . . . . . . . . . . . . . . . . . 113

Viewing SNMP Statistics for Directory Connections (C-Web Interface) . . . . . . . . 114

Viewing SNMP Information for Client Licenses (SRC CLI) . . . . . . . . . . . . . . . . . . . 115

Viewing SNMP Statistics for Client Licenses (C-Web Interface) . . . . . . . . . . . . . . 116

Viewing SNMP Information for Local Licenses (SRC CLI) . . . . . . . . . . . . . . . . . . . 116

Viewing SNMP Statistics for Local Licenses (C-Web Interface) . . . . . . . . . . . . . . 117

Viewing SNMP Statistics for Licenses by Device (C-Web Interface) . . . . . . . . . . . 118

Viewing SNMP Information for Licenses on Virtual Routers (SRC CLI) . . . . . . . . . 119

Viewing SNMP Information for Policies (SRC CLI) . . . . . . . . . . . . . . . . . . . . . . . . . 119

Viewing SNMP Statistics About Policies (C-Web Interface) . . . . . . . . . . . . . . . . 120

Viewing SNMP Information for the SAE Server Process (SRC CLI) . . . . . . . . . . . 120

Viewing SNMP Statistics About Server Processes (C-Web Interface) . . . . . . . . . 121

Viewing Statistics for RADIUS Clients (SRC CLI) . . . . . . . . . . . . . . . . . . . . . . . . . . 121

Viewing SNMP Statistics About RADIUS (C-Web Interface) . . . . . . . . . . . . . . . . 122

Viewing SNMP Information for RADIUS Clients (SRC CLI) . . . . . . . . . . . . . . . . . . 122

Viewing SNMP Statistics About RADIUS Clients (C-Web Interface) . . . . . . . . . . 123

Viewing SNMP Information for Routers and Devices (SRC CLI) . . . . . . . . . . . . . . 124

Viewing SNMP Statistics for Devices (C-Web Interface) . . . . . . . . . . . . . . . . . . . 124

Viewing Statistics for Device Drivers (SRC CLI) . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

Viewing Statistics for Specific Device Drivers (SRC CLI) . . . . . . . . . . . . . . . . . . . . 126

Viewing SNMP Statistics for Specific Devices (C-Web Interface) . . . . . . . . . . . . 127

Viewing Statistics for Subscriber and Service Sessions (SRC CLI) . . . . . . . . . . . 128

Viewing SNMP Statistics for Subscriber Sessions and Service Sessions (C-Web

Interface) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

Monitoring Statistics for Subscriber and Service Sessions (SRC CLI) . . . . . . . . . 129

Viewing Information About Components Installed (SRC CLI) . . . . . . . . . . . . . . . 129

Viewing Information About Components Installed (C-Web Interface) . . . . . . . . 130

Copyright © 2014, Juniper Networks, Inc.vi


Part 4 Troubleshooting

Chapter 22 Troubleshooting Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

Collecting Data with the Activity Monitor (SRC CLI) . . . . . . . . . . . . . . . . . . . . . . . 135

Collecting Data with the Activity Monitor (C-Web Interface) . . . . . . . . . . . . . . . . 136

Viewing Graphs (C-Web Interface) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

Viewing Graphs from a Web Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

Viewing Graphs for a Preset Time Period from a Web Page . . . . . . . . . . . . . 137

Viewing Graphs for Specified Time Periods from a Web Page . . . . . . . . . . . 138

Part 5 Index

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

viiCopyright © 2014, Juniper Networks, Inc.

Table of Contents

Copyright © 2014, Juniper Networks, Inc.viii


List of Tables

About the Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Table 1: Notice Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii

Table 2: Notice Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii

Table 3: Text Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii

Part 1 Overview

Chapter 1 Software Features Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Table 4: Descriptions of SRC Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Chapter 3 SNMP Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Table 5: Symbols in Performance Traps Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Table 6: Event Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Table 7: Alarm State Transitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Chapter 4 SRC Performance Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Table 8: Performance Traps–SAE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Table 9: Performance Traps–Accounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Table 10: Performance Traps–Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Table 11: Performance Traps–NIC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Table 12: Performance Traps–Router Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Table 13: Performance Traps–System Management Event . . . . . . . . . . . . . . . . . . 28

Table 14: Performance Traps–Policy Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Table 15: Performance Traps–SRC Redirector . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Table 16: Performance Traps–SRC ACP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Table 17: Performance Traps–JPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Table 18: Performance Traps–Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Part 2 Configuration

Chapter 17 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Table 19: Example Table for juniSaeRouterTable Object . . . . . . . . . . . . . . . . . . . . 95

Part 3 Administration

Chapter 21 Routine Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Table 20: Output Fields for show component . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

ixCopyright © 2014, Juniper Networks, Inc.

Copyright © 2014, Juniper Networks, Inc.x


About the Documentation

• Documentation and Release Notes on page xi

• Supported Platforms on page xi

• Documentation Conventions on page xi

• Documentation Feedback on page xiv

• Requesting Technical Support on page xiv

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.

Supported Platforms

For the features described in this document, the following platforms are supported:

• C Series

Documentation Conventions

Table 1 on page xii defines notice icons used in this guide.

xiCopyright © 2014, Juniper Networks, Inc.

http://www.juniper.net/techpubs/

http://www.juniper.net/books

http://www.juniper.net/techpubs/en_US/release-independent/src/information-products/pathway-pages/c-series/index.html

Table 1: Notice Icons

DescriptionMeaningIcon

Indicates important features or instructions.Informational note

Indicates a situation that might result in loss of data or hardware damage.Caution

Alerts you to the risk of personal injury or death.Warning

Alerts you to the risk of personal injury from a laser.Laser warning

Indicates helpful information.Tip

Alerts you to a recommended use or implementation.Best practice

Documentation Conventions

Table 1 on page xii defines the notice icons used in this guide. Table 3 on page xiii defines

text conventions used throughout this documentation.

Copyright © 2014, Juniper Networks, Inc.xii


Table 2: Notice Icons

DescriptionMeaningIcon

Indicates important features or instructions.Informational note

Indicates a situation that might result in loss of data or hardware damage.Caution

Alerts you to the risk of personal injury or death.Warning

Alerts you to the risk of personal injury from a laser.Laser warning

Indicates helpful information.Tip

Alerts you to a recommended use or implementation.Best practice

Table 3: Text Conventions

ExamplesDescriptionConvention

• Specify the keyword exp-msg.

• Run the install.sh script.

• Use the pkgadd tool.

• To cancel the configuration, click Cancel.

• Represents keywords, scripts, and tools intext.

• Represents a GUI element that the userselects, clicks, checks, or clears.

Bold text like this

user@host# set cache-entry-agecache-entry-age

Represents text that the user must type.Bold text like this

nic-locators { login { resolution { resolver-name /realms/ login/A1; key-type LoginName; value-type SaeId; }

Represents information as displayed on yourterminal’s screen, such as CLI commands inoutput displays.

Fixed-width text like this

• system ldap server{stand-alone;

• Use the request saemodify device failover

commandwith the force option

• user@host# . . .

• http://www.juniper.net/techpubs/software/management/sdx/api-index.html

• Represents configuration statements.

• Indicates SRC CLI commands and optionsin text.

• Represents examples in procedures.

• Represents URLs.

Regular sans serif typeface

xiiiCopyright © 2014, Juniper Networks, Inc.


command

http://www.juniper.net/techpubs/software/ management/sdx/api-index.html

http://www.juniper.net/techpubs/software/ management/sdx/api-index.html

Table 3: Text Conventions (continued)

user@host# set local-addresslocal-address

Represents variables in SRC CLI commands.Italic sans serif typeface

Another runtime variable is <gfwif>.In text descriptions, indicate optionalkeywords or variables.

Angle brackets

Press Enter.Indicates the name of a key on the keyboard.Key name

Press Ctrl + b.Indicates that you must press two or morekeys simultaneously.

Key names linked with a plus sign(+)

• There are two levels of access: user andprivileged.

• SRC-PE Getting Started Guide.

• o=Users, o=UMC

• The /etc/default.properties file.

• Emphasizes words.

• Identifies book names.

• Identifies distinguished names.

• Identifies files, directories, and paths intext but not in command examples.

Italic typeface

Plugin.radiusAcct-1.class=\net.juniper.smgt.sae.plugin\RadiusTrackingPluginEvent

At the end of a line, indicates that the textwraps to the next line.

Backslash

diagnostic | lineRepresent a choice to select one keyword orvariable to the left or right of this symbol.(The keyword or variable may be eitheroptional or required.)

Words separated by the | symbol

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/.

• E-mail—Send your comments to [email protected]. 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.

Copyright © 2014, Juniper Networks, Inc.xiv


http://www.juniper.net/techpubs/index.html

https://www.juniper.net/cgi-bin/docbugreport/

mailto:[email protected]?subject=

• 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 Casewith JTAC

You can open a case with JTAC on the Web or by telephone.

• 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).

For international or direct-dial options in countries without toll-free numbers, see

http://www.juniper.net/support/requesting-support.html.

xvCopyright © 2014, Juniper Networks, Inc.


http://www.juniper.net/us/en/local/pdf/resource-guides/7100059-en.pdf

http://www.juniper.net/support/warranty/

http://www.juniper.net/customers/support/

http://www2.juniper.net/kb/

http://www.juniper.net/techpubs/

http://kb.juniper.net/

http://www.juniper.net/customers/csc/software/

http://kb.juniper.net/InfoCenter/

http://www.juniper.net/company/communities/

http://www.juniper.net/cm/

https://tools.juniper.net/SerialNumberEntitlementSearch/

http://www.juniper.net/cm/

http://www.juniper.net/support/requesting-support.html

Copyright © 2014, Juniper Networks, Inc.xvi


PART 1

Overview

• Software Features Overview on page 3

• Custom SNMP Monitors on page 7

• SNMP Traps on page 9

• SRC Performance Traps on page 19

• SNMP Chassis Alarms on page 33

1Copyright © 2014, Juniper Networks, Inc.

Copyright © 2014, Juniper Networks, Inc.2


CHAPTER 1

Software Features Overview

• SRC Component Overview on page 3

SRC Component Overview

The SRC software is a dynamic system. It contains many components that you use to

build a subscriber management environment. You can use these tools to customize and

extend the SRC software for your use and to integrate the SRC software with other

systems. The SRC software also provides the operating system and management tools

for C Series Controllers.

Table 4 on page 3 gives a brief description of the components that make up the SRC

software.

Table 4: Descriptions of SRC Components

DescriptionComponent

Server Components

• Authorizes, activates, and deactivates subscriber and service sessions by interacting withsystems such as Juniper Networks routers, cable modem termination system (CMTS)devices, RADIUS servers, and directories.

• Collects accounting information about subscribers and services from routers, and storesthe information in RADIUS accounting servers, flat files, and other accounting databases.

• Provides plug-ins and application programming interfaces (APIs) for starting and stoppingsubscriber and service sessions and for integrating with systems that authorize subscriberactions and track resource usage.

Service activation engine (SAE)

Used in conjunction with the MX Series router running the packet-triggered subscribers andpolicy control (PTSP) solution, the SIC listens for RADIUS accounting events from IP edgedevices (accounting clients) and stores them in the Session State Registrar (SSR), orforwards them to a remote AAA server, allowing the SRC software to gain increasedsubscriber awareness. Additionally, the SIC can optionally edit accounting events beforerouting them.

Subscriber Information Collector (SIC)

Acts as a policy decision point (PDP) and policy enforcement point (PEP) that managesthe relationships between application managers and CMTS devices in a PCMM environment.

Juniper Policy Server (JPS)

Collects information about the state of the network and can provide a mapping from agiven type of network data to another type of network data.

Network information collector (NIC)


Table 4: Descriptions of SRC Components (continued)


Redirects HTTP requests received from IP Filter to a captive portal page.Redirect Server

The SRC Third-Generation Partnership Project (3GPP) gateway is a Diameter-basedcomponent in the SRC software, which provides integration with 3GPP Policy and ChargingControl environments, to provide fixed-mobile convergence (FMC). The SRC 3GPP gatewayprovides Gx-based integration with the Policy and Charging Rules Function (PCRF). TheSRC 3GPP gateway uses the Gx interface to mediate between the PCRF and JuniperNetworks routers like the E Series Broadband Services routers and MX Series routers. TheGx interface on the SRC 3GPP gateway communicates with the PCRF using the Diameterprotocol.

3GPP Gateway

The SRC software includes a Web application server that hosts the Web Services Gatewayand the Volume Tracking Application (SRC VTA). In production environments, thisapplication server is designed to host only these applications. However, you can load yourown applications into this server for testing or demonstration purposes.

Web Application Service

Allows a gateway client—an application that is not part of the SRC network—to interactwith SRC components through a Simple Object Access Protocol (SOAP) interface.

The Web Services Gateway provides the Dynamic Service Activator which allows a gatewayclient to dynamically activate and deactivate SRC services for subscribers and to run scriptsthat manage the SAE.

Web Services Gateway

Repository

The SRC software includes the Juniper Networks database, which is a built-in LightweightDirectory Access Protocol (LDAP) directory for storing all SRC data including services,policies, and small subscriber databases.

For large subscriber databases, you must supply your own directory.

Directory

The SSR is a stateless, highly reliable and highly available database cluster. When used inconjunction with an MX Series router running the packet-triggered subscribers and policycontrol (PTSP) solution, the SSR stores the IP edge attachment subscriber sessions datalearned from IP edge devices in the centralized SSR database.

Session State Registrar (SSR)

SRC Configuration andManagement Tools

Provides a way to configure the SRC software on a C Series Controller from a Junos OS–likeCLI. The SRC CLI includes the policies, services, and subscribers CLI, which has separateaccess privileges.

SRC command line interface (CLI)

Provides a way to configure, monitor, and manage the SRC software on a C Series Controllerthrough a Web browser. The C-Web interface includes a policies, services, and subscriberscomponent, which has separate access privileges.

C-Web interface

Monitors system performance and availability. It runs on all the SRC hosts and makesmanagement information available through SNMP tables and sends notifications by meansof SNMP traps.

Simple Network Management Protocol(SNMP) agent

Service Management Applications (Run on external system)





Integrates into an IP multimedia system (IMS) environment. The SRC software provides aDiameter protocol-based interface that allows the SRC software to integrate with servicesfound on the application layer of IMS.

IMS Services Gateway

SRC Programming Interfaces

Allows you to configure or request information from the NETCONF server on a C SeriesController that runs the SRC software. Applications developed with the NETCONF API runon a system other than a C Series Controller.

NETCONF API

Tracks sessions and enables linking the rest of the service provider’s operations supportsystem (OSS) with the SRC software so that the OSS can be notified of events in the lifecycle of SAE sessions. Hosted plug-ins only.

CORBA plug-in service providerinterface (SPI)

Provides remote access to the SAE core API. Applications that use these extensions to theSRC software run on a system other than a C Series Controller.

CORBA remote API

Performs NIC resolutions. Applications that use these extensions to the SRC software runon a system other than a C Series Controller.

NIC access API

Controls the behavior of the SRC software. Applications that use these extensions to theSRC software run on a system other than a C Series Controller.

SAE core API

Provides an interface to call scripts that supply custom services such as provisioning policieson a number of systems across a network.

Script services

The Volume Tracking Application (VTA) API is a Simple Object Access Protocol (SOAP)interface that allows developers to create gateway clients and that administrators use tomanage VTA subscribers and sessions. The SRC Web Services Gateway allows a gatewayclient—an application that is not part of the SRC network—to interact with SRC components,such as the VTA, through a SOAP interface.

VTA API

Authorization and Accounting Applications

Authenticates subscribers and authorizes their access to the requested system or service.Accepts accounting data—time active and volume of data sent—about subscriber andservice sessions. RADIUS servers run on a system other than a C Series Controller.

AAA RADIUS servers

Authorizes and tracks subscribers’ use of network resources associated with services thatthe SRC application manages.

SRC Admission Control Plug-In (SRCACP)

Stores tracking data to accounting flat files that can be made available to external systemsthat send the data to a rating and billing system.

Flat file accounting


Chapter 1: Software Features Overview



The SRC Volume Tracking Application (SRC VTA) is an SRC component that allows serviceproviders to track and control the network usage of subscribers and services. You can controlvolume and time usage on a per-subscriber or per-service basis. This level of control meansthat service providers can offer tiered services that use volume as a metric, while alsocontrolling abusive subscribers and applications.

When a subscriber or service exceeds bandwidth limits (or quotas), the SRC VTA can takeactions including imposing rate limits on traffic, sending an e-mail notification, or chargingextra for additional bandwidth consumed.

Volume Tracking Application

Demonstration Applications (available on the Juniper NetworksWeb site)

Defines a callback interface, which receives events when IT managers complete specifiedoperations.

Enterprise Audit Plug-In

Allows service providers to provision services for enterprise subscribers on routers runningJunosE or Junos OS and allows IT managers to manage services.

Enterprise Manager Portal can be used with NAT Address Management Portal to allowservice providers to manage public IP addresses for use with NAT services on routers runningJunos OS and to all IT managers to make requests about public IP addresses through theEnterprise Manager Portal.

Enterprise Manager Portal

Integrates IP address managers, such as a DHCP server or a RADIUS server, into anSRC-managed network so that the SAE is notified about subscriber events. The MonitoringAgent application runs on a Solaris platform.

Monitoring Agent application

Provides a framework for building Web applications that allow residential and enterprisesubscribers to manage their own network services. It comes with several full-featuredsample Web applications that are easy to customize and suitable for deployment. TheResidential service selection portals run on a Solaris platform.

Residential service selection portals

Lets service providers supply an interface to their business customers for managing andprovisioning services.

Sample enterprise service portal

RelatedDocumentation

• SRC Product Description



CHAPTER 2

Custom SNMPMonitors

• SNMP Monitoring on C Series Controllers on page 7

SNMPMonitoring on C Series Controllers

You can create custom SNMP monitors to detect changes in MIB objects. Use custom

monitors to generate an alarm and take action in response to an alarm.

To configure a monitor, you define a condition that when met generates an SNMP

notification. You can define a monitor for any single MIB object (of type integer) supported

on a C Series Controller. These MIBs include Juniper Networks enterprise-specific objects

as well as standard MIB objects.

You can configure the following for custom monitors:

• Alarms—Define an alarm condition and an event to generate in response to the alarm.

An alarm identifies the object to be monitored, the frequency with which the monitor

retrieves a sample value for the object, and a condition that triggers an event.

• Events—Define the type of action (SNMP set or notification) to be taken in response

to an alarm condition. If you do not define an event for an alarm, SNMP sends the

notifications based on the monitor type.

The SRC software supports the following types of alarm conditions for monitors:

• Boolean test—Compares a sample value with a specified value or range of values.

• Existence test—Monitors when an object appears, disappears, or changes value.

• Threshold test—Monitors when an object's value rises above or falls below specified

values.

A monitor supports only one type of alarm condition, or test, at a time. Each alarm can

use one of the following sampling methods:

• Absolute value—Uses the actual value of the object.

Existence tests support only absolute values.

• Delta value—Uses the difference between two sample values.


By using the delta value sampling method, you can configure SNMP to detect a

discontinuity in values to prevent false alarms caused by the value of a MIB object

being reset. At the end of a polling interval before the SNMP agent calculates a delta

value, SNMP checks the value of a MIB object called a discontinuity marker. If the value

of the discontinuity marker changes, SNMP does not perform the test for the associated

condition until the next polling interval.

For alarms that do not have a configured event, SNMP sends the following notifications

that are defined in RFC 2981—Event MIB (October 2000):

• Boolean or existence test—mteTriggerFired

• Threshold test (rising value)—mteTriggerRising

• Threshold test (falling value)—mteTriggerfalling

The default configuration for SNMP custom monitors assesses all objects in a MIB branch

based on the object identifier specified for the monitor. For this type of monitor, you can

configure SNMP notification MIB objects located in the same row as the object that

generates the event, as well as for a single object. You can create sophisticated monitors

by monitoring an entire branch, then creating notifications for multiple objects.

See the information about SRC MIBs on the Juniper Web site at

http://www.juniper.net/techpubs/software/management/src.

Also, see information about the disman event MIB in RFC 2981—Event MIB (October

2000).


• SNMP Traps Overview on page 9

• Configuring an SNMP Alarm on a C Series Controller (SRC CLI) on page 80

• Configuring an SNMPv3 Security Name for SNMP Monitoring (SRC CLI) on page 85

• Configuration Statements for Customized SRC SNMP Monitors on page 100

• Example: SNMP Monitoring of Multiple MIB Objects on page 95



http://www.juniper.net/techpubs/software/management/src

CHAPTER 3

SNMP Traps


• Performance Traps on page 11

• Trap Numbers in Performance Traps on page 12

• Event Traps on page 13

• Alarm State Transitions on page 16

SNMP Traps Overview

The SNMP agent provides network management systems with SNMP trap notifications

in case of component failure or when critical resources are out of configurable limits.

This information is captured in a Management Information Base (MIB).

The SNMP agent can be run on each SRC host. It can monitor any SRC process running

on the host and is preconfigured to monitor SRC processes. Additionally, it provides

detailed monitoring and configuration of SRC server components.

MIBs

The SNMP agent monitors MIB variables. Most variables measure the performance of

the system. Some variables are counters, such as the saeLogins variable, which counts

the total number of subscriber logins since startup. Some variables are gauges, and their

numbers go up and down, such as the saeHeapUsed variable, which measures the Java

Virtual Machine heap that is currently in use.

A MIB defines a trap type that is associated with many MIB variables. For traps based on

counters, the SNMP agent periodically polls each specified variable. It takes the difference

between the previous and current values of the variable and compares that difference

with the threshold. If the difference has moved up across thresholds, the SNMP agent

sends a trap raising an alarm (minor, major, or critical) for the highest threshold crossed

to all configured receivers. If the difference has moved down across thresholds, the agent

sends a trap clearing the alarm of the lowest threshold crossed.

You can configure the polling interval between samples. If you change the polling interval,

also adjust the thresholds. For instance, if the critical threshold for SAE logins is 1,000

and the interval is 60 seconds, then a critical alarm is raised if there are more than 1,000

logins in 60 seconds. But if you change the interval to 600 seconds, then you would need

to change the threshold to 10,000 to have the same meaning.


For traps based on gauges, the previous value is not needed; the current value is compared

with the thresholds.

In the trap tables, there is a field named R/AV, where R means rate, and AV means

absolute value. Rate is used for variables that are counters, and it measures the rate of

change of the counter. Absolute value is used for variables that are gauges.

ConfigurationMIBs

The SRC software has a limited number of MIB variables that can be set, such as variables

to shut down or start components.

MIB Structure

The SNMP agent MIB uses the following Juniper Networks MIBs:

• Juniper-SDX-ACP-MIB—SRC ACP MIB

• Juniper-SDX-CHASSIS-MIB—Chassis MIB (for C Series Controllers)

• Juniper-SDX-DES-MIB—Directory eventing system MIB

• Juniper-SDX-GW-MIB—Gateway applications MIB (includes the NIC MIB)

• Juniper-SDX-JPS-MIB—JPS MIB

• Juniper-SDX-LICENSE-MIB—Licensing MIB

• Juniper-SDX-MIB—Main Juniper Networks SDX MIB

• Juniper-SDX-MIBS—Collection of Juniper Networks SDX MIB modules

• Juniper-SDX-POM-MIB—Policy management MIB

• Juniper-SDX-REDIRECTOR-MIB—Redirector MIB

• Juniper-SDX-SAE-MIB—SAE MIB

• Juniper-SDX-TC-MIB—Textual conventions MIB

• Juniper-SDX-TRAP-MIB—SRC trap definition MIB

• Juniper-UNI-SMI—Base SMI MIB

MIB Location

The MIBs are located on the Juniper Networks Web site at


Traps

Traps are individual events that the SNMP agent can monitor, such as the number of

timeouts or errors that have occurred or connections that have opened or closed. There

are two types of traps:

• Performance traps—Traps that poll MIB variables associated with the trap to determine

whether a variable has crossed configured thresholds. If the variable crosses a threshold,

an alarm is triggered and a trap is sent to the list of configured receivers.



• Event traps—Traps that are sent when an event occurs; for example, when a connection

is established or closed.

SNMP Traps and Informs

SNMP notifications can be sent as traps or inform requests. SNMP traps are unconfirmed

notifications. SNMP informs are confirmed notifications.

SNMP traps are defined in either standard or enterprise-specific MIBs. The standard and

enterprise-specific traps are compiled into the network management software.

With traps, the receiver does not send any acknowledgment when it receives a trap and

the sender cannot determine if the trap was received. To increase reliability, SNMP informs

are supported in SNMPv3. With an inform, the receiver acknowledges the message with

a response.

For information on system logging severity levels for SNMP traps, see Categories and

Severity Levels for Event Messages.


Configuring the SRC SNMP Agent (SRC CLI) on page 41•

• SAE Performance Traps on page 19

• Accounting Performance Traps on page 21

• Authentication Performance Traps on page 23

• NIC Performance Traps on page 25

• Router Driver Performance Traps on page 25

• System Management Performance Traps on page 28

• Policy Engine Performance Traps on page 28

• SRC Redirector Performance Traps on page 29

• SRC ACP Performance Traps on page 29

• JPS Performance Traps on page 30

Performance Traps

Trap tables list all the traps supported by the SNMP agent, the text displayed for each

trap, trap thresholds and intervals, and any special notes pertaining to the trap.

Table 5 on page 11 describes the symbols used in the performance traps tables.

Table 5: Symbols in Performance Traps Tables

DescriptionSymbol

Severity level of the trap: MINOR, MAJOR, CRITICAL, or CLEAR$S

Status data$D


Chapter 3: SNMP Traps

Table 5: Symbols in Performance Traps Tables (continued)

DescriptionSymbol

Polling interval$P

Threshold value$T

Trap action; displayed as RAISED or CLEARED$A

“Exceeded” if the trap is raised; “ is below” if the trap is cleared$L

SRC performance trap tables contain a trap ID, text displayed, and default values for

alarm threshold levels, as well as rate (R) and absolute values (AV) fields.

R/AV

Each performance trap table has a field called R/AV. R means rate, and AV means

absolute value.

• Rate is used for variables that are counters. The rate is the difference between the

current value of the underlying MIB variable being monitored and its previous value,

which was read <interval> time ago. The interval length affects those values that are

appropriate for the thresholds; that is, the longer the interval, the larger the thresholds

must be. For instance, saeLogins is a counter of the total number of SAE logins. With

the default interval of 60 seconds, the critical threshold of 2,000 means that a critical

trap is sent if there are more than 2,000 logins within one minute. If you change the

interval to 300 seconds (5 minutes), to keep the critical threshold at 2,000 logins a

minute, you need to change the threshold to 10,000 (the number of logins in 5 minutes

for a rate of 2,000 per minute).

• Absolute value is used for variables that are gauges, and they transition from one alarm

threshold level to the next.


SNMP Traps Overview on page 9•


• Configuring Performance Traps (SRC CLI) on page 71



Trap Numbers in Performance Traps

Performance traps contain a trap ID, a severity, and an action. The trap ID, severity, and

action are encoded in the trap number to make it easy to configure trap receivers, such

as HP OpenView, to color and highlight traps.

Every performance trap has four trap definitions: one for critical, major, and minor severity

levels, and one for the clear action. For critical, major, and minor severity levels, the action



is raise. For the clear action, there is no severity level, because the severity level is implied

by the last raise action for the trap ID.

Severity levels are assigned the following numbers:

• Critical=1

• Major=2

• Minor=3

• Information=5

The JuniSdxTrapID ::= TEXTUAL-CONVENTION section in the Juniper-SDX-TC MIB lists

the trap IDs for all traps. The Juniper-SDX-TRAP MIB defines the SDX traps.

You can access the MIBs on the Juniper Web site at



Performance Traps on page 11•

• Decoding Trap Numbers for Raised Trap Actions on page 77

• Decoding Trap Numbers for Clear Trap Actions on page 77

Event Traps

Table 6 on page 13 lists the event traps.

Table 6: Event Traps

Text DisplayedTrap IDTrap Event

$S:SAE:The total number of sum-weighted line cards allocated in this SRC network is$LINE_CARD_NUMBER ($THRESHOLD_PERCENTAGE)%. This $L the network ERXcapacity threshold of $T sum-weighted line cards.: $A

9saeLicenseNetworkCapacity

$S:LICENSE SERVER:$SERVICE_SESSIONS ($SERVICES_PERCENTAGE%) of theavailable licensed service sessions are in use.: $A

11saeServiceSessionLicense

INFORMATION:SAE:Vta EJB plug-in connection changes its status:RAISE13vtaEjbConnectionStatus

When the trap is raised, the text displayed is:

SS Plugin:{plugin-name}: Mem Fail queue Size during Synchronization exceeded:RAISE

When the trap is cleared, the text displayed is:

SS Plugin:{plugin-name}: Mem Fail queue Size during Synchronization exceeded:CLEAR

NOTE: If the SAE is restarted after the trap is raised, then the SRC software does notsend the clear trap for the already raised trap.

15sspluginSyncFailQueueSize



Table 6: Event Traps (continued)


When juniSaeRouterUseFailOver is FALSE:

• INFORMATION:SAE Router Driver: The router connection to $juniSaeRouterClientIdhas been closed.:RAISE

When juniSaeRouterUseFailOver is TRUE:

• INFORMATION:SAE Router Driver:The router connection to $juniSaeRouterClientIdhas been closed and redirected to$juniSaeRouterFailOverIp:$juniSaeRouterFailOverPort:RAISE

211routerConnClosed

INFORMATION:SAE Router Driver:The router connection to $juniSaeRouterClientIdwent down.:RAISE

212routerConnDown

INFORMATION:SAE Router Driver:The router connection from $juniSaeRouterClientIdhas been rejected.:RAISE

213routerConnRejected

INFORMATION:SAE Router Driver:A new router connection was established with$juniSaeRouterClientId.:RAISE

210routerConnUp


• INFORMATION:SAE Router Driver: The configured state of router$juniSaeRouterClientId is out of synch with SAE. The configured action to be takenby SAE is $configuredAction.:RAISE


• INFORMATION:SAE Router Driver: The configured state of router$juniSaeRouterClientId is successfully resynchronized with SAE.:CLEAR

214routerConfOutOfSynch

INFORMATION:Agent: The agent has started.:RAISE110agentStarted

CRITICAL: Agent: The agent has failed to restart after $ATTEMPTS attempts:RAISE111agentRestartFailed

INFORMATION:Agent:The agent has shutdown.:RAISE112agentShutdown

INFORMATION:$I: This component is up.:RAISE114componentUp

INFORMATION:$I: This component is down:RAISE115componentDown

INFORMATION:$I:The directory connection has been established with $LDAP_HOSTon port $LDAP_PORT, and has a type of $CONNECTION_TYPE.:RAISE

130dirConnected

CRITICAL:$I:The directory connection with $LDAP_HOST has failed.:RAISE131dirConnectionFailure

CRITICAL:$I:A directory connection is not available.:RAISE132dirNotAvail

INFORMATION:NIC Host: The redundancy state of the NIC Host has switched to$juniNicHostRedundState.:RAISE

240nicHostRedundStateSwitched

INFORMATION:NIC Host: The NIC Host failed to start due to misconfiguration. The errormessage is "$MESSAGE".:RAISE

241nicHostMisconfigured





CRITICAL:NIC sae-client agent:Blacklisted SAE: <SAE-KEY>:RAISE242nicHostBlacklistedSAE

INFORMATION: ACP State Sync:ACP finished state sync with SAE for$juniAcpVirtualRouterName.:RAISE

290acpSyncCompleted

INFORMATION: ACP Host:The redundancy state of the ACP Host has switched to$juniAcpRedundState.:RAISE

291acpRedundStateSwitched


• 'CRITICAL:ACP:{acpCPUsed%}% of congestion point is in use. This exceeded thethreshold of {THRESHOLD}%.:RAISE' where acpCPUsed% is the percentage ofbandwidth in use out of the total bandwidth of the congestion point.

• 'MAJOR:ACP:{acpCPUsed%}% of congestion point is in use. This is below thethreshold of {THRESHOLD}%.:RAISE' where acpCPUsed% is the percentage ofbandwidth in use out of the total bandwidth of the congestion point.

• 'MINOR:ACP:{acpCPUsed%}% of congestion point is in use. This exceeded thethreshold of {THRESHOLD}%.:RAISE' where acpCPUsed% is the percentage ofbandwidth in use out of the total bandwidth of the congestion point.


• 'CLEAR:ACP:{acpCPUsed%}% of congestion point is in use. This is below thethreshold of {THRESHOLD}%.:CLEAR' where acpCPUsed% is the percentage ofbandwidth in use out of the total bandwidth of the congestion point.

281acpCPUsage

INFORMATION: JPS:A new application manager connection was established.:RAISE260jpsAmConnUp

INFORMATION:JPS:The application manager connection went down.:RAISE261jpsAmConnDown

INFORMATION:JPS:A new CMTS connection was established.:RAISE262jpsCmtsConnUp

INFORMATION:JPS:A CMTS connection went down.:RAISE263jpsCmtsConnDown


• INFORMATION:jdbReplicationFailure:Failed to replicate LDAP data{juniSdxJdbReplicationDirection} neighbor {juniSdxJdbNeighbor}.The latest JDBreplicaiton status is:{juniSdxJdbLastStatus }:RAISE


• INFORMATION: jdbReplicationFailure:Community directory server{juniSdxJdbNeighbor} latest update status error:CLEAR

292jdbReplicationFailure


• INFORMATION:System:hardware failure is found with $juniSdxOperatingSensor onsystem $juniSdxOperatingLocation:RAISE


• INFORMATION:System:hardware failure with $juniSdxOperatingSensor on system$juniSdxOperatingLocation is cleared:CLEAR

300systemOperatingFailure






• INFORMATION:System:disk failure is found:RAISE

When the trap is cleared, text displayed is:

• INFORMATION:System:disk failure is cleared:CLEAR

301diskFailure


SNMP Traps Overview on page 9•

• Configuring Event Traps (SRC CLI) on page 72

• Alarm State Transitions on page 16

Alarm State Transitions

Table 7 on page 16 lists the alarm state transitions.

Table 7: Alarm State Transitions

Action(s)Current DataThreshold

Last DataThreshold

No actionNONENONE

Raise minor eventMINORNONE

Raise major eventMAJORNONE

Raise critical eventCRITICALNONE

Clear minor eventNONEMINOR

No actionMINORMINOR

Raise major eventMAJORMINOR

Raise critical eventCRITICALMINOR

Clear critical eventNONEMAJOR

Raise minor eventClear major eventMINORMAJOR

No actionMAJORMAJOR

Raise critical eventCRITICALMAJOR

Clear critical eventNONECRITICAL



Table 7: Alarm State Transitions (continued)

Action(s)Current DataThreshold

Last DataThreshold

Raise minor eventClear critical eventMINORCRITICAL

Raise major eventClear critical eventMAJORCRITICAL

No actionCRITICALCRITICAL








CHAPTER 4

SRC Performance Traps




• NIC Performance Traps on page 25

• Router Driver Performance Traps on page 25

• System Management Performance Traps on page 28

• Policy Engine Performance Traps on page 28

• SRC Redirector Performance Traps on page 29

• SRC ACP Performance Traps on page 29

• JPS Performance Traps on page 30

• Chassis Performance Traps on page 31

SAE Performance Traps

Table 8 on page 19 lists the performance traps for the SAE.

Table 8: Performance Traps–SAE

Alarm Threshold Levels(default values)

R/AVInterval(sec)MinorMajorCriticalText Displayed

TrapIDTrap Event

AV60809095$S:SAE:$D% ofJava VM heap is inuse. This $L thethreshold of$T %.:$A

1saeHeapUsed

R6040010002000$S:SAE:Duringthe last $Ps, $Dlogins occurred.This $L thethreshold of $Tlogins.:$A

2saeLogins


Table 8: Performance Traps–SAE (continued)



TrapIDTrap Event

R6040010002000$S:SAE:Duringthe last $Ps, $Dlogouts occurred.This $L thethreshold of $Tlogouts.:$A

3saeLogouts

R6050010002000$S:SAE:Duringthe last $Ps, $Dservices wereactivated. This $Lthe threshold of$T serviceactivations.:$A

4saeServiceActivations

R6050010002000$S:SAE:Duringthe last $Ps, $Dservices weredeactivated. This$L the thresholdof $T servicedeactivations.:$A

5saeServiceDeactivations

AV60120001400018000$S:SAE:Thenumber of usersessions is $D.This $L thethreshold of $Tusers sessions.:$A

6saeCurrentUsers

AV60909599$S:SAE:$D% ofthe availablelicenses are inuse. This $L thethreshold of$T.:$A

7saeUserNumberLicense

AV350014101$S:SAE:The SAElicense is about toexpire in $D days.This $L thethreshold of$T.:$A

8saeUserLicenseExpiry



Table 8: Performance Traps–SAE (continued)



TrapIDTrap Event

AV900407090$S:SAE:The clienthas consumed$D% of itsavailable license.This $L thethreshold of$T.:$A

12saeClientLicExpiry

AV120100030005000{0}:SAE:The SAEVTA Fail QueueSize is {1} MB.

14saeVtaFailQueueSize





Accounting Performance Traps

Table 9 on page 21 lists the performance traps for accounting.

Table 9: Performance Traps–Accounting



TrapIDTrap Event

R60125$S:SAE RADIUSAccountingClient:During thelast $Ps, $D invalidserver addresserrors occurred. This$L the threshold of$T invalid serveraddress errors.:$A

20saeAccInvalidServerAddresses

AV6075015002250$S:SAE RADIUSAccountingClient:The round tripmessage time is$Dms. This $L thethreshold of$Tms.:$A

21saeAccRoundTripTime


Chapter 4: SRC Performance Traps

Table 9: Performance Traps–Accounting (continued)



TrapIDTrap Event

R60125$S:SAE RADIUSAccountingClient:During thelast $Ps, $Dretransmissionsoccurred. This $Lthe threshold of $Tretransmissions.:$A

22saeAccRetransmissions

R60125$S:SAE RADIUSAccountingClient:During thelast $Ps, $Dmalformedresponses occurred.This $L thethreshold of $Tmalformedresponses.:$A

23saeAccMalformedResponses

R60125$S:SAE RADIUSAccountingClient:During thelast $Ps, $D badauthenticator erroroccurred. This $Lthe threshold of $Tbad authenticatorserrors.:$A

24saeAccBadAuthenticators

AV60102550$S:SAE RADIUSAccountingClient:The numberof pending requestsis $D. This $L thethreshold of $Tpending requests:$A

25saeAccPendingRequests

R60102030$S:SAE RADIUSAccountingClient:During thelast $Ps, $Dtimeouts occurred.This $L thethreshold of $Ttimeouts.:$A

26saeAccTimeouts



Table 9: Performance Traps–Accounting (continued)



TrapIDTrap Event

R60102030$S:SAE RADIUSAccountingClient:During thelast $Ps, $Dunknown type errorsoccurred. This $Lthe threshold of $Tunknown typeerrors.:$A

27saeAccUnknownTypes

AV60102030$S:SAE RADIUSAccountingClient:During thelast $Ps, $D packetswere dropped. This$L the threshold of$T droppedpackets.:$A

28saeAccPacketsDropped





Authentication Performance Traps

Table 10 on page 23 lists the performance traps for authentication.

Table 10: Performance Traps–Authentication


R/AVInterval(sec)MinorMajorCriticalText DisplayedTrapIDTrap Event

AV601510$S:SAE RADIUS AuthenticationClient:During the last $Ps, $Dinvalid server address errorsoccurred. This $L the threshold of$T invalid server addresserrors.:$A

40saeAuthInvalidServerAddresses



Table 10: Performance Traps–Authentication (continued)



R6075015002250$S:SAE RADIUS AuthenticationClient:The round trip messagetime is $Dms. This $L thethreshold of $Tms:$A

41saeAuthRoundTripTime

R60125$S:SAE RADIUS AuthenticationClient:During the last $Ps, $Dretransmissions occurred. This $Lthe threshold of $Tretransmissions.:$A

42saeAuthAccessRetransmissions

R60125$S:SAE RADIUS AuthenticationClient:During the last $Ps, $Dmalformed responses occurred.This $L the threshold of $Tmalformed responses.:$A

43saeAuthMalformedAccessResponses

60125$S:SAE RADIUS AuthenticationClient:During the last $Ps, $D badauthenticators errors occurred.This $L the threshold of $T.:$A

44saeAuthBadAuthenticators

AV60102550$S:SAE RADIUS AuthenticationClient:The number of pendingrequests is $D. This $L thethreshold of $T pendingrequests:$A

45saeAuthPendingRequests

R60125$S:SAE RADIUS AuthenticationClient:During the last $Ps, $Dtimeouts occurred. This $L thethreshold of $T timeouts.:$A

46saeAuthTimeouts

R60125$S:SAE RADIUS AuthenticationClient:During the last $Ps, $Dunknown type errors occurred.This $L the threshold of $Tunknown type errors.:$A

47saeAuthUnknownTypes

R60125$S:SAE RADIUS AuthenticationClient:During the last $Ps, $Dpackets were dropped. This $L thethreshold of $T droppedpackets.:$A

48saeAuthPacketsDropped







NIC Performance Traps

Table 11 on page 25 lists the performance traps for NIC.

Table 11: Performance Traps–NIC



R601510$S:NIC Host: During the last $Ps,the number of resolution errorsthat occurred is $D. This $L is thethreshold of $T errors.:$A

230nicHostReslvErrors

R602505001000$S:NIC Host: During the last $Ps,the average time this NIC Hostspent on resolutions is $Dms. This$L the threshold of $Tms.:$A

231nicHostAvgReslvTime





Router Driver Performance Traps

Table 12 on page 25 lists the performance traps for router drivers.

Table 12: Performance Traps–Router Drivers



R601510$S:SAE Router Driver($juniSaeRouterClientId):Duringthe last $Ps, $D router errorsoccurred. This $L the threshold of$T errors.:$A

190routerMsgErrors



Table 12: Performance Traps–Router Drivers (continued)



R601510$S:SAE Router Driver($juniSaeRouterClientId):Duringthe last $Ps, $D router timeoutsoccurred. This $L the threshold of$T timeouts.:$A

191routerMsgTimeouts

R60100250500$S:SAE Router Driver($juniSaeRouterClientId):Duringthe last $Ps, the average time thatincoming router messages waitedto be processed is $Dms. This $Lthe threshold of $Tms.:$A

192routerAvgJobQTime

AV601005002500$S:SAE Router Driver($juniSaeRouterClientId):Thenumber of unprocessed incomingrouter messages is $D. This $L thethreshold of $T messages.:$A

193routerJobQLength

AV6050001000030000$S:SAE Router Driver($juniSaeRouterClientId):Theoldest unprocessed routermessage has been waiting for$Dms. This $L the threshold of$Tms.:$A

194routerJobQAge

R601005001000$S:SAE Router Driver($juniSaeRouterClientId): Duringthe last $Ps, the average time (inmilliseconds) this router driverspent handling 'object added'notifications is $Dms. This $L thethreshold of $Tms.:$A

195routerAvgAddTime

R601005001000$S:SAE Router Driver($juniSaeRouterClientId): Duringthe last polling interval, theaverage time (in milliseconds) thisrouter driver spent handling'object changed' notifications is$Dms. This $L the threshold of$Tms.:$A

196routerAvgChgTime



Table 12: Performance Traps–Router Drivers (continued)



R601005001000$S:SAE Router Driver($juniSaeRouterClientId): Duringthe last polling interval, theaverage time (in milliseconds) thisrouter driver spent handling'object deleted' notifications is$Dms. This $L the threshold of$Tms.:$A

197routerAvgDelTime

AV3011050{0}:SAE Router Driver:REMOVEDEC message timed out. ERXRouter and the router driver are ininconsistent state. Either COPSconnection bounce or SAE restartis required to trigger the syncrequest : {1}

198routerStateOutOfSynch







SystemManagement Performance Traps

Table 13 on page 28 lists the performance traps for system management event.

Table 13: Performance Traps–SystemManagement Event



AV3090%ofMAX

95%ofMAX

100%of MAX

$S: Ldap: The Ldap Limit has beenreached: $D entries, during thelast $Ps. This $L the threshold of$T entries.:$A.

113agentLdapLimitReached





Policy Engine Performance Traps

Table 14 on page 28 lists the performance traps for policy engine.

Table 14: Performance Traps–Policy Engine



AV601000500200$S:Policy Engine:The averagepolicy group modificationprocessing time is $D ms. This $Lthe threshold of $T ms.:$A

150penAvgPGModProcTime

AV601000500200$S:Policy Engine:The averageinterface classifier modificationprocessing time is $D ms. This $Lthe threshold of $T ms.:$A

151penAvgICMModProcTime



Table 14: Performance Traps–Policy Engine (continued)



R301510$S:Policy Decision Point:Duringthe last $Ps, $D errors occurred.This $L the threshold of $T PDPerrors.:$A

152pdpErrors





SRC Redirector Performance Traps

Table 15 on page 29 lists the performance traps for SRC redirector.

Table 15: Performance Traps–SRC Redirector



R900123$S:SDX Redirector:During the last$Ps, the global bucket limit hasbeen reached for $D times. This$L the threshold of $T times.:$A

170redirGBLimitReached





SRC ACP Performance Traps

Table 16 on page 30 lists the performance traps for the SRC-Admission Control Plug-In

(SRC ACP) application.



Table 16: Performance Traps–SRC ACP



AV6080%90%95%$S:ACP:$D% of Java VM heap is in use.This $L the threshold of $T%.:$A

280acpHeapUsed





JPS Performance Traps

Table 17 on page 30 lists the performance traps for the Juniper Policy Server (JPS).

Table 17: Performance Traps–JPS



AV6080%90%95%$S:JPS:$D% of Java VM heap is in use. This$L the threshold of $T%.:$A

250jpsHeapUsed

R60200s600s900s$S:JPS:During the last $Ps, the averagetime this JPS spent on CMTSsynchronizations is $Dms. This $L thethreshold of $Tms.:$A

251jpsCmtsAvgSyncTime

R601s2s3s$S:JPS:During the last $Ps, the averagetime the CMTS connection spent onsuccessfully completed DEC/RPTtransactions is $Dms. This $L the thresholdof $Tms.:$A

252jpsCmtsAvgDecTime

R602s5s10s$S:JPS:During the last $Ps, the averagetime the JPS message handler spent onmessage handling is $Dms. This $L thethreshold of $Tms.:$A

253jpsMsgHdlrProcTime

R606s15s30s$S:JPS:During the last $Ps, the averagetime the JPS message flow spent onmessage handling is $Dms. This $L thethreshold of $Tms.:$A

254jpsMsgFlowProcTime



Table 17: Performance Traps–JPS (continued)



R6011001000$S:JPS:During the last $Ps, the number ofmessages dropped by a JPS message flowis $D. This $L the threshold of $T.:$A

255jpsMsgFlowDroppedMsgs





Chassis Performance Traps

Table 18 on page 31 lists the performance traps for chassis events.

Table 18: Performance Traps–Chassis


R/AVInterval(sec)MinorMajorCriticalText DisplayedTrap IDTrap Event

AV6080%ofMAX

90%ofMAX

95% ofMAX

$S:diskUsage: directory(juniSdxDiskPath) uses upto(juniSdxDiskUsedPercentage)of disk space. This exceeded(THRESHOLD).:RAISE

302diskUsage









CHAPTER 5

SNMP Chassis Alarms

• SNMP Chassis Alarms on a C Series Controller on page 33

SNMPChassis Alarms on a C Series Controller

You can configure SNMP to establish built-in chassis alarms that monitor the sensors

on C Series Controllers. The chassis alarms are preconfigured SNMP monitors that detect

changes in the MIB objects described in Juniper-SDX-CHASSIS-TRAP-MIB (Chassis Trap

MIB). The chassis alarms are configured to use the Boolean test condition and absolute

value sampling method. Each time you start the SNMP agent and you have enabled

chassis alarms, the initial action is to raise the clear trap for all chassis sensors.

You cannot delete chassis alarms, but you can disable them. You can modify the time

interval between which SNMP samples the value for the chassis alarms. You can also

define the alarm thresholds for each chassis alarm.

NOTE: If you want to use the built-in chassis alarms, youmust delete anycustom SNMPmonitors that you configured to detect changes in theJuniper-SDX-CHASSIS-TRAP-MIBMIB objects.

To configure the chassis alarms, youmust set the editing level to expert.


• Configuring SNMP Chassis Alarms (SRC CLI) on page 87





PART 2

Configuration

• Configuration Tasks for SNMP Agent on page 37

• Configuration Tasks for SRC SNMP Agent on page 41

• Configuration Tasks for SRC SNMP Agent Properties on page 43

• Configuration Tasks for SNMPv3 Users Access on page 51

• Configuration Tasks for Communities Access on page 57

• Configuration Tasks for SNMP Groups Access on page 65

• Configuration Tasks for SNMP Notifications on page 69

• Configuration Tasks for SNMP Traps on page 71

• Tasks for Decoding Trap Numbers on page 77

• Configuration Tasks for Custom SNMP Monitors on page 79

• Configuration Tasks for SNMP Chassis Alarms on page 87

• Example on page 95

• Configuration Statements on page 97




CHAPTER 6

Configuration Tasks for SNMP Agent

• Configuring the SRC SNMP Agent (SRC CLI) on page 37

• Configuring the SNMP Agent (C-Web Interface) on page 37

• Configuring System Information for the SRC SNMP Agent (SRC CLI) on page 38

• Configuring System Information for the SNMP Agent (C-Web Interface) on page 39

Configuring the SRC SNMPAgent (SRC CLI)

To configure the SRC SNMP agent to control its operation:

1. Configure information supplied by the SRC SNMP agent, including the listening address

and system information.

See “Configuring System Information for the SRC SNMP Agent (SRC CLI)” on page 38.

2. Configure access control for the SRC SNMP agent, including access for SNMPv3 users,

SNMPv1 and SNMPv2 communities (traditional access control), and the view-based

access control model (VACM).

See “Configuring Access Control for SNMPv3 Users (C-Web Interface)” on page 53.

See “Configuring Access Control for Communities (SRC CLI)” on page 57.

See “Configuring Access Control for the VACM (SRC CLI)” on page 59.

3. Configure active monitoring.

See “Configuring Notification Targets (SRC CLI)” on page 69.


Configuration Statements for the SRC SNMP Agent on page 98•

• Operating the SRC SNMP Agent on page 105

Configuring the SNMPAgent (C-Web Interface)

To configure the SNMP agent to control its operation:

1. Configure information supplied by the SNMP agent, including the listening address

and system information.


See “Configuring System Information for the SNMP Agent (C-Web Interface)” on

page 39.

2. Configure access control for the SNMP agent, including access for SNMPv3 users,

SNMPv1 and SNMPv2 communities (traditional access control), and the view-based

access control model (VACM).

See “Configuring Access Control for SNMPv3 Users (C-Web Interface)” on page 53.

See “Configuring Access Control for Communities (C-Web Interface)” on page 58.

See “Configuring Access Control for the VACM (C-Web Interface)” on page 60.

3. Configure active monitoring.

See “Configuring Notification Targets (C-Web Interface)” on page 70.




• Configuring Access Control for SNMPv3 Users (C-Web Interface) on page 53


Configuring System Information for the SRC SNMPAgent (SRC CLI)

Use the following configuration statements to configure information supplied by the SRC

SNMP agent:

snmp {contact contact;name name;location location;description description;address [address...];

}

To configure properties for the SRC SNMP agent:

1. From configuration mode, access the configuration statement that configures the

SRC SNMP agent.

[edit]user@host# edit snmp

2. (Optional) Specify the administrative contact for the system being managed by SNMP.

[edit snmp]user@host# set contact contact

3. (Optional) Specify the name of the system being managed by SNMP.

[edit snmp]user@host# set name name



4. (Optional) Specify the location of the system being managed by SNMP.

[edit snmp]user@host# set location location

5. (Optional) Specify the description of the system being managed by SNMP.

[edit snmp]user@host# set description description

6. (Optional) Specify the listening address on which to receive incoming SNMP requests.

[edit snmp]user@host# set address [address...]

To list more than one IP address, enter the addresses separated by spaces within

brackets. By default, the SRC SNMP agent listens on all IPv4 interfaces.

7. (Optional) Verify your configuration.

[edit snmp] user@host# show

If you did not configure the SNMP agent, the command displays only the SRC SNMP

agent configuration.





• Configuration Statements for the SRC SNMP Agent on page 98

Configuring System Information for the SNMPAgent (C-Web Interface)

To configure properties for the SNMP agent:

1. Click Configure, and expand SNMP>Agent.

The Agent pane appears.

2. Enter information as described in the Help text in the main pane, and then clickApply.


• Configuring the SNMP Agent (C-Web Interface) on page 37

• Configuring System Information for the SRC SNMP Agent (SRC CLI) on page 38

• Configuring SNMP Custom Monitors (C-Web Interface) on page 79


Chapter 6: Configuration Tasks for SNMP Agent



CHAPTER 7

Configuration Tasks for SRC SNMP Agent


• Configuring the SRC SNMP Agent (C-Web Interface) on page 42

Configuring the SRC SNMPAgent (SRC CLI)

The SRC SNMP agent obtains most of its information from the directory, but you configure

the local properties that cannot be stored in the directory.

To configure the local properties for the SRC SNMP agent:

1. Configure general properties for the SRC SNMP agent, including trap history limit,

component polling interval, and protocol log level.

See “Configuring General Properties for the SRC SNMP Agent (SRC CLI)” on page 43.

2. Configure initial properties for the SRC SNMP agent, including the connection from

the SRC SNMP agent to the directory and directory monitoring properties.

See “Configuring Initial Properties for the SRC SNMP Agent (SRC CLI)” on page 45.

See “Configuring Directory Connection Properties for the SRC SNMP Agent (SRC CLI)”

on page 46.

See “Configuring Directory Monitoring Properties for the SRC SNMP Agent (SRC CLI)”

on page 47.

3. Configure logging destinations for the SRC SNMP agent.

See “Configuring Logging Destinations for the SRC SNMP Agent (SRC CLI)” on page 48.

4. (Optional) Configure the Java heap memory for the SRC SNMP agent.

See “Configuring JRE Properties (SRC CLI)” on page 49.

After you configure the local properties for the SRC SNMP agent, you can configure the

SNMP agent. See “Configuring the SRC SNMP Agent (SRC CLI)” on page 37.


Starting the SRC SNMP Agent (SRC CLI) on page 105•

• Stopping the SRC SNMP Agent (SRC CLI) on page 106

• Monitoring the SRC SNMP Agent (SRC CLI) on page 109


Configuring the SRC SNMPAgent (C-Web Interface)

The SNMP agent obtains most of its information from the directory, but you configure

the local properties that cannot be stored in the directory.

To configure the local properties for the SRC SNMP agent:

1. Configure general properties for the SRC SNMP agent, including trap history limit,

component polling interval, and protocol log level.

See “Configuring General Properties for the SRC SNMP Agent (C-Web Interface)” on

page 44.

2. Configure initial properties for the SRC SNMP agent, including the connection from

the SRC SNMP agent to the directory and directory monitoring properties.

See “Configuring Initial Properties for the SRC SNMP Agent (C-Web Interface)” on

page 46.

See “Configuring Directory Connection Properties for the SRC SNMP Agent (C-Web

Interface)” on page 47.

See “Configuring Directory Monitoring Properties for the SRC SNMP Agent (C-Web

Interface)” on page 48.

3. Configure logging destinations for the SRC SNMP agent.

See “Configuring Logging Destinations for the SRC SNMP Agent (C-Web Interface)”

on page 49.

4. (Optional) Configure the Java heap memory for the SRC SNMP agent.

After you configure the local properties for the SRC SNMP agent, you can configure the

SNMP agent. See “Configuring the SNMP Agent (C-Web Interface)” on page 37.


• Starting the SRC SNMP Agent (C-Web Interface) on page 106

• Configuring an SRC Component to Store Log Messages in a File (SRC CLI)



• Monitoring the SRC SNMP Agent (C-Web Interface) on page 109



CHAPTER 8

Configuration Tasks for SRC SNMP AgentProperties

• Configuring General Properties for the SRC SNMP Agent (SRC CLI) on page 43

• Configuring General Properties for the SRC SNMP Agent (C-Web Interface) on page 44

• Configuring Initial Properties for the SRC SNMP Agent (SRC CLI) on page 45

• Configuring Initial Properties for the SRC SNMP Agent (C-Web Interface) on page 46

• Configuring Directory Connection Properties for the SRC SNMP Agent (SRC

CLI) on page 46

• Configuring Directory Connection Properties for the SRC SNMP Agent (C-Web

Interface) on page 47

• Configuring Directory Monitoring Properties for the SRC SNMP Agent (SRC

CLI) on page 47

• Configuring Directory Monitoring Properties for the SRC SNMP Agent (C-Web


• Configuring Logging Destinations for the SRC SNMP Agent (SRC CLI) on page 48

• Configuring Logging Destinations for the SRC SNMP Agent (C-Web


• Configuring JRE Properties (SRC CLI) on page 49

• Configuring JRE Properties (C-Web Interface) on page 50

Configuring General Properties for the SRC SNMPAgent (SRC CLI)

Use the following configuration statements to configure general properties for the SRC

SNMP agent:

snmp agent {trap-history-limit trap-history-limit;component-polling-interval component-polling-interval;protocol-log-level protocol-log-level;

}



SRC SNMP agent.


[edit]user@host# edit snmp agent

2. (Optional) Specify the maximum number of elements stored in the SNMP trap history

table.

[edit snmp agent]user@host# set trap-history-limit trap-history-limit

3. (Optional) Specify the interval at which an SRC component is polled.

[edit snmp agent]user@host# set component-polling-interval component-polling-interval

4. (Optional) Specify the log level for SNMP requests and responses received from the

master agent.

[edit snmp agent]user@host# set protocol-log-level protocol-log-level

To enable packet-level logging, set the protocol-log-level option to 9 or less.


[edit snmp agent] user@host# show

The output indicates the trap history limit, the component polling interval, the protocol

log level, the initial properties, the logging destinations, and the Java heap size.





Configuring General Properties for the SRC SNMPAgent (C-Web Interface)



The SNMP pane appears.



Configuring General Properties for the SRC SNMP Agent (SRC CLI) on page 43•






Configuring Initial Properties for the SRC SNMPAgent (SRC CLI)

Use the following configuration statements to configure initial properties for the SRC

SNMP agent:

snmp agent initial {base-dn base-dn;host-id host-id;

}



SRC SNMP agent.

[edit]user@host# edit snmp agent initial

2. Specify the DN of the directory used for the SRC SNMP agent configuration data.

[edit snmp agent initial]user@host# set base-dn base-dn

3. Identifies the system management configuration in the directory server that provides

the remaining configuration for the SRC SNMP agent.

[edit snmp agent initial]user@host# set host-id host-id

If the entry does not exist, the entry and the subentries for the components and traps

is automatically created in the system management configuration.


[edit snmp agent initial] user@host# showbase-dn o=UMC;host-id POP-ID;directory-connection { url ldap://127.0.0.1:389/; principal cn=sysman,ou=components,o=operators,<base>; credentials ********;}directory-eventing { eventing;}




• Configuring General Properties for the SRC SNMP Agent (SRC CLI) on page 43



Chapter 8: Configuration Tasks for SRC SNMP Agent Properties

Configuring Initial Properties for the SRC SNMPAgent (C-Web Interface)


1. Click Configure, and expand SNMP>Agent >Initial.

The Initial pane appears.



Configuring General Properties for the SRC SNMP Agent (C-Web Interface) on page 44•



Configuring Directory Connection Properties for the SRC SNMPAgent (SRC CLI)

Use the following configuration statements to configure directory connection properties

for the SRC SNMP agent:

snmp agent initial directory-connection {url url;backup-urls [backup-urls...];principal principal;credentials credentials;protocol (ldaps);timeout timeout;check-interval check-interval;blacklist;snmp-agent;

}

To configure directory connection properties:


SRC SNMP agent.

[edit]user@host# edit snmp agent initial directory-connection

2. Specify the directory connection properties.

[edit snmp agent initial directory-connection]user@host# set ?

For more information about the directory connection properties, see Configuring

Directory Connection Properties.


[edit snmp agent initial directory-connection] user@host# showurl ldap://127.0.0.1:389/;



principal cn=sysman,ou=components,o=operators,<base>;credentials ********;



• Configuring Directory Connection Properties for the SRC SNMP Agent (C-Web Interface)

on page 47

• Configuring Directory Monitoring Properties for the SRC SNMP Agent (SRC CLI) on

page 47


ConfiguringDirectoryConnectionPropertiesfor theSRCSNMPAgent(C-WebInterface)

To configure directory connection properties:

1. Click Configure, and expand SNMP>Agent >Initial >Directory Connection.

The Directory Connection pane appears.



Configuring Directory Connection Properties for the SRC SNMP Agent (SRC CLI) on

page 46

•

• Configuring Directory Monitoring Properties for the SRC SNMP Agent (C-Web Interface)

on page 48



Configuring Directory Monitoring Properties for the SRC SNMPAgent (SRC CLI)

Use the following configuration statements to configure directory monitoring properties

for the SRC SNMP agent:

snmp agent initial directory-eventing {eventing;signature-dn signature-dn;polling-interval polling-interval;event-base-dn event-base-dn;dispatcher-pool-size dispatcher-pool-size;

}



SRC SNMP agent.

[edit]user@host# edit snmp agent initial directory-eventing



2. Specify the properties for the SRC SNMP agent.

[edit snmp agent initial eventing]user@host# set ?


[edit snmp agent initial directory-eventing] user@host# showeventing;



• Configuring Directory Monitoring Properties for the SRC SNMP Agent (C-Web Interface)

on page 48

• Configuring Directory Connection Properties for the SRC SNMP Agent (SRC CLI) on

page 46


ConfiguringDirectoryMonitoringProperties for theSRCSNMPAgent(C-WebInterface)


1. Click Configure, and expand SNMP>Agent >Initial >Directory Eventing.

The Directory Eventing pane appears.



Configuring Directory Monitoring Properties for the SRC SNMP Agent (SRC CLI) on

page 47

•

• Configuring Directory Connection Properties for the SRC SNMP Agent (C-Web Interface)

on page 47



Configuring Logging Destinations for the SRC SNMPAgent (SRC CLI)

Use the following configuration statement to configure logging destinations for the SRC

SNMP agent:

snmp agent logger name ...

To configure logging destinations:


SRC SNMP agent.

[edit]user@host# edit snmp agent



2. Specify the name and type of logging destination.

For file-based logging:

[edit snmp agent]user@host# set logger name file

For system log–based logging:

[edit snmp agent]user@host# set logger name syslog



• Configuring System Logging (SRC CLI)

• Configuring an SRC Component to Store Log Messages in a File (SRC CLI)

• Configuring the SAE to Store Log Messages in a File (C-Web Interface)

• Configuring Logging Destinations for the SRC SNMP Agent (C-Web Interface) on

page 49

Configuring Logging Destinations for the SRC SNMPAgent (C-Web Interface)

To configure logging destinations:


2. From the Create new list, select Logger.

3. Enter a name for the new Logger in the dialog box, and click OK.

4. For file-based logging, from the side pane, expandFile, enter information as described

in the Help text in the main pane, and then click Create.

5. For system log-based logging, expand Syslog, enter information as described in the

Help text in the main pane, and then click Create.


Configuring Logging Destinations for the SRC SNMP Agent (SRC CLI) on page 48•




Configuring JRE Properties (SRC CLI)

Use the following configuration statements to configure Java Runtime Environment (JRE)

properties for the SRC SNMP agent:

snmp agent java {heap-size heap-size;

}





SRC SNMP agent.

[edit]user@host# edit snmp agent java

2. (Optional) Specify the maximum amount of memory available to the JRE.

[edit snmp agent java]user@host# set heap-size heap-size

Do not change this value unless instructed to do so by Juniper Networks.


[edit snmp agent java] user@host# showheap-size 160m;


Configuring JRE Properties (C-Web Interface) on page 50•

Configuring JRE Properties (C-Web Interface)


1. Click Configure, and expand SNMP>Agent >Java.

The Java pane appears.



• Configuring JRE Properties (SRC CLI) on page 49



CHAPTER 9

Configuration Tasks for SNMPv3 UsersAccess

• Creating SNMPv3 Users on page 51

• Configuring Access Privileges for SNMPv3 Users (SRC CLI) on page 52


• Configuring Authentication for SNMPv3 Users (SRC CLI) on page 53

• Configuring Authentication (C-Web Interface) on page 54

• Configuring Encryption for SNMPv3 Users (SRC CLI) on page 54

• Configuring Encryption (C-Web Interface) on page 55

Creating SNMPv3 Users

You can create a user associated with an SNMPv3 group. For each SNMPv3 user, you

specify the authentication type, encryption, and access privileges. The username functions

as a security name when the SNMPv3 security model is a user-based security model

(USM). This provides a level of security for SNMPv3.

To create an SNMPv3 user:

• From configuration mode, enter the following configuration statement.

[edit]user@host# edit snmp v3 usm local-engine user username


Configuring Authentication (C-Web Interface) on page 54•



• Configuring Access Privileges for SNMPv3 Users (SRC CLI) on page 52


Configuring Access Privileges for SNMPv3 Users (SRC CLI)

In a user-based security model (USM), you can define access privileges for SNMPv3

users. But you cannot assign the security name to an SNMP group. Here, the security

name is the username configured at the [edit snmp v3 usm local-engine user] hierarchy

level.

Use the following configuration statements to define access privileges for an SNMPv3

user at the [edit snmp v3 usm local-engine user username access] hierarchy level:

snmp v3 usm local-engine user username access {authorization (read-only | read-write);oid oid;

}

To define access privileges for an SNMPv3 user in a USM:

1. From configuration mode, enter the following configuration statement.

[edit]user@host# edit snmp v3 usm local-engine user username access

2. (Optional) Specify the authorization level.

To specify read-only access:

[edit snmp v3 usm local-engine user username access]user@host# set authorization read-only

To specify read-and-write access:

[edit snmp v3 usm local-engine user username access]user@host# set authorization read-write

3. (Optional) Specify the object identifier used to represent the subtree of MIB objects

to which access is allowed.

[edit snmp v3 usm local-engine user username access]user@host# set oid oid

NOTE: By default, all clients are allowed to access the completeOID tree.


root@c3bng-src4# showauthorization read-only;oid 1;


Creating SNMPv3 Users on page 51•





• Configuring Access Control for Communities (SRC CLI) on page 57


Configuring Access Control for SNMPv3 Users (C-Web Interface)

To configure access control for SNMPv3 users:

1. Click Configure, and expand SNMP>V3>USM>Local Engine.

2. From the Create new list, select User.

3. Enter a name for the new User in the dialog box, and click OK.

4. From the side pane, expand the name of the user, and (optional) specify the

authentication type and (optional) the encryption.

NOTE: Before you configure encryption, youmust configure theauthentication type.


Configuring an SNMPv3 Security Name for SNMP Monitoring (SRC CLI) on page 85•



Configuring Authentication for SNMPv3 Users (SRC CLI)

For SNMPv3 users, you can configure the authentication type and the password used for

authentication. The type of authentication can be Message Digest 5 (MD5) or Secure

Hash Algorithm (SHA). By default, authentication is not configured for SNMPv3 users.

To configure authentication for SNMPv3 users:


authentication type.

To configure MD5 authentication:

[edit]user@host# set snmp v3 usm local-engine user username authentication-md5

To configure SHA authentication:

[edit]user@host# set snmp v3 usm local-engine user username authentication-sha

2. Specify the authentication password.

To configure authentication password for MD5:

[edit]


Chapter 9: Configuration Tasks for SNMPv3 Users Access

user@host# set snmp v3 usm local-engine user username authentication-md5authentication-password

To configure authentication password for SHA:

[edit]user@host# set snmp v3 usm local-engine user username authentication-shaauthentication-password

The password must contain at least eight characters.




• Configuring Authentication (C-Web Interface) on page 54



Configuring Authentication (C-Web Interface)

To configure the authentication type for SNMPv3 users:


2. To configure MD5 authentication, from the side pane, expand the name of the user,

and click Authentication MD5.

3. To configure SHA authentication, from the side pane, expand the name of the user,

and click Authentication SHA.

4. Specify the authentication password as described in the Help text in the main pane,

and then click Create.

The password must be at least eight characters.


Configuring Encryption (C-Web Interface) on page 55•



• Defining Access Privileges for an SNMP Group (C-Web Interface) on page 67

Configuring Encryption for SNMPv3 Users (SRC CLI)

Before you configure encryption, you must configure the authentication type. See

“Configuring Authentication for SNMPv3 Users (SRC CLI)” on page 53. You need to use

the authentication type and encryption when you query MIB values. By default, if you do

not configure encryption for an SNMPv3 user, all clients are allowed access to all MIB

values. To restrict access to MIB values and thereby increase security, you need to

configure encryption.



To configure encryption for SNMPv3 users:


encryption.

To configure AES encryption:

user@host# edit snmp v3 usm local-engine user username privacy-aes

To configure DES encryption:

user@host# edit snmp v3 usm local-engine user username privacy-des

2. Specify the privacy password.

user@host# set privacy-password privacy-password

The password must contain at least eight characters.





Configuring Encryption (C-Web Interface)

Before you configure encryption, you must configure the authentication type. See

“Configuring Authentication (C-Web Interface)” on page 54.

To configure encryption for SNMPv3 users:


2. To configure AES encryption, from the side pane, expand the name of the user, and

click Privacy AES.

3. To configure DES encryption, from the side pane, expand the name of the user, and

click Privacy DES.

4. Specify the authentication password as described in the Help text in the main pane,

and then click Create.

The password must be at least eight characters.






Chapter 9: Configuration Tasks for SNMPv3 Users Access



CHAPTER 10

Configuration Tasks for CommunitiesAccess


• Configuring Access Control for Communities (C-Web Interface) on page 58

• Configuring Access Control for the VACM (SRC CLI) on page 59

• Configuring Access Control for the VACM (C-Web Interface) on page 60

• Associating Security Names with a Community (SRC CLI) on page 60

• Associating Security Names with a Community (C-Web Interface) on page 62

• Defining Named Views (SRC CLI) on page 62

• Defining Named Views (C-Web Interface) on page 63

Configuring Access Control for Communities (SRC CLI)

An SNMP community string is a text string that functions as a password. SNMP uses the

community string to authenticate messages that are transmitted between the SNMP

manager and the SNMP agent. The community string is included in every packet that is

transmitted between the SNMP manager and the SNMP agent. You can configure SNMP

community strings for SNMPv1 and SNMPv2c users only. SNMPv3 users do not use

community strings.

Use the following configuration statements to configure community strings for traditional

access control:

snmp community community {authorization (read-only|read-write);clients clients;oid oid;

}

To configure community strings:


community string. Community names must be unique.

[edit]user@host# edit snmp community community


2. (Optional) Specify the authorization level.

To specify read-only access:

[edit snmp community community]user@host# set authorization read-only

To specify read-and-write access:

[edit snmp community community]user@host# set authorization read-write

3. Specify the IP address or subnet of the SNMP client hosts that are authorized to use

this community.

[edit snmp community community]user@host# set clients clients

By default, all clients are allowed.

4. (Optional) Specify the object identifier used to represent a subtree of MIB objects to

which access is allowed.

[edit snmp community community]user@host# set oid oid


[edit snmp community community] user@host# show




Configuring Access Control for Communities (C-Web Interface)

To configure community strings:

1. Click Configure>SNMP.

2. From the Create new list, select Community.

3. Enter a name for the new Community in the dialog box, and click OK.

4. From the side pane, expand the name of the community, enter information as described

in the Help text in the main pane, and then click Apply.


Configuring Access Control for Communities (SRC CLI) on page 57•



• Assigning Security Names to Groups (C-Web Interface) on page 68




Configuring Access Control for the VACM (SRC CLI)

Use the view-based access control model (VACM) to restrict access to particular branches

of a subtree of MIB objects by excluding or including a MIB variable. If you want to include

system-related MIB values but not the system name and system contact MIB OID, then

create a view by excluding the system name and system contact MIB OID. Then the

system name and system contact MIB OID are not displayed.

To configure access control for a view-based access control model (VACM):

NOTE: You can also associate anSNMPviewwith a community by using thisconfiguration.

1. Define a named view.

See “Defining Named Views (SRC CLI)” on page 62.

2. Map an SNMPv1 or SNMPv2c community name to a security name.

See “Associating Security Names with a Community (SRC CLI)” on page 60.

3. Create an SNMPv3 user.

See “Creating SNMPv3 Users” on page 51.

4. Map from a group of users or communities to a view.

See “Defining Access Privileges for an SNMP Group (SRC CLI)” on page 65.

5. Map a security name into a named group.

See “Assigning Security Names to Groups (SRC CLI)” on page 67.


[edit snmp v3]

snmp-community 123 {address 10.212.10.2;community-name TEST-Community;security-name testSecurity;

}usm {local-engine {user testUser;

}}vacm {access {group testGroup {default-context-prefix {security-model usm {security-level none {


Chapter 10: Configuration Tasks for Communities Access

read-view testView;write-view none;

}}

}}

}security-to-group {security-model usm {security-name testUser {group-name testGroup;

}}security-model v2c {security-name testSecurity {group-name testGroup;

}}

}}




Configuring Access Control for the VACM (C-Web Interface)

To configure the access control for the view-based access control model (VACM):

1. Map an SNMPv1 or SNMPv2c community name to a security name.

See “Associating Security Names with a Community (C-Web Interface)” on page 62.

2. Define a named view.

See “Defining Named Views (C-Web Interface)” on page 63.

3. Map from a group of users or communities to a view.

See “Defining Access Privileges for an SNMP Group (C-Web Interface)” on page 67.

4. Map a security name into a named group.

See “Assigning Security Names to Groups (C-Web Interface)” on page 68.


Configuring Access Control for the VACM (SRC CLI) on page 59•


Associating Security Nameswith a Community (SRC CLI)

For SNMPv1 or SNMPv2c packets, you must assign security names to groups at the [edit

snmpv3 vacmsecurity-to-group] hierarchy level and you must associate a security name

with an SNMP community.



Use the following configuration statements to configure SNMPv1 or SNMPv2c

communities for the VACM:

snmp v3 snmp-community community-index {community-name community-name;security-name security-name;address address;

}

To configure the community:


community.

[edit]user@host# edit snmp v3 snmp-community community-index

Use a unique index that identifies an SNMP community.

2. (Optional) Specify the community string for the SNMPv1 or SNMPv2c community.

[edit snmp v3 snmp-community community-index]user@host# set community-name community-name

If a community name is not specified, the community index is used.

3. Specify the VACM security name to associate with the community string.

[edit snmp v3 snmp-community community-index]user@host# set security-name security-name

4. (Optional) Specify the IP address or subnet of the SNMP clients that are authorized

to use this community.

[edit snmp v3 snmp-community community-index]user@host# set address address

If an address is not specified, all clients are authorized to use the community.


[edit snmp v3 snmp-community community-index]user@host# show



• Defining Access Privileges for an SNMP Group (SRC CLI) on page 65




Associating Security Nameswith a Community (C-Web Interface)

For SNMPv1 or SNMPv2c packets, you must assign security names to groups at the [edit

snmpv3vacmsecurity-to-group]hierarchy level, and you must associate a security name

with an SNMP community.

To configure the community:

1. Click Configure>SNMP>V3.

2. From the Create new list, select SNMPCommunity.

3. Enter a name for the new SNMP Community in the dialog box, and click OK.

4. From the side pane, expand the name of the SNMP community, enter information as

described in the Help text in the main pane, and then click Apply.


Associating Security Names with a Community (SRC CLI) on page 60•

• Defining Named Views (C-Web Interface) on page 63


Defining Named Views (SRC CLI)

A named view identifies a group of MIB objects to which access is enabled. Each MIB

object in a named view contains a common object identifier (OID) prefix that represents

a subtree of MIB objects for the view.

Use the following configuration statements to define named views:

snmp view view-name ...snmp view view-name oid oid {(include|exclude);

}

To configure named views:


named views.

[edit]user@host# edit snmp view view-name

2. Specify the object identifier (OID) that represents a subtree of MIB objects for the

view and whether the OID is included in or excluded from the view.

To include the OID in the view:

[edit snmp view view-name]user@host# set oid oid include

To exclude the OID from the view:



[edit snmp view view-name]user@host# set oid oid exclude


[edit snmp view view-name]

user@host# show

test_view {oid 1.3.6.1.2.1.1.4 {exclude;

}oid 1.3.6.1.2.1.1.5 {exclude;

}oid system {include;

}}


Defining Named Views (C-Web Interface) on page 63•

• Creating SNMPv3 Users on page 51


Defining Named Views (C-Web Interface)

To configure named views:

1. Click Configure, and expand SNMP.

2. From the Create new list, select View.

3. Enter a name for the new View in the dialog box, and click OK.

4. From the side pane, expand the name of the view,

5. From the Create new list, select OID.

6. Enter a name for the new OID in the dialog box, and click OK.

The View OID pane appears.









CHAPTER 11

Configuration Tasks for SNMP GroupsAccess

• Defining Access Privileges for an SNMP Group (SRC CLI) on page 65


• Assigning Security Names to Groups (SRC CLI) on page 67


Defining Access Privileges for an SNMPGroup (SRC CLI)

Use the following configuration statements to define access privileges for SNMP groups:

snmp v3 vacm access group group-name ...snmp v3 vacm access group group-name default-context-prefix security-model(any|v1|v2c|usm) ...

snmp v3 vacm access group group-name default-context-prefix security-model(any|v1|v2c|usm) security-level (authentication|none|privacy) {read-view read-view;write-viewwrite-view;

}

To configure MIB views with a group for the VACM:


VACM group.

[edit]user@host# edit snmp v3 vacm access group group-name

The group name is the name for a collection of SNMP security names that belong to

the same SNMP access policy.

2. Specify the security model for access privileges.

[edit snmp v3 vacm access group group-name]user@host# set default-context-prefix security-model (any|v1|v2c|usm)

To specify any security model:

user@host# set default-context-prefix security-model any


To specify the SNMPv1 security model:

user@host# set default-context-prefix security-model v1

To specify the SNMPv2c security model:

user@host# set default-context-prefix security-model v2c

To specify the SNMPv3 user-based security model (USM):

user@host# set default-context-prefix security-model usm

3. Specify the security level for access privileges.

[edit snmp v3 vacm access group group-name]user@host#setdefault-context-prefixsecurity-model (any|v1|v2c|usm)security-level(authentication|none|privacy)

To specify a security level that provides authentication but no encryption:

user@host#setdefault-context-prefixsecurity-model (any|v1|v2c|usm)security-levelauthentication

To specify a security level that provides no authentication and no encryption:

user@host#setdefault-context-prefixsecurity-model (any|v1|v2c|usm)security-levelnone

For SNMPv1 or SNMPv2c access, specify none as the security level.

To specify a security level that provides authentication and encryption:

user@host#setdefault-context-prefixsecurity-model (any|v1|v2c|usm)security-levelprivacy

4. (Optional) Specify the view used for SNMP read access. You must specify the read-view

option or the write-view option.

[edit snmp v3 vacm access group group-name default-context-prefix security-model(any|v1|v2c|usm) security-level (authentication|none|privacy)]

user@host# set read-view read-view

5. (Optional) Specify the view used for SNMP write access. You must specify the

read-view option or the write-view option.

[edit snmp v3 vacm access group group-name default-context-prefix security-model(any|v1|v2c|usm) security-level (authentication|none|privacy)]

user@host# set write-viewwrite-view







Defining Access Privileges for an SNMPGroup (C-Web Interface)

To configure MIB views with a group for the VACM:

1. Click Configure, and expand SNMP>V3>VACM>Access.

2. From the Create new list, select Group.

3. Enter a name for the new Group in the dialog box, and click OK.

The group name is the name for a collection of SNMP security names that belong to

the same SNMP access policy.

4. From the side pane, expand the name of the group, click on Default Context Prefix,

5. From the Create New box, select the Security Model for access privileges.

6. From the Create New box, select the Security Level for access privileges.

The Security pane appears.



Defining Access Privileges for an SNMP Group (SRC CLI) on page 65•



Assigning Security Names to Groups (SRC CLI)

For SNMPv1 or SNMPv2c packets, you must assign security names to groups and you

must associate a security name with an SNMP community at the [edit snmp v3

snmp-community community-index ] hierarchy level.

Use the following configuration statements to assign security names to groups:

snmp v3 vacm security-to-group security-model (v1|v2c|usm) ...snmpv3vacmsecurity-to-groupsecurity-model (v1|v2c|usm)security-namesecurity-name{group-name group-name;

}

To map security names to groups for the VACM:


security model for a group.

user@host# edit snmp v3 vacm security-to-group security-model (v1|v2c|usm)

To specify the SNMPv1 security model:

user@host# edit snmp v3 vacm security-to-group security-model v1

To specify the SNMPv2c security model:


Chapter 11: Configuration Tasks for SNMP Groups Access

user@host# edit snmp v3 vacm security-to-group security-model v2c

To specify the SNMPv3 user-based security model (USM):

user@host# edit snmp v3 vacm security-to-group security-model usm

2. Specify the security name.

user@host# edit snmp v3 vacm security-to-group security-model (v1|v2c|usm)security-name security-name

If the security model is USM, the security name is the username configured at the [edit

snmp v3 usm local-engine user] hierarchy level.

3. Specify the group to which the security name is assigned.

[edit snmp v3 vacm security-to-group security-model (v1|v2c|usm) security-namesecurity-name]

user@host# set group-name group-name



• Associating Security Names with a Community (SRC CLI) on page 60

Assigning Security Names to Groups (C-Web Interface)

For SNMPv1 or SNMPv2c packets, you must assign security names to groups and you

must associate a security name with an SNMP community.

To map security names to groups for the VACM:

1. Click Configure, and expand SNMP>V3>VACM.

2. Expand the desiredSecurityModel and desired Security Name, enter information as

described in the Help text in the main pane, and then click Apply.







CHAPTER 12

Configuration Tasks for SNMPNotifications

• Configuring Notification Targets (SRC CLI) on page 69

• Configuring Notification Targets (C-Web Interface) on page 70

Configuring Notification Targets (SRC CLI)

Use the following configuration statements to configure notification targets:

snmp notify target target-name {address address;port port;community community;type (trapv1|trapv2|inform);

}

To configure notification targets:


notification target.

[edit]user@host# edit snmp notify target target-name

Specify the notification target name.

2. Specify the IPv4 or IPv6 address of the system to receive notifications.

[edit snmp notify target target-name]user@host# set address address

3. (Optional) Specify the SNMP trap port number.

[edit snmp notify target target-name]user@host# set port port

4. Specify the community string used when sending traps.

[edit snmp notify target target-name]user@host# set community community


5. Specify the notification types as traps or informs. Traps are unconfirmed notifications.

Informs are confirmed notifications.

To specify the notification type as an SNMPv1 trap:

[edit snmp notify target target-name]user@host# set type trapv1

To specify the notification type as an SNMPv2 trap:

[edit snmp notify target target-name]user@host# set type trapv2

To specify the notification type as an SNMPv2 inform:

[edit snmp notify target target-name]user@host# set type inform


[edit snmp notify target target-name]user@host# show


Configuring Notification Targets (C-Web Interface) on page 70•


Configuring Notification Targets (C-Web Interface)

To configure notification targets:

1. Click Configure > SNMP>Notify.

The Notify pane appears.

2. From the Create New box, select Target, enter the name of the target, and click OK.

The Target pane appears.



• Configuring Notification Targets (SRC CLI) on page 69

• Configuring Performance Traps (C-Web Interface) on page 72



CHAPTER 13

Configuration Tasks for SNMP Traps




• Configuring Event Traps (C-Web Interface) on page 73

• Defining SRC ACP Congestion Point Usage Trap Thresholds (SRC CLI) on page 73

Configuring Performance Traps (SRC CLI)

Use the following configuration statements to configure performance traps:

snmp notify alarm category category-name ...snmp notify alarm category category-name alarm alarm-name {interval interval;critical critical;majormajor;minorminor;

}

To configure performance traps:


type of performance trap.

[edit]user@host# edit snmp notify

2. Specify the type of trap and the trap name.

[edit snmp notify]user@host# set alarm category category-name alarm alarm-name

You can select from the list of trap types and their associated traps or create new

traps.

3. (Optional) Specify the interval at which the variable associated with the trap is polled.

[edit snmp notify alarm category category-name alarm alarm-name]user@host# set interval interval

4. Specify the threshold above which a critical alarm is generated.


[edit snmp notify alarm category category-name alarm alarm-name]user@host# set critical critical

5. Specify the threshold above which a major alarm is generated.

[edit snmp notify alarm category category-name alarm alarm-name]user@host# setmajormajor

6. Specify the threshold above which a minor alarm is generated.

[edit snmp notify alarm category category-name alarm alarm-name]user@host# setminorminor


Configuring Event Traps (SRC CLI) on page 72•

• Configuration Statements for the SNMP Traps on page 99




Configuring Performance Traps (C-Web Interface)

To configure performance traps:

1. Click Configure > SNMP>Notify, and expand Alarm.

2. From the Create New box, select the category and associated traps, and click OK.

The Alarm pane appears.



Configuring Performance Traps (SRC CLI) on page 71•

• Configuring Event Traps (C-Web Interface) on page 73


• For information about various SRC performance traps, see JPS Performance Traps on

page 30

Configuring Event Traps (SRC CLI)

Use the following configuration statements to configure event traps:

snmp notify event category category-name ...snmp notify event category category-name event event-name ...

To configure event traps:




type of event trap.

[edit]user@host# edit snmp notify

2. Specify the type of trap and the trap name.

[edit snmp notify]user@host# set event category category-name event event-name

You can select from the list of trap types and their associated traps or create new

traps.






Configuring Event Traps (C-Web Interface)

To configure event traps:

1. Click Configure > SNMP > Notify, and expand Event.

2. From the Create New box, select the category and the category name, and click OK.

The Category pane appears.

3. From the Create New box, select the event and click OK,

The Event pane appears.



Configuring Event Traps (SRC CLI) on page 72•



• For information about event traps, see Event Traps on page 13

Defining SRC ACP Congestion Point Usage Trap Thresholds (SRC CLI)

Four alarms are used for the ACP congestion point usage trap (acpCPUsage): critical,

major, minor, and clear trap. Critical, major, and minor traps are sent when the

corresponding thresholds are exceeded. The clear trap is sent when the previous event

is cleared. When the sampled value falls below a higher threshold but is still above a

lower threshold, a clear trap is sent followed by a trap corresponding to the lower

threshold.


Chapter 13: Configuration Tasks for SNMP Traps

Objects sent with the traps include the congestion point ID (congestion point DN plus

instance ID, which is optional), the CP’s upstream bandwidth, downstream bandwidth,

upstream bandwidth in use, and downstream bandwidth in use.

To avoid configuring thresholds for every congestion point, the threshold is defined as a

percentage of in-use bandwidth, which is calculated with the following expression:

used bandwidth/(total bandwidth-background bandwidth)

Where, total bandwidth is usually the provisioned bandwidth of the congestion point but

can be overridden if the ACP receives an update through L2C or RemoteUpdateInterface.

A congestion point’s upstream bandwidth and downstream bandwidth are evaluated

with this expression and compared to the configured threshold separately. If either the

upstream or downstream bandwidth of the congestion point exceeds a threshold, a trap

corresponding to the threshold is generated. A clear trap is sent only when the usage of

both the upstream and downstream bandwidth fall below the threshold. The same trap

is not sent multiple times consecutively.

Use the following configuration statements to configure the acpCPUsage trap:

shared acp configuration snmp {selector [selector...];critical-threshold critical-threshold;major-thresholdmajor-threshold;minor-thresholdminor-threshold;

}

To configure the acpCPUsage trap:


acpCPUsage trap.

user@host# edit shared acp configuration snmp

2. (Optional) Configure Java regular expressions to match against congestion point DN.

A congestion point is chosen for notification if its DN matches any one of the

expressions. If not specified, all congestion points are selected.

[edit shared acp configuration snmp]user@host# set selector selector;

3. Configure the critical threshold for the congestion point usage trap. The threshold is

a percentage of used bandwidth out of the total accessible bandwidth, which is the

current bandwidth minus the background bandwidth of a congestion point.

[edit shared acp configuration snmp]user@host# set critical-threshold critical-threshold ;

4. Configure the major threshold for the congestion point usage trap. The threshold is a

percentage of used bandwidth out of the total accessible bandwidth, which is the


[edit shared acp configuration snmp]



user@host# setmajor-thresholdmajor-threshold ;

5. Configure the minor threshold for the congestion point usage trap. The threshold is a

percentage of used bandwidth out of the total accessible bandwidth, which is the


[edit shared acp configuration snmp]user@host# setminor-thresholdminor-threshold ;







Chapter 13: Configuration Tasks for SNMP Traps



CHAPTER 14

Tasks for Decoding Trap Numbers



Decoding Trap Numbers for Raised Trap Actions

To decode a trap number for raised trap actions:

• Use the following equation:

Trap number = Trap ID * 10 + severity

For example, if the trap number is 43, then the trap ID is 4 (saeServiceActivations) and

the severity is 3 (MINOR). Therefore, a trap number of 43 means that a MINOR event has

occurred for the saeServiceActivations trap.


Decoding Trap Numbers for Clear Trap Actions on page 77•




Decoding Trap Numbers for Clear Trap Actions

To decode a trap number for clear trap actions:

• Use the following equation:

Trap number = Trap ID * 10

For example, if the trap number is 250, then the trap ID is 25 (saeAccPendingRequests).

Therefore, a trap number of 250 means that the saeAccPendingRequests alarm has

been cleared.









CHAPTER 15

Configuration Tasks for Custom SNMPMonitors

• Configuring SNMP Custom Monitors (C-Web Interface) on page 79


• Defining an Alarm for an SNMP Monitor That Compares Object Values (SRC

CLI) on page 82

• Defining an Alarm to Monitor the Status of an Object (SRC CLI) on page 83

• Defining an Alarm for an SNMP Monitor That Compares Values Against Thresholds

(SRC CLI) on page 83

• Defining a Discontinuity Check to Validate Delta Values (SRC CLI) on page 84


• Defining Events for Which SNMP Sends Notifications (SRC CLI) on page 85

• Defining Events That Set Values for SNMP MIB Objects (SRC CLI) on page 86

Configuring SNMPCustomMonitors (C-Web Interface)

You can create custom SNMP monitors to detect changes in MIB objects.

To create custom SNMP monitors:

1. Click Configure, expand SNMP, and click Monitor.

The Monitor pane appears.

2. From the Create new list, select Alarm.

3. Type a name for the new alarm in the dialog box, and click OK.

The alarm name appears in the side pane and the SNMP pane.

4. Enter alarm properties as described in the Help text in the Main pane, and click OK.

5. Configure a test condition for the alarm.

a. In the side pane, under the alarm you are configuring select a test condition:Booleantest, Existence Test, or Threshold Test.

b. (Optional) If you configured a Boolean or threshold test, and set the sample type

as delta-value, you can select Delta Discontinuity Check to validate delta values.


c. Enter test properties as described in the Help text in the Main pane, and click OK.

6. In the side pane, select Monitor again.

The Monitor pane appears.

7. From the Create new list, select Event.

8. Type a name for the new event in the dialog box, and click OK.

9. In the side pane, under the event that you created, expand the event.

10. ClickNotification and enter notification properties as described in the Help text in the

Main pane, and click OK.

Or

Click SNMPSet and enter set properties as described in the Help text in the Main

pane, and click OK.

11. (Optional) In the left pane, select Monitor; then in the Main pane enter an SNMP v3

security name.


SNMP Monitoring on C Series Controllers on page 7•


Configuring an SNMPAlarm on a C Series Controller (SRC CLI)

You can configure SNMP to establish alarms for custom monitors.

NOTE: Configure only onemonitor test at a time.

To configure an SNMP alarm:

1. Specify an SNMP username.

See “Configuring an SNMPv3 Security Name for SNMP Monitoring (SRC CLI)” on

page 85.

2. From configuration mode, access the configuration statements that configures an

alarm. For example:

[edit]user@host# edit snmpmonitor alarm saeHeapUsage

where saeHeapUsage is the name of the alarm.

3. Specify the number of seconds between which SNMP samples the value of an object.

For example:

[edit snmpmonitor alarm saeHeapUsage]user@host# set interval 60

4. Specify whether to sample the actual value of the object or the difference between

two values. For example, to use the actual of the object:



[edit snmpmonitor alarm saeHeapUsage]user@host# set sample-type absolute-value

If you set the sample type to delta-value, you can configure a discontinuity check.

See “Defining a Discontinuity Check to Validate Delta Values (SRC CLI)” on page 84.

5. (Optional) Indicate that an alarm not be sent when the alarm is initially activated.

[edit snmpmonitor alarmsaeHeapUsage]user@host# set ignore-startup-alarm

6. (Optional) Specify the name of the event to be generated in response to an alarm

condition. For example:

[edit snmpmonitor alarm saeHeapUsage]user@host# set event saeHeapUsageEvent

7. Specify the name or object identifier (OID) of the MIB variable to be monitored. For

example:

[edit snmpmonitor alarm saeHeapUsage]user@host# set variable juniSdxSaeHeapUsed.0

8. (Optional) Specify whether to monitor the SNMP object instance identified by a

variable attribute. To monitor the SNMP object instance specified by the variable

attribute:

[edit snmpmonitor alarm saeHeapUsage]user@host# set strict-oid

Do not enable the strict-oidoption when you monitor a column of an SNMP MIB table.

An alarm for a column monitors the column on all entries of the table. If an entry for

an object in the column passes an alarm test, an event is generated for that object.

9. Configure a Boolean, existence, or threshold test for the alarm.


Defining an Alarm for an SNMP Monitor That Compares Object Values (SRC CLI) on

page 82

•







Chapter 15: Configuration Tasks for Custom SNMP Monitors

Defining an Alarm for an SNMPMonitor That Compares Object Values (SRC CLI)

You can configure a monitor to compare a sample value to a specified value or range of

values by using one of the following types of comparisons:

• equal

• unequal

• less

• less-or-equal

• greater

• greater-or-equal


Before you define an alarm type, configure the associated SNMP alarm.

See “Configuring an SNMP Alarm on a C Series Controller (SRC CLI)” on page 80.

To configure a monitor to compare a sample to a specified value or range of values:

1. From configuration mode, access the configuration statements that configure SNMP

monitoring for a Boolean test. For example:

[edit]user@host# edit snmpmonitor alarm saeHeapUsage boolean-test

where saeHeapUsage is the name of the alarm.

2. Specify the type of Boolean test. For example:

[edit snmpmonitor alarm saeHeapUsage boolean-test]user@host# set comparison greater

3. Define the value that the test uses. For example:

[edit snmpmonitor saeHeapUsage boolean-test]user@host# value 14000000


Defining an Alarm to Monitor the Status of an Object (SRC CLI) on page 83•








Defining an Alarm toMonitor the Status of an Object (SRC CLI)

You can configure a monitor to identify when a MIB object appears, disappears, or changes

value. If the test criteria are met, the test is considered to be successful.




To configure an alarm to monitor the status of an object:

• Specify the type of alarm: present, absent, or changed. For example for an alarm named

existence-alarm:

[edit snmpmonitor alarm existence-alarm existence-test]user@host# set type present



page 82

•






Defining an Alarm for an SNMPMonitor That Compares Values Against Thresholds(SRC CLI)

You can configure a monitor to compare a sample value for a MIB object to a threshold

encountered as the value rises and a threshold encountered as the value falls.




To configure an alarm for a monitor that compares a sample value to an upper threshold

value and a lower threshold value:

1. Define the upper threshold against which to compare a rising sample value. For

example:



[edit snmpmonitor alarm thresholds threshold-test]user@host# set rising-threshold 2

2. Define the lower threshold against which to compare a falling sample value. For

example:

[edit snmpmonitor alarm threshold-alarm]user@host# set falling-threshold 1



page 82

•





Defining a Discontinuity Check to Validate Delta Values (SRC CLI)

You can configure a monitor to use a discontinuity check to prevent sending false alarms

when the value of the monitored object is reset between two samples.

Use a discontinuity check when the sampling type for a monitor is delta-value and the

test type is Boolean or threshold. You define a variable, called a discontinuity marker (a

MIB object used to validate the delta, or difference, between values). Typically, the marker

object is of the TimeTicks, DateAndTime, or Timestamp type.

To define a discontinuity check:

1. Configure an SNMP alarm with the sample type set to delta-value.


2. From configuration mode, access the configuration statements that configures a

discontinuity check. For example, for an alarm named ifErrorsDelta:

[edit]user@host# edit snmpmonitor alarm ifErrorsDelta delta-discontinuity-check

3. Specify the name or object identifier (OID) of the discontinuity marker. For example:

[edit snmpmonitor alarm sequence-check ifErrorsDelta delta-discontinuity-check]user@host# set variable ifTable.ifEntry.ifLastChange


Defining Events That Set Values for SNMP MIB Objects (SRC CLI) on page 86•






Configuring an SNMPv3 Security Name for SNMPMonitoring (SRC CLI)

To configure an SNMPv3 security name to access a monitored MIB object:


monitoring.

[edit]user@host# edit snmpmonitor

2. Specify an SNMPv3 security name.

[edit snmpmonitor]user@host# set security-name your-security-name


Configuring an SNMP Alarm on a C Series Controller (SRC CLI) on page 80•



Defining Events forWhich SNMPSends Notifications (SRC CLI)

NOTE: Do not define an event notification and an SNMP set for the sameevent.

To define an event for which SNMP sends a notification:


event notification and provide a name for the event. For example:

[edit]user@host# edit snmpmonitor event routerErrorEvent notification

2. Specify the object identifier (OID) object identifier of the notification object. For

example:

[edit snmpmonitor event routerErrorEvent notification]user@host# set oid juniSdxMibs.24.2.1

3. (Optional) Allow wildcards in the OID to include instances of subidentifiers that

correspond to the monitored object. For example:

[edit snmpmonitor event routerErrorEvent notification notification]user@host# set wildcarded-object [juniSaeRouterMsgErrors,juniSaeRouterMsgTimeouts]

Alternatively, you can configure event notification to use a specific OID.


Configuring an SNMP Alarm on a C Series Controller (SRC CLI) on page 80•






Defining Events That Set Values for SNMPMIB Objects (SRC CLI)

You can configure SNMP to set the value of a MIB object in response to an SNMP event.

NOTE: Do not define an event notification and an SNMP set for the sameevent.

To define an event that sets the value for a MIB variable in response to an SNMP event:

1. From configuration mode, access the configuration statements that configure an

SNMP set for an event.

[edit]user@host# edit snmpmonitor event event-name snmp-set

2. Specify the object identifier (OID) of the MIB variable to set.

[edit snmpmonitor event event-name snmp-set]user@host# set oidOID

3. Specify the value for the object.

[edit snmpmonitor event event-name snmp-set]user@host# set value value

4. (Optional) Specify whether the software monitors only the OID specified by the

variable option. If you do not set this option, the index of the object triggering the alarm

is appended to the variable to be set.

[edit snmpmonitor event event-name snmp-set]user@host# set strict-oid








CHAPTER 16

Configuration Tasks for SNMP ChassisAlarms


• Defining Alarm Thresholds for Battery Voltage Sensors on page 88

• Defining Alarm Thresholds for CPU Sensors on page 88

• Defining Alarm Thresholds for Fan Speed Sensors on page 91

• Defining Alarm Thresholds for System Temperature Sensors on page 91

• Defining Alarm Thresholds for Voltage Sensors on page 92

Configuring SNMPChassis Alarms (SRC CLI)

To configure SNMP chassis alarms:

1. Set the editing level for the CLI to expert.

user@host> set cli level expert


chassis alarms.

[edit]user@host# edit snmpmonitor chassis-alarm

3. (Optional) Disable all chassis alarms. You cannot delete the chassis alarms.

[edit snmpmonitor chassis-alarm]user@host# set disable

4. (Optional) Specify the number of seconds between which SNMP samples the value

of an object. For example:

[edit snmpmonitor chassis-alarm]user@host# set interval 60


Defining Alarm Thresholds for Battery Voltage Sensors on page 88•

• Defining Alarm Thresholds for CPU Sensors on page 88

• Defining Alarm Thresholds for Fan Speed Sensors on page 91

• Defining Alarm Thresholds for System Temperature Sensors on page 91



Defining Alarm Thresholds for Battery Voltage Sensors

To configure SNMP chassis alarm thresholds for battery voltage sensors:



2. From configuration mode, access the configuration statement that defines the

thresholds for battery voltage sensors.

[edit]user@host# edit snmpmonitor chassis-alarm battery-voltage

3. (Optional) Specify the lower threshold for the minor alarm. For example:

[edit snmpmonitor chassis-alarm battery-voltage]user@host# set below-minor 3024

4. (Optional) Specify the lower threshold for the major alarm. For example:

[edit snmpmonitor chassis-alarm battery-voltage]user@host# set below-major 3008

5. (Optional) Specify the lower threshold for the critical alarm. For example:

[edit snmpmonitor chassis-alarm battery-voltage]user@host# set below-critical 2992

6. (Optional) Specify the upper threshold for the minor alarm. For example:

[edit snmpmonitor chassis-alarm battery-voltage]user@host# set over-minor 3744

7. (Optional) Specify the upper threshold for the major alarm. For example:

[edit snmpmonitor chassis-alarm battery-voltage]user@host# set over-major 3760

8. (Optional) Specify the upper threshold for the critical alarm. For example:

[edit snmpmonitor chassis-alarm battery-voltage]user@host# set over-critical 3776


Configuring SNMP Chassis Alarms (SRC CLI) on page 87•


Defining Alarm Thresholds for CPU Sensors

• Defining Alarm Thresholds for CPU Core Voltage Sensors on page 89

• Defining Alarm Thresholds for CPU DIMM Voltage Sensors on page 89

• Defining Alarm Thresholds for CPU Temperature Sensors on page 90



Defining Alarm Thresholds for CPU Core Voltage Sensors

To configure SNMP chassis alarm thresholds for CPU core voltage sensors:




thresholds for CPU core voltage sensors.

[edit]user@host# edit snmpmonitor chassis-alarm cpu-core-voltage


[edit snmpmonitor chassis-alarm cpu-core-voltage]user@host# set below-minor 1030


[edit snmpmonitor chassis-alarm cpu-core-voltage]user@host# set below-major 1020


[edit snmpmonitor chassis-alarm cpu-core-voltage]user@host# set below-critical 1008


[edit snmpmonitor chassis-alarm cpu-core-voltage]user@host# set over-minor 1728


[edit snmpmonitor chassis-alarm cpu-core-voltage]user@host# set over-major 1740


[edit snmpmonitor chassis-alarm cpu-core-voltage]user@host# set over-critical 1752

Defining Alarm Thresholds for CPUDIMMVoltage Sensors

To configure SNMP chassis alarm thresholds for CPU DIMM voltage sensors:




thresholds for CPU DIMM voltage sensors.

[edit]user@host# edit snmpmonitor chassis-alarm cpu-dimm-voltage


[edit snmpmonitor chassis-alarm cpu-dimm-voltage]user@host# set below-minor 2292


Chapter 16: Configuration Tasks for SNMP Chassis Alarms


[edit snmpmonitor chassis-alarm cpu-dimm-voltage]user@host# set below-major 2280


[edit snmpmonitor chassis-alarm cpu-dimm-voltage]user@host# set below-critical 2268


[edit snmpmonitor chassis-alarm cpu-dimm-voltage]user@host# set over-minor 2832


[edit snmpmonitor chassis-alarm cpu-dimm-voltage]user@host# set over-major 2844


[edit snmpmonitor chassis-alarm cpu-dimm-voltage]user@host# set over-critical 2856

Defining Alarm Thresholds for CPU Temperature Sensors

To configure SNMP alarm thresholds for CPU temperature sensors:




thresholds for the CPU temperature sensors.

[edit]user@host# edit snmpmonitor chassis-alarm cpu-temperature


[edit snmpmonitor chassis-alarm cpu-temperature]user@host# setminor 76


[edit snmpmonitor chassis-alarm cpu-temperature]user@host# setmajor 78


[edit snmpmonitor chassis-alarm cpu-temperature]user@host# set critical 80






Defining Alarm Thresholds for Fan Speed Sensors

To configure SNMP chassis alarm thresholds for fan speed sensors:




chassis alarm thresholds for fan speed sensors.

[edit]user@host# edit snmpmonitor chassis-alarm fan-speed

3. (Optional) Specify the lower threshold for the minor alarm in revolutions per minute.

For example:

[edit snmpmonitor chassis-alarm fan-speed]user@host# setminor 540

4. (Optional) Specify the lower threshold for the major alarm in revolutions per minute.

For example:

[edit snmpmonitor chassis-alarm fan-speed]user@host# setmajor 405

5. (Optional) Specify the lower threshold for the critical alarm in revolutions per minute.

For example:

[edit snmpmonitor chassis-alarm fan-speed]user@host# set critical 270




Defining Alarm Thresholds for System Temperature Sensors

To configure SNMP chassis alarm thresholds for system temperature sensors:




thresholds for system temperature sensors.

[edit]user@host# edit snmpmonitor chassis-alarm system-temperature


[edit snmpmonitor chassis-alarm system-temperature]user@host# setminor 76


[edit snmpmonitor chassis-alarm system-temperature]



user@host# setmajor 78


[edit snmpmonitor chassis-alarm system-temperature]user@host# set critical 80




Defining Alarm Thresholds for Voltage Sensors

You can configure alarm thresholds for these voltage sensors:

• 1.8V

• 3.3V

• 5V

• 12V

• –12V

To configure SNMP chassis alarm thresholds for voltage sensors:




thresholds for voltage sensors.

[edit]user@host# edit snmpmonitor chassis-alarm voltage-sensor

For example:

[edit]user@host# edit snmpmonitor chassis-alarm voltage-1.8v

[edit]user@host# edit snmpmonitor chassis-alarm voltage-3.3v

[edit]user@host# edit snmpmonitor chassis-alarm voltage-5v

[edit]user@host# edit snmpmonitor chassis-alarm voltage-12v

[edit]user@host# edit snmpmonitor chassis-alarm voltage-negative12v

NOTE: The voltage-negative12v option is not available on the C3000 and

C5000 Controllers.




[edit snmpmonitor chassis-alarm voltage-1.8v]user@host# set below-minor 1644


[edit snmpmonitor chassis-alarm voltage-1.8v]user@host# set below-major 1632


[edit snmpmonitor chassis-alarm voltage-1.8v]user@host# set below-critical 1620


[edit snmpmonitor chassis-alarm voltage-1.8v]user@host# set over-minor 2028


[edit snmpmonitor chassis-alarm voltage-1.8v]user@host# set over-major 2040


[edit snmpmonitor chassis-alarm voltage-1.8v]user@host# set over-critical 2052








CHAPTER 17

Example


Example: SNMPMonitoring of Multiple MIB Objects

You can configure SNMP to monitor a column of a MIB table and configure SNMP

notifications to include MIB objects located in the same row as the object that generates

the event. This example shows how to configure an alarm to generate an event in response

to error conditions and send notifications that contain both the number of router errors

and router timeouts.

This example uses the juniSaeRouterTable shown in Table 19 on page 95. SNMP monitors

the juniSaeRouterMsgErrors branch, and sends a notification object (juniSdxMibs.24.2.1)

for the objects in the same row as the object attached to the notification:

juniSaeRouterMsgTimeouts and juniSaeRouterMsgErrors. The monitor generates an

event named routerErrorEvent for the column juniSaeRouterMsgErrors.

Table 19: Example Table for juniSaeRouterTable Object

juniSaeRouterMsgTimeoutsjuniSaeRouterMsgErrorsjuniSaeRouterClinetId

5100default@router1

011default@router2

252default@router3

.........

The following example shows the configuration for this scenario.

snmpmonitor {alarm saeRouterErrors {variable juniSaeRouterMsgErrors;//strict-oid;event routerErrorEvent;…

}event routerErrorEvent notification {oid juniSdxMibs.24.2.1


wildcarded-object [juniSaeRouterMsgErrors,juniSaeRouterMsgTimeouts]

}}







CHAPTER 18

Configuration Statements





Configuration Statements for the SRC SNMPAgent

Use the following configuration statements to configure the SRC SNMP agent at the

[edit] hierarchy level.

snmp agent {trap-history-limit trap-history-limit;component-polling-interval component-polling-interval;protocol-log-level protocol-log-level;

}snmp agent initial {base-dn base-dn;host-id host-id;

}snmp agent initial directory-connection {url url;backup-urls [backup-urls...];principal principal;credentials credentials;protocol (ldaps);timeout timeout;check-interval check-interval;blacklist;snmp-agent;

}snmp agent initial directory-eventing {eventing;signature-dn signature-dn;polling-interval polling-interval;event-base-dn event-base-dn;dispatcher-pool-size dispatcher-pool-size;

}snmp agent java {heap-size heap-size;

}


snmp agent logger name ...snmp agent logger name file {filter filter;filename filename;rollover-filename rollover-filename;maximum-file-sizemaximum-file-size;

}snmp agent logger name syslog {filter filter;host host;facility facility;format format;

}

For detailed information about each configuration statement, see the SRC PE CLI

Command Reference.



Configuration Statements for the SRC SNMPAgent

Use the following configuration statements to configure the SRC SNMP agent at the

[edit] hierarchy level.

snmp {contact contact;name name;location location;description description;address [address...];

}snmp community community {authorization (read-only|read-write);clients clients;oid oid;

}snmp notify target target-name {address address;port port;community community;type (trapv1|trapv2|inform);

}snmp v3 snmp-community community-index {community-name community-name;security-name security-name;address address;

}snmp v3 usm local-engine user username ...snmp v3 usm local-engine user username access {authorization (read-only | read-write);oid oid;

}snmp v3 usm local-engine user username authentication-md5 {authentication-password authentication-password;



}snmp v3 usm local-engine user username authentication-sha {authentication-password authentication-password;

}snmp v3 usm local-engine user username privacy-aes {privacy-password privacy-password;

}snmp v3 usm local-engine user username privacy-des {privacy-password privacy-password;

}snmp v3 vacm access group group-name ...snmp v3 vacm access group group-name default-context-prefix security-model(any|v1|v2c|usm) ...

snmp v3 vacm access group group-name default-context-prefix security-model(any|v1|v2c|usm) security-level (authentication|none|privacy) {read-view read-view;write-viewwrite-view;

}snmp v3 vacm security-to-group security-model (v1|v2c|usm) ...snmpv3vacmsecurity-to-groupsecurity-model (v1|v2c|usm)security-namesecurity-name{group-name group-name;

}snmp view view-name ...snmp view view-name oid oid {(include|exclude);

}


Command Reference.



Configuration Statements for the SNMP Traps

Use the following configuration statements to configure the SNMP traps and the

notification target at the [edit] hierarchy level.

snmp notify alarm category category-name ...snmp notify alarm category category-name alarm alarm-name {interval interval;critical critical;majormajor;minorminor;

}snmp notify event category category-name ...snmp notify event category category-name event event-name ...snmp notify target target-name {address;port;community;type (trapv1|trapv2|inform);

}


Chapter 18: Configuration Statements


Command Reference.





Configuration Statements for Customized SRC SNMPMonitors

Use the following configuration statements to configure the SNMP custom monitoring

at the [edit] hierarchy level.

snmpmonitor {security-name security-name;

}snmpmonitor alarm name{interval interval;sample-type (absolute-value | delta-value);ignore-startup-alarm;event event;variable variable;strict-oid;

}snmpmonitor alarm name boolean-test {comparison (equal | unequal | less | less-or- equal | greater | greater-or-equal);value value;

}snmpmonitor alarm name existence-test {type (present | absent | changed);

}snmpmonitor alarm name threshold-test {rising-threshold rising-threshold;falling-threshold falling-threshold;

}snmpmonitor alarm name delta-discontinuity-check {variable variable;

}snmpmonitor event namenotification {oid oid;strict-object [strict-object...];wildcarded-object [wildcarded-object...];

}snmpmonitor event name snmp-set {variable variable;value value;strict-oid;

}


Command Reference.









Chapter 18: Configuration Statements



PART 3

Administration

• Managing the SRC SNMP Agent on page 105

• Monitoring the SRC SNMP Agent on page 109

• Routine Monitoring on page 111




CHAPTER 19

Managing the SRC SNMP Agent


• Starting the SRC SNMP Agent (SRC CLI) on page 105



• Stopping the SRC SNMP Agent (C-Web Interface) on page 107

Operating the SRC SNMPAgent

You must configure the SRC SNMP agent and then manually start the agent. If you

attempt to manually start the SRC SNMP agent before it is configured, the software

displays a message that the agent has not been configured and cannot start.

The SRC SNMP agent automatically restarts in the event of a host reboot or process

failure that stops the agent.




Starting the SRC SNMPAgent (SRC CLI)

Before you start the SRC SNMP agent:

1. Perform the initial configuration tasks.

See Configuring the SRC Software.

2. Configure the SRC SNMP agent.

See “Configuring the SRC SNMP Agent (SRC CLI)” on page 41.

Manually start the SRC SNMP agent the first time it runs. Thereafter, the agent

automatically restarts.

To start the SRC SNMP agent:

user@host> enable component agent


The system responds with a start message. If the SRC SNMP agent is already running,

the system responds with a warning message indicating that fact.


Starting the SRC SNMP Agent (C-Web Interface) on page 106•



Starting the SRC SNMPAgent (C-Web Interface)

You must configure the SNMP agent and then manually start the agent. If you attempt

to manually start the SNMP agent before it is configured, the software displays a message

that the agent has not been configured and cannot start.

The SNMP agent automatically restarts in the event of a host reboot or process failure

that stops the agent.

Before you start the SRC SNMP agent:

1. Perform the initial configuration tasks on the C Series Controller.

2. Configure the SRC SNMP agent.

See “Configuring the SRC SNMP Agent (C-Web Interface)” on page 42.

Manually start the SRC SNMP agent the first time it runs. Thereafter, the agent

automatically restarts.

To start the SNMP agent:

1. Click Manage>Enable.

2. From the Component box, select agent.

The system responds with a start message. If the SNMP agent is already running, the

system responds with a warning message indicating that fact.


Starting the SRC SNMP Agent (SRC CLI) on page 105•

• Stopping the SRC SNMP Agent (C-Web Interface) on page 107


Stopping the SRC SNMPAgent (SRC CLI)

To stop the SRC SNMP agent:

user@host> disable component agent

The system responds with a stop message. If the SRC SNMP agent is not running when

you issue the command, the software responds with a warning message indicating that

fact.




Stopping the SRC SNMP Agent (C-Web Interface) on page 107•

• Starting the SRC SNMP Agent (SRC CLI) on page 105


Stopping the SRC SNMPAgent (C-Web Interface)

To stop the SNMP agent:

1. Click Manage>Disable.

2. From the Component box, select agent.

The system responds with a stop message. If the SNMP agent is not running when you

issue the command, the software responds with a warning message indicating that fact.







Chapter 19: Managing the SRC SNMP Agent



CHAPTER 20

Monitoring the SRC SNMP Agent



Monitoring the SRC SNMPAgent (SRC CLI)

Purpose Display the SRC SNMP agent status.

Action user@host> show component

The system responds with a status message.


Monitoring the SRC SNMP Agent (C-Web Interface) on page 109•


Monitoring the SRC SNMPAgent (C-Web Interface)

To display the SRC SNMP agent status:

1. Click Monitor>Component.

The system responds with a status message.








CHAPTER 21

Routine Monitoring

• Viewing Statistics About the Directory (SRC CLI) on page 112

• Viewing SNMP Statistics for the Directory (C-Web Interface) on page 112

• Viewing Statistics for Directory Connections (SRC CLI) on page 113

• Viewing SNMP Statistics for Directory Connections (C-Web Interface) on page 114

• Viewing SNMP Information for Client Licenses (SRC CLI) on page 115

• Viewing SNMP Statistics for Client Licenses (C-Web Interface) on page 116

• Viewing SNMP Information for Local Licenses (SRC CLI) on page 116

• Viewing SNMP Statistics for Local Licenses (C-Web Interface) on page 117

• Viewing SNMP Statistics for Licenses by Device (C-Web Interface) on page 118

• Viewing SNMP Information for Licenses on Virtual Routers (SRC CLI) on page 119

• Viewing SNMP Information for Policies (SRC CLI) on page 119

• Viewing SNMP Statistics About Policies (C-Web Interface) on page 120

• Viewing SNMP Information for the SAE Server Process (SRC CLI) on page 120

• Viewing SNMP Statistics About Server Processes (C-Web Interface) on page 121

• Viewing Statistics for RADIUS Clients (SRC CLI) on page 121

• Viewing SNMP Statistics About RADIUS (C-Web Interface) on page 122

• Viewing SNMP Information for RADIUS Clients (SRC CLI) on page 122

• Viewing SNMP Statistics About RADIUS Clients (C-Web Interface) on page 123

• Viewing SNMP Information for Routers and Devices (SRC CLI) on page 124

• Viewing SNMP Statistics for Devices (C-Web Interface) on page 124

• Viewing Statistics for Device Drivers (SRC CLI) on page 125

• Viewing Statistics for Specific Device Drivers (SRC CLI) on page 126

• Viewing SNMP Statistics for Specific Devices (C-Web Interface) on page 127

• Viewing Statistics for Subscriber and Service Sessions (SRC CLI) on page 128

• Viewing SNMP Statistics for Subscriber Sessions and Service Sessions (C-Web


• Monitoring Statistics for Subscriber and Service Sessions (SRC CLI) on page 129


• Viewing Information About Components Installed (SRC CLI) on page 129

• Viewing Information About Components Installed (C-Web Interface) on page 130

Viewing Statistics About the Directory (SRC CLI)

Purpose View statistics about the directory.

Action user@host> show sae statistics directory

SNMPStatisticsServices read 51Services written 0Subscriptions read 0Subscriptions written 0Users read 0Users written 0


Configuring the Directory Location for SAE Data (C-Web Interface)•




Viewing SNMPStatistics for the Directory (C-Web Interface)

Purpose View SNMP statistics for the directory.

Action Click Monitor>SAE >Statistics>Directory.1.

The Statistics/Directory pane appears.

2. In the Slot box, enter the number of the slot for which you want to display SNMP

statistics for the directory.

3. Click OK.

The Statistics/Directory pane displays statistics for the directory.




Configuring SAE Properties for Global Default SNMP Communities for Use with JunosE

Routers and Devices Running Junos OS

•




Viewing Statistics for Directory Connections (SRC CLI)

Purpose View information for all or specific directory connections.

Action To view statistics for directory connections:

user@host> show sae statistics directory connections

DES connectionConnection ID FEEDBACK_DATA_MANAGERNumber of read 93Number of write 93Number of events sent 0Number of events dropped 0Average read time 2Average write time 23Directory host 127.0.0.1Directory port 389Directory type primaryPrimary restore time 83218Event queue length 0

...

DES connectionConnection ID ldapAuth-LdapAuthenticatorNumber of read 0Number of write 0Number of events sent 0Number of events dropped 0Average read time 0Average write time 0Directory host 127.0.0.1Directory port 389Directory type primaryPrimary restore time 83200Event queue length 0

To view information about particular directory connections, specify all or part of the

connection ID.

user@host> show sae statistics directory connections filter filter

For example, if you wanted to view the directory connection that contained ldap in its

connection ID:

user@host> show sae statistics directory connections filter ldap

DES connectionConnection ID ldapAuth-LdapAuthenticator


Chapter 21: Routine Monitoring

Number of read 0Number of write 0Number of events sent 0Number of events dropped 0Average read time 0Average write time 0Directory host 127.0.0.1Directory port 389Directory type primaryPrimary restore time 83608Event queue length 0

To view only the directory connection IDs:

user@host> show sae statistics directory connections brief

Directory ConnectionsFEEDBACK_DATA_MANAGEREQUIPMENT_DATA_MANAGERPOM_EngineLICENSE_MANAGERSAE_ConfigMgradminLdap-LdapAuthenticatorSERVICE_DATA_MANAGERUSER_DATA_MANAGERSAE_ConfigMgr(dynamicProps)ldapAuth-LdapAuthenticator


Configuring the Directory Location for SAE Data (C-Web Interface)•




Viewing SNMPStatistics for Directory Connections (C-Web Interface)

Purpose View SNMP statistics for directory connections.



Action 1. Click Monitor>SAE >Statistics>Directory>Connections.

The Statistics/Directory/Connections pane appears.

2. In the Connection ID box, enter a full or partial connection ID for which you want to

display information, or leave the box blank to display all SNMP statistics for all directory

connections.


statistics for directory connections.

4. Select an output style from the Style list.

5. Click OK.

The Statistics/Connections pane displays statistics for directory connections.




•




Viewing SNMP Information for Client Licenses (SRC CLI)

Purpose View SNMP information about the state of client licenses.

Action user@host> show sae statistics license client




•







Viewing SNMPStatistics for Client Licenses (C-Web Interface)

Purpose View SNMP statistics for client licenses.

Action Click Monitor>SAE >Statistics>License>Client.1.

The Statistics/License/Client pane appears.


statistics for client licenses.

3. Click OK.

The Statistics/License/Client pane displays statistics for client licenses.


Viewing SNMP Statistics for Licenses by Device (C-Web Interface) on page 118•





Viewing SNMP Information for Local Licenses (SRC CLI)

Purpose View SNMP information about the state of local licenses.



Action user@host> show sae statistics license local

Client License StateMode PilotNumber of licensed users 100Number of current users 0Expiry 2007-02-23




•





Viewing SNMPStatistics for Local Licenses (C-Web Interface)

Purpose View SNMP statistics for local licenses.

Action Click Monitor>SAE >Statistics>License>Local.1.

The Statistics/License/Local pane appears.


statistics for local licenses.

3. Click OK.

The Statistics/License/Local pane displays statistics for local licenses.




•








Viewing SNMPStatistics for Licenses by Device (C-Web Interface)

Purpose View SNMP statistics for licenses by device.

Action 1. Click Monitor>SAE >Statistics>License>Device.

The Statistics/License/Device pane appears.

2. In the Device Name box, enter a full or partial device name for which you want to

display information, or leave the box blank to display SNMP statistics for all devices.

For JunosE router drivers, use the format:

<virtual router name>@<router name>

For device drivers running Junos OS and PCMM drivers, use the format:

default@<router name>


statistics for device licenses.


5. Click OK.

The Statistics/License/Device pane displays statistics for virtual router licenses.


Connections to Managed Devices•








Viewing SNMP Information for Licenses on Virtual Routers (SRC CLI)

Purpose View SAE license information for the SRC software.

Action To view SNMP information about the state of licenses on specified virtual routers:

user@host> show sae statistics license device

To view information about the state of licenses for a particular virtual router, specify all

or part of the VR name. For device drivers running Junos OS and PCMM drivers, use the

format default@routerName.

user@host> show sae statistics license device name name

To view only the virtual router names:

user@host> show sae statistics license device brief




•





Viewing SNMP Information for Policies (SRC CLI)

Purpose View SNMP information for the policy engine, policy decision point, and the shared object

repository where the policy objects are stored:

Action user@host> show sae statistics policy-management

SNMPStatisticsPolicy Management Type Policy Engine DataTotal number of policy group modifications 0Total number of interface classifier modifications 0Average time for processing policy group modification 0Average time for processing interface classifier modification 0Policy Management Type PDP DataTotal number of default policy decisions 45Total number of service policy decisions 0Total number of errors 0Policy Management Type Repository DataCurrent total number of policy groups loaded 1




•



• Viewing Information About Policies (C-Web Interface)

• Viewing SNMP Statistics About Policies (C-Web Interface) on page 120

Viewing SNMPStatistics About Policies (C-Web Interface)

Purpose View SNMP statistics about policies.

Action Click Monitor>SAE >Statistics>Policy Management.

The Statistics/Policy Management pane appears.


statistics for policies.

2. Click OK.

The Statistics/Policy Management pane displays statistics for policies.




•

• Viewing Information About Policies (C-Web Interface)

• Viewing SNMP Information for Policies (SRC CLI) on page 119

Viewing SNMP Information for the SAE Server Process (SRC CLI)

Purpose View SNMP information for the SAE server process.



Action user@host> show sae statistics process

SNMPStatisticsHeap in use 19211 kilo bytes (2%)Heap limit 910016 kilo bytesThreads 96Up time 80877 seconds since Tue Jan 23 19:51:42 EST 2007




•

• Viewing SNMP Statistics About Server Processes (C-Web Interface) on page 121

Viewing SNMPStatistics About Server Processes (C-Web Interface)

Purpose View SNMP statistics about server processes.

Action Click Monitor>SAE >Statistics>Process.1.

The Statistics/Process pane appears.


statistics for server processes.

3. Click OK.

The Statistics/Process pane displays statistics for server processes.




•

• Viewing SNMP Information for the SAE Server Process (SRC CLI) on page 120

Viewing Statistics for RADIUS Clients (SRC CLI)

Purpose View SNMP statistics for RADIUS clients.



Action user@host> show sae statistics radius

SNMPStatisticsAccounting ACKs from unrecognized IP 0Authentication ACKs from unrecognized IP 0Radius client ID SAE.buffy


Configuring the RADIUS Local IP Address and NAS ID (C-Web Interface)•

• Viewing SNMP Information for RADIUS Clients (SRC CLI) on page 122

Viewing SNMPStatistics About RADIUS (C-Web Interface)

Purpose View SNMP statistics about RADIUS.

Action Click Monitor>SAE >Statistics>RADIUS.1.

The Statistics/RADIUS pane appears.


statistics for RADIUS.

3. Click OK.

The Statistics/RADIUS pane displays statistics for RADIUS.




•

• Viewing SNMP Statistics About RADIUS Clients (C-Web Interface) on page 123

Viewing SNMP Information for RADIUS Clients (SRC CLI)

Purpose View SNMP information for RADIUS clients. You can view information for all accounting

or authentication clients, or by IP address, UDP port number, or IP address and UDP port.



Action To view SNMP information for RADIUS accounting clients:

user@host> show sae statistics radius client accounting

To view SNMP information for RADIUS authentication clients:

user@host> show sae statistics radius client authentication

To view information for a particular RADIUS client by IP address:

user@host> show sae statistics radius client ip-address ip-addressuser@host> show sae statistics radius client accounting ip-address ip-addressuser@host> show sae statistics radius client authentication ip-address ip-address

To view information for a particular RADIUS client by UDP port number:

user@host> show sae statistics radius client udp-port udp-portuser@host> show sae statistics radius client accounting udp-port udp-portuser@host> show sae statistics radius client authentication udp-port udp-port

To view only the RADIUS clients that were accessible by IP address and port number:

user@host> show sae statistics radius client briefuser@host> show sae statistics radius client accounting briefuser@host> show sae statistics radius client authentication brief


Configuring the RADIUS Local IP Address and NAS ID (C-Web Interface)•

• Viewing Statistics for RADIUS Clients (SRC CLI) on page 121

Viewing SNMPStatistics About RADIUS Clients (C-Web Interface)

Purpose View SNMP statistics about RADIUS clients.

Action 1. Click Monitor>SAE >Statistics>RADIUS>Client.

The Statistics/RADIUS/Client pane appears.

2. Select a client type from the Client Type list:

• accounting—Displays RADIUS accounting information

• authentication—Displays RADIUS client authentication information



3. In the IP Address box, enter the client IP address to display SNMP information for a

specific RADIUS client, or leave the box blank to display SNMP information for all

RADIUS clients.


statistics for RADIUS clients.


6. In the UDP Port box, enter a port number to display SNMP information for a specific

RADIUS client, or leave the box blank to display SNMP information for all RADIUS

clients.

7. Click OK.

The Statistics/RADIUS/Client pane displays statistics for RADIUS clients.




•

• Viewing SNMP Statistics About RADIUS (C-Web Interface) on page 122

Viewing SNMP Information for Routers and Devices (SRC CLI)

Purpose View SNMP information for routers and devices that the SAE manages. You can view

information for all routers and devices, or for specific ones.

Action To view SNMP information for routers and devices that the SAE is managing:

user@host> show sae statistics device

To view information for a particular router, specify all or part of the VR name. For device

drivers running Junos OS and PCMM drivers, use the format default@routerName.

user@host> show sae statistics device filter filter

To view only the RADIUS clients that were accessible by IP address and port number:

user@host> show sae statistics device brief




•




Viewing SNMPStatistics for Devices (C-Web Interface)

Purpose View SNMP statistics about devices.



Action 1. Click Monitor>SAE >Statistics>Device.

The Statistics/Device pane appears.


display information, or leave the box blank to display all devices.


statistics for devices.


5. Click OK.

The Statistics/Device pane displays statistics for all devices.




•




Viewing Statistics for Device Drivers (SRC CLI)

Purpose View SNMP statistics for all device drivers.



Action user@host> show sae statistics device common

SNMPStatisticsDriver type JunosE COPSNumber of close requests 0Number of connections accepted 0Number of current connections 0Number of open requests 0Server address 0.0.0.0Server port 3288Time since last redirect 0

SNMPStatisticsDriver type PACKETCABLE COPSNumber of close requests 0Number of connections accepted 0Number of current connections 0Number of open requests 0Server address 0.0.0.0Server port 0Time since last redirect 0

SNMPStatisticsDriver type JunosNumber of close requests 0Number of connections accepted 0Number of current connections 0Number of open requests 0Server address 0.0.0.0Server port 3333Time since last redirect 0

The value of the server address can be either an IPv4 or IPv6 address, depending on the

platform.


Shutting Down the Device Drivers (C-Web Interface)•

• Viewing Information About SAE Device Drivers (SRC CLI)



Viewing Statistics for Specific Device Drivers (SRC CLI)

Purpose View statistics for specific router drivers or device drivers.

Action To view SNMP statistics for device drivers running Junos OS:

user@host> show sae statistics device common junos

To view SNMP statistics for JunosE router drivers:

user@host> show sae statistics device common junose-cops



To view SNMP statistics for PCMM device drivers:

user@host> show sae statistics device common packetcable-cops

To view SNMP statistics for third-party device drivers:

user@host> show sae statistics device common proxy

For example, to view SNMP statistics for device drivers running Junos OS:

user@host> show sae statistics device common junos

SNMPStatisticsDriver type Junos OSNumber of close requests 0Number of connections accepted 0Number of current connections 0Number of open requests 0Server address 0.0.0.0Server port 3333Time since last redirect 0


Configuring the Session Store Feature (SRC CLI)•

• Viewing Information About SAE Device Drivers (SRC CLI)



Viewing SNMPStatistics for Specific Devices (C-Web Interface)

Purpose View SNMP statistics about specific devices.

Action 1. Click Monitor>SAE >Statistics>Device>Common.

The Statistics/Device/Common pane appears.


display information, or leave the box blank to display all devices.


statistics for specific devices.



4. Select a device type from the Type list:

• junos—Displays SNMP statistics for device drivers running Junos OS

• junose-cops—Displays SNMP statistics for JunosE router drivers

• packetcable-COPS—Displays SNMP statistics for PCMM device drivers

• proxy—Displays SNMP statistics for third-party drivers

5. Click OK.

The Statistics/Device/Common pane displays statistics for the specified device.




•




Viewing Statistics for Subscriber and Service Sessions (SRC CLI)

Purpose View SNMP statistics for subscriber and service sessions.

Action user@host> show sae statistics sessions

SNMPStatisticsCurrent service sessions 0Current user sessions 0Logins (includes sync. and static IP portal logins) 0Logouts 0Service session idle timeouts 0Service sessions started 0Service sessions stopped 0Service session timeouts 0


Configuring Access to Subscriber Data (SRC CLI)•

• Configuring Access to Service Data (SRC CLI)

• Viewing Information About Subscriber Sessions by DN (SRC CLI)

• Viewing Information About Subscriber Sessions by Service Name (SRC CLI)

• Viewing Information About Subscriber Sessions by Session ID (SRC CLI)

• Monitoring Statistics for Subscriber and Service Sessions (SRC CLI) on page 129

Viewing SNMPStatistics for Subscriber Sessions and Service Sessions (C-WebInterface)

Purpose View SNMP statistics about subscriber sessions and service sessions.



Action Click Monitor>SAE >Statistics>Sessions.1.

The Statistics/Sessions pane displays statistics for subscriber sessions and service

sessions.


statistics for specific devices.

3. Click OK.

The Statistics/Sessions pane displays statistics for subscriber sessions and service

sessions.




•



Monitoring Statistics for Subscriber and Service Sessions (SRC CLI)

Purpose Display real-time SNMP statistics for subscriber and service sessions.

Action To display real-time SNMP statistics for subscriber and service sessions:

user@host> monitor sae statistics sessions

To specify the time interval for refreshing the data:

user@host> monitor sae statistics sessions interval interval


Viewing Statistics for Subscriber and Service Sessions (SRC CLI) on page 128•

• Output Control Keys for monitor Command

Viewing Information About Components Installed (SRC CLI)

Purpose View release and status information for SRC components installed on a system.



Action user@host> show component

Installed ComponentsName Version Statuscli Release: 7.0 Build: CLI.A.7.0.0.0171 running acp Release: 7.0 Build: ACP.A.7.0.0.0174 disabledjdb Release: 7.0 Build: DIRXA.A.7.0.0.0176 running editor Release: 7.0 Build: EDITOR.A.7.0.0.0176 running redir Release: 7.0 Build: REDIR.A.7.0.0.0176 disabledlicSvr Release: 7.0 Build: LICSVR.A.7.0.0.0179 stopped nic Release: 7.0 Build: GATEWAY.A.7.0.0.0170 disabledsae Release: 7.0 Build: SAE.A.7.0.0.0166 running www Release: 7.0 Build: UMC.A.7.0.0.0169 disabledjps Release: 7.0 Build: JPS.A.7.0.0.0172 disabledagent Release: 7.0 Build: SYSMAN.A.7.0.0.0174 running webadm Release: 7.0 Build: WEBADM.A.7.0.0.0173 disabled

Meaning Table 20 on page 130 describes the output fields for the show component command.

Output fields are listed in the order in which they appear.

Table 20: Output Fields for show component

Field DescriptionField Name

Name of the componentName

Version of the componentVersion

State of the component, running or disabledStatus


Viewing Information About Components Installed (C-Web Interface) on page 130•

• Viewing C Series Controller Information

• Directories on the C Series Controller

Viewing Information About Components Installed (C-Web Interface)

Purpose View the installed SRC components.

Action Click Monitor>Component.

The Component pane displays the status of each installed component.




• Viewing Information About Components Installed (SRC CLI) on page 129

• Viewing C Series Controller Information

• Directories on the C Series Controller





PART 4

Troubleshooting

• Troubleshooting Procedures on page 135




CHAPTER 22

Troubleshooting Procedures

• Collecting Data with the Activity Monitor (SRC CLI) on page 135

• Collecting Data with the Activity Monitor (C-Web Interface) on page 136

• Viewing Graphs (C-Web Interface) on page 137

• Viewing Graphs from a Web Page on page 137

Collecting Data with the Activity Monitor (SRC CLI)

You can collect data with the Activity Monitor for specific components over a specified

time and save them to a tar.gz file in the /opt/UMC/activity/var/diagnostic/* directory.

You can view the exact file name and path after you execute the request support

information command. Before you perform data collection with the Activity Monitor,

make sure the filter for the specific components is enabled.

To perform data collection with the Activity Monitor:

• user@host> request support information

Some of the information retrieved includes:

• System log messages from the /var/log/messages/* directory.

• The configuration in text format, XML format, and set format.

• The host name in the name of the diagnostic file.

To perform data collection for specific components:

• user@host> request support information component

where component is one of the following:

• acp—SRC Admission Control Plug-In

• activity—Activity Monitor

• agent—SNMP agent

• appsvr—Application server

• cli—SRC CLI

• diameter—Diameter application


• dsa—Dynamic Service Activator

• extsubmon—External Subscriber Monitor

• ims—IP multimedia subsystem

• jdb—Juniper Networks database

• jps—Juniper Policy Server

• licSvr—License server

• nic—Network information collector

• redir—Redirect server

• sae—SAE

• webadm—C-Web interface

To perform data collection for a specified number of days:

• user@host> request support information days

where days is in the range of 1–36500.


Before You Load a Configuration•



• Monitoring Activity on C Series Controllers

Collecting Data with the Activity Monitor (C-Web Interface)

You can collect data with the Activity Monitor for specific components over a specified

time. Before you configure data collection for the Activity Monitor, make sure the Activity

Monitor (activity), CLI (cli), and C-Web interface (webadm) components are enabled.

To perform data collection with the Activity Monitor:

1. Click Manage>Request>Support>Information.

The Support Information pane appears.

2. From the Components list, select the components you want to monitor, and clickOK.

3. (Optional) Enter the number of days for which you want to collect data, and clickOK.


Viewing Graphs (C-Web Interface) on page 137•





Viewing Graphs (C-Web Interface)

You can display graphs for components for which the Activity Monitor has collected data.

To display graphs from the Activity Monitor with the C-Web interface:

1. Click Graphs.

2. In the side pane, select the component and the graph that you want to display.

The pane for selecting the time period displayed by the graph appears.

3. Select one of the preset values or enter the time range in the From and To boxes, and

click OK.

The graphs appear.


Collecting Data with the Activity Monitor (C-Web Interface) on page 136•



Viewing Graphs from aWeb Page

You can display graphs for components for which the Activity Monitor has collected data

from a Web page. Before you display these graphs, make sure the Activity Monitor

(activity) and C-Web interface (webadm) components are enabled. For more secure

displays, configure the C-Web interface to use HTTPS and use POST requests.

• Viewing Graphs for a Preset Time Period from a Web Page on page 137

• Viewing Graphs for Specified Time Periods from a Web Page on page 138

Viewing Graphs for a Preset Time Period from aWeb Page

To display graphs with preset time periods from the Activity Monitor from a Web page:

http://ip-address/graph?&id=username&pw=password&name=graph-name&time=time-period

where

• ip-address—IP address of the C Series Controller

• username—Username used to log in to the C Series Controller

• password—Password used to log in to the C Series Controller

• graph-name—Name of graph to display in the format <component>-<graph>, where

<graph> is the name of the graph as specified in the C-Web interface in all lowercase

letters with hyphens separating words

• time-period—Period of time that data was collected for display in a graph in the format

<number><units>


Chapter 22: Troubleshooting Procedures

The <number> is the number of <units>, which are specified as one of the following

values:

• m—minutes

• h—hours

• d—days

• w—weeks

• M—months

• y—years

For example, to view the CPU graph for the System component for the past 10 minutes

on the C Series Controller called c2000 for the user admin:

http://c2000/graph?&id=admin&pw=secret&name=system-cpu&time=10m

The CPU Usage graph appears.

Viewing Graphs for Specified Time Periods from aWeb Page

To display graphs for specified time periods from the Activity Monitor from a Web page:

http://ip-address/graph?&id=username&pw=password&name=graph-name&start=date-time

&end=date-time

where

• ip-address—IP address of the C Series Controller

• username—Username used to log in to the C Series Controller

• password—Password used to log in to the C Series Controller



• graph-name—Name of graph to display in the format <component>-<graph>, where

<graph> is the name of the graph as specified in the C-Web interface in all lowercase

letters with hyphens separating words

• date-time—Date and time that data was collected for display in a graph in the format

yyyyMMddHHmm, where:

• yyyy—year

• MM—month

• dd—day

• HH—hour

• mm—minute

For example, to view the heap usage graph for the SAE component from January 15 to

January 28 on the C Series Controller called c2000 for the user admin:

http://c2000/graph?&id=admin&pw=secret&name=sae-heap&start=200901150000

&end=200901280000

The SAE Heap Usage graph appears.


• Collecting Data with the Activity Monitor (SRC CLI) on page 135

• Collecting Data with the Activity Monitor (C-Web Interface) on page 136




Chapter 22: Troubleshooting Procedures



PART 5

Index

• Index on page 143




Index

AACP congestion point usage trap

configuring .......................................................................73

Activity Monitor

data collection......................................................135, 136

graphs, viewing..............................................................137

Cconventions

notice icons.......................................................................xii

text........................................................................................xii

customer support...................................................................xiv

contacting JTAC..............................................................xiv

Ddirectory

description..........................................................................4

directory server...........................................................................4

documentation

comments on..................................................................xiv

JJuniper Networks database

SNMP information, viewing

C-Web interface............................................112, 114

LLDAP (Lightweight Directory Access Protocol).See

directory; directory server

licenses


C-Web interface.............................................116, 117

Mmanuals

comments on..................................................................xiv

MIBs

Juniper Networks, list....................................................10

monitoring with SNMP agent......................................9

Nnetwork devices


C-Web interface...................................118, 124, 127

notice icons................................................................................xii

notification targets

configuring with C-Web interface............................70

Ppolicies


C-Web interface...................................................120

RRADIUS statistics


C-Web interface...........................................122, 123

Sserver processes


C-Web interface....................................................121

service sessions


C-Web interface...................................................128

SNMP agent

access control, configuring on C Series

Controllers

community strings.........................................57, 60

named views...........................................................62

SNMP groups..........................................................65

VACM.........................................................................59

access control, configuring on C Series

Controllers with C-Web interface

VACM.........................................................................60

configuration statements....................................97, 98

configuring

C Series Controllers........................................37, 41

C Series Controllers with C-Web

interface...............................................................42

C-Web interface.....................................................37

SRC CLI................................................................37, 41

configuring with C-Web interface

SRC CLI.....................................................................42

directory connection parameters, configuring

C-Web interface.....................................................47

SRC CLI.....................................................................46

Java Runtime Environment, configuring

SRC CLI.....................................................................49


local properties, configuring

SRC CLI......................................................................41

with C-Web interface...........................................42

logging, configuring

SRC CLI.....................................................................48

MIBs.....................................................................................10

monitoring

C-Web interface..................................................109

SRC CLI...................................................................109

named views, defining

C Series Controllers..............................................62

notification targets, configuring


SRC CLI.....................................................................69

See also SNMP traps .....................................................11

starting

C-Web interface..................................................106

SRC CLI...................................................................105

stopping

C-Web interface...................................................107

SRC CLI...................................................................106

system information, configuring

SRC CLI.....................................................................38

trap history, configuring

SRC CLI.....................................................................43

viewing information on SAE

C-Web

interface.112, 114, 116, 117, 118, 120, 121, 122, 123, 124, 127, 128

SNMP Agent

master agent SNMP versions...................................98

SNMP alarm

Boolean test.....................................................................82

discontinuity check.......................................................84

existence test..................................................................83

overview............................................................................80

threshold test..................................................................83

SNMP chassis alarms

battery voltage sensors...............................................88

configuring........................................................................87

CPU core voltage sensors...........................................89

CPU DIMM voltage sensors.......................................89

CPU sensors....................................................................88

CPU temperature sensors..........................................90

fan speed sensors...........................................................91

overview.............................................................................33

system temperature sensors......................................91

voltage sensors...............................................................92

SNMP events....................................................................85, 86

SNMP monitors

alarms................................................................................80

Boolean test............................................................82

existence test.........................................................83

threshold test..................................................83, 84

chassis alarms..........................................................33, 91

configuring...............................................................87

events.........................................................................85, 86

overview................................................................................7

security name..................................................................85

statement hierarchy...................................................100

SNMP traps

alarm state transitions..................................................16

configuring...................................................................71, 72

event traps

configuring................................................................72

defined........................................................................11

list and description................................................13

notification targets, configuring


notifications

defined........................................................................11

overview.............................................................................10

performance traps

accounting................................................................21

authentication........................................................23

chassis........................................................................31

configuring.................................................................71

defined.......................................................................10

JPS..............................................................................30

NIC...............................................................................25

policy engine...........................................................28

redirect server.........................................................29

router driver.............................................................25

SAE..............................................................................19

SRC ACP...................................................................29

system management..........................................28

snmp-named-views-cli........................................................62

snmp-security-names-cli....................................................67

snmp-statements...................................................................97

SRC components

description...........................................................................3

information, viewing

C-Web interface...................................................130

SRC CLI....................................................................129

subscriber sessions


C-Web interface...................................................128

support, technical See technical support



Ttechnical support

contacting JTAC..............................................................xiv

text conventions.......................................................................xii

traps. See SNMP traps


Index



Documents

SNMP Management for the SRC Software - Juniper Networks · PDF file(SNMP)agent ServiceManagementApplications ... (OSS)withtheSRCsoftwaresothattheOSScanbenotifiedofeventsinthelife cycleofSAEsessions.Hostedplug-insonly