Share This:

I am pleased to announce the release of BMC MainView for IP 3.3. This release enhances the monitoring and diagnostic capability for network monitoring and management. Enhanced trace analysis and packet trace improvements will provide better diagnostics and formatting for unwanted events. You will have more confidence to isolate problems with these new Trace enhancements, being able to pinpoint more issues like dropped packets and retransmits in a formatted and easy to read display.

 

New features and functions are:

-    -   The packet traces enhancements are:

     o   Start packet traces at a specific time.

     o   Save packet headers in the MainView for IP history files.

     o   Write packet traces in sniffer format, making the file accessible to sniffer products like Wireshark from Wireshark Foundation.

     o   Save packet traces when the MainView for IP product address space is recycled. 

 

-     MainView for IP now acquires two sessions with ISTPDCLU, one for the VTAM session data, and now a second session for the VTAM PIU Tracing. The VTAM PIU tracing enhancements allows the user to specify global traces for LU’s and SSCP’s, as well as PIU traces for specific named LU’s. PIU Trace data can be displayed by the VTAM session and also saved to the MainView history files when the VTAM session ends. You will be able to customize which VTAM/LU sessions are traced, and how many PIUs are kept for each session, and if they are logged to MainView history.

A VTAM PIU trace on a specific LU can be displayed, started, and stopped on any of the VTAM session views.

 

  1 .jpg

 

          The ‘DT’ command will display the VTAM PIU Trace for the VTAM session

   

2 .jpg

 

     Global PIU tracing can be started from the MVIPSAWD view. This will start PIU tracing for all VTAM sessions that have tracing enabled in the SAW Filters (The SAW Filters can be hyperlinked from the MVIPSAWD view). Note: The definition for the MainView IP VTAM application must be defined with EAS=2 and PARSESS=YES, and must be active to enable SAW data collection and PIU tracing.

 

 

3.jpg

 

4.jpg

 

 

-    The new Sysplex views show all Dynamic virtual IP addresses (VIPAs) for all the TCP/IP stacks in a sysplex. You can then drill down on each Dynamic VIPA to get more detailed information. 

 

-    MainView for IP will retrieve both OMPRoute RTTABLE and RIP data via the D TCPIP,,OMPROUTE,RIP and D TPCIP,,OMPROUTE,RTTABLE commands. The OMPRTT (and OMPRTTD) view display all of the routes in the OMPRoute main routing table.

 

     5.jpg

   The OMPRIP and OMPRIPD views display the RIP-related configuration information.

 

     6.jpg

      8.jpg

-      The Availability Monitoring (AMON) view now uses an MPD wizard to add resources, making the process easier. The existing MPD to add an AMON resource was complicated and not straightforward as to which fields needed to be entered for each type of AMON resource. The new ‘ADD’ command will no longer be entered from column 1, but must be entered from the command line.

 

     The ‘Add’ command will prompt the user for the Resource Type:

9.jpg

 


      Then after selecting ‘Next’, the required fields for that Resource Type will be requested. For example, for resource type ‘PORT’:

 

  10.jpg

 

-     MainView for IP can now act as the Primary Program Operator, and all VTAM messages will be routed to MainView for IP that were destined for the system console. The user can specify filters that will determine whether VTAM message is discarded, written to system console, or logged to MainView for IP (and logged to history). 

 

The MVIPPPOD view allows the user to configure the PPO application. The PPO interface requires a VTAM application for MainView for IP and must be active. The PPO Filters determine which VTAM messages are filtered and what action is taken. 

 

11.jpg

 

The PPO Filter table determines if the VTAM Message is logged to MainView (Log), or written to the System Console (WTO) by matching the VTAM Message number. If there is no match, the default on the MVIPPOD view is taken. The valid values are ALL (every message), NO (none), or a number 1-200 (every nth message to be processed).

 

12.jpg

 

The VTAM Messages that are logged to MainView can be displayed on the VTAMMSG view. The messages will be written to MainView history at interval time.

 

13.jpg

 

- The VTAM Session Configuration view (VTMSESSD) now shows a topology for the VTAM session.

 

For further information on MainView for IP 3.3, please visit us at www.bmc.com/mainview