v1.2.2 FINAL bug reports and comments

[jportman]

Been using dude 4.x for four years. Never did use 3.x

In addition, 1.2.2 broke my rancid script as well.

[Eric Stern]

I tried 4.0beta3, it seems to work fine too. If you can figure out a way for me to recreate the problem I'll look into it further.

[jportman]

I downgraded to 1.2.0rc8 and my problems disappeared. I am unsure of the cause. I have hundreds of devices being monitored by dude, using v1 and v2 snmp.
Never seen this kind of behaviour before. The interface list keeps updating and never has the full list of interfaces when you 'add a link' between the switch and some other device. The actual graph, it turns out, seems fine. The 'real time display' always shows 0bps.

Just fyi,
JP

[sirhc]

Is anyone else having issues with v1.2.2 and SNMP?

Is anyone else using v1.2.2 and the Dude?

Now keep in mind v1.2.2 does not support SNMP v1

PLEASE REPORT EITHER WAY, PROBLEM OR NO PROBLEM

[jportman]

V 1.2.0 and V 1.2.2 will not get a DHCP address on an SFP port from a cold boot. I am trying V 1.1.8 to see if it is there also.

I suspect that the SFP init happens after the dhcp request in the boot sequence?

On cold boot, the unit can be reached at 192.168.1.20 every time.

[sirhc]

I forwarded this post Eric to take a look at.

[jportman]

I can verify that DHCP client does not work at all on 250-AC-12 or 250-AC on version 1.2.2 on any port



You can change it from the interface and it will acquire a DHCP address. Upon reboot it never does again.

JP

[Eric Stern]

I tested 1.2.2 in the lab with a WS-12-250-AC. I tested ports 1 and 12 and both SFP ports, with both cold boots and reboots. DHCP worked perfectly every time.

You may need to do a wireshark capture to see what is going wrong with yours.

[jportman]

I pulled a perfectly working TSPro and put this in its place. Same Port. SameDHCP server. No go.
It's directly connected to a Mikrotik router. Nothing in between.
I'm not a complete moron. I'm only reporting the behaviour I observe.

And, on a side note, it appears that Vlan trunking is broken as well. :)

[sirhc]

I am using VLAN trunking with v1.2.2 and it works for me?

Can anyone else please confirm what they are seeing as to VLAN trunking and if you have your switch getting an IP address OK?

I can not confirm the DHCP with my WISP deployments as I only use static IPs