INM 03[1].2.00 Releasenotes

IronView Network Manager Software Release 03.2.00 Release Notes v1.0

July 31, 2009

Document History

Document Title Summary of Changes Publication Date

IronView Network Manager Software Release 03.2.00 Release Notes v1.0

New document July 2009

IronView Network Manager Software Release 03.2.00 Page 2 of 57 Release Notes v1.0

Copyright © 2009 Brocade Communications Systems, Inc. All Rights Reserved.

Brocade, the B-wing symbol, BigIron, DCX, Fabric OS, FastIron, IronPoint, IronShield, IronView, IronWare, JetCore, NetIron, SecureIron, ServerIron, StorageX, and TurboIron are registered trademarks, and DCFM, Extraordinary Networks, and SAN Health are trademarks of Brocade Communications Systems, Inc., in the United States and/or in other countries. All other brands, products, or service names are or may be trademarks or service marks of, and are used to identify, products or services of their respective owners.

Notice: The information in this document is provided “AS IS,” without warranty of any kind, including, without limitation, any implied warranty of merchantability, noninfringement or fitness for a particular purpose. Disclosure of information in this material in no way grants a recipient any rights under Brocade's patents, copyrights, trade secrets or other intellectual property rights. Brocade reserves the right to make changes to this document at any time, without notice, and assumes no responsibility for its use.

The authors and Brocade Communications Systems, Inc. shall have no liability or responsibility to any person or entity with respect to any loss, cost, liability, or damages arising from the information contained in this book or the computer programs that accompany it.

Notice: The product described by this document may contain “open source” software covered by the GNU General Public License or other open source license agreements. To find-out which open source software is included in Brocade products, view the licensing terms applicable to the open source software, and obtain a copy of the programming source code, please visit http://www.brocade.com/support/oscd.

Export of technical data contained in this document may require an export license from the United States Government.


Contents Summary of Enhancements ..................................................................................................... 5

General Enhancements ........................................................................................................................... 5

Dashboard Enhancements ...................................................................................................................... 6

Administration Enhancements................................................................................................................ 7

Topology Manager Enhancements ......................................................................................................... 8

Configuration Manager Enhancements .................................................................................................. 9

MPLS Manager .................................................................................................................................... 12

ServerIron Manager Enhancements ..................................................................................................... 12

Traffic Analyzer ................................................................................................................................... 12

Performance Monitor ........................................................................................................................... 13

Reports.................................................................................................................................................. 13

System Requirements ............................................................................................................ 14 Minimum Server System Requirements ............................................................................................... 14

Minimum Client System Requirements ............................................................................................... 16

Required TCP and UDP Ports .............................................................................................................. 18

Software Images ..................................................................................................................... 19 Before Installing the Application ........................................................................................... 19

New Installations .................................................................................................................................. 20

Installation On a Windows Platform .................................................................................................... 21

Enabling Automatic Windows Service Startup ................................................................................... 22

Disabling Windows Service Startup .................................................................................................... 22

Changing the Selected Web Server Connection .................................................................................. 22

Installation on a UNIX Platform Using a Graphical Environment....................................................... 24

Installation on a UNIX Platform Using Console Only ......................................................................... 25

Copying IronView Network Manager to Another Server Before Upgrading ........................ 26 On a Windows Platforms...................................................................................................................... 27

Copying to a Server with no Previous IronView Network Manager Installed .................................... 27

Copying to a Server that Had a Previous IronView Network Manager Installed ................................ 30

Creating the Start Menu Options for IronView Network Manager ..................................................... 33

Adding Foundry Icons ......................................................................................................................... 34

On UNIX Platforms .............................................................................................................................. 34

Upgrading IronView Network Manager to Release 03.2.00 .................................................. 35 Performing the Upgrade ....................................................................................................................... 36

Upgrading IronView Network Manager in a Graphical Environment ................................................ 36


Upgrading IronView Network Manager in a UNIX Platform Using Console Only ........................... 38

Installing or Upgrading the Java Plug-in ............................................................................... 41 Where to Get More Information .............................................................................................. 41 How to Get Help or Report Errors .......................................................................................... 41

Web Access .......................................................................................................................................... 42

E-mail Access ....................................................................................................................................... 42

Telephone Access ................................................................................................................................. 42

Documentation Updates ......................................................................................................... 42 New Device Support, Supported Operating Systems, and Supported Web browsers .......................... 42

Address to Request IronView Network Manager Licenses .................................................................. 42

Software Fixes ......................................................................................................................... 43 Known Limitations and Issues ............................................................................................... 48

Release 03.2.00 ..................................................................................................................................... 49

Release 03.1.00 ..................................................................................................................................... 52

Service Pack 03.0.00a .......................................................................................................................... 54

Release 03.0.00 ..................................................................................................................................... 56


Summary of Enhancements These release notes contain information specific to the IronView Network Manager Release 03.2.00.

General Enhancements

Manager/Feature Enhancement Described in the following document

System Requirements IronView Network Manager server now requires Java 2 Runtime Environment (JRE) 1.6.0_13 on all server and client platforms.

The following Virtual Machines can be used as IronView Network Manager servers on Windows and Linux platforms:

• VM-Ware Workstation Version 6.5.2

o Windows: Host OS: Win 2008 Enterprise Server 64-bit

o Linux RHEL5: Host OS: RHEL5 64-bit

• Microsoft Hyper-V Manager Version 6.0.6001.18016

o Windows only: Host OS: Win 2008 Enterprise Server 64-bit

Clients can use Window Vista Business operating system.

Clients can be running Internet Explorer 7.0 and 8.0 browsers on Windows platforms. Internet Explorer is not supported on Solaris and Linux platforms.

For Firefox browsers, only Firefox 3.0.x is supported on Windows, Solaris, and Linux platforms.

System Requirements on page 14



Support for new Brocade devices

Support for the following devices has been added in this release:

• NetIron CES

• FastIron CX

• TurboIron 24X

• ServerIron ADX

Refer to the “Supported Devices” chapter of the IronView Network Manager User Guide to determine which IronView Network Manager features can be used to manage these devices. For example, GSLB Manager does not support ServerIron ADX running software release 12.0.00.

Book: IronView Network Manager User Guide

Chapter: Supported Devices

Rebranded application screens

IronView Network Manager has a new look. Its menus and screens now show the Brocade identity.

N/A

Changing HTTP or HTTPS services

There is a new, easier procedure to change the service used for client-to- server communication from HTTP to HTTPS and vice versa.


Chapter: Getting Started

Section: Changing HTTP or HTTPS Service

Dashboard Enhancements


Dashboard Device categories in Dashboard have been changed. New devices have been included in the categories and some categories in previous releases have been consolidated.

Also, Dashboard now shows the wired devices count, wireless devices count, and event count in the IronView Status pane.

Book IronView Network Manager User Guide

Chapter: Quickly Checking Network Status Using Dashboard



Dashboard Event Summary

If an IronView Network Manager user is assigned to an AOR, only the events from the devices in that user’s AOR are shown in the Dashboard Event Summary.



Section: Displaying Event Summary Details

Dashboard Event Summary

Event Summary Duration options have been changed. The new options "Today" and "Yesterday" replace the "Last 24 Hours" option



Section: Customizing Dashboard Information

Administration Enhancements


Role Manager The Role Manager table has a new column called Type. This column identifies an entry as either a Role or an AOR.


Chapter: Administering Access Accounts

Section: Managing Roles and Areas of Responsibilities

Role Manager Administrators can configure custom AORs and roles in an external AAA (RADIUS and TACACS+) server.


Chapter: Administering Access Accounts

Section: Using External Servers for Authentication and Authorization



User Manager, Edit User

The User Manager Edit User function has a new tab for the Northbound Interface (NBI) feature. Using Java or Perl scripts, the default administrator can extract device information from Brocade wired and wireless devices, as well as third party devices that are known to IronView Network Manager.


Chapter: Using Northbound Interface

Discovery Multiple Discovery profiles can be created and multiple scheduling options for Discovery can be configured. However, only one Discovery profile can run at any one time.

Furthermore, the Discovery configuration panel has been redesigned and a report of the Discovery process can be displayed.


Chapter: Enabling and Running Discovery

Licensing During the evaluation period, IronView Network Manager licenses are limited to:

• 60 days of operation

• 1 user license

• 40 licenses for MPLS configured devices. Each MPLS configured device consumes one license; however, three NetIron CES devices with MPLS configured consume only one MPLS license.


Chapter: Managing IronView Network Manager Licenses

Section: Licenses for New Installations

Topology Manager Enhancements


Network Object Manager

An IronView Network Manager user assigned to an AOR will see all the System defined device and port groups; however, under each group, the user will see only the devices that belong to his or her AOR.

Also, the IronView Network Manager user will see only the user defined device


Chapter: Creating and Managing Management Groups

Section: About the Management Groups



and port groups that belong to his or her AOR.

The IronView Network Manager user who adds the devices in Network Object Manager can specify in which AOR the devices can be assigned.

Topology maps, all views

A background image can be added to topology maps.

You can import one or more background images and bind different images to different topology views.


Chapter: Managing Network Topologies

Section: Adding a background to the map

Configuration Manager Enhancements


Configuration Wizard, scheduling payload deployment

Only the IronView Network Manager user who created the payload deployment schedule can modify the schedule. Other users who are able to view the payload cannot modify the schedule.


Chapter: Defining Brocade Wired Devices Payloads

Section: Creating a New Payload Configuration

Configuration Wizard, Wired Devices, sFlow payload

The sFlow payload allows you to deploy “sFlow forwarding” to devices interfaces.



Section: sFlow Configuration



Configuration Wizard, Wired Devices, IPv6 address support

IPv6 addresses can be entered for the following payloads:

• DNS

• DNS Name Search List

• RADIUS Servers

• SNMP Trap Receivers

• TACACS+ Servers

• Time Zone (SNTP)

Book IronView Network Manager User Guide


Sections:

• DNS

• DNS Name Table

• RADIUS Servers

• SNMP Trap Receivers

