There are several reasons why customer is unable to see payloads:
- payloads Payloads capturing is not supported
- payloads Payloads are not being sentpayloads
- Payloads capture in DPOD has errors
- Payloads are sent but filtered out in DPOD
- payloads Payloads fully collected and still not appears
...
2) MPGW objects from IFG firware 7.5.2 and DPOD 1.0.2 but only text payloads.
If you are expecting to see payload and your are trying to see it in a non suported object type and/or versions please upgrade or submit an RFE.
Payloads are not being sent
...
- Verify yo enabled WS-M capturing by perform the following steps S-M setup for device , WS-M Subscriptions for All Domains (Optional) as they appear in Adding Monitored Devices
- Verify in IDG that subscriptions are created . In the expected domain - navigate to Status → Web Service → WSM Agent Status (see in blue). You should have 1 Active subscriber of polled type (in red). if payloads were captured than you will be able to see it as Records seen. more statiscs data can be seen on WSM
- If records seen is 0 than you might not have running transaction
- If Active subsriberes is 1 and number of polled subscribers is 0 also than you have not perform the or follow the next step
- Check WS-M Agent in IDG is configured correctly :
- We expect Agent to be enabled and Capture mode to be set to all
- If your WS-M agent in IDG is enabled , subscription is created from DPOD by performing step WS-M Subscriptions for All Domains (Optional) and recors seen counter is increasing by any running transaction than you should expect the payload to arrive to DPOD WS-M Agent
Payloads are sent but filtered out
Payload are send to DPOD WS-M agent . in this phase we make sure they are arrived and proessed .
- Make sure DPOD WS-M agent is up and running - Check System Services Status with the CLI . It should be up and running.
- Make sure DPOD WS-M agent is green. this means that keep alive message are processed. perform tasks appears at Check System Status Using the Web Console
Go to WS-M logs and see if there any exceptions. logs shouls be accessed using Telnet . path is /logs/wsmAgents/<Agent-name>/. this are good log records:
11/10/XXXX 08:26:03,477- INFO o.m.a.f.h.NHttpFileServer [I/O-dispatch-2] wsmHttpSource1 Incoming entity content (bytes): 2908. ← an actual arrive payload
11/10/XXXX 08:26:10,166- INFO o.m.a.f.h.NHttpFileServer [I/O-dispatch-3] wsmHttpSource1 Incoming entity content (bytes): 2220. ← size 2220 means usually keep alive messageIf size