Have questions? Stuck? Please check our FAQ for some common questions and answers.

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

Overview

This page describes the proposal of SDX use case that concerns the BGP functionality of SDN-IP application.

Association of peers with interfaces

Description

There is the case that multiple peers belong to the same AS and are connected through different connection points to the SDX controlled by ONOS. In this case, the user should be able to explicitly define the connection points to each peer. This is necessary since the identification of the appropriate interface by the application itself is not enough. Overlapping or identical sub-nets may exist in the "ports" section of the network configuration and thus the identification of which connection point should be used for a given peer is not straightforward.

Requirements

The requirement applying to the above feature are the following:

  • Different peering sessions can be maintained for the same AS.
  • Interfaces towards overlapping and/or identical sub-nets can be defined in the "ports" -> "interfaces" section of network configuration. These interfaces can be used for BGP peering sessions and, in order be be referenced to, a "name" must be specified for them.
  • In case that a given peer's IP address matches with two or more interfaces, it shall be recommended that the user should explicitly specify the interface that applies.
  • Backwards compatibility shall be kept with existing configuration structure.

  • New functionality shall be also supported by add-bgp-peer command.

  • Any previous explicit associations of peers with interfaces shall be cleared with remove-bgp-peer command.
  • The user shall be able to monitor such configurations with appropriate printout command. A new command named bgp-peers is proposed to be introduced for this purpose.

Sample configuration

An example of a network configuration supported by the proposed feature is the following: network-cfg.json.

This configuration is based on the one described in the SDN-IP tutorial. New peers with IP addresses 10.0.1.2 and 10.0.1.129 have been added in the topology, all of them belonging to the same sub-net 10.0.1.0/24 (AS1). Peer 10.0.1.2 is connected through a different connection point than the others to the SDX. Peer 10.0.1.129 is connected through the same connection point as 10.0.1.1 but uses vlan-id 100.

The following part describes the structure of the new attribute proposed for the association between peers and interfaces. It takes as prerequisite that an optional attribute "name" has been added to  "ports" -> "interfaces" in order for the interfaces to be referenced to. The "name"  for "bgpPeers" shall be also optional.

"apps" : {
  "org.onosproject.router" : {
    "bgp" : {
      "bgpPeers" : [
        {
          "name" : "AS1-Router1",
          "ip" : "10.0.1.1",
          "interface" : "AS1-conn1"
  }
]}}}
  • No labels