Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Ipdiscover ip/mac send from agent not found in table netmap #443

Open
bud4 opened this issue Oct 10, 2023 · 2 comments
Open

Ipdiscover ip/mac send from agent not found in table netmap #443

bud4 opened this issue Oct 10, 2023 · 2 comments

Comments

@bud4
Copy link

bud4 commented Oct 10, 2023 •
edited

General informations

Operating system :
CentOS Stream 8
ocsreport: 2.12.0
MariaDB Server version 10.3.28-MariaDB
Apache/2.4.37 (CentOS Stream) OpenSSL/1.1.1k mod_perl/2.0.12 Perl/v5.26.3
PHP 7.3.33
agent: OCS-NG_WINDOWS_AGENT_v2.10.0.0

Problem's description

ipDiscover agent send ip 172.30.18.254 @MAC:70:DF:2F:00:9F:BF NAME:172.30.18.254
not show in ipdidcovery inventory. Not found record in netmap table.
================= TRACE STOP ===============
AGENT => Prolog successfully sent
AGENT => Prolog Frequency set to 9 hour(s)
AGENT => Inventory on startup option set to 1
AGENT => Inventory required
AGENT => Launching hardware and software checks
INVENTORY => Loading Download history
INVENTORY => Adding Download Package <1690554445> to report
INVENTORY => Adding Download Package <1690554548> to report
INVENTORY => WMI FLAG MODE is set to <WBEM_FLAG_RETURN_WBEM_COMPLETE>
INVENTORY => Logged on user ID is <a.vivaldi>
INVENTORY => Operating System is <Microsoft Windows 10 Pro 10.0.19045 >, description <>
INVENTORY => Operating System uses 64 bits memory address width
INVENTORY => Computer domain or workgroup is <aoup.lan>
INVENTORY => User domain is <>
INVENTORY => System Manufacturer , System Model , System S/N , Bios Manufacturer <American Megatrends International, LLC.>, Bios Date <23/02/2022>, Bios Version <1.A1>, Motherboard Manufacturer <Micro-Star International Co., Ltd.>, Motherboard Model <>, Motherboard S/N <07D1412_KC1C102872>
INVENTORY => 1 processor(s) AMD Ryzen 3 PRO 4350G with Radeon Graphics [4 core(s) x86_64] at 3801 MHz
INVENTORY => OS Memory 7574 MB, OS Swap size 8790 MB
INVENTORY => 2 memory slot(s) found
INVENTORY => 3 input device(s) found
INVENTORY => 19 system port(s) found
INVENTORY => 14 system slot(s) found
INVENTORY => 6 system controller(s) found
INVENTORY => 3 storage peripheral(s) found
INVENTORY => 2 sound device(s) found
WARNING *** INVENTORY => Failed to retrieve modems
INVENTORY => 6 network adapter(s) found
INVENTORY => 5 system printer(s) found
INVENTORY => 1 video adapter(s) found
INVENTORY => 1 system monitor(s) found
INVENTORY => Default IPv4 address is <172.30.18.118>
INVENTORY => Default Gateway address is <172.30.18.254>
INVENTORY => Default DNS address is <10.166.64.2 / 10.166.64.3 / 10.166.67.2>
INVENTORY => Registered company <>, registered owner , Product ID <00330-54...>
INVENTORY => Product key <DDP3Q-N8...>
INVENTORY => 199 software found
INVENTORY => Computer/VM UUID is
INVENTORY => Computer seems to be Microsoft virtual host
INVENTORY => System Memory set to 8192 (instead of 7574)
INVENTORY => Reading last inventory state
AGENT => Communication Server asks for Registry Query
REGISTRY => Executing query asked by server
REGISTRY => 10 query successfully executed
AGENT => Communication Server asks for IpDiscover
IPDISCOVER => Scanning to detect IPv4 enabled hosts for network <172.30.18.0> with <100> ms between each request
IPDISCOVER => Computer found @IPv4:172.30.18.3 @MAC:2C:F0:5D:D6:7D:15 NAME:affgen-18-03.aoup.lan
IPDISCOVER => Computer found @IPv4:172.30.18.13 @MAC:2C:F0:5D:D6:86:9E NAME:Per-18-13.aoup.lan
IPDISCOVER => Computer found @IPv4:172.30.18.15 @MAC:E4:54:E8:AC:71:4C NAME:PER-18-15
IPDISCOVER => Computer found @IPv4:172.30.18.16 @MAC:9C:93:4E:BC:15:4D NAME:XC-BC154D
IPDISCOVER => Computer found @IPv4:172.30.18.17 @MAC:50:9A:4C:31:C8:4C NAME:PER-18-17
IPDISCOVER => Computer found @IPv4:172.30.18.19 @MAC:8C:EC:4B:45:87:52 NAME:PER18-19
IPDISCOVER => Computer found @IPv4:172.30.18.21 @MAC:2C:F0:5D:D6:86:77 NAME:PER-18-21.aoup.lan
IPDISCOVER => Computer found @IPv4:172.30.18.24 @MAC:1C:66:6D:8C:72:3D NAME:Per-18-24.aoup.lan
IPDISCOVER => Computer found @IPv4:172.30.18.25 @MAC:9C:93:4E:BC:0B:F7 NAME:XC-BC0BF7
IPDISCOVER => Computer found @IPv4:172.30.18.26 @MAC:2C:F0:5D:D6:7A:AC NAME:Per-18-26.aoup.lan
IPDISCOVER => Computer found @IPv4:172.30.18.27 @MAC:8C:EC:4B:45:ED:6D NAME:PER-18-27
IPDISCOVER => Computer found @IPv4:172.30.18.29 @MAC:2C:F0:5D:D6:86:7E NAME:Per-18-29.aoup.lan
IPDISCOVER => Computer found @IPv4:172.30.18.31 @MAC:9C:93:4E:BC:10:F8 NAME:XC-BC10F8
IPDISCOVER => Computer found @IPv4:172.30.18.33 @MAC:2C:F0:5D:D6:75:44 NAME:Per-18-33.aoup.lan
IPDISCOVER => Computer found @IPv4:172.30.18.35 @MAC:00:17:C8:8E:10:53 NAME:NM8E1053
IPDISCOVER => Computer found @IPv4:172.30.18.36 @MAC:78:E7:D1:86:68:B1 NAME:PER1836
IPDISCOVER => Computer found @IPv4:172.30.18.38 @MAC:9C:93:4E:BC:0F:33 NAME:XC-BC0F33
IPDISCOVER => Computer found @IPv4:172.30.18.39 @MAC:E4:54:E8:AE:64:3D NAME:PER-18-39
IPDISCOVER => Computer found @IPv4:172.30.18.41 @MAC:2C:F0:5D:D6:7F:5B NAME:Per-18-41.aoup.lan
IPDISCOVER => Computer found @IPv4:172.30.18.42 @MAC:00:23:24:A9:F3:26 NAME:Per-18-42.aoup.lan
IPDISCOVER => Computer found @IPv4:172.30.18.44 @MAC:48:4D:7E:B9:54:9D NAME:Per-18-44.aoup.lan
IPDISCOVER => Computer found @IPv4:172.30.18.43 @MAC:2C:F0:5D:8A:37:F1 NAME:Per-18-43.aoup.lan
IPDISCOVER => Computer found @IPv4:172.30.18.45 @MAC:6C:4B:90:63:ED:19 NAME:PER-18-45
IPDISCOVER => Computer found @IPv4:172.30.18.47 @MAC:8C:EC:4B:45:7F:A4 NAME:PER-18-47
IPDISCOVER => Computer found @IPv4:172.30.18.6 @MAC:00:90:1E:FC:02:74 NAME:172.30.18.6
IPDISCOVER => Computer found @IPv4:172.30.18.50 @MAC:2C:F0:5D:D6:76:04 NAME:Per-18-50.aoup.lan
IPDISCOVER => Computer found @IPv4:172.30.18.52 @MAC:2C:F0:5D:D6:7B:C1 NAME:Per-18-21.aoup.lan
IPDISCOVER => Computer found @IPv4:172.30.18.53 @MAC:2C:F0:5D:D6:79:B4 NAME:Per-18-53.aoup.lan
IPDISCOVER => Computer found @IPv4:172.30.18.54 @MAC:48:4D:7E:B8:BF:87 NAME:PER-18-54
IPDISCOVER => Computer found @IPv4:172.30.18.57 @MAC:2C:F0:5D:D6:86:89 NAME:Per-18-57.aoup.lan
IPDISCOVER => Computer found @IPv4:172.30.18.60 @MAC:B4:B5:2F:DB:C4:4C NAME:STADAI-18-60
IPDISCOVER => Computer found @IPv4:172.30.18.61 @MAC:9C:93:4E:BC:15:0D NAME:XC-BC150D
IPDISCOVER => Computer found @IPv4:172.30.18.66 @MAC:78:E7:D1:81:31:D0 NAME:PER-18-66
IPDISCOVER => Computer found @IPv4:172.30.18.56 @MAC:2C:F0:5D:D6:86:AC NAME:PER-18-56.aoup.lan
IPDISCOVER => Computer found @IPv4:172.30.18.67 @MAC:78:E7:D1:81:31:6F NAME:PER-18-67
IPDISCOVER => Computer found @IPv4:172.30.18.68 @MAC:2C:F0:5D:D6:86:A7 NAME:PER-18-68.aoup.lan
IPDISCOVER => Computer found @IPv4:172.30.18.69 @MAC:00:17:C8:8C:2D:46 NAME:NM8C2D46
IPDISCOVER => Computer found @IPv4:172.30.18.72 @MAC:00:17:C8:8C:2B:98 NAME:NM8C2B98
IPDISCOVER => Computer found @IPv4:172.30.18.64 @MAC:2C:F0:5D:D6:79:27 NAME:Per-30-18-64.aoup.lan
IPDISCOVER => Computer found @IPv4:172.30.18.76 @MAC:00:D8:61:43:BD:5E NAME:PER-18-76
IPDISCOVER => Computer found @IPv4:172.30.18.34 @MAC:50:9A:4C:2F:06:C8 NAME:172.30.18.34
IPDISCOVER => Computer found @IPv4:172.30.18.79 @MAC:6C:4B:90:62:82:C0 NAME:PER-18-79
IPDISCOVER => Computer found @IPv4:172.30.18.37 @MAC:E4:54:E8:AE:64:1A NAME:172.30.18.37
IPDISCOVER => Computer found @IPv4:172.30.18.81 @MAC:2C:F0:5D:D6:7D:53 NAME:PER-18-81.aoup.lan
IPDISCOVER => Computer found @IPv4:172.30.18.82 @MAC:78:E7:D1:83:39:F6 NAME:PER-18-63
IPDISCOVER => Computer found @IPv4:172.30.18.84 @MAC:9C:93:4E:BC:11:61 NAME:XC-BC1161
IPDISCOVER => Computer found @IPv4:172.30.18.87 @MAC:A8:A1:59:60:36:FC NAME:Rag-18-87.aoup.lan
IPDISCOVER => Computer found @IPv4:172.30.18.89 @MAC:00:17:C8:8C:2B:F3 NAME:NM8C2BF3
IPDISCOVER => Computer found @IPv4:172.30.18.93 @MAC:2C:F0:5D:D6:7E:AD NAME:RAG-18-93.aoup.lan
IPDISCOVER => Computer found @IPv4:172.30.18.94 @MAC:2C:F0:5D:D6:75:9D NAME:Rag-18-94.aoup.lan
IPDISCOVER => Computer found @IPv4:172.30.18.99 @MAC:2C:F0:5D:D6:75:DC NAME:Rag-18-99.aoup.lan
IPDISCOVER => Computer found @IPv4:172.30.18.100 @MAC:2C:F0:5D:D6:7E:7D NAME:RAG-18-100.aoup.lan
IPDISCOVER => Computer found @IPv4:172.30.18.103 @MAC:00:23:24:A9:E6:00 NAME:Rag-18-103.aoup.lan
IPDISCOVER => Computer found @IPv4:172.30.18.105 @MAC:2C:F0:5D:D6:7A:06 NAME:Rag-18-105.aoup.lan
IPDISCOVER => Computer found @IPv4:172.30.18.110 @MAC:2C:F0:5D:D6:7E:A9 NAME:RAG-18-110.aoup.lan
IPDISCOVER => Computer found @IPv4:172.30.18.101 @MAC:E4:54:E8:AB:75:11 NAME:RAG-18-101
IPDISCOVER => Computer found @IPv4:172.30.18.112 @MAC:2C:F0:5D:D6:7C:1D NAME:Rag-18-112.aoup.lan
IPDISCOVER => Computer found @IPv4:172.30.18.113 @MAC:00:17:C8:8C:2C:16 NAME:NM8C2C16
IPDISCOVER => Computer found @IPv4:172.30.18.114 @MAC:9C:93:4E:BC:10:32 NAME:XC-BC1032
IPDISCOVER => Computer found @IPv4:172.30.18.117 @MAC:9C:93:4E:BC:1A:B5 NAME:XC-BC1AB5
IPDISCOVER => Computer found @IPv4:172.30.18.118 @MAC:2C:F0:5D:D6:7E:64 NAME:RAG-18-118.aoup.lan
IPDISCOVER => Computer found @IPv4:172.30.18.122 @MAC:64:51:06:4F:EF:8C NAME:RAG-18-122.aoup.lan
IPDISCOVER => Computer found @IPv4:172.30.18.123 @MAC:2C:F0:5D:D6:7E:61 NAME:RAG-18-123.aoup.lan
IPDISCOVER => Computer found @IPv4:172.30.18.127 @MAC:48:4D:7E:B9:58:F2 NAME:RETRIB-18-127
IPDISCOVER => Computer found @IPv4:172.30.18.130 @MAC:2C:F0:5D:D6:86:A3 NAME:RETRIB-18-130.aoup.lan
IPDISCOVER => Computer found @IPv4:172.30.18.133 @MAC:2C:F0:5D:D6:75:FC NAME:Retrib-18-133.aoup.lan
IPDISCOVER => Computer found @IPv4:172.30.18.135 @MAC:2C:F0:5D:D6:7E:68 NAME:Retrib-18-135.aoup.lan
IPDISCOVER => Computer found @IPv4:172.30.18.125 @MAC:50:9A:4C:31:47:D7 NAME:RAG-18-125
IPDISCOVER => Computer found @IPv4:172.30.18.136 @MAC:6C:4B:90:62:83:51 NAME:RETRIB-18-136
IPDISCOVER => Computer found @IPv4:172.30.18.137 @MAC:2C:F0:5D:D6:79:E2 NAME:Retrib-18-137.aoup.lan
IPDISCOVER => Computer found @IPv4:172.30.18.139 @MAC:6C:4B:90:62:84:89 NAME:RETRIB-18-139
IPDISCOVER => Computer found @IPv4:172.30.18.141 @MAC:00:17:C8:8A:C0:C6 NAME:NM8AC0C6
IPDISCOVER => Computer found @IPv4:172.30.18.150 @MAC:4C:CC:6A:79:66:34 NAME:RETRIB-18-150
IPDISCOVER => Computer found @IPv4:172.30.18.152 @MAC:2C:F0:5D:D6:7E:E9 NAME:RETRIB-18-152.aoup.lan
IPDISCOVER => Computer found @IPv4:172.30.18.153 @MAC:00:17:C8:8C:2D:A2 NAME:NM8C2DA2
IPDISCOVER => Computer found @IPv4:172.30.18.158 @MAC:2C:F0:5D:D6:75:C2 NAME:Retrib-18-158.aoup.lan
IPDISCOVER => Computer found @IPv4:172.30.18.160 @MAC:2C:F0:5D:D6:7E:6F NAME:Retrib-18-160.aoup.lan
IPDISCOVER => Computer found @IPv4:172.30.18.164 @MAC:00:25:B3:14:8B:49 NAME:RETRIB-18-164
IPDISCOVER => Computer found @IPv4:172.30.18.166 @MAC:E4:54:E8:B6:1C:E3 NAME:NUCCORINISI-AOP
IPDISCOVER => Computer found @IPv4:172.30.18.167 @MAC:2C:F0:5D:8A:44:E9 NAME:Stadai-18-167.aoup.lan
IPDISCOVER => Computer found @IPv4:172.30.18.168 @MAC:6C:4B:90:62:84:47 NAME:STADAI-18-168
IPDISCOVER => Computer found @IPv4:172.30.18.169 @MAC:2C:F0:5D:8A:45:05 NAME:Stadai-18-169.aoup.lan
IPDISCOVER => Computer found @IPv4:172.30.18.170 @MAC:BC:5F:F4:FB:B4:17 NAME:Rag-18-170.aoup.lan
IPDISCOVER => Computer found @IPv4:172.30.18.128 @MAC:6C:4B:90:62:83:4E NAME:172.30.18.128
IPDISCOVER => Computer found @IPv4:172.30.18.171 @MAC:2C:F0:5D:D6:7C:08 NAME:LEX-18-171.aoup.lan
IPDISCOVER => Computer found @IPv4:172.30.18.173 @MAC:9C:93:4E:BC:0F:9B NAME:XC-BC0F9B
IPDISCOVER => Computer found @IPv4:172.30.18.184 @MAC:2C:F0:5D:D6:82:EB NAME:Per-18-184.aoup.lan
IPDISCOVER => Computer found @IPv4:172.30.18.187 @MAC:2C:F0:5D:D6:85:46 NAME:P-RAFFAELLI.aoup.lan
IPDISCOVER => Computer found @IPv4:172.30.18.188 @MAC:E4:54:E8:AC:70:1F NAME:PER-18-188
IPDISCOVER => Computer found @IPv4:172.30.18.189 @MAC:E4:54:E8:AE:63:4E NAME:Per-18-189
IPDISCOVER => Computer found @IPv4:172.30.18.190 @MAC:8C:EC:4B:45:E8:E2 NAME:PER-18-190
IPDISCOVER => Computer found @IPv4:172.30.18.191 @MAC:2C:F0:5D:D6:76:D1 NAME:AFFGEN-18-191.aoup.lan
IPDISCOVER => Computer found @IPv4:172.30.18.193 @MAC:2C:F0:5D:D6:80:40 NAME:AFFGEN-18-193.aoup.lan
IPDISCOVER => Computer found @IPv4:172.30.18.194 @MAC:2C:F0:5D:D6:86:04 NAME:AFFGEN-18-194.aoup.lan
IPDISCOVER => Computer found @IPv4:172.30.18.200 @MAC:2C:F0:5D:D6:85:BD NAME:Affgen-18-200.aoup.lan
IPDISCOVER => Computer found @IPv4:172.30.18.202 @MAC:78:E7:D1:86:52:E6 NAME:AFFGEN-18-202
IPDISCOVER => Computer found @IPv4:172.30.18.163 @MAC:54:E1:40:7D:1A:78 NAME:172.30.18.163
IPDISCOVER => Computer found @IPv4:172.30.18.165 @MAC:50:9A:4C:2F:52:95 NAME:172.30.18.165
IPDISCOVER => Computer found @IPv4:172.30.18.208 @MAC:00:17:C8:8C:28:63 NAME:NM8C2863
IPDISCOVER => Computer found @IPv4:172.30.18.214 @MAC:00:23:24:A9:E6:75 NAME:AFFGEN-18-214
IPDISCOVER => Computer found @IPv4:172.30.18.216 @MAC:00:17:C8:8D:E2:A4 NAME:NM8DE2A4
IPDISCOVER => Computer found @IPv4:172.30.18.217 @MAC:78:E7:D1:81:30:D9 NAME:AFFGEN-18-217
IPDISCOVER => Computer found @IPv4:172.30.18.204 @MAC:D0:50:99:53:8A:F1 NAME:Affgen-18-204
IPDISCOVER => Computer found @IPv4:172.30.18.221 @MAC:2C:F0:5D:D6:80:42 NAME:AFFGEN-18-221.aoup.lan
IPDISCOVER => Computer found @IPv4:172.30.18.224 @MAC:50:9A:4C:19:A7:20 NAME:Affgen-18-224.aoup.lan
IPDISCOVER => Computer found @IPv4:172.30.18.174 @MAC:78:8C:77:AA:7A:56 NAME:172.30.18.174
IPDISCOVER => Computer found @IPv4:172.30.18.227 @MAC:2C:F0:5D:D6:85:B8 NAME:Affgen-18-227.aoup.lan
IPDISCOVER => Computer found @IPv4:172.30.18.234 @MAC:2C:F0:5D:D6:80:E7 NAME:Affgen-18-234.aoup.lan
IPDISCOVER => Computer found @IPv4:172.30.18.235 @MAC:2C:F0:5D:D6:80:2B NAME:AFFGEN-18-235.aoup.lan
IPDISCOVER => Computer found @IPv4:172.30.18.236 @MAC:2C:F0:5D:D6:86:22 NAME:AFFGEN-18-236.aoup.lan
IPDISCOVER => Computer found @IPv4:172.30.18.237 @MAC:2C:F0:5D:D6:86:05 NAME:AFFGEN-18-237.aoup.lan
IPDISCOVER => Computer found @IPv4:172.30.18.242 @MAC:4C:CC:6A:79:5D:74 NAME:Per-18-242.aoup.lan
IPDISCOVER => Computer found @IPv4:172.30.18.243 @MAC:4C:CC:6A:79:5E:57 NAME:Per-18-243.aoup.lan
IPDISCOVER => Computer found @IPv4:172.30.18.245 @MAC:8C:EC:4B:45:87:61 NAME:PER-18-245
IPDISCOVER => Computer found @IPv4:172.30.18.251 @MAC:4C:CC:6A:79:6B:F3 NAME:PER-18-251
IPDISCOVER => Computer found @IPv4:172.30.18.226 @MAC:6C:4B:90:63:E6:A4 NAME:172.30.18.226
IPDISCOVER => Computer found @IPv4:172.30.18.240 @MAC:8C:EC:4B:45:E8:E2 NAME:Per-18-190
IPDISCOVER => Computer found @IPv4:172.30.18.254 @MAC:70:DF:2F:00:9F:BF NAME:172.30.18.254
IPDISCOVER => Waited 4140 ms for the threads to die
IPDISCOVER => NETWORK scan finished, 118 hosts found, 255 scanned
EXECUTABLE PLUGIN => Searching for VBS script(s) in folder <C:\Program Files (x86)\OCS Inventory Agent\plugins>
EXECUTABLE PLUGIN => Found executable plugin <driverslist.vbs>
================= TRACE START ===============

================= TRACE STOP ===============
EXECUTABLE PLUGIN => Plugin <driverslist.vbs> executed successfully
EXECUTABLE PLUGIN => Found executable plugin <listprinters.vbs>
================= TRACE START ===============

================= TRACE STOP ===============
EXECUTABLE PLUGIN => Plugin <listprinters.vbs> executed successfully
EXECUTABLE PLUGIN => Found executable plugin <oracle.vbs>
================= TRACE START ===============

================= TRACE STOP ===============
WARNING *** EXECUTABLE PLUGIN => Plugin <C:\Program Files (x86)\OCS Inventory Agent\plugins\oracle.vbs> does not produce any output
EXECUTABLE PLUGIN => Found executable plugin <osinstall.vbs>
================= TRACE START ===============

================= TRACE STOP ===============
EXECUTABLE PLUGIN => Plugin <osinstall.vbs> executed successfully
EXECUTABLE PLUGIN => Found executable plugin <runningprocess.vbs>
================= TRACE START ===============

================= TRACE STOP ===============
EXECUTABLE PLUGIN => Plugin <runningprocess.vbs> executed successfully
EXECUTABLE PLUGIN => Found executable plugin <scheduledtasks.vbs>
================= TRACE START ===============

================= TRACE STOP ===============
EXECUTABLE PLUGIN => Plugin <scheduledtasks.vbs> executed successfully
EXECUTABLE PLUGIN => Found executable plugin <security.vbs>
================= TRACE START ===============

================= TRACE STOP ===============
EXECUTABLE PLUGIN => Plugin <security.vbs> executed successfully
EXECUTABLE PLUGIN => Found executable plugin <sharedfolders.vbs>
================= TRACE START ===============

================= TRACE STOP ===============
EXECUTABLE PLUGIN => Plugin <sharedfolders.vbs> executed successfully
EXECUTABLE PLUGIN => Found executable plugin <uptime.vbs>
================= TRACE START ===============

================= TRACE STOP ===============
EXECUTABLE PLUGIN => Plugin <uptime.vbs> executed successfully
EXECUTABLE PLUGIN => Searching for PS1 script(s) in folder <C:\Program Files (x86)\OCS Inventory Agent\plugins>
EXECUTABLE PLUGIN => Found executable plugin <defaultwindowsapp.ps1>
================= TRACE START ===============

================= TRACE STOP ===============
EXECUTABLE PLUGIN => Plugin <defaultwindowsapp.ps1> executed successfully
EXECUTABLE PLUGIN => Found executable plugin <gpresult.ps1>
================= TRACE START ===============

================= TRACE STOP ===============
EXECUTABLE PLUGIN => Plugin <gpresult.ps1> executed successfully
EXECUTABLE PLUGIN => Found executable plugin <Saas.ps1>
================= TRACE START ===============

