Files
napalm-amt/tests/fixtures/dmt-wsman-messages/CIM_MediaAccessDevice.pull.xml
T
christianmanivong 0052ba7884 feat: Intel AMT driver over WS-Management (0.1.0)
An `amt` driver (napalm_amt.AmtDriver), a ManagementControllerDriver for the
management controller of Intel vPro machines, with its own lean WS-Management
client (requests + ElementTree, HTTP Digest, ports 16992/16993).

It reads the machine's identity, hardware with the SMBIOS system UUID, firmware
(AMT with build, BIOS), power state and the hardware event log, reports what AMT
listens on (plain HTTP or TLS, KVM incl. port 5900, IDE-R), and switches the
machine's power. AMT cannot be reset over WS-Management, so there is no
reboot_host. Discovery recognises AMT by its ports and its Server header.

Tested against Intel's published AMT 12 recordings (go-wsman-messages,
Apache-2.0, see NOTICE). `python -m napalm_amt.record` records a real AMT
read-only; the first test devices are two Lenovo ThinkCentre M910x.
2026-10-18 14:55:32 +02:00

54 lines
3.0 KiB
XML

<?xml version="1.0" encoding="UTF-8"?>
<a:Envelope xmlns:a="http://www.w3.org/2003/05/soap-envelope"
xmlns:b="http://schemas.xmlsoap.org/ws/2004/08/addressing"
xmlns:c="http://schemas.dmtf.org/wbem/wsman/1/wsman.xsd"
xmlns:d="http://schemas.xmlsoap.org/ws/2005/02/trust"
xmlns:e="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"
xmlns:f="http://schemas.dmtf.org/wbem/wsman/1/cimbinding.xsd"
xmlns:g="http://schemas.xmlsoap.org/ws/2004/09/enumeration"
xmlns:h="http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_MediaAccessDevice"
xmlns:i="http://schemas.dmtf.org/wbem/wscim/1/common"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<a:Header>
<b:To>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</b:To>
<b:RelatesTo>1</b:RelatesTo>
<b:Action a:mustUnderstand="true">http://schemas.xmlsoap.org/ws/2004/09/enumeration/PullResponse</b:Action>
<b:MessageID>uuid:00000000-8086-8086-8086-000000000E72</b:MessageID>
<c:ResourceURI>http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_MediaAccessDevice</c:ResourceURI>
</a:Header>
<a:Body>
<g:PullResponse>
<g:Items>
<h:CIM_MediaAccessDevice>
<h:Capabilities>4</h:Capabilities>
<h:CreationClassName>CIM_MediaAccessDevice</h:CreationClassName>
<h:DeviceID>MEDIA DEV 0</h:DeviceID>
<h:ElementName>Managed System Media Access Device</h:ElementName>
<h:EnabledDefault>2</h:EnabledDefault>
<h:EnabledState>0</h:EnabledState>
<h:MaxMediaSize>960197124</h:MaxMediaSize>
<h:OperationalStatus>0</h:OperationalStatus>
<h:RequestedState>12</h:RequestedState>
<h:Security>2</h:Security>
<h:SystemCreationClassName>CIM_ComputerSystem</h:SystemCreationClassName>
<h:SystemName>ManagedSystem</h:SystemName>
</h:CIM_MediaAccessDevice>
<h:CIM_MediaAccessDevice>
<h:Capabilities>4</h:Capabilities>
<h:CreationClassName>CIM_MediaAccessDevice</h:CreationClassName>
<h:DeviceID>MEDIA DEV 1</h:DeviceID>
<h:ElementName>Managed System Media Access Device</h:ElementName>
<h:EnabledDefault>2</h:EnabledDefault>
<h:EnabledState>0</h:EnabledState>
<h:MaxMediaSize>500107862</h:MaxMediaSize>
<h:OperationalStatus>0</h:OperationalStatus>
<h:RequestedState>12</h:RequestedState>
<h:Security>2</h:Security>
<h:SystemCreationClassName>CIM_ComputerSystem</h:SystemCreationClassName>
<h:SystemName>ManagedSystem</h:SystemName>
</h:CIM_MediaAccessDevice>
</g:Items>
<g:EndOfSequence></g:EndOfSequence>
</g:PullResponse>
</a:Body>
</a:Envelope>