Skip to content

Checklist For EMS

ewb

  • If Apache service is normal running, input the ewb ip address in brower for check whether ems page and common function is normal.
  • Open the administration page configure rule and accept event for later testing.
  • Test escalation rule function and check whether alert was sent successful when matched rules.(more detail infomation link:https://docs.mas.webex.com/ems/knowledge-base/runbook/?h=escalation#how-to-troubleshoot-escalation-rule-not-work)

epi

  • Test sending api event to 'http://$hostName/api/internal/handler_v2' if it's not starting service through cmc refresh.
  • For details, please refer to EMS Rest API Dcoumentation

ims

  • After configuring the rule, test whether the email event can be successfully received.
  • Track and check whether there are errors in emsd logs, such as those related to Kafka, RabbitMQ and email.
  • Check email event function is work.

ets

  • Check snmptrap.log "tail -f /var/log/snmptrapd.log".
  • Packet capture "tcpdump -i ens192 udp port 162".
  • Send a trap and catch it "tcpdump -i ens192 udp port 162 | grep "{hostname}"". 
    /usr/bin/snmptrap -v 2c -c public bmsj1traps.webex.com "" .1.3.6.1.4.1.11435.102.2.1.6 .1.3.6.1.4.1.11435.102.1.1 s  "Filesystem: /dev/vda9999; Mounted On: /; Usage: 6%; Filesystem: /dev/vda1; Mounted On: /boot; Usage: 18%; Filesystem: /dev/vda3; Mounted On: /var; Usage: 6%; Filesystem: /dev/vda5; Mounted On: /var/log; Usage: 9%; Filesystem: /dev/vda8; Mounted On: /var/log/audit; Usage: 26%;"