-
Notifications
You must be signed in to change notification settings - Fork 117
OFSW management port requirements
Establish the operational user stories for utilizing management ports in the OpenFlow switch. Articulate the requirements that serve to fulfill them.
The OpenFlow controller must handle one, and only one IPv4 per OpenFlow switch. This assures simplicity for programming and observing the OpenFlow switch.
The OpenFlow switch must have two management ports. This allows redundant physical connectivity for protecting against port, cable, direct upstream port or network device failure.
IP connectivity to the OpenFlow switch management address must remain stable, through forward transitions events between the two management ports. This assures that the control plane of the OpenFlow switch remains stable through a physical connectivity issue adjacent to any of the two management ports.
The upstream ports where the OpenFlow management ports connect to, must not require any special configuration besside ordinary host port configuration. This assures simplicity in the upstream network devices configuration.
The OpenFlow switch must be able to acquire IP configuration information using DHCP on the management ports. The MAC address of the management ports must also be known. This assures the OpenFlow switch can be provisioned automatically upon installation.
OpenFlow switches must allow management ports connecting using optic fiber media, as well as copper cables. This assures management plane connectivity across longer distances.
It is assumed that at factory defaults, some OpenFlow switches have a single management port with its associated network stack. Other OpenFlow switches have two management ports with individual independent network stacks. These premises, together with the user stories, shape the requirements of the next section.
The user stories state the use of one IP address per OpenFlow switch. In addition they require two ports for the management plane, and basic host-port configuration in the network devices upstream. A bootstrapping mechanism must be available for provisioning, and different connectivity media must be supported. The following requirements fulfill these user stories.
The OpenFlow switch has two management physical ports, supporting 2 different connectivity media each, copper and fiber.
The MAC addresses of the management ports must be externally individually stamped in the OpenFlow switch chassis via a barcode or QR code. Using UPC-A and UPC-E encoding for barcode and ISO/IEC 18004:2015 for QRcodes.
The management ports must have DHCP client enabled when at factory default, or when a factory reset is performed.
The two management ports must be allowed to be bonded together in Active-Backup. Their expected behaviour is:
- At any given time, one port is Active, the other is Backup;
- Either ports accepts ingress packets;
- When the carrier in the Active port is up, only the Active egreesses sent packets;
- When the carrier in the Active port is down, the Backup egresses sent packets;
- Whenever packet egress changes between ports, gratuitous ARPs must be sent;
When bonding the two management ports:
- The MAC address of the lowest numbered management port is used;
- The lowest numbered management port takes the Active role;
When bonding between a management port and a data plane port, the management port is considered the lowest numbered port.