v1.4.8rcX Bug reports and comments

[tonym]

CISCO-CDP-MIB:
cdpCacheIfIndex and cdpCacheDeviceIndex should be inaccessible (only used for the index)

We have enough info for discovery, but to draw links, we need cdpCacheDevicePort
cdpCacheVersion should be included as well.

[diegoms77]

Since 1.4.7 does not work "/ Tools / Port Bounce"
The log shows that it was executed at the indicated time, but the reality is that the port does NOT turn off the 10 seconds set.


Edit: In 1.4.5 / 1.4.6 it worked fine

[Julian]

Since 1.4.7 does not work "/ Tools / Port Bounce"
The log shows that it was executed at the indicated time, but the reality is that the port does NOT turn off the 10 seconds set.


Edit: In 1.4.5 / 1.4.6 it worked fine

I think you may have a defective port, there - I just verified port bounce as working on more than one model, here.

try following the steps outlined here:

viewtopic.php?f=6&t=2780

You will probably find it beneficial to read that entire thread, too.

Thanks,

Julian

[diegoms77]

Since 1.4.7 does not work "/ Tools / Port Bounce"
The log shows that it was executed at the indicated time, but the reality is that the port does NOT turn off the 10 seconds set.


Edit: In 1.4.5 / 1.4.6 it worked fine

I think you may have a defective port, there - I just verified port bounce as working on more than one model, here.

try following the steps outlined here:

https://forum.netonix.com/viewtopic.php?f=6&t=2780

You will probably find it beneficial to read that entire thread, too.

Thanks,

Julian

Hi, I do not think it's a faulty port, because:
"Power> shutdown time / startup time" works correctly
"Status> port bounce" works correctly
"Status> Errors" without problems
(No extra problem)
Only "DOES NOT work" Tools> Port Bounce Daily at X time
Thanks

[Omniflux]

SNMP issue with CISCO-CDP-MIB:

$ snmpwalk -v2c -c public 192.168.1.20 .

Code: Select all

...
CISCO-STACK-MIB::portDuplex.1 = INTEGER: auto(4)
CISCO-STACK-MIB::portDuplex.2 = INTEGER: half(1)
CISCO-STACK-MIB::portDuplex.3 = INTEGER: auto(4)
CISCO-STACK-MIB::portDuplex.4 = INTEGER: half(1)
CISCO-STACK-MIB::portDuplex.5 = INTEGER: half(1)
CISCO-STACK-MIB::portDuplex.6 = INTEGER: half(1)
CISCO-STACK-MIB::portDuplex.7 = INTEGER: half(1)
CISCO-STACK-MIB::portDuplex.8 = INTEGER: half(1)
CISCO-STACK-MIB::portDuplex.9 = INTEGER: half(1)
CISCO-STACK-MIB::portDuplex.10 = INTEGER: half(1)
CISCO-STACK-MIB::portDuplex.11 = INTEGER: auto(4)
CISCO-STACK-MIB::portDuplex.12 = INTEGER: half(1)
CISCO-STACK-MIB::portDuplex.13 = INTEGER: half(1)
CISCO-STACK-MIB::portDuplex.14 = INTEGER: half(1)
CISCO-CDP-MIB::cdpCacheIfIndex.11.1 = INTEGER: 11
CISCO-CDP-MIB::cdpCacheIfIndex.11.2 = INTEGER: 11
CISCO-CDP-MIB::cdpCacheIfIndex.1.3 = INTEGER: 1
Error: OID not increasing: CISCO-CDP-MIB::cdpCacheIfIndex.11.2
 >= CISCO-CDP-MIB::cdpCacheIfIndex.1.3

[Omniflux]

Another SNMP issue...

$ snmpget -v2c -c public 192.168.1.20 IF-MIB::ifMtu.1
IF-MIB::ifSpeed.1 = Gauge32: 1000000000

[ellisway]

hi all doing some testing of erps g8032 with other vendor kit in a ring of 3 switches

netonix ws-12-250A
extreme x460-24t
alcatel os6250-8m


and during the testing came accross the above situation
where erps thinks its forwarding traffic on a port that is down

regards

ellis

[BangorIT]

Hello,

We have a new installation with 1.4.8rc7 on a WS-8-150-AC. Over the weekend, the customer reported they had no internet and I found that the switch was rebooting on its own. I troubleshooted to 1 cable run that has the green pair with abnormal termination. I unplugged that cable and everything works fine. After testing the cable a few times trying to repair, the switch would reboot a few seconds after starting the cable diagnostic. Is this a bug or normal for these devices?

[Julian]

Hello,

We have a new installation with 1.4.8rc7 on a WS-8-150-AC. Over the weekend, the customer reported they had no internet and I found that the switch was rebooting on its own. I troubleshooted to 1 cable run that has the green pair with abnormal termination. I unplugged that cable and everything works fine. After testing the cable a few times trying to repair, the switch would reboot a few seconds after starting the cable diagnostic. Is this a bug or normal for these devices?

This sounds like a hardware issue - it was leading you around the nose by not rebooting after you unplugged that one cable. Sorry for the trouble, but your switch is defective.

We fix this issue free, please replace and RMA. Contact me off list if you would like steps to test for this defect in your replacement unit, the information is in my signature.

[jpaine619]

Minor bug, but a bug....

When using the ping tool, hitting the cancel button does nothing.

I ran a ping test the other day, and meant to type in 10 in the count field, but fat fingered it and typed 100. When I noticed (the ping test had started), I hit cancel and...... nothing happened. The test continued all the way to 100 packets.

I tested a couple of more times using lower numbers, and in all cases, the ping test will not terminate after hitting "cancel".