cloud discovery

[Detlef Biederma]

Hello  

I have to configure cloud discovery.  To prepare this, I play around with my PDI and my AWS account. 

Creating:
- aws service account

- aws cloud account  (only "eu-central-1")

- scheduled discovery:  "aws_sched_01"   which will result into 2 schedules 
  aws_sched_01 -  connect to AWS directly (api)
  aws_sched_01- VM schedule -  discovers the VM's  (like it would be on premise)
  

Question:  aws_sched_01- VM schedule  -  does not have any "Discovery IP Ranges" defined,  how does the job know what to discover ? 

Sincerely Detlef Biedermann

[Community Alums]

Hi @Detlef Biederma ,

Please go though these links:

https://www.servicenow.com/community/itom-forum/horizontal-discovery-is-not-getting-trigger-for-some...

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0966207

[Detlef Biederma · Accepted solution]

Hello 

I could answer myself: 

 var v_gr = new GlideRecord('discovery_schedule');

 v_gr.get('name','aws_sched_all- VM schedule');    //all AWS Datacenters

var ipList = new CloudDiscoveryScheduleConfig().getListofIPAddressesForVMSchedule(v_gr.sys_id);

gs.info(ipList);

 var v_gr = new GlideRecord('discovery_schedule');

 v_gr.get('name','aws_sched_05- VM schedule');   //datacenter eu-west-1

var ipList = new CloudDiscoveryScheduleConfig().getListofIPAddressesForVMSchedule(v_gr.sys_id);

gs.info(ipList);

 var v_gr = new GlideRecord('discovery_schedule');

 v_gr.get('name','AWS_sched_04- VM schedule');  //datacenter eu-central-1

var ipList = new CloudDiscoveryScheduleConfig().getListofIPAddressesForVMSchedule(v_gr.sys_id);

gs.info(ipList);

results to:

*** Script: 34.243.150.143,172.31.11.161,18.192.45.189,172.31.32.115,52.59.196.252,172.31.27.155
*** Script: 34.243.150.143,172.31.11.161
*** Script: 18.192.45.189,172.31.32.115,52.59.196.252,172.31.27.155

First row: all IP's over all datacenter

Second & third row - only IP's into the corresponding datacenter

Question:  2 of the IP's belong to the mid server  (172.31.32.115 & 18.192.45.189)    

(same situation on all other server (one private & one public IP)  

To discover the public IP should be sufficient ?  (even I can not ping all private IP's from mid server)

Sincerely Detlef Biedermann