Professional Documents
Culture Documents
Page - 1
Neighbor Discovery
Motivations and previous approaches Data Plane Discovery
Functionality OIF UNI Discovery G.7714.1 Discovery
Discovery Motivation
Who is on the other side of the link? Analogy: The human hello protocol
Let me find out who that is Its Ms. Orange and she got my name right. Let me double check that I got her name right Nice to meet you Ms. Orange. Hello, Im Mr. Blue Its Mr. Blue. Lets tell him who I am and check his name. Hi, Mr. Blue, Im Ms. Orange
Page - 3
Page - 4
Edge Equipment #1
OC-48 lines
OC-48 lines
Port 12
Port 2
Conduit
Port 13
Page - 6
Box A
Box B
Port 1
Port 12
Port 13 Port 2
Page - 7
Box A
Box B
Page - 8
Page - 9
Page - 10
2-Way
Page - 11
Page - 12
= Optical Fiber = Optical Support Channel for Transport layer = Optical Support Channel for multiplex layer
Page - 13
= Optical Fiber = Regenerator section overhead = Multiplex section (line) overhead = User traffic (path layer) = Unused time slots
Page - 14
SONET/SDH Layers
1.5Mbps 6Mbps Multiplexing here 50Mbps 40Gbps Multiplexing here
VT Path Lower order Virtual Containers Higher order Virtual Containers Tandem Connection (optional) Multiplex Section
Section
Regenerator Section
Physical
(a) SONET
STS Path Tandem Connection (optional) Line Section Line Section Section Line Section
Physical
(b) SDH
Line Section
PTE
TCTE
LTE
STE
STE
LTE
TCTE
PTE
Page - 15
PTE
LTE
STE
PLR
PLR
STE
LTE
PTE
Definitions PLR - Physical Layer Regenerator STE - Section Terminating Equipment LTE - Line Terminating Equipment PTE - Path Terminating Equipment
Page - 16 Grotto Networking 2004
Control Plane
If we are going to participate in a control protocol who should I talk to? Control Plane
Page - 18
Sec ti on Overhead
BIP-8 B1
Orderwi re E1
Us er F1
Data Com D1
Data Com D2
Data Com D3
Poi nter H1
Poi nter H2
Section DCC
Sy nchronous Pay load Env elop 9 rows
BIP-8 B2
APS K1
APS K2
Line Overhead
Data Com D4
Data Com D5
Data Com D6
Data Com D7
Data Com D8
Data Com D9
Page - 19
status G1
Path Overhead
9 rows
user F2
multi frame H4
Growth Z3
Growth Z4
Tandem N1
Page - 20
Operation
Trace text string (16 or 64 characters) is set via a management system. Expected trace (what you should be getting) is also set via a management system. Supervision is accomplished by enabling alarms if the expected trace doesnt match the received trace.
Page - 21 Grotto Networking 2004
Page - 22
EMS
Report A, Z Values Report Z, A Values
A: TID, AID
Out-of-band Control
Z: TID, AID
Page - 23
Issues
The previous method dumps most of the work back to the EMS Doesnt necessarily blend with the rest of the control plane
How are the values of the traces filled in? May not work between domains (need some type of agreement, i.e., a standard!)
Doesnt work for the Line (multiplex section layer) since no trace
The line layer is very important since most ADM and high capacity cross connects work at this layer.
Page - 24 Grotto Networking 2004
Use of a DCC/GCC
For layers without trail trace a set of messages exchanged over the data communications channel (DCC) or General Communications Channel (GCC), that are part of the overhead for that layer.
Page - 25
MS layer:
Within the MS layer, the Multiplex Section DCC may be used to support discovery of the MS TCP-to-TCP adjacency.
HOVC layer:
Within the HOVC layer, the higher order Path layer J1 trace may be used to support discovery of the HOVC TCP-to-TCP adjacency.
LOVC layer:
Within the LOVC layer, the lower order Path layer J2 trace may be used to support discovery of the LOVC TCP-to-TCP adjacency.
Page - 26 Grotto Networking 2004
OTUk layer:
Within the OTUk layer the SM section monitoring bytes and the GCC0 may be used to support discovery of the OTUk adjacency. Specifically, the SAPI subfield within the SM is used to carry the discovery message.
ODUk layer:
Within the ODUk layer the PM path monitoring bytes and the GCC-1 and GCC-2 bytes may be used to support discovery of the ODUk adjacency. Specifically, the SAPI subfield within the PM is used to carry the discovery message.
Page - 27 Grotto Networking 2004
3824 3825
4080 SM
2 3
TTI
BIP-8
1 2 3 4 5 6 7 8
SAPI
15 16
BEI
BDI IAE
RES
Column #
1 1 2 3 4 5 6 7 8 9 10 11 12 13 14 31 32
FAS
FA: FAS: MFAS: SM: GCC: RES:
MFAS
SM
Frame Alignment Frame Alignment Signal MultiFrame Alignment Signal Section Monitoring General Communication Channel Reserved for future international standardisation
Operator Specific
63
Use the SAPI (source access point identifier) portion of the TTI (trail trace identifier) for G.7714.1 discovery.
Page - 28 Grotto Networking 2004
TTI
k DU O O d ea rh ve
1 2 3
BIP-8
SAPI
15 16
BEI
BDI
15 16
STAT
1 2
Frame Alignment overhead RES TCM3 GCC1 GCC2 TCM ACT TCM2 APS/PCC TCM6 TCM5 TCM1
Mapping specific
Row#
2 3 4
FTFL EXP
OPUk overhead
3 4
PSI
PT RES
Path Monitoring Tandem Connection Monitoring Source Access Point Identifier Destination Access Point Identifier Reserved for future international standardisation Activation/deactivation control channel
Fault Type & Fault Location reporting channel Experimental General Communication Channel Automatic Protection Switching coordination channel Protection Communication Control channel
Trail Trace Identifier Bit Interleaved Parity - level 8 Backward Error Indication Backward Defect Indication Status Payload Structure Identifier Payload Type
255
Use the SAPI (source access point identifier) portion of the TTI (trail trace identifier) for G.7714.1 discovery.
Page - 29 Grotto Networking 2004
Page - 31
Implications
Message must fit into the severely space limited J0 section trace message. Total of 16 bytes. One byte used for CRC, One for distinguishing character, of remaining 14 bytes we can only use 7 out of 8 bits (compatibility with ITU-T T.50 character set). Additional compatibility requires the use of printable characters!
Page - 32 Grotto Networking 2004
Page - 33
Local TCP-ID
Page - 34
G.7714.1 procedures
For Trace based mechanism
Use the desired message format as the trace string.
Config Objects
Config Message Node ID: Sending Node ID; CCID: Port number Msg ID: Unique ID assigned by sending node Hello Interval Hello Dead Interval Hello Config Object Hello Int. : Frequency of Hello messages; Hello Dead Int.: Waiting time before declaring neighbor dead
Page - 37 Grotto Networking 2004
T R
R T
ConfigAck (Node ID = 198.28.134.5, CCID = 4, Recd. Node ID = 192.28.134.2, Rcv. CC ID = 1) Config (Node ID = 192.28.134.2 , CCID = 3)
T R
R T
Client
OXC
Node ID = 192.28.134.2
Node ID = 192.28.134.5
Page - 38
N2 (192.15.2.3)
T R T R 11 10 Config (N1, msg=1, ccid=1) Config (N1, msg=2, ccid=2) Exchanges at Ack (N2,ccid = 10, msg=2, N1, N1,P1 and N1,P2 rccid=2) Ack (N2,ccid = 11, msg=1, N1, rccid=1)
T
3 R
T R
12
Page - 39
Page - 40
LTE or PXC
LTE or PXC
IPc
IPa
Data Plane
Control Plane
Page - 41
IP Network
Grotto Networking 2004
How do we establish and maintain the communications channel between these entities?
The IETFs Link Management Protocol (LMP) has procedures for Control Channel Management In does this via a Config procedure which verifies bidirectional connectivity and a heartbeat procedure (named Hello) to monitor connectivity.
Page - 42 Grotto Networking 2004
LMP Messages
LMP messages run over UDP (User Datagram Protocol)
Control Channel Management Messages Link Property Correlation Messages Link Verification Messages (optional not really needed for SDH/OTN) Fault Management Messages (optional not really needed for SDH/OTN)
Two flags: Control channel down, and LMP restart
Version # (Reserved) LMP Length Flags (Reserved) Msg Type
Type 1 2 3 4 5
Type 6 7 8 9 10
Type 11 12 13 14 15
Type 16 17 18 19 20
Page - 43
LMP Objects
LMP Messages consist of LMP Objects of the following form
N indicates whether the object is negotiable C-Type is the generic class type of the object Class is the particular type of object, e.g., an IPv4 address versus an IPv6 address
N
C-Type
Class
Length
(object contents)
Page - 44
ConfigNack Message
::= <Common Header> <LOCAL_CCID><LOCAL_NODE_ID> <REMOTE_CCID><MESSAGE_ID_ACK><REMOTE_NODE_ID > <CONFIG>
Page - 45
LinkSummaryAck Message
::= <Common Header> <MESSAGE_ID_ACK>
LinkSummaryNack Message
::= <Common Header> <MESSAGE_ID_ACK><ERROR_CODE> [<DATA_LINK>...]
Page - 46
LMP Functions
Conceptual control channel created and maintained via LMP config and hello messages.
IP Network
Conceptual TE link, a bundle of real links agreed upon via LMP summary messages.
Page - 47 Grotto Networking 2004
Discovery Summary
Which layer should I discover?
Generally rule: all layers that you process. Most important for layers that you switch at.
Status
Interoperability
No significant demonstration of neighbor discovery interoperability yet But standardization of G.7714.1 should help.
Deployment
A variety of proprietary implementations typically tied to link state protocols running over line or section DCC are being used in production transport networks Integration with existing OSS
Page - 49 Grotto Networking 2004