PDF(82.0 KB) View with Adobe Reader on a variety of devices
ePub(80.4 KB) View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
Mobi (Kindle)(65.4 KB) View on Kindle device or Kindle app on multiple devices
Updated:January 13, 2021
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
* Only for system having MUC configured as external component under:
UMS_CLI/System/ProfileTuning/GeneralSettings> g profileTuningName = mucExternal
According to the test requested by TAC, you will need to enable/disable one or more of the troubleshooting channels using the related API Attributes.
Note the customers will be unable to enable those ExtaLogging IMPLog channels with the original test instructions from those patches.
The original patches release Notes "test instructions" contain improper information, plus the API have change over time to be able to survive restart of the UMS server
Here are the right instruction on using API /gateway/implog
1. To enable extra IMP logging, you need to send a POST HTTP command with the name of the API Attributes matching the channel you need. Here is an example for channel componentProtocolExtraLoggingActive:
2. To verify how the channels configuration, you need to send the following API command:
Response from the server will have the channels listed showing individual configuration: