Cisco Cisco Prime Network Services Controller 3.0
© 2013, 2014 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public.
Page 132 of 169
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(policy-mgr)# scope org
nsc(policy-mgr) /org # scope policy
nsc(policy-mgr) /org/policy # scope faultpolicy EaFaultPA12
nsc(policy-mgr) /org/policy/faultpolicy # set flapinterval 3500
nsc(policy-mgr) /org/policy/faultpolicy* # commit-buffer
nsc(policy-mgr) /org/policy/faultpolicy #
Setting the Retention Interval
You can set the retention interval in a fault policy.
BEFORE YOU BEGIN
Services Controller CLI.
CLI
Policy Manager
SUMMARY STEPS
1. connect policy-mgr
2. scope org
3. scope policy
4. scope faultpolicy <policy-name>
5. set retentioninterval {<number of days> <number of hours> <number of minutes> <number ofseconds>
| forever}
where the arguments should be provided within the range given below:
Days
—0 to 24854
Hours
—0 to 23
Minutes
—0 to 59
Seconds
—0 to 59
Note The valid range for retention interval in the Prime Network Services Controller CLI is from 0 to
24854. After you set a value in the CLI, the Prime Network Services Controller GUI displays the same
value. If you try to edit the value from the Prime Network Services Controller GUI, the range has to be
from 0 to 99.
24854. After you set a value in the CLI, the Prime Network Services Controller GUI displays the same
value. If you try to edit the value from the Prime Network Services Controller GUI, the range has to be
from 0 to 99.
6. commit-buffer