MasterScope Network Manager 8.0 Release Notes - nec. · PDF file... Internet Explorer, Office and Excel are ... advocated by the PostgreSQL Global Development Group. ... command line

MasterScope Network Manager 8.0Release Notes

NVP00RE0800-01

CopyrightsThe information in this document is the property of NEC Corporation. No part of this document maybe reproduced or transmitted in any form by any means, electronic or mechanical, for any purpose,without the express written permission of NEC Corporation.

The information in this manual may not include all the information disclosed by NEC Corporation ormay include expressions that differ from information disclosed by other means. Also, thisinformation is subject to change or deletion without prior notice.

Although every effort has been made to ensure accuracy in producing this manual, NEC Corporationdoes not guarantee the accuracy or applicability of the information contained herein. In addition,NEC Corporation is not liable for any loss or damage incurred as a result of the use or non-use of thisinformation by any party.

Trademark• Microsoft, Windows, Windows Server, Windows Vista, Internet Explorer, Office and Excel are

the registered trademarks of Microsoft Corporation in the United States and other countries.

• Intel, Pentium, and Itanium are trademarks or registered trademarks of Intel Corporation or itssubsidiaries in the United States and other countries.

• UNIX is the registered trademark of The Open Group in the United States and other countries.

• Linux is the registered trademark of Linus Torvalds in the United States and/or other countries.

• Red Hat is the trademark or registered trademark of Red Hat Software, Inc.

• HP-UX is the proprietary name of the Hewlett-Packard Company operating system.

• Oracle is the registered trademark of Oracle Corporation in the United States and othercountries.

• PostgreSQL is the name of the open source object-relational database management systemadvocated by the PostgreSQL Global Development Group.

• PATLITE is a registered trademark of PATLITE Corporation.

• Adobe, Acrobat and Reader is the trademarks or the registered trademarks of Adobe SystemsIncorporated in the United States and other countries.

• The anti-virus software "VirusScan Enterprise 8.0" is a McAfee, Inc. product.

• This product includes software developed by the OpenSSL Project for use in the OpenSSLToolkit (http://www.openssl.org/).

• This product includes cryptographic software written by Eric Young ([email protected]).

• All other company names and trademark names are the trademarks or registered trademarks oftheir respective companies.

• The ™ and ® symbols are not specified in this manual.

i

IntroductionThank you for choosing MasterScope Network Manager.

This document explains the release contents of MasterScope Network Manager 8.0

• To return to the former page after jumping from the hyper link in the PDF manual or the onlinehelp, press ALT + Left keys. (In the case of using Adobe Reader or Windows HTML helpviewer)

• Due to upgrades, the specifications and design of windows in this manual are subject to changewithout notice.

Notations and Text Conventions

Document ConventionsIn this manual, the following notations are used to indicate items that require special attention andsupplementary information.

Notations of Items Requiring Attention and Supplementary Information

Mark Description

Caution

Indicates important points that the user should observe to configure and use theproduct properly.

1)

Note

Explains notes placed in the text.

Tip

Indicates useful information.

Text ConventionsIn this manual, the following text conventions are used.

Text Conventions

Notation Description Example

uiname Indicates graphical user interfacessuch as dialog boxes, tabs, menus,items, and buttons.

Alert Detail dialog, OKbutton

<userinput> Indicates items that changedepending on the user environmentor items that the user must specify.

<filepath>

configuration file Indicates the contents of theconfiguration file.

Set the following value:

port = 54321

command line Indicates command line operations. Run the following script:

$> NvPRODBSetup.bat

ii

AbbreviationsAbbreviations

Formal Name Abbreviation

MasterScope Network Manager Network Manager, NetMgr

MasterScope Unified Management Framework UMF

Configuration management database Configuration management DB, CMDB

Alert management database AlertDB

sFlow database sFlowDB

Install PathDefault installation directory: Windows

• 32bit OS: C:\Program Files\NEC\UMF\Operations

• 64bit OS: C:\Program Files (x86)\NEC\UMF\Operations

iii

ContentsChapter 1. Overview .................................................................................................................... 1

1.1 Overview ..............................................................................................................................2

Chapter 2. Operating Environment ........................................................................................... 32.1 System Configuration............................................................................................................4

2.2 System Requirements............................................................................................................4

Chapter 3. Documents ................................................................................................................. 7

Chapter 4. New and Improved Functions.................................................................................. 84.1 Improvements to the Trap Definition Management ...............................................................9

4.2 Support for the WebAPI ......................................................................................................104.2.1 Operations that WebAPI Supports .............................................................................104.2.2 System Architecture for using WebAPI.....................................................................11

4.3 Improvements to Monitoring Functions ..............................................................................134.3.1 Monitored node SNMP character code specification function ...................................134.3.2 Improvements to the communication failure judgment process of the alive monitoring

function (state monitoring)...........................................................................................13

4.4 Improvements to Configuration Management Functions .....................................................144.4.1 LLDP-MIB support through physical topology discovery .........................................144.4.2 Improvement in discovery of ProgrammableFlow topology .....................................154.4.3 Item addition of import/export for configuration information....................................15

4.5 Improvements of the SNMP Monitoring Function ..............................................................164.5.1 SNMP inform monitoring support .............................................................................16

4.6 Improvements to Operationality ..........................................................................................164.6.1 Improvement of messages indicating a syntax error when incorporating a MIB file ..174.6.2 Improvement of monitoring terminal start performance ............................................174.6.3 Improvement of remote login connection processing performance ...........................174.6.4 Enhancement in the Linking of Performance Information between MasterScope

Products .......................................................................................................................174.6.5 Sorting support for the interface property display information ..................................184.6.6 Improvements to entry setting (state monitoring and data collection) ........................18

4.7 Newly Supported Device Types ..........................................................................................194.7.1 Cisco Nexus 2000 configuration visualization (Nexus autodiscover) ........................194.7.2 Device front panel display (Node Manager function) ................................................194.7.3 Configuration and software management (Resource Manager function)....................204.7.4 Linking with NEC SigmaSystemCenter (Network Provisioning function) ................26

Chapter 5. Functions with Specification Changes .................................................................. 275.1 Specification Changes in Version 8.0 ..................................................................................28

5.1.1 Changes to specification of Trap Definition Management .........................................285.1.1.1 Changes to the Trap definition operation .........................................................285.1.1.2 Trap definition file migration process .............................................................28

5.1.2 Changes to menu names ............................................................................................30

iv

5.1.3 Changes to the specifications of the state monitoring/data collection settingcommands....................................................................................................................30

5.1.4 Changes to the management method of Cisco ASA 5500 startup-config in multiplecontext mode ...............................................................................................................30

5.2 Specification Changes in Version 6.1 ..................................................................................315.2.1 Changes to the target data of the setting backup ........................................................315.2.2 Changes to the processing method of Counter-type and Counter64-type MIBs .........315.2.3 Changing behavior when collection processing is not completed within the interval .....

.....................................................................................................................................325.2.4 Changes to the default display method for OctetString-type MIBs ............................33

5.3 Specification Changes in Version 5.1 ..................................................................................335.3.1 Changes to the location of MIB definition files .........................................................335.3.2 Changes to required software ....................................................................................33

5.3.2.1 Database software ...........................................................................................335.3.3 Various changes to Alert Management specifications ................................................33

5.3.3.1 Alert recovery processing when restarting the Manager ..................................345.3.3.2 Changes to the severity level of undefined SNMP trap alerts ..........................345.3.3.3 More options in the [Update Property] menu...................................................34

Chapter 6. Precautions and Limitations .................................................................................. 356.1 Precautions on Upgrading ...................................................................................................36

6.1.1 Precautions to take when both new and old versions of the monitoring terminalfunction exist ...............................................................................................................36

6.1.2 Precautions on incorporating an MIB for data collection...........................................37

6.2 Precautions on Topology Information Autodiscover............................................................38

6.3 Limitation about Patlite reports ...........................................................................................38

v

Chapter 1. Overview

Contents1.1 Overview .....................................................................................................................................2

Chapter 1. Overview

1

1.1 OverviewMasterScope Network Manager (hereafter referred to as "Network Manager") is an SNMP-basednetwork management system that improves the efficiency of multi-vendor networks and reducesmanagement costs.

The following management operations are available using the basic Network Manager functions:

• Configuration Management

- Graphical display of network configuration

- Management of information concerning the characteristics of network elements

- Visualization of the network device front panel

• Fault Management

- Network status monitoring

- Receipt of fault notifications from devices

- Reporting of faults to the administrator

• Performance Management

- Reports and graphical display of the network performance

- Network traffic information based on sFlow protocol

Advanced functions of management operations:

• Resource Manager function

Management of device configuration information and software

• Network Provisioning function

Settings for devices linked with NEC Sigma System Center

Chapter 1. Overview

2

Chapter 2. Operating Environment

Contents2.1 System Configuration...................................................................................................................4

2.2 System Requirements...................................................................................................................4


3

2.1 System ConfigurationFigure 2-1 shows the system configuration of Network Manager.

Figure 2-1 System Configuration

Network Manager consists of two functions: the manager function and the monitoring terminalfunction. The role of each function is shown in Table.

Table 2-1 Manager function and Monitoring Terminal function

Function Description

Manager function Manages and monitors target devices.

Monitoring Terminal function Provides viewer functions such as operating and configuring the managerfunction and network status display.

TipThe monitoring terminal function can be installed in multiple machines and they can connect simultaneouslyto a single manager function.

Network Manager uses the bundled databases (internal databases) to store various information suchas configurations, failure events, and performance data (sFlow). Network Manager can also use thedatabases installed in the manager server (external databases) to store the information.

Pay attention to the following points when selecting databases.

1. Internal databases and external databases cannot be used concurrently. If using externaldatabases, configurations, failure events, and performance data (sFlow) information is storedin the external databases. Internal databases are not used.

2. You cannot change the databases in midstream. For example, if external databases were usedbefore upgrading, you cannot switch to the internal databases.

2.2 System RequirementsNetwork Manager operates on the following Operating Systems.


4

Table 2-2 List of supported Operating Systems

Operating System Managerfunction

MonitoringTerminalfunction

Windows Server 2016 (x64) Y 1) 2) Y 1) 2)

Windows Server 2012 R2 (x64) Y 1) Y 1)

Windows Server 2012 (x64) Y 1) Y 1)

Windows Server 2008 R2 (x64) Y 1) Y 1)

Windows Server 2008 (32bit / x64) Y 1) Y 1)

Windows 10 Pro, Enterprise (32bit / x64) N Y 3)

Windows 8.1 Pro, Enterprise (32bit / x64) N Y

Windows 7 Professional/Enterprise/Ultimate (32bit / x64) N Y

Note1. Windows Server Core is not supported.2. Nano Server is not supported.3. Tablet mode is not supported.

System Requirements (for the Windows manager function)Table shows the system requirements for the manager function.

Table 2-3 System requirements for the manager function

Item Description

CPU Intel Pentium series, 2 GHz or higher is recommended

System memory 1 GB or more

Disk (free space) 2 GB or more (10GB or more is recommended)

Network 100 Mbps LAN or faster recommended

Required software Microsoft Visual C++ 2005 SP1 Redistributable Package (x86) 1)

Supported cluster EXPRESSCLUSTER X 2.1 or later

External database software(Optional)

• Microsoft SQL Server 2014 1)

• Microsoft SQL Server 2012 1)

Note1. Microsoft Visual C++ 2005 SP1 Redistributable Package (x86) is required when using internal

databases. It will be installed automatically in the manager function installation.2. The following editions are not supported in the cluster environment.

• Microsoft SQL Server 2014 Express• Microsoft SQL Server 2012 Express


5

System Requirements (for the monitoring terminalfunction)

Table 2-4 System requirements for the monitoring terminal function

Item Description

CPU Intel Pentium series, 2 GHz or higher is recommended

System memory 512 MB minimum (1 GB or more is recommended)

Disk (free space) 400 MB

Network 100 Mbps LAN or faster recommended 1)

Note1. If the manager and monitoring terminal are connected with the network which has large

communication latency like WAN, it may take a few minutes to start the monitoring terminal function.

Web monitoring view function requires the same system requirements for the normal monitoringterminal function. Web monitoring view function is supported in Internet Explorer 7 ~ 11 (32bit).


6

Chapter 3. DocumentsThe following lists the documents supplied with this version.

The documents are contained under /doc/NvPRO of the MasterScope Network Manager Media.

Table 3-1 Network Manager manual list

File Name and Title Contents

MasterScope Network Manager 8.0 Release Notes( NvPRO_relememo.pdf )

Explains the release contents of MasterScope NetworkManager

MasterScope Network Manager 8.0 Setup Guide(For Windows environment)( NvPRO_setup_win.pdf )

Explains how to set up Network Manager for Windowsenvironment. MasterScope Network Manager

MasterScope Network Manager 8.0 Setup GuideWindows/EXPRESSCLUSTER X Environment( NvPRO_CS_setup_win.pdf )

Explains how to set up MasterScope Network Manager(Windows version) in a cluster system.

MasterScope Network Manager Setup Guide(Rolling Update)Windows/EXPRESSCLUSTER X Environment( NvPRO_update_win.pdf )

Explains how to update MasterScope Network Manager(Windows version) using Rolling Update method in acluster system.

MasterScope Network Manager 8.0 User's Manual( NvPRO.pdf )

Operation manual of MasterScope Network Manager.

MasterScope Network Manager WebAPI 1.1 ReferenceManual( NvPRO_webapi.pdf )

Manual of MasterScope Network Manager WebAPI 1.1.

Chapter 3. Documents

7

Chapter 4. New and Improved Functions

Contents4.1 Improvements to the Trap Definition Management ......................................................................9

4.2 Support for the WebAPI .............................................................................................................10

4.3 Improvements to Monitoring Functions .....................................................................................13

4.4 Improvements to Configuration Management Functions ............................................................14

4.5 Improvements of the SNMP Monitoring Function .....................................................................16

4.6 Improvements to Operationality .................................................................................................16

4.7 Newly Supported Device Types .................................................................................................19


8

4.1 Improvements to the Trap DefinitionManagement

Previously, trap definitions that determine the contents of the alert notification when an SNMP trap isreceived had to be placed in an external file and incorporated into Network Manager by executing theNvPROReloadDllMgr command or NvPROReloadDefFileMgr command. In addition, to create atrap definition from an MIB file, an AMIB definition had to be incorporated in advance.

In this version, former operation procedures for trap definitions have been improved so that it is nowpossible to display a list, add, edit, and delete trap definitions, and reflect definition items from themonitoring terminal window. In addition, it is no longer necessary to incorporate AMIB definitionsbefore creating trap definitions from MIB files.

