Cisco Bug: CSCul57298 - Improve CLI output and selection capabilities
May 04, 2016
- Cisco Network Registrar
Known Affected Releases
Symptom: Several new features were added to nrcmd: <ol> <li>A new command was added to improve readability of output - "session set output-using=<i>command</i>", where <i>command</i> is a user specified command (such as more).When set, this causes nrcmd to write all output to a temporary file and then execute <i>command</i> specifying this file. To undo this, use "session set output-using=". <br> Notes: <ul> <li>The temporary file is created in /tmp (if it exists) or the path specified by the TMP or TEMP environment variable.</i> <li>A restriction is that at least on Windows, the 'more' tool has a line limit of 4096 characters; some of the formatting used by nrcmd can generate "lines" that are longer than this and may have odd results. </li> </ul> <li>Special filtering options were added to most list operations. The lease/lease6 list, listbrief, listcsv operations have supported <i>attribute</i>=<i>value</i> expressions for some time. This has been extended to most other list, listbrief, and listcsv commands. In addition, the following special filtering rules can be specified for certain attributes: <ul> <li>If the attribute type is a string value, the comparison is usually case blind. By specifying the "|" character as the first character of value, the comparison will be case exact.</li> <li>If the attribute type is an IPv6 prefix, the comparison is for containment (i.e., is the attribute value contained within the specified IPv6 prefix). By specifying the "|" character as the first character of value, the comparison can be made contained by (i.e., does the attribute value contain the IPv6 prefix).</li> <li>If the attribute type is an IPv6 address, the comparison is equality. By specifying the "|" character as the first character of value, the comparison can be made contained by (i.e., does the attribute value contain the IPv6 address).</li> <li>If the attribute type is a flag, the comparison uses a regex to determine if the requested bits are set. By specifying the "|" character as the first character of value, the comparison is for an exact match.</li> <li>For all attribute types, a regex can be specified by specifying the "~" character before the value. Note that some regex characters may be tricky to enter or require escaping. For example, if you want to specify the regex to match a period character, you may need to enter \\\. for the character to assure that it is properly escaped.</li> </ul> <li>For flag type attributes, you can now add flag(s) by specifying <i>attribute</i>=+<i>flag(s)</i> or remove flag(s) by specifying <i>attribute</i>=-<i>flag(s)</i> for a set operation. This avoids having to get the current value to determine what changes to make.</li> </ol> Conditions: None.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases