HP NonStop Networking Overview HP Part Number: 529874-009 Published: August 2012 Edition: J06.04 and all subsequent J-series RVUs, H06.
© Copyright 2009, 2010, 2011, 2012 Hewlett-Packard Development Company, L.P. Legal Notice Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license. The information contained herein is subject to change without notice.
Contents About This Guide..........................................................................................5 Supported Release Version Updates (RVUs)..................................................................................5 Intended Audience....................................................................................................................5 New and Changed Information in This Edition..............................................................................
Figures 1 2 3 4 5 6 7 8 9 10 11 12 Integrity NonStop System P-Switch Connection to a NonStop S-Series I/O Enclosure...................8 Integrity NonStop BladeSystem Connection to a NonStop S-Series I/O Enclosure.......................9 Connecting Legacy Systems With Integrity NonStop Systems Running H-Series RVUs.................12 Connecting Legacy Systems With Integrity NonStop BladeSystems..........................................14 Transparent Network Scalability, Multiple Hosts.......................
About This Guide This manual provides an overview of networking on the J-series and H-series release version updates (RVUs) on Integrity NonStop systems, including supported hardware configurations and migration and planning information. Supported Release Version Updates (RVUs) This manual supports J06.04 and all subsequent J-series RVUs and H06.16 and all subsequent H-series RVUs until otherwise indicated in a replacement publication.
Related Information To plan for networking on Integrity NonStop systems, use this manual.
1 Networking on Integrity NonStop Systems This section provides a high-level overview of networking on H-series and J-series RVUs on Integrity NonStop systems.
Products for Connecting to NonStop I/O Enclosures You can use other networking hardware products by connecting some Integrity NonStop system models to a NonStop S-series I/O enclosure that has IOMF2 components installed. This connection is made from the system processor switch (p-switch) or ServerNet switch. This option is not available on the NonStop NS2000 series system or NonStop NS2100 system.
Figure 2 Integrity NonStop BladeSystem Connection to a NonStop S-Series I/O Enclosure Legacy NonStop S-series networking I/O adapters supported through the NonStop S-series I/O enclosure include: • GESA, FESA, and E4SA (Ethernet adapters) • TRSA (Token-ring) • ATM3SA (Asynchronous Transfer Mode 3–port ServerNet adapter) NOTE: Support for these products is only for legacy adapters already existing in the environment. These products have reached end-of-sale status.
On NonStop NS-series systems, ServerNet wide area network (SWAN) concentrators use TCP/IP to connect through the G4SA or CLIM, through Ethernet ports in the VIO enclosure or through other Ethernet adapters in a NonStop S-series I/O enclosure. On NonStop BladeSystems, SWAN concentrators connect through the CLIM or G4SA. On NonStop NS2000, NS2100, and NS2200-series systems, SWAN concentrators connect through the VIO. AWAN is not supported on NonStop NS2000, NS2100, and NonStop NS2200-series systems.
• NonStop TCP/IPv6 • NonStop TCP/IP (conventional) • OSI/AS • OSI/FTAM • OSI/MHS • OSI/TS • Port Access Method (PAM) • QIO • ServerNet LAN Systems Access (SLSA) • SNAX High Level Support (SNAX/HLS) • SNAX/XF (includes SNAX/APN functionality) • SNMP • Spooler • Spooler FastP Network Print Processes • Spooler Plus • TELSERV • TN3270e • TR3271 Tributary Access Method • Wide area network (WAN) subsystem Networking software available only on G-series RVUs includes: • 6100 T
NOTE: Not all Integrity NonStop systems support ServerNet clustering. For more information, see the planning guide for your system model (for example, the Integrity NonStop NS16000 Series Planning Guide). Figure 3 shows interoperability between multiple NonStop systems.
NonStop Integrity Systems can support these clustering topologies: Cluster Topology Systems Supported Hardware Required BladeCluster Solution NonStop BladeSystems Refer to the BladeCluster Solution Manual. Mixed NonStop BladeSystems and NS16000 series systems Refer to the BladeCluster Solution Manual. Connection to 6780 ServerNet Cluster comprised of NonStop BladeSystems, NS16000 series systems, NS14000 series systems, or NonStop S-series systems Refer to the BladeCluster Solution Manual.
Figure 4 Connecting Legacy Systems With Integrity NonStop BladeSystems What’s Unique About Networking on Integrity NonStop Systems If you are new to the Integrity NonStop systems, you should be aware of differences between its networking architecture and solutions and the architecture of other platforms, including other NonStop systems.
to the Integrity NonStop system, but the hardware for that legacy networking technology is accessible only by connecting to a NonStop S-series I/O enclosure. (See Networking Software Products Available on H-Series and J-Series RVUs (page 10) for a list of all networking products available.) Integrity NonStop System Networking Compared to Other Platforms The Integrity NonStop system clustering technology makes it possible for the system to appear as multiple hosts.
For the purposes of this discussion we make the distinction between: • Network Scalability • Application Scalability Network Scalability Network scalability refers to the use of multiple physical interfaces to accommodate bandwidth requirements for which a single network interface is insufficient. You can achieve network scalability by having multiple network interfaces on multiple hosts or by having a multi-homed host (a single system that has multiple network interfaces).
subnet. All clients requesting an IP address on that subnet are returned the IP address of the host that is also on that subnet. • Clients on subnet 192.168.1.1 requesting the IP address of MyCompany.com receive the IP address of Webserver 1. • Clients on subnet 192.168.2.1 requesting the IP address of MyCompany.com receive the IP address of Webserver 2. • Clients on subnet 192.168.3.1 requesting the IP address of MyCompany.com receive the IP address of Webserver 3. • Clients on subnet 192.168.4.
In a NonStop system environment, those n hosts can be consolidated onto a single system and have access to a shared database on that same system. Returning to the Nonstop TCP/IPv6 and CIP subsystems' architectural features of allowing multiple server processes to bind to a shared port and IP address, the web server process in can run 16 copies of itself and access a shared database while presenting a single image to the network.
Fault-Tolerance and Scalability on the NonStop System When you have configured for scalability, the failure of one or more processors does not impact the availability in any way: • Availability of an application is not impacted by a failed processor because the application process is replicated.
Figure 8 Conventional TCP/IP: Data From the Interface is Restricted to Applications Using the Associated Process In NonStop TCP/IPv6, if you do not configure the environment to use logical-network partitioning and in CIP if you did not configure the environment to use Providers, applications using those subsystems cannot determine which interface they will get because the interface is no longer associated with the TCP/IP process used by the applications.
Persistence The NonStop TCP/IPv6 and CIP products on the Integrity NonStop systems participate in the system configuration database as generic processes and can be managed by the persistence manager. If you add their processes as generic processes, they start automatically upon system reload and restore their stored and subordinate objects. For more information about configuring NonStop TCP/IPv6 to be persistent, see the TCP/IPv6 Configuration and Management Manual.
Table 1 Comparison of NonStop TCP/IP Products (continued) Adapters Conventional TCP/IP NonStop TCP/IPv6 Cluster I/O Protocols (CIP) • MFIOB • MFIOB CLIM • IOAM+E4SA • IOAM+E4SA • IOAM+FESA • IOAM+FESA • IOAM+GESA • IOAM+GESA • IOAM+G4SA • IOAM+G4SA • VIO+G4SA • VIO+G4SA • IOAM+ATM3SA • IOAM+TRSA • IOAM+CCSA 22 Maximum Adapters 4 60 48 Maximum Hardware Interfaces 4 per process pair 240 240 IP versions IPv4 IPv4, IPv6 IPv4, IPv6 SCTP Support No No Yes Protocol Stack Ancestr
Table 1 Comparison of NonStop TCP/IP Products (continued) Configuration Commands Conventional TCP/IP NonStop TCP/IPv6 Cluster I/O Protocols (CIP) • $user-assigned name through SCF • $ZZTCP through SCF • $ZZCIP through SCF • $ZZLAN through SCF • climconfig through CLIMCMD • $ZZLAN through SCF • TCP6SAM through SCF • CIPSAM through SCF • NonStop I/O Essentials plug-in to HP Systems Insight Manager (SIM) Compatible Commands in SAM 1 N/A • ABORT • ABORT • INFO • INFO • LISTOPENS • • NAMES
2 Networking Concepts This section provides a brief overview of networking concepts including the following topics: • Address Resolution • Name Resolution • Allocation of IP Addresses (page 25) • Routers (page 26) • Switches (page 26) • Gateways (page 26) • Network Interface Name (page 26) • Firewalls (page 27) • “IP Security (IPSec)” (page 27) • IPv6 (page 28) For more detailed information about Internet concepts and services, see the TCP/IP Configuration and Management Manual.
For procedures about configuring the various subsystems to use the HOSTS file, see the: • TCP/IPv6 Configuration and Management Manual • TCP/IP Configuration and Management Manual • Cluster I/O Protocols (CIP) Configuration and Management Manual Domain Name System (DNS) The Internet has created an ever-increasing demand for IP addresses, and IP address management has presented a challenging task for administrators.
Routers A router is a device that has multiple network interfaces and transfers Internet Protocol (IP) packets from one network or subnet to another within an internetwork. (In many IP-related documents, this device is also referred to as a “gateway.”) Routing protocols find a path between network nodes. If multiple paths exist for a given protocol, the shorter paths are usually chosen. Each protocol has a cost or a metric that it applies to each path.
IPv6: 3ffe:1200:190:2:21f:29ff:fe57:182e IPv6: fe80::21f:29ff:fe57:182e eth4 UP UP IPv6: 3ffe:1200:190:1:21f:29ff:fe57:182f IPv6: 3ffe:1200:190:2:21f2:9ff:fe57:182f IPv6: fe80::21f:29ff:fe57:182f eth3 UP UP IPv6: 3ffe:1200:190:1:21f:29ff:fe57:182c IPv6: 3ffe:1200:190:2:21f:29ff:fe57:182c IPv6: fe80::21f:29ff:fe57:182c eth2 UP UP IPv6: 3ffe:1200:190:2:21f:29ff:fe57:182d IPv6: 3ffe:1200:190:1:21f:29ff:fe57:182d IPv6: fe80::21f:29ff:fe57:182d . . .
ESP headers since it is used to choose the right SA to be applied for decrypting and authenticating the packet. In unicast transmissions, the SPI is normally chosen by the destination node and sent back to the sender when the communication is set up. In multicast transmissions, the SPI must be common to all the members of the multicast group. Each node must be able to correctly identify the right SA by combining the SPI with the multicast address.
3 Planning for Migrating Networking Solutions to H-Series and J-Series RVUs This section provides examples of product-suite requirements for some legacy networking solutions on H-series and J-series RVUs. These examples were chosen to show the general placement and relationships of legacy networking software and hardware in the H-series and J-series RVU environments. In addition, this section provides guidance for finding Internet application documentation.
Figure 10 Products for SNAX/XF The manuals you might need for running SNAX/XF include: 30 • Cluster I/O Protocols (CIP) Configuration and Management Manual • Ethernet Adapter Installation and Support Guide • Gigabit Ethernet 4-Port Adapter Installation and Support Guide • Gigabit Ethernet Adapter Installation and Support Guide • Introduction to Networking for HP NonStop S-Series Servers • LAN Configuration and Management Manual • Planning guide for your system • Port Access Method (PAM) Co
X.25 Communications For X.25 communications on H-series or J-series RVUs, you need: • X25AM • CIP, NonStop TCP/IP, or NonStop TCP/IPv6 • WAN subsystem • SLSA (for NonStop TCP/IP and NonStop TCP/IPv6 only) • CLIM, G4SA, E4SA, FESA, or GESA • A SWAN or SWAN 2 Concentrator • NonStop S-series I/O enclosure (optional, used for TRSA, E4SA, FESA, or GESA connectivity) Figure 11 Products for X.25 Communications for H-Series or J-Series RVUs The manuals you might need for X.
• WAN Subsystem Configuration and Management Manual • X25AM Configuration and Management Manual Asynchronous Wide Area Network (AWAN) Connectivity If you want AWAN connectivity on the H-series or J-series RVU you need: • Telserv • FASTPTCP print processes • CIP, NonStop TCP/IP, NonStop TCP/IPv6 • SLSA (for NonStop TCP/IP or NonStop TCP/IPv6 only) • CLIM or G4SA • AWAN 3886 server • NonStop S-series I/O enclosure (optional, used for TRSA, E4SA, FESA, or GESA connectivity) NOTE: AWAN is not
• LAN Configuration and Management Manual • LAN Configuration and Management Manual • Spooler FASTP Network Print Processes Manual • TCP/IP Configuration and Management Manual • TCP/IPv6 Configuration and Management Manual • Telserv Manual Selecting Your TCP/IP Product HP recommends using NonStop TCP/IPv6 or CIP for your TCP/IP needs because of the superior processing power of the parallel architecture that underlies these products.
Table 3 Internet Application Product Documentation 34 Product Manuals BEA WebLogic Server for the NonStop Server HP NonStop Server Platform Guide for WebLogic Server 8.
Index Symbols 6100 TINET Multi-PT Supervisor-PDG, 11 6100 UTS-40 Multi-PT Supervisor, 11 6100 UTS-40 Multi-PT Tributary, 11 6100 VIP Multi-PT Supervisor, 11 6763 Common Communication ServerNet adapter (CCSA-2) , 21 A Address resolution, 24 AM3270 Access Method, 10 Asynchronous Terminals and Printer Processes, 10 ATP6100 WANPRINT, 10 B BEA WebLogic Server, 34 BladeCluster Solution, 10, 12 C CCSA-2, 21 CLIM, 7 CLuster I/O Module (CLIM), 7 Cluster I/O Protocols (CIP), 10 D DNS overview, 25 scaling, 16 supp
overview, 8 Scalability for DNS, 16 ServerNet LAN Systems Access (SLSA), 11 SNAX High Level Support (SNAX/HLS), 11 SNAX/APN, 11 SNAX/XF, 11 SNMP, 11 Spooler, 11 Spooler FastP Network Print Processes, 11 Spooler Plus, 11 Systems Insight Manager (SIM), 23 T TANDEM NBT NETBIOS, 11 TCP, TANDEM NBT NETBIOS, 11 TCP/IP (conventional), 11 TELSERV, 11 TN3270e, 11 Token ring ServerNet adapter, 21 TR3271 Tributary Access Method, 11 TRSA, 21 V Versatile I/O (VIO) enclosure, 9 W White paper, CLIM strategies, 20 Wide
