Guest

Preview Tool

Cisco Bug: CSCuq73410 - Python PSS: Sequence number zero in L3 ACE gets configured as 10

Last Modified

Feb 16, 2018

Products (1)

  • Cisco MDS 9000 NX-OS and SAN-OS Software

Known Affected Releases

7.1(0)N1(0.317)

Description (partial)

Symptom:
When configuring L3 ACLs on an N6K via a Python onep app, if I create an ACE with sequence number 0 (zero) then it actually gets configured as "10".

In the scenario that ACE1 has seqnum 1 and ACE2 has seqnum 2, if ACE1's seqnum is "accidentally" specified as 0, then its seqnum actually ends up being 10 which is higher than 2. Thereby altering the order in which the ACE's will be accessed when that ACL is applied to an interface.

Zero is not a valid value for sequence numbers even via the CLI...

-- snip -- 
onep-n6k-1(config-acl)# 0 ?
                        ^
% Invalid number, range is (1:4294967295) at '^' marker.
onep-n6k-1(config-acl)# 0 
-- snip --

Conditions:
Observed with:
onePK Python SDK version:  onePK-sdk-python-rel-1.3.0.197
N6K Image:  n6000-uk9.7.1.0.N1.0.317.bin
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)
  • 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.