================= TRACE STOP ===============
WARNING *** EXECUTABLE PLUGIN => Plugin <C:\Program Files (x86)\OCS Inventory Agent\plugins\Saas.ps1> does not produce any output
EXECUTABLE PLUGIN => Found executable plugin <services.ps1>
================= TRACE START ===============

================= TRACE STOP ===============
EXECUTABLE PLUGIN => Plugin <services.ps1> executed successfully
EXECUTABLE PLUGIN => Found executable plugin <winupdate.ps1>
================= TRACE START ===============

================= TRACE STOP ===============
EXECUTABLE PLUGIN => Plugin <winupdate.ps1> executed successfully
EXECUTABLE PLUGIN => Found executable plugin <winusers.ps1>
================= TRACE START ===============

================= TRACE STOP ===============
EXECUTABLE PLUGIN => Plugin <winusers.ps1> executed successfully
AGENT => Sending Inventory
INVENTORY => Checking last inventory state
INVENTORY => Logical drives inventory state changed
INVENTORY => Software inventory state changed
INVENTORY => Inventory changed since last run
INVENTORY => Generating XML document with Device properties
INVENTORY => XML Update BIOS
INVENTORY => XML Update 1 CPU(s)
INVENTORY => XML Update 2 Memory Slot(s)
INVENTORY => XML Update 3 Input Device(s)
INVENTORY => XML Update 19 System Port(s)
INVENTORY => XML Update 6 System Controller(s)
INVENTORY => XML Update 14 System Slot(s)
INVENTORY => XML Update 2 Sound Device(s)
INVENTORY => XML Update 3 Storage Peripheral(s)
INVENTORY => XML Update 5 Logical Drive(s)
INVENTORY => XML Update 0 Modem(s)
INVENTORY => XML Update 6 Network Adapter(s)
INVENTORY => XML Update 1 Video Adapter(s)
INVENTORY => XML Update 1 Monitor(s)
INVENTORY => XML Update 5 Printer(s)
INVENTORY => XML Update 200 Software
INVENTORY => XML Update 18 Registry Value(s)
INVENTORY => XML Update Administrative Information(s)
INVENTORY => XML Update common Device properties
COM SERVER => Initializing cURL library for sendRequest
COM SERVER => Using cURL without server authentication
COM SERVER => Disabling cURL proxy support
COM SERVER => Enabling cURL SSL server validation support using CA Bundle <cacert.pem>
COM SERVER => Sending HTTP Post request to URL https://ocs.aoup.lan/ocsinventory
COM SERVER => HTTP Post response received <HTTP Status Code #200>
COM SERVER => Cleaning cURL library
================= TRACE START ===============

