|
|
|
Reason:
A Packet Analyzer request to the SOLVE SSI on LPAR P1 failed because the Packet Analyzer has no EE statistics.
System Action:
The request fails.
User Action:
If the SOLVE SSI on P1 has recently started, retry later; otherwise, check that EE is operational on P1. If EE is operational, contact Technical Support.
Reason:
You entered an invalid SORT command.
System Action:
SORT command is rejected.
User Action:
Enter SORT ? and select an option from the list.
Reason:
You issued the LOCATE command with invalid operand P1 . The connection list is sorted by local or remote address, so P1 must be an IP address or part thereof.
System Action:
None.
User Action:
Do one of the following:
Reason:
You issued the R action against a UDP connection, but the selected connection is using port P1 , which is used for EE signal traffic only. No RTPs use this connection.
System Action:
None.
User Action:
Select a different connection.
Reason:
You used the SORT ? command to present a prompt list of connection list sort fields, but did not select a sort field.
System Action:
None.
User Action:
Specify a sort field or select a field from the prompt list.
Reason:
A request to list EE UPD connections has found nothing. If the request is for a CP name, the packet analyzer has seen no EE packets to the selected CP name.
System Action:
None.
User Action:
Retry later. This may be a transient condition if the packet analyer has recently been restarted, or if it has not yet seen an RTP to the remote CP.
Reason:
From the EE UDP Connection List, you can use simple line commands to easily start, view, and manage SmartTrace packet traces.
The following SmartTrace line commands are available:
PT starts a packet trace.
PTV views the packets in the trace. (You can view packets while the trace is active.)
PTI inactivates the packet trace. (When inactivated, the trace is automatically deleted after a certain interval; save it if you want to keep it permanently.)
PTD inactivates and immediately deletes the packet trace.
An EE UDP Connection is identified by its remote and local IP address and port number. Tracing an EE UDP Connection traces all traffic for that port's priority, between the local and remote addresses.
For EE ports carrying application data (generally, local ports 12001 - 12004), the trace includes all RTP Pipes using that priority or class of service.
System Action:
A panel of optional EE trace criteria appears. A SmartTrace packet trace starts for the EE UDP Connection.
User Action:
After the trace is activated, use the PTV command to view and manage the active trace.
More About SmartTrace
To list all EE-related SmartTraces, for all resources and users, use the L option from the EE SmartTrace Menu (shortcut /EETRALL ).
More About the EE UDP Connection List
As well as packet tracing, actions are available from this list to show connection traffic, packet breakdowns, and to drill down to the specific RTP Pipes that flow over any connection. Type ? on any line, to see all available commands.
Reason:
The Packet Analyzer has determined that IPSec is used by this stack. If the list is for a specific remote address, traffic protected by IPSec has been seen for the remote address.
If the IPSec-protected traffic includes EE data, the EE connections cannot be identified by Packet Analyzer, so cannot be included in the list.
System Action:
None.
User Action:
None.
Reason:
A request to list EE UDP connections has found nothing. However, Packet Analyzer has seen IPSec traffic on this stack, and if the request is for a CP name, IPSec traffic has been seen for the remote address. If the IPSec-protected traffic includes EE data, the EE connections cannot be identified by Packet Analyzer, so cannot be included in the list.
System Action:
None.
User Action:
If IPSEC is being used for EE traffic, this option is not useful.
If IPSec is not being used, retry later. This condition can be transient if Packet Analyzer has recently been restarted or if it has not yet seen an RTP to the remote CP.
Reason:
The processing for a list of P1 UDP connections reached the implementation maximum set by the global variable &GLBL$EEUDPCOUNT.
System Action:
The list of displayed UDP connections is truncated.
User Action:
To change the displayed limit, set the global variable to a value between 1 and 10,000. The default value is 500.
Reason:
The Packet Analyzer has determined that IPSec is used by this stack. If the list is for a specific remote address, traffic protected by IPSec has been seen for the remote address.
If the IPSec-protected traffic includes EE data, the EE connections cannot be identified by Packet Analyzer, so cannot be included in the list.
System Action:
None.
User Action:
None.
Reason:
A request to list EE UPD connections has found nothing. However, Packet Analyzer has seen IPSec traffic on this stack, and if the request is for a CP name, IPSec traffic has been seen for the remote address. If the IPSec-protected traffic includes EE data, the EE connections cannot be identified by Packet Analyzer, so cannot be included in the list.
System Action:
None.
User Action:
If IPSEC is being used for EE traffic, this option is not useful.
If IPSec is not being used, retry later. This condition can be transient if Packet Analyzer has recently been restarted or if it has not yet seen an RTP to the remote CP.
Reason:
The SSI is currently running with its Packet Analyzer PALEVEL parameter set to a value other than FULL.
Packet statistics are available only when PALEVEL is FULL.
System Action:
No packet statistics are displayed.
User Action:
Check why the SSI is not running with the parameter PALEVEL=FULL.
When including Packet Analyzer functions in an SSI, it is recommended to always set the PALEVEL parameter to FULL. If you run with a level other than FULL, various IP monitoring functions will not be available.
Only use a PALEVEL other than FULL if instructed by Technical Support.
Reason:
A packet analyzer request to the SOLVE SSI failed because the SSI region cannot be contacted or does not include support for the packet analyzer. The SSID (P1) and system (P2) identify the SSI region where the request is issued. This can be the local SSI region or a remote region, possibly on another LPAR.
System Action:
The request fails.
User Action:
Do the following in the region running on P2:
Ensure that Packet Analyzer support is enabled by specifying PKTANALYZER=YES.
Also ensure that the parameters include PALEVEL=FULL
Only use a PALEVEL other than FULL if instructed by Technical Support.
Note: Only one SOLVE SSI region (per LPAR) can include support for the packet analyzer.
Reason:
A Packet Analyzer request to the SOLVE SSI on LPAR P1 failed because the Packet Analyzer is not enabled for EE processing.
System Action:
The request fails.
User Action:
Check why EE analysis is disabled on P1.
EE analysis requires Packet Analyzer version 116.01 or greater.
To detect EE traffic, these two things must be set up:
Both of these are specified as parameters in the SOLVE SSI JCL. Enter OCS command SELFTEST and look for messages similar to:
NSN101 SNANMI EPS REGISTERED, NAME=$SYS.$EE.?SYS
NSN103 0 ACTIVE SNANMI REQUEST(S), SUBTASK STATUS: STARTED
or
IPDI5201 SNANMI interface is active (via a remotely connected SSI) and IPDI52FB EE Packet Analysis enabled: stack ?STACK, port base UDP 12000
If the SNANMI interface is not active on the local or a remote SSI, see the Installation Guide.
If EE Packet Analysis is not enabled, see the Installation Guide
Make sure the EE ?STACK stack name is correct. If there are multiple TCP/IP stacks on this LPAR, only one of them will support EE.
IBM do not recommend changing the EE port base to other than 12000.
Check that EE is defined and active to VTAM on this LPAR.
Enter the VTAM command D NET,EE to display any active EE Connections.
If the SSI and Packet Analyzer are correctly set up, and this error occurs even when there are active EE connections, contact Technical Support and provide them with the output of the OCS $$SYSPRO EE command.
Reason:
A Packet Analyzer request to the SOLVE SSI on LPAR P1 failed because the Packet Analyzer has no EE statistics.
System Action:
The request fails.
User Action:
If the SOLVE SSI on P1 has recently started, retry later; otherwise, ensure that EE is operational on P1. If EE is operational, contact Technical Support.
Reason:
A request for Enterprise Extender (EE) traffic information was received but failed because the Packet Analyzer on LPAR P1 is not aware of any EE connections. The following causes are possible:
System Action:
The request fails.
User Action:
To detect EE traffic, these two things must be set up:
Both of these are specified as parameters in the SOLVE SSI JCL.
Enter the SELFTEST OCS command and look for messages similar to:
NSN101 SNANMI EPS REGISTERED, NAME=$SYS.$EE.?SYS
NSN103 0 ACTIVE SNANMI REQUEST(S), SUBTASK STATUS: STARTED
or
IPDI5201 SNANMI interface is active (via a remotely connected SSI)
IPDI52FB EE Packet Analysis enabled: stack ?STACK, port base UDP 12000
If the SNANMI interface is not active on the local or a remote SSI, see the Installation Guide.
If EE Packet Analysis is not enabled, see the Installation Guide.
Make sure the EE ?STACK stack name is correct. If there are multiple TCP/IP stacks on this LPAR, only one of them will support EE.
IBM does not recommend changing the EE port base to other than 12000.
Enter the D NET,EE VTAM command to display any active EE Connections.
If the SSI and Packet Analyzer are set up correctly, IPSec is not used, and this error occurs even when there are active EE connections.
For assistance, contact Technical Support. Provide the output of the $$SYSPRO EE OCS command.
Reason:
A request to aggregate the cumulative EE statistics from the Packet Analyzer EEI records failed with a run-time error.
System Action:
The request fails. Additional run-time error details are written to the activity log under the same message ID.
User Action:
Browse the activity log for the error details.
Retry the request.
For assistance, contact Technical Support. Provide them with the text of the EEPKG05 messages from the log.
Reason:
A request to return the EE traffic statistics for the timeframe P1 cannot be satisfied because the timeframe has not passed.
For EE statistics collection, the SSI region and this NetMaster region must both be active for the whole of the timeframe.
For the HOUR timeframe, there has not been a whole hour since this region and its SSI have been collecting EE statistics.
For the DAY timeframe, there has not been a whole day since this region and its SSI have been collecting EE statistics.
System Action:
The next best timeframe is used.
For the DAY timeframe, the HOUR data is returned (if available).
For the HOUR timeframe, the cumulative total since the SSI and NetMaster regions were both started is returned.
User Action:
None.
The HOUR timeframe will be available after the SSI and NetMaster regions have collected statistics for at least one full clock hour.
The DAY timeframe will be available after the SSI and NetMaster regions have collected statistics for at least one full calendar day.
Reason:
The EE traffic statistics collector process could not gather the required statistics because of the reason stated in message P1.
System Action:
Statistics collection is rescheduled for the next interval.
User Action:
Determine the cause stated in the encapsulated message P1.
Reason:
EE traffic statistics collection and performance attribute sampling cannot be performed by this region because the SNANMI SSI function does not appear to be supported by any SSI known to LPAR P1 .
EE traffic statistics and performance attribute values come from a combination of Packet Analyzer data, and from the z/OS Communications Server SNA Network Management Interface.
A local or remotely connected SSI can provide SNANMI functions to a region. This is controlled by the SSI parameter SNANMI=YES
System Action:
Requests for EE traffic statistics fail.
Performance data attribute sampling may fail.
User Action:
Do the following on this region:
1. Issue the OCS command
SSI STATUS
If messages NSN101 and NSN103 appear, then the local SSI on this LPAR is providing the SNANMI functions to this region. Retry the request.
2. Issue the OCS command
SH EPS SERV=$SYS.$EE.?sysname
where ?sysname is the system name of this LPAR.
If message N99755 appears, then a remotely connected SSI is providing the SNANMI functions to this region.
Retry the request.
3. If the local SSI is active, but neither the local nor a remote SSI is providing the SNANMI functions, you may need to add the SNANMI keyword to the SSI parameters, and possible also enable SNANMI processing in VTAM.
See the product installation instructions.
| Copyright © 2012 CA. All rights reserved. |
|