Furthermore, a function (search matching definitions) to check which trap definition is applied to analert notification when SNMP trap is received is provided to facilitate trap definition management,which was cumbersome up to now.

Figure 4-1 Trap definition management window

For details on the changes to trap definition operations, refer to MasterScope Network ManagerUser's Manual "4.11 Monitoring SNMP traps/informs".

TipThe definition items of the former trap definition file corresponding to the parameters of the trap definitionmanagement window are as follows.

Table 4-1 Items in a trap definition file and corresponding items on the trap definitionmanagement window

Items in the former trap definition file Trap definition management window

Enterprise Enterprise ID

GenericCode Generic Trap Code

SpecificCode Specific Trap Code


9

Items in the former trap definition file Trap definition management window

Severity Severity

Summary Summary

Detail Detail

Action Action

RecoveryNo RecoveryNo

RecoveryCondition RecoveryCondition

Node Node

Logging Alert Notification

ExternFun ExternFun

You can also add, edit, and delete trap definitions from the commands (nvptrapdefconf andnvpmib2trapdef). For details, refer to MasterScope Network Manager User's Manual "9.6 TrapDefinition Operation Commands".

4.2 Support for the WebAPIThe WebAPI, which acquires and manipulates management information remotely via HTTP/HTTPS,is supported. The following sections explains the scope of WebAPI support and the operationenvironment.

4.2.1 Operations that WebAPI SupportsThis WebAPI supports the following operations.

Table 4-2 Operations WebAPI supports.

Function name Operation Description

ConfigurationInformationManagement

Obtaining map list Obtaining, adding, updating and deleting the propertyinformation of the map.These are the same functions as the map view operationsof the monitoring device window.

Obtaining map details

Adding map

Updating map

Deleting map

Obtaining node list Obtaining, adding, updating and deleting the propertyinformation of the node.In addition, obtaining the interface property information.These are the same functions as the map view operationsof the monitoring terminal window. However, theoperations of the login information are not supported.

Obtaining node details

Adding node

Updating node

Deleting node

Updating device information ofnode

Updating the property information of the registered nodeby obtaining the information using SNMP.Providing the same functions as Update Propertymenu of the monitoring terminal window and executionof nvpnodeup command.

Obtaining severity state list ofnode

Obtaining the severity status (alert occurrence state) ofthe node.


10

Function name Operation Description

Obtaining severity state of node These are the same functions as the icon colorconfirmation functions of the map view of themonitoring terminal window.

Obtaining map configuration Obtaining the configuration information of the map andnode belonging to the specified map.This is the function to confirm the configurationinformation, that is same as the tree view displayingfunction of the monitoring terminal window.

Expanding standard componentname specification format

Obtaining the component name corresponding to thespecified standard component name specification format.In the case of specifying the target component of thestatus monitoring rule entry or the data collection entry,this operation is used to confirm the target specificcomponent when the standard component namespecification format is used.

State Monitoring Obtaining state monitoring ruleentry list

Obtaining, adding, updating and deleting the informationof the status monitoring rule entry. In addition, obtainingthe built-in state information of the status monitoringrule.These are the same operation functions as those of StateMonitoring view of the monitoring terminal window.However, the embedding and removing operations of thestatus monitoring rule are not supported.

Obtaining state monitoring ruleentry

Adding state monitoring ruleentry

Updating state monitoring ruleentry

Deleting state monitoring ruleentry

Obtaining state monitoring rulelist

Data Collection Obtaining data collection entrylist

Obtaining, adding, updating and deleting the informationof the data collection entry.These are the same operation functions as those of DataCollecting Setting view of the monitoring terminalwindow. However, the following operations are notsupported.• Operation of the cumulative schedule in the threshold

monitoring and setting.• Operations of adding a new MIB calculation formula

and confirming the registered definition (i.e.operations corresponding to those of MIB ExpressionCreating window).

Obtaining data collection entry

Adding data collection entry

Updating data collection entry

Deleting data collection entry

Alert Management Obtaining alert list Obtaining, updating and deleting the alert information.These are the same operation functions as those of AlertManagement window of the monitoring terminalwindow.

Obtaining alert

Confirming alert

Confirming alert in a batch

Deleting alert

Deleting alert in a batch

4.2.2 System Architecture for using WebAPIThis section describes the system architecture for using WebAPI.


11

To use WebAPI, it needs to install the following two components of the Service Governor on theserver that the manager function is installed.

Service Governor:

• MaterScope Service Governor

• Application Server (Tomcat)

The client system using WebAPI accesses to the Service Governor and operates MasterScopeNetwork Manager as described in "Figure 4-2 Standard architecture for using WebAPI (page 12)".

Figure 4-2 Standard architecture for using WebAPI

In the environment that multiple MasterScope Network Manager are located, install the ServiceGovernor on one of the servers that the manager function is installed as described in "Figure4-3 System architecture under multiple managers environment (pattern 1) (page 12)".

Figure 4-3 System architecture under multiple managers environment (pattern 1)

As described in "Figure 4-4 System architecture under multiple managers environment (pattern 2)(page 13)", it is possible to configure the system by installing the Service Governor on a differentserver with those of the manager function is installed.


12

Figure 4-4 System architecture under multiple managers environment (pattern 2)

In any case, the client system using WebAPI can operate all MasterScope Network Manager byaccessing the Service Governor.

4.3 Improvements to Monitoring FunctionsIn this version, improvements have been made to monitoring functions.

4.3.1 Monitored node SNMP character code specificationfunction

It is now possible to process any UTF-8 characters contained in SNMP Get/Set and SNMP Traps/Informs without the characters getting garbled.

Previously, the specifications were such that if non-ASCII characters such as Japanese characterswere contained in SNMP Get/Set and SNMP Traps/Informs, all these characters were garbled. Forthis reason, if UTF-8 character codes were contained, it was not possible to display themappropriately.

This version supports a function for specifying, on a node-by-node basis, what character code to useto interpret the non-ASCII characters contained in the data in SNMP Get/Set and SNMP Traps/Informs.

Supported character code is: UTF-8.

4.3.2 Improvements to the communication failure judgmentprocess of the alive monitoring function (state monitoring)

The Communication_Failure_Repeat variable has been newly added to theupdown:UpDownCheck rule and the updownv6:ipv6UpDownCheck rule of the statusmonitoring function.

The updown:UpDownCheck rule and the updownv6:ipv6UpDownCheck rule are fordetecting communication failures in monitored nodes via ICMP Echo. Under this rule, if an ICMPEcho response cannot be obtained or a message is received indicating that communication withmonitored nodes such as ICMP Destination Unreachable cannot be established in lieu of a response,this is immediately judged as a communication failure and an alert is issued.

In this version, it is possible to specify the number of consecutive times the above-mentionedcommunication failure is detected before an alert is to be issued.


13

This makes it possible to perform monitoring by ignoring the instantaneous interrupts of the networkand other faults.

If, for example, you specify that “an alert is to be issued when a communication failure is detectedtwo consecutive times”, the following happens.

1. At the point the first communication failure is detected, an alert is not issued.

2. After the first communication failure is detected, the next monitoring is executed after theinterval elapses.

a. If a communication failure is detected in the next monitoring as well, an alert is issued.

b. If a communication failure is not detected (there is an ICMP Echo Reply) in the nextmonitoring, an alert is not issued.