NO_ACCOUNT_UPDATE

================= TRACE STOP ===============
AGENT => Inventory successfully sent
INVENTORY => Writing new inventory state
AGENT => Communication Server asked for Package Download
DOWNLOAD => Package history file successfully cleaned for duplicate IDs
DOWNLOAD => Download and setup tool successfully started
AGENT => Unloading communication provider
AGENT => Unloading plug-in(s)
AGENT => Execution duration: 00:03:59.

immagine
@Lea9250
Copy link
Contributor

Lea9250 commented Dec 11, 2023

Hi @bud4,

Can you generate the inventory locally and check within the file generated if the IpDiscover section did return this IP to the server ?

Regards,
Léa

@bud4
Copy link
Author

bud4 commented Dec 15, 2023 •
edited

Hi @Lea9250 , as you can see from the previously attached debug log, the ocs agent sends the IP to the server which is not present in the netmap table.
IPDISCOVER => Computer found @IPv4:172.30.18.254 @MAC:70:DF:2F:00:9F:BF NAME:172.30.18.254
Furthermore we have 93 subnets of the type 172.3X.XX.0/24. In all these subnets the gateway is the IP address with final number 254. For example 172.31.74.0/24 has the gateway 172.31.74.254.
Well, although there are OCS agents in all 93 subnets in the netmap table there are only 50 addresses with a final of 254.
As you can see from the result of the following sql queries:
*** number of subnet of type 172.3%.xxx.xx/24
SELECT count(DISTINCT substr(IP,1,10)) FROM netmap where ip like '172.3%';
93
**** number of ip end in 254 (gateway)
SELECT count( DISTINCT IP) FROM netmap where ip like '172.3%.254%';
50
#*************
an example of a missing ip(gateway) is 172.30.18.254 although there are 4 ipdiscover agents in its subnet.
Below is the snmp scan result to show that it is present
immagine

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@bud4 @Lea9250