IBM Cloud Pak for Integration Support Guide for App Connect L2

CP4I is a platform designed to offer multiple containerized products. Below is a list of components that are integrated in CP4I

• Platform Navigator, a simple integrated user interface spanning components
• Asset Repository, allows the user to store, manage, retrieve and search integration assets
• Cloud Private, providing a Kubernetes-based foundation
• API Connect, implementing managed APIs
• App Connect Enterprise, providing integration workflows
• MQ Advanced, for robust guaranteed transport
• Event Streams (MQ team), for event handling based on Kafka
• DataPower Gateway, for gateway services
• Aspera High Speed Transfer Server, for large file transfers
• App Connect Designer, to connect applications (apps) in minutes

Use this MustGather if a client is doing cp4i install following the steps in CP4I Knowledge Center

1. Re-run the CP4I installer in verbose mode by appending this command to the installer command, and provide the output log: -vvv | tee ~/cp4i_install.log.

If a client is doing CP4I install on IBM Cloud using one-click procedure or the automation script,

1. What is the OCP version: ?
2. We'll also need to collect some information from cluster summary. (On ibm cloud Kubernetes -> clusters -> cluster name)
3.  The 1-click install logs from the web-ui
4. Run the below OC Commands after logging in (oc login) to the cluster.
   oc get pods -n kube-system
   oc get pods -n
   oc get routes --all-namespaces
   oc describe route navigator -n integration
   oc describe route icp-console -n kube-system
   oc describe route icp-proxy -n kube-system
   oc get events --all-namespaces

1. CP4I Version: cloudctl version.
2. Platform Options: OpenShift version on [Redhat, MS Azure, AWS, Google Cloud, IBM Cloud, AWS, Google, IBM Cloud, Centos, Ubuntu].
3. Output all pods in your namespace to text file: oc get pods -n <namespace>.
4. Get the pod(s) log(s) in text file: oc logs -f <pod name> -c <container name> -n <namespace>. It is possible to have more than one pod; Better to get the logs for all if logs contents are not the same.
5. Describe the pod(s) and redirect the output to a text file: oc describe pod <pod name> -n <namespace>. It is possible to have more than one pod; Better to describe all if they provide different outputs.
6. Output all nodes in your namespace to atext file: oc get nodes -n <namespace>.
7. Output of the ingress to text file: oc get ingress -n <namespace>.
8. Output of the routes to text file: oc get routes.
9. Output of the jobs to text file: oc get jobs -n <namespace>.
10. Output of the pods in the kube-system namespace to text file: oc get pods -n kube-system.
11. Output of the daemonsets in the kube-system to text file: oc get daemonsets -n kube-system.
12. Get the tiller pod log in text file: oc logs <tiller pod name> -n <namespace>.

If client is having any type of issue with a product specific dashboard, please transfer the parent case to that product specific team. In addition, if the issue is related to the run-time of a product specific, you would also transfer the parent case to that product team.

In case, it happens that the product specific is ACE, the CP4I team will take ownership of the parent case and work it. Please look at the ACE DASHBOARD section for the MustGather. If you need to engage L3 then you must engage ACE L3 via a skill case. Please review ACE_L2_L3 case template before opening the skill case.

1. https://docs.openshift.com/container-platform/4.6/welcome/index.html

1. CP4I Version: cloudctl version.
2. Platform Options: OpenShift version on [Redhat, MS Azure, AWS, Google Cloud, IBM Cloud, AWS, Google, IBM Cloud, Centos, Ubuntu].
3. Output all pods in your namespace to text file: oc get pods -n <namespace>.
4. Get the pod(s) log(s) in text file: oc logs -f <pod name> -c <container name> -n <namespace>. It is possible to have more than one pod; Better to get the logs for all if logs contents are not the same.
5. Describe the replicaset and redirect the output to a text file: kubectl describe rs/<replicaset name>.
6. For ACE-specific logging, please refer to the ACE FAQ under the section Troubleshooting and Serviceability

Clients might have issues with bar file deployment, execution of mqsi commands, accessing webui, or issue related to their project interchange (PI).

1. CP4I Version: cloudctl version.
2. Platform Options: OpenShift version on [Redhat, MS Azure, AWS, Google Cloud, IBM Cloud, AWS, Google, IBM Cloud, Centos, Ubuntu].
3. Output all pods in your namespace to text file: oc get pods -n <namespace>.
4. Get the pod(s) log(s) in text file: oc logs -f <pod name> -c <container name> -n <namespace>. It is possible to have more than one pod; Better to get the logs for all if logs contents are not the same.
5. For ACE-specific logging, please refer to the ACE FAQ under the section Troubleshooting and Serviceability

Clients are experiencing issues with one or more Common Services / RHOCP components packaged with CP4I

export MGDIR=cp-ibmcommonservices-$(date -Ihours)
export LOGLIMIT="--tail=10000"
mkdir -p $MGDIR

oc get nodes > $MGDIR/node-list.txt
oc describe nodes > $MGDIR/node-describe.txt
oc get namespaces > $MGDIR/namespaces.txt
oc get clusteroperators > $MGDIR/cluster-operators.txt
oc get pods --all-namespaces -o wide > $MGDIR/all-pods-list.txt
oc adm top nodes > $MGDIR/top-nodes.txt
oc adm top pods --all-namespaces > $MGDIR/top-pods.txt
oc get cm ibmcloud-cluster-info -n kube-public -o yaml > $MGDIR/ibmcloud-cluster-info.txt

for NS in ibm-common-services kube-system; do
  export NS=$NS; mkdir $MGDIR/$NS; echo gathering info from namespace $NS
  oc get all,secrets,cm,ing,events -n $NS -o wide &> $MGDIR/$NS/all-list.txt
  oc get pods -n $NS | awk 'NR>1{print "oc -n $NS describe pod "$1" > $MGDIR/$NS/"$1"-describe.txt && echo described "$1}' | bash
  oc get pods -n $NS -o go-template='{{range $i := .items}}{{range $c := $i.spec.containers}}{{println $i.metadata.name $c.name}}{{end}}{{end}}' > $MGDIR/$NS/container-list.txt
  awk '{print "oc -n $NS logs "$1" -c "$2" $LOGLIMIT -p > $MGDIR/$NS/"$1"_"$2"_previous.log && echo gathered previous logs of "$1"_"$2}' $MGDIR/$NS/container-list.txt | bash
  awk '{print "oc -n $NS logs "$1" -c "$2" $LOGLIMIT > $MGDIR/$NS/"$1"_"$2".log && echo gathered logs of "$1"_"$2}' $MGDIR/$NS/container-list.txt | bash
done

tar czf $MGDIR.tgz $MGDIR/
echo "DONE"
echo "--- Please send "$MGDIR.tgz" to Common Services Support Team ---"

• DESCRIPTION OF THE ISSUE
  • Provide as much description as possible of the problem.
• ENVIRONMENT DETAILS
  • Platforms: [RedHat OpenShift, MS Azure, AWS, Google Cloud, IBM Cloud]
  • Versions: [CP4I version], [Platform Version]
  • CSP Case Number: [Parent Case Number]
  • CSP Case Severity: [Case Priority Number]
• MUST GATHERS / DOCUMENTATION PROVIDED
  • Provide ecurep path to the documentation to be analyzed
• IS THE PROBLEM RECREATABLE
  • Can the problem be easily recreated by either us or the customer outside of production?
• ACTION PLAN
  • What is the suggested next action for CP4I L3 to perform
• URGENCY
  • Production or Test/Development environment:
  • Customer deadlines:
  • Is this a critsit?

• PROBLEM SUMMARY
  • Short description of the problem
• ENVIRONMENT DETAILS
  • Platforms: [RedHat OpenShift version, MS Azure, AWS, Google Cloud, IBM Cloud]
  • Versions: [CP4I version], [Platform Version]
• MUST GATHERS/ DOCUMENTATION PROVIDED
  • Provide ecurep path to the documentation to be analyzed
• IS THE PROBLEM RECREATABLE
  • Can the problem be easily recreated by either us or the customer outside of production?
• ACTION PLAN
  • What is the suggested next action for Common Services to perform
• URGENCY
  • Production or Test/Development environment:
  • Customer deadlines:
  • Is this a critsit?

Note:To find which product name, support mission, support skill to use when creating skill cases or transferring parent cases to Common Services team, please check the Product CRF & Escalations tab on this page

• Fyre Labe setup and login instructions