Correct. 208.77.78.155 is the ip address for the switch. Here is part of
the config file for reference
vlan 1922
name "managment"
untagged 1,21-24
ip address 208.77.78.155 255.255.255.248
ip access-group "40" out
exit
vlan 9
name "openflow"
untagged 5-10
no ip address
exit
gvrp
power-over-ethernet pre-std-detect
ip ssh filetransfer
ip route 0.0.0.0 0.0.0.0 vlan 1922
openflow
vlan 9
enable
controller "tcp:208.77.78.134:6633" listener "ptcp:6633"
exit
-----Original Message-----
From: Aaron Rosen [mailto:aro...@clemson.edu]
Sent: Thursday, March 01, 2012 9:19 AM
To: Elias Paz
Cc: Paul Chang; openflow-discuss@lists.stanford.edu
Subject: Re: [openflow-discuss] OpenFlow Switch Configuration
208.77.78.155 is the ip address of your switch correct? Also, is
OpenFlow enabled for this vlan which you added the listener? openflow
<vlan> enable .
Aaron
On Thu, Mar 1, 2012 at 10:46 AM, Elias Paz <nmeli...@unm.edu> wrote:
> Sorry my mistake
> I tried
> telnet 208.77.78.155 6633 and get
>
> Trying 208.77.78.155...
> telnet: Unable to connect to remote host: Connection refused
>
>
> -----Original Message-----
> From: openflow-discuss-boun...@lists.stanford.edu
> [mailto:openflow-discuss-boun...@lists.stanford.edu] On Behalf Of Elias
Paz
> Sent: Thursday, March 01, 2012 8:44 AM
> To: 'Aaron Rosen'
> Cc: 'Paul Chang'; openflow-discuss@lists.stanford.edu
> Subject: Re: [openflow-discuss] OpenFlow Switch Configuration
>
> I can't telnet into that port
> nmeliasp@openflow:~$ telnet 208.77.78.155:6633
> telnet: could not resolve 208.77.78.155:6633/telnet: Name or service not
> known
>
> Also when I run
> ./nox_core -i ptcp:6633 routing
>
> I get this output
> 00001|openflow|WARN:stream: send error: Broken pipe
> 00002|nox|WARN:Error sending features request: Broken pipe
>
>
>
> -----Original Message-----
> From: Aaron Rosen [mailto:aro...@clemson.edu]
> Sent: Wednesday, February 29, 2012 10:37 AM
> To: Elias Paz
> Cc: openflow-discuss@lists.stanford.edu; Paul Chang
> Subject: Re: [openflow-discuss] OpenFlow Switch Configuration
>
> Okay, so in the case of a listener port the switch will bind on that port.
>
> Can you do telnet <switch_ip> <tcp_port>
>
> Where tcp_port coordinates to the port you used in the command below.
>
> openflow <vlan_id> listener ptcp:<tcp_port>
>
>
>
> On Wed, Feb 29, 2012 at 12:27 PM, Elias Paz <nmeli...@unm.edu> wrote:
>> Oops sorry about that. So after doing this I can see the switch trying to
>> connect like you said.
>>
>> listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes
>> 09:37:37.107940 IP openflow.unm.edu.60544 > 208.77.78.155.6633: Flags
[S],
>> seq 4266433666, win 5840, options [mss 1460,sackOK,TS val 1140247971 ecr
>> 0,nop,wscale 7], length 0
>> 09:37:37.108462 IP 208.77.78.155.6633 > openflow.unm.edu.60544: Flags
> [R.],
>> seq 0, ack 4266433667, win 0, length 0
>>
>> However I still get this message from the controller
>> dpctl: failed to send packet to switch: Connection refused.
>>
>> Is this a switch configuration issue?
>>
>> -----Original Message-----
>> From: Aaron Rosen [mailto:aro...@clemson.edu]
>> Sent: Wednesday, February 29, 2012 10:17 AM
>> To: Elias Paz
>> Cc: OpenFlow Discuss
>> Subject: Re: [openflow-discuss] OpenFlow Switch Configuration
>>
>> You want to use eth0 or whatever interface the switch would talk to
>> your computer over, not $IFACE.
>>
>> Aaron
>>
>> P.S: keep the list CC'ed so others could help as well.
>>
>> On Wed, Feb 29, 2012 at 12:04 PM, Elias Paz <nmeli...@unm.edu> wrote:
>>> Hmmm I tried this and this is the output I get...
>>>
>>> root@openflow:/opt/openflow/utilities# tcpdump -i $IFACE tcp port 6633
>>> tcpdump: tcp: No such device exists
>>> (SIOCGIFHWADDR: No such device)
>>>
>>>
>>> -----Original Message-----
>>> From: Aaron Rosen [mailto:aro...@clemson.edu]
>>> Sent: Wednesday, February 29, 2012 9:47 AM
>>> To: Elias Paz
>>> Cc: OpenFlow Discuss
>>> Subject: Re: [openflow-discuss] OpenFlow Switch Configuration
>>>
>>> The switch does not bind on port 6633 the controller does. The switch
>>> does a connect to the controller. If you run `tcpdump -i $IFACE tcp
>>> port 6633` on the machine that you pointed your switch to you should
>>> see the switch trying to connect.
>>>
>>> Aaron
>>>
>>> On Wed, Feb 29, 2012 at 11:35 AM, Elias Paz <nmeli...@unm.edu> wrote:
>>>> Unfortunately I've gone through this and I still cant find my problem.
>>> When
>>>> I was trying to connect NOX to my switches, I did a scan of open ports
>> and
>>>> port 6633 was closed. Is there anything that I have to enable on the
>>> switch
>>>> to open this port up?
>>>>
>>>>
>>>> -----Original Message-----
>>>> From: Aaron Rosen [mailto:aro...@clemson.edu]
>>>> Sent: Wednesday, February 29, 2012 9:31 AM
>>>> To: Elias Paz
>>>> Cc: openflow-discuss@lists.stanford.edu
>>>> Subject: Re: [openflow-discuss] OpenFlow Switch Configuration
>>>>
>>>> This should probably help you out:
>>>> http://www.openflow.org/wk/index.php/Configuring_HP_Procurve
>>>>
>>>> Aaron
>>>>
>>>>
>>>> On Wed, Feb 29, 2012 at 11:07 AM, Elias Paz <nmeli...@unm.edu> wrote:
>>>>> Hello,
>>>>>
>>>>> I am in the beginning stages of implementing an OpenFLow network on
our
>>>>> campus. I am having a configuration issue with my switch. I am using
an
>>> HP
>>>>> ProCurve 3500 yl. I am having trouble connecting to my NOX server.
I've
>>>>> discovered that the NOX is running correctly which leaves a possible
>>>>> configuration issue with my switch. Can someone help me out with this?
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Thanks in advance,
>>>>>
>>>>> Elias Paz
>>>>>
>>>>> UNM-IT
>>>>>
>>>>> Data Network Assistant
>>>>>
>>>>> nmeli...@unm.edu
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> openflow-discuss mailing list
>>>>> openflow-discuss@lists.stanford.edu
>>>>> https://mailman.stanford.edu/mailman/listinfo/openflow-discuss
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Aaron O. Rosen
>>>> Masters Student - Network Communication
>>>> 306B Fluor Daniel
>>>>
>>>
>>>
>>>
>>> --
>>> Aaron O. Rosen
>>> Masters Student - Network Communication
>>> 306B Fluor Daniel
>>>
>>
>>
>>
>> --
>> Aaron O. Rosen
>> Masters Student - Network Communication
>> 306B Fluor Daniel
>>
>
>
>
> --
> Aaron O. Rosen
> Masters Student - Network Communication
> 306B Fluor Daniel
>
> _______________________________________________
> openflow-discuss mailing list
> openflow-discuss@lists.stanford.edu
> https://mailman.stanford.edu/mailman/listinfo/openflow-discuss
>
--
Aaron O. Rosen
Masters Student - Network Communication
306B Fluor Daniel
_______________________________________________
openflow-discuss mailing list
openflow-discuss@lists.stanford.edu
https://mailman.stanford.edu/mailman/listinfo/openflow-discuss
