Link Selection and OAMVersion 01 Stephen Haddock July 18, 2012
Example Scenario Co-Location Facility Carrier Network Data Center Network Server Client • Client connects to a Server in a Co-Location facility • A single VLAN is used to carry this service within the Data Center Network • All frames transmitted and received by Server are untagged. • VLAN is monitored using CFM with Up MEPs at each interface to the Data Center Network.
Server connects with Link Aggregation Server MAC Relay Server VLAN (6.9) Link Agg Link Agg MAC MAC MAC MAC • Server connects using Link Aggregation • 5-tuple hash used to distribute frames among LAG links. • Up MEP sits above Link Aggregation • In practice, separation of the physical ports of the LAG may complicate implementation of the MEP, forcing it to be either distributed between the ports or centralized but not resident on a single physical port.
Server connects with DRNI • Server connects to two physically separate nodes (Systems A and B) • The logical view, as seen from the point of view of the Server and the Data Center Network, is that there the Server connects to a third node (Emulated System C) through a single logical port. Relay (B) Server Distributed Relay (EmulatedSystem C) (6.9) Relay (A) MAC (6.9) (6.9) VLAN (6.9) (6.9) MAC MAC Link Agg Link Agg MAC MAC MAC MAC MAC B Server Gateway Links (virtual) A
Distributed Relay as seen by Systems A and B Relay (A) Relay (B) (6.9) (6.9) MAC Selected Gateway for this VLAN MAC Server Distributed Relay (C)* Distributed Relay (C)* (6.9) (6.9) (6.9) (6.9) (6.9) (6.9) MAC LAG* MAC MAC LAG* MAC Link Agg MAC MAC MAC MAC MAC IPL • Link Selection still based on 5-tuple hash, so both LAG links carry data. • Where does the Up MEP go?
Options for MEP Implementation • Distribute MEP functionality across the physical DRNI ports. • Requires standardizing how MEP functionality gets distributed. • Almost certainly requires support from the Intra-Portal Protocol. • Distribute MEP functionality across the Intra-Portal Port and the DRNI ports in the system with the selected Gateway. • Distributes MEP functionality among ports in the same physical system (which is the same problem that arises with today’s LAG). • Intra-Portal Link is not included in the MA monitored by the MEP. • MEP functionality moves when the selected Gateway changes. • Constrain the Link Selection such that all frames that would pass through the same MEP use the same DRNI link. • VERY restrictive constraint. • Are there any other options?
2nd Example: DRNI at an I-tagged service interface I-tagged Service Interface* Carrier A Network Carrier B Network B A B-components (B-BEBs) • The service ID on an I-tagged service interface is the I-SID. • Link selection is by I-SID • Multiple I-SIDs map into a B-VLAN in the Carrier A Network • The B-VLAN is monitored using CFM with Up MEPs at each interface to the Carrier A Network. * Reference: 802-1Q Figure 25-9 and 26.6.2
I-tagged DRNI as seen by Systems A and B Relay (A) Relay (B) (6.9) (6.9) MAC Selected Gateway for this B-VLAN MAC Distributed Relay (C)* Distributed Relay (C)* (6.9) (6.11) (6.9) (6.9) (6.11) (6.9) MAC LAG* MAC MAC LAG* MAC MAC MAC MAC IPL • Link Selection based on I-SID, so I-SIDs from both LAG links could map to the B-VLAN. • Where does the Up MEP go?