Leveraging DataPower XI50z and Sysplex. Section 9249 August 10,2011 STG Lab Services Thomas Cosenza, CISSP

Transcription

1 Leveraging atapower XI50z and ysplex ection 9249 ugust 10,2011 TG Lab ervices Thomas Cosenza, CIP

2 What is a ysplex? ysplex is a clustering technology utilized historically by z/o You can spread a workload over several LPRs In case of an LPR failure the workload can be moved without the end users knowledge (in most cases) ysplex uses metrics to balance out workload (not just a spray) CPU Usage Current Capacity Current Load llows applications on z/o to be dependent on the physical connections

3 The z/o High vailability rchitecture pplication Layer Infrastructure ystems Networking WLM B2 W RR RM CIC YPLEX Coupling Facilities Workload istribution Techniques ynamic VIP IP Routing Network Interfaces MQ FM Redundancy

4 What is the XI50z atapower evice Part of zenterprise ecure ppliance High peed Cryptography Can secure just parts of data Credit Card PN N numbers Built in EB evice used in O

5 atapower and zenterprise zenterprise s main strength ecure Environment Hybrid Work Load upport atapower XI50z llows zenterprise components to communicate without application changes Legacy applications Web ervices XML HTTP HMC

6 ysplex Enhancement ysplex design originally was only for z/o systems O and Cloud are Game Changers Hybrid-Workload support In V1R11 the ysplex could now target IPv4 devices outside of ystem z IPv6 evices came in V1R12 One of the first targets for the ysplex was atapower

7 Open 24/7 atapower XI50z does not have a routing daemon efault Gateway tatic Routes While this works in the distributed world in z we must have almost 100% up time If you do not want to connect your IEN to an external router what do you do? Target OX on z/o as default gateway or static route hop? LPR Failure tack bend OX failure

8 Going back on what was a best practice In the past it was considered a best practice to put ynamic Vipas on different subnets then your O card. till is for the and OE cards However for IEN devices it is advisable to actually do the opposite Layer 2 routing llows us to use a VIP as the efault Gateway to the XI50z (or any other zbx type blade) I have nicknamed these IEN VIPs Not an official IBM name just my nickname ame as other type of VIP however

9 Way 1. Infrastructure VIP atapower does not support any routing protocols tatic Routes efault Gateway Routing Would you really want to? Want more CPU dedicated for Transactions o use a VIP with the same IP ddress ubnet as the IEN subnet Using LYER 2 Routing

10 What is Layer 2 Routing The LN infrastructure transports Frames between Network Interface Cards (NICs) Each NIC has a physical hardware address called Media ccess Control (MC) Every frame comes from a MC and goes to a MC frame carries a payload of a specified protocol type, such as RP, IPv4, IPv6, N LLC2, etc. Uses a Protocol Called RP in order to discover other MC address and their corresponding IPv4 addresses LN Frame IP Packet TCP egment Ethernet II Hdr IEEE801.Q Hdr IP Hdr. TCP Hdr. ata Trailer est MC addr rc MC addr Next header VLN I VLN priority Payload protocol est IP addr rc IP addr Type Of ervice Transport protocol est port number rc port number Frame Check equence (FC)

11 o lets look at this process RP Cache TCP/IP IP MC address MC MC3 NIC MC1 Who owns IPv4 address ?? Here is a unicast packet for at MC3 2. I do and my MC address is MC3!! O NIC MC2 O NIC MC3 TCP/IP TCP/IP

12 z/o VIP address visibility on the IEN TCPIP VIP XCF IP address: XCF IP address: TCPIPB VIP Port name PORT Port name PORTB Port name PORTC Port name PORT Home IP address Mac address MC1 Home IP address Mac address MC2 Home IP address Mac address MC3 Home IP address Mac address MC4 Gratuitous RP and respond to RP requests for: OX IEN-Host-1: OX IPv4 subnet: /24 IEN OX OX IEN-Host-2: [Gratuitous RP and respond to RP requests for: ] O PORT s OT IP ddress RP Owner Yes Yes No No IEN-Host-1 s RP cache IP ddress MC ddress MC MC MC MC MC1 OX interfaces must be defined with the INTERFCE statement With VMC and ROUTELL, only addresses for which O has to perform RP are registered in the OT In all other cases, all HOME IP addresses will be registered in the OT and the OT content will be changed as the HOME lists change due to (dynamic) movement of IP addresses. OX interfaces will do gratuitous RP for the O interface IP address and for VIP addresses that belong to the same subnet as the O interface.

13 Network connectivity resilience on the IEN z/o TCP/IP supports interface recovery if multiple interfaces to the same subnet exist. In this example, both O PORT and PORTB are connected to the IEN ( /24 subnet). Port name Home IP address Mac address PORT MC1 TCPIP VIP OX Port name Home IP address Mac address OX XCF IP address: PORTB MC2 When PORT fails, PORTB is given RP ownership of the addresses PORT previously had. PORTB sends gratuitous RPs to enable downstream hosts to update their RP cache. IEN-Host-1 s RP cache IP ddress MC ddress MC MC MC1 IEN O PORT fails IEN-Host-1: /24 IEN-Host-1 s RP cache IP ddress MC ddress MC MC MC2 O PORT s OT O PORTB s OT O PORT s OT O PORTB s OT IP ddress RP Owner Yes Yes No No IP ddress RP Owner No No Yes No IP ddress RP Owner Yes Yes No No IP ddress RP Owner Yes Yes Yes No

14 o Lets look at how the infrastructure VIP would work External External ny ny VIP VIPEFINE VIP VIPBCKUP OX OX OX OX IEN IEN efault efault VLN VLN I I IPv4 IPv4 subnet subnet / / efault router:

15 zbx Backend pplication This recommendation is much like the last however the focus has changed Instead of routing of the blade We will now look at Backend pplications

16 What if VIP was on a different subnet External External ny ny VIP VIPBCKUP VIP VIPEFINE VIP VIPEFINE VIP VIPBCKUP OX OX OX OX IEN IEN efault efault VLN VLN I I IPv4 IPv4 subnet subnet / / efault router: Transaction to

17 What if VIP was on a different subnet External External ny ny VIP VIPBCKUP VIP VIPEFINE VIP VIPEFINE VIP VIPBCKUP OX OX OX OX IEN IEN efault efault VLN VLN I I IPv4 IPv4 subnet subnet / / efault router: Transaction to

18 3) Tier upport for atapower Communication erver has added support to expand targets beyond zo atapower was an early adapter of this technology atapower can give ysplex metrics so that ysplex can make smart decision on what atapower evice it should target

19 External External ny ny VIP VIPEFINE VIPEFINE TIER VIPITRIBUTE TIER1 GROUP1 GRE CONTROLPORT 1702 ITMETHO TRGCONTROLLE Port ETIP OX OX OX OX IEN IEN efault efault VLN VLN I I IPv4 IPv4 subnet subnet / /24 ata Power Tier

20 What if my ysplex was larger What if you deployed an Ensemble within two zenterprise systems that are physical separated? VIP VIPEFINE External External ny ny B2 B2 B2 B2 B2 B2 OX OX OX OX VLN VLN I I / / VLN VLN I I / /

21 Multi-Tier Weighting s part of the ysplex we can now look at the whole transaction. Very important when talking about atapower since it is rarely the end point for any transaction ysplex istributor can add up the weights of any defined Tier 1 and Tier 2 (backend) connection

22 External External ny ny VIP VIPEFINE VIP B2 B2 B OX OX OX OX B2 B2 B2 VIP ay all P weights are equal VLN VLN I I / / VLN VLN I I / /

23 External External ny ny The Transactions will never leave the zenterprise on the left since the zentprise on the Left has better weights on the atapower devices VIP VIPEFINE VIP B2 B2 B OX OX OX OX B2 B2 B VIP VLN VLN I I / / VLN VLN I I / /

24 External External ny ny VIP VIPEFINE VIP B2 B2 B2 OX OX OX OX B2 B2 B2 VIP VIPEFINE TIER VIPITRIBUTE TIER1 GROUP1 GRE CONTROLPORT 1702 ITMETHO TRGCONTROLLE Port ETIP VIPEFINE CPCCOPE VIPEFINE TIER2 CPCCOPE VIPITRIBUTE TIER2 GROUP1 ITMETHO ERVERWLM Port ETIP LL VLN VLN I I / / VLN VLN I I / /

25 External External ny ny VIP VIPEFINE VIP OX OX OX OX B2 B2 B2 VLN VLN I I / / B2 B2 B2 VLN VLN I I / /24 VIP VIPEFINE CPCCOPE VIPEFINE TIER2 CPCCOPE VIPITRIBUTE TIER2 GROUP1 ITMETHO ERVERWLM Port ETIP LL

26 Thomas Cosenza ystem z I/T pecialist IBM TG Lab ervices XI50z Team Lead 3031 N Rocky Point R Tampa, FL Tel Mobile tcosenza@us.ibm.com