sql*net wizards course zürich 14-18 june 1989 osi overview : matching the model to reality...
TRANSCRIPT
SQL*NET
WizardsCourse
Zürich 14-18 June 1989
OSI Overview :Matching the model to reality
Frédéric Hemmer CERN
OSI Overview:Matching the model to
reality
• Today's computers• OSI layers overview• Bridges, Routers and Gateways• Decnet, TCP/IP• SQL*Net• Common questions• SQL*Net example : CERN• Performance• Conclusions
PC's and MAC's
• Single user operating system• Monotasking operating system• Limited (expensive) disk space availability• Usually no native networking• Availability of resource sharing systems• Very good dedicated user interface
Workstations
• Multitasking operating system• Multiuser operating system• Higher disk space availability• Native networking• Resource sharing by means of standards• Good (distributed) windowing interface• A lot of CPU dedicated to the user interface
Mainframes
• Multitasking operating system• Multiuser time-shared operating system• High (cheap) disk space availability• No native multi-vendor networking• Resource sharing by means of standard
protocols• Weak user interface• Little CPU used for the user interface
ISO/OSI Reference Model
Application
Presentation
Session
Transport
Network
Data Link
Physical
ISO/OSI Reference Model
ApplicationApplication
PresentationPresentation
SessionSession
TransportTransport
NetworkNetwork
Data LinkData Link
PhysicalPhysicalRS232, CSMA/CDIBM TR, FDDI
HDLC, SDLC, LAPBLLC, 802.x
X25, IP,CLNS,CONS
TCP, UDP, NSP,TP0 -> TP4
ISO/CCITT session
ISO/CCITTpresentation (X409)
FTP, Telnet, FTAM, Set host, RDA
MAC-Level Bridges
Application
Presentation
Session
Transport
Network
Data Link
Physical
Application
Presentation
Session
Transport
Network
Data Link
Physical
Data Link
Physical
Decnet Phase IVlayers
Network Management
Network Application
Session Control
Network Services
Transport
Data Link
Physical
User
Decnet Phase Vlayers
Application
Presentation
Session Control
Transport
Network
Data Link
Physical
DNA Session Control
DNA Application
OSI Application
NamingService
TCP/IP layers
Telnet, FTP, SMTP,Name Server,
r-series,NFS (+ Sun RPC),
User programs
TCP/UDP
IP/ICMP/ARP
Drivers/Controllers
Physical
SQL*Net layers
UPIUPI
Two-TaskCommon
Two-TaskCommon
OSN OSN
User Oracle
Two-TaskCommon
Two-TaskCommon
OPIOPI
Transport
Network
Data Link
Physical
Problem #1
• I understood protocols upper layers are independent of the data link layer.
So, why should I buy an ExcelanEthernet board to run TCP/IP on myMicrosoft / Intel PC?
Problem #2
• I understood protocols like TCP/IP are standards.
So, why does the Oracle installation procedure for SQL*NET TCP/IP on VMS ask me which TCP/IP (Wollongong orExcelan) ?Similarly, why does SQL*NET TCP/IP notwork for CMU TCP/IP which is almost free ?
Problem #3
• Oracle provides a SQL*NETdriver for TCP/IP on IBM's 6150(RT/PC). What should I do to makeit work over IBM's Token ringusing TCP/IP ?
Problem #4
• I'm a newcomer in the networkingworld. What networking protocolshould I use ?
• What SQL*NET networking protocolshould I use if I have the choice ?
SQL*NET Topologyat CERN
MacMacIBM PCIBM PC
IBM PCIBM PCIBM PCIBM PC
IBM PCIBM PCIBM PCIBM PC
IBM PCIBM PC
MacMacMacMac
MacMacMacMac
MacMac
Sun Sun
IBM PCIBM PC
Mac Mac
ApolloApollo
NovellNovell FastpathFastpath
LEP
ApolloApollo
RT PCRT PC
CentralVAX/VMSCluster
CentralVAX/VMSCluster
IBM 3090/6006 VF - VM/XA
IBM 3090/6006 VF - VM/XA
Siemens 7890 SVM/HPO
Siemens 7890 SVM/HPO
UltrixUltrix
LAVCLAVCLAVCLAVC
8232
3725
3732
IP
CTC
SNA (LU 6.2)
VTAM
... Decnet
UltrixUltrixUltrixUltrix
Cray X/MP 48Sun
CLC
TCP
TCPTCP
IPX
Appletalk
TCP
UltrixUltrix
PS
UltrixUltrixUltrixUltrix
TCP
The LEP Control System
LEP SPS
Computer Centre
PCR
Domain
PbarLab and offices
Dev
Software Architecture
IBM PC/AT PCAApollo
IBM
RTPC
Application Application Application Application
SQL*NetSQL*NetRPC client RPC client
RPC Servers
ApplicationServers Oracle
SQL*Net
SQL*Net
DataBaseServer
OracleServer
LEP Control System
Performance
KB
ms
Decnet
Tcp/Ip
Local0
100
200
300
400
500
600
0 10 20 30 40 50 60 70
Conclusions
• ISO protocols being specified• ISO protocols not yet fullyimplemented.• Interim solutions.• SQL*Net hides the protocol for
the user.• Better use of computers• Oracle will have to provide SQL*Net/ISO