Conventions	Conventions used in this document.
Installation Notes	Description of the IND application.
New Features	New features in the Release 1.0.x.
IND Licenses	Summary of supported licenses for Release 1.0.x.
System Requirements	System requirements for Release 1.0.x.
Installation Notes	Procedures for downloading software.
Important Notes	Notes about Release 1.0.x.
Limitations and Restrictions	Known limitations in IND.
Caveats	Open and Resolved caveats in Release 1.0.x.
Related Documentation	Links to the documentation associated with this release.

Conventions	Indication
bold font	Commands and keywords and user-entered text appear in bold font.
italic font	Document titles, new or emphasized terms, and arguments for which you supply values are in italic font.
[ ]	Elements in square brackets are optional.
{x | y | z }	Required alternative keywords are grouped in braces and separated by vertical bars.
[ x | y | z ]	Optional alternative keywords are grouped in brackets and separated by vertical bars.
string	A nonquoted set of characters. Do not use quotation marks around the string or the string will include the quotation marks.
courier font	Terminal sessions and information the system displays appear in courier font.
< >	Nonprinting characters such as passwords are in angle brackets.
[ ]	Default responses to system prompts are in square brackets.
!, #	An exclamation point (!) or a pound sign (#) at the beginning of a line of code indicates a comment line.

Table 1 New Features in IND 1.0.x

Feature	Description	First released	Related Documentation
IND Device Pack 1.0.1-x	Two new devices are now supported by the IND application with the new device pack: ■IE-4010-4S24P ■IE-4010-16S12P The device pack supports the following Cisco IOS Releases: ■Cisco IOS Release 15.2(5)E ■Cisco IOS Release 15.2(4)EA2 ■Cisco IOS Release 15.2(4)EA1 ■Cisco IOS Release 15.2(3)E3 ■Cisco IOS Release 15.2(3)E2 The device pack supports the following Cisco platforms: ■CGS 2520 ■IE 2000, IE 2000U ■IE 3000, IE 3010 ■IE 4000, IE 4010 ■IE 5000	1.0.1-x
Operate	You can review or perform the following actions at the Operate page: ■Manage Alarms: Open or close an alarm, view alarm details, assign an alarm to someone, add notes to the alarm (Operate > Alarms) ■Asset Discovery: Search assets by IP Scan or Link Layer. Assets include Industrial Ethernet (IE) switches and clients that connect to IE switches (Operate > Asset Discovery) ■Audit Trails: See a listing of all operations performed by users. Each entry includes the following information: timestamps, operation, device IP address, status, username, user IP address and details (description of the entry). (Operate > Audit Trail). ■Inventory: View all devices found from a scan of the network by the application. This page is the default opening page of the IND application. (Operate > Inventory) ■Tasks: Review information on tasks that are actively running or have completed.(Operate > Tasks) ■Topology: View a full network topology map of all devices and neighbors discovered by a scan of the network. (Operate > Topology)	1.0.0	IND Online Help
Settings	You can view information or perform the following actions at the Settings page: ■Active Sessions: View information on all active sessions, which includes: user ID, login, last accessed, IP address. (Settings > Active Sessions) ■Alarm Settings: View categories of alarms available on the system and the number of alarms in each category as well as disable/enable alarms and change alarm severity. (Settings > Alarm Settings) ■Backup: Schedule backups or initiate on-demand backups. (Settings > Backup) ■Device Pack: Allows you to add support for new device types to the system. (Settings > Device Pack) ■Group Management: Create groups and assign devices to those groups. (Settings > Group Management) ■Licenses: Manage Smart and Classic IND Licenses and their details and status. (Settings > Licenses) ■Network Profiles: Create and manage access credentials used by devices and discovery profiles. (Settings > Network Profiles) ■Password Policies: Eight password policies are defined by default on the system. You can enable or disable any of the policies or the values of those policies. (Settings > Password Policies) ■System Settings: Modify system settings for data retention, data collection, Cisco Active Advisor and log levels. (Settings > System Settings) ■User Accounts: Add new user accounts including assigning user role (Network Administrator, Operator, System Administrator) and view existing users defined for the system. ■User Roles: Three roles are predefined on the system: –Network Administrator: User with this role has permissions to manage network resources. –Operator: User with this role has permissions to monitor the network. –System Administrator: User with this role has all available permissions on the system.	1.0.0	IND Online Help

Table 2 System Requirements

Desktop Requirements	Minimum Requirement
Windows Operating System (OS)	Windows 7 or Windows 10
Browser	Chrome: Version 50.0.2661.102 or later Firefox: Version 46.01 or later
CPU	Dual Core 2.4Ghz
RAM	8 GB
Storage	50 GB

IND Application Installation

The installation procedure for IND is described in the Installation Guide for Industrial Network Director for Release 1.0.x.

Device Pack Installation

Installation Requirements

IND Device Packs can only be installed with the IND application that has a matching version number, and the release number must be the same or greater than the IND release number.

For example, in release 1.0.1-3, 1.0.1 is the version number and 3 is the release number.

A new Device Pack must be version 1.0.1 and the release must be 3 or higher.

Installation Steps

For Device Pack installation steps, refer to the Installation Guide for Cisco Industrial Network Director, Release 1.0.x.

Unsupported PIDs

The following IE 2000 PIDs are not supported by IND 1.0.x and are not supported by IND Device Packs in 1.0.1-x:

■IE-2000-4TS-G-B-U

■IE-2000-8TC-G-B-U

■IE-2000-16TC-G-E-U

Supported but Untested PIDs

The following IE-2000 IP67 PIDs are supported by IND 1.0.1-x. Device Packs but were not tested and the following IE-2000 IP67 PIDs are supported by IND 1.0.x. but were not tested:

■IE-2000-8T67-B

■IE-2000-8T67P-G-E

■IE-2000-16T67-B

■IE-2000-16T67P-G-E

■IE-2000-24T67-B

Supported Cisco IOS Software

IND 1.0.x supports the following Cisco IOS Releases:

■Cisco IOS Release 15.2(5)E

■Cisco IOS Release 15.2(4)EA2

■Cisco IOS Release 15.2(4)EA1

■Cisco IOS Release 15.2(3)E3

■Cisco IOS Release 15.2(3)E2

Open Caveats

■CSCva80749

Symptom: Trigger Seed Discovery on a switch which has a CIP chassis path with multiple CIP IP addresses and connects to two different two IE switches. A duplicate entry appears in inventory.

Conditions: Dual-Homed Client Device C is connected to Switch A via Single Link (Link1) and Switch B via two links (Link2, Link3). Use RSLinx tool to see this problem clearly.

Workaround: Do the following:

a. Delete the Duplicate Client Devices.

b. Decommission the two switches that are connected to the Dual-homed Client device.

c. Move Switch A to Managed State and wait till the Client Device is discovered.

d. Move Switch B to Managed State.

■CSCva97099

Symptom: When you install IND on Windows 10, you might not be able to see the uninstall option. This is because the plug-in used by IND does not claim support for Windows 10 yet.

Conditions: This issue might occur when you install IND in Windows 10.

Workaround: When you want to uninstall IND, go directly to Control Panel > Uninstall a Program and then manually uninstall IND and delete all related files in Program Files and in Program Data.

■CSCvb24719

Symptom: Tasks are an asynchronous way to execute certain operations in IND. When we take a backup of the database, that backup action itself is a task and is in a RUNNING state. So, when we restore the database and startup all the tasks which were in a RUNNING state, they will be moved to FAILED.

Conditions: During the time when we do a backup, there can be some other operations simultaneously running as a task other than the backup task itself.

Workaround: There is no workaround for this issue. But this does not impact any feature or functionality. It is expected that when we backup we are reverting to an older revision of the application and hence some tasks might have failed as you cannot re-create that operation at the current time.

■CSCvb24728

Symptom: When users access the URL with the parameters: “ % ” no proper valid error message appears to the user.

Conditions: The problem occurs only when the URL has the “ % ” special character.

Workaround: In the URL, the user should not use the “ % ” special character.

■CSCvb31292

Symptom: When there are client devices which support CIP protocol, they do no have LLDP or CDP support and thus we cannot see its connected devices from the topological view in the API.