To specify the number of consecutive times a communication failure is detected for which an alert isto be issued, set the number for Communication_Failure_Repeat in the state monitoring ruleentry setting window. The default is 1, so that an alert is issued when the first communication failureis detected.

4.4 Improvements to Configuration ManagementFunctions4.4.1 LLDP-MIB support through physical topology discovery

In addition to OADP/CDP/FDP supported devices, this version supports LLDP supported devicesthrough the Physical Topology menu. This allows users to automatically acquire and checkaccurate connection information between multiple devices.

CautionIn order to discover a physical topology in Network Manager, the devices to be monitored must satisfy thefollowing conditions.• The following MIB files are supported among the LLDP-MIBs that conform to IEEE802.1ab-2005:

- lldpLocSysName (1.0.8802.1.1.2.1.3.3.0)- lldpLocPortIdSubtype (1.0.8802.1.1.2.1.3.7.1.2)

The value must be 5 (interfaceName).- lldpLocPortId (1.0.8802.1.1.2.1.3.7.1.3)- lldpRemSysName (1.0.8802.1.1.2.1.4.1.1.9)


14

- lldpRemPortIdSubtype (1.0.8802.1.1.2.1.4.1.1.6)The value must be 5 (interfaceName).

- lldpRemPortId (1.0.8802.1.1.2.1.4.1.1.7)• LLDP is operating.

4.4.2 Improvement in discovery of ProgrammableFlowtopology

The support area of the discovery of ProgrammableFlow topology ProgrammableFlowTopology menu, where you can automatically discover or draw the physical topology of aProgrammableFlow network that is configured by a ProgrammableFlow switch, has been expanded.

Under the ProgrammableFlow Topology, physical topology is drawn by comparing acorrespondence table that is maintained within Network Manager with interface names acquired bothfrom the MIB of a ProgrammableFlow switch (PFS) and the WebAPI of a ProgrammableFlowcontroller (PFC). Therefore, only the PF5200 series which included the correspondence table as astandard feature could discover a physical topology under the previous version.

This version provides the correspondence table of interface names of the PF5459 series and thePF5820 series as a standard feature, in addition to the PF5200 series. Further, as shown in Figure 4 1,the definition of the correspondence table for interface names can be manually incorporated even if anew PFS series is incorporated in the network. This allows to execute "autodiscovery of physicaltopology" which is followed by configuration supported by PFC.

Figure 4-5 Detection of physical topology for a ProgrammableFlow network

CautionWhen you use this function, you need to set up the WebAPI of the PFC in advance.Select "Use the user name and password on OS" as the authentication method of the user of the WebAPI.For details, refer to the manual provided with PFC.

4.4.3 Item addition of import/export for configurationinformation

The following property information was added to the import and export of configuration information:


15

• Discovery Protocol• Administration Node Name• sysName

Although up until now it was necessary to manually perform information registration/updates foreach node from the Properties dialog box, these properties have become import and export items sothat the registration/updates of multiple node information can be performed in a batch to enhancework efficiency.

4.5 Improvements of the SNMP MonitoringFunction4.5.1 SNMP inform monitoring support

Unlike SNMP traps, SNMP informs define specifications where a notification of receipt is deliveredto the sender. As shown in "Figure 4-6 SNMP inform monitoring (page 16)", whether or not anotification (inform request) transmitted from a monitoring target network device in a networksystem has been securely delivered to Network Manager is confirmed by whether such notification isresponded to or not. If there is no response against the inform request, the network device transmitsthe inform request again to improve the reliability of the notification.

Figure 4-6 SNMP inform monitoring

Because the reliability of fault notifications from monitored devices has been improved by usingSNMP informs, the number of status monitoring (periodical MIB monitoring) items in NetworkManager can be reduced to lower the steady load of monitored devices and Network Manager,consequently widening the range of monitoring design.

4.6 Improvements to OperationalityIn this version, the operability of existing functions has been improved.


16

4.6.1 Improvement of messages indicating a syntax errorwhen incorporating a MIB file

When running the NvPROMib2Amib command to incorporate a MIB file, messages are output if asyntax error is detected in a MIB file while analyzing it. In this version, these messages have beenimproved.

In the previous versions, if a MIB file with a syntax error was specified to run the NvPROMib2Amibcommand, only the line number in which the error was detected was notified along with a syntaxerror message.

4.6.2 Improvement of monitoring terminal start performanceThe processing at the start of the monitoring terminal is optimized to shorten the time required for thestart of the monitoring terminal.

The start time is improved considerably, especially if a band-limited network with large delays, suchas a WAN, exists between manager and monitoring terminal.

TipIn our verification, the shortening of the start time by up to 95% has been confirmed with a case with 3000registered nodes and the network delay between manager and monitoring terminal being 10 ms.

4.6.3 Improvement of remote login connection processingperformance

Time for completing the connection has been greatly reduced by optimizing Telnet/SSH connectionprocessing to a monitored device through remote login and by reducing the impact on a network asmuch as possible where delays through WAN, etc. are large between a manager and monitoredterminals and where a network exists whose bandwidth is limited.

TipAs a result of the verification, NEC has found that the time to complete the connection has become constantwhen a network delay is changed within a range of 0 ms to 50 ms, and also an 81% reduction in connectiontime when a network delay is 50 ms under an environment where there is no network delay between themanager and a monitored device (device to be connected).

4.6.4 Enhancement in the Linking of Performance Informationbetween MasterScope Products

In Network Manager, performance information (MIB values) collected by the data collectionfunction is delivered to the performance management service so that comprehensive performancemanagement can be executed, including a multi-graphical view and invariant analysis, by also usingserver performance information collected by other MasterScope products when the performancemanagement service of MasterScope framework is operating under the same service.

The performance management service can be operated under the same service as Network Managerwhen the following conditions apply.

• When the MasterScope products which are compatible with MasterScope framework, such asMasterScope SystemManager G, are installed on the same service.

In the previous versions, because all the performance information collected by Network Manager hasbeen passed to the performance management service, the performance management service


17

processing may have become high-loaded or needed large disk capacity for managing performanceinformation.

This version filters only the necessary performance information to pass to the performancemanagement service. Through this, the load for performance management service has been reducedand disk capacity has been saved thereby system configuration is possible using smaller resources.

4.6.5 Sorting support for the interface property displayinformation

It is now possible to sort the interface information displayed in the Interface Properties dialog box byitem.

Previously, the interface information in the Interface Properties dialog box was displayed in theascending order of the value of Index. In this version, it is possible to sort the display in theascending or descending order of each item by clicking the label of the display.

This makes it easy to find the relevant interface information when, for example, setting the defaulttarget port.

4.6.6 Improvements to entry setting (state monitoring anddata collection)

In the function for checking the contents when setting status monitoring rule entries and datacollection entries, the input limits on some items are eased.

Setting of status monitoring rule entriesPreviously, the following limit was imposed and the following process was performed for the settingof status monitoring rule entries.

• It was not possible to specify a node not registered in Network View or a nonexistent group fora monitored Component.

• In a state monitoring rule entry whose monitoring was in the start state, if all nodes or groupsspecified for Component were deleted from Network View, the monitoring of the rule entrywas placed in the stop state when the manager function was rebooted.

In this version, the above limit and process have been improved as below.

• It is now possible to set a state monitoring rule entry by specifying a node not registered inNetwork View or a nonexistent group, and it is now also possible to place the monitoring ofthe state monitoring rule entry in the start state.

