Cisco Cisco Prime Network Services Controller 3.0
© 2013, 2014 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public.
Page 74 of 169
EXAMPLES
This example shows how to assign a critical severity level to all logging files in the resource manager CLI:
nsc# connect resource-mgr
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(resource-mgr)# scope monitoring
nsc (resource-mgr) /monitoring # scope sysdebug
nsc (resource-mgr) /monitoring/sysdebug # scope mgmt-logging
nsc (resource-mgr) /monitoring/sysdebug/mgmt-logging # set all crit
nsc (resource-mgr) /monitoring/sysdebug/mgmt-logging #
Resetting the Management Log Levels
You can reset the management log levels.
BEFORE YOU BEGIN
Services Controller CLI.
CLI
Management controller
Policy manager
Resource manager
Service registry
Virtual machine manager
SUMMARY STEPS
1. (Optional) connect {policy-mgr | resource-mgr | service-reg | vm-mgr}
Note Step 1 is optional. You can also perform the reset command in the management controller CLI.
Each CLI allows you to control a different set of logs.
Each CLI allows you to control a different set of logs.
2. scope monitoring
3. scope sysdebug
4. scope mgmt-logging
5. reset