For more details, please see ourCookie Policy.


DevNet Documents

Video: Connect Brocade SDN Controller and HP ProCurve/ProVision 2920 Switch

by Anonymous ‎04-11-2015 03:17 PM - edited ‎06-26-2015 03:04 PM (3,639 Views)

This video shows how to connect HP ProCurve/ProVision 2920 Switch to Brocade SDN Controller.

 

 

 

HP ProCurve/ProVision Configuration File:

 

HP-2920-48G(config)# show run
Running configuration:
; J9728A Configuration Editor; Created on release #WB.15.16.0006
; Ver #06:0c.fc.f3.ff.35.0d:c2
hostname "HP-2920-48G"
module 1 type j9728a
snmp-server community "public" unrestricted
openflow
   controller-id 1 ip 172.22.19.67 controller-interface vlan 1
   instance "bvc"
      listen-port
      member vlan 5
      controller-id 1
      enable
      exit
   enable
   exit
oobm
   ip address dhcp-bootp
   exit
vlan 1
   name "DEFAULT_VLAN"
   no untagged 5-10
   untagged 1-4,11-48,A1-A2,B1-B2
   ip address dhcp-bootp
   exit
vlan 5
   name "Openflow-ports"
   untagged 5-10
   ip address 10.1.1.1 255.255.255.0
   exit
HP-2920-48G(config)#

 

Video Transcript:

 

00:00:00.229 --> 00:00:03.760
other today we're gonna teach you how to
connect the HP pro vision

00:00:03.760 --> 00:00:10.000
2920 to the Brocade by a controller okay
so here we are connected to $29.20

00:00:10.000 --> 00:00:14.269
we're going into the global config mode
then we're going to define our

00:00:14.269 --> 00:00:17.720
connection to the BBC so going to find a
controller

00:00:17.720 --> 00:00:21.500
we're gonna give a controller id: one
we're gonna give the IP address OVR BBC

00:00:21.500 --> 00:00:24.910
and then we're going to indicate the
communications OpenFlow protocol

00:00:24.910 --> 00:00:27.769
communications with the BBC will be over
the land one

00:00:27.769 --> 00:00:31.820
they're gonna enter the OpenFlow
sub-contract mode I'm going to find an

00:00:31.820 --> 00:00:33.399
instance name to BBC

00:00:33.399 --> 00:00:39.760
in there were going to to find a listen
port really little faulted 6633 but

00:00:39.760 --> 00:00:41.870
that's where you would enter a different
port

00:00:41.870 --> 00:00:45.360
we're gonna indicate that any stations

00:00:45.360 --> 00:00:48.520
on that are being controlled we'll be on

00:00:48.520 --> 00:00:52.430
wheel and five we're gonna indicate that
the controller

00:00:52.430 --> 00:00:56.000
is in fact the one we defined earlier
which is our BBC controller id: one

00:00:56.000 --> 00:01:00.739
refined version of OpenFlow which were
gonna leave the fall which is 1.0 but it

00:01:00.739 --> 00:01:02.719
here that you were changed to 1.3

00:01:02.719 --> 00:01:06.470
then

00:01:06.470 --> 00:01:09.909
we're gonna go ahead and enable that and
exit out this

00:01:09.909 --> 00:01:13.780
abode and then we're going to unable

00:01:13.780 --> 00:01:20.780
open flowing exit out about that so then
we're going to define

00:01:20.920 --> 00:01:24.060
ports 5 through 10 to be on people and
five

00:01:24.060 --> 00:01:29.100
so that's where we're gonna connector
test stations and then we're going to

00:01:29.100 --> 00:01:30.159
define the subnet

00:01:30.159 --> 00:01:34.280
over IP addresses that will be given out
to any station to connect

00:01:34.280 --> 00:01:37.970
sports but in the tent up on top 10

00:01:37.970 --> 00:01:42.250
on range

00:01:42.250 --> 00:01:44.300
really were setting up the veal and five
here

00:01:44.300 --> 00:01:49.730
or just gonna give it

00:01:49.730 --> 00:01:53.630
name OpenFlow to more he's overflow
ports to

00:01:53.630 --> 00:01:58.170
more reasonably on track case let's
commit your changes but during a break

00:01:58.170 --> 00:01:58.590
from

00:01:58.590 --> 00:02:02.490
okay on the 29 $20 let's just validate
are configured

00:02:02.490 --> 00:02:05.590
so here we are on the 29 $20 we're gonna
do a show

00:02:05.590 --> 00:02:10.080
OpenFlow and that shows us that there is
one instance BBC

00:02:10.080 --> 00:02:13.870
atop it has some hardware and software
flows in the versions 1.0

00:02:13.870 --> 00:02:17.970
what show that instance that BBC
instance and get some more details you

00:02:17.970 --> 00:02:21.330
can see the member list is on the line 5
you can see down here the parliament's

00:02:21.330 --> 00:02:22.540
connected an active

00:02:22.540 --> 00:02:27.280
arm and then we're gonna show the
running-config which importantly here it

00:02:27.280 --> 00:02:31.310
shows the instanceof BBC to listen port
call a configuration that we set up

00:02:31.310 --> 00:02:34.970
is there arm so we can see that we have

00:02:34.970 --> 00:02:41.030
the configuration in place

00:02:41.030 --> 00:02:41.880
so let's go

00:02:41.880 --> 00:02:46.720
can actually validate connection okay so
the valid connection

00:02:46.720 --> 00:02:51.450
were back on the BBC I'm we're gonna go
ahead and login

00:02:51.450 --> 00:02:58.450
to the BBC with admin admin months we've
logged in we're gonna look at the top

00:02:59.040 --> 00:02:59.630
policy

00:02:59.630 --> 00:03:03.020
um up and operate corn you can see a
picture of our setup

00:03:03.020 --> 00:03:06.140
the gray and blue wires are stations

00:03:06.140 --> 00:03:09.350
and yellow wire connects us to the BBC

00:03:09.350 --> 00:03:12.680
arm so you can see the Graham blue wires

00:03:12.680 --> 00:03:17.260
our imports 5&7 which remember 5 through
10 percent up for stations

00:03:17.260 --> 00:03:21.030
I mean what we're doing here is we're
just poking around in the BBC

00:03:21.030 --> 00:03:24.640
to validate that in fact the topology
shows the switch

00:03:24.640 --> 00:03:27.690
and the stations and that their nodes
also show that

00:03:27.690 --> 00:03:28.080
as well

Contributors