Hi John
It is likely possible to parse out the special characters from the config using the Perl script. Unfortunately for us in Support we do not have that specific knowledge. I would recommend to continue reaching out to the Communities for any assistance - perhaps rephrasing the question like
"How to parse out asterisk "*" character from NCM config capture over SSH w/ Perl script, to avoid error '
SPC-OCC-10170: Unable to process. Device configuration data contains special characters.' - the device config itself cannot be modified"
I can also recommend to reach Broadcom Services team either through contacting customer support or through you sales rep, and they could assist in the scripting of Perl. ------------------------------
Senior Support Engineer
Broadcom
------------------------------
Original Message:
Sent: 03-30-2020 01:56 AM
From: john Robert singh
Subject: SPC-OCC-10170: Unable to process. Device configuration data contains special characters.
Hi Jason,
I have tried these things already , and found the "*" is the special char , but the device is our core so the network team is not going to change anything in these device end.
Can we able to match these "*" char using the perl script.
Original Message------
Hello John
Please check this article. https://knowledge.broadcom.com/external/article?articleId=92584
Just curious, were you able to search Broadcom support for the error to locate the article?
------------------------------
Senior Support Engineer
Broadcom
------------------------------