Cisco Crosswork Hierarchical Controller 8.0.2 Release Notes

This document provides information about:

●       Patch installation procedure with detailed steps to upgrade from 8.0.1 to 8.0.2

●       Issues resolved and known limitations in this release

●       Application updates

Upgrade

Crosswork Hierarchical Controller 8.0.1 can be upgraded to version 8.0.2

Patch Installation Procedure

Upgrading Crosswork Hierarchical Controller from version 8.0.1 to version 8.0.2, requires you to copy and upload the system pack to one of the nodes, pull it to the other instances, and then apply the upgrade on all nodes. 

Note: Also download the adapter service packs. These will be required after the upgrade, and before you re-enable the adapters.  The installation command MUST use the adapter names that are in use prior to upgrading, so record the names that appear in Device Manager. 

Before you begin:

1.     Download the HCO v8.0.2 system pack from cisco.com.

2.     Check if the system status i  s Running.

sedo system status

To upgrade Crosswork Hierarchical Controller 8.0.1 to 8.0.2:

1.     Make a full backup of the system:

sedo backup create full

2.     Download the backup.

sedo backup download -P <Add password> <add backup name>

The backup file is available in the /nxf folder. Copy the backup file to an easily accessible and secure location on your system.

3.     Disable all the adapters. For each adapter:

a.     In the applications bar in Crosswork Hierarchical Controller, select Device Manager > Adapters.

b.    Select the required adapter in the Adapters list on the left.

c.     Select the General tab.

d.    Deselect the Enabled checkbox.

e.    Click Save.

4.     Disable all the adapters on the pods.

sudo kubectl --kubeconfig /etc/kubernetes/admin.conf -n zone-b scale statefulset {adapter}  --replicas=0

5.     Copy the system pack provided to one of the instances (e.g. node1).

6.     Upload the system pack (from the node it was copied to, e.g. node1):

sudo sedo system upgrade upload <system-pack-name>

7.     List the available upgrades: 

sudo sedo system upgrade list

8.     Pull the system pack on all other instances (there is no need to pull it to the instance on which it was uploaded): 

sudo sedo system upgrade pull <system-pack-name>

9.     Apply the upgrade (on all nodes): 

sudo sedo --kubeconfig /etc/kubernetes/admin.conf system upgrade apply

10.  Confirm that the upgrade was successfully applied to all nodes. If any node did not receive the upgrade, reapply it to that node.

Note: The system will not reboot if the upgrade fails to apply on a node.

11.  Check the system status and ensure that the HCO pods are not running.

sedo system status

12.  Reboot to complete (all nodes): 

sudo reboot  

Post-Upgrade Tasks

1.     Check:

sedo version

sedo system status

Verify that the version is 8.0.2 and the system status is Running.

2.     Check the logs in the folder: nxf-system/controller to be sure there are no issues encountered during the upgrade.

3.     Run the sedo logs brain command to verify that there are no unusual exceptions. If any are found, contact Cisco Customer Support.

4.     Download the adapter service packs. 

5.     Install the adapter service packs. The installation command MUST use the name that was in use prior to upgrading (if this is not the default adapter name, that is, if the DYNAMIC_APP_GUID param was used in the original installation to modify the name, install the new service pack with DYNAMIC_APP_GUID=[adapter name as it was displayed in Device Manager on v8.0.1].

6.     Wait until the adapter pods are re-created using the newly installed service pack, and then validate that the adapter pods are restarted:

sedo system status command

7.     Reconfigure and enable the adapters in Device Manager.

Issues Resolved

Crosswork Network Controller

●       CSCwn09919. The Crosswork Network Controller adapter fails to process L3VPN service creation when using Link Aggregation Groups (LAG).

●       CSCwj12674. The sedo hco rest Xable command does not function correctly in the Crosswork Network Controller adapter with IGP discovery enabled.

●       CSCwo11521. When modeling the Crosswork Network Controller adapter with OSPF links, the TopologyBuilder crashes because it does not expect these link types.

●       CSCwo05280. The Crosswork Network Controller adapter fails to create R_LOG ports using the create_logical_port command when the tp.ip-address-prefix parameter has a single value.

Network Inventory

●       CSCwj09953. Using the group_by query in device tagging blocks the processing of additional tags.

●       CSCwj70179. The Network Inventory table displays the Physical Address and Speed \[Gbps\] columns for Multichannel (MC) ports.

●       CSCwk11778. The Export Table operation in the inventory window of the Network Inventory application frequently fails.

Failure Impact

●       CSCwn01073. The Failure Impact application does not handle ETH_UNKNOWN value for the EthPortype parameter for the port.

Known Limitations

This section outlines the known limitations of the 8.0.2 release.

For the complete list of limitations and operational considerations in the 8.0 and 8.0.1 releases, see Crosswork Hierarchical Controller Release notes.

Crosswork Network Controller

●       CSCwo43493. Crosswork Network Controller fails to update device reachability status to Crosswork Hierarchical Controller.

To address this issue, follow these steps in the Crosswork Network Controller UI:

Step 1: Select the device and navigate to its Edit screen.

Step 2: Change the Admin state to DOWN and save the changes. Allow some time for the update to process.

Step 3: Again, select the device and go to its edit screen.

Step 4: Change the Admin state back to UP and save the changes. Wait for a while to ensure the update is applied.

Service Deletion with Embedded NSO

●       CSCwo49068. When an L3 service is created using Embedded NSO and Crosswork Network Controller and then deleted through Embedded NSO, it still appears in the SHQL, 3D Explorer, and Network Inventory applications in Crosswork Hierarchical Controller.

CLI

●       CSCwn60610. The commands sedo hco version and sedo nso version output wrong version information.

Upgrade

●       CSCwo26595. After upgrading from previous versions (v8.0.0 to v8.0.1 and then to v8.0.1 to v8.0.2), the list of all installed images is missing.

●       CSCwo26737. After upgrading from v8.0.1 to v8.0.2, the Dashboard application encounters a 502 Bad Gateway error.

Application Updates

Deprecated Features

●       The SR Provisioning Wizard in the Service Manager application is deprecated in this release and will be entirely removed from HCO v12 (2H CY 2015).

Release Collaterals

All the Cisco Crosswork Hierarchical Controller 8.0 documents are relevant and can be used.

This includes: