Cisco Cisco Prime Network Services Controller 3.0
© 2013, 2014 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public.
Page 12 of 169
Step 2 update
Example:
nsc (local-mgmt)# update bootflash:/PNSC.3.0.bin
Updates the system.
EXAMPLES
This example shows how to update the system:
nsc# connect local-mgmt
Cisco Prime Network Services Controller
TAC support: http://www.cisco.com/tac
Copyright (c) 2002-2013, Cisco Systems, Inc. All rights reserved.
The copyrights to certain works contained in this software are
owned by other third parties and used and distributed under
license. Certain components of this software are licensed under
the GNU General Public License (GPL) version 2.0 or the GNU
Lesser General Public License (LGPL) Version 2.1. A copy of each
such license is available at
http://www.opensource.org/licenses/gpl-2.0.php and
http://www.opensource.org/licenses/lgpl-2.1.php
nsc(local-mgmt)# update bootflash:/PNSC.3.0.bin
Setting the Host Name
You can set the host name.
BEFORE YOU BEGIN
See
Services Controller CLI.
Caution: Changing the host name will cause new certificate generation designed to warn the user of the impact of
the change. The VM Manager Extension file would have to be exported again and installed on vCenter. Any web
browser client that had the certificate installed will get a prompt for a new certificate.
Changing the certificate will also cause InterCloud Switch and Virtual Supervisor Module (VSM) instances to lose
visibility and Prime Network Services Controller will be unable to manage the devices. To reconnect a VSM, use
the VSM CLI to uninstall and then reinstall the VSM-CPA. To reconnect an InterCloud Switch, reboot the
InterCloud Switch from the Prime Network Services Controller GUI.
CLI
Management controller
SUMMARY STEPS
1. scope system
2. set hostname