Opendaylight and snmp4sdn plugin work or not - Please advise
|
dangerzone ar <dangerzonen@...>
I'm testing SDN controller ODL and looking onto snmp support where there is a plugin of snmp4sdn under ODL project. I follow the guideline ... create switch list db file in csv and vendor specific file in xml. I able to read and print the db This is my install snmp4sdn 296 | Active | 80 | 0.3.4.Beryllium-SR4 | snmp4sdn plugin But when i do curl of topodiscover or topodiscoverswitch...i got empty rpc get-node-list is called, node list: I have tested with Beryllium and Carbon... both same issue. May I know if anyone have successfully done it? I have follow the instruction and facing some issues such as no topology/devices discover via curl even do i able to print all the devices list (sample csv) on the terminal. The documentation does not help much on how I can do the troubleshooting. If anyone have successfully done odl with snmp4sdn please advise me further... I'm not able to do it because of this block... Appreciate someone to clarify and help. Thank you.
|
|
|
|
Yi-Ling Hsieh
Hi,
It looks you successfully “create switch list db file in csv”, but note that the content such as switch IP address needs to be assigned correctly because snmp4sdn query the switch via the IP address. Besides the IP address, snmp community should be correctly, too.
Christine
From: snmp4sdn-dev-bounces@... [mailto:snmp4sdn-dev-bounces@...]
On Behalf Of dangerzone ar
I'm testing SDN controller ODL and looking onto snmp support where there is a plugin of snmp4sdn under ODL project. I follow the guideline ... create switch list db file in csv and vendor specific file in xml. I able to read and print the db This is my install snmp4sdn 296 | Active | 80 | 0.3.4.Beryllium-SR4 | snmp4sdn plugin But when i do curl of topodiscover or topodiscoverswitch...i got empty rpc get-node-list is called, node list: I have tested with Beryllium and Carbon... both same issue. May I know if anyone have successfully done it? I have follow the instruction and facing some issues such as no topology/devices discover via curl even do i able to print all the devices list (sample csv) on the terminal. The documentation does not help much on how I can do the troubleshooting. If anyone have successfully done odl with snmp4sdn please advise me further... I'm not able to do it because of this block... Appreciate someone to clarify and help. Thank you. -- 本信件可能包含工研院機密資訊，非指定之收件者，請勿使用或揭露本信件內容，並請銷毀此信件。 This email may contain confidential information. Please do not use or disclose it in any way and delete it if you are not the intended recipient.
|
|
|
|
dangerzone ar <dangerzonen@...>
Hi Christine...thanks for your response. As per guideline i follow exactly as require..the content of the db csv file... i did the same as the sample file. I dont understand how to assign the ip address correctly..what do you mean?..is the ip from the example wrong?... just i know what ever info in the csv file (hostname/ip address/snmp community) is just a sample...and i don't really have those devices in my real network... Do u mean i need to have actual snmp device that odl can ping and reachable..for snmp in odl to work? Have you test it?.. Pls advise.. i would like to see odl in action for snmp device...thank you. On Tue, 16 Apr 2019 10:12 , <ylhsieh@...> wrote
|
|
|
|
Yi-Ling Hsieh
> Do u mean i need to have actual snmp device that odl can ping and reachable? Have you test it? Yes, snmp4sdn has been tested with actual snmp devices. More specifically, people use snmp4sdn for legacy Ethernet switch. You need actual legacy Ethernet switch and then the steps describe in snmp4sdn user guide will work.
> I dont understand how to assign the ip address correctly..what do you mean? For the commands you tried: it means snmp4sdn will query the devices listed in the snmp4sdn_swdb.csv (ie. the devices you see using the command “snmp4sdn:printdb”, in general case they are legacy Ethernet switches) If there’s no actual devices, it’s normal that “topodiscover” and “topodiscoverswitches” find nothing.
Christine
From: dangerzone ar [mailto:dangerzonen@...]
Hi Christine...thanks for your response. As per guideline i follow exactly as require..the content of the db csv file... i did the same as the sample file. I dont understand how to assign the ip address correctly..what do you mean?..is the ip from the example wrong?... just i know what ever info in the csv file (hostname/ip address/snmp community) is just a sample...and i don't really have those devices in my real network...
Do u mean i need to have actual snmp device that odl can ping and reachable..for snmp in odl to work? Have you test it?.. Pls advise.. i would like to see odl in action for snmp device...thank you.
On Tue, 16 Apr 2019 10:12 , <ylhsieh@...> wrote
-- 本信件可能包含工研院機密資訊，非指定之收件者，請勿使用或揭露本信件內容，並請銷毀此信件。 This email may contain confidential information. Please do not use or disclose it in any way and delete it if you are not the intended recipient.
|
|
|
|
dangerzone ar <dangerzonen@...>
Hi... What i understand now..to test odl snmp plugin..i need to have live ip device that snmp enable...am i right...Can i just simulate snmp device (cisco) on gns3 and test it with odl? Thanks
On Wed, 17 Apr 2019 19:24 , <ylhsieh@...> wrote:
|
|
|
|
Yi-Ling Hsieh
To see the topology among devices, the required conditions: 1. device has IP address that ODL can reach 2. device supports snmp 3. device supports lldp (so that snmp4sdn can get the topology among devices)
Christine
From: dangerzone ar [mailto:dangerzonen@...]
Hi... What i understand now..to test odl snmp plugin..i need to have live ip device that snmp enable...am i right...Can i just simulate snmp device (cisco) on gns3 and test it with odl? Thanks
On Wed, 17 Apr 2019 19:24 , <ylhsieh@...> wrote:
-- 本信件可能包含工研院機密資訊，非指定之收件者，請勿使用或揭露本信件內容，並請銷毀此信件。 This email may contain confidential information. Please do not use or disclose it in any way and delete it if you are not the intended recipient.
|
|
|
|
dangerzone ar <dangerzonen@...>
Noted and thank you. I will tried it again and simulate the devices in GNS3. I will update and share my finding later. Thank you
On Wed, Apr 17, 2019 at 8:14 PM <ylhsieh@...> wrote:
|
|
|