Digital PDFs

ACT005-A

2000

81 pages

Original

5.0MB

Document:	DECnet/OSI A Technical Overview
Order Number:	ACT005-A
Revision:	0
Pages:	81
Original Filename:

OCR Text

/
di

DIGITAL EQUIPMENT CORPORATION
TAPESTRY SEMINAR SERIES

DECnet/OSI
A Technical Overview

smiii]

ACT005-01/A

r--

SiM

“Topics
The Value of Standards
a Seven Layer OSI Model
a OSI Products and Applications
a DECnet/OSI
a DECnet/OSI Phase V Migration

ACT005-03/A

r -1

The Value Of Standards

Why standards?
Standards organizations
« iSO approvai process
What is OSI?
OSi terms
E;

Overview of a layered architecture

ACT005-04/A

The Value Of Standards
Why Standards?
■ Information is business’s most important resource
Over 90% of all DP sites have equipment from more
than one vendor
Provide a common architecture across multiple platforms
Facilitate the sharing of information throughout
the enterprise
Reduce duplicate Implementation and support costs

ACT005-0S/A

-F -t)

Standards Organizations
« International Standards Organization - ISO
■ Corporation for Open System - COS
■ American National Standards Institute - ANSI
u Institute of Electrical and Electronic Engineers - IEEE
y International Consultative Committee for Telephony
ccirr
and Telegraphy
Omnicom Inc.
National Institute of Standards and Technology

NIST

■ Standard Promotion and Application Group - SPAG
*Government Open Systems Interconnect Profile — GOSIP
*

ACT005-06/B

ISO Approval Process
X-

NWI - New Work Item

■ DP - Draft Proposal
DIS - Draft Infernatlonal Standard
i

IS - International Standard
:1

Average time for entire process
is three-to-four years
ACT005-07/B
1

»
\

Digital And Open Systems
■ Participation In ISO since 1979
■ Over 120 committees worldwide
■ Chairmanship of committees such as
OSI network layer, protocols for security,
NBS Implementers workshop, and COS
■ Leadership in COS, OSInet, OSIcom, EUROsinet

ACT005-08/A

'
A

-What Is OSI?
Seven layer peer-to-peer Network Architecture
I Standards set by ISO
- ISO-7548 Basic Reference Model Definition
OSI origin based on existing architectures
I Network Standards for the 21’st century
y Accepted by customers, vendors, governments
vyang

Honeyv^l^

OSI

IBM

Digital
i-iv

UNISYS

SUN

ACT00S-09/A

OSI
Presents User’s Application
fOranslates Data
Controls Dialogue
nsures Message Integrity
Routes Packets
Detects Errors
F Connects Device
JTo Network

ACT005-10/A

OSI Terms

‘OO^^’

Ct/Vg.

’Cog>

'GOs/p.
ACT005-11/A

Principles Of A Single Layer
The protocol is conveyed using the service of the
next lower level
The N-protocol is carried as data by the
(N-1) service
The lower layer has no knowledge of, or interest in
the content of the data it conveys
n-layer client

n-entity

n-protocol

n-service

n-entity

n-layer

(n-1)-sen/ice
Communication through lower layers
ACT00S-12/A

W-

Protocol Control Information
Each layer of the architecture specifies particular
Protocol Control Information (PCI) to be added to
the user data
The user data and PCI form the
Protocol Data Unit-PDU
nPCI

I (n~l)-layer
PCI
'

WW-«'

W«n.VAWV

(n-M)-layer
User Data

(n+1)-layer
PCI

!!5S!!!5BB!!SB5S5SS^SSSS«S5«S<SS5

n-layer User Data
4

nPDU
ACT005-13/A

DNA/OSI

ill*

TPDUs
TSDUs

-S<-

f 1-: '-

NSDUs

DSDUs

Transport
Layer

{i»l

NSDUs

Network
Layer

DSDUs

Data Link
Layer

Intermpdii^te System

NPDUs i
(Packets) ;

DPDUs
(Frames)

^ TSDUs

I--JI

Physical Channel

Physical
Layer
ACT005-14/A

Topics
■ The Value of Standards
■ Seven Layer OSI Model
■ OSI Products and Applications
■ DECnet/OSI
(

■ DECnet/OSI Phase V Migration

ACT005-15/A

Layer OSI Model
APPUCATION

Application Layer

I PRESENTATION

Presentation Layer

>flSESSION

Session Layer

flTRANSPORT

Transport Layer
Network Layer

lETWORK
WATA LINK
●.f
i

-i Data Link Layer

PHYSICAL

ill

- Physical Layer
ACT005-16/A

Application Layer
APPUCATION

Provides services for end-user and
application tasks

;

SESSION

Interface between communications
environment and application process
■ Specific Applications Service
Elements - SASE

PRESENTATION

TRANSPORT
.NETWORK
s

- File Transfer, Access and Management - FTAM
|
(ISO 8571)
- Virtual Terminal Protocol - VTP
(ISO 9040 - ISO 9041)
- Message Handling System - X.400 MHS
- Job Transfer and Management - JTM

iATA LINK
PHYSICAL
VS

■ Association Control Service Element — ACSE
ACT005-17/B

/%}

>S *

Presentation Layer
Conversion of data for application
processes
Provides a specialized data transfer
service to the application layer
■ Transfers data in a
system-independent way
■ ISO 8822 - OSI Presentation
Service Definition
■ ISO 8823 - OSI Presentation
Protocol Specification
■ ISO 8824 - ASN.1 Notation
■ ISO 8825 - ASN.1 Encoding Rules

APPLICATION
PRESENTATION
SESSION
TRANSPORT
.NETWORK
►ATA LINK
I

I
I

PHYSICAL

H *

ACT00S-18/B

Session Layer
PPLICATION

'i
4

RESENTATION

Responsible for system-dependent
aspects of communication
■ Matches incoming requests to
appropriate users

SESSION

TRANSPORT

:.1

lETWORK
5

»ATA LINK

Manages transport connections
for users

PHYSICAL

Enforces access control policies

■ ISO 8326 - OSI Session Layer Service Definition
■ ISO 8327 - OSI Session Layer Protocol Specification

ACT005-19/A
1

Session Connection Control
Making an outgoing connection
Receiving an incoming connection
Handles Disconnect or Abort request
to end logical link
Connect Request
Connect Confirmed

I I

◄

Data Request
Data Transfer
Data Transfer
Data Transfer

◄

End of Data Transfer
Session Disconnect

►

Session
Establishment

Data
Transfer
Session
Termination
ACT00S-20/A

Pransport Layer
>

PPLICATION

Transparent data transfer between
end systems
Starting/stopping logical links

f V

ss
I

[i
PRESENTATION

'i
-s ?

5:1

14
14

SESSION

rlTRANSPORT

Flow control and congestion avoidance
\.yy!

ETWORK

Segmentation and reassembly
Multiplexing over CONS links

f.
DATA UNK

PHYSICAL

Piggybacking
:h

End to end error detection/recovery
ISO 8072

OSI Transport Layer Service Definition

ISO 8073 - OSI Transport Layer Protocol Specification
ACT00S-21/A

rransport Service Classes

Class 0
- Simple protocol with limited features
- No multiplexing, flow control, or error checking
- Required for X.400 MHS

Class 2
- Multiplexes transport connections over single network connection
- Flow control optional
- Used over X.25 networks only

Class 4
- Most complex - but most reliable
- Multiplexing, flow control, and error detection and recovery
- Good for LAN and subnetworks
- Uniform service independent of network

Class 1 & 3 not supported by DNA/OSI

ACT005-22/A

Transport Protocols
And Network Services
Session
Layer

OSI Session

f
s ,-? ●;●■

-4"

4!i'

●>

■;:

y ^

r; ^5?:-

<●

V'
5>.

r4
'5

''W

vO-

^ ●*/»X<-X

ri;

■S'-

Transport
Layer

r-: ●:>>%%

▼

TP
4

TP
2

)

wi^v:::-::*;*:-;*:*:*:*:*:*:*:*:*::*:*

^●.●.●;:-::v::x-:-:*:*::-;

>%;.;.;.;.:.;.:.%:.:.:.:.:.;.;.:.;.:.:.:.:.;.:.;.;.:.x«x»x-x-;

>4
i

CLNS «● i. <
f

>.
'd

f
CONS

i
f

●:v:»:-:::-x::-x*

'Ai'r

Network
Layer
ACT005 - 23/A
I

Network Layer
^ U'

APPLICATION

Establishes, maintains, and terminates
communication between nodes

PRESENTATION
I

Sets up the most economical path between
communicating nodes

SESSION
TRANSPORT

Routes messages through intervening nodes
to their destination

IrlNETWORK
lATA LINK

Controls the flow of messages
between nodes
ISO-9542 provides End System to
Intermediate System Routing Protocol

PHYSICAL
m
\

u Proposed Intermediate System to Intermediate System
[IS to IS] protocol
I

ACT005-24/A

''A'y

Data Link Layer
APPLICATION
>:;

Passes data between directly
connected nodes

PRESENTATION

sV. %

'tf#-

[TRANSPORT

Features supported
- Connection establishment and release
- Data transfer
- Framing and synchronization
- Sequence control - pipelining
- Error detection and recovery
- Flow control
- ID and parameter exchange

SESSION

[NETWORK
fy

LINK

|,ATA

af'-

PHYSICAL
\
s'

s >

&
T

■ ISO 8802-3, 8802-4, 8802-5, HDLC,
CCITT X.25, ISDN, FDDI
ACT00S-25/B

ItaL

-aM.

Topics

■ The Value of Standards
■ Seven Layer OSI Model
■ OSI Products and Applications
■ DECnet/OSI
■ DECnet/OSI Phase V Migration

ACT00S-26/A

i DECnet/OSI
in

DECnet/OSI Data Link Layer Protocols

m DECnet/OSI Local /^ea Networks
Support of X.25 Networks
m DECnet/OSI End System to Intermediate System Protocol
m DECnet/OSI Network Layer
I

m DECnet/OSI Network Layeir Functions
m Link State Routing
M

DECnet
and OSI Addressing
;

m. ISO Addressing Authorities
m DECnet/OSI Multiple Routing Domains
Other Network Layer Features of DECnet/OSI
Distributed Name Service
Network Management
Enterprise Management Architecture - EMA
ACT005-27/A
I

Physical Layer
m

Handles the electrical and mechanical
transmission interface between
directly connected systems

APPLICATION

m
PRESENTATION
SESSION

Extensive use of industry standards
(EIA, CCITT, IEEE, ISO. ANSI)

TRANSPORT

JMETWOBK

Switched network support X.21, ISDN

ii
'-i -f

w|ig

Modem connect features
- Call control and monitoring
- Call sharing
- Network management

lATA LINK
f

r PHYSICAL

{ JSJ

■ ISO 8802-3, ISO 8802-4, ISO 8802-5, EIA RS-232-D and
RS423, CCITT V.24 and V.35, FDDI, ISDN

ACT005-28/B

Digital’s Commitment
To Standards
DECnet/OSI

Phase V
■ iso/osi
Phase IV

Phase III
Phase II
Phase I
■ RIe
Transfer

■ Remote
RIe Access

■ Computer
Integrated
Telephony

■ Adaptive
Routing

Standards
Bas^
Enterprise
Networks

●X.

^■Ethernet
LAN/802.3
■ DECnet for PCs

■ CCm X.25

■ DECnet/OSI
Integration

■ DECnet/SNA

Integration
of OSI
Standards

Multivendor
Networking

vyide Area
Networking

Peer-to-peer
Communication

Network
Management

32
Nodes

256
Nodes

1,024
Nodes

64,449
Nodes

>1.000,000
Nodes

1975

1978

1980

1982

1990

1990s
ACT00S-29/A

DECnet/OSI Data Link
Layer Protocols
DDCMP - synchronous or asynchronous
HDLC - synchronous only
- Extended sequence numbering
- Error detection - 32 bit option
- Includes LAPS support
X.25 - packet switched data networks
m CSMA/CD - LAN
- Ethernet V2.0
- ISO 8802-3, IEEE 802.3
Fiber Distributed Data Interface
FDDI
ACT00S-30/A

DATA UNK
F PHYSICAL

ACT005-31/A
1

IEEE 802.3
2

Preamble

Destination

Source

S
Preamble F D^Iiwtlon
D
.s

46-1500

Data

CRC

(bytes)

.1 1 1
0
PAD

Data

Source|
Lm
|
f
fp l

WvM

;\v:vX%svi*:

ivI'MvIvJvX*;

CRC

LLC PDU
SSAP & DSAP:
1

Protocol ID

(bytes)

J55!5!5S5!5!S*?55!555^

ISO 8802.2 SNAP Frame Format

SFD
Destination
Source
Type

= Start Frame Delimiter
= Destination Address
= Source Address
= Protocol Type

Len
DSAP
SSAP
SNAP
Ul

= Length of PDU
= Destination Service Access Point
= Source Service Access Point
= Sub Network Access Protocol
= Unnumbered Information
ACT005-32/A

FDDI And Other
LAN Standards
S'

%%r>

-'W 'tj

■S
e' I

y
‘W'VWVA

^"vTcSvSJSJ^^TSiiKSfs^rsssovSSSSSJi^^^^

M ?i$r!l45i;;v:i?$®i

>
j'j

//^ /

iiiil
Z^v' y
¥«;;:SWSS:S:

,A.#-Sx

DATA UNK

wmf:

M
T
I
:●
●:

PHY
X3.138
PMD
X3.166
I

§
§g

IEEE
802.3
CSMA/CD

IEEE
802.5
Token Ring

IEEE
802,4
Token Bus

I PHYSICAL

;-w *M*x-w*:*::*:‘:-:‘:

x*>;:':*;*x*:«xv:v:v:v:v:-:v:*:

FDDI
ACT005 -33/A

I
I

FDDI And
Other LAN Standards
A

f.'
5^v

»x««

DATA
UNK
LAYER
4i

"'SSI
ji K«4-^ ^

I:●:
●:●:
;:●●

:●:
:●:

PHYSICAL I
LAYER I:●:

4" ,

J-

8094

!=| Tolmii Rino

/
/

● Encode/Decode
● piQcWng
/

PMD

/
/

Physical Media Dependent
● Electrical/Optlpal Unk
● Connectors and Cables

ToMn Bim

PHY

!::●●:

IEEE
^4 ■

' Fb^

J‘

Physical Protocol
● Ring Monitoring
● Ring Management
● Ring Configuration
● Connection
Management

EEE
802J
i*● CSMA/CO

«:::.*:WSv;K¥S!#fc

Managfmer^

PHY
PMO
X3.1M

●i't

«/

ilLiiiiiii

^ii
/>r. '\r^o

^ : J-

8
M
T

/■'

/
/■

,vx*:*.s'

■x\v:*XvX%‘X%%‘:

?!S!!SS88!5BS!?S<???!?5!S?!S!?!?5SS5!?S5!S!w5!^5:-x-:

FDD

ACT005 -34/A

FDDI Characteristics
100 Mbps token passing ring with 125 Mbaud
transmission rate
I

■ 62.5/125 micron, muitimode fiber @ 1300 nm
t

♦

Circumference up to 200 km
inter-station distance up to 2 km
Support for up to 500 stations

ACT005-35/A

Differences:
FDDI - 802.3 - 802.5

FDDI

IEEE 802.3

IEEE 802.5

Media

Optical fiber

Coax
Twisted Pair
Opticai fiber

Twisted Pair
Optical fiber

Bandwidth

100 Mbps

10 Mbps

4 or 16 Mbps

Encoding

NRZI-4B/5B

Manchester

Seizes token

By absorption

(CSMA/CD)

By flipping a bit

Reieases token

After transmit

(CSMA/CD)

After receive (4 Mbps)
After transmit (16 Mbps)

Frame size

4500 bytes max

1500 bytes max

No maximum

Link monitoring

Explicit spec

No spec

No spec
ACT005-36/A

m '4

FDDI Token Operation
if
i-

#
●iVASV.

A
I

■
X

‘●f >

<1
X

p
ACT005 -37/A

DAS

DA?

iza
?T!?
<■

i.
■

{
^■●vbVA

:●

:■

'if

ma^

●»:

wff>iyj>iyA'

DAS
SAS

^SAS^

= Dual Attachment Station
= Single Attachment Station
= Wiring Concentrator
= Primary Ring
= Secondary Ring
= Token
ACT005 -38/A

Support Of X.25 Networks
Native X.25 calls
DECnet/OSI data link mapped calls
X.29 Inbound/outbound terminal

■ OSI transport class 0, 2, 4
Packet or frame level trace facility
I

Security and accounting facility

t
I

i Host-based or gateway access
ACT005-39/A
I

I
I

iDECnet/OSI End System To
Intermediate System Protocol
■ End systems
- Talk directly to other end systems - single hop
- Talk to intermediate systems
- Uses ISO 9542 routing protocol
■ Intermediate systems
- Talk to end systems
- Enter data onto backbone
- Route data to destination
- Uses proposed ISO IS-IS protocol
- Typically dedicated devices (OSI L1-L3)
- May provide portal services (encapsulation)
ACTQ0S-40/A

wDECnet/OSI Network Layer
Provides end to end data transfer across network
Provides routing - finds best path dynamicaily
ISO-8473
ISO Connectionless Network Service
- ’Internet’ Protocol
- Send data message without first establishing connection
(datagram service)
- Allows duplicate, out of order, or lost packets
- Does not allow modification or mis-delivery

ISO Connection-mode Network Service — ISO-8348
- Send data message only after first establishing connection
- Used to support X.25 subnetworks
ACT005-41/A

h-mM DECnet/OSI Network
Layer Functions
Adaptive routing
- Administrative and pubiic domains
- End systems and intermediate systems
- Sub-networks
- DECnet has sub-domains (areas)
+ levei 1 routing
Segmentation and reassembiy
. i Lifetime controi

per iink

Congestion avoidance marking
ACT005-42/A

Link State Routing
Nodes sense their local environment (links, neighbors)
Node broadcast this information to the entire network
Li

Each node builds up a topological map of the whole
network

L.J

Each node independently computes routes
Updates In local environment status are conveyed via
Link State Protocol data units (LSPs)

ACT005-43/A

-i Advantages And Disadvantages
Of Link State Routing
Advantages
- Scales well with network size
- Converges rapidly after changes
- Rarely exhibits loops and stamps them out quickly
- Easy to diagnose: each node has a full topology map
- Easier to secure than distance vector
LJ

Disadvantages
- Very difficult to design and build correctly
- Needs specialized mechanisms to deal with
highly-connected networks (e.g. LANs)
ACT005-44/A

5 Example Of
Link-State Routing
/●!

Area 7^
●y

Area C
- -2

\ f
< 5 ■●'

●f

X.25
PDN

●■s

2
Area B
Foreign Net

ACT005 -45/A

iDECnet And OSI Addressing
IDP - Initial Domain Part
- API - Authority and Format Identifier
- IDI - Initial Domain Identifier - number
- 11 bytes in length
u DSP - Domain Specific Part
— DEOnet area address
- + 2 bytes
- + 65,000 areas per subnet
- DECnet ID
- + 6 bytes
- d- 280,000,000,000,000 nodes/area
- Protocol selection byte

ACT005-46/A

Phase V Addressing
A Phase IV Network Address looks like this;
Area

Node

6 bits

loTbits

= 2 bytes

A Phase V Network Address looks like this:
ISO 8348/Add.2 address
IDP

API

IDI

DSP

<20 bytes

LOG-AREA

SEL

2 bytes

6 bytes

1 byte

●... .-.y.v

1 byte

<10 bytes

ACT005-47/A

I ISO Addressing Authorities
X.121 - for X.21 and X.25 networks
E.163 - POTS for telephone network
E.164 - for ISDN networks
i

F.69 - for Telex
- ISO Geographic
- ISO Non-geographic

ACT00S-48/A

uiMM Global Address Domain

Routing poma^ 4

Administrative
Domain 2
Administrative
Domain 1

ACT005-49/A

^DECnet/OSI Multiple
Routing Domains
Reasons for inter-domain routing:
- Limits routing overhead
- Scaleable for performance and management
- Robustness - protected from MIS-management
- Interoperability - with non-DNA routing algorithms
Done with static or derived routing
- Performed at the DECnet Level 2 Router
- Suggested that it be performed by
dedicated router
ACT005-S0/A

'A
A

Example Of
Multiple Routing Domains
Boutins pomoin 3

2
/

'0
'i
■>

VV*

t
s

X.25
PDN

' Domain 1
<

<
<

Area B
■>

Foreign Net

Routing Domain 2
ACT005 -61/A

other Network Layer Features
Of DECnet/OSI
j Phase V routers support Phase IV routing
^ Autoconfiguration of end systems (IDP and area)
ui Multi-linked end system - load sharing/
multiple subnets
Multiple addresses
; Multi-homing end system
« Dynamically established data links - X.25/X.21
Equal cost path splitting
ACT005-52/B

<Ss

Multi-link End Systems
An End System with more than one circuit
DECnet/OSI
''●im

DECrouter

Ethernet

Multi-Link
End System

Ethernet

O
DECrouter

DECnet/OSI
ACT005 - 63/A

Multi-homed Systems

>iy

Area B.
Ail Nodes in this area
will have two addresses:
IDP1 + B +ID
IDP2+ B + ID
ACT005-54/A

DECnet/OSI Tranport Protocols
And Network Services
DNA Session Control

Session
Layer

OSI Session

:::●

DNA Naming Sendee I DNA Session Con^
A/.\

▼

NSP

TP
4

TP
2

TP
0

▼

Transport
Layer

»»y*v

t
y

CLNS

's'

<ss

Sso

it
5
<

CONS

Network
Layer
ACT00S-65/A

vyjk'

DNA Naming Service DECnet/OSI Session Layer
■ Provides global names for nodes, devices, applications,
and other objects in multiple DNA networks
y Available now as a DSS product for Phase IV
■ In Phase V, it bedomes a central and required part of
DECnet for all DNA implementations
u Design goals:
- Scaleable
- Robust
- Self configuring
- Fast
- Totally decentralized management
ACT00S-S6/A

'''

Naming Service Concepts
u Names are stored in directories.
A directory can contain:
- Object entries
- Child directory entries
- Soft links
Directories are linked together into a rooted tree,
called a namespace
-i Namespaces, and all entries therein, have globally
unique identifiers associated with them
ACT00S-57/A

mm.

iii

Example Names
Parts.widgets,left-handed.SMOKESHIFTER
Government:Treasury.Bills.CurrentSeries
DEC:.Engineering.Networks.Arch.Specifications
n

ULTRIX.Sources."OSITransport.c

D N A$ReverseTranslation.%X09004532AB

ACTOO5-50/A

Example Namespace
DEC
Qlsen
HQ
ENG
Research
NaC
Staff
Bergil

VAX

Sites
/Landover
Uttleton
Nashua
\Maynard

staff
PROT01

Arch
i

Sales
Market '
DNA-Specs
Tapestry y

Distributed Systems
Architecture

Oran
Oran-MBX
SPECS .
ACT00S-S9/A

S'"

-●v

Open Systems Enterprise
Management Architecture

CZ3 a czn a a c=3

■■nmiii
■miifiwiinii
ifirifuniifiiii
r

IMUUHiUK

/
y*

>
I

!
I

Vi i ^ t-

/If. f

ACT005 - 60/A

Network Management
y Common Management Information Protocol/
Common Management Information Service - CMIP/CMIS
- Management Information Control and Exchange - MICE
- Management Event Notification - MEN
- Replaces NICE and EVL
LJ

Maintenance Operation Protocol

MOP

- Down/up line loading
- Unk loopback testing
- Remote system console control
i’v J

Network Control Language

NCL

- User access to network management
- Scripting and wildcarding
- Access to name server for nodes
- Migration module for Phase IV nodes
ACT005-61/A

Uid Enterprise Management
EMA
Architecture
Standards based architecture addresses all OSI
management areas
y Open, consistent, and easy to use modular interfaces
/

II Flexible management domains
Consistent database of management information
u ’Entity-Director’ model
Allow for monitoring and control of DNA and
non-DNA networks
ACT00S-62/A

Digital’s Enterprise Network
Management \^sion
Migrate/Converl
Maintain
Operate

Design/Pla
Database^
Application^
Systemi
Voice Netwo

1
y.

I●5

Data Networks

5:
:l:
/-■

Configuratii
Fault
Traditional Management
Elements

\
Security
Accounting

ACT00S-63/A

Director Entity Model
Network
Management

Network

Mani^erinifnt

Dfr^tor

Director

w* vm

Service
Interface

E
N
T
I
T
Y

Agent

Service
Element

t
Client
Interface

Agent

Service
Interface

Sen/ice
Interface

Sen/ice
Element

Agent

Service
Element

t
Client
Interface

Client
Interface
ACT005-64/A

'P
'

Digital’s Enterprise
Management Architecture
Presentation Modules
>
.:
●

Functional
Modules

Access
Modules

5
J.

[

:●
:●

I
1

Interface

:■

:●
I;

Executive

:
:■

>:
a

Mgmt,
Info.

ACT005 -65/A

EMA System Structure
Presentation Modules
Reports

Access
Modules

Functional
Modules

Cpnfig. FM
■IvIvIvXwI

DECnet AM

Interface

W’>:vKwXv;‘

Fault FM
i

Performance
FM
Security FM

Accounting FM

Executive

'6
>1

sW<-. -iis. .‘.‘8x! ^ >●●●

Ethernet
*●
; AM
^

I
N

Term. Server AM

E
R
R
A
C
E

Bridg# AM

Modem AM
, PBX AM

Management
Information
Repository

T1AM
●.

ACT00S-66/A

Topics
m The Value of Standards
Seven Layer OSI Model
OSI Products and Applications
DECnet/OSI
m PECnet/OSI Phase V Migration

ACT005-67/A

OSI Products And Applications
Message Router X.400 Gateway - MR/X
u File Transfer and Access Management - FTAM
i

y VAX OSI Application Kernel - OSAK

ACT005-68/A

Digital Provides OSI Today
Njess^gjng.
MRX

pile Transfer Program-Program
FTAM

OSAK

4 - rv^iOSI Transport

!
!
t

i
I

ISO
8802.3
(Ethernet)

ISO
8208
(X.25)
ACTOOS-69/A

Message Router X.400
MR/X
Gateway
Layered VMS application
Conforms to CCITT X.400 1984 recommendations
>:*

Demonstrated interworking with over 30 vendors

y Aliows access from all Digital MAILbus products
to X.400 conforming systems
VOTS included to
VAX OSI Transport Service
provide the Network, Transport, and Session Layers
of the OSI stack
Operates over X.25 WAN or ISO 8802-3 LAN
ACT005-70/A

Message Router X.400 (MRX)
other

Digital

X.400 User
Agents

Message
Router
X.400

MAILbus
<

●o. s%.'

ULTRIX
Mail
Connection

TCP/IP

MR/P

MR/S

SNA

SNA/SNADS \
)

X.400
Network

r
X

‘

I
SMTP Mall
User
Agents

PROFS

DISOSS
ACT005-71/A

File Transfer, Access And
FTAM
Management Service
Layered VMS application
Uses ISO 8571 - File Transfer, Access and
Management protocol
kj Allows transfer and access of files with other FTAM
compliant systems

Supports:
- FTAM 1 - unstructured files with ACSIl data and
stream record formats
- FTAM 2 - sequential text files with variable record
formats and carriage return attributes
- FTAM 3 - unstructured files with binary data and
stream record formats
ACT005-72/B

File Transfer, Access And
FTAM
Management Service

Supports any file naming convention
y Includes control programs, tracing utilities,
event logging and reporting
VOTS Included to provide the Network,
Transport, and Session Layers
!
i-iiM

Operates over X.25 WAN or ISO 8802-3 LAN

ACT00S-73/A

File Transfer, Access And
FTAM
Management Service
FTAM

VAX FTAM
VAX

System

J5T

IFAM

, DEGnet/X^
Router

Host

DECnet/OSI

X.25
VAX
FTAM
Micro
VAX

DECrouter

I
DECrouter
VAX

1
[

DXiScmms

VAX

□

I
T

VAX FTAM
ACT005- 74/B

^VAX OSI Application
OSAK
Kernel
y Layered VMS product
m Provides application interfaces to the OSI session
(ISO 8327), Transport (ISO 8073), and Network
layers (ISO 8473)
iii Allows application developers to create OSI-based
applications
Conforms to Session Layer protocol ISQ 8327
Operates over X.25 WAN or ISO 8802-3 LAN
ACT005-75/A

Integration Within
DECnet/OSI Phase V

DECnet

■

J:*

►DECnet/OSI

OSI
'i ■

A
v^ %

PECnet
Phase
IV

; ■?

:●:

>»

●:|

tf?g

U'^'iiUUi

DDCMP
Ethernet
X.25

:●:
I

TOT

''V.

X
'V

<●■
'■.

■■●:

,4-

"Ssrr

ISO
8802-2
8802-3

'
●'-'X

% s

'■>:. :●,

ACT00S-76/A

“Topics
The Value of Standards
Seven Layer OSI Model
I
I

OSI Products and Applications
DECnet/OSI
DECnet/OSI Phase V Migration

ACT00S-77/A

New Features Of Phase V
With Regards To Migration
The new concept of IDPs appear
The Node ID field grows from 10 bits (1023 max)
to 6 bytes (extremely large)
I

The Area field grows from 6 bits (63 max)
to 2 bytes (64,000)
Network Management is enhanced and extended
New appiication interfaces will appear
ACT005-78/A

Phase IV Backwards
Compatibility In Phase V Allows:
■ Phase IV nodes to be directly connected to
Phase V nodes
■ Applications on Phase IV nodes to communicate
with applications on Phase V nodes
■ Applications written to use the standard Phase IV
programming interfaces to run on Phase V nodes
y Network Management of both Phase IV and
Phase V nodes from Phase V node
ACT00S-79/A

Phase IV Backwards
Compatibility Rules
Phase IV and Phase V nodes can be
interconnected and fully interoperate if they
follow the rules;
- Phase IV nodes cannot talk to other systems
with nodes IDs greater than 1023 or Areas
greater than 63
- Phase V and Phase IV nodes that wish to
communicate must reside in the same IDP

ACT00S-60/A

●V

Mixed Phase IV And
Phase V Network
IDP T
Phase
IV

Phase
V

kSdj

I f

y.10.99999

(x)10.5
Phase
V

IDP ’X’

/ Phase
V

x.10.90

Phase
IV
!

□□

Phase
IV

[y.)10.123
M
V

Phase
V

Phase

y.99.10

I I

Phase
V

^ czia
ACT00S-81/A

All

●#●

'‘M

filifs-

:51:●

'ii’S

i
i?

OSI Appliqatltni
Layer Protocols

User

Applications

OSI PresentMon
OSI Session

i
'T>oaQ«p,

M
A
N
A
G
E
M
E
N
T

1
I

sja
'f<

t Layer

A-

‘i

M
A

G
■B

M
E
N
T
^s*

<● :

❖d-:

2^2.3

DDCMP
J ' '\A

>●

●t''

:■:

' ' ●. ,ii0tsS.^

Tf: IK

' 'H

it
..V

ACT005 -82/A