Sometimes you're facing very unfortunate failure that caused by literally unreal coincidence.


Exactly this kind of bug was listed in a weekly letter from Cisco.

Title

Policy-map name 'policy-map PIN-G3/1/3.8' causes TB and subsequent RP Crash on Policy deletion/add.

Symptom

Configuring 'policy-map PIN-G3/1/3.8' causes Traceback error and failure to apply policy-map config. Subsequent addition/deletion of policy-map then causes RP crash. Issue is not seen if the policy-map name string is changed even slightly to that shown above.

Workaround

Do not use policy-map name 'PIN-G3/1/3.8'