L3 Services
MINI-LINK 6600
DESCRIPTION
69/1551-HRA 901 20/11 Uen B
Contents
Contents
1 Introduction 1
2 L3 IP Router 3
3 L3VPNs 5
4 Supported Routing Protocols 7
5 MPLS Networking 9
5.1 Label Distribution 9
5.2 MPLS-Based Solutions 9
6 Supported IP Protocols 11
69/1551-HRA 901 20/11 Uen B | 2018-02-26
L3 Services
69/1551-HRA 901 20/11 Uen B | 2018-02-26
Introduction
1 Introduction
The NE provides Layer 3 Virtual Private Network (L3VPN) services and IPv4
routing and transport services.
Table 1 lists the features that are possible to configure for Layer 3 solutions.
Table 1 Configurable Features for Layer 3 Solutions
Business Application Routing Options Services
L3VPN BGP/MPLS CE-PE routing options: QoS
Layer 3 VPN (L3 OSPFv2 Route filters
PE router)
Static BFD
P router
eBGP MPLS OAM
Core routing options: LAG or ECMP
BGP
MPLS
LSP: LDP
IGP: OSPF, IS-IS
Layer 3 IP Router Core routing options: QoS
BGP Route filters
MPLS BFD
LSP: LDP MPLS OAM
IGP: OSPF, IS-IS LAG or ECMP
69/1551-HRA 901 20/11 Uen B | 2018-02-26 1
L3 Services
2 69/1551-HRA 901 20/11 Uen B | 2018-02-26
L3 IP Router
2 L3 IP Router
The NE supports standard IP routing that forwards packets to their final
destination using intermediate nodes. Each node looks up the destination
IP address and forwards the packet toward the destination through routes
collected in a routing table.
On the NE, route information is collected from the different routing protocols in
the RIB on the controller card, which calculates the best routes and downloads
them to the FIB stored on the NE. The RIB process collects routes to directly
attached devices, configured static IP routes, and routes learned dynamically
from OSPF and BGP.
When a network event causes routes to go down or become unavailable,
routers distribute routing update messages that are propagated across
networks, causing a recalculation of optimal routes. Routing algorithms that
converge slowly can cause routing loops or network outages.
69/1551-HRA 901 20/11 Uen B | 2018-02-26 3
L3 Services
4 69/1551-HRA 901 20/11 Uen B | 2018-02-26
L3VPNs
3 L3VPNs
The NE provides the following Layer 3 services and solutions:
• End-to-end Layer 3 connection over an IP/Multiprotocol Label Switching
(MPLS) core network
• Business Virtual Private Networks (VPNs), such as Border Gateway
Protocol (BGP)/MPLS L3VPNs.
• Core routing solutions, such as P router, in an IP/MPLS core network
• Multiple virtual routing instances via Virtual Routing Forwarding (VRF)
• The NE can provide Layer 2 Ethernet transport services and Layer 3 unicast
routing on the same NE without separate Layer 2 and Layer 3 devices.
Figure 1 illustrates MINI-LINK 6600 in a Layer 3 network with VPNs.
CE PE P P PE
L3VPN1
L3VPN1
Router Router
L3VPN1
L3VPN1 IP/MPLS
L3VPN2
L3VPN2
Router Router
L3VPN2
MINI-LINK 6600 MINI-LINK 6600
• Static routes
• Dynamic protocols
18284
Figure 1 L3VPNs
69/1551-HRA 901 20/11 Uen B | 2018-02-26 5
L3 Services
6 69/1551-HRA 901 20/11 Uen B | 2018-02-26
Supported Routing Protocols
4 Supported Routing Protocols
The NE supports the following routing protocols:
• Static Routing
• OSPF
OSPF is an Interior Gateway Protocol (IGP) that uses Link-State
Advertisements (LSAs) to inform other routers of the state of the sender
links. In a link-state routing protocol, each NE distributes information about
its interfaces and neighbor relationships. The collection of the link states
forms a database that describes the Autonomous System (AS) topology.
As OSPF routers accumulate link-state information, they use the Shortest
Path First (SPF) algorithm to calculate the shortest path to each node,
which forms the basis for developing routing information for that AS.
The following summarizes the OSPF features:
0 An NE can be a part of a non-stub area, stub area or totally stub area.
0 An NE can act as an Internal Router (IR) or an Area Border Router
(ABR).
0 Virtual links are supported, which is useful when an area needs to be
split in two parts.
0 Link summarization is supported, which is used in the ABR to minimize
the routing information distributed to the backbone and/or other areas.
• IS-IS
Intermediate System to Intermediate System (IS-IS) is a routing protocol
designed to move information efficiently within a computer network, a group
of physically connected computers or similar devices. It accomplishes this
by determining the best route for data through a packet-switched network.
• BGP
Border Gateway Protocol (BGP), is an EGP based on the distance-vector
algorithms which uses TCP as its transport protocol. BGP operates
between two BGP nodes, called BGP speakers. After a TCP connection is
established, the two BGP speakers exchange dynamic routing information
over the connection. The exchange of messages is a BGP session
between BGP peers.
0 Multiprotocol internal BGP (MP-iBGP) is used to exchange the routing
information and service label allocations between the VPN endpoints
in PE nodes of L3VPN networks.
0 External BGP (eBGP) is a standardized protocol run by routers
belonging to different autonomous systems (AS) to exchange the BGP
69/1551-HRA 901 20/11 Uen B | 2018-02-26 7
L3 Services
updates, for example, eBGP can be used to exchange the routing
information between PE and CE nodes.
• Routing Policies
Routing policies allow network administrators to enforce various routing
policy decisions on incoming, outgoing, and redistributed routes. The
tools used to configure routing policies include BGP AS path lists, BGP
community lists, IP-prefix lists, and route maps with match and set
conditions.
8 69/1551-HRA 901 20/11 Uen B | 2018-02-26
MPLS Networking
5 MPLS Networking
The NE supports MPLS to forward packets through a network efficiently.
In a conventional IP Network, routers forward packets through the network from
one NE to the next, with each NE making an independent forwarding decision
by analyzing the packet header. Packet processing often causes considerable
forwarding delay. With MPLS, the complete analysis of the packet header is
performed only once when it enters an MPLS-enabled network.
5.1 Label Distribution
To communicate labels and their meanings among LSRs, MPLS uses LDP,
which enable dynamic label allocation and distribution in an MPLS network.
• An LSR enabled with LDP can establish LSPs to other LSRs in the network.
LDP creates label bindings by assigning labels to connected routes and
advertising the bindings to neighbors. LDP also assigns labels to label
bindings learned from neighbors and readvertises the binding to other
neighbors. When an LSR advertises a label binding for a route, the LSR is
advertising the availability of an LSP to the destination of that route. LDP
can learn several LSPs from different neighbors for the same route. LDP
must be configured with an IGP, such as OSPF. LDP assigns a label only
to routes selected by the underlying IGP.
5.2 MPLS-Based Solutions
The NE supports L3VPN solutions using MPLS networks in which customer
connectivity among multiple remote sites is deployed across a shared central
infrastructure and still provides the same access or security as a private
network.
• BGP/MPLS VPNs
Layer 3 BGP/MPLS VPNs are a collection of policies that control
connectivity among a set of sites. A customer site is connected to the
service provider network, often called a backbone, by one or more ports.
The service provider associates each port with a VPN context.
A BGP/MPLS VPN allows you to implement a wide range of policies. For
example, within a VPN, you can allow every site to have a direct route to
every other site (full mesh), or you can restrict certain pairs of sites from
having direct routes to each other (partial mesh).
69/1551-HRA 901 20/11 Uen B | 2018-02-26 9
L3 Services
10 69/1551-HRA 901 20/11 Uen B | 2018-02-26
Supported IP Protocols
6 Supported IP Protocols
The NE supports the following IP service protocols:
• ARP
The ARP implementation is consistent with RFC 826, An Ethernet Address
Resolution Protocol, also called Converting Network Protocol Addresses
to 48.bit Ethernet Address for Transmission on Ethernet Hardware. In
addition, the NE provides a configurable ARP entry-age timer and the
option to delete expired dynamic ARP entries automatically.
• BFD
The NE supports RFC 5880 BFD. A BFD is a low-overhead, short-duration
protocol intended to detect faults in the bidirectional path between two
forwarding engines, including physical interfaces, sub-interfaces, data
link(s). A pair of routers periodically transmits BFD packets over each
path between the two routers. If a system stops receiving BFD packets
after a predefined time interval, a component in the bidirectional path
to the neighboring NE is assumed to have failed. A path is declared to
be operational only when two-way communication has been established
between the systems.
To establish BFD sessions, configure one or more BFD clients on the same
interface as BFD.
Note: BFD clients are the routing protocols, which uses BFD events to
detect the link failures. For example, the BFD clients can be BGP,
OSPF, or other applications.
• NTP
The NE supports versions 1, 2, and 3 of the Network Time Protocol (NTP).
On the NE, NTP operates only in client mode. A remote NTP server can
synchronize the NE, but the NE cannot synchronize remote clients.
Note: Before using NTP, the NE must be configured with the IP address
of one or multiple NTP servers.
• DHCP
DHCP dynamically leases IP address information to host clients. The NE
provides the following DHCP support.
0 DHCPv4 relay server
The NE acts as an intermediary between an external DHCPv4 server
and the client. The NE forwards requests from the client to the DHCPv4
server and relays the responses from the server back to the client.
0 DHCPv6 relay server (only for DCN)
69/1551-HRA 901 20/11 Uen B | 2018-02-26 11
L3 Services
The NE relays or passes client requests for IPv6 addresses and
prefixes to an external server (third-party equipment). The external
server then provides the IPv6 addresses or prefixes to the client.
12 69/1551-HRA 901 20/11 Uen B | 2018-02-26
