Preview Tool

Cisco Bug: CSCuq46058 - in explorer, going from interfaces -> demands gives far too many demands

Last Modified

Oct 06, 2014

Products (1)

  • Cisco MATE Live

Known Affected Releases


Description (partial)

in explorer, going from interfaces -> demands gives far too many demands

The problem is in the regular expression and the way we represent demands.  Going from interface: (PALTBPRJ01.RD.PT	ae0), to all related demands, generates the query: "Path(~PALTBPRJ01.RD.PT|ae0);"  The problem with this query is that | is an OR operator and this query returns all paths which contain ae0, which is about 40% of all demands.  URL encoding the query to: PALTBPRJ01.RD.PT%7Cae0 yields no demands.  What is the correct query?  Perhaps: PALTBPRJ01.RD.PT.ae0 , which gives a close approximation?   Unfortunately, it will also include ae0.1 and the other physical interfaces associated with ae0.  This is an improvement and unless you can think of a more accurate query, it's probably an adequate fix.  Build: 6.0-249-ge287322, new cox data from
Bug details contain sensitive information and therefore require a account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.