VES has sourceName indicating the device measurement are collected for, whereas reportingEntityName is most cases would be same as sourceName if the same device is sending the events to DCAE Collector. If there is an EMS or OAM VM involved sending events on the behalf of source then reportingEntityName should have the name of the EMS/OAM VM.
Regards, Alok Gupta 732-420-7007 MT B2 3D30 [email protected]<mailto:[email protected]> From: [email protected] <[email protected]> On Behalf Of PLATANIA, MARCO Sent: Wednesday, December 19, 2018 9:09 AM To: [email protected]; [email protected]; HERNANDEZ-HERRERO, JORGE <[email protected]> Subject: Re: [onap-discuss] [POLICY] Actor SO not triggered when simulators turned off ***Security Advisory: This Message Originated Outside of AT&T *** Reference http://cso.att.com/EmailSecurity/IDSP.html for more information. I see 2 different vLB names in the logs. Can you please describe your scenario? How are the closed loop and guard policies designed? Also, what is the reporting entity name in the VES message? My guess is that there’s some conflict somewhere. Marco From: <[email protected]<mailto:[email protected]>> on behalf of vamshi <[email protected]<mailto:[email protected]>> Reply-To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>>, "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Date: Wednesday, December 19, 2018 at 8:43 AM To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>>, "HERNANDEZ-HERRERO, JORGE" <[email protected]<mailto:[email protected]>> Subject: [onap-discuss] [POLICY] Actor SO not triggered when simulators turned off Hi, I’ve tried vDNS usecase with the controlloop created from CLAMP. All is well when I tried with simulators – policy could trigger SO API for vnf-scale out. The same behavior I anticipated when turning the simulators off, but it stopped processing after guard PERMIT received for SO VF MODULE CREATE. Can somebody suggest what could cause the POLICY restrain from triggering SO api for vnf scale out. I’ve attached network.log for both simulated and non-simulated mode of vDNS execution. Appreciate your assistance. Thanks & Regards, Vamshi Krishna | Tech Mahindra [id:[email protected]]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.techmahindra.com_&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=_g_bZIoC9S_5OOU0uqUWMSpjM-bG5_TKUu7Kx_C970o&s=E1zBHG5xg5etfEwpnGCd3wn5VoCcJeVCcWtCiHCQ5tY&e=> ============================================================================================================================ Disclaimer: This message and the information contained herein is proprietary and confidential and subject to the Tech Mahindra policy statement, you may review the policy at http://www.techmahindra.com/Disclaimer.html<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.techmahindra.com_Disclaimer.html&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=_g_bZIoC9S_5OOU0uqUWMSpjM-bG5_TKUu7Kx_C970o&s=1Tcr_GrhVKQtyf1PkQKn41accJQ2blSG3xzouHBE_NA&e=> externally http://tim.techmahindra.com/tim/disclaimer.html<https://urldefense.proofpoint.com/v2/url?u=http-3A__tim.techmahindra.com_tim_disclaimer.html&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=_g_bZIoC9S_5OOU0uqUWMSpjM-bG5_TKUu7Kx_C970o&s=CS2EYExJl50vnAjnvh36v2xJUiEN2YCfb2TGVg_xFP4&e=> internally within TechMahindra. ============================================================================================================================ -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#14623): https://lists.onap.org/g/onap-discuss/message/14623 Mute This Topic: https://lists.onap.org/mt/28801807/21656 Group Owner: [email protected] Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
