05-23-2017 01:29 PM
Working on a fresh 2.2 Patch 1 deployment and we are seeing some odd behavior in certain spots in ISE. I normally use underscores in my naming convention in ISE as I know underscores are allowed on all screens (well not the purge policy names but don't get me started on that). Dashes are allowed on most screens but not all. This customer wants to use dashes even though I cautioned them on using it.
Periodically when the customer is modifying profiling policies with dashed in them the application server service will restart. The browser just hangs that and if you go to the CLI you can see the service is initializing. I saw this today on a Webex with them when working on an Endpoint Identity Group. I created the group with an underscore out of habit, Paul_Whitelist. I saved it and everything was fine. They reminded me of their use of dashes. I clicked on the group, changed to a dash, Paul-Whitelist, clicked save and service crashed.
Is this a known issue. Doesn't always happen.
Thanks.
Solved! Go to Solution.
05-23-2017 03:29 PM
Hi Paul,
If it is a live deployment, please reach out to TAC and open a defect. Looks like a new issue to me.
-Krishnan
05-23-2017 03:29 PM
Hi Paul,
If it is a live deployment, please reach out to TAC and open a defect. Looks like a new issue to me.
-Krishnan
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide