Cisco IND Release 1.1.x - Release Notes for Cisco Industrial Network Director
Available Languages
Table of Contents
Release Notes for Cisco Industrial Network Director, Release 1.1.x
Pre-Configuration Requirements for IE Switches
Requirements for ALL IE Switches Running Cisco IOS
Configuration Required for Discovery
Configuration Required for NEW to MANAGED State
Configuration Required for NEW to MANAGED State in Secure Mode
Device Manager Configuration Required for IE1000 Switches
Obtaining Documentation and Submitting a Service Request
Release Notes for Cisco Industrial Network Director, Release 1.1.x
This release note contains the latest information about using Release 1.1.x of the Cisco Industrial Network Director (IND) application that supports configuration and management of Industrial Ethernet switches.
The IND application provides three types of Online Help (OLH): Context-Sensitive Help, Embedded Help such as the Guided Tours, and Tooltips.
Conventions
This document uses the following conventions.
Note: Means reader take note. Notes contain helpful suggestions or references to material not covered in the manual.
About Cisco IND
Cisco Industrial Network Director provides operations teams an easily-integrated system delivering increased operator and technician productivity through streamlined network monitoring and rapid troubleshooting. IND is part of a comprehensive IoT solution from Cisco:
■
Easy-to-adopt network management system purpose-built for industrial applications that leverages the full capabilities of the Cisco Industrial Ethernet product family to make the network accessible to non-IT operations personnel.
■Creates a dynamic integrated topology of automation and networking assets using industrial protocol (CIP, PROFINET) discovery to provide a common framework for plant floor and plant IT personnel to monitor and troubleshoot the network and quickly recover from unplanned downtime.
■Rich APIs allow for easy integration of network information into existing industrial asset management systems and allow customers and system integrators to build dashboards customized to meet specific monitoring and accounting needs.
Cisco IND Features and Benefits
■Purpose-built user experience for non-IT operations personnel - Rapid adoption by operations teams for improved productivity.
■Targeted discovery of plant floor network assets customized for industrial environments – Ensures that automation devices connected to the network are not affected by discovery process.
■Automation endpoint discovery using CIP and PROFINET industrial protocols – Complete automation infrastructure inventory, not solely network inventory details.
■Optimized alarm management with real-time alerting of network events and reporting of effects to automation assets – Allows for operations and plant IT team to consume network events in context of the industrial process to simplify troubleshooting issues.
■Real-time monitoring of device metrics, traffic statistics, and network infrastructure status – Increased visibility of network health for the operations team and reduced unplanned downtime.
■Comprehensive RESTful APIs for integration with automation applications and control systems – Rapid adoption and integration with existing systems and customization by system integrators.
■Role-based access control with customizable permission mapping – Restrict system access to authorized users on a per feature basis.
■Detailed audit trails for operational visibility of network changes, additions, and modifications – Record user actions on network devices for change management.
■Search capability integrated with major functions - Easily locate functionality and mine for information.
■Cisco Active Advisor - Free cloud-based service that provides essential network life cycle information to make sure security and product updates are current.
■Guided tours - Step-by-step guidance to maximize productivity and ease adoption.
New Features
In this release of the product, there are two primary functions supported: Operations (Operate) and Settings.
Release 1.1.x supports all the IND features summarized in New Features in IND 1.1.x.
■ ■ |
|||
■ ■ |
|||
■ |
|||
IE 1000 is now supported by the IND application with the new device pack: Note: IND only supports PROFINET clients on IE 1000. Additional IE4010 system support added: Note: Above IE4010 PIDs support these Cisco Universal IOS images: ■ The device pack supports the following Cisco and Rockwell Automation/Allen-Bradley platforms: Rockwell Automation/Allen-Bradley platforms: ■ ■ ■ |
|||
Minimizes User configuration required to ready an IE switch for management by IND. |
See Pre-Configuration Requirements for IE Switches section in these release notes |
||
■ ■ ■ ■ |
|||
Provides a summary view of devices within a Group. |
|||
All devices must be assigned to a Group. By default, the IND application assigns a device to the default Root Group in the absence of another Group assignment. ■ ■ ■ |
|||
A Groups-Tree-View displays within the left pane for the following pages: |
|||
The following data items will be retrieved from PROFINET Clients using PROFINET IO: ■ |
|||
New Device Terminology and Definitions within the Application |
■ ■ ■ – – – – ■ |
||
You can review or perform the following actions on the Operate page: ■ ■ ■ ■ ■ ■ |
|||
You can view information or perform the following actions on the Settings page: ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ – – – |
IND Licenses
The Cisco Industrial Network Director is licensed on a per-device, term subscription basis and supports two licensing models. For details on the supported lND licenses, refer to the:
System Requirements
Pre-Configuration Requirements for IE Switches
The following information describes the CLI configuration required for IND to discover a Supported Device and transition the device from NEW to MANAGED state and NEW to MANAGED state in secure mode.
■For IE switches running Cisco IOS, refer to Requirements for ALL IE Switches Running Cisco IOS
■For IE1000 switches, refer to Device Manager Configuration Required for IE1000 Switches
Requirements for ALL IE Switches Running Cisco IOS
■Configuration Required for Discovery
■Configuration Required for NEW to MANAGED State
■Configuration Required for NEW to MANAGED State in Secure Mode
Note: After entering the Configuration Required for Discovery steps, you will enter only one of the NEW to MANAGED State configurations referenced above: NEW to MANAGED State or NEW to MANAGED State.
Configuration Required for Discovery
The following configuration must be configured on the Supported Device for the system to successfully discover it:
Note: After entering the Configuration Required for Discovery steps above, you will enter only one of the NEW to MANAGED State configurations referenced below:
Configuration Required for NEW to MANAGED State
The following configuration must be configured on the Supported Device for the system to successfully transition the Supported Device from NEW to MANAGED administrative state.
Configuration Required for NEW to MANAGED State in Secure Mode
The following configuration must be configured on the Supported Device for the system to successfully transition the Supported Device from NEW to MANAGED administrative state in Secure mode:
Device Manager Configuration Required for IE1000 Switches
1. Login to the IE1000 Device Manager.
2. Leave the username field blank and enter cisco as password.
4. Create Device Access User and use the same in Access Profile on IND.
5. Configure SNMP community string for Read Only (ro):
a. Choose Configure > SNMP. Click OK in the pop-up windows to confirm enabling SNMP.
b. Check the check box to enable SNMP Mode globally. Click Submit
6. Select Community Strings tab. Add a public Community String read only access. (By default, this is a Read Only (ro) string)
7. Choose Admin > Access Management.
a. Check the check box to enable either SSH or Telnet. (This option determines how the IE1000 communicates with IND)
Installation Notes
IND Application Installation
The installation procedure for IND is described in the Installation Guide for Industrial Network Director for Release 1.1.x.
Installation Requirements
IND Device Packs can only be installed with an 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.1.1-49. 1.1.1 is the version number and 49 is the release number.
A new Device Pack must be version 1.1.1 and the release must be 49 or higher.
Installation Steps
For Device Pack installation steps, refer to the Installation Guide for Cisco Industrial Network Director, Release 1.1.x.
Important Notes
Please note the following information about Cisco IOS software and PID support on IND.
Unsupported PIDs
The following IE 2000 PIDs are not supported by IND 1.1.x and are not supported by IND 1.1.0-x Device Packs:
Supported Cisco IOS Software
IND 1.1.x supports the following Cisco IOS Releases:
■Release 1.6 for Industrial Ethernet 1000
Supported IND Release Upgrades
You can perform the following IND 1.x upgrades (with some limitations as noted below):
■If you upgrade from IND 1.0.1-3 to 1.1.x, please see Open Caveats associated with the release upgrade (CSCvc78199, CSCvd24673).
■If you upgrade from any IND 1.0.x or 1.1.x release to 1.1.1-49:
–CIP devices need to be rediscovered to collect MAC address (This item is part of Discover enhancements.)
–Other/Unknown devices need to be rediscovered to identify these devices more accurately. (This item is part of Discover enhancements.)
Limitations and Restrictions
Cisco recommends that you review this section before you begin working with IoT IND. These are known limitations that will not be fixed, and there is not always a workaround for these issues. Some features might not work as documented, and some features might be affected by recent changes to the software.
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.
Caveats
This section presents open caveats in this release and information on using the Bug Search Tool to view details on those caveats.
■Accessing the Bug Search Tool
Open Caveats
Symptom: IE-5000-12S12P-10G - Metric data refresh fails for the Managed Device after IND upgrade to 1.1.0
Conditions: Upon upgrading the IND from 1.0.1 to 1.1.x. This happens only if the device CLI output gets changed and those devices are in managed state of IND. Issue seen with IE-5000-12S12P-10G Cisco IOS Release (15.2(5)E or higher) IOS image.
Workaround: Manually move the device to decommission state and move back to managed state or delete the device from the IND and discover it again.
Symptom: When the system is upgraded to 1.1 image, the saved topology will be lost. The view will be auto-layout. All the devices and groups will be auto arranged.
Conditions: IND System is upgraded from 1.0.1 to 1.1.x.
Workaround: The user has to re-arrange the topology and save the layout again.
Symptom: Some devices in the DB shows up as unknown devices on the connected grid of its connected neighbors. Hence, a link to the device is not available at the following places:
–Dashboard Port traffic utilization widget
Conditions: When the thread running neighbor queries finish faster than the thread updating local if table, the port on the local ifTable is not matched. Hence the topology service categorizes this device as unknown device instead of mapping the device ID 5a11.
Workaround: Re-triggering topology might solve this as it is a multi-threading/timing issue.
Symptom: When a scheduled weekly backup is deleted, it shows the scheduled day to be one day ahead of the actual schedule. Logs show the day to be incorrect as well.
Conditions: Occurs when a weekly scheduled backup is deleted.
Workaround: There is no workaround.
Resolved Caveats
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: This issue is resolved in Release 1.1.0.
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: This issue is resolved in Release 1.1.0.
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
3. Move the device to Decommissioned
Workaround: This issue is resolved in Release 1.1.0.
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: This issue is resolved in Release 1.1.0.
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: This issue is resolved in Release 1.1.0.
Symptom: Sometimes, some of the Japanese characters translated to “???” if installed in Windows with English locale.
Conditions: The Japanese version of IND should be installed in the Japanese locale of Windows.
Accessing the Bug Search Tool
You can use the Bug Search Tool to find information about caveats for this release, including a description of the problems and available workarounds. The Bug Search Tool lists both open and resolved caveats.
To access the Bug Search Tool, you need the following items:
■Cisco.com user ID and password
To access the Bug Search Tool, use the following URL: https://tools.cisco.com/bugsearch/search
To search using a specific bug ID, use the following URL: https://tools.cisco.com/bugsearch/bug/ <BUGID>
Related Documentation
Installation Guide for Industrial Network Director Application for Release 1.1.x at:
http://www.cisco.com/c/en/us/products/cloud-systems-management/industrial-network-director/index.html
Find documentation for the Cisco Industrial Ethernet Switches at: (select the link for the relevant switch to access user guide)
http://www.cisco.com/c/en/us/products/switches/industrial-ethernet-switches/index.html
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, using the Cisco Bug Search Tool (BST), submitting a service request, and gathering additional information, see What’s New in Cisco Product Documentation.
To receive new and revised Cisco technical content directly to your desktop, you can subscribe to the What’s New in Cisco Product Documentation RSS feed. The RSS feeds are a free service.
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.
The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.
NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.
All printed copies and duplicate soft copies are considered un-Controlled copies and the original on-line version should be referred to for latest version.
Cisco has more than 200 offices worldwide. Addresses, phone numbers, and fax numbers are listed on the Cisco website at www.cisco.com/go/offices.
FeedbackContact Cisco
- Open a Support Case
- (Requires a Cisco Service Contract)