This makes it possible to perform operations such as the following: Immediately after a newnode is registered or a group is set, the node or group is monitored by automatically applying apreset state monitoring rule entry to it.

• The process has been changed so that if a node not registered in Network View or anonexistent group is specified as a monitored target and the monitoring of the rule entry is set tothe start state, the monitoring of the rule entry is not placed in the stop state but is kept in thestart state even if the manager function is rebooted.

This measure is a revision of the process associated with the improvements to the advancesetting of status monitoring rule entries for unregistered components.


18

Setting of data collection entriesPreviously, the following limits were imposed on the setting of data collection entries.

• It was not possible to specify a node not registered in Network View or a nonexistent group forTarget Node.

• In Threshold value monitoring setting, it was not possible to specify for RecoveryThreshold the same value as the value set for Threshold Value.

In this version, the above limits are eased to enable settings and operations such as the following.

• It is now possible to set a data collection entry by specifying a node not registered in NetworkView or a nonexistent group, and it is now also possible to place the collection of the datacollection entry in the start state.

This makes it possible to perform operations such as the following: Immediately after a newnode is registered or a group is set, data is collected by automatically applying a preset datacollection entry to the node or group.

• In Threshold value monitoring setting, it is now possible to specify for RecoveryThreshold the same value as the value set for Threshold Value.

This makes it possible to meet various operation requirements in accordance with the alreadysupported specification range.

4.7 Newly Supported Device TypesThis section explains the functions for which the supported device types have been expanded in thecurrent version, as well as providing information on those device types.

4.7.1 Cisco Nexus 2000 configuration visualization (Nexusautodiscover)

The configuration visualization function of Cisco Nexus 2000 (Nexus autodiscover) now supportsCisco Nexus 5500 and 5600 series.

Previously, Nexus autodiscover supported only two models (5010 and 5020) of the Cisco Nexus5000 series.

In this version, the following models are also supported by Nexus autodiscover.

• Cisco Nexus 5596T

• Cisco Nexus 5596UP

• Cisco Nexus 5548P



• Cisco Nexus 56128P

In the supported models, the alerts for interface faults (such as the reception of linkDown traps) thatoccur on the connected Nexus 2000 series (2000, 2100, and 2200 series) can be reported to the iconindicating the Nexus 2000 series, making it easy to identify the fault locations.

4.7.2 Device front panel display (Node Manager function)Devices newly supported by the Node Manager function are shown in Table.


19

Table 4-3 Devices supported by the Node Manager function

Device Name Version 1)

PF5459-48GT-4X2Q 2) 7.1.12

PF5459-48XP-4Q 2) 7.1.12

PF5459-48XT-4Q 2) 7.1.12

Note1. Indicates the versions of the managed devices whose operation is guaranteed. For other versions as

well, management can be performed in the range of information in the management items that isimplemented by the target devices.

2. The display of stack configurations is also supported.

4.7.3 Configuration and software management (ResourceManager function)

Devices newly supported by the Resource Manager function are shown below, along with their scopeof support under the function.

CautionScope of support depends on individual device specifications.

QX-S1000G seriesThe following explains the status of the support of the QX-S1000G series.

• Supported version: 5.1.2 and up

• The scope of supported function is shown in Table.

Table 4-4 Scope of support for QX-S1000G series

Resource Manager Function Details Supported

Collect running-config Y

Deploy running-config Y

Collect startup-config Y

Deploy startup-config Y

Manage configuration changes Y

Backup software Y

Deploy software Y

Reboot Y





20

Table 4-5 QX-S4100G series


Collect running-config 1) Y

Deploy running-config N




Backup software Y

Deploy software Y

Reboot Y

Note1. The use of an external FTP/TFTP server is not supported.











Backup software Y

Deploy software Y

Reboot Y









21






Backup software Y

Deploy software Y

Reboot Y


IP8800/S2500 seriesThe following models of the IP8800/S2500 series have undergone verification and evaluation toconfirm that they are operable without a problem.

• IP8800/S2530-48P2X (Version: 4.3) 1)

Note1. The stack configuration is also supported.

IP8800/S4630 seriesThe following explains the status of the support of the IP8800/S4630 series.

• Supported version: 11.12.A and up


Table 4-8 Scope of support for IP8800/S4630 series



Deploy running-config Y 1)




Backup software Y

Deploy software Y 2)

Reboot Y

Note1. In the stack configuration, uploading running-config is not supported due to the device

specification.2. Only "Deploy to master switch" is supported for stack configurations,. While switching the

master switch by rebooting, deploy software to all the switches making up a stack.


22

IP8800/S8300 seriesThe following explains the status of the support of the IP8800/S8300 series.

• Supported version: 12.6 and up


Table 4-9 Scope of support for IP8800/S8300 series







Backup software Y

Deploy software Y 1)

Reboot Y

Note1. The device manages the software with a fixed file name, so current software cannot be remained

when deploying new software. The software is always overwritten.

CautionIn order to protect the device, IP8800/S8300 series devices impose a fixed rate limit in the process ofreceiving data. If packets are received faster than the specified rate, packets will be discarded in accordancewith this device specification.It is recommended to use FTP as a file transfer protocol to avoid this limitation.

IX2000 and 3000 seriesThe following models of the IX2000 and IX3000 series have undergone verification and evaluationto confirm that they are operable without a problem.

• IX2207 (Version: 9.0.14)

• IX3015 Version: 9.1.10)

• IX3315 (Version: 9.4.15)

WA seriesThe following models of the WA series have undergone verification and evaluation to confirm thatthey are operable without a problem.

• WA1510 (Version: 7.2.0)

• WA1511 (Version: 7.2.0)

• WA2610-AP (Version: 7.2.0)

• WA2611-AP (Version: 7.2.0)


23

F5 Networks BIG-IP V11 seriesThe following explains the status of the support of the F5 Networks BIG-IP V11 series.



Table 4-10 Scope of support for BIG-IP V11 series




Collect startup-config N

Deploy startup-config N


Backup software N

Deploy software N

Reboot Y

Caution• On the device side, be sure to suppress the output of logs to the console.• For the operation of running-config management, note the following:

- An SCF text file is handled as running-config. For this reason, information about the settingsrelated to GTM/ASM and other product modules, licenses, and SSL certificates is not managed.

- During Deploy running-config, the load sys config file command is executed. For this reason, ifreboot is executed after Deploy running-config, rebooting is performed by updating startup-config because of the device specifications.

- In the operation of device replacement due to, for example, a device failure, it may not bepossible to display the running-config collected before device replacement directly to the newdevice after device replacement.After device replacement, perform Collect running-config on the device after replacement. Then,edit the newly collected configuration file and perform Deploy running-config.

• If managing BIG-IPs in a redundant configuration, note the following:- A virtual IP address cannot be assigned to the BIG-IP management interface (Management Port)

because of the device specifications. For this reason, you must register the two BIG-IPs in theredundant configuration with individual icons on the map and manage them.

- During Deploy running-config, synchronous processing for the configuration file is notperformed. It is recommended that to manage BIG-IPs in a redundant configuration, you performauto sync setting. If you do not perform auto sync setting, execute config-sync manually afterdeploying the configuration file.

A10 Networks Thunder ADC seriesThe following explains the status of the support of the A10 Networks Thunder ADC series.

• Supported version: 2.7.1-GR1 and up



24

Table 4-11 Scope of support for Thunder ADC series







Backup software N

Deploy software 1) Y

Reboot Y

Note1. On the device side, you must make the settings for sending the axSystemRestart trap.

Caution• To avoid competition between the processing from the Resource Manager function and other setting

work, it is recommended to enable the arrangement for simultaneous settings on the device side.• The Thunder ADC series with a specific 2.7.2 version (2.7.2-P5 or earlier) contains a defect whereby

the MIB (sysObjectID) for identifying a model returns an invalid value.If using the Resource Manager function with the Thunder ADC series that contains this defect,manually change the following items of the icon properties of the device to appropriate values.- OS Type

Specify “A10Thunder”.- SW Version

Specify “2.7..2”

Fortinet FortiGate seriesThe following explains the status of the support of the Fortinet FortiGate series.

• Supported version: ver4.0 MR3 patch8 and up


Table 4-12 Scope of support for FortiGate series


Collect running-config N


Collect startup-config Y 1)

Deploy startup-config Y 1) 2)

Manage configuration changes N

Backup software N

Deploy software N

Reboot Y


25

Note1. Handled as startup-config because of the nature of the configuration file of this device.2. After deploying the configuration file, be sure to perform Reboot in accordance with the device

specifications.

CautionThe FortiGate series supplies the VDOM (virtual UTM) function, which enables you to create multiplevirtual FortiGates on a single FortiGate appliance.The FortiGate series supplies the VDOM (virtual UTM) function, which enables you to create multiplevirtual FortiGates on a single FortiGate appliance.

4.7.4 Linking with NEC SigmaSystemCenter (NetworkProvisioning function)

Devices newly supported by the Network Provisioning function are shown in Table.

CautionThe scope of support depends on the specifications of the model.

Table 4-13 Devices supported by the Network Provisioning function

Device Name Version Supported

QX-S1000G series 5.1.2 and up VLAN Settings



IP8800/S4630 series 11.12.A and up VLAN Settings

IP8800/S8300 series 12.6 and up VLAN Settings

A10 Networks Thunder ADC series 2.7.1-GR1 and up Load Balancer Settings

The following model has undergone verification and evaluation to confirm that it is operable withouta problem.

• IP8800/S2530-48P2X (Version: 4.3)


26

Chapter 5. Functions with Specification Changes

Contents5.1 Specification Changes in Version 8.0 .........................................................................................28

5.2 Specification Changes in Version 6.1 .........................................................................................31

5.3 Specification Changes in Version 5.1 .........................................................................................33


27

5.1 Specification Changes in Version 8.0This section describes functions for which specifications have changed under MasterScope NetworkManager 8.0

5.1.1 Changes to specification of Trap Definition ManagementAlong with the enhancement of the trap definition operation, the specification of the trap definitionmanagement has been changed

5.1.1.1 Changes to the Trap definition operationIn MasterScope Network Manager 8.0, the specification of the trap definition operation has beenchanged as follows:

• The operation for the trap definition with conventional files is now abolished.

• The following commands can no longer operate trap definitions.

- NvPROMib2Amib -trap- NvPROReloadDllMgr- NvPROReloadDefFileMgr

• The operation after version 8.0 can be performed on the trap definition management window orby newly added commands (nvptrapdefconf, nvpmib2trapdef).

TipThe operation of AMIB definition files is performed by NvPROMib2Amib and NvPROReloadDefFileMgrcommands as in the past.

CautionIf you store the trap definition files in the conventional storage location of trap definition files,NvPROReloadDllMgr and NvPROReloadDefFileMgr commands do not reload these files, however, thesefiles are reloaded after restarting the manager.• Conventional storage location of trap definition files

<On the manager, %sharedfolder%>\Manager\sg\NvPRO\NVWORK\public\trap\For a non-cluster configuration, read <on the manager, %sharedfolder%> as <on the manager,%installfolder%>.

For this reason, if trap definition files are stored in above location, existing trap definitions will beoverwritten unintentionally.After version 8.0, it is recommended not to store trap definition files in the conventional storage location.

5.1.1.2 Trap definition file migration processIf you upgrade an earlier version to MasterScope Network Manager 8.0, convert the contents of allexisting trap definition files into the definition format that makes them operable in the trap definitionmanagement window and perform a migration process when starting services for the first time.

CautionOperations with the former trap definition files will no longer be possible.

The following lists the migration targets.


28

• Standard trap definition files supplied with the product

In the trap definition management window, they are managed in the category of "Systemdefinition".

• Trap definition files automatically generated from an MIB file

In the trap definition management window, they are managed in the category of "MIB originaldefinition."

• User-created trap definitions (user.def)

In the trap definition management window, they are managed in the category of "Userdefinition". Any trap definitions that are clearly judged to have been created by users althoughtheir file names do not contain user.def are processed as migration targets in the "Userdefinition" category.

The specifications of the trap definition management window are such that multiple definitions in thesame category, for which the combinations of settings are the same for the Enterprise ID, SpecificTrap Code, Generic Trap Code, and Node, cannot be retained. For this reason, if there are duplicatetrap definitions in a category, only the definition that has the highest priority for processing NetworkManager is regarded as a migration target.

If there are duplicate trap definitions, the priority is determined as below.

• If there are duplicate trap definitions among multiple trap definition files, the priority is judgedfrom the names of the files containing the trap definitions. Specifically, the definition with thehighest priority is the one contained in the user.def file. For all other definitions, a trapdefinition whose file name comes later in the character code order is judged to have higherpriority.

• The specifications of the processing of MasterScope Network Manager are such that if, in theEnterprise in a trap definition and an SNMP trap, the end of the OID is ".0", the alertnotification process is performed by excluding the ".0". For this reason, in the Enterprise in atrap definition, a definition with a ".0" at the end of the OID and a definition without a ".0" atthe end of the OID are handled as the same OID definition. For trap definitions that are regardedas duplicate regardless of the presence and absence of a ".0" at the end of the OID in theEnterprise, the definition with a ".0" added is judged to have higher priority.

In the migration process, the following process is performed on the trap definition with higherpriority.

• Enterprise definition conversion

If, in the trap definition to be migrated, the end of the vendor identifier (Enterprise) is ".0", it ismigrated by deleting the ".0".

• Node definition division

If the trap definitions to be migrated include a trap definition in which multiple components areregistered delimited by a comma (,) for the Node, the trap definition is migrated as multiple trapdefinitions by dividing the components for the Node.

After the completion of the migration process, the former trap definition files are moved to thefollowing folder.

Destination of former trap definition files

<On the manager, %sharefolder%>\Manager\sg\NvPRO\NVWORK\PUBLIC\trap_backup\<YYYYMMDDHHmmSS>• For a non-cluster configuration, read <On the manager, %sharefolder%> as <On the manager,

%installfolder%>.


29

• <YYYYMMDDHHmmSS> is the folder name representing the date and time the migrationprocess was performed.

If you want to incorporate any trap definitions judged to have low priority, register them using thetrap definition management window or the trap definition batch registration command(nvptrapdefconf), based on the contents of the former trap definition file.

5.1.2 Changes to menu namesIn MasterScope Network Manager 8.0, the names of the following two menus have been changed.

Before changes (version 6.1 or earlier) After changes (version 8.0 or later)

Programmable Flow AuthenticationSetting

-> ProgrammableFlow Authentication Setting

Programmable Flow TopologyDiscovery

-> ProgrammableFlow Topology Discovery

