This section describes about the necessary configuration changes in SAM (Service Assurance Manager), to get the notifications from vRealize Operations.
Configuration changes for OnPrem and Cloud vROPS in SAM:
- Go to, <SAM-Basedir>/smarts/local/conf/clientConnect.conf file and edit the clientConnect.conf file, by entering the following lines:
kafka:<Kafka-Host>:<Kafka-Server-Username>:<Kafka-Server-Password>
dcc:<dccIP>:<dcc-Username>:<dcc-password>
If the DCC default password does not work, use the following text to make it work:dcc:<dccIP>:"":""
Also, there is no support for Kafka authentication in TCO-DCC. So, the username and the password fields must be
Kafka:<KafkaIP>:"":"".Note: For VMware Telco Cloud Service Assurance installation, use the following IP addresses for Kafka and DCC:- Use domain manager IP address for Kafka.
- Use control node IP address for DCC.
You can create the API token on the cloud service portal. To access the Cloud vROPS, you must update the API token in the following format:
vrops:<console-Hostname of Cloud>:””:<API Token for Cloud Access>Note: Username of Cloud must be “”To access the OnPrem vROPS, you must update the username and password in the following format:
vrops:<vropsIP>:<vrops-username>:<vrops-password>
You must add the line under Program Access and above "\\*:\\*:admin.
- Go to, <SAM-Basedir>/smarts/local/conf/icoi/kafka_adapter.conf file uncomment and edit the kafka_adapter.conf file by modifying the following parameters:
# Field used to check if a kafka adapter is enabled or not # By default it would be set to FALSE # Once you set the value to TRUE make sure all below # fields are uncommented # # A value of TRUE indicates that driver would subscribe to kafka # A value of FALSE indicates that the driver should not subscribe to kafka EnableKafkaSubscription TRUE # DCC Poll interval value # unit is in seconds # Default value is 300 seconds, A value less than # default will have performance impact # Any change to default value requires server restart DccPollInterval 300 # Kafka Poll timeout value # unit is in seconds # Any change to default value requires server restart KafkaPollTimeOut 30 # Kafka consumer session timeout value # unit is in miliseconds # Any change to default value requires server restart KafkaSessionTimeOut 10000 # Kafka consumer request timeout value # unit is in miliseconds # Any change to default value requires server restart KafkaRequestTimeOut 15000 # # Types Of Alerts you want to Subscribe for VROPS # Supported values are : ALL, PERFORMANCE, COMPLIANCE # SubscribedAlertype ALL # # To enable OI adapter logging, Set log level value to OFF, FATAL, ERR, WARN, INFO, DEBUG, TRACE, ALL. # Only one value can be set at a time. By default log level set to ERR # Any change to the default value requires server restart # Loglevel ERR # # To enable SMARTS kafkaAdapter logging independently, Set log level value from apache org.apache.log4j.Level # to OFF, FATAL, ERROR, WARN, INFO, DEBUG, TRACE, ALL. # Only one value can be set at a time. By default log level set to ERROR # Any change to the default value requires server restart # KafkaAdapterLogLevel ERROR # # # vROPS Standalone/on-prem Service Alert Collector Configuration # To subsubibe vrop please refer to the below exmaple # configuration # Any change it requires server restart # #VROPS-x.x.x.x ONPREM <Uncomment and update the VROPS IP address> #VROPS_PROTOCOL-x.x.x.x https <Uncomment and update the VROPS IP address> #VROPS_PORT-x.x.x.x 443 <Uncomment and update the VROPS IP address> #DCC-x.x.x.x y.y.y.y <Uncomment and update the VROPS and DCC IP address> #DCC_PORT-x.x.x.x 8443 <Uncomment and update the VROPS IP address> #DCC_PROTOCOL-x.x.x.x https <Uncomment and update the VROPS IP address> #KAFKA-x.x.x.x z.z.z.z:9092,z.z.z.z:9093 <Uncomment and update the VROPS, KAFKA IP address and KAFKA Port> #KAFKA_TOPICS-x.x.x.x vrops-new <Uncomment and update the VROPS IP address and KAFKA Topic> # vROPS Cloud Service Alert Collector Configuration #VROPS-cloud.com CLOUD <Uncomment and update the VROPS Cloud Service URL> #VROPS_CLOUD_API-cloud.com www.cloud-api.com <Uncomment and update the VROPS Cloud Service URL and Cloud API URL> #VROPS_PROTOCOL-cloud.com https <Uncomment and update the VROPS Cloud Service URL> #VROPS_PORT-cloud.com 443 <Uncomment and update the VROPS Cloud Service URL> #DCC-cloud.com y.y.y.y <Uncomment and update the VROPS Cloud Service URL and DCC IP address>> #DCC_PORT-cloud.com 8443 <Uncomment and update the VROPS Cloud Service URL> #DCC_PROTOCOL-cloud.com https <Uncomment and update the VROPS Cloud Service URL> #KAFKA-console-cloud.com z.z.z.z:9092,z.z.z.z:9093 <Uncomment and update the VROPS Cloud Service URL, KAFKA IP, and KAFKA Port> #KAFKA_TOPICS-cloud.com vrops-cloud <Uncomment and update the VROPS Cloud Service URL and KAFKA Topic>
Note:- When you upgrade from 10.x to 10.1.5.0, before starting the OI server, rename the kafka_adapter.conf file to kafka_adapter.conf_backup , in the path
<Basedir>/smarts/local/conf/icoi/kafka_adapter.confand follow step 2.
- When you upgrade from 10.x to 10.1.5.0, before starting the OI server, rename the kafka_adapter.conf file to kafka_adapter.conf_backup , in the path
Installation of vROPS Collector enables user to subscribe to All or Performance or Compliance alerts that are coming from vROps. This reduces the unnecessary events flow from vROPS to SAM.
If subscribe for All alerts, you can filter it further to see only Performance alerts by adding filter as category==performance in the SAM console.
To apply the necessary configuration changes, start OI server when you are using it for the first time.
Later, you can change the subscription level or you can change any variable. To get into effect, run the cmd:
<dmctl> invoke GA_Driver::vROPS_Alerts_Adapter-Driver start
