today I tested the new version v1.12.1 and found errors that kept me from upgrading to this version, because I was not able to track down and solve the problem.
Please have a look at the following intstatus.txt examples. The output comes from a nexus 7000 switch.
As you can see the description for the port N7KH1A,Eth10/10.2005 moves to the portname itself which cannot be correct, right?
Another contributor cleaned up a bunch of code the other day and looks like they introduced this bug. I would revert to the nxosscraper.pl from the last version for right now until he can respond, but he's usually pretty quick.
Jonathan
On Nov 14, 2013, at 9:14 AM, "Michael Schmidt" mscsl@users.sf.net wrote:
Hi Jonathan,
today I tested the new version v1.12.1 and found errors that kept me from upgrading to this version, because I was not able to track down and solve the problem.
Please have a look at the following intstatus.txt examples. The output comes from a nexus 7000 switch.
As you can see the description for the port N7KH1A,Eth10/10.2005 moves to the portname itself which cannot be correct, right?
Regards,
Michael
File /opt/netdb/data/intstatus.txt from v1.12 :
NetDB Interface Status Data: (switch,port,status,vlan,description,speed,duplex)
You should be able to do an svn update and pull the latest nxosscraper which should have be fixed for sub-interfaces. Please save your old copy in case there is still a problem, but I think it should be fixed.
Jonathan
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Jonathan,
today I tested the new version v1.12.1 and found errors that kept me from upgrading to this version, because I was not able to track down and solve the problem.
Please have a look at the following intstatus.txt examples. The output comes from a nexus 7000 switch.
As you can see the description for the port N7KH1A,Eth10/10.2005 moves to the portname itself which cannot be correct, right?
Regards,
Michael
File /opt/netdb/data/intstatus.txt from v1.12 :
File /opt/netdb/data/intstatus.txt from v1.12.1 :
Michael,
Another contributor cleaned up a bunch of code the other day and looks like they introduced this bug. I would revert to the nxosscraper.pl from the last version for right now until he can respond, but he's usually pretty quick.
Jonathan
On Nov 14, 2013, at 9:14 AM, "Michael Schmidt" mscsl@users.sf.net wrote:
Michael,
You should be able to do an svn update and pull the latest nxosscraper which should have be fixed for sub-interfaces. Please save your old copy in case there is still a problem, but I think it should be fixed.
Jonathan