ProgrammableFlow Topology Discovery There are no changes to the functions on each menu.

5.1.3 Changes to the specifications of the state monitoring/data collection setting commands

In MasterScope Network Manager 8.0, the specifications related to the operation of entries in thestart state with the state monitoring setting command (nvpstsmonconf) and the data collection settingcommand (nvpdatacolconf) have been changed.

In MasterScope Network Manager 6.1 or earlier, if the -silent argument was specified with eachsetting command, the target entry could be stopped to change or delete the entry even if the entry wasin the start state. For this reason, if the target entry was specified incorrectly, this could result in theunintended stoppage of entry operation or the deletion of the entry, possibly affecting the operation ofthe system.

In MasterScope Network Manager 8.0, from the viewpoint of preventing erroneous operations, thespecifications have been changed so that if the -silent argument is specified, any entries in the startstate cannot be operated. If wanting to operate an entry in the start state, stop the entry operationexplicitly first and then change or delete the entry.

5.1.4 Changes to the management method of Cisco ASA 5500startup-config in multiple context mode

In the Resource Manager function, the management method of startup-configs of Cisco ASA 5500series under the multiple context mode has been improved.

In version MasterScope Network Manager 5.1, the management method of startup-configs of generalcontexts has been changed as follows to enable more intuitive management.

The changes are as below.

• Displayed nodes in the startup-config management window

- Before change

Only admin context nodes are displayed.

- After change

Both admin context nodes and general context nodes are displayed.


30

• Acquiring, displaying, and detecting differences of startup-configs

- Before change

Startup-configs of both an admin context and general contexts are merged in one imagewhen acquiring and displaying them. Detecting differences of startup-configs is alsoperformed for the merged image, therefore it is difficult to find a context where a startup-config has been changed.

- After change

Startup-configs of an admin context and general contexts are acquired and displayedseparatedly for each context. Detecting differences is also performed for each context.

• Deploying startup-configs

- Before change

