Test the PeSIT Connections

Edit online

About this task

To verify that the engine can receive and initiate communications sessions, you have to establish a connection between a Sterling Connect:Express PNODE and the engine, initiate a session from the engine to the Sterling Connect:Express SNODE in the trusted zone, and review the Secure Proxy log for the results.

This procedure enables you to verify that the engine can:
  • Establish a Sterling Connect:Express session between a PNODE and Secure Proxy
  • Initiate a session to a Sterling Connect:Express SNODE on behalf of the Sterling Connect:Express PNODE connection

To verify the communications sessions:

Procedure

  1. View the secureproxy.log.
  2. Confirm that the sessions were established, as shown in the following example. 
    23 avr. 2010 13:39:37,459 INFO  [ProxyNearScheduler-Thread-9] 
sys.ADAPTER.PeSITClearAdapter - protocol=pesit sessid=124048677744407 
SSP103I Session started from Peer Address: PNODE1.company/10.20.10.80 
23 avr. 2010 13:39:37,459 INFO  [ProxyNearScheduler-Thread-9] 
sys.ADAPTER.PeSITClearAdapter - protocol=pesit sessid=120000000007 
SSP104I Session Proceeding after Node match: INSERVER 
23 avr. 2010 13:39:37,459 INFO  [ProxyNearScheduler-Thread-9] 
sys.ADAPTER.PeSITClearAdapter - protocol=pesit sessid=120000000007 
SSE1831I Authentication mechanism: no authentication. 
23 avr. 2010 13:39:37,475 INFO  [ProxyNearScheduler-Thread-3] 
sys.ADAPTER.PeSITClearAdapter - protocol=pesit sessid=120000000007 
SSE0103I Connecting to server.  
23 avr. 2010 13:39:37,475 INFO  [ProxyNearScheduler-Thread-3] 
sys.ADAPTER.PeSITClearAdapter - protocol=pesit sessid=120000000007 
SSP0237I Attempting outbound connection with 
10.20.129.3/InetSocketAddress-host:/10.20.129.3-port:4004 ... 
23 avr. 2010 13:39:37,631 INFO  [ProxyFarScheduler-Thread-12] 
>  :  Bytes Received: 646 [at:  7.398711524695777E-4 MBPS] 
>  Bytes Sent: 402 [at:  4.604151753758053E-4 MBPS] 
>  
>  :  Bytes Received: 402 [at:  4.710017574692443E-4 MBPS] 
>  Bytes Sent: 646 [at:  7.568834212067955E-4 MBPS] 
>  23 avr. 2010 13:39:44,459 INFO  [ProxyFarScheduler-Thread-14] 
sys.ADAPTER.PeSITClearAdapter - protocol=pesit sessid=12400000000744407 
SSE0112I Session ended.

    If your session was unsuccessful, review the log information to determine the likely cause of the failure and the corrective action to take.

    Additional PeSIT configuration options support the following features:
    • Define alternate nodes for failover support
    • Record an error message or shutdown a connection based on protocol errors
    • Block PeSIT command from a PNODE