• TACACS or TACACS+ Server Table

• Time Zone/SNTP

Configuration Wizard, Wired Devices, SNTP payload

The new “Configure SNTP” parameter enables or disables the deployment of the SNTP payload to devices.



Section: Time Zone/SNTP

Configuration Wizard, Wired Devices, Protocol payload

A 32-bit number can be entered for a BGP local AS in the Protocol payload.



Sections: Protocols

Configuration Wizard, Wired Devices,

IronView Network Manager supports the ifIndex assignment change available in NetIron XMR and NetIron MLX software release 04.0.00 and later. However, IronView Network Manager must be configured to receive traps from the devices to synchronize the new ifIndex assignment in the devices.



Sections: SNMP Trap Receivers

VLAN Manager VLAN Manager displays only VLANs that contain devices that are in an IronView Network Manager user’s AOR. Empty VLANs are no longer displayed.


Chapter: Displaying a List of VLANs



Section: Displaying a List of VLANs

VLAN Manager, QOS QOS levels for a VLAN now includes “none”, which can be selected only for NetIron CES devices that do not have VLAN priority set.


Chapter: Displaying a List of VLANs

Section: Adding Tagged or Untagged Ports to VLANs

CLI Configuration Manager

You can include one or more CLI Configuration templates to a Global Configuration or Device Monitoring Configuration template.


Chapter: Creating Device Configurations and Reports Using the CLI Configuration Manager


MPLS Manager


MPLS Manager MPLS Manager now supports the NetIron CES.


Chapter: Using MPLS Manager

ServerIron Manager Enhancements


VIP Server Manager Statistics for virtual server ports and real server ports can be displayed on the VIP Server Manger table. For this feature, the VIP-Server Mgr Leaf Node Read-Write privilege has been added to IronView Network Manager.


Chapter: Managing ServerIron Features

Section: Displaying Port Statistics

Traffic Analyzer


Custom Reports, support for 32-bit AS numbers

You can enter 32-bit numbers for BGP local AS numbers when defining Routing filters for custom sFlow reports.

These AS numbers are reflected on the generated reports.


Chapter: Creating and Generating Custom sFlow Reports

Section: Routing Tab


Performance Monitor


SNMP Monitor A new MIB index page that provides more control in selecting polling MIB instances has been added to this release. Also, multiple monitoring instances of a single MIB in a collector can be configured. Furthermore, a dynamic MIB walk has been added.


Chapter: Monitoring Traffic Using SNMP

Reports


Deployment Reports If an IronView Network Manager user is assigned to an AOR, that user can view only the Deployment Reports for the payloads that he or she deployed.


Chapter: Viewing Reports

Section: Displaying the Deployment Report

Device CLI Report If an IronView Network Manager user is assigned to an AOR, that user can view only the Device CLI Report for the CLI Configuration Manager configurations that he or she deployed.


Chapter: Viewing Reports

Section: Device CLI Report


System Requirements Check the server and client requirements below.

