Cisco - CiscoWorks Blue Maps Version 3.0

The major new functionality in Maps 3.0 is improved performance to monitor and manage large SNA environments. The host discovery and status update propagation processes for large SNA environments have been significantly improved.

Customers told us that there were two things that they liked about the combination of Maps and SNA View. First, they liked to be able to get maps of the network, which showed the relationships between all of the Systems Network Architecture (SNA) routers. This functionality is provided by Maps. Second, they liked the ability to display an end-to-end view of the SNA sessions that crossed over the networks that Maps displayed.

But our customers said they needed more. They had multiple types of SNA networks. In addition to the Data-Link Switching (DLSw), remote source-route bridging (RSRB), and Advanced Peer-to-Peer Networking (APPN) networks that the Version 1.2 of SNA View could monitor, they had traditional subarea SNA and new TN3270 networks to worry about. This is where SNA View excels. SNA View provides end-to-end session views of traditional subarea SNA sessions, DLSw, RSRB, and APPN sessions, as well as TN3270 sessions passing through Cisco TN3270 Servers. In short, Maps displays maps, while SNA View displays views of SNA sessions.

Do I have to install code on the mainframe? If so, what is it, and how big is it?

Yes. Maps and SNA View have components that run on the mainframe, as well as on the UNIX servers. There are two pieces on the mainframe: a VTAM exit, named ISTEXCCS, and a started task that takes the information from this exit and transports it to the UNIX workstation. The information from VTAM is correlated with the information from the router network to provide the end-to-end session correlation for SNA sessions.

Yes. Maps will work but some of its functionality will be limited. Maps will create the topographical maps from information gathered from the routers. The Dependency View will not be able to correlate router information with PU and LU names.

The amount of mainframe resources used by the VTAM exit is insignificant. The amount of mainframe resources required to transfer this information to the UNIX workstation is difficult to quantify. It depends on the number of physical units (PUs) in the network and how much filtering is done at the mainframe. In general, the impact on the mainframe is minimal, except during the initial PU discovery process.

Which operating system and network management platforms does Maps Version 3.0 support?

Table 1 lists the primary operating system and platform support. Cisco IOS" requirements and a complete list of the Maps Version 3.0 operating system and platform support is included in the SNA View and Maps Version 3.0 data sheets.

Table 1 Maps 3.0 Operating System and Platform Support
Operating System	Platform (Optional)
Solaris 2.5.1 and 2.6	SunNet Manager 2.2.3 and 2.3, and HP OpenView 5.01, 5.03, and 6.0
HP-UX 11.0	HP OpenView 5.01, 5.03, and 6.0
AIX 4.21 and 4.3.1	Tivoli NetView for AIX 4.1 and 5.0

No, Maps 3.0 runs only on Solaris, HP-UX, and AIX. SNA View, however, has been ported to Windows NT.

No. Versions prior to Maps 2.1 required a network management system and CiscoWorks for UNIX. Version 3.0 of Maps does not require any of these other products, although it will integrate with these products if they are available.

Because Maps 3.0 does not run on Windows NT, there is no capability of launching Maps 3.0 from SNA View 3.0 on Windows NT.

Does Maps provide management of SNA resources that are not running through the routed network?

No. Maps develops a model of the DLSw, RSRB, and APPN connections by querying the MIBs within the Cisco routers. It does not manage SNA connections that do not flow through the routers.

SNA View allows users to control SNA resources that are defined to any VTAM. SNA View displays the session connectivity for any VTAM resource, with expanded capabilities for resources that traverse Cisco routers using DLSw, APPN, or RSRB, and TN3270 sessions that utilize the Cisco TN3270 Server for the Channel Interface Processor (CIP) or Channel Port Adapter (CPA).

Maps has a Web front end. Can I use just the Web-enabled version for management of my consolidated SNA and IP network?

Yes and no. Many customers have found that utilizing the Web version allows them to get to all of the information that is required for problem determination and isolation. Also, the tabular nature of the Web-based interface has been extremely useful for customers with large routed environments. However, this capability is limited to display only and is staticćnot dynamicćinformation.

At this point, we have not determined an upper boundary on the numbers of PUs or LUs that can be managed. However, in our test lab, Cisco has managed up to 10,000 PUs without any problems or defects. New performance enhancements in Maps 3.0 significantly improve discovery and status propagation.

Internetwork Status Monitor is a mainframe application that runs as a Tivoli NetView for OS/390 or SOLVE:Netmaster application. It provides a mainframe operator with device-level management of routers. Maps shows the interrelationship of Cisco devices that provide SNA connectivity over an IP network.

Yes. Maps provides extensive information about the connectivity of Cisco devices that support APPN networks.

The Web-based interfaces of Maps can be launched from within CiscoWorks2000's tool menus, as part of the Cisco Management Connection.

What type of Cisco service and support is provided for CiscoWorks Blue Maps Version 3.0?

CiscoWorks Blue Maps Version 3.0 is covered by the Cisco Software Application Support (SAS) program. SAS includes 7x24 access to the Cisco Technical Assistance Center (TAC), Cisco Connection Online (CCO) privileges, and software maintenance updates (within a single release). Contact your local sales office for further information.

Table Of Contents

Q & A

CiscoWorks Blue Maps Version 3.0