04-04-2023 05:37 AM
Our Cisco ISE Admin primary Server is complaining that its secondary Admin ISE messaging service process is not running.
A stop and restart of the services was performed this morning, but made no difference.
Apr 02 2023 04:11:45.562 AM
ISE Messaging Service not running : Server=n-ciscoise-05
Cisco Identity Services Engine
---------------------------------------------
Version : 3.1.0.518
It is not service impacting, but curious to know what implications this will have?
thanks
04-04-2023 05:50 AM
- Whilst this bug report may not be related https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvo74441 , (it also refers to another version) , I would try a reload anyway ,
M.
04-04-2023 08:04 AM
Patch version?
04-04-2023 05:01 PM
hello @DigiDen, the feature is enabled in all the nodes within the an environment as default it's main purpose is related to the logging of information , if you go to the menu Administration>system>logging>log settings, you will be able to see here that there is a global setting that is related and says " ", hence if you have this setting enabled and your node has the service not running as expected , you might encounter that the logging of that node is not arriving to the MNT nodes within your implementation.
To see the log categories that all the nodes in your deployment will send to MNT go to the menu named "Logging Categories" under the same section , this is how all the nodes are sending syslog information , the targets named "logcollector" "logcollector2" are PMNT and SMNT . To review more information about, please review https://www.cisco.com/c/en/us/td/docs/security/ise/3-1/admin_guide/b_ise_admin_3_1/b_ISE_admin_31_deployment.html#id_100229
Rate and let me know if that helped you.
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