Hi Terry,
Here is the exact configuration I used for NOX (RouteFlow). My controller was
192.168.1.17, my ip was 192.168.1.100.
openflow
enable
controller-id 2 ip 192.168.1.17 controller-interface vlan 3
instance "routeflow"
listen-port
member vlan 1
controller-id 2
connection-interruption-mode fail-standalone
enable
exit
vlan 1
name "DEFAULT_VLAN"
no untagged 1-2
untagged 3-24
ip address dhcp-bootp
exit
vlan 3
name "CNTL_VLAN"
untagged 2
ip address 192.168.1.100 255.255.255.0
exit
On Feb 21, 2013, at 8:11 PM, terryxing <xingtia...@gmail.com> wrote:
> thanks Noble
>
> do you have to add that port into vlan 10? untagged or tagged ?
>
> Thanks
>
> On Feb 21, 2013 11:09 PM, "Steve Noble" <sno...@sonn.com> wrote:
> I think you cannot. I think i used vlan 10.
>
> On Feb 21, 2013 12:14 PM, "terryxing" <xingtia...@gmail.com> wrote:
> BTW, I can understand that controller communication needs separate VLAN. Can
> I use VLAN 1 as the VLAN to communicate with controller from OFS ?
>
> The controller use port 12 to connect to the HP OFS. Should I add the port
> into the specific VLAN ? like vlan 1 ? Port 12 should be added as untagged or
> tagged ?
>
> I just wanna make controller and OFS connected first.
>
> Thanks very much.
>
> On Thu, Feb 21, 2013 at 9:57 AM, terryxing <xingtia...@gmail.com> wrote:
> Thanks very much for your timely reply.
>
> The thing is, I use port 12 as the port for communicating with controller. I
> need to specify a vlan for communication betwee OFS and POX. I used VLAN 1,
> but the status is still disconnected. They can ping each other but can not
> connected.
>
> Another weird thing is that I use port 1 and 2 for connecting two physical
> servers so that VMs can talk to each other. As I tested yesterday, the weird
> thing is, even I did not run the openflow, two VMs can still ping each other
> through port 1 and 2. Based on my understanding, if I enabled openflow on
> the HP switch, without running application on controller, like l2_learning
> switch, the traffic of port 1 and 2 can not be forwarded.
>
> Any thought ?
>
> Thanks very much.
>
>
> On Wed, Feb 20, 2013 at 7:09 PM, Steve Noble <sno...@sonn.com> wrote:
> Hi Terry,
>
> When I did my testing I used the configuration outlined in this post
>
> http://www.routeranalysis.com/state-of-openflow-2012-day-56-notes-on-hp/
>
> Let me know of that helps.
> On Feb 20, 2013 4:01 PM, "terryxing" <xingtia...@gmail.com> wrote:
> Dear All,
>
> I am configuring the HP 3500yl openflow switch. I already burn the firmware
> K15.10 version into the secondary OS of the HP openflow switch and boot as
> the secondary OS. I think the openflow is already successfully installed on
> the HP switch since I can use openflow CLI to configure. The thing is , I can
> not make my openflow swtich talk to the controller.
>
> I configure the 192.168.1.66 as the ip of HP OFS and 192.168.1.60 for the POX
> controller as a virtual machine (the physical server is connected to HP OFS)
> They can ping each other which means the connection is good.
>
> But when I configure the OFS by following the manual for K15.10 version. I
> can not make OFS and POX connected. I configure the instance as aggregate
> mode but I dont know how can I specific the vlan for controller and vlan for
> management. The POX is connecting to HP OFS through port 12 which belongs to
> VLAN1 (the default VLAN). Also, in the manual, there is one command line
> which can not be executed, which is "openflow instance aggregate member vlan
> vlan-id" There is not member key words.
>
> Can anyone help ? I have been struggling on this for 3 days.
>
> Thanks very much.
>
> --
> Best regards,
>
>
>
> Terry
>
> _______________________________________________
> openflow-discuss mailing list
> openflow-discuss@lists.stanford.edu
> https://mailman.stanford.edu/mailman/listinfo/openflow-discuss
>
>
>
>
> --
> Best regards,
>
> Terry
>
>
>
>
> --
> Best regards,
>
> Terry
_______________________________________________
openflow-discuss mailing list
openflow-discuss@lists.stanford.edu
https://mailman.stanford.edu/mailman/listinfo/openflow-discuss