Conditions: When there are CIP devices in the network connected to IE switches, then connected devices for that client would be empty though there is a valid physical connection.

Workaround: Client API has extended attributes which shows the connected devices in the UI.

■CSCvb31945

Symptom: The health metrics and bandwidth utilization charts are not available on IE-5000-12S12P-10G for Cisco IOS Release15.2(5)E.

Conditions: System IE 5000, PID IE-5000-12S12P-10G, had Cisco IOS Release15.2(5)E release installed.

Workaround:.Other IE 5000 family PID works without an issue. Additionally, IE-5000-12S12P-10G PID works with Cisco IOS Releases 15.2(4)E and 15.2(3)E.

■CSCvb38948

Symptom: In the Asset Discovery page, an Export of Discovery Profile entries to a CSV file results in a missing value. The discovery profile Type column is not populated in the CSV.

In the VLANs section of the Forwarding tab of the Network Device Details page, an Export of VLANs entries to a CSV file results in an incorrect column formatting in the CSV file. Multiple values in the single “Switch Port Names” column are exported to multiple columns in the CSV file

Conditions: A Discovery Profile is of two types: IP Scan or Link Layer. This is populated in the Type column in the Asset Discovery page. An export of Discovery profile entries to CSV results in a missing value in the Type column of the CSV file.

When a network device is moved to the Managed state, clicking on the device name in the Inventory page gives the Network Device Details page. The Forwarding tab has a VLANs column. If the “Switch Port Names” column has multiple values, then an export of VLANs to CSV gives an incorrect column formatting in the CSV file. The multiple values are formatted into multiple columns.

Workaround: Since the exported Discovery Profiles CSV file is available for the user to edit, a manual addition of the discovery profile Type values can solve the problem.

Since the exported VLANs CSV file is available for the user to edit, a manipulation of the Switch Port Names values can solve the problem.

■CSCvb40505

Symptom: On the Port Detail page, sometimes the Connected Devices field is empty even though the device is displayed on the Connected Devices grid in the Device Detail page.

Conditions: When a port on the device has a neighbor and the topology discovery has been run, sometimes the field is empty when IND does not have enough information to display properly.

Workaround: Information is displayed on the Connected Devices grid regarding the neighbors of each device and the port on which each neighbor is connected to.

■CSCvb41224

Symptom: When multiple ports are in Admin State down and half-duplex mode, and a device is either moved to managed or an On demand refresh is triggered or during metrics poller run, there is only one event generated against one of the ports.

Conditions: When multiple ports are in Admin State down and half-duplex mode, and a device is either moved to managed or an On demand refresh is triggered or during metrics poller run, there is only one event generated against one of the ports instead of an alarm each for every port.

Workaround: There is not workaround.

■CSCvb41219

Symptom: The following links are broken under certain conditions:

1. On the Device detail page, Connected Devices grid - links in Source Port and Port columns

2. On Client Detail - link in Connected To field

3. On topology, when a link between two connected devices is clicked - Port name link

Conditions: Perform the following operations:

1. Discover a device that has clients and network neighbors

2. Discover topology

3. Move the device to Decommissioned

Workaround: Move the device to Managed and back to Decommissioned.

■CSCvb41139

Symptom: When editing a network profile in Advanced mode, if the user changes the Access Mechanism from Regular to Secure, the HTTPS port does not auto populate to 443.

Conditions: Create a network profile in regular mode. Edit the network profile. Change the mode to secure mode.

Workaround: Manually edit the HTTPS port field to 443.

■CSCvb43029

Symptom: The affected devices in the alarm detail page shows client device links for devices that have been moved into the Other category. These links lead to an empty or misleading client detail page.

Conditions: There are two conditions:

1) The affected devices in the alarm detail page shows client device links for devices that have been moved into the Other category, or for client devices that have been deleted. These links lead to an empty or misleading client detail page.

2) An alarm is generated where a client device becomes an affected device. Then, the client device is deleted.

Workaround: For the first case, run topology immediately after moving a device from Client to Other. For the second case, navigate to Other to view the device.