NOTE: This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit. (http://www.openssl.org/). This product includes software written by Eric Young ([email protected]). This product includes software written by Tim Hudson ([email protected]).

Minimum Server System Requirements The following are the minimum system requirements for IronView Network Manager server for Release 03.2.00.

Windows Solaris Linux

OS version

IronView Network Manager installation is limited only to the operating system platforms listed here

Supported Windows platforms:

• Windows Server 2008

• Windows XP Professional Edition, SP 3

• Windows 2003 Server SP2

Solaris 9 and 10 (SPARC platform only) are supported

Supported RedHat Enterprise Linux (x86 platform):

Release 4 (AS, ES, WS, and Desktop)

Release 5 (Advanced Platform, Base Server, and Desktop)

Virtual Machines Support

VM-Ware workstation version 6.5.2 for Windows

Host OS: Windows 2008 Enterprise Server 64-bit

Microsoft Hyper-V Manager version 6.0.6001.18016

Host OS: Windows 2008 Enterprise Server 64-bit

Not supported VM-Ware Workstation version 6.5.2 for RHEL5 Host OS: RHEL5 64-bit

Java JRE version JRE 1.6.0_13 JRE 1.6.0_13 JRE 1.6.0_13

mailto:[email protected]�



Min. CPU speed • 1-200 devices:

2.0 GHz Pentium 4 with 2GB of RAM (minimum), 3.0 GHz Pentium 4, 3GB of RAM (recommended)

• 200-1000 devices:

2.0 GHz Dual Core CPU with 3 GB of RAM (minimum), Multi Core Xeon Processor 3000 sequence or above (or similar AMD processor) with 4 GB of RAM (recommended)

• 1000+ devices:

Dual (or more) Xeon 5000 sequence or above (or similar AMD processor) with 4+ GB of RAM (recommended)

• 1-200 devices:

Sun UltraSPARC T1 (or similar UltraSPARC processor) with 2GB of RAM (recommended)

• 200 - 1000 devices:

Sun UltraSPARC T2 (or similar UltraSPARC processor) with 4GB of RAM (recommended)

• 1000+ devices:

Sun UltraSPARC T2+ (or similar UltraSPARC processor) with 4+GB of RAM (recommended)

• 1-200 devices:

2.0 GHz Pentium 4 with 2GB of RAM (minimum), 3.0 GHz Pentium 4, 3GB of RAM (recommended)

• 200-1000 devices:

2.0 GHz Dual Core CPU with 3 GB of RAM (minimum), Multi Core Xeon Processor 3000 sequence or above (or similar AMD processor) with 4 GB of RAM (recommended)

• 1000+ devices:

Dual (or more) Xeon 5000 sequence or above (or similar AMD processor) with 4+ GB of RAM (recommended)

Min. RAM 3 GB 3 GB 32 GB

Min. Hard Disk Space

200 GB 200 GB 200 GB

TCP/IP protocol stack

Required Required Required

CD-ROM drive Required Required Required

Support for international operating systems

Yes Yes Yes


NOTES:

• On Windows platforms, device driver for the display must be configured to support at least 256 colors; otherwise, monitoring functions will not work properly.

• The IronView Network Manager installs and requires TFTP services for the configuration of Brocade IP wired and wireless devices.

• If you will be collecting sFlow traffic, it is recommended that you use Gigabit Ethernet network interface cards and have at least 2 GB of RAM on the machine running the IronView Network Manager server.

• If multiple (older) versions of JRE have been installed, then make sure that the latest JRE version (JRE-1.6.0_13 or higher) is being used. This can be checked by going to the Java Control Panel > Java > Java > View. Make sure 1.6.0_13 or higher is only enabled.

Minimum Client System Requirements Supported operating systems and client browsers must meet the following minimum requirements; otherwise, some of the features in the application will not run.


OS version

IronView Network Manager installation is limited only to the operating system platforms listed here

Supported Windows platforms:

• Windows Server 2008

• Windows XP Professional Edition, SP 3

• Windows 2003 Server SP2

• Windows Vista Business

Solaris 10 (SPARC platform only)

RedHat Enterprise Linux (x86 platform):

• Release 5 (Advanced Platform, Base Server, and Desktop)

Internet Explorer browser

7.0 and 8.0 only Not supported Not supported

Firefox 3.0 only 3.0 only 3.0 only

Java Plug In JRE-1.6.0_13 only

Runtime Environment: jre-6u13-windows-i586-p.exe

JRE-1.6.0_13 only

Runtime environment: jre-6u13-solaris-sparc.sh

JRE-1.6.0_13only

Runtime environment: jre-6u13-linux-i586.bin

Support for international operating systems

Yes Yes Yes



NOTES:

• Refer to the “Notes about Web browsers” section, in the “Getting Started” chapter of the IronView Network Manager User Guide for more information on the Internet Explorer and Firefox Web browsers.

• Apple OSX is not supported as an IronView Network Manager client.

• Before connecting to the IronView Network Manager server, the Java Plug-in must be updated to the version specified above for your operating system; otherwise, you may not be able to display some of the pages in the application. Refer to “Installing or Upgrading the Java Plug-in” on page 41.

The Java plug-in is shipped with IronView Network Manager and is also available from the Java Plug In page. To use the Java Plug In supplied by Brocade, click the “Java Plug-in Installation” link on the IronView Network Manager title panel. To install from the Java Plug-in page, see http://java.sun.com/products/plugin/.

Required TCP and UDP Ports IronView Network Manager uses the following ports for certain services:

• TCP Port 25 for SMTP for e-mail alerts. You can change the port for this service in the configuration.properties file or in the Administration > Global Preferences menu option.

• TCP Port 80 for HTTP services. You can change the port for this service at installation. Unless the default port is used, IronView Network Manager clients must include the port number in the URL when they connect to IronView Network Manager.

• TCP Port 443 for Secure HTTP services. You can change the port for this service at installation. IronView Network Manager clients must include the port number in the URL when they connect to IronView Network Manager.

• UDP Port 162 for SNMP traps. You can change the port for this service in the configuration.properties file or in the Administration > Global Preferences menu option.

• UDP port 69 for TFTP services. The port for this service cannot be changed.

• UDP Port 514 for Syslog services. You can change the port for this service in the configuration.properties file or in the Administration > Global Preferences menu option.

• UDP Port 6343 to receive sFlow packets. You can change the port for this service in the configuration.properties file or in the Administration > Global Preferences menu option.

Although the following ports are not required for communication with devices, they are used by the IronView Network Manager server:

• TCP Port 2648 is used by the Sybase database engine, which is part of IronView Network Manager.

• TCP Port 8005 is used for shutdown requests.


Software Images The following table presents the software images required for this release.


Full-installation

inm_installer_win03.2.00.exe inm_installer_solaris03.2.00.bin inm_installer_linux03.2.00.bin

Upgrade inm_upgrade_win03.2.00.exe inm_upgrade_solaris03.2.00.bin inm_upgrade_linux03.2.00.bin

Before Installing the Application NOTE: IronView Network Manager 03.2.00 will only support 3DES for SSH. Therefore, IronView Network Manager will not be able to communicate with a device via SSH if that device is configured with the ip ssh encryption aes-only command.

Obtain the following items before installing the IronView Network Manager application:

• IronView Network Manager application CD-ROM. This CD-ROM contains the full installation program.

• Entitlement Certificate. This certificate contains information you need to obtain your IronView Network Manager license files.

• IronView Network Manager User Guide

• IronView Network Manager Release Notes

• Warranty Card

• Name of the Web server. By default, this is the name of the machine on which IronView Network Manager is installed.

• Name of your SMTP mail host server and e-mail address of the SNMP event sender if you want to use the send email alerts for events.

• Administration privileges, ID, and password on the machine where IronView Network Manager will be installed.

• If you want to log debug information while IronView Network Manager is being installed or upgraded, make sure a "tmp" directory exists (C:\tmp on Windows platforms or /tmp on UNIX platforms).

• Check “Required TCP and UDP Ports” on page 18 to make sure that ports required by IronView Network Manager are not being used by other services.

Once IronView Network Manager is installed, refer to the IronView Network Manager User Guide for instructions for the following tasks:

• Adding user licenses to IronView Network Manager.

• Starting up and shutting down IronView Network Manager

• Connecting to the IronView Network Manager server


• Synchronizing server time

• Customizing IronView Network Manager

New Installations The IronView Network Manager runs as a server and is accessed through a Web browser. The server can be installed on a local or remote machine.

CAUTION: Use the procedures in this section only if you are installing a new server. Do not use this procedure to upgrade an existing server! If you do accidentally install a new server on an existing server, the database will be replaced with an empty one. All the information in the database will be deleted and you will need to rediscover and reconfigure the information. To upgrade an existing server, see “Upgrading IronView Network Manager to Release 03.2.00” on page 35.

During installation, remember the following installation requirements:

• The name of the installation directory cannot contain spaces.

• Make sure you enter the correct character when indicating directory folders or subdirectories. For example, make sure you enter "c:\ironview" instead of c:/ironview" if you are installing on a Windows platform.

• Determine which port number will be used for IronView Network Manager HTTP or Secure HTTP services. By default, IronView Network Manager uses port 80 for HTTP and port 443 for Secure HTTP. You can change the port number during installation; however, this port number must be included in the URL for IronView Network Manager when clients connect to the server.

• You will be asked to enter the name of the HTTP or HTTPS server you will be using. By default, IronView Network Manager uses the local computer name as the HTTP or HTTPS server.

• On Windows platforms, select the type of Web Server Connection you want to enable on the IronView Network Manager server. You can select IPv4, IPv6, or both. The default is IPv4.

• Enter the name of the Web server to be used for IronView Network Manager. The default name is the name of the machine on which IronView Network Manager is being installed.

• Enter the SMTP mail host name using the following format: SMTPhostname.xyzcompany.com.

For example: mailhost.brocade.com

• Enter the sender’s e-mail address using the following format: [email protected].

For example: [email protected]

• Also make sure no other application or service is using the port specified for IronView Network Manager HTTP or Secure HTTP (HTTPS) services.

NOTE: If IronView Network Manager will be using HTTPS, it is recommended that you install it on a host that has a minimum of 2.4 GHz CPU; otherwise you may experience some performance issues. Refer to “SSL and Secure HTTP Server Performance” section in the IronView Network Manager User Guide.

When you begin the installation process, a screen such as the following is displayed.


Follow the prompts on the installation screen.

Installation On a Windows Platform NOTE: This procedure is for new installations only. Refer to “Upgrading IronView Network Manager in a Graphical Environment” on page 36 to upgrade IronView Network Manager running on a Windows platform.

Follow the installation procedure below to install IronView Network Manager server on supported Windows platforms.

NOTES:

• You must have the "Administrator" privilege to be able to install and use IronView Network Manager.

• When installing IronView Network Manager on Windows XP, make sure sFlow and TFTP services are allowed. You can do this using one of the following methods:

o Disable (uncheck) Internet Connection Firewall under the Local Area Connection Properties/Advanced Settings. If it is enabled, sFlow and TFTP will not work; firewall software will block these functions.

o If you want to enable Internet Connection Firewall, set up services to allow TFTP and sFlow.

• On Windows platforms, device drivers for the display must be configured to support at least 256 colors; otherwise, some will not work properly.

1. Shut down any application running the Sybase database.

2. On Windows platform, you can check the Windows Task Manager to see if any dbeng*.exe or dbsrv*.exe programs are running. If they are end the task.

3. Ensure that DNS and hosts files are properly configured on the IronView Network Manager server and clients, or add a host entry locally on the IronView Network Manager server. Otherwise, IronView Network Manager may not work properly.


4. Run the inm_installer_win<release-number>.exe executable file located on the IronView Network Manager CD-ROM.

For example, look for inm_installer_win03.2.00.exe.

5. Follow the instructions on the installation wizard to complete the installation.

NOTE: If you do not want IronView Network Manager to be launched automatically at system startup, do not select Windows (Startup) services during installation.

6. When installation is complete, place the installation IronView Network Manager CD-ROM in a safe, accessible place. You will need this CD-ROM in case you have to restore IronView Network Manager.

7. Manually startup IronView Network Manager (refer to the IronView Network Manager User Guide) or if Windows startup services was selected, reboot the machine to start up the application.

Enabling Automatic Windows Service Startup

If Windows Services was not selected when IronView Network Manager was installed, you must manually start the application. If you want the application to automatically start whenever Windows reboots, do the following:

1. Stop the IronView Network Manager server if it is running.

2. Change to the <install-dir>\bin directory.

3. Run the "inm_service_install.bat" file by entering inm_service_install.bat <install-dir>.

4. Restart IronView Network Manager.

Disabling Windows Service Startup

To disable the automatic startup of IronView Network Manager at system reboot, do the following:

1. Stop the IronView Network Manager server if it is running.

2. Change to the <install-dir>\bin directory.

3. Run the "inm_service_remove.bat" file by entering inm_service_remove.bat <install-dir>.

4. Restart IronView Network Manager.

Changing the Selected Web Server Connection

The Web Server Connection type you select allows IPv4, IPv6, or both types of clients to connect to the IronView Network Manager server. During installation, you selected which Web Server Connection type is allowed. If you want to change that connection type, do the following:

1. Go to the <install-dir>\Tomcat\conf\ directory and open the server.xml file with a text editor.

2. Look for the following lines: 

<Connector port="80" address="0.0.0.0" maxHttpHeaderSize="8192"

maxThreads="150" minSpareThreads="25" maxSpareThreads="75"

enableLookups="false" disableUploadTimeout="true"

acceptCount="100" />






3. To disable a Web Server Connection type, remark it out by enclosing it with the following characters: 

4. To enable the Web Server Connection type, remove the characters.

For example, the example in Step 2 shows that IPv4 is the Web Server Connection type that was selected. IPv6 is disabled. To allow IPv6, as well as IPv4, as a Web Server Connection type, edit the lines to look like the following: 










5. To allow IPv6 and disallow IPv4 as a Web Server Connection type, edit the lies to look like the following: 









6. Save the file.

7. Restart the IronView Network Manager server.

Installation on a UNIX Platform Using a Graphical Environment NOTE: This procedure is only for new installations. Refer to “Upgrading IronView Network Manager in a Graphical Environment” on page 36 to upgrade IronView Network Manager running on a UNIX platform that has a graphical environment.

By default, the IronView Network Manager installer program is a graphical-based program that needs X-Windows on a UNIX environment to run. If the IronView Network Manager server is running on a machine that does not have X-Windows environment, you can still do a console (headless) installation. However it is highly recommended that you install IronView Network Manager on a server with a graphics environment.

To install IronView Network Manager on a machine that does not have X-windows, use the procedure in the section “Upgrading IronView Network Manager in a UNIX Platform Using Console Only” on page 38.

To install IronView Network Manager on a UNIX platform (Sun Solaris SPARC or RedHat Linux) using X-Windows, do the following:

NOTE: Root access is required to install and run IronView Network Manager on a UNIX platform.


2. Make sure that X-Windows is running.

3. Ensure that DNS and hosts files are properly configured on the IronView Network Manager server and clients, or add a host entry locally on the IronView Network Manager server. Otherwise, IronView Network Manager may not work properly.

4. Log into the system as root and create an “ironview” group and an “ironview” user: /usr/sbin/groupadd ironview

/usr/sbin/useradd -g ironview ironview

5. Copy the executable file from the IronView Network Manager CD-ROM to the system.

6. Change the installer file mode to executable by entering the following command: chmod uog+x <filename>

For example, chmod uog+x inm_installer_solaris03.2.00.bin

or chmod uog+x inm_installer_linux03.2.00.bin

7. Start an xterm window and enter the following: ./<filename>

For example, ./inm_installer_solaris03.2.00.bin

or ./inm_installer_linux03.2.00.bin

The installation wizard helps you complete the IronView Network Manager installation. When asked for the installation path, make sure to specify the entire path, starting from the root.

NOTE: The destination directory must be writable for the login user; if it is not, the installation program will fail and the installation script will hang.


8. Place the IronView Network Manager installation CD-ROM in a safe, accessible place. You will need this CD-ROM in case you have to restore IronView Network Manager.

9. Startup IronView Network Manager (refer to the IronView Network Manager User Guide).

NOTE: On Linux platforms, check if the native firewall is enabled. The firewall could block TFTP and SNMP packets from the IronView Network Manager server; therefore, disable the firewall.

Installation on a UNIX Platform Using Console Only NOTE: This procedure is only for new installations. Refer to “Upgrading IronView Network Manager in a UNIX Platform Using Console Only” on page 38 to upgrade an existing IronView Network Manager server from the console.

If your UNIX platform does not have X-Windows or a graphics environment, then the installer will not run and you see the following exceptions on the console:

java.lang.NoClassDefFoundError at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Unknown Source) at java.awt.GraphicsEnvironment.getLocalGraphicsEnvironment

If this is the case, then follow the procedure below to install IronView Network Manager using the console.

You need to create an inm.properties file and define the input values for the IronView Network Manager installation. Here is an example of an inm.properties file. It installs IronView Network Manager on /home/ironview/ to use HTTPS.

INSTALLER_UI=console USER_INSTALL_DIR=/home/ironview IS_HTTP_SET=Secure HTTP HTTP_PORT_NUM=80 EMAIL_SERVER_HOST=mailhost.mycompany.com [email protected] HTTPS_PORT_NUM=443

To create the inm.properties file, do the following:


2. Download the installation program (the inm_installer_<platform>.bin file) into a directory on your machine.

3. Create an inm.properties file using a text editor and save it under the directory where you downloaded the installation program.

4. Enter values for the following properties:

Installation Property Description of Property

INSTALLER_UI= Forces the installer to use console mode for installation. Make sure this parameter is set to console.

USER_INSTALL_DIR= Defines the IronView Network Manager installation directory, for example, as /home/ironview. This property is required.


IS_HTTP_SET= Enter HTTP for HTTP selection, Secure HTTP for HTTPS selection. The default is HTTP, but you must enter HTTP or Secure HTTP.

HTTP_PORT_NUM= Defines the HTTP port number that IronView Network Manager will use if IS_HTTP_SET is set to HTTP. The default is 80, but you must enter a port number.

HTTPS_PORT_NUM= Defines the HTTPS port number that IronView Network Manager will use if IS_HTTP_SET is set to Secure HTTP. The default is 443, but you must enter a port number.

EMAIL_SERVER_HOST= Defines the e-mail server name or IP address. The default is null, but you must enter a host name. A warning appears if this property is not defined.

ALERT_SENDER_ADDR= Defines the e-mail sender’s address for sending IronView Network Manager e-mail alerts. The default is null but you must enter an email address. A warning appears if this property is not defined.

5. You can add the LAX_DEBUG flag to enable the installation debug messages. For example, LAX_DEBUG=true

export LAX_DEBUG

6. Save the inm.properties file.

7. At the console command line, enter the one of the following commands: ./inm_installer_linux03.2.00.bin -f inm.properties

or ./inm_installer_solaris03.2.00.bin -f inm.properties


Copying IronView Network Manager to Another Server Before Upgrading Before you upgrade, it is recommended that you test the upgrade by copying or cloning your current IronView Network Manager application to another server to ensure the upgrade is stable.

The following procedures explain how to copy or clone your current IronView Network Manager application and its database to a different server. You should use these procedures:

• If you want to deploy IronView Network Manager on a new server but want to retain the current data.

• Before you upgrade to a new version of IronView Network Manager to ensure the upgrade is stable and to minimize upgrade effects on the production server.


You can copy your IronView Network Manager application and its data to a different server if the target server is running the same operating system as the current server. For example, you can copy IronView Network Manager running on Windows to another server running Windows. You can copy IronView Network Manager on a Linux server to another server running Linux. (You can copy IronView Network Manager on a Linux WS3 server to a Linux WS3 or WS4 server.)

If IronView Network Manager is running on Windows, go to the section “On a Windows Platforms” on page 27.

If IronView Network Manager is running on a Linux or Solaris server, follow the procedure under “On UNIX Platforms” on page 34.

On a Windows Platforms To copy IronView Network Manager on a server running Windows, use one of the following procedures:

• “Copying to a Server with no Previous IronView Network Manager Installed” on page 27

• “Copying to a Server that Had a Previous IronView Network Manager Installed” on page 30

Copying to a Server with no Previous IronView Network Manager Installed

Use the procedure below to copy your current IronView Network Manager application and its database to a new server, one that has never had an IronView Network Manager installed.

1. Shut down the IronView Network Manager on the current server running Windows.

2. Make a backup of the entire IronView Network Manager installation directory under the <install-dir> directory.

3. Copy the contents of the entire <install-dir> to a backup media.

4. On the new server running Windows, create an IronView Network Manager <install-dir> directory that has the same name and the same drive path as the one in the current server.

For example, if IronView Network Manager is installed in the C:\ironview\ directory on the current server, create a C:\ironview\ directory on the new server.

Copying from C:\ironview\ to D:\ironview\ will not work. The same drive path must be used.

5. Copy the entire contents of the IronView Network Manager <install-dir> directory on the current server to the newly created directory on the new server.

6. Wait until the copy process is complete, then go to the new server and change the name of that server in the files listed below, replacing “Name” with the name of the new Windows server. To identify the Windows server name, issue the command ipconfig /all from a Windows command prompt. “Host Name” identifies the name of the server.

• <install-dir>\startup.bat file. Look for the following line: dbspawn -f "dbsrv10 -ti 0 -gl all -ch 25p -c 10M -o ..\logs\db_output.log -os 1M -x tcpip{ServerPort=2648} -n IronView_NAME

• <install-dir>\ htdocs\WEB- INF\classes\com\foundrynet\server\util\configuration.properties file. Change the parameter: Database.name1=IronView_NAME

• <install-dir>\database\db_utility.bat file. Look for the following line: %ASA_HOME%\dbisql -c "eng=IronView_NAME" -host localhost -port 2648 %2 %3 %4 %5 %6 %7 %1


• <install-dir>\database\run_sql.bat file. Look for the following line: %JAVA_HOME%\bin\java -Dtomcat.home=C:\images\ironview2000New com.foundrynet.server.DataAccess.ExecuteSqlFile IronView_NAME %1

Make sure you save all updated files.

Since IronView Network Manager has never been installed on the server, two key variables need to be added to the Windows registry.

7. Go to the Windows command line and enter the regedit command.

8. When the Registry Editor opens, expand the HKEY_LOCAL_MACHINE folder and select the SOFTWARE folder. For example:

9. Right click on the SOFTWARE folder and select New -> Key

10. Enter “FoundryNetworks” as the value of the new Key.

11. Once the “FoundryNetworks” Key is created, create another Key called “IronViewNetworkManager” under the FoundryNetworks Key.

12. Right-click on the FoundryNetworks folder and select New -> Key and enter “IronViewNetworkManager” as the value of the new Key.


13. Under the “IronViewNetworkManager” Key, create two string values. First, with the

IronViewNetworkManager Key selected in the left pane, right-click the right pane area and select New --> String Value.

14. Enter “Installed_Dir” as the value of the first string.

15. Next, repeat Step 12 and enter “Log_Event” as the value of the second string.

At this point, you should have the following strings under “IronViewNetworkManager”.

16. Right-click the “Installed_Dir” string, select Modify, then enter the name of the <install-dir> as the

value of the “Installed_Dir” string. For example, you should see something similar to the following if your installation directory is “C:\ironview”:


17. Right-click the “Log_Event” string, select Modify, then enter 6 as the value for the string. Once entered, you should see “Log_Event” set to “6” in the Data column of the Window Registry screen.

18. Exit from the Windows Registry.

19. Go to the Windows command line and enter the following command: <install-dir>\startup.bat.

20. As IronView Network Manager starts up, check its Java console to make sure no error is reported.

21. Log into IronView Network Manager to make sure the client connects to the server successfully.

22. Log out of IronView Network Manager.

23. Go to the server Windows command line and enter the following command to shut down the application: <install-dir>\shutdown.bat

24. Make sure the server stops successfully by monitoring its status from its Java console. No error should be reported.

25. If AAA authentication is configured in the original server, then add the AAA configuration in the new IronView Network Manager server, adding the AAA client hostname, AAA client IP address, and authentication used.

26. At this point, you can upgrade IronView Network Manager on the new server. Follow the upgrade instructions presented in this document.

27. After upgrade is complete, go to the Windows command line and start up IronView Network Manager by entering the following: <install-dir>\startup.bat

28. As IronView Network Manager starts up, verify that the server starts successfully by monitoring its status from its Java console.

29. Log into IronView Network Manager on the new server and reconfigure Discovery parameters as needed (for example, define its Ping Sweep parameters) since the new server may reside in a different quadrant of your network.

30. Run Discovery. Once Discovery is complete, IronView Network Manager in the new server is ready for deployment. You can either upgrade IronView Network Manager on the current production server or deploy the one you installed on the new server.

31. Go to “Creating the Start Menu Options for IronView Network Manager” on page 33 to add the IronView Network Manager options to the Windows Start menu. You can also add the IronView Network Manager icons to the options by following the procedure in the section "Adding Foundry Icons" on page 34.

Copying to a Server that Had a Previous IronView Network Manager Installed

If the server to which IronView Network Manager will be copied had IronView Network Manager previously installed, it is recommended that you uninstall it using the Windows Add/Remove Programs. Then make sure the IronView Network Manager directory is removed from the server after uninstalling IronView Network Manager.

Next, follow the procedure in this section to copy your current IronView Network Manager set-up to the new server.

1. Shut down the IronView Network Manager on the current server.


2. Make a backup of the entire IronView Network Manager installation directory under the <install-dir> directory.

3. Copy the contents of the entire <install-dir> directory to a backup media.

4. On the new server, create an IronView Network Manager <install-dir> directory that has the same name and same drive path as the one on the current server. The <install-dir> may exist on the server since it contained an earlier installation of IronView Network Manager. Make sure this directory is empty. Also, make sure its name and drive path are the same as the <install-dir> on the current server.

For example, if IronView Network Manager on the current server is in C:\ironview\, make sure “C:\ironview” directory exists on the new server.

5. Copy the contents of the <install-dir> directory in the current server into the <install-dir> directory of the new server.

6. Wait until the copy process is complete, then change the name of the server in the files listed below, replacing “Name” with the name of this new Windows server. To identify the Windows server name, issue the command ipconfig /all from a Windows command prompt. “Host Name” identifies the name of the server name:

• <install-dir>\startup.bat file. Look for the following line: dbspawn -f "dbsrv10 -ti 0 -gl all -ch 25p -c 10M -o ..\logs\db_output.log -os 1M -x tcpip{ServerPort=2648} -n IronView_NAME

• <install-dir>\ htdocs\WEB- INF\classes\com\foundrynet\server\util\configuration.properties file. Change the parameter:

Database.name1=IronView_NAME

