- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
Management IP goes offline with OpenFlow is enabled
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The management IP on the M4300 goes offline when OpenFlow is enabled.
(SW) #ping 198.8.8.205
Pinging 198.8.8.205 with 0 bytes of data
Reply From 198.8.8.205: icmp_seq = 0. time= 1 msec.seq = 1. time <1 msec.
Reply From 198.8.8.205: icmp_seq = 2. time <1 msec.
----198.8.8.205 PING statistics----
3 packets transmitted, 3 packets received, 0% packet loss
round-trip (msec) min/avg/max = <1/<1/1
(SW) #configure
(SW) (Config)#openflow enable
(SW) (Config)#1970-01-01T01:10:10Z|00076|rconn|INFO|fastpath<->tcp:198.8.8.205:6633: connecting...
1970-01-01T01:10:10Z|00077|rconn|INFO|fastpath<->tcp:198.8.8.205:6633: connected
(SW) (Config)#exit
(SW) #ping 198.8.8.205
Pinging 198.8.8.205 with 0 bytes of data
1970-01-01T01:10:20Z|00078|rconn|ERR|fastpath<->tcp:198.8.8.205:6633: no response to inactivity probe after 5 seconds, disconnecting
1970-01-01T01:10:20Z|00079|connmgr|INFO|fastpath<->tcp:198.8.8.205:6633: 1 flow_mods 9 s ago (1 adds)
1970-01-01T01:10:21Z|00080|rconn|INFO|fastpath<->tcp:198.8.8.205:6633: connecting...
1970-01-01T01:10:22Z|00081|rconn|INFO|fastpath<->tcp:198.8.8.205:6633: connection timed out
1970-01-01T01:10:22Z|00082|rconn|INFO|fastpath<->tcp:198.8.8.205:6633: waiting 2 seconds before reconnect
1970-01-01T01:10:24Z|00083|rconn|INFO|fastpath<->tcp:198.8.8.205:6633: connecting...
1970-01-01T01:10:26Z|00084|rconn|INFO|fastpath<->tcp:198.8.8.205:6633: connection timed out
1970-01-01T01:10:26Z|00085|rconn|INFO|fastpath<->tcp:198.8.8.205:6633: waiting 4 seconds before reconnect
----198.8.8.205 PING statistics----
3 packets transmitted, 0 packets received, 100% packet loss
round-trip (msec) min/avg/max = <1/<1/<1
Solved! Go to Solution.
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I understand why now. The SDN Controller take control of the ports once connected and the connection drops. Best to access the SDN Controller via the OOB port. The Netgear M4300 documentation is excellent in general except when it comes to OpenFlow, it is like they want to keep it hidden for some unknown reason. Like anything, it is not difficult once you understand how. I put a primer on how to configure OpenFlow on my website:
http://www.obriain.com/primers/netgear_M4300_OpenFlow_Config.php
All Replies
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I understand why now. The SDN Controller take control of the ports once connected and the connection drops. Best to access the SDN Controller via the OOB port. The Netgear M4300 documentation is excellent in general except when it comes to OpenFlow, it is like they want to keep it hidden for some unknown reason. Like anything, it is not difficult once you understand how. I put a primer on how to configure OpenFlow on my website:
http://www.obriain.com/primers/netgear_M4300_OpenFlow_Config.php