net-net route manager central 1.0 user guide

Net-Net® Route Manager CentralUser Guide

Release Version 1.0

Acme Packet, Inc.71 Third AvenueBurlington, MA 01803 USAt 781-328-4400f 781-425-5077www.acmepacket.com

Last updated: May 28, 2010Document Number: 400-0136-10 Rev 1.0.0

Notices©2002—2010 Acme Packet®, Inc., Burlington, Massachusetts. All rights reserved. Acme Packet®, Session Aware Networking®, Net-Net®, and related marks are registered trademarks of Acme Packet, Inc. All other brand names are trademarks, registered trademarks, or service marks of their respective companies or organizations.

Patents Pending, Acme Packet, Inc.

The Acme Packet Documentation Set and the Net-Net systems described therein are the property of Acme Packet, Inc. This documentation is provided for informational use only, and the information contained within the documentation is subject to change without notice.

Acme Packet, Inc. shall not be liable for any loss of profits, loss of use, loss of data, interruption of business, nor for indirect, special, incidental, consequential, or exemplary damages of any kind, arising in any way in connection with the Acme Packet software or hardware, third party software or hardware, or the documentation. Some jurisdictions do not allow the exclusion or limitation of incidental or consequential damages, so the above exclusions may not apply. These limitations are independent from all other provisions and shall apply notwithstanding the failure of any remedy provided herein.

Copying or reproducing the information contained within this documentation without the express written permission of Acme Packet, Inc., 71 Third Avenue Burlington, MA 01803, USA is prohibited. No part may be reproduced or retransmitted.

Acme Packet Net-Net products are protected by one or more of the following patents: United States: 7072303, 7028092, 7002973, 7133923, 7031311, 7142532, 7151781. France: 1342348, 1289225, 1280297, 1341345, 1347621. Germany: 1342348, 1289225, 1280297, 1341345, 1347621. United Kingdom: 1342348, 1289225, 1280297, 1341345, 1347621. Other patents are pending.

Mibble Open-Source SNMP MIB ParserLicensing

This work is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version.

This work is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA

Copyright (c) 2004-2006 Per Cederberg. All rights reserved.

SSH2

SSH, the SSH logo, TECTIA and the TECTIA logo are either trademarks or registered trademarks of SSH.

Proprietary & Confidential

Contents

About this Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Who is Acme Packet? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Customer Questions, Comments, or Suggestions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Contact Us . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

1 Installing Net-Net RMC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Before You Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Creating nnems Group and User. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Defining sudo Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Editing the sudoer Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Operating Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Memory and Disk Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

OpenSSL for HTTPS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Installing HTTPS with Third-Party Certificates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Certificate Acquisition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

About the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Extracting the Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Running Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Initialization Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Run Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Installing Net-Net RMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Choosing the Installation Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Typical Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Accept License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Applying a New License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

HTTP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

HTTPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

No Self-Signed Certificate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Creating Self-Signed Certificate. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Configuring Net-Net RMC Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Configuring SAML Single Sign-On . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20


CONTENTS

Importing Certificates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21

Starting Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22

Changing User to nnems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22

Shutting Down Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22

Uninstalling Net-Net RMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22

Backup and Restore Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23

Backing Up with Server Shutdown. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23

Backing Up with Server Running . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24

Restoring Database Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24

2 Using Net-Net RMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25

Basic Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25

Basic Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25

CSV Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25

LRT File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26

Route Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27

Accessing the Net-Net RMC GUI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28

SAML Single Sign-On . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28

Overview of Net-Net RMC GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29

Menu Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30

Navigation Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30

Content Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34

Viewing Net-Net RMC License Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35

Managing Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36

About Groups and Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36

About Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36

About Users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36

About Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37

About Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37

Accessing User Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37

Creating User Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37

Configuring Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38

Creating Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38

Changing Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39

Resetting Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40

Assigning Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41

Administrative . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41

Changing the Password Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42

Accessing Password Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42

2 Net-Net Route Manager Central Release 1.0


CONTENTS

Password Reuse Count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Administrator Password Length . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Non-Administrator Password Length . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Password Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Modifying the Inactivity Timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Audit Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Viewing Audit Logs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Searching the Audit Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Purging Audit Log Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Manually Purging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

3 Managing Route Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Property Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Accessing Route Sets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Customizing the Display. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Adding Route Sets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Working with Existing Route Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Editing Route Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Copying Route Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Viewing Associated Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Viewing LRT Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Deleting Route Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Updating Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Fail. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Success . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Importing Route Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Managing Routes in Route Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Customizing the Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Searching for Routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Adding Routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Replacing Route Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Searching Routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Editing Routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Comparing Route Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Managing Import Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Accessing Import Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Adding Import Templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Release 1.0 Net-Net Route Manager Central 3


CONTENTS

Editing Import Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75

Copying Import Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75

4 Working with Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77

About Managed Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77

Accessing All Devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77

Adding Managed Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77

Working with Devices in Route Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .78

Accessing Devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .78

Customizing the Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79

Working with Devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80

Viewing Route Sets Associated with Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80

Comparing LRT Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80

Retrieving LRT Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81

Updating Device with Route Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81

Associating Route Sets with Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83

Updating Devices with Route Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .84

Accessing Update Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .84

Creating Update Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85

Committing an Update. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .86

Rolling Back an Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .87

Viewing Update Task History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .87

Removing Managed Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .89

5 Backup and Restore Route Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .91

Accessing Route Set Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .91

Searching for Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92

Scheduling Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94

Restoring Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .96

4 Net-Net Route Manager Central Release 1.0


About this Guide

The Net-Net Route Manager Central User Guide provides the information you need to install and use the application to centrally automate the management and distribution of routing data.

Who is Acme Packet?

Acme Packet enables service providers to deliver trusted, first class interactive communications—voice, video and multimedia sessions—across IP network borders. Our Net-Net family of session border controllers satisfy critical security, service assurance and regulatory requirements in wireline, cable and wireless networks. Our deployments support multiple applications—from VoIP trunking to hosted enterprise and residential services; multiple protocols—SIP, H.323, MGCP/NCS and H.248; and multiple border points—interconnect, access network and data center.

Established in August 2000 by networking industry veterans, Acme Packet is a public company trading on the NASDAQ and headquartered in Burlington, Massachusetts.

Customer Questions, Comments, or Suggestions

Acme Packet is committed to providing our customers with reliable documentation. If you have any questions, comments, or suggestions regarding our documentation, please contact your Acme Packet customer support representative directly or email [email protected].

Contact Us Acme Packet 71 Third AvenueBurlington, MA 01803 USAt 781 328 4400f 781 425 5077www.acmepacket.com

Version 1.0 Acme Packet, Inc. Technical Publications 5


mailto:[email protected]

http://www.acmepacket.com

http://www.acmepacket.com

ABOUT THIS GUIDE

6 Net-Net Route Manager Central Version 1.0


1 Installing Net-Net RMC

Overview

This document explains how to install or upgrade Net-Net RMC in a Linux or Solaris operating system. Review the specific system and client requirements that have been certified for Net-Net RMC support by Acme Packet.

Before You Start

This section contains the information you should review before you start the installation process.

Creating nnems Group and User

For security reasons, you can create an account named nnems and a group named nnems. (You also must have the UNIX sudo facility installed and define sudo privileges.) After the installation, all the installed files are owned by nnems.

Linux To create nnems group and user:

1. Login as root.

2. Enter the following lines:

groupadd nnems

useradd -m -g nnems -d /home/nnems -s /RMC server/bin/bash nnems

passwd nnems

Solaris To create nnems group and user:

1. Login as root.

2. Enter the following lines:

groupadd nnems

useradd -m -g nnems -d /export/home/nnems -s /usr/bin/bash nnems

passwd nnems

Defining sudo Privileges

You must have the UNIX sudo facility installed on the server for deployments with user nnems. The user nnems must be granted sudo privilege. The sudo facility comes by default with RHEL AS v4.0, but not on Solaris 10. If using the Solaris version, download the utility from the Sun site. For example:

http://www.sun.com/software/solaris/freeware/

Editing the sudoer Configuration File

You need to use the visudo tool to make edits to the sudoer configuration. The Net-Net RMC administrator will need to provide a sudo password when starting Net-Net RMC.

1. Login as root.



INSTALLING NET-NET RMC

2. Add the following line to the sudoer configuration (use the visudo tool):

<named user> <hostname>=(ALL) ALL

For example:

nnems myemshost=(ALL) ALL

Operating Systems Linux:

• RHEL v5.0 (64 bit)

Solaris:

• Solaris 10 OS SPARC (64 bit)

• Solaris 10 OS x64/x86 (64 bit)

– OpenSSL 0.9.7d 17 Mar 204

(with security fixes for: CVE-2005-2969 CVE-2006-2937 CVE-2006-2940 CVE-2006-3738 CVE-2006-4339 CVE-2006-4343 CVE-2007-5135 CVE-2008-5077 CVE-2009-0590)

– Solaris patches required are:

– Solaris 10 10/09 patch bundle

– SUNWcry and SUNWcryr for OpenSSL

Memory and Disk Requirements

• Minimum platform memory: 12GB

• Minimum disk requirement: 195 GB

• Minimum CPU: 4-core 2.1 GHz processor or better

Note: Sun chip multithreading (CMT) based servers (e.g., T5220/T5440) are not recommended hardware platforms for the RMC.

OpenSSL for HTTPS

If you plan to use HTTPS, you need to verify OpenSSL is installed on the server using the openssl version command.

• To verify on Solaris:

/usr/sfw/bin/openssl version

• To verify on Linux:

/usr/bin/openssl version

If you need to install it, download OpenSSL and install it on the Net-Net RMC server before you install Net-Net RMC. Download the following OpenSSL file from www.openssl.org/source/:

openssl-0.9.7e.tar.gz

Follow the directions supplied by OpenSSL to install the files.

Installing HTTPS with Third-Party Certificates

You can use third-party X.509 certificates instead self-signed certificates for HTTPS communication. You can acquire certificates from an external certificate signing authority such as Verisign or from an in-house certificate signing authority. The typical deployment involves a chain of trust in which the certificate for a particular RMC server is signed by an intermediate authority. There might be a chain of such

8 Net-Net Route Managemer Central Version 1.0



intermediate certificate authorities whose trustworthiness is ultimately established by a root certificate authority that is known to the client browser.

Net-Net RMC supports the use of Intermediate Certificate Authorities (CAs). Intermediate CAs represent the chain of trusted certificate authorities by which trust is established from the level of a signed certificate for an individual server up to a trusted Root CA whose trustworthiness is known to the browser.

Preparing for using third-party X.509 certificates with Net-Net RMC includes:

• certificate acquisition

• server preparation

• client preparation

The certificates must be accessible on the RMC server because they are copied into the installation area.

Note: If you run the script as user nnems rather than as root, ensure that any third-party certificate and key files required are readable by nnems user.

Certificate Acquisition You must acquire the server certificates and any intermediate certificates in the chain of trust for each RMC server. If deploying an HA pair, you need to acquire the certificates for each of the RMC servers. The certificates for the chain of trust above the RMC server might be the same, but each RMC server certificate is distinct.

The RMC server certificate and key file must be in X.509 format, PEM-encoded, and not password-protected or encrypted (other than RSA 1024 or 2048). For example, des3 is not supported.

Intermediate certificates (if used) must be in X.509 format and PEM-encoded. Certificates in .pb7 or PKCS7 format are not supported. Also, the certificates must not be encrypted or password protected.

About the Installation

The application server is packaged and delivered a one .zip file. This file contains all the required components that will allow the application servers to be configured and started on Linux and Solaris machines. The package is self-contained and requires that a setup application run in order to properly configure the servers for startup.

The installation process consists of extracting the contents of a zip file and running a set up application to configure the servers. You then can choose to perform a typical or a custom installation. The following steps summarize the process.

1. Login as root on the host system where the application is to be installed.

2. Download the installation zip file specific to your operating system.

• Linux OS

RMC100Linux64bit.zip

• Solaris 10+ OS (64 bit)

RMC100Solaris64.zip

RMC100Solaris64x86.zip

3. Unzip the installation zip file in the /opt directory.




4. Apply the correct permissions to the directories and files in order to run the setup application. For example in the /opt directory you set full permissions to the files in the AcmePacket directory:

chmod –R 777 ACMEPacket

5. Change directory to AcmePacket/RMC100/bin.

cd /opt/ACMEPacket/RMC100/bin

6. Run the ./startrmc.sh script.

./startrmc.sh

Extracting the Application

The following steps describe the process of extracting the application onto the host machine.

1. Log into the host system as root.

2. FTP the compressed package ZIP file to the /opt directory.

3. Change directory to /opt.

4. Unzip the compressed package file. For example:

unzip RMC100Solaris64.zip

Running Setup The setup application can be run multiple times. When you run setup, the application:

• Moves the DB XML database data and schema directories to default location

• Checks host machine environment to ensure it meets the applications required configurations.

• Provides a means to apply a valid AcmePacket license

• Provides a means to choose between running browser client access via HTTP or HTTPS

• Lets you configure service requirements

Initialization Process Once executed, the setup script performs an initialization process that:

• Sets up proper directory and file permissions

• Transfers the database to a default location

• Checks system for minimum requirements

For example:




Run Setup To run the setup application:

1. Login as root.

2. Change directory to ACMEPacket/RMC100/bin.


3. Run the setup script.

./setup.sh

After a successful initialization, you can either perform a typical or custom installation of Net-Net RMC.




Installing Net-Net RMC

When you install Net-Net RMC, you need to perform a typical installation. The custom installation is not available for the Version 1.0 release.

Choosing the Installation Method

To choose installation method:

1. Enter 1 for Typical installation and press Enter. You are prompted about continuing. For example:

2. Enter Y to continue and press Enter. You now begin the typical installation.

Typical Installation To perform a typical installation:

1. Enter Y to continue and press Enter. The following appears:

2. Enter 1 and press Enter. You are prompted to continue.

3. Enter Y and press Enter to continue. The Typical configuration options appear.




4. Enter 1 and press Enter to check and apply the license. You are prompted to continue.

5. Enter Y and press Enter to continue. The system checks for an existing license. For example:

Accept License To accept an existing license:

1. Press Enter to accept the default. You are prompted to continue.

2. Press Enter to accept default. The license is accepted and the configuration options appear. From here you can configure HTTP/HTTPS.

Applying a New License

To apply a new license:

1. Enter 2 and press Enter to apply a new license. You are prompted to continue.

2. Enter Y and press Enter to continue. You are prompted to specify the source directory and file name of the license.




3. Enter the source directory and file name and press Enter. For example:, /opt/Licenses/AcmePacketNetNetEMS.xml.

4. Press Enter. The valid license is loaded and the contents are displayed.

5. Review the license information before applying it.

6. Press Enter to accept the license. You are prompted to continue.

7. Enter Y to continue and press Enter

8. From here you setup HTTP/HTTPS configuration. Continue with the next set of instructions to configure HTTP or skip to HTTPS on page 16 for configuration instructions.

HTTP 1. Enter 2 to perform HTTP/HTTPS configuration and press Enter. You are prompted to continue.

2. Enter Y and press Enter. The configuration options appear.

3. Enter 1 to configure HTTP mode and press Enter. You are prompted about continuing.

4. Enter Y to continue and press Enter. You are prompted for the user name.

5. Retain the default value nnems or enter another user name and press Enter. You are prompted for the group name.




6. Retain the default group name nnems or enter a new one and press Enter. You are prompted for the port number.

7. Retain the default value 8080 or enter the port number the HTTP server should listen on and press Enter.

HTTP is configured and you are prompted to configure Net-Net RMC. See Configuring Net-Net RMC Properties on page 19.

HTTPS To configure HTTPS:

1. Enter 2 to perform HTTP/HTTPS configuration and press Enter. The configuration options appear.

2. Enter 2 to configure HTTPS and press Enter. You are prompted about continuing.

3. Enter Y and press Enter to continue. You are prompted for the user name.

4. Retain the default value nnems as user name or enter a new one.

5. Press Enter. You are prompted for the group name.

6. Retain the default value nnems as the group name or enter a new one.




7. Press Enter. You are prompted for the port number the server should listen on.

8. Retain the default port number or enter a new one.

9. Press Enter. You are prompted for the server’s DNS name.

10. Enter the DNS name of the server and press Enter. You are prompted about creating a self-signed certificate.

No Self-Signed Certificate

11. Retain the default value No if you do not want to create a self-signed certificate. (Or skip to Creating Self-Signed Certificate on page 18 to create a self-signed certificate.)

12. Press Enter. You are prompted about continuing.

13. Enter Y to continue and press Enter. You are prompted for the private key file.

14. Enter the file name, including the path, and press Enter. You are prompted for the certificate file.

15. Enter the file name, including the path, and click Enter. You are prompted about intermediate certificates.

16. Press Enter to accept the default. You are prompted about continuing.

17. Enter Yes to continue. You are prompted for the alias name for the certificate in the truststore.

18. Press Enter to accept the default or enter a different alias name and press Enter. You are prompted for the trustore password.

19. Press Enter to accept the default or enter a different password and press Enter. You are done configuring typical options and are prompted to configure Net-Net RMC properties.




Creating Self-Signed Certificate

To create a self-signed certificate:

1. Enter 1 if you want to create a self-signed certificate and press Enter. You are prompted about continuing.

2. Enter Y to continue and press Enter. You are prompted for the common name (DNS name) of the server.

3. Enter the DNS name of the server and press Enter. You are prompted for the certificate alias name in the trustore.

4. Retain the default or enter a different alias name and press Enter. You are prompted for the trustore password.

5. Enter the trustore password and press Enter. You are done configuring typical options and are prompted to configure Net-Net RMC properties.




Configuring Net-Net RMC Properties

To configure Net-Net RMC properties:

1. Press Enter to accept the default choice 3. You are prompted about continuing.

2. Enter Y and press Enter. The number of backups parameter appears.

3. Retain the default value of 10 or enter a new value ranging from 1 to 500.

4. Press Enter. You are prompted for the SAML Single sign-on configuration.




Configuring SAML Single Sign-On

Net-Net RMC supports login through an external server using SAML single sign-on. You enter a username and password used in the request to the external server for authentication.

If using self-signed certificates, you can import into the Net-Net RMC certificates file (cacerts).

To configure SAML single sign-on:

1. Press Enter to accept the default value 4. You are prompted about continuing.

2. Enter Y and press Enter. The

3. Enter the username for basic authentication and press Enter. You are prompted for the password.

4. Enter the password required for basic authentication and press Enter. You are prompted about importing a certifcate.

5. Retain the default value No if you do not want to import a certificate. You are prompted about continuing.

If you do want to import a certificate, see the following section for details.




6. Enter Y and press Enter to continue. You are done configuring SAML single sign-on.

7. Press Enter to quit setup. You are prompted about continuing.

8. Enter Y and press Enter to quit the setup program.

Importing Certificates To import certificates:

1. Enter 1 and press Enter to import certificates. You are prompted about continuing.

2. Enter Y and press Enter. You are prompted for the responder server IP address.

3. Enter the IP address and press Enter. You are prompted for the responder server port number.

4. Retain the default value or enter a port number and press Enter. The import process starts and you are prompted to choose the certificate you want to import.

5. Enter 1 and press Enter to choose the certificate. You are prompted about continuing.

6. Enter Y and press Enter to continue. The import occurs and the certificate is added to the cacerts file using the alias sane. The Main Menu appears.




7. Press Enter to quit setup. You are prompted about continuing.

8. Enter Y and press Enter to quit the setup program.

Starting Servers To start the server:

1. Log into host machine as root.

2. Navigate to EMS/RMC bin directory.

cd /opt/AcmePacket/RMC100/bin

3. Run the start up script.

./startrmc.sh &

Changing User to nnems

You need to follow this process each time you run the setup script as root user.

To start servers as nnems user:

1. Change directory to where Net-Net RMC is installed.

2. Change owner of AcmePacket from root to nnems using the following command:

# chown –R nnems ACMEPacket

3. Change group of AcmePacket from root to nnems using the following command:

# chgrp –R nnems ACMEPacket

4. Logout.

5. Login as nnems.

6. Navigate to the RMC bin directory.

7. Start the server using the startrmc.sh script.

Shutting Down Servers

To shut down the server:

1. Log into host machine as root.

2. Navigate to EMS/RMC bin directory.


3. Run the shut down script.

#./shutdownrmc.sh &

Uninstalling Net-Net RMC

Currently only the system administrator can uninstall Net-Net RMC. You need to make sure there are recent backups of the database and the archive directory.

To uninstall Net-Net RMC:

1. Log into the RMC server as root.

2. Navigate to the directory where Net-Net RMC is installed.




cd /opt/ACMEPacket

3. Choose the RMC version that is to be uninstalled and remove the directory and all its children directories as follows:

ls –al

drwxr-xr-x 4 root root 4096 Mar 9 10:00 db

drwxr-xr-x 2 root root 4096 Mar 15 19:17 RMC100

drwxr-xr-x 5 root root 4096 Mar 9 10:01 RMCArchive

rm –Rf RMC100

If you need to delete the XML database, you need to also delete the db directory. Ensure you have a recent backup of the database.

4. Remove the directory.


./ start_DB_ColdBackup.sh

cd /opt/ACMEPacket

ls –al

drwxr-xr-x 4 root root 4096 Mar 9 10:00 db


rm –Rf db

If you need to delete the RMC archive directory, ensure you first store the archive directory contents in another directory.

5. Remove the archive directory:

#cd /opt/ACMEPacket

# cp –R RMCArchive <storagediretory>

# ls –al <Enter>


#rm –Rf RMCArchive

Backup and Restore Servers

If you have administrator privileges, you can back up your servers either while they are shutdown or while still running. If you want to backup a server while it is running, tell any user working on that server to minimize their usage during backup.

Backing Up with Server Shutdown

Backing up while the server is shutdown is a cold backup. After all backups are complete, you can restart the servers.

1. Shutdown all servers you want to backup.

2. Log in as administrator.

3. Change directory to the following:


4. Run the coldbackup script.

./backupcold.sh

The backup process runs.




Backing Up with Server Running

Backing up while the server is running is a hot backup. You need to tell all users of the server to minimize their system usage during hot backup process.

Note: Remember to tell any user on the server to minimize their system usage during backup.

1. Inform users to minimize their server usage.

2. Ensure the server is running.



cd /opt/AcmePacket/RMC100GA/bin

5. Start the hot backup script.

./backuphot.sh

The backup process runs.

Restoring Database Backups

You need to shutdown all servers on which you are restoring database backups. If restoring database backups on servers in a cluster, you need to restore databases on each one.

1. Shutdown all servers you plan to restore backups on.



cd /opt/AcmePacket/RMC100GA/bin

4. Start the database restore script.

./restoredb.sh

The database restoration process runs.



2 Using Net-Net RMC

Introduction

This chapter explains how to use the Net-Net RMC.

Basic Functionality

Net-Net RMC lets you easily update local route table (LRT) data on a single device or on multiple devices. With Net-Net RMC, you can provision large LRTs across multiple Net-Net SBCs and Net-Net Session Routers for numeric-based routing. Net-Net RMC lets you:

• Import a comma-separated values (CSV) file containing routing information

• Build an XML route table from the CSV contents

• Assign a list of devices to the route set

• Generate a LRT file from the route set

• Push the LRT file to all assigned devices

• Refresh the LRT data on the device using the LRT file that was pushed

• Backup, restore, and rollback route sets

Basic Components When using Net-Net RMC you are working with CSV files, LRT files, route sets, routes, and devices.

CSV Files You import CSV files to build XML route tables. The minimum fields required in a CSV formatted record for an import file are:

• operation

• public identifier (pub-id): a public identifier in the form of a telephone number or prefix (for example, NPA-NXX) used in LRT lookup. It is referred to in the LRT XML as object “user” of type “E164”.

• Session establishment data (SED or the formula and the associated fields required to generate SED): identified in the LRT XML as the object “next” of type “regex”. SED can be directly imported or edited or it could be the result of the record’s formula. The regex in the LRT file is the URI scheme used by the network attribute to route the call.

Any other combination of fields can be empty, unless they are included in the formula field of the record for which an error should be reported in the import log.

A formula specified in Net-Net RMC during import is applied globally and stored with each record during the import operation. A value supplied in the formula field of a record has precedence over the formula specified in Net-Net RMC during the import process.

The order and preference determines the order of the numbers in the XML file. The lowest number appears first.

Version 1.0 Acme Packet, Inc. Technical Publicatons 25


USING NET-NET RMC

isted here.

s an exampleltiple routes to me destination. of appearance LRT file s preference.

LRT File The process of creating a LRT file starts with importing individual routes from a CSV file. These routes are stored in the database and grouped into a route set. The database also contains a list of devices that the LRT file resides upon. This list is used when an update task refreshes the LRT information for a specific route set.

The LRT file is gzipped and placed at a specified location on the device. Once the file has been successfully transferred to a device, an action can be issued to each device to load the file. The LRT file location on the device is /code/lrt. You can also import an LRT file from a device into Net-Net RMC.

The following example shows an LRT file meant for distribution to devices.

<?xml version="1.0" encoding="UTF-8"?>

<localRoutes>

<route>

<user type="E164">9999999</user>

<next type="regex">!^.*$!sip:[email protected]:5060!</next>

</route>

<route>

<user type="E164">98888888</user>

<next type="regex">!^.*$!h323:\[email protected]:1720!</next>

</route>

<route>





</route>

<route>

<user type="E164">7817654321</user>


</route>

<route>

<user type="E164">9817654321</user>


</route>

<route>



</route>

</localRoutes>

The SEDrepresen

Here iof muthe saOrderin thedictate



USING NET-NET RMC

Route Set A route set contains a group of routes. It is used to create a LRT file and can contain up to ten entries with the same pubid, or ten alternate routes to the same destination.

The following table lists the route set properties along with their definitions.

Property Definition

Order Numerical value used as a mechanism for sorting the display of route records in the application or order the output of routes in the LRT that have the same pub-id. The order of display or output is lowest numerical value to highest.

Preference Numerical value used as a mechanism for sorting the display of route records in the application or order the output of routes that have the same pub-id and order. The order of display or output is lowest numerical value to highest.

Destination Group Group of public identifiers that have an object in common. That object stores information that can be used to select a subset of the route set for an operation, for example for global replacement.

Next Hop IP address, FQDN, session agent name, or session agent group name that can be used in the formula to generate the SED for a route record.

Trunk Group Alphanumeric string that can be used in the formula to generate the SED for a route record.

Trunk Context Alphanumeric string that can be used in the formula to generate the SED for a route record.

Routing Number (RN) Telephone number or prefix that can be used in the formula to generate the SED for a route record.

Carrier identification code ($CIC) Numeric value that can be used in the formula to generate the SED for a route record.

User 1 through User 5 Alphanumeric value that has a user-specific definable meaning that can be used in the formula to generate the SED for a route record. It can also be used for aggregating route records into groups. Once defined, use of this field must be consistent within the route set.

Formula Alphanumeric string that contains an expression used to define string concatenation and text replacement to generate the SED for a route record.



USING NET-NET RMC

Accessing the Net-Net RMC GUI

You can access the Net-Net RMC by HTTP login, using the following address formats:

http://<RMC server IP address>:8080

https://<RMC server IP address>:8443

To access the Net-Net RMC GUI:

1. Open a Web browser.

2. Connect to the Net-Net RMC server using one of the following address formats:

http://<RMC server IP address>:8080

https://<RMC server IP address>:8443

The Login screen appears.

3. Enter your user name and password and click Login. (The default username is admin, with a default password of admin.)

SAML Single Sign-On You can also access Net-Net RMC by a login URL that accepts a key parameter to allow for SAML single sign-on authentication. When the parameter is passed the normal username and password are replaced with a progress message.

For example:

https://172.33.2.12/login.html?key=<artifact>

The <artifact> is base-64 encoded.



USING NET-NET RMC

You have now accessed Net-Net Route Manager Central.

Overview of Net-Net RMC GUI

The Net-Net RMC GUI is divided into the following areas:

• Menu bar: The menu bar houses the drop down lists for administration, help, monitoring tools.

• Navigation bar: Contains route management, user management, and device management.

• Body area: The main body is the content view where the routing information is displayed in the appropriate forms.



USING NET-NET RMC

Menu Bar The menu bar across the top of the screen contains sets of functions you can perform organized into different categories (menus). You click a menu to access a list of options, from which you then select the function you want to perform.

The following table lists the menus and their options; including a brief description.

Navigation Bar The left pane is called the Navigation bar. The Navigation bar is divided into categories represented by sliders.

The Navigation bar contains the following categories:

Menu Menu Option Description

File Logout Exit Net-Net RMC.

Tools Change password Change the password used to login to Net-Net RMC.

Settings Edit the login banner Edit the information that appears in the banner at login.

Help License Information Access the Net-Net RMC license information

About Access Net-Net RMC version information.



USING NET-NET RMC

• Devices: displays the list of managed devices that you can work with in route management.

• Route Management: where you work with devices, route sets and configure backup and restore.



USING NET-NET RMC



USING NET-NET RMC

• Security: contains the user management and audit log functionality. User management lets you create groups of users, users, set password rules, configure the inactivity timer, and configure the password interval. The audit log functionality lets you view the audit log, save it to a file, and set an automatic purge interval or manually purge the log.



USING NET-NET RMC

Content Area The content area is your work area. As you navigate through Net-Net RMC, the forms for configuration entries and results from searches are displayed here. The following example shows the information that appears in the content area when you choose Groups from User Management, which is located under the Security slider.:



USING NET-NET RMC

Viewing Net-Net RMC License Information

This section explains how to view the Net-Net RMC license information.

To view license information:

1. From the Help menu, choose License Information. The Net-Net RMC License Information window appears:

2. Scroll the Signature information by clicking the arrows.

3. Click Reload License to reload the license information.

4. Click Cancel to cancel the window.



USING NET-NET RMC

Managing Users

If you have the appropriate privileges, you can create new users and new user groups, and set group-based authorization where users are assigned to groups with different levels of authorization.

Setting authorization means you assign permissions to the group to which a user belongs. The permissions for that group are also assigned to the user. When a user logs into Net-Net RMC, they can access features and functionality based on the permissions assigned to them.

About Groups and Users

You can create new users or new groups of users, and control the different security levels of Net-Net RMC by assigning permissions. You can manage the following functions:

• Provide group-based authorization where users can be assigned to groups that have configured levels of authorization, and that provide specific authorizations to a user.

• Provide fine-grained access control for specific groups, views, and operations. Limit the access for some users to specific features and functionality.

About Groups A group is a logical collection of users grouped together to access common information or perform similar tasks. You assign specific permissions to a group, and then assign users to it. Those users in turn, inherit the group-based permissions.

The following groups are created by default when Net-Net RMC is installed:

• LIAdministrators can perform all operations except changing the admin password privilege.

• administrators can perform all operations except changing admin password privileges and LI configurations.

• provisioners can configure Net-Net SBCs with the exception of lawful intercept (LI) configurations. They can save and apply configurations to Net-Net SBCs.

• monitors can only view data. This group has the fewest privileges.

About Users A user is an individual entity which logs into Net-Net RMC and is configured to perform a set of Net-Net RMC-related operations. Before a user can access Net-Net RMC operations, they must be added as a user to the RMC server database. After you have created users, you can add them to user groups and the user privileges for that group will apply to the user.

After logging into Net-Net RMC, the operations available to a user are based on the group to which the specific user belongs.

The following users are created by default when Net-Net RMC is installed:

• LIAdministrator can perform all operations except changing the admin password privilege.

• admin can perform all operations except changing admin password privileges and LI configurations



USING NET-NET RMC

About Operations Operations are all the operations you can perform using Net-Net RMC, such as adding routes to route sets and assigning route sets to devices. You provide or deny access to these operations by assigning them permissions.

About Permissions Permissions include allowing or disallowing a user from performing operations. Most of the time permissions are assigned on the group level and are propagated to all users who belong to the group.

When you assign configuration permissions, you are assigning that permission to each configuration operation for that element.

Accessing User Management

To access user management:

1. While logged into Net-Net RMC, expand the Security slider in the Navigation bar.

2. Expand the User Management directory.

From here you can access all user management functionality.

Creating User Groups

To create user groups:

1. Click Groups in the Navigation bar. A table of user groups appears in the content body.

2. Click Add. The Add Group dialog box appears.

3. Group name—Enter a name for this group using the following guidelines:

• minimum of 3 characters and maximum of 50

• name must start with an alphabetical character

• alphanumeric characters, hyphens, and underscores are allowed

• case insensitive

• cannot be the same as an existing user name



USING NET-NET RMC

4. Group permissions copy from—Choose an existing group from the drop-down list or choose None to manually configure the permissions.

5. Click OK. A message appears indicating success.

6. Click OK to clear the message.

If you did not choose to inherit permissions from an existing group, you need to configure them.

Configuring Permissions

To configure permissions:

1. Click the group in the table and click Edit. The permissions appear in the content area divided into four categories you access by clicking the appropriate tab.

2. Click the checkbox of the permission you want to assign. Some permissions are organized into directories. You can either assign the permission at the top level for all permissions or you can assign them individually.

Creating Users To create users:

1. Click Users in the Navigation bar. A table of users appears in the content body.

2. Click Add. The Add User dialog box appears.

3. Assigned group—Choose the group to which you want to add the user. The permissions for that group apply to this user.

4. User name—Enter the user’s name using the following guidelines:

• minimum of 3 characters and maximum of 50

• name must start with an alphabetical character

• alphanumeric characters, hyphens, and underscores are allowed

• case insensitive

• cannot be the same as an existing group name

5. Password—Enter the password for this user.

6. Confirm password—Enter the password for this user again to confirm it.

7. Account—Enter the number of days after which the user’s account expires. Entering 0 means the account will not expire.



USING NET-NET RMC

8. Password—Enter the number of days after which the password expires. You must enter a value less than what is set for account expiration.

9. Click OK.

Changing Passwords If you have administrative operations permission, you can change a user’s password.

To change a user password:

1. Click a user from the table and click Change Password. The Change Password dialog box appears.

2. New password—Enter the new password for this user.

3. Confirm new password—Enter the new password for this user again to confirm it.

4. Click OK.



USING NET-NET RMC

Resetting Passwords If you have permission to reset passwords, you can reset user passwords.

To reset user passwords:

1. Click a user from the table and click Reset Password. The Reset Password window appears prompting for confirmation you want to reset the password.

2. Click Yes to reset it or No to exit the window and quit the reset process.



USING NET-NET RMC

Assigning Permissions

When you create a new user group or new user, you need to indicate which of the Net-Net RMC operations they can or cannot perform. This section describes the operations you can perform using Net-Net RMC. You assign permissions to these operations to allow or disallow groups of users, or individual users, the ability to perform them.

When you assign permissions to parent operations, the children automatically inherit the same permissions. To be able to assign permissions to individual operations you have to clear permissions from the parent (blank out the checkbox). This is important when assigning permissions at the user level.

Administrative The following table lists the administrative operations along with a brief description.

Operation Description

Administrative operations Set the permission levels for all of the following administrative operations.

Security administration Set the permission levels for all of the following security administration operations.

Group operations Set permissions for all the following group operations.

Add group Add a new group.

Update group Modify groups.

Delete group Delete existing groups.

User operations Set permissions for all the following user operations.

Add users Create new users.

Update users Modify user information.

Delete users Delete existing users.

Reset password Reset your password used to login to Net-Net RMC.

Change password Change another user’s password used to login to Net-Net RMC.

Change inactivity timer Change the inactivity timer, which logs off the user if the client is no longer being used.

Change Password Rule Configure the password rules used when creating a new user.

View all audit logs View the audit logs for all users.

View own audit log View only personal audit log.

Change audit log auto purge interval Configure the number of days of audit logs to keep.

Export audit logs Export all or part of an audit log to a file.

Manual audit log purge Manually purge audit logs.

View health monitor console Access health monitor console to detect issues.



USING NET-NET RMC

Changing the Password Rules

This section explains how you can change the password rules. The password rules determine the format of the passwords administrators enter when creating new users. For the two types of users, administrators and non-administrators, you can specify the:

• length of the password

• how many times it can be reused

• whether specific characters, such as a numeric value, can be used

Accessing Password Rules

To access the password rules:

1. From the Navigation bar, click Password rules. The password rule information appears in the content area.

Password Reuse Count

To set password reuse count for all users:

1. For all users—Enter a value that indicates the number of counts to use to prevent the reuse of a password. The reuse count restricts the user from reusing the password entered in the last x number of counts. For example, if you enter 2 here the user cannot reuse the same password used on the previous two occasions.

Administrator Password Length

To set the administrator password length:

1. Minimum length—Enter a value that indicates the minimum length of a password for a user with Administrator privileges. Range of values is 6 to 16 characters.

2. Maximum length—Enter a value that indicates the maximum length of a password for a user with Administrator privileges. Maximum value for this field is 16 characters.

Non-Administrator Password Length

To set the non-administrator user password length:

1. Minimum length—Enter a value that indicates the minimum length of a password for a user who does not have Administrator privileges. Range of values is 8 to 16 characters.

2. Maximum length—Enter a value for that indicates the maximum length of a password for a user who does not have Administrator privileges. Maximum value for this field is 16 characters.

Password Contents To choose password contents:

1. Numeric character—Click the checkbox to force the use of at least one numeric character from 0 to 9 in the password.

2. Alphabetic character—Click the checkbox to force the use of at least one character from the English language alphabet in the password.



USING NET-NET RMC

3. Punctuation character—Click the checkbox to force the use of at least one special or punctuation character in the password.

You cannot use the following special characters for a username or password:

asterisk (*)

backslash (\)

forward slash (/)

greater than (>)

lesser than (<)

ampersand (&)

double quotes (“)

single quote (‘)

question mark (?)

colon (:)

pipe (|)

4. Click Apply. The password rules are saved and the window closes.



USING NET-NET RMC

Modifying the Inactivity Timer

This section explains how to modify the inactivity timer. The inactivity timer logs off the user from the Net-Net RMC session when it’s value is exceeded. The user must re-enter their password to continue. You can set different values for a user with administrative permissions and users who do not have administrative permissions.

To modify the inactivity timer:

1. From the Navigation bar, click Inactivity timer. The inactivity timer information appears in the content area.

2. Admin—Enter the number of minutes of inactivity after which the user with administrative permissions is logged off. A value of zero (0) disables the inactivity timer.

3. Non-Admin—Enter the number of minutes of inactivity after which the non-administrator user is logged off. A value of zero (0) disables the inactivity timer.

4. Click Apply.



USING NET-NET RMC

Audit Logs

The audit log provides information about the changes made using the Net-Net RMC. The audit log contains audit trails. Audit trails enable you to view all operations that have been performed, the time they were performed, whether they were successful, and who performed them.

Viewing Audit Logs

To view audit logs:

1. In the Navigation bar, click View. The audit log table appears in the content area.



USING NET-NET RMC

2. Click a row in the table and click Details. The Audit log details window appears.

Audit trails include the following information:

• Name of the user who performed the operation

• Time the operation was performed by the user

• Category of operation performed by the user

• Specific operation performed by the user

• Address of the management server accessed

• IP address of the client that was used

• Device the user performed operation upon

• Status of the operation performed by the user, whether it was successful or failed

• Description of the operation

3. Click OK to exit the window.

4. Click Save to file to open the audit log file or save it to a file.



USING NET-NET RMC

Searching the Audit Log

You can search the audit log using one or more criteria.

To search the audit log:

1. Click the Search button. The Audit Log Search dialog box appears.

2. Username:—Choose a user name from the drop-down list.

3. Category:—Choose a category from the drop-down list.

4. Operation:—Choose an operation from the drop-down list.

5. Management Server:—Enter the IP address of a management server.

6. Client IP:—Enter the IP address of a client.

7. Device:—Enter a device IP address.

8. Status:—Choose a operation status from the drop-down list.

9. Start Time:—Choose a start time from the calendar.



USING NET-NET RMC

10. End Time:—Choose a start time from the calendar.

11. Click OK to search using the configured criteria.

12. Click Show All to re-display all audit log entries.



USING NET-NET RMC

Purging Audit Log Files

If you have the permission assigned, you can configure the number of days of audit logs to keep. You can also manually purge audit logs.

To purge audit log files:

1. In the Navigation bar, click Purge. The Purge audit logs information appears in the content area.

2. Interval in days:—Enter the number of days for which you want to keep audit logs.

3. Click Apply.

Manually Purging To manually purge audit logs:

1. With the purge audit log information displayed in the content area, click Purge. The Manual Audit log purge dialog box appears.

2. Purge audit log records prior to—Choose the date from the calendar prior to which you want audit logs purged.

3. Click OK.



USING NET-NET RMC



3 Managing Route Sets

Overview

This document describes how to manage route sets. Route sets are a collection of route entries. The routes contained in the route set are imported from multiple CSV files or entered via the RMC GUI. Route sets are associated with devices. They can be associated with one or multiple devices.

Route sets have a version that is incremented the first time after you commit the result of an operation:

• Importing from a CSV file

• Editing a route

• Deleting a route

• Restoring from a device

Property Definitions

The following table lists the route set properties along with their definitions.

Property Definition

Order Numerical value used as a mechanism for sorting the display of route records in the application or order the output of routes in the LRT that have the same pub-id. The order of display or output is lowest numerical value to highest.

Preference Numerical value used as a mechanism for sorting the display of route records in the application or order the output of routes that have the same pub-id and order. The order of display or output is lowest numerical value to highest.

Destination Group Group of public identifiers that have an object in common. That object stores information that can be used to select a subset of the route set for an operation, for example for global replacement.

Next Hop IP address, FQDN, session agent name, or session agent group name that can be used in the formula to generate the SED for a route record.

Trunk Group Alphanumeric string that can be used in the formula to generate the SED for a route record.

Trunk Context Alphanumeric string that can be used in the formula to generate the SED for a route record.



MANAGING ROUTE SETS

Accessing Route Sets

To access route sets:

1. Under the Route Management area of the navigation pane, click Route Sets. The is displayed in the right pane.

From here you can add new route sets and work with existing route sets.

Routing Number (RN) Telephone number or prefix that can be used in the formula to generate the SED for a route record.

Carrier identification code ($CIC) Numeric value that can be used in the formula to generate the SED for a route record.

User 1 through User 5 Alphanumeric value that has a user-specific definable meaning that can be used in the formula to generate the SED for a route record. It can also be used for aggregating route records into groups. Once defined, use of this field must be consistent within the route set.

Formula Alphanumeric string that contains an expression used to define string concatenation and text replacement to generate the SED for a route record.

Property Definition



MANAGING ROUTE SETS

Customizing the Display

You can change the route set table display by changing the columns that are displayed and/or the order of table entries.

To customize the table display:

1. Position the cursor over a column heading. An arrow appears on the right side of the box. For example:

2. Click the down arrow to display the menu. For example:

3. Click Sort Ascending to order the route sets by ascending or Sort Descending.

4. Click Columns to access a list of column names. For example:

5. Click a marked checkbox to hide that column or click an empty checkbox to display that column.

6. Click elsewhere in the display to clear the menus.



MANAGING ROUTE SETS

Adding Route Sets To add new route sets:

1. From the Route Sets tab, click Add. The Add Route Set dialog box appears.

2. Name—Enter a name for the new route set using alphanumeric characters without spaces.

3. Device LRT configuration name—Enter the configuration name of the LRT associated with the route set. This value must match the configured name on the device.

4. Device LRT file name—Enter the name you want to use for this LRT file. The file name must match what is in the device’s configuration.

5. Optional. Enter a description and notes.



MANAGING ROUTE SETS

6. Populate from existing route set—If you want to populate the new route set with data from an existing route set, choose the source route set from the drop-down list.

7. Click OK. The new route set appears in the Route Sets table.



MANAGING ROUTE SETS

Working with Existing Route Sets

You can work with the existing route sets displayed in the table.

Editing Route Sets To edit a route set:

1. Click a row in the table to select route set and click Edit. The Edit Route Set dialog box appears.

2. Add a description and/or notes to your route set. You cannot edit any of the other parameters.

3. Click OK to save your edits.

Copying Route Sets

To copy a route set:

1. Click the row for the route set you want to copy and click Copy. The Copy Route Set dialog box appears.

2. Name—Enter a name for the route set copy.

3. Retain the default value or enter a new configuration name.

4. Retain the default or enter a new file name.

5. Optional. Enter a description and/or notes for the copy.



MANAGING ROUTE SETS

6. Retain the default existing route set from which you want to populate the cop or choose a new one from the drop-down list. You can also choose not to populate from an existing route set.

7. Click OK.



MANAGING ROUTE SETS

Viewing Associated Devices

To view associated devices:

1. Click the route set row in the table and click View Associated Devices. The Devices Associated with Route Set window appears listing the devices associated with that route set.

For example, the following image shows the HA pair associated with the route set named secondrs.

2. Click OK to close the window or click either Associate Devices or Update Devices to access additional functionality. See

Viewing LRT Files To view LRT files:

1. Click a row in the table and click View LRT File. A status message shows the progress of loading the LRT file. After the file is loaded, you are prompted to either open or save the file.

2. Open the file in an XML editor to review it or save the file.

Deleting Route Sets To delete route sets:

1. Click the route set row in the table and click Delete. A confirmation message appears.

2. Click Yes to continue with the deletion or No to exit.



MANAGING ROUTE SETS

Updating Devices

You can update the devices for route sets displayed in the Route Sets table. Check the Devices - Requires Updating #/Total # column to identify those route sets that require updating.

To update devices:

1. Click the route set in the table that has devices requiring update. The Update Devices button becomes active.

2. Click Update Devices. The Add Update Task information appears.

3. Name—Retain the default update task name or enter a new one.

4. Notes—Enter text for the optional notes.

5. Select the device in the Route Set Devices tree and click Add to add it to the Devices to Update list.

6. Repeat step 5 to select all the devices you want to update for the route set.

7. Click the radio button of the action you want taken if device update fails for any of the selected devices.



MANAGING ROUTE SETS

8. Click OK. The update process begins and an Update Task Details window appears displaying the progress.



MANAGING ROUTE SETS

Fail If the update task fails, the progress bar reflects the Failed status and a message appears in the Update Details table. For example:

The selected failover action occurs. If you selected a failover action of roll back, click the Rollback Details tab.

9. Click OK to exit the Update Task Details window.



MANAGING ROUTE SETS

Success If the update task succeeds, the progress bar reflects the Completed status and the devices appears under the Status:Completed section of the table. For example:

1. Click OK to exit the Update Task Details window. The Device Route Set Updates tab appears.

2. Click Commit to save the device updates.



MANAGING ROUTE SETS

Importing Route Sets

When you import CSV, column definitions and minimum fields are required in the file. Formulas specified in Net-Net RMC during the import process are applied globally and stored with each record during the import.

A value supplied in the formula field of a record has precedence over the formula specified in Net-Net RMC during import. Order and precedence determine order of the numbers in the XML file, with the lowest appearing first.

You specify the CSV file and the file format. Then you allow mapping of CSV columns to RMC properties. Finally, you see a confirmation of what will be imported, including a display of errors.

To import route sets:

1. In the Route Sets table, click the row of the route set for which you want to import routes and click Import Routes. The Route Set Import - Step 1 - File Selection information appears.

2. File—Browse to the file you want to import.

3. Does the file contain a header line—Click the appropriate radio button.

4. File delimiter—Choose the file delimiting method from the drop-down list.

5. Template to use—Choose the template from the drop-down list, or leave this field blank.

6. Click Next. The Route Set Import - Step 2 - CSV Column Alignments information appears.

7. Select the corresponding CSV column from the drop-down list to map to each property listed. If you map a CSV column to the SED property, the two formula properties are disabled. If Session Establishment Data is mapped to a column in the CSV file, that SED is used for the route and the formula, if specified, is ignored.

Note that if you use a template in Step 5, this mapping is already defined.

The value for the Operation property must be either:

• add to add the route

• delete to delete the route

Modify works by having two rows in the CV, a delete row and an add row.



MANAGING ROUTE SETS

8. If formula properties are displayed, enter a formula. The formula is used to create the SED.

9. Save mappings to a template, if not already specified in an earlier step, by enter a name for it in the Save as Template textbox.



MANAGING ROUTE SETS

10. Click Next. The Route Set Import - Step 3 - Confirmation appears showing a sample of what will be imported and displaying any errors. If the number of errors exceeds a certain amount, the Finish button is disabled.

11. If there are errors, click Back and correct your mappings.

12. Click Finish.



MANAGING ROUTE SETS

Managing Routes in Route Sets

You manage the routes in the existing route sets. For information about importing route sets, see the information in the prior section.

To manage routes:

1. Click a route set in the table and click Manage Routes. The Route Set Edit tab for that route set appears. The default view is of routes organized by pub-id.

2. Click the Session Establishment Data (SED) to view route sets organized by SED. For example:



MANAGING ROUTE SETS



MANAGING ROUTE SETS


You can customize the information displayed on the tab.

To customize the display:

1. Position the cursor in the column heading. An arrow appears at the right side of the box.

2. Click the down arrow to display the following menu.

3. Click Columns to display the following menu.

4. Click the empty checkboxes to display hidden columns or click the marked checkboxes to hide displayed columns.

5. Click elsewhere in the display to clear the menu.



MANAGING ROUTE SETS

Searching for Routes

You can search for routes by pub-id, SED, and/or other properties. You can use the asterisk (*) as a wildcard for a partial substring match and the question mark (?) for character match for all the property fields except SED and formula.

To search for routes:

1. Click the Search button. The Route Search dialog box appears.

2. pub-id—Enter the public identifier you want to use as search criteria.

3. Session Establishment Data (SED)—Enter the SED you want to use as search criteria.

4. Enter values for the advanced properties if you want to use them as search criteria. See for definitions.

5. Click Search. The results of the search are displayed.

Adding Routes To add routes to route set:

1. On the Route Sets tab, click Add. The Add Route dialog box appears.

2. pub-id—Enter the public identifier for this route.

3. Session Establishment Data (SED)—Enter the SED for this route.

4. Optional. Enter additional property values if needed.



MANAGING ROUTE SETS

5. Formula—Enter the formula

6. Click OK.

Replacing Route Properties

You can replace a property for multiple routes based on search criteria.

To replace route properties:

1. On the Route Set Edit page click Replace. The Route Replace All dialog box appears.

2. Enter the search criteria such as pub-id, SED, and/or other property values. You can use the wildcard values asterisk (*) and question mark (?).



MANAGING ROUTE SETS

For example, to search for pub-id 123456789 to replace the current Order value of 10 with 25

3. Click Replace. A confirmation message appears, For example:

4. Click Yes to continue. A progress message appears and the replacement is made.



MANAGING ROUTE SETS

Searching Routes

You can search route sets for a specific pub-id.

To search route sets:

1. Click the Route Search tab.

2. Enter the pub-id to use as search criteria. You can use the asterisk (*) as a wildcard.

3. Click the checkboxes for each route set you want to search.

4. If you want to filter by device, choose device from drop-down list. The route sets are checked for the device.

5. Click Search. The results appear at the bottom of the screen. You can page through the results and refresh the display.

6. Select a row in the display and either click Edit to access the Edit Route dialog box to modify the route or click Delete to delete the route from the route set.

Editing Routes To edit routes:

1. In the Edit Route dialog box, edit existing information or enter new information in empty textboxes.

2. Create a formula using the properties contained in the route.

3. Click OK.



MANAGING ROUTE SETS

Comparing Route Sets

You can compare two route sets. For example, before performing an update you can compare the contents of your route set with the one in the LRT file currently active on the Net-Net SBC. The differences between the two route sets are highlighted in yellow.

To compare route sets:

1. In Route Sets, click the Route Set Compare tab.

2. Route Set 1:—Choose the first route from the drop-down list.

3. Route Set 2:—Choose the second route from the drop-down list. The Compare button is activated.

4. Click Compare. A progress bar appears while the comparison is done. When complete, the results are displayed in two columns at the bottom of the screen. If the contents are identical between the two, messages appear in both columns.

Managing Import Templates

You can manage your existing import templates and add new ones.

Accessing Import Templates

To access import templates:



MANAGING ROUTE SETS

1. In the Route Sets window, click Import Templates. A table of import templates appears.

From here you can add new import templates and edit existing ones.

Adding Import Templates

To add import templates:

1. In the Import Templates window, click Add. The Add Import Template dialog box appears.

2. Name—Enter a name for the new import template.

3. Map the properties to the corresponding row in the CSV file. You choose the row number from the drop-down list. For example:

4. Enter the next hop formula that will generate the SED.

5. Click OK. The template is created.



MANAGING ROUTE SETS

Editing Import Templates

To edit import templates:

1. Click an import template in the table. The operation buttons are activated.

2. Click Edit. The Edit Import Template dialog box appears.

3. Make the edits you need to the properties and/or formula.

4. Click OK.

Copying Import Templates

To copy import templates:

1. Click the row of the import template you want to copy in the table and click Copy. The Copy Import Template dialog box appears.

2. Name—Enter a name for the import template copy.

3. Map properties to the corresponding rows in the CSV file.



MANAGING ROUTE SETS

4. Enter a formula.

5. Click OK.



4 Working with Devices

Overview

Devices are the Net-Net SBCs managed through Net-Net RMC. Using Net-Net RMC, you work with those managed devices when managing and distributing route set information.

About Managed Devices

You can view a list of all devices being managed. From this list, all or some of them will appear in the Devices list under Route Management.

Accessing All Devices

To access a list of all devices:

1. Under the Devices area of the Navigation bar, click Devices. A table of all managed devices appears.

2. Click Refresh to update the table contents.

From here you can add or remove managed devices.

Adding Managed Devices

To add a managed device:

1. Click Add. The Add Device dialog box appears.

2. IP address 1—Enter the first IP address of the device.

3. IP address 2—Enter the second IP address of the device.

4. SNMP community name—Enter the name of the SNMP community configured on the device.

5. SNMP port—Enter the SNMP port number configured on the device.

6. User name—Enter the user’s name.

7. Password—Enter the user’s password.



WORKING WITH DEVICES

Working with Devices in Route Management

This section contains information about working with the managed devices for route management.

Accessing Devices To access devices:

1. Under the Route Management area of the navigation bar, click Devices. The Device table is displayed in the content area.





You can change the device table display by changing the columns that are displayed and/or the order of table entries.

To customize the table display:

1. Position the cursor over a column heading. An arrow appears on the right side of the box. For example:

2. Click the down arrow to display the menu. For example:

3. Click Sort Ascending to order the devices by ascending or Sort Descending.

4. Click Columns to access a list of column names. For example:

5. Click a marked checkbox to hide that column or click an empty checkbox to display that column.

6. Click elsewhere in the display to clear the menus.




Working with Devices

You can work with the existing devices displayed in the table.

Viewing Route Sets Associated with Device

To view route sets associated with a device:

1. Click a row in the device table and click View Associated Route Sets. The View Device Route Set Details window appears.

2. Click OK to close the window.

Comparing LRT Files

You can compare an LRT file retrieved from a device against the current route set version.

To compare LRT files:

1. Click a row in the devices table and click Compare. The Select route set information appears.

2. Route Set—Choose the route set whose version of the LRT file you want to compare the LRT file retrieved from the device.

3. Click Compare. A message indicates the progress status and the results are displayed at in the Results area of the content area. Any differences are highlighted in yellow.

4. Click the Devices tab to return to the device table.




Retrieving LRT Files

You can retrieve an LRT file from a device to use in a new route set.

To retrieve LRT file from a device:

1. Click the device in the table and click Retrieve LRT file. The Retrieve LRT file from device dialog box appears.

2. New route set name—Enter a name for the new route set.

3. Device LRT configuration name—Enter the name of the device LRT configuration.

4. Device LRT file name—Enter the device LRT filename and choose the extension from the drop-down list.

5. Click OK.

Updating Device with Route Set

This section shows you how to update a device with a route set.

To update a device with a route set:

1. Check the Needs Updating column in the device table for the word Yes. This action indicates a device that needs updating, meaning the route set has been modified since it was last pushed to the device.

2. Click the Update Device button. The Add Update Task information appears in the content area.

3. Name—Retain the task name or enter a new one.

4. Notes—Add optional text for notes.




5. Select the device from the Route Set Devices column and click the Add button.

The device is moved to the Devices to Update column.

6. Repeat for each route set device you want to update.

7. Choose the failure action you want performed if failure occurs by clicking a radio button.

8. Click OK.




Associating Route Sets with Devices

This section explains how to associate route sets with a device. A device can be associated with one or multiple route sets, there is no limit.

To associate route sets with devices:

1. Click the Device Route Sets tab. The route set information appears in the content area.

2. Click a route set in the Route Sets column and either click Add or Add To All if you want to associate the route set with all devices shown in the devices column.

3. Repeat step 2 for each route set you want to associate with a device.

4. Click OK. A message appears indicating the association was updated successfully.

5. Click OK to clear the message.




Updating Devices with Route Sets

After you associate route sets with devices, you need to transfer those routes sets to the associated devices. You make the transfer by first configuring an update task and then activating the update. While an update task is in progress, the target device is locked to all other updates.

You can then choose to commit the update to the device or roll it back instead. Committing an update removes the lock on the target device and the update task from this table, while adding it to the table displayed on the Update Task History tab. Rolling back an update rolls back any changes made to the target device. (You cannot access the rollback function while an update task is in progress.)

Note: If the update task included multiple target devices and rollback fails on any one device, Net-Net Route Manager Central continues the rollback on all other devices.

Accessing Update Tasks

To access update tasks:

1. With Devices selected in the Navigation bar, click the Device Route Set Updates tab. The Update Tasks table appears in the content area.

2. Double-click an update task in the table to view details about it. For example:

3. Click OK to close the window.




Creating Update Tasks To create an update task:

1. In the Device Route Set Updates tab, click Update. The Add Update Task information appears in the content area.

2. Name—Retain the task name or enter a new one.

3. Notes—Add optional text for notes.

4. Select the device from the Route Set Devices column and click the Add or Add to All button.

The device is moved to the Devices to Update column.

5. Repeat for each device you want to update.

6. Choose the failure action you want performed if failure occurs by clicking a radio button.




7. Click OK. The Update Task Details window appears with a progress bar that indicates the status of the update process.

Also a new update task appears in the Update Tasks table. Once the update tasks completes, the information in the Update Task Details window is refreshed and indicates either update was a success or a failure.

If the update failed and you chose rollback as the action, you can click Retry Failures in the Update Task Details window to try the update again. Otherwise, exit the window and rollback the update.

Note: If the update fails because a targeted device is busy or locked, an error message appears.

8. Click OK to close the Update Task Details window.

Committing an Update If the update was a success, you can commit the update on the device.

To commit the update:

1. Click the successful update task in the Update Tasks table.

2. Click Commit. The update is committed on the target device and the update task is removed from the Update Tasks table. The lock on the target device is removed. Also, the table available on the Update Task History table is updated with the successful update task.




Rolling Back an Update

If the update failed and you chose rollback as the action upon failure, you can rollback the update.

To rollback an update:

1. Click the failed update task you want to rollback in the Update Tasks table.

2. Click Rollback. The rollback starts and a progress bar indicates the status of the rollback. The update task status is updated in the Update Tasks table and the lock is removed on the device. Also, the table available on the Update Task History table is updated with the update task.

Viewing Update Task History

You can view a history of all route updates made to devices and delete tasks from the history.

To view update task history:

1. With Devices selected in the Navigation bar, click the Update Task History tab. A table of update tasks appears in the content area.




2. To delete an update task from the history, click it in the table and click Delete. You are prompted for confirmation.

3. Click Yes to delete the task, No to exit without deleting.




Removing Managed Devices

To remove a managed device:

1. In the navigation bar, click Devices.

2. In the content area, click the row in the Device table corresponding to the device you want to remove. The row is highlighted to show your selection, and the Remove button displays in the content area.

3. Click the Remove button.




4. A dialog box appears, asking you to confirm the removal. Click Yes to proceed with the removal. Click No if you do not want to remove the device.

Proceeding with device removal will not interrupt an RM update of routing information or any administration device command in progress. If such an operation is in progress, an error message appears and the device will not be removed.



5 Backup and Restore Route Sets

Overview

This chapter contains information about how to backup and restore your route sets. When you restore a route set backup, you remove all edits made to the route set after the backup was made.

Accessing Route Set Backups

To access route set backups:

1. In the Navigation bar, click Backup/Restore. The Route Set Backups information appears in the content area.



BACKUP AND RESTORE ROUTE SETS

2. Click the Refresh tab to refresh the table display.

Searching for Backups

You can search for route set backups based on name only, name and date and time, or on date and time.

To search for route set backups:

1. Click the Search tab. The Backup Search dialog box appears.

2. Name—Enter the name of the route set backup.

3. Starting at—Choose the date from the calendar and the time from the drop down list.

4. Ending at—Choose the date from the calendar and the time from the drop down list.




5. Click Search. The results are displayed in the table.

6. Click Show All to redisplay all backups.




Scheduling Backups

You can schedule backups to run now, daily, or weekly. If you create a backup to run now, a scheduled task is created and listed in the scheduled tasks table. Once it runs, the scheduled task is removed from the table.

You can schedule a maximum of three backups for each type of backup. For example, for a route set named national, you can schedule three backups scheduled Now, another three scheduled Daily, and a final three scheduled Weekly.

To schedule backups:

1. Click the Route Set Scheduled Backups tab. The scheduled backups table appears.

2. Click Add. The Add Scheduled Backups dialog box appears.

3. Name—Enter the name of the route set backup.

4. Backup Directory—Retain the default backup directory or enter a new one, including the path.

5. Route Set—Choose the route set you want to backup from the drop-down list.




6. Click Now to create a backup task that will run immediately.

7. Click Daily to create a backup task that runs daily at the time you choose from the drop-down list.

8. Click Weekly to create a backup task that runs weekly at the time and on the day of the week you choose from the drop-down lists.

9. Click OK. The backup task is added to the table. If it is scheduled to run now, it is deleted from the table after the process completes.




Restoring Backups

When your restore a route set backup, you lose any edits made after the backup was done.

To restore route set backups:

1. On the Route Set backups tab, choose a route set from the table and click Restore. You are prompted about continuing with the backup.

2. Click Yes to continue and No to cancel. If you click Yes, a progress bar appears indicating the restore is occurring. After the restoration is complete, the route set version number is incremented.



net-net route manager central 1.0 user guide

Documents

allowed case

saml single

free software

emsrmc bin

groupadd nnems

intermediate

password reuse

restoring