• <install-dir>\database\db_utility.bat file. Look for the following line: %ASA_HOME%\dbisql -c "eng=IronView_NAME" -host localhost -port 2648 %2 %3 %4 %5 %6 %7 %1

• <install-dir>\database\run_sql.bat file. Look for the following line: %JAVA_HOME%\bin\java -Dtomcat.home=C:\images\ironview2000New com.foundry.server.DataAccess.ExecuteSqlFile IronView_NAME %1

Make sure you save all updated files.

Since IronView Network Manager was previously installed on the server, the server should have IronView Network Manager registry keys; however, they need to be modified. If the keys do not exist, follow Step 7 through Step 17 below to create the keys.

7. Go to the Windows command line and enter the regedit command.

8. When the Registry Editor opens, expand the HKEY_LOCAL_MACHINE folder and select the SOFTWARE folder. For example:


9. Under the SOFTWARE folder, look for the “FoundryNetworks” Key, expand it, then highlight the “IronViewNetworkManager” Key.

10. Right-click the “Installed_Dir” string, select Modify, then enter the name of the <install-dir> as the value of the string. For example, you should see something similar to the following if IronView Network Manager is installed in “C:\ironview”:

11. Right-click the “Log_Event” string, select Modify, then enter 6 as the value for the string. Once

entered, you should see “Log_Event” as set to “6” in the Data column of the Window Registry screen.

12. Exit from the Windows Registry.

13. Go to the Windows command line and start up IronView Network Manager by entering the following: <install-dir>\startup.bat




17. Go to the Windows command line and shut down the application, by entering the following: <install-dir>\shutdown.bat

Make sure the server stops successfully by monitoring its status from its Java console. No errors should be reported.


19. After upgrade is complete, go to Windows command line and start up IronView Network Manager by entering the following: <install-dir>\startup.bat

20. As IronView Network Manager starts up, verify that the server starts successfully by monitoring its status from its Java console.

21. Log into IronView Network Manager on the new server and reconfigure Discovery parameters as needed (for example, define its Ping Sweep parameters) since the new server may reside in a different quadrant of your network.


23. Go to “Creating the Start Menu Options for IronView Network Manager” on page 33 to add the IronView Network Manager options to the Windows Start menu. You can also add the IronView


Network Manager icons to the options by following the procedure in the section “Adding Foundry Icons” on page 34.

Creating the Start Menu Options for IronView Network Manager

Optionally, you can add start up and shut down options to the Windows Start menu. These options allow you to start up and shut down IronView Network Manager from the Start menu. Follow the following procedure:

1. First, to add the option to start up IronView Network Manager, click the Windows Start button.

2. From the Windows Start menu, select “Control Panel”, then “Taskbar and Start Menu”.

3. Click the "Start Menu" tab to display the “Taskbar and Start Menu" properties page.

4. Select the “Classic Start Menu” radio button, then click the Customize... button.

5. Click the Add... button to display the “Create Shortcut” page.

6. Enter the path of the IronView Network Manager startup.bat file (for example, C:\ironview\startup.bat) or click the Browse... button and look for the file.

7. Click Next to display the “Select Program” page.

8. Select a folder for the IronView Network Manager shortcut location.

9. Click the "New Folder..." button and enter "Foundry IronView Network Manager" for the folder name.

10. Click Next to display the “Select a title for the program” page.

11. Enter "Startup IronView Server" as the name of the shortcut.

12. Click the Finish button.

13. Next, to add the option to shut down IronView Network Manager, click the Windows Start button.

14. From the Windows Start menu, select “Control Panel” then “Taskbar and Start Menu”.

15. Click on the "Start Menu" tab to display the “Taskbar and Start Menu properties” page.

16. Select the “Classic Start Menu” radio button, then click the Customize... button.

17. Click the Add... button to display the “Create Shortcut” page.

18. Enter the path of the IronView Network Manager shutdown.bat file (for example, C:\ironview\shutdown.bat) or click the Browse... button and look for the file.

19. Click Next to display the “Select Program” page.

20. Select the "Foundry IronView Network Manager" folder you created in Step 8 above from the Program.

21. Click Next to display the “Select a title for the program” page.

22. Enter "Stop IronView Server" as the name of the shortcut.

23. Click the Finish button.

24. Click on OK to exit.


Adding Foundry Icons

After completing the steps in the "Creating the Start Menu Options for IronView Network Manager” section on page 33, the Start menu options will show generic icons. If you want to display Foundry icons for these options, do the following:

1. To change the icon for Start up IronView Network Manager, go to Windows Start -> All Programs -> Foundry IronView Network Manager.

2. Right-click on "Startup IronView Server", then select Properties.

3. Click the Change Icon button to display the “Change Icon” page.

4. Browse through the directories to select the startup.ico file. (For example, the file might be in C:\ironview\startup.ico.)

5. When the icon appears in the Change Icon box, select the icon, then click OK.

6. To change the icon for Stop IronView Network Manager, go to Start > All Programs > Foundry IronView Network Manager.

7. Right-click on "Stop IronView Server" then select Properties.

8. Click the Change Icon button to display the “Change Icon” page.

9. Browse through the directories and select the shutdown.ico file. (For example, the file might be in C:\ironview\shutdown.ico.)

10. When the icon appears in the Change Icon box, select the icon, then click OK.

On UNIX Platforms To copy IronView Network Manager on a server running a UNIX operating system, such Linux or Solaris, do the following:

1. Shut down the IronView Network Manager on the current server.

2. Make a backup of the entire IronView Network Manager installation directory under the <install-dir>.

3. Save the entire file system to a backup media. It is recommended that you use -tar to zip up the file onto the backup media:

• Tar File Creation: tar -cvf inmbackup.tar ./ironview

• Tar File Compression: gzip inmbackup.tar

4. On the new server, copy the zipped tar file to a folder that has the same name as the <install-dir> folder on the current server. For example, <install-dir> is a directory located from the root “/” level of the current UNIX server; therefore, the tar file must be copied into root “/” of the new server.

5. Unzip and extract the tar file to create the directory:

• Unzip the tar file: gunzip inmbackup.tar.gz

• Extract the tar file: tar –xvf inmbackup.tar

6. After the copy is completed, go to the new server and change the name of the IronView Network Manager host server in the following files:

• <install-dir>/startup.sh file. Look for the following line:


dbspawn -f "dbsrv10 -ti 0 -gl all -ch 25p -c 10M -o ../logs/db_output.log -os 1M -x tcpip{ServerPort=2648} -n IronView_NAME

NOTE: The text “dbsrv10” appears if IronView Network Manager uses Sybase 10; “dbsrv10” is displayed if the application uses Sybase 10.

• <install-dir>/htdocs/WEB- INF/classes/com/foundrynet/server/util/configuraton.properties file. Change the parameter: Database.name1=IronView_NAME

• <install-dir>/database/db_utility.sh file. Look for the following line: %ASA_HOME%/dbisql -c "eng=IronView_NAME" -host localhost -port 2648 %2 %3 %4 %5 %6 %7 %1

• <install-dir>/database/run_sql.sh file. Look for the following line: %JAVA_HOME%/bin/java -Dtomcat.home=C:/images/ironview2000New com.foundrynet.server.DataAccess.ExecuteSqlFile IronView_NAME %1

NOTE: In all files, replace “Name” with the name of the IronView Network Manager host server. Make sure you save all updated files.

7. Enter the following to start up IronView Network Manager: <install-dir>/startup.sh




11. Enter the following to shut down IronView Network Manager: <install-dir>/shutdown.sh

12. Make sure the server stops successfully by monitoring its status from its Java console. No errors should be reported.


14. After upgrade is complete, enter the following to start up IronView Network Manager: <install-dir>/startup.sh

15. As IronView Network Manager starts up, verify that it starts up successfully by monitoring its status from its Java console.

16. Log into IronView Network Manager on the new server and configure Discovery parameters as needed (for example, define its Ping Sweep parameter) since the new server may reside in a different quadrant of your network.


Upgrading IronView Network Manager to Release 03.2.00


CAUTION: Use the procedures in this section only if you are upgrading an existing IronView Network Manager server. Do not use this procedure to install a new server! To install a new server, see “New Installations” on page 20.

NOTE: IronView Network Manager 03.2.00 will only support 3DES for SSH. Therefore, IronView Network Manager will not be able to communicate with a device via SSH if that device is configured with the ip ssh encryption aes-only command.

You can upgrade to IronView Network Manager Release 03.2.00 if your system is running IronView Network Manager Release 03.1.00.

If your system is running a version earlier than Release 03.1.00, you must upgrade to Release 03.1.00 first; otherwise, the upgrade will fail.

Download the release and release notes from the Brocade Knowledge Portal (kp.foundrynet.com) if you have a valid support contract and permission to access the site. Refer to the appropriate release notes for upgrade information.

NOTE: It is recommended that you copy your IronView Network Manager to another server and test the upgrade on that server before you upgrade the production system. Refer to “Copying IronView Network Manager to Another Server Before Upgrading” on page 26 for details.

Performing the Upgrade Before you upgrade, make sure you backup your database.

To upgrade IronView Network Manager Release 03.1. 00 to Release 03.2.00, download the Release 03.2.00 upgrade programs from kp.foundrynet.com. Use the most appropriate procedure below to install the program:

NOTE: Be sure to read the upgrade procedure thoroughly before attempting the upgrade. Also, make sure you test the upgrade process on a test server before upgrading the production server.

Upgrading IronView Network Manager in a Graphical Environment

NOTE: This procedure is only for a upgrading your IronView Network Manager system. Refer to the IronView Network Manager User Guide for installation instructions.

Use this procedure to upgrade an existing IronView Network Manager server on a Windows platform or a UNIX platform that has X-Windows. Refer to “Upgrading IronView Network Manager in a UNIX Platform Using Console Only” on page 38 if your UNIX environment does not have X-Windows.

1. Shut down the IronView Network Manager server application you are upgrading. The server must be shut down before you begin.


3. Copy any .properties files you modified to a directory or folder that is not in the <install-dir> folder or directory. For example, you may have modified the following files:

• change.properties

• cliShowMessages.properties

• cliResponses.properties

• foundry_alarm.properties

• mib.properties


• mib_categories.properties

User-configured parameter values in some of the .properties files are not retained during the backup. You will need to refer to the saved files to restore the parameter values after the upgrade.

4. Make sure you are logged in at the required privilege level:

• Windows: You must be logged in at the Administrator level.

• UNIX: X-Windows must be running and you must be logged in at the root level.

5. Start the upgrade by running the executable file:

• For Windows platforms, run the inm_patch_upgrade_win<release-number>.exe. (For example: inm_upgrade_win03200.exe)

• For Solaris platforms, run

chmod oug+x inm_upgrade_solaris

<release-number>.bin

/inm_upgrade_solaris<release-number>.bin

For example, chmod oug+x inm_upgrade_solaris03200.bin

./inm_upgrade_solaris03200.bin

• For Linux platforms, run

chmod oug+x inm_upgrade_linux

<release-number>.bin

/inm_upgrade_linux<release-number>.bin

For example, chmod oug+x inm_upgrade_linux03200.bin

./inm_upgrade_linux03200.bin

6. Follow the prompts. If the program prompts you to do so, select the directory where the IronView Network Manager is installed. The program copies all the files into that directory.

• On Windows systems, the program looks for the directory automatically. The program prompts you to select or browse for the directory only if the program cannot find the directory containing the previous installation.

• On UNIX systems, you must select or browse for the directory.

The program executes an update script to perform the necessary configuration for the installation. This may take several minutes to complete, based on the size of the database.

NOTE: If you receive an error message stating that the SMTP mail server host name and e-mail address format you entered is incorrect, continue with the installation. Then go to the configuration.properties file to correct the host name and e-mail address format.

7. When the upgrade is complete, clear the Java cache on the IronView Network Manager clients from the Java Control Panel by doing the following:

a. Launch the Java Control Panel:


On Windows platforms, click the Java coffee cup icon on the Windows Control Panel.

On UNIX platforms, enter /usr/java/jre1.5.0_15/bin/ControlPanel on the command prompt.

b. When the Java Control Panel loads, click the General tab.

c. Click on the "Delete Files..." button.

d. Click OK to delete the temporary files for "Downloaded Applets", "Downloaded Applications", and "Other Files".

8. Click OK to close the applet.

9. Clear the Web browser cache by following the instructions that comes with your Web browser.

10. Close the Web browser, and then open a new session of the Web browser.

11. Start up and log in to IronView Network Manager.

12. Run Discovery to make sure all devices on the network that you are to be managed by IronView Network Manager are in the database.

Upgrading IronView Network Manager in a UNIX Platform Using Console Only

NOTE: This procedure is only for a upgrading your IronView Network Manager system. Refer to the IronView Network Manager User Guide for installation instructions.

To upgrade an IronView Network Manager server on a UNIX platform that does not have X-Windows, do the following:

1. Shut down the IronView Network Manager server application you are upgrading. The server must be shut down before you begin the upgrade.


3. Copy any .properties files you modified to a directory or folder that is not in the <install-dir> folder or directory. For example, you may have modified the following files:

• change.properties

• cliShowMessages.properties

• cliResponses.properties

• foundry_alarm.properties

• mib.properties

• mib_categories.properties

User-configured parameter values in some of the .properties files are not retained during the backup. You will need to refer to the saved files to restore the parameter values after the upgrade.

4. Make sure you have enough disk space for the upgrade. Disk space should be twice the amount of disk space used by the current IronView Network Manager application.

5. Make sure you are logged in at the root level of your operating system.

6. Create an inm.properties file with the following parameters:

Installation Property Description of Property

INSTALLER_UI=console Forces the installer to use console mode for installation. Make sure this


parameter is set to console.

USER_INSTALL_DIR= Defines the IronView Network Manager installation directory, for example, as /home/ironview. This property is required.

INM_PATH= Defines the path to IronView Network Manager, for example, /home/ironview. This property is required.

IS_HTTP_SET= Enter HTTP for HTTP selection, Secure HTTP for HTTPS selection. The default is HTTP, but you must enter HTTP or Secure HTTP.

HTTP_PORT_NUM= Defines the HTTP port number that IronView Network Manager will use if IS_HTTP_SET is set to HTTP. The default is 80, but you must enter a port number.

HTTPS_PORT_NUM= Defines the HTTPS port number that IronView Network Manager will use if IS_HTTP_SET is set to Secure HTTP. The default is 443, but you must enter a port number.

EMAIL_SERVER_HOST= Defines the e-mail server name or IP address. The default is null, but you must enter a host name. A warning appears if this property is not defined.

ALERT_SENDER_ADDR= Defines the e-mail sender’s address for sending IronView Network Manager e-mail alerts. The default is null but you must enter an email address. A warning appears if this property is not defined.

WEB_SERVER_NAME= Defines the Web server name for the IronView Network Manager HTTP/HTTPS server. The default is the local machine DNS name. This property is required.

For example, you may have the following lines in the inm.properties file: INSTALLER_UI=console USER_INSTALL_DIR=/var/tmp/b2 INM_PATH=/var/tmp/b2 IS_HTTP_SET=HTTP HTTP_PORT_NUM=80 HTTPS_PORT_NUM=443 EMAIL_SERVER_HOST=relay.foundrynet.com [email protected] WEB_SERVER_NAME=sparct1000

7. Save the file in the same directory where the upgrade file is stored.

8. Run the upgrade program by entering one of the following commands:

• For Solaris platforms, enter: ./inm_upgrade_solaris03.2.00.bin -f inm.properties

• For Linux platforms, enter: ./inm_upgrade_linux03.2.00.bin -f inm.properties


The upgrade may take several minutes to complete, depending on the size of the database.

9. Upgrade your Java plug-in to the version specified for your operating system in the section “Minimum Client System Requirements” on page 16. If you do not upgrade the JRE plug-in, some panels may not display properly, menu buttons may disappear, and other display problems may occur. Refer to “Installing or Upgrading the Java Plug-in” on page 41.

10. After the upgrade, check the .properties files and reconfigure any parameters whose values were not retained during the upgrade. You should have backed up the .properties files in Step 4.

NOTE: The properties files that come with the upgrade contain new parameters for the new features and enhancements. Do not replace the new properties files with copies you made before the upgrade. You must re-enter the values you want in the new properties files.

11. Save the upgrade executable program to a backup medium in case you need to re-install the upgrade. It should be kept with the original IronView Network Manager installation CD-ROM and the system backups you make. You will need all these items in case you have to restore the IronView Network Manager and your system data.

12. After the upgrade, clear the Java cache on the IronView Network Manager clients and servers from the Java Control Panel by doing the following:

a. Launch the Java Control Panel by entering /usr/java/jre1.5.0_15/bin/ControlPanel on the command prompt.

b. When the Java Control Panel loads, click the General tab.

c. Click on the "Delete Files..." button.

d. Click OK to delete the temporary files for "Downloaded Applets", "Downloaded Applications", and "Other Files".

e. Click OK to close the applet.

13. Clear the Web browser cache by following the instructions that comes with your Web browser.

14. Close the Web browser, then open a new session of the Web browser.

15. Start up and log in to IronView Network Manager.

16. Run Discovery to make sure all devices on the network that you are to be managed by IronView Network Manager are in the database.

NOTE: After upgrading to this release, IronView Network Manager may not shut down completely if the original name for the IronView Network Manager server was changed sometime before the upgrade. During the upgrade, IronView Network Manager does not update the server’s name in the configuration.properties file.

To remedy this situation, edit the configuration.properties file using a text editor. Go to the Database.name1 parameter and enter the new name of the machine on which the IronView Network Manager server is installed. Enter this name in the IronView_<INM-server-name> line, for example, IronView_lab0123.

Do not change the value of Database.name1 unless you have the situation described above.



Installing or Upgrading the Java Plug-in Make sure the correct version of the Java plug-in is installed; otherwise, your browser may crash, pages may not display properly, menu buttons may disappear, or runtime errors may be displayed. You can determine what the installed version of the Java plug-in is by enabling the Java console for the browser, opening the console, and checking the version number shown at the top. If the version is different from what is specified in the section “Minimum Client System Requirements” on page 16, install the correct version.

The Java plug-in is included on the IronView Network Manager CD-ROM and is also available from the Java Plug-in Web site. To use the supplied plug-in, click the “Java Plug-in Installation” link on the IronView Network Manager title page. To install the plug-in from the Java Plug-in Web site, refer to http://java.sun.com/products/plugin/.

NOTE: Web browsers place all the files, including downloaded Web pages, in the cache as you view various pages. When the cache fills up, old pages, even the Java files, are deleted from cache. Flushed pages need to be downloaded again when necessary.

You can increase the Web browser cache size to prevent cached pages from being deleted. Refer to instructions for your Web browser to determine how to increase the browser cache. For example, in Internet Explorer, go to Tools > Internet Options > General: Settings > Amount of disk space to use.

If the client experience out of memory conditions, you may need to allocate more memory to the Java plug-in. Do the following:

1. Launch the Java Control Panel.

2. Click on Java tab and then the Java Applet Runtime Settings View button.

3. When the Java Runtime Settings dialog box appears, select the JRE version currently running (it is also on the first line in Java Console).

4. In Java Runtime Parameters for that version, enter one of the following commands:

• Xmx256m for 256MB cache

• Xmx512m for 512MB cache

NOTE: The commands are case sensitive.

Where to Get More Information The features presented in these release notes are discussed in detail in the IronView Network Manager User Guide. The guide can be found on the Brocade Knowledge Portal (kp.foundrynet.com).

Manuals and release notes for this product may be updated between releases. For the latest edition of manuals and release notes, check the Brocade Knowledge Portal at kp.foundrynet.com.

How to Get Help or Report Errors If you need assistance or find errors in the manuals, contact Brocade using one of the following options.


Web Access Go to kp.foundrynet.com and log in to the Knowledge Portal (KP) to obtain more information about a product, or to report documentation errors. To report errors, click on Cases > Create a New Ticket.

E-mail Access Send an e-mail to: [email protected]

Telephone Access United States: 800-752-8061

Europe, Middle East & Africa: Not Toll Free: +1 800-AT FIBREE (+1 800 28 34 27 33)

Asia Pacific: Not Toll Free: +1 800-AT FIBREE (+1 800 28 34 27 33)

Areas unable to access 800 numbers: +1-408-333-6061

Documentation Updates This section provides information on last-minute additions and corrections to the IronView Network Manager User Guide and Help.

New Device Support, Supported Operating Systems, and Supported Web browsers There is a typographical error in the " Support for new Brocade devices" row, under the "What's New in This Edition" section of the "About This Guide" chapter.

The new Brocade devices supported by this release are the following:

• NetIron CES

• FastIron CX

• TurboIron 24X

• ServerIron ADX

Refer to the “Supported Devices” chapter of the IronView Network Manager User Guide to determine which IronView Network Manager features can be used to manage these devices. For example, GSLB Manager does not support ServerIron ADX running software release 12.0.00.

Also, the correct Web browsers and operating systems supported for IronView Network Manager clients are listed in the "Minimum Client System Requirements" on page 16.

Address to Request IronView Network Manager Licenses Send your request for new licenses either to [email protected] or [email protected].




Software Fixes The table below lists the software fixes in this release. The table is sorted alphabetically first by category, then by Priority (P). Values under the P column can be one of the following:

0 = Critical

1 = Major

2 = Medium

3 = Minor

4 = Enhancement

Category P Description Bug ID#

ACL Manager, ACL

1 Symptom: Deploying ACL Group payloads to the NetIron XMR and NetIron MLX may display a message indicating that some ACL entries cannot be removed. These ACL entries are used by IronView Network Manager to deploy ACL groups, but are removed once the deployment is complete. However on NetIron XMR and NetIron MLX running release 03.6.00 through 03.9.00a, these ACL entries are not removed. Also, they cannot be removed from the device CLI.

Resolution: Fixed in Release 03.2.00.

90916, 90957, and 93766

ACL Manager, ACL

2 Symptom: Lines for ACL remarks and the ACL entries may become inverted when the ACL is imported into IronView Network Manager.


93599

Administration, Discovery

1 Symptom: If the "Run Discovery on Startup" flag is checked in the Discovery, General page, then the IronView Network Manager Server fails to startup completely. No logins are allowed.


98128

Administration, Discovery

2 Symptom: If discovery is configured to automatically run at startup, you may not be able to login to IronView Network Manager using a Web browser.


96645

Administration, Event Reception

2 Symptom: Event Reception does not display SNMP configuration options.


102966



Administration, Global Preferences and front panel displays

2 Symptom: If HTTPS is selected as the Web Element Management Communication Setting in Global Preferences, it may take awhile before the device front panel displays.


91499

Administration, User Manager

2 Symptom: IronView Network Manager is unable to delete a stale user session from the Login Session table.


97406

Change Manager, Backup Configuration Manager

1 Symptom: Change manager manual backup operation fails if the LLDP chassis id on the device contains the characters * and \.


99204

Change Manager, Backup Configuration Manager

4 Symptom: FESX 04.3.00 images cannot be backed up to, imported into, nor deployed from IronView Network Manager.


95427

Change Manager, Configuration

1 Symptom: If SSH v1 is configured on a device and SCP only is selected as the Device Communication service in IronView Network Manager (Administration > Global Preferences > Device Communication), the following error messages may be displayed if that device is selected from Change Manager and the GET button is clicked:

Retrieving TftpCfgTransferPL... Error in retrieving TftpCfgTransferPL: SshException: java.net.SocketException Finished


81057

Configuration Manager, CLI Configuration Manager

1 Symptom: Deployment of large configurations created in CLI Configuration Manager may fail when Device Communication Setting in Administration > Global Preferences is set to SSH.


94848


3 Symptom: Error messages appear when deploying QOS commands to FES devices.


95045



Configuration Manager, Configuration Wizard

2 Symptom: When creating a payload from Configuration Wizard to deploy an ACL to a virtual routing interface (VE), the VEs are not visible or available to choose in the device list. Only physical ports are seen.


98481

Configuration Manager, VLAN Manager

1 Symptom: When a user tries to create 1000 VLANs on a FastIron SuperX device with a port in all of those, the client memory is exhausted

Probability:


98371


2 Symptom: A failure occurs when IronView Network Manager tries to deploy 166 VLANs containing a single tagged port. Even though the system maximum is set to 200, IronView Network Manager fails to deploy port 1/1 at the 166th VLAN. The initial error message presented is: Deployment update: device:SuperX_INM_Automation[180.180.180.10], DDJid=5016, messageType=3, message=Deploying VlanPortMemberHPL..., exception=null Deployment update: device:SuperX_INM_Automation[180.180.180.10], DDJid=5016, messageType=2, message=Error in deploying VlanPortMemberHPL, exception=The SNMP agent at 180.180.180.10 responded with an error (Error in response. Response message would have been too large.


95361


2 Symptom: VLAN configurations that are saved in release 03.0.00 cannot be modified after upgrading the system to release 03.1.00.


95426

Dashboard 2 Symptom: Help for Dashboard cannot be launched in the following scenario: Launch Network Object Manager by clicking on a slice of the Wired Device pie chart or Inventory chart in Dashboard. Then close Network Object Manager and try to click on the Dashboard Help at this point. Help does not launch.


95334



Database 0 Symptom: IronView Network Manager does not start up because of a database crash.


100449

Device Configuration, Configuration Wizard

2 Symptom: If the Sampling Interval value is not entered, the sFlow payload deployment does not appear in the running configuration.


100294

Diagnostic 2 Symptom: The runSQL.sh diagnostic tool that executes Sybase SQL commands (for example, query) is not operational for UNIX platforms.


95300

Event Manager, Custom Reports

2 Symptom: When configuring target devices and target ports in the report definitions, Info types of severities and Traps and Syslog events are not filtered.


96606

Event Manager, Event Log

1 Symptom: When the IronView Network Manager is running on Linux platforms on networks with IPv6 only network interfaces, internal IronView Network Manager traps may be dropped.


95132


2 Symptom: When filtering and deleting logs by severity in the Event Log, event logs for all severities are deleted.


96675


2 Symptom: IronView Network Manager does not interpret traps from BigIron RX correctly.


104696



General, Web browser

1 Symptom: Several issues occur when the incorrect Java Plug-in JRE is installed on Windows platforms and the Firefox browser is used to run the IronView Network Manager client. For example:

• GSLB Manager and L2 ACL Manager

• Wireless RADIUS payload cannot be configured with a server name.

• Wireless Reload APs payload cannot be configured from a Firefox 2.X browser.


83448, 83292

Installation 2 Symptom: If a leading space is entered for the HTTP or HTTPS port number during installation, the IronView Network Manager server connection will not work.


103478

Network Object Manager

1 Symptom: If Network Object Manager is launched from a topology map or from Dashboard, the browser may hang after a user tries to resize and close the Network Object Manager window.


94885

Other 1 Symptom: Browser session does not timeout if there is an active server-to-client communication.


49616

Other 1 Symptom: Deploying a unified image fails if the default TFTP directory has been changed.


97176

Other 1 Symptom: Weekly backups occur one day after the scheduled day.


101124

Other 2 Symptom: If the backup directories have different years, for example when the year rolls over, backup processes sort the directories incorrectly and delete the wrong directory


101155



Other, SNMP 2 Symptom: The message “SnmpException: Unable to discover engineID” is displayed when SNMP v3 is configured but the device is offline.


99371

Performance Monitor, SNMP Collector

2 Symptom: When a device that is bound to an SNMP collector is deleted from Network Object Manager, the Collection Status Summary table may still show that collector’s status. If there is a live graph plotted prior to the deletion of the device, the graph that was reporting on that device still shows the collector. In this state, any change to the parameters of the graph can display a Java error in the client console.


94733

Performance Monitor, SNMP Monitor

2 Symptom: Existing SNMP collectors cannot be modified after IronView Network Manager is upgraded to Release 03.1.00.


94929

Topology Manager, Network Object Manager

2 Symptom: IronView Network Manager is unable to add the FastIron SuperX 1600 to Network Object Manager when multiple port LACP trunks are configured and are operational on the device.


97062

Topology Manager, Network Object Manager

2 Symptom: IronView Network Manager does not add the FastIron GS to Network Object Manager.


98704

Traffic Analyzer, Monitoring

2 Summary: sFlow Monitoring is not functional if the IronView Network Manager server is set to a non-English locale.


95098

Known Limitations and Issues This section presents the current known limitations and issues in the application and the release versions in which they were found. The P column indicates the priority of the known issue, as follows:

• 0 = Critical

• 1 = Major

• 2 = Medium


• 3 = Minor

• 4 = Enhancement

The tables below are sorted first by category (alphabetically), then by priority.

Release 03.2.00


Administration, Licensing

2 Symptom: On version 8 of the Internet Explorer browser, IronView Network Manager displays the incorrect path for the license that is being imported. The license is imported successfully, however.

101420


2 Symptom: When using SCP to restore a startup configuration to the FastIron CX, the device responds with the following message. FCX624S Router#Downloading scp copied startup to members... Write startup-config done.

The device does not return a # or a > prompt so IronView Network Manager thinks the deployment failed even though the configuration was restored by IronView Network Manager.

Workaround: Ignore the message.

105426

Configuration Manager, Configuration Wizard, ACL port binding

2 Symptom: Binding ACLs to ports on a ServerIron ADX 1000 shows the ports as slot-number/port-number, instead of just the port number. The binding, however, is successful.

106023

Configuration Manager, Configuration Wizard, VLAN Manager

2 Symptom: After discovering a ServerIron ADX 1000 device that has port VLANs configured, if user creates a new VLAN, the deployment fails.

104718


2 Symptom: IronView Network Manager may display multiple trap messages for SNMP monitor expressions

106193

Event Manager, Event Processor

2 Symptom: When creating a new Event Processor for a ServerIron ADX, no event action is generated if “Used IfIndex in source matching” box is checked.

106020



Event Manager, Event Processor

2 Symptom: Event Action CLI CFG MGR deployment bound to a payload with an include statement fails and displays a java.lang.Exception.

106128

General 2 Symptom: IronView Network Manager 03.2.00 will only support 3DES for SSH. Therefore, IronView Network Manager will not be able to communicate with a device via SSH if that device is configured with the ip ssh encryption aes-only command.

105876


2 Symptom: If the IronView Network Manager server is running on a Windows XP platform, “Headlessgraphics” exception errors may be displayed on the java.exe console window if the PC goes into screen saver mode or if a remote desktop connection to the IronView Network Manager server is established.

For example, you may see the following exception errors: Exception in thread "AWT-EventQueue-0" java.lang.ClassCastException: sun.java2d.HeadlessGraphicsEnvironment

at sun.awt.windows.WToolkit$4.run(Unknown Source) at java.awt.event.InvocationEvent.dispatch(Unknown Source)

The errors do not affect IronView Network Manager’s functionality.

40527


2 Symptom: The browser may run out of memory or will fail to load a page without showing an exception. Also, on the Java Console, a java OutOfMemory exception is displayed.

Workaround: Do one of the following:

• First, increase the Java client runtime applet memory. Refer to the “Dealing with OutOfMemoryError Messages” section in the “Viewing sFlow Traffic Reports” chapter of the IronView Network Manager User Guide.

• If the issue still persists, disable the "Enable the next-generation Java Plug-in" setting in the Java Control Panel > Advanced > Java Plug-in.

105385



Logout 2 Symptom: Logout dialog fails to display and client exception is thrown if you select the menu options in the following sequence: Performance Monitor SNMP Monitoring > About > Logout

Workaround: Do one of the following:

• Select another menu option, except Reports, then click Logout.

• Turn off the “Enable the Next-generation Java Plug-in (Requires browser restart)” option in the JRE Control Panel.

106021

Other, Installation

2 Symptom: IronView Network Manager will not start up the service if IronView Network Manager a hyphen is entered as part of the installation.

Workaround: Use the Windows Start menu to start up and stop the IronView Network Manager server or use the startup.bat and shutdown.bat scripts from the command line.

106348

Other, SNMP v3

2 Symptom: If SNMP v3 is used to manage FESX , FastIron Super X, and FastIron CX devices, the device status may show orange (Warning) occasionally, even though the devices are online and are accessible. This false status change is usually temporary, and it will usually become normal during the next device polling cycle (default is 3 minutes). This is primarily an agent issue on the device.

Workaround: Use SNMP v2 to manage the device.

104715


2 Symptom: When creating a port level SNMP Monitor for a ServerIron ADX1000 device, the IfIndex values are not correctly populated on the index page when an If MIB is chosen.

Workaround: Launch MIB Walk dialog and manually pick the IfIndex instances

106008


2 Symptom: A device deleted from a collector can promote a remnant collectible object in the Monitor > From Collectible tree view.

106196



ServerIron Manager, SSL Certificate Manager

2 Symptom: When a certificate and key are imported from a SeverIron, the certificate and key are paired in IronView Network Manager and associated to the SeverIron. However, if a user deletes the certificate, but did not delete the related key in ServerIron, then imported the certificate and key again from ServerIron, the certificate and key pair would be disassociated from the ServerIron.

Workaround: Delete both the certificate and the related key in ServerIron.

106189

Topology Manager, VLAN Topology View

2 Symptom: When viewing the VLAN Topology Views for STP/RSTP Root Bridge identification, the selection of a subsequent VLAN ID may present an incorrect ROOT Bridge ID for the displayed topology.

Workaround: In VLAN Topology Views, when moving immediately from one VLAN Folder to the next, be sure to select the STP button twice (turn off, turn on) to promote the proper ROOT Bridge ID for the view.

106488

Release 03.1.00


Administration > Restart INM Server

2 Symptom: The std_out.log file is not updated when IronView Network Manager is restarted from Administration > Restart INM Server.

Workaround: Stop IronView Network Manager, then restart it.

95054

Administration, Licensing

2 Symptom: IronView Network Manager Licensing fails If IPv6 protocol is installed on Windows platforms and IPv6 addresses are disabled on all of the NIC interfaces.

Workaround: Ensure that at least one NIC card interface has an IPv6 address.

92736


1 Symptom: A Device Monitoring configuration containing the show tech command may be created in CLI Configuration Manager; however, the complete show tech output is not displayed if the Device Monitoring configuration is deployed to a FastIron stack using “SSH only”.

92721



4 Symptom: RADIUS server payloads (all actions) cannot be deployed to EdgeIron 48GS and EdgeIron 8x10G devices. Also, payloads that delete RADIUS servers cannot be deployed to all EdgeIron devices.

84785

Installation, Windows 2008

1 Symptom: The following error messages may be displayed on Windows Server 2008 during installation:

InstallAnywhere, Please select another location to extract the installer to

Workaround: Do the following:

1. Log into Windows 2008 Server Console (not remote desktop) using the "Administrator" user name.

2. Obtain the IronView Network Manager CD ROM and launch the installer (inm_installer_win03.1.00.exe file) from the CD ROM.

94218

Starting and Stopping IronView Network Manager: Windows only

3 Symptom: On Windows XP platforms configured as a service to automatically start IronView Network Manager, restarting the IronView Network Manager server from the Service window prevented clients from connecting to IronView Network Manager.

Workaround: Do not select Restart on the Service window. Instead, choose Stop then Start to restart IronView Network Manager.

94357

Wireless, AP Relief

4 Symptom: When an IronPoint 250 is configured in IP 200-compatible mode, the feature that converts a sensor back to AP mode is not supported. However, an IronPoint 250 in sensor mode can be converted to AP mode and vice versa.

Workaround: If the IronPoint 250 must be converted from sensor mode to AP mode and vice versa, disable the IP 200-compatible mode on the IronPoint 250.

93641


Service Pack 03.0.00a



1 Symptom: Deployment of changes containing port VLAN transitions to a device may seem to be successful. However, after the deployment, the port does not appear under the show vlan port list on the device CLI nor does it appear in the Available Ports List of the Port VLAN Configuration dialog. This situation could occur if the following port VLAN assignment transitions are attempted:

• Changing the port VLAN from dual mode to Default VLAN then back to dual mode

• Changing the port VLAN from dual mode to Default VLAN then to non-dual mode

Workaround: The following is an example of a workaround:

Initial state: Port X is Tagged in VLAN A and untagged in default VLAN.

Desired state: Port X in default VLAN

Do the following

1. In the Port VLAN Configuration Dialog under the "Selected Ports" box, remove the untagged port from Default VLAN. This makes the port as tagged to VLAN A.

2. Deploy this configuration. 3. In the Port VLAN Configuration Dialog under the "Selected

Ports" box, remove the port from VLAN A and assign it to the Default VLAN as untagged.

4. Deploy the configuration.

78940




2 Symptom: In some cases, changing port VLAN assignments in the Port VLAN Configuration dialog may produce an SNMP error during deployment. The port VLAN assignment transitions that may produce the SNMP error are:

• Changing the port VLAN from dual mode to non-dual mode

• Changing the port VLAN from dual mode to dual mode

• Changing the port VLAN from non-dual mode to dual mode

Workaround: If you need to change port VLAN assignments, perform the changes in more than one deployment. For example:

1. Remove the port from the current VLAN assignment. 2. Deploy the configuration. 3. Add the port to the desired VLAN. 4. Deploy the configuration.

78939


Release 03.0.00


Dashboard 1 Symptom: Event Summary sometimes becomes non-functional when devices are deleted from Network Object Manager then the same devices are added back in.

Workaround: Stop, then restart IronView Network Manager.

74629

Configuration Manager, ADC Manager

1 Symptom: Java errors are displayed when you refresh the Web browser while ADC is displayed.

75103


4 Symptom: If your network is not using VLAN tagging and your IronPoint–FES port on which ADC is enabled has an untagged default VLAN that has a VLAN ID other than VLAN 1, that VLAN will be changed to VLAN 1 when realms are deployed from ADC Manager. This change occurs because the default VLAN for the realms is VLAN 1. Furthermore, the deployed VLAN 1 will be tagged and will be in dual-mode. However, since VLAN 1 is in dual-mode, it will allow untagged traffic on the IronPoint-FES default VLAN.

Workaround: None, but this issue should not affect access point connectivity.

75784


4 Symptom: When you deploy ADC configurations, IronView Network Manager changes the VLAN ID on the IronPoint–FES to VLAN 1, if VLAN 1 is not the default VLAN on the IronPoint–FES.

75784

HP OpenView Integration

2 Symptom: On Windows platforms, HP OpenView Network Node Manager (NNM) does not display the correct source agent address in the alarm browser because of WinSNMP library and functionality.

Workaround: Turn off WinSNMP by starting ovtrapd with the "-W" option and stop the WinSNMP SNMP trap service from the Control Panel service. This will allow NNM ovtrapd to use the agent-address as source when it receives SNMP V1 traps.

72839



Report, IP Subnet Report

2 Symptom: The IP Subnet Report lists subnet entry as Device IP/255.255.255.255 or Device IP/128. When you click on the device, no device is identified. Also, if you delete the device from IronView Network Manager Configuration Manager > Network Object manager, the entry in the IP Subnet Report is not deleted.

This situation occurs when the IPv4 and IPv6 address MIB tables is empty.

73131

Topology Manager, topology views

1 Symptom: Direct connections from a FastIron GS to a FastIron SuperX show a Layer 2 Cloud instead of straight lines. The Layer 2 Cloud means that devices are not directly connected to each other and each device does not have Layer 2 information from other devices.

75566

Date post:	10-Apr-2015
Category:	Documents
Upload:	jliehr
View:	172 times
Download:	4 times

INM 03[1].2.00 Releasenotes

Documents