It is necessary to deploy them after deleting the sharp (#) at the start of "#~context~" on thestart line of the general context image, located in the startup-config image of the Admincontext node.

- After change No special editing operations such as those before the change are necessary.You can execute the deploy operation directly on the general context node. For details ofhow to make settings for management, refer to "Managing Cisco ASA 5500 redundant/multiple context mode configuration" in the MasterScope Network Manager User'sManual.


5.2.1 Changes to the target data of the setting backupIn the setting backup function (SysMonMgr -backup), the backup target data has been changed.

MasterScope Network Manager 5.1 and earlier, if configuring the performance management bysFlow with CSV file output option, the following CSV files that contain flow data were also backedup.

• Path of flow data CSV files:

<On the manager, %installfolder%>\Manager\sg\NvPRO\SFlowCollector\work\dat\sFlowAgent\YYYY\MM\FLA_DD.csv

These files are used for analyzing flow data by other applications. They are not necessary forrestoring the settings.

MasterScope Network Manager 6.1, these files have been excluded from the backup targets to reducebackup data size.

CautionIf you want to backup the flow data CSV files, copy them to another folder by hand.

5.2.2 Changes to the processing method of Counter-type andCounter64-type MIBs


31

In the data collecting function, the method of difference calculation for Counter-type and Counter64-type MIBs has been changed.

For details of Counter-type and Counter64-type MIBs, refer to "About Counter-type and Counter64-type MIBs" described later.

MasterScope Network Manager 5.1 and earlier, if the acquired Counter-type or Counter64-type MIBvalue was less than the previous value (the counter had exceeded the maximum value, and returnedto 0), the acquired value was treated as an invalid value. For this reason, when the accumulated valuereturned to 0, the acquired data was not displayed in the graph.

MasterScope Network Manager 6.1, this specification has been changed to calculate the difference asthe accumulated value has returned to 0 only once, if the Counter-type or Counter64-type value isless than the previous value.

This specification change makes it possible to calculate the differences correctly and display graphswithout data missing even if the accumulated values have returned to 0 once within the interval.

CautionWhen collecting the Counter-type MIBs, you should specify the appropriate time interval so that theaccumulated value does not return to 0 multiple times.For example, when collecting the traffic (ifInOctets or ifOutOctets) from the interface where 100 Mbpscommunication always occurs, the accumulated value returns to 0 in about less than 6 minutes (232 * 8 /100,000,000 (bps) = 343.6 (sec)). If the interval is set to 12 minutes, the accumulated value may return to 0twice within the interval and the traffic may not be calculated correctly.In this case, take measures such as shortening the collection interval.

About Counter-type and Counter64-type MIBsCounter-type and Counter64-type MIBs hold the accumulated values from when the device hasstarted. These accumulated values become useful by calculating the differences from current valuesand previous values.

The range of Counter-type values is 0 to 4,294,967,295, and the range of Counter64-type values is 0to 18,446,744,073,709,551,615. These values return to 0 when they exceed the maximum value.

5.2.3 Changing behavior when collection processing is notcompleted within the interval

In the data collecting function, the data collection behavior has been changed when collectionprocessing is not completed within the interval.

In MasterScope Network Manager 4.0 and 5.1, if the data collection processing was not completedwithin the interval, the collection processing was skipped at that time and the next interval was set.

• Example: When the collection processing at five minutes intervals is set to Switch A

If acquisition of data is not completed within five minutes after the first collection request forSwitch A, the first request is canceled without collecting data and the second collection requestis issued. The second request is also monitored whether the data collection is completed withinfile minutes. If not, the data collection is skipped and the request is canceled.

In MasterScope Network Manager 6.1, this specification has been changed to wait until the datacollection has completed even if the collection processing is not completed within the interval. Thespecification after changing is the same as MasterScope Network Manager 2.0.


32

5.2.4 Changes to the default display method for OctetString-type MIBs

The default display method for OctetString-type data in SNMP packes has been changed.

In MasterScope Network Manager 5.1 and earlier, OctetString-type data was displayed inhexadecimal by default. To display OctetString-type data as a character string, the data type definedin AMIB definition files should be changed to "DisplayString". InMasterScope Network Manager6.1, this specification has been changed to display data in character strings by default.

To display OctetString-type data in hexadecimal, add the MIB object ID in the prescribed file. Fordetails, refer to MasterScope Network Manager User's Manual "7.4.1.5. MIB Definition hexadecimalnotation setting procedure".


5.3.1 Changes to the location of MIB definition filesNetwork Manager comes with the MIB file definition information (AMIB definition files) required touse each function. It is also possible to add new definition information (AMIB definition files) fromMIB files published by RFC or device vendors.

In MasterScope Network Manager 4.0 and earlier, the built-in AMIB definition files and user-addedAMIB definition files are stored in the same folder. InMasterScope Network Manager 5.1, theinstallation folder of built-in AMIB definition files has been changed in order to avoid confusionwith user-incorporated AMIB definition files.

• Installation path of built-in AMIB definition files (changed) On the manager,

<On the manager, %installfolder%>\Manager\sg\NvPRO\NVWORK\local\amib\• Installation path of user-added AMIB definition files (not changed) On the manager,

<On the manager, %sharefolder%>\Manager\sg\NvPRO\NVWORK\local\amib\If same definitions exist, the definition in the user-added AMIB definition file is given high priority.

5.3.2 Changes to required software

5.3.2.1 Database softwareThrough MasterScope Network Manager 4.0, an external database was required in NetworkManager, but this is no longer a requirement due to the built-in database included in MasterScopeNetwork Manager 5.1.

If the internal database is used, separate database software is no longer required. However, separatedatabase software is still required when using an external database.

5.3.3 Various changes to Alert Management specifications


33

5.3.3.1 Alert recovery processing when restarting theManager

The previous specification, in which all unrecovered alerts were recovered when restarting theManager, has been improved so that alerts that do not need to be recovered are not automaticallyrecovered when restarting the Manager. Such alerts remain in the same state as before the restart.

TipAutorecover alerts detected by the State Monitoring function are automatically recovered when restarting theManager, and monitoring is resumed the Manager restarts. If an error is still detected after this, the alert isreissued.

5.3.3.2 Changes to the severity level of undefined SNMP trapalerts

In MasterScope Network Manager 4.0 and earlier, the severity level of alerts for received SNMPtraps not defined in the trap definition file (i.e., notifications with "Vendor-defined Trap" listed in theSummary field) was set to "Normal."

But in MasterScope Network Manager 5.1, this specification has been changed so that when anSNMP trap is received that is not defined in the trap definition file, the severity level for thenotification is now reported as "Unknown."

5.3.3.3 More options in the [Update Property] menuThe icon properties updatable via the node icon right-click menu by clicking [ConfigurationManagement] and selecting [Update Property] have been revised, and now more options are includedin the [Update Property] menu.

• Specifications in Version 4.0 and earlier:

When pdate Property was selected, all the properties that could be retrieved from the devicewere updated.

• Specifications in Version 5.1:

Update Property>Update Required Property, only those properties retrieved from thedevice that are required for operation of the product are updated.

Update Property>Update All Property, all the properties that can be retrieved from thedevice are updated, in the same way that they were updated in versions 4.0 and earlier.

TipFor details regarding the updatable properties, refer to the MasterScope Network Manager User's Manual"4.2.7. Updating device information via a network".

As a result of these changes, even when device properties are updated it is still possible to retainmanually input administrator information and default target ports for an interface during operation.


34

Chapter 6. Precautions and LimitationsIn this version, there are following precautions and limitations.

Contents6.1 Precautions on Upgrading ..........................................................................................................36

6.2 Precautions on Topology Information Autodiscover...................................................................38

6.3 Limitation about Patlite reports ..................................................................................................38

Chapter 6. Precautions and Limitations

35

6.1 Precautions on UpgradingThe following explains the precautions on upgrading an old version to the latest version.

6.1.1 Precautions to take when both new and old versions ofthe monitoring terminal function exist

Network Manager supplies an arrangement whereby it can support the temporary existence of bothnew and old versions of the monitoring terminal function, considering the possibility that not allmonitoring terminals can be upgraded at once when the environment in which multiple monitoringterminals are deployed and operated is to be upgraded to the new version.

If you connect the new version of the manager function to an old version of the monitoring terminalfunction, you can perform operations such as map view and alert confirmation in the range of the oldversion of the function, but you must note the following when performing operations on the oldversion of the monitoring terminal.

Precautions on menu executions on the map viewIf an attempt is made to perform the following menu executions and window operations from an oldversion (6.1 or earlier) of the monitoring terminal function, an error message is displayed, and theycannot be performed normally.

• Manual Register execution and operation

• Map or node

Property execution and operation

• Connection-line Properties dialog box operation (newly adding)

• Connection-line Properties dialog box operation (editing)

They cannot be performed normally in the following, either.

• Registration of Simple Line from the Line Type Selection dialog box

• Port Name display setting saving (The display is switched only with the executed monitoringterminal function.)

Precautions on using the device and networkautodiscover functionIf you register a device or a network by executing the following menu from an old version (6.1 orearlier) of the monitoring terminal function, it is recorded twice in the same audit log.

• Autodiscover of TCP/IP Hosts• Autodiscover of Network and Routers• Autodiscover of Nexus

Example of an audit log in which it is recorded twice (message text):

A node is added. (NODE=node:192.168.10.250)(METHOD=AUTO DISCOVER)


36

Precautions on using the setting of the network viewmanagement authorityWith the new version of the monitoring terminal function, even a user who can view only limitedmaps and nodes can operate all maps and nodes if he or she logs in from an old version (5.1 orearlier) of the monitoring terminal function. In addition, in node copying and movement operations,the management authority set for the node after the operations differs depending on which of the newand old versions of the monitoring terminal functions is used to perform the operations.

For example, if you grant only the management authority for Map_A and Node_A to usermanagement group A, and you paste a copy of Node_A to Map_B from the new version of themonitoring terminal function, the management authority for the pasted Node_A is the same as theoriginal management authority. If, on the other hand, you perform the same operation from an oldversion of the management terminal function, the management authority for Node_A is the same asthat for Map_B, the upper map to which it is pasted.

Figure 6-1 Difference in management authority after a node copy operation

CautionThe operation in which a connection is made to the new version of the manager function with an old versionof the monitoring terminal function is a temporary avoidance method for continuing monitoring operation,and longtime operation in this state shall not be guaranteed. It is recommended to upgrade all monitoringterminal functions to the new version as soon as possible.

6.1.2 Precautions on incorporating an MIB for data collectionTo make the collection settings for a vendor-extended MIB in the data collection MIB calculationformula, you must incorporate an MIB file containing the definition of the MIB to be collected inNetwork Manager.

In MasterScope Network Manager 6.1 or later, the processing method has been changed to confirmthe definitions in the incorporated MIB file in all processes of the MIB calculation formula, so thatthe OIDs and instance numbers of the MIB can be determined and processed more accurately. For


37

this reason, even if MasterScope Network Manager operates normally in an environment ofMasterScope Network Manager 5.1 or earlier but if any MIB file has failed to be incorporated,MasterScope Network Manager may not operate normally after upgrade to version 6.1 or later.

Before the upgrade, confirm the MIB file incorporation state to check that there is no MIBincorporation error.

6.2 Precautions on Topology InformationAutodiscover

The following explains the precautions on topology information autodiscover.

Precautions on performing physical topology discoveryIf you execute physical topology discovery, you may not be able to perform the followingoperations until the completion of the process due to exclusive control for ensuring configurationinformation consistency.

• Open the menu on the icon (map or node)

• Operation from the WebAPI (configuration information management API) on the icon (map ornode)

If you select a map and execute autodiscover of Physical Topology, this has an influence on theoperation on all maps and nodes under the map. If you select multiple nodes and executeautodiscover of Physical Topology, this has an influence on the operation on the selected nodesand the maps on which the nodes are registered.

Precautions on performing ProgrammableFlow TopologydiscoveryIf you execute autodiscover of ProgrammableFlow Topology, you may not be able to performthe following operations until the completion of the process due to exclusive control for ensuringconfiguration information consistency.

• Open the menu on the map and the nodes under the map

• Operation from the WebAPI (configuration information management API) on the map and thenodes under the map

Precautions on operating the Topology Check toolIf you execute the Check Topology on a node, you may not be able to perform operations on thenode from the WebAPI (configuration information management API) until the completion of theprocess due to exclusive control for ensuring configuration information consistency.

6.3 Limitation about Patlite reportsThe Patlite report using RS-232C port, such as PHC-100A and PHE-3FB, is not supported.


38

39

MasterScope Network Manager 8.0Release Notes

NVP00RE0800-01

September, 2017 1 Edition

NEC Corporation

© NEC Corporation 2007 - 2017