BSI Presents: I Pv 6 / VSE

steambeanΛογισμικό & κατασκευή λογ/κού

30 Ιουν 2012 (πριν από 5 χρόνια και 4 μήνες)

465 εμφανίσεις

BSI Presents:
IPv6/VSE
1
st
IPv6
TCP/IP
Product For
z/VSE
bsiopti.com
Barnard Software, Inc.
BSI has been providing VSE tools since 1993
1998 – BSI first TCP/IP based toolset
2000 – BSI introduced TCP/IP Tools IP Stack
May 2009 – BSI introduced BSI IPv6/VSE
BSI IPv6/VSE
z/OS Affinity: Dual-Stack
Implementation
Graphic source:
z/OS V1R9.0 Communications Server:
IPv6 Network and Application Design Guide
SC31-8885-05
Figure: 22
z/OS Dual-mode Stack
Implementation
API
BSI
Pseudo
-dual-mode Stack
Implementation
IPv4
Stack
IPv6
Stack
Application
Partition
Stack
Partitions
Although there are actually two
stacks running in two
separate

partitions, the Application
Programming Interface (API)
phase (located in the application
partition) controls which stack is
used for a specific request.
The application thinks it is talking
to a dual-mode stack, yet the
stacks are still isolated from each
other enhancing performance and
reliability.
It's all in the API layer!
(No mirrors involved)
EZASOKET
EZASMI
LE/C
APIs
IPv4 Stack
IPv6 Stack
IPv4 Mapped as IPv6
SOCKET.IF value?
INET6
INET
Non-Socket
Calls
The IF= value passed on
the SOCKET call is the
primary control to
determine which stack
receives the request
An IPv6 address
that contains a
mapped IPv4
address will
receive special
routing to the
IPv4 stack
Request
Couple ID
IPv6
IPv4
Assembler
SOCKET
API
IPv4 Stack
IPv6 Stack
IPv4 Mapped as IPv6
SRBLOK.IPv6-X?
x“F6”
x“00”
Control Calls
The IPv6-X flag in the
SRBLOK passed on the
OPEN call is the primary
control to determine which
stack receives the request
An IPv6 address
that contains a
mapped IPv4
address will
receive special
routing to the
IPv4 stack
IPv6
IPv4
Request
Couple ID
Protocol-independent client applications are possible with
IPv6/VSE using the same methods as described in:
z/OS Communications Server
IPv6 Network and Design Guide
Version 1 Release 9
SC31-8885-05
Protocol-independent server applications are also
possible with IPv6/VSE using the EZA interface. Since
IPv6/VSE provides a Pseudo-Dual-Mode Stack and not a
true Dual-Mode stack, the API emulates listening for both
IPv4 and IPv6 using automatic Dual-Listens. The
application only issues one Bind-Listen-Accept, yet the
API will post the Bind-Listen-Accept on both the IPv4 and
IPv6 stacks. In IPv6/VSE, this is called the “Dual-Listen”
feature.
Protocol-Independent Clients/Servers
IPv4 Stack
IPv6 Stack
IPv4 Mapped as IPv6
SOCKET.IF value?
INET6
INET
Non-Socket
Calls
Dual-Listen
Feature
NOT AVAILABLE
when using the
Assembler
SOCKET API
EZA applications have the
ability to
simultaneously
listen
on the same port on both
stacks using just one socket
This is the default
but may be turned
off by using a
SETSOCKOPT call
IPv4 connections are
reported as IPv6
addresses
IPv6
IPv4
Request
Couple ID
Listen
IPv6
Listen IPv4
TCP/IP
V4 Stack
TCP/IP
V6 Stack
OSA/X
LCS
CICS/TS
TCP
Application
Power
Basic BSI IPv6/VSE System
IPv4 Only
SYSPARM
='44'
SYSPARM
='66'
SYSPARM
='66'
IPv6
TRAN
IPv4
TRAN
IPv6/IPv4
Mixed
SYSID 44
SYSID 66
COUPLE 44
TCP/IP
V6 Stack
TCP/IP
V4 Stack
OSA/X
LCS
CICS/TS
TCP
Application
Power
IPv4 Path Pointing to IPv4 Stack
SYSID 44
SYSID 66
IPv4 Only
SYSPARM
='44'
SYSPARM
='66'
SYSPARM
='66'
IPv6
TRAN
IPv4
TRAN
API
IPv6/IPv4
Mixed
COUPLE 44
IPv4 Data
TCP/IP
V6 Stack
TCP/IP
V4 Stack
OSA/X
LCS
CICS/TS
TCP
Application
Power
IPv4 Path Pointing to IPv6 Stack
IPv4 Only
SYSPARM
='44'
SYSPARM
='66'
SYSPARM
='66'
IPv6
TRAN
IPv4
TRAN
Request Couple ID
IPv4 Data
API
IPv6/IPv4
Mixed
SYSID 44
SYSID 66
COUPLE 44
TCP/IP
V6 Stack
TCP/IP
V4 Stack
OSA/X
LCS
CICS/TS
TCP
Application
Power
IPv6 w/ IPv4 mapped as IPv6
IPv4 Only
SYSPARM
='44'
SYSPARM
='66'
SYSPARM
='66'
IPv6
TRAN
IPv4
TRAN
Request Couple ID
IPv4 Mapped as IPv6 Data
IPv6 Data
API
IPv6/IPv4
Mixed
SYSID 44
SYSID 66
COUPLE 44
TCP/IP
V6 Stack
TCP/IP
V4 Stack
OSA/X
LCS
CICS/TS
TCP
Application
Power
IPv6 & IPv4 Multi-
protocol
Application
COUPLE 44
IPv4 Only
IPv6/IPv4
Mixed
SYSPARM
='44'
SYSPARM
='66'
SYSPARM
='66'
IPv6
TRAN
IPv4
TRAN
Request Couple ID
IPv4 and IPv4 Mapped as IPv6 Data
IPv6 Data
API
SYSID 44
SYSID 66
BSI IPv6/VSE
IPv6 Enabled Assembler Socket API
SOCKET OPEN,TCP,
DESC=WKDESC,

