OPMS optunnel domain information update

Products

• CA App Synthetic Monitor
• DX Application Performance Management

Issue/Introduction

As part of the ASM 10.5 upgrade there have been changes to the domains from ca.com to saas.broadcom.com

Steps are required to update OPMS configuration to maintain communication with our servers

Environment

All ASM SaaS releases. Updated info for 10.5 and later

Resolution

 

- Edit the /etc/asm/optunnel.yaml file

 

- change the client/websocket/host key

 

 from

 

     opp1.asm.ca.com,opp2.asm.ca.com 

 

to

 

     opp1.asm.saas.broadcom.com,opp2.asm.saas.broadcom.com 

 

(be careful to preserve the indentation in the file)

 

and save the file

 

- restart the service using the command

 

     /etc/init.d/optunnel-client restart

 

This is an example of how the updated file will look

 

# cat optunnel.yaml

client:

    client-tunnel-cid: xxxxxxxx-xxxx-xxx-xxxxxxxxxxxx

    websocket:

        host: opp1.asm.saas.broadcom.com,opp2.asm.saas.broadcom.com

        wss_port: 443

        verify: false

        idle-timeout: 80

    proxy:

        max-connections: 2048

        stream-timeout: 10

        stream-threshold: 8192

        timeout: 360

logging:

    handlers:

        file:

            filename: /var/log/optunnel/optunnel-client.log

            level: INFO

Additional Information

 

IP addresses change:

 

As a result of the infrastructure provider change, the IP addresses the product is running on will change. If you are running any IP based firewalls, please update them accordingly.