Ultra M Manager Health Check Service Configuration ·...
4
Ultra M Manager Health Check Service Configuration • Feature Summary and Revision History, on page 1 • Feature Description, on page 1 Feature Summary and Revision History Summary Data All Applicable Product(s) or Functional Area UGP deployed on Ultra M Applicable Platform(s) Disabled - Configuration Required Feature Default Related Changes in This Release Ultra M Solutions Guide Related Documentation Revision History Release Revision Details 6.0 First introduced in a FCS release. (It had been previously releases in the 5.1.8 ER. Feature Description The Ultra M Manager now allows you to specify which components, domains, services, and severity to monitor and support. During configuration, the individual domains for which you wish to perform event aggregation can be specified within the ultram_cfg.yaml file. Alternatively, if no components or services are specified, then the default behavior is to monitor all domains. Ultra M Manager Health Check Service Configuration 1
Transcript of Ultra M Manager Health Check Service Configuration ·...
Ultra M Manager Health Check ServiceConfiguration
• Feature Summary and Revision History, on page 1• Feature Description, on page 1
Feature Summary and Revision HistorySummary Data
AllApplicable Product(s) or FunctionalArea
UGP deployed on Ultra MApplicable Platform(s)
Disabled - Configuration RequiredFeature Default
Related Changes in This Release
Ultra M Solutions GuideRelated Documentation
Revision History
ReleaseRevision Details
6.0First introduced in a FCS release. (It had been previously releases in the 5.1.8 ER.
Feature DescriptionThe UltraMManager now allows you to specify which components, domains, services, and severity to monitorand support.
During configuration, the individual domains for which you wish to perform event aggregation can be specifiedwithin the ultram_cfg.yaml file. Alternatively, if no components or services are specified, then the defaultbehavior is to monitor all domains.
Ultra M Manager Health Check Service Configuration1
To facilitate this change, the following parameters are now available in the ultram_cfg.yaml:#------------------------------------------------------------------# Configuration data for Ultra-M Health Check#------------------------------------------------------------------
# Health check polling frequency 15min# In order to ensure optimal performance, it is strongly recommended that# you do not change the default polling-interval of 15 minutes (900 seconds).polling-interval: 900
# under-cloud info, this is used to authenticate# OSPD and mostly used to build inventory list (compute, controllers, OSDs)under-cloud:environment:OS_AUTH_URL: http://192.200.0.1:5000/v2.0OS_USERNAME: adminOS_TENANT_NAME: adminOS_PASSWORD: *******
prefix: neutonoc
# over-cloud info, to authenticate OpenStack Keystone endpointover-cloud:enabled: trueenvironment:OS_AUTH_URL: http://172.21.201.217:5000/v2.0OS_TENANT_NAME: user1OS_USERNAME: user1OS_PASSWORD: *******OS_ENDPOINT_TYPE: publicURLOS_IDENTITY_API_VERSION: 2OS_REGION_NAME: regionOne
modules:- ceph- cinder- nova- pcs- rabbitmqctl- neutron- ntpdc- systemctl
controller-services:- aodh- ceilometer- cinder- glance- gnocchi- heat- nova- swift- ntpd- mongod- memcached- neutron-dhcp-agent- neutron-l3-agent- neutron-metadata-agent- neutron-openvswitch-agent- neutron-server- httpd
compute-services:- ceph-mon.target- ceph-radosgw.target
Ultra M Manager Health Check Service Configuration2
Ultra M Manager Health Check Service ConfigurationFeature Description
- ceph.target- openvswitch.service- neutron-sriov-nic-agent- neutron-openvswitch-agent- ntpd- nova-compute- libvirtd
osd-compute-services:- ceph-mon.target- ceph-radosgw.target- ceph.target- openvswitch.service- neutron-sriov-nic-agent- neutron-openvswitch-agent- ntpd- nova-compute- libvirtd
# SSH Key to be used to login without username/passwordauth-key: /home/stack/.ssh/id_rsa
# Number of OpenStack controller nodescontroller_count: 3
# Number of osd-compute nodesosd_compute_count: 3
# Number of OSD disks per osd-compute nodeosd_disk_count_per_osd_compute: 4
# Mark "ceph df" down if raw usage exceeds this settingceph_df_use_threshold: 80.0
# Max NTP skew limit in milisecondsntp_skew_limit: 100
snmp:severity: 5nms-server:10.105.248.149:community: public
10.105.248.149:user:name: testauth-protocol: md5auth-key: admin12345priv-protocol: cbc-despriv-key: admin12345
agent:community: public
ucs-cluster:enabled: trueuser: adminpassword: *******data-dir: '/opt/cisco/usp/ultram_health.data/ucs'log-file: '/var/log/cisco/ultram_ucs.log'
uas-cluster:enabled: falselog-file: '/var/log/cisco/ultram_uas.log'data-dir: '/opt/cisco/usp/ultram_health.data/uas'autovnf:
Ultra M Manager Health Check Service Configuration3
Ultra M Manager Health Check Service ConfigurationFeature Description
172.21.201.53:autovnf:login:user: ubuntupassword: *******
netconf:user: adminpassword: admin
em:login:user: ubuntupassword: *******
netconf:user: adminpassword: *******
esc:login:user: adminpassword: *******
172.21.201.54:autovnf:login:user: ubuntupassword: *******
netconf:user: adminpassword: *******
em:login:user: ubuntupassword: *******
netconf:user: adminpassword: *******
esc:login:user: adminpassword: *******
#rsyslog configuration, here proxy-rsyslog is IP address of Ultra M Manager Node (NOT remotersyslog):rsyslog:level: 4,3,2,1,0proxy-rsyslog: 192.200.0.251
Ultra M Manager Health Check Service Configuration4
Ultra M Manager Health Check Service ConfigurationFeature Description