FOPORT=WKPORT,
FOIP=WKIPADDR,
ECB=WKECB
IPv4 Assembler Socket API
Port
IPv4 Address
Descriptor
SRBLOK
ECB
SRFOIP
No IPv4 application changes
needed even if the SYSPARM
is changed to point to an
IPv6 stack
SOCKET OPEN,TCP,
DESC=WKDESC,

FOPORT=WKPORT,
FOIP=WKIPADDR,
ECB=WKECB
IPv6 Enabled
Assembler Socket API
Port
(pointer)
Descriptor
SRBLOK
ECB
(pointer)
6
SRFOIP IPv6 Address
IPv6 Address
Family
Socket Address Structure (IPv6 layout shown)
IPv6-X
Flag
SOCKET OPEN,TCP,
DESC=WKDESC,

FOPORT=WKPORT,
FOIP=WKIPADDR,
ECB=WKECB
IPv4 using IPv6 Enabled
Assembler Socket API
Port
(pointer)
Descriptor
SRBLOK
ECB
(pointer)
6
Family
SRFOIP
IPv4 Address
Socket Address Structure (IPv4 layout shown)
IPv6-X
Flag
IPv4 Address
BSI IPv6/VSE
IPv6 Tunneling
LCS
TCP/IP
V6 Stack
LCS
CICS/TS
TCP
Application
Power
IPv6 Tunneling
IPv4 Only
SYSPARM
='44'
SYSPARM
='66'
SYSPARM
='66'
IPv6
TRAN
IPv4
TRAN
IPv6/IPv4
Mixed
SYSID 66
Tunnel Broker
TCP/IP
V4 Stack
SYSID 44
COUPLE 44
OSA/X
LCS
IPv6 Tunneling Support
Using IPv6 Tunneling it is possible to communicate with
external IPv6 networks even if the local infrastructure does
not support IPv6.
The remote end of the IPv6 tunnel (Tunnel Broker) could be
one of several commercial vendors or just local hardware.
IPv6 Tunneling overcomes:

Lack of OSA Express hardware

Pre-VSE 4.2 levels

Old local network infrastructure

Lack of ISP support for IPv6
IPv6 Tunneling is an internet protocol designed for testing
and migration. As such it has limits. It is not recommended
for high-volume production workloads.
The IPv6 tunnel is simply a network interface definition.

IPv6/VSE provides an unchanged image to an IPv4
only application

Existing Assembler SOCKET applications run
unchanged

Existing EZA applications run unchanged

No IPv4 application changes needed even if the
SYSPARM is changed to point to an IPv6 stack

IPv6/VSE provides a Dual-mode Stack image to any
IPv6 enabled EZA application

User applications transported from z/OS should run
without significant, if any changes

New z/VSE applications are transportable to z/OS

New IPv6 conforming applications can
automatically talk to both IPv6 and IPv4 clients

Only minor changes are required to IPv6 enable
Assembler SOCKET applications

IPv6 Tunneling is available for network migration
GOOD NEWS!