Question - PODM do not find PSME REST server when not add psme service in services list

[housemic]

Dear intel, the issue is related to - Question for PODM do not find second PSME server and PSME compute simulator #50,

PODM can find PSME compute asset after I add psme service in : /tmp/services.list https://:8443/redfish/v1 psme

but if I do not add psme service in : /tmp/services.list, PODM can not find PSME REST server.

the following is my detail checking, Please support, thank you. House

[housemic]

Dear intel, I use tcpdump to display network packets, found that PODM send M-SEARCH, but PSME do not response.

the following action are my steps -

I installed 2 PODM and 1 PSME (running PSME REST Server and PSME compute agent simulator),

PODM No.1 IP Address - 192.168.1.87

PODM No.2 IP Address - 192.168.1.105

PSME Server No.1 IP Address - 192.168.1.135

user@psme1:~$ sudo tcpdump -ni any host 192.168.1.87 -ttttt [sudo] password for user: tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on any, link-type LINUX_SLL (Linux cooked), capture size 262144 bytes 00:00:00.000000 ARP, Request who-has 192.168.1.136 tell 192.168.1.87, length 46 00:00:01.025627 ARP, Request who-has 192.168.1.136 tell 192.168.1.87, length 46 00:00:02.049630 ARP, Request who-has 192.168.1.136 tell 192.168.1.87, length 46 00:01:05.999759 ARP, Request who-has 192.168.1.136 tell 192.168.1.87, length 46 00:01:07.009332 ARP, Request who-has 192.168.1.136 tell 192.168.1.87, length 46 00:01:08.033352 ARP, Request who-has 192.168.1.136 tell 192.168.1.87, length 46 00:02:12.999427 ARP, Request who-has 192.168.1.136 tell 192.168.1.87, length 46 00:02:14.017123 ARP, Request who-has 192.168.1.136 tell 192.168.1.87, length 46 00:02:15.041051 ARP, Request who-has 192.168.1.136 tell 192.168.1.87, length 46 00:02:39.147555 IP 192.168.1.87.46431 > 239.255.255.250.1900: UDP, length 121 00:02:39.647745 IP 192.168.1.87.46431 > 239.255.255.250.1900: UDP, length 121 00:02:40.147883 IP 192.168.1.87.46431 > 239.255.255.250.1900: UDP, length 121 00:03:19.999071 ARP, Request who-has 192.168.1.136 tell 192.168.1.87, length 46 00:03:21.024762 ARP, Request who-has 192.168.1.136 tell 192.168.1.87, length 46 00:03:22.048746 ARP, Request who-has 192.168.1.136 tell 192.168.1.87, length 46 00:04:26.998864 ARP, Request who-has 192.168.1.136 tell 192.168.1.87, length 46 00:04:28.000512 ARP, Request who-has 192.168.1.136 tell 192.168.1.87, length 46 00:04:29.024453 ARP, Request who-has 192.168.1.136 tell 192.168.1.87, length 46 00:05:33.998520 ARP, Request who-has 192.168.1.136 tell 192.168.1.87, length 46 00:05:35.008150 ARP, Request who-has 192.168.1.136 tell 192.168.1.87, length 46 00:05:36.032174 ARP, Request who-has 192.168.1.136 tell 192.168.1.87, length 46 00:06:37.998240 ARP, Request who-has 192.168.1.136 tell 192.168.1.87, length 46 00:06:39.007856 ARP, Request who-has 192.168.1.136 tell 192.168.1.87, length 46 00:06:40.031891 ARP, Request who-has 192.168.1.136 tell 192.168.1.87, length 46 00:07:41.997968 ARP, Request who-has 192.168.1.136 tell 192.168.1.87, length 46 00:07:43.007568 ARP, Request who-has 192.168.1.136 tell 192.168.1.87, length 46 00:07:44.031569 ARP, Request who-has 192.168.1.136 tell 192.168.1.87, length 46 00:08:48.997639 ARP, Request who-has 192.168.1.136 tell 192.168.1.87, length 46 00:08:50.015294 ARP, Request who-has 192.168.1.136 tell 192.168.1.87, length 46 00:08:51.039247 ARP, Request who-has 192.168.1.136 tell 192.168.1.87, length 46 00:09:53.997388 ARP, Request who-has 192.168.1.136 tell 192.168.1.87, length 46 00:09:55.007053 ARP, Request who-has 192.168.1.136 tell 192.168.1.87, length 46 00:09:56.030988 ARP, Request who-has 192.168.1.136 tell 192.168.1.87, length 46 00:11:00.997040 ARP, Request who-has 192.168.1.136 tell 192.168.1.87, length 46 00:11:02.014709 ARP, Request who-has 192.168.1.136 tell 192.168.1.87, length 46 00:11:03.038716 ARP, Request who-has 192.168.1.136 tell 192.168.1.87, length 46 00:12:04.996720 ARP, Request who-has 192.168.1.136 tell 192.168.1.87, length 46 00:12:06.014396 ARP, Request who-has 192.168.1.136 tell 192.168.1.87, length 46 00:12:07.038385 ARP, Request who-has 192.168.1.136 tell 192.168.1.87, length 46 00:12:39.144951 IP 192.168.1.87.46431 > 239.255.255.250.1900: UDP, length 121 00:12:39.645283 IP 192.168.1.87.46431 > 239.255.255.250.1900: UDP, length 121 00:12:40.145431 IP 192.168.1.87.46431 > 239.255.255.250.1900: UDP, length 121 00:13:09.996464 ARP, Request who-has 192.168.1.136 tell 192.168.1.87, length 46 00:13:11.006108 ARP, Request who-has 192.168.1.136 tell 192.168.1.87, length 46 00:13:12.030094 ARP, Request who-has 192.168.1.136 tell 192.168.1.87, length 46 00:14:16.996100 ARP, Request who-has 192.168.1.136 tell 192.168.1.87, length 46

user@psme1:~$ sudo tcpdump -ni any host 192.168.1.105 -ttttt [sudo] password for user: tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on any, link-type LINUX_SLL (Linux cooked), capture size 262144 bytes 00:00:00.000000 IP 192.168.1.105.41150 > 239.255.255.250.1900: UDP, length 121 00:00:00.500205 IP 192.168.1.105.41150 > 239.255.255.250.1900: UDP, length 121 00:00:01.000491 IP 192.168.1.105.41150 > 239.255.255.250.1900: UDP, length 121 00:00:43.436017 ARP, Request who-has 192.168.1.1 tell 192.168.1.105, length 46 00:00:44.466813 ARP, Request who-has 192.168.1.1 tell 192.168.1.105, length 46 00:00:45.486806 ARP, Request who-has 192.168.1.1 tell 192.168.1.105, length 46 00:00:48.441023 ARP, Request who-has 192.168.1.1 tell 192.168.1.105, length 46 00:00:49.458828 ARP, Request who-has 192.168.1.1 tell 192.168.1.105, length 46 00:00:50.478782 ARP, Request who-has 192.168.1.1 tell 192.168.1.105, length 46 00:00:53.446076 ARP, Request who-has 192.168.1.1 tell 192.168.1.105, length 46 00:00:54.446770 ARP, Request who-has 192.168.1.1 tell 192.168.1.105, length 46 00:00:55.470746 ARP, Request who-has 192.168.1.1 tell 192.168.1.105, length 46 00:00:58.451153 ARP, Request who-has 192.168.1.1 tell 192.168.1.105, length 46 00:00:59.470723 ARP, Request who-has 192.168.1.1 tell 192.168.1.105, length 46 00:01:00.494730 ARP, Request who-has 192.168.1.1 tell 192.168.1.105, length 46 00:01:03.456318 ARP, Request who-has 192.168.1.1 tell 192.168.1.105, length 46 00:01:04.462745 ARP, Request who-has 192.168.1.1 tell 192.168.1.105, length 46 00:01:05.486705 ARP, Request who-has 192.168.1.1 tell 192.168.1.105, length 46 00:01:08.461332 ARP, Request who-has 192.168.1.1 tell 192.168.1.105, length 46 00:01:09.486738 ARP, Request who-has 192.168.1.1 tell 192.168.1.105, length 46 00:01:10.510737 ARP, Request who-has 192.168.1.1 tell 192.168.1.105, length 46 00:01:13.466443 ARP, Request who-has 192.168.1.1 tell 192.168.1.105, length 46 00:01:14.478644 ARP, Request who-has 192.168.1.1 tell 192.168.1.105, length 46 00:01:15.502694 ARP, Request who-has 192.168.1.1 tell 192.168.1.105, length 46 00:01:18.471507 ARP, Request who-has 192.168.1.1 tell 192.168.1.105, length 46 00:01:19.502569 ARP, Request who-has 192.168.1.1 tell 192.168.1.105, length 46 00:01:20.526610 ARP, Request who-has 192.168.1.1 tell 192.168.1.105, length 46 00:05:43.434981 ARP, Request who-has 192.168.1.1 tell 192.168.1.105, length 46 00:05:44.460837 ARP, Request who-has 192.168.1.1 tell 192.168.1.105, length 46 00:05:45.484896 ARP, Request who-has 192.168.1.1 tell 192.168.1.105, length 46 00:05:48.439991 ARP, Request who-has 192.168.1.1 tell 192.168.1.105, length 46 00:05:49.452846 ARP, Request who-has 192.168.1.1 tell 192.168.1.105, length 46 00:05:50.476853 ARP, Request who-has 192.168.1.1 tell 192.168.1.105, length 46 00:05:53.445041 ARP, Request who-has 192.168.1.1 tell 192.168.1.105, length 46 00:05:54.476758 ARP, Request who-has 192.168.1.1 tell 192.168.1.105, length 46 00:05:55.500755 ARP, Request who-has 192.168.1.1 tell 192.168.1.105, length 46 00:05:58.450024 ARP, Request who-has 192.168.1.1 tell 192.168.1.105, length 46 00:05:59.468732 ARP, Request who-has 192.168.1.1 tell 192.168.1.105, length 46 00:06:00.492752 ARP, Request who-has 192.168.1.1 tell 192.168.1.105, length 46 00:06:03.455289 ARP, Request who-has 192.168.1.1 tell 192.168.1.105, length 46 00:06:04.460699 ARP, Request who-has 192.168.1.1 tell 192.168.1.105, length 46 00:06:05.484694 ARP, Request who-has 192.168.1.1 tell 192.168.1.105, length 46 00:06:08.460293 ARP, Request who-has 192.168.1.1 tell 192.168.1.105, length 46 00:06:09.484696 ARP, Request who-has 192.168.1.1 tell 192.168.1.105, length 46 00:06:10.508707 ARP, Request who-has 192.168.1.1 tell 192.168.1.105, length 46 00:06:13.465402 ARP, Request who-has 192.168.1.1 tell 192.168.1.105, length 46 00:06:14.476740 ARP, Request who-has 192.168.1.1 tell 192.168.1.105, length 46 00:06:15.500626 ARP, Request who-has 192.168.1.1 tell 192.168.1.105, length 46 00:06:18.470366 ARP, Request who-has 192.168.1.1 tell 192.168.1.105, length 46 00:06:19.500600 ARP, Request who-has 192.168.1.1 tell 192.168.1.105, length 46 00:06:20.524617 ARP, Request who-has 192.168.1.1 tell 192.168.1.105, length 46 00:09:59.996318 IP 192.168.1.105.41150 > 239.255.255.250.1900: UDP, length 121 00:10:00.496526 IP 192.168.1.105.41150 > 239.255.255.250.1900: UDP, length 121 00:10:00.996751 IP 192.168.1.105.41150 > 239.255.255.250.1900: UDP, length 121

user@psme1:~$ sudo tcpdump -ni any host 192.168.1.135 -ttttt [sudo] password for user: tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on any, link-type LINUX_SLL (Linux cooked), capture size 262144 bytes 00:00:00.000000 ARP, Request who-has 192.168.1.1 tell 192.168.1.135, length 28 00:00:00.999996 ARP, Request who-has 192.168.1.1 tell 192.168.1.135, length 28 00:00:02.000064 IP 192.168.1.135 > 192.168.1.135: ICMP host 192.168.1.1 unreachable, length 84 00:00:02.000071 IP 192.168.1.135 > 192.168.1.135: ICMP host 192.168.1.1 unreachable, length 84 00:00:02.000072 IP 192.168.1.135 > 192.168.1.135: ICMP host 192.168.1.1 unreachable, length 68 00:00:04.007690 ARP, Request who-has 192.168.1.1 tell 192.168.1.135, length 28 00:00:05.003991 ARP, Request who-has 192.168.1.1 tell 192.168.1.135, length 28 00:00:06.003996 ARP, Request who-has 192.168.1.1 tell 192.168.1.135, length 28 00:00:07.004058 IP 192.168.1.135 > 192.168.1.135: ICMP host 192.168.1.1 unreachable, length 84 00:00:07.004063 IP 192.168.1.135 > 192.168.1.135: ICMP host 192.168.1.1 unreachable, length 84 00:00:07.004065 IP 192.168.1.135 > 192.168.1.135: ICMP host 192.168.1.1 unreachable, length 68 00:00:09.012826 ARP, Request who-has 192.168.1.1 tell 192.168.1.135, length 28 00:00:10.012029 ARP, Request who-has 192.168.1.1 tell 192.168.1.135, length 28 00:00:11.011970 ARP, Request who-has 192.168.1.1 tell 192.168.1.135, length 28 00:00:12.012055 IP 192.168.1.135 > 192.168.1.135: ICMP host 192.168.1.1 unreachable, length 84 00:00:12.012061 IP 192.168.1.135 > 192.168.1.135: ICMP host 192.168.1.1 unreachable, length 84 00:00:12.012062 IP 192.168.1.135 > 192.168.1.135: ICMP host 192.168.1.1 unreachable, length 68 00:00:14.018037 ARP, Request who-has 192.168.1.1 tell 192.168.1.135, length 28 00:00:15.015989 ARP, Request who-has 192.168.1.1 tell 192.168.1.135, length 28 00:00:16.016003 ARP, Request who-has 192.168.1.1 tell 192.168.1.135, length 28 00:00:17.016077 IP 192.168.1.135 > 192.168.1.135: ICMP host 192.168.1.1 unreachable, length 84 00:00:19.023599 ARP, Request who-has 192.168.1.1 tell 192.168.1.135, length 28 00:00:20.020060 ARP, Request who-has 192.168.1.1 tell 192.168.1.135, length 28 00:00:21.019993 ARP, Request who-has 192.168.1.1 tell 192.168.1.135, length 28 00:00:22.020013 IP 192.168.1.135 > 192.168.1.135: ICMP host 192.168.1.1 unreachable, length 84 00:00:24.779228 ARP, Request who-has 192.168.1.1 tell 192.168.1.135, length 28 00:00:25.776005 ARP, Request who-has 192.168.1.1 tell 192.168.1.135, length 28 00:00:26.775983 ARP, Request who-has 192.168.1.1 tell 192.168.1.135, length 28 00:00:27.776033 IP 192.168.1.135 > 192.168.1.135: ICMP host 192.168.1.1 unreachable, length 68 00:00:27.776037 IP 192.168.1.135 > 192.168.1.135: ICMP host 192.168.1.1 unreachable, length 68 00:00:27.776038 IP 192.168.1.135 > 192.168.1.135: ICMP host 192.168.1.1 unreachable, length 78 00:00:29.784949 ARP, Request who-has 192.168.1.1 tell 192.168.1.135, length 28 00:00:30.783951 ARP, Request who-has 192.168.1.1 tell 192.168.1.135, length 28 00:00:31.784010 ARP, Request who-has 192.168.1.1 tell 192.168.1.135, length 28 00:00:32.784289 IP 192.168.1.135 > 192.168.1.135: ICMP host 192.168.1.1 unreachable, length 68 00:00:32.784303 IP 192.168.1.135 > 192.168.1.135: ICMP host 192.168.1.1 unreachable, length 68 00:00:32.784304 IP 192.168.1.135 > 192.168.1.135: ICMP host 192.168.1.1 unreachable, length 78 00:00:34.789826 ARP, Request who-has 192.168.1.1 tell 192.168.1.135, length 28 00:00:35.787952 ARP, Request who-has 192.168.1.1 tell 192.168.1.135, length 28 00:00:36.787995 ARP, Request who-has 192.168.1.1 tell 192.168.1.135, length 28 00:00:37.788033 IP 192.168.1.135 > 192.168.1.135: ICMP host 192.168.1.1 unreachable, length 68 00:00:37.788040 IP 192.168.1.135 > 192.168.1.135: ICMP host 192.168.1.1 unreachable, length 68 00:00:37.788041 IP 192.168.1.135 > 192.168.1.135: ICMP host 192.168.1.1 unreachable, length 78 00:00:39.794897 ARP, Request who-has 192.168.1.1 tell 192.168.1.135, length 28 00:00:40.792043 ARP, Request who-has 192.168.1.1 tell 192.168.1.135, length 28 00:00:41.792004 ARP, Request who-has 192.168.1.1 tell 192.168.1.135, length 28 00:00:42.792028 IP 192.168.1.135 > 192.168.1.135: ICMP host 192.168.1.1 unreachable, length 68 00:00:42.792035 IP 192.168.1.135 > 192.168.1.135: ICMP host 192.168.1.1 unreachable, length 68 00:00:42.792036 IP 192.168.1.135 > 192.168.1.135: ICMP host 192.168.1.1 unreachable, length 78

[housemic]

Dear intel, on 2018-01-24, I installed PSME Mock (node js simulator) in PODM No.1 (in the same server), and PSME Mock screen display -Running SSDP discovery and log file - /var/log/pod-manager/pod-manager/pod-manager-services-detection have the PSME Mock record - 2018-01-19 11:56:22,472 [EE-ManagedScheduledExecutorService-TasksExecutor-Thread-2] INFO c.i.p.d.e.ServiceDetectionListenerImpl - Service {URI=https://192.168.1.136:8443/redfish/v1/, type=PSME, UUID=3ddcdcb8-fb16-11e7-8a1f-774dbb7e1223} detected 2018-01-19 12:02:46,752 [EE-ManagedScheduledExecutorService-TasksExecutor-Thread-8] INFO c.i.p.d.e.ServiceDetectionListenerImpl - Service {URI=https://192.168.1.105:8443/redfish/v1/, type=PSME, UUID=80330acc-f9d3-11e7-aef4-27af4715432f} detected 2018-01-24 17:43:10,026 [EE-ManagedScheduledExecutorService-TasksExecutor-Thread-1] INFO c.i.p.d.e.ServiceDetectionListenerImpl - Service {URI=http://127.0.0.1:9443/redfish/v1, type=PSME, UUID=fc500510-00ea-11e8-82a9-fd7409e6577e} detected 2018-01-24 17:43:17,973 [EE-ManagedScheduledExecutorService-TasksExecutor-Thread-7] INFO c.i.p.d.e.ServiceDetectionListenerImpl - Service {URI=http://127.0.0.1:9443/redfish/v1, type=PSME, UUID=fc500510-00ea-11e8-82a9-fd7409e6577e} detected

Today I run the PODM in a server and run PSME compute simulator in the other server, but PODM do not find the PSME, Is the issue related to PSME REST Server SSDP function fail ? thank you.

[RobertCMa]

Hi @housemic ,

Some questions will like to clarify the situation.

1/ Please check the listening port on PSME simulator and see if ssdp is running/listening on this system. It can take use of the command like "netstat -plu" & "netstat -plnu"

2/ Do you have another psme-compute sled (not the PSME simulator) in the same network which can respond to the SSDP discover ?

[housemic]

Dear RobertCMa, Response 1 : executed netstat in the following

Response 2 : currently I modify PSME compute agent code, it can send standard IPMI command (ex : Get Device ID) to Purley BMC (AST2500), but the BMC do not support IPMI MDR commands, so PSME compute agent can not find the BMC.

Could you help the question ? thank you - Question 1 - if I run PSME REST Server and PSME compute agent Simulator, Do They not support SSDP feature ? thank you. House

[RobertCMa]

Hi @housemic ,

From the screen capture, it can see that SSDP listening socket is created successfully. It will be good to add some debug logs to check on the IP binding and received packet handling in the \Simulators\node-ssdp\lib\index.js

Like: 1/ _allowWildcards in SSDP.prototype._respondToSearch 2/ ip (referred to the package.json) in SSDP.prototype._init

In the meanwhile, the last Q2 is trying to clarify if SSDP is working properly in that network environment. Is any system supporting SSDP able to respond to the SSDP request ? If not, let's check on the debug log above for more information.

[housemic]

Dear RobertCMa,

1. I am tracking code in index.js. Could you need me to add debug messages in these location ? and dump message to log ?

   1/ _allowWildcards in SSDP.prototype._respondToSearch 2/ ip (referred to the package.json) in SSDP.prototype._init

2. I installed a new PODM (No.3 server) and PSME Mock, and confirm that after PSME Mock running, log file - /var/log/pod-manager/pod-manager/pod-manager-services-detection have the PSME Mock record.

3. I found a new Problem / Question , and create a new issue - Question - PODM wildfly fail - 404-Not Found - after run PSME Mock and can not recovery #57

thank you House

[RobertCMa]

Hi @housemic,

As we can see that the listening socket was created successfully, it's a wonder that how the service is binding on the socket and how the received M search request packet is handled/processed for further action. These two functions just caught my eyes to clarify the puzzles. If you find any suspicious functions, it's certainly helpful to add logs to clarify the situation.

[housemic]

Dear RobertCMa, thanks your suggestion, but currently to modify PSME Mock code and PSME REST server code is difficult for me and need lots of time.

I have 2 environments - (1). SSDP can not work on - PODM + PSME REST Server + PSME Compute simulator, I can not found PSME service in /var/log/pod-manager/pod-manager/pod-manager-services-detection

(2). SSDP works on - PODM + PSME Mock I can found PSME service in /var/log/pod-manager/pod-manager/pod-manager-services-detection

by above result, I think that PSME REST server and PSME compute simulator maybe have limitation, so SSDP can not work ? or there are SSDP issue in them ?

and Could you have more directions to check ? for example - Could you build a NEW Environment like this - PODM + PSME REST Server + PSME Compute simulator, their IP address was assigned OK by switch hardware. and do not add psme service in : /tmp/services.list https://:8443/redfish/v1 psme

Could you help to check SSDP is normal or not ? thank you House

[RobertCMa]

Hi @housemic,

As below tcpdump, the simulator (10.5.250.60) can respond to the SSDP discovery from two PODM [10.5.251.20 / 10.5.250.25]

10.5.250.60.1900 > 10.5.251.20.51420: UDP, length 320
10.5.250.60.1900 > 10.5.251.20.51420: UDP, length 320
10.5.250.60.1900 > 10.5.251.20.51420: UDP, length 320
10.5.250.60.1900 > 10.5.251.20.51420: UDP, length 320

10.5.250.60.1900 > 10.5.250.25.55402: UDP, length 320
10.5.250.60.1900 > 10.5.250.25.55402: UDP, length 320
10.5.250.60.1900 > 10.5.250.25.55402: UDP, length 320
10.5.250.60.1900 > 10.5.250.25.55402: UDP, length 320

One configuration may need to be adjusted in "package.json", like the ip mask fitting up for your environment "ip": "^1.1.4"

After that modification and restart the simulator, it should be able to see the SSDP response.

However, one thing needs to be reminded. As simulator is created for test purpose, it has not considered every scenario. It's suggested to keep the simulator usage in the same system as PODM for in-band communication.

[housemic]

Dear RobertCMa, thank you, Could you help the questions ?

Question 1 - if my PODM IP address is - 192.168.1.105, and PSME IP is 192.168.1.135, How do I change the setting of - "ip": "^1.1.4"

---

Question 2 - package.json are in /RSD/Simulators/.../ for example - /RSD/Simulators/node-ssdp/package.json. this is PSME Mock (node js simulator).

but I use PSME compute agent Simulator, it is in /RSD/PSME/sgent-simulator/compute/ and it is not the same as PSME Mock, I have SSDP issue that is - when I run PSME compute agent Simulator and PSME REST Server, but use tcpdump, not found the PSME compute agent simulator respond to the SSDP discovery. Could you help to setup the environment to check ? thank you House

[RobertCMa]

Hi @housemic,

You can try ip": "^192.168" or other to fit into your network environment.

The Compute Simulator should not be related to SSDP. PSME Compute Agent Simulator is used for Deep Discovery feature and exposing the host system asset data (specifics in section 2.2 of PSME User Guide and 6.3 of PODM User Guide). We have verified SSDP on the compute system (PSME REST + Compute agent) without seeing issues. It's suggested to check if SSDP is turned on in psme-rest-server and respond the notification in announce-interval. The detail can refer to "configuration_schema.json"

[housemic]

Dear RobertCMa , I modify package.json in /home/user/IntelRSD/intelRSD-2-2/Simulators/node-ssdp/ ip": "^192.168"

and startup ./psme-compute-simulator ../../agent-simulator/compute/configuration.json but PODM still not found the hardware assets of psme-compute-simulator.

Question 2 - configuration_schema.json is in /home/user/IntelRSD/intelRSD-2-2/PSME/agent/compute/ not found in /home/user/IntelRSD/intelRSD-2-2/Simulators/ not found in /home/user/IntelRSD/intelRSD-2-2/PSME/agent-simulator/compute/

and What items I can check in configuration_schema.json ? thank you House

---

the following are my detail steps,

find package.json in PSME

sudo gedit /home/user/IntelRSD/intelRSD-2-2/Simulators/node-ssdp/package.json

"ip": "^1.1.4"

change to

"ip": "^192.168"

---

cd /home/user/IntelRSD/intelRSD-2-2/PSME/build/bin

sudo ./psme-rest-server ../../application/configuration.json

---

cd /home/user/IntelRSD/intelRSD-2-2/PSME/build/bin

sudo ./psme-compute-simulator ../../agent-simulator/compute/configuration.json

---

https://localhost:8443/redfish/v1

https://localhost:8443/redfish/v1/Systems

[RobertCMa]

Hi @housemic,

That modification is for Simulator only when you run the PSME Mock (node js simulator). The Compute Agent Simulator is used for other purpose with PSME Rest, which was described in (specifics in section 2.2 of PSME User Guide). Back to the SSDP in node js simulator, will like to clarify if it works after the modification.

For the SSDP service in psme-rest-server, it can check the psme-rest-server-configuration.json about "ssdp-service". The configuration, like announce-interval-seconds, is referring to "configuration_schema.json"

[housemic]

Dear RobertCMa , Now PODM can find PSME simulator success.

I enable PODM DHCP (uBuntu isc-dhcp-server), and startup intel PSME REST server and PSME compute simulator to test, pass. the issue can be closed, thank you. Notes : do not use Switch / HUB hardware DHCP function. House

[RobertCMa]

Good to hear that the issues are clarified and passed. Let's conclude this.