Netonix Forums

I have an ongoing issue which seems to be coming more prevalent where all traffic ceases and my WS-24-400A becomes inaccessible on only one VLAN (VLAN1) for an undefined period of time. This could last for just a few minutes or up to an hour. Interestingly, my second VLAN (VLAN2) still functions correctly during this "outage" and the switch is accessible on it. My setup is pretty plain (see screen shots). I have 2 Cisco SFP modules in ports 25-26, which are not in use. The errors appear during the outage. Nothing looks out of ordinary in the log files, but I am yet to examine them closely when the outage occurs.

You do realize that the switch UI/CLI only responds to the Default/Management VLAN which you have chose to leave as VLAN ID 1.

VLAN 1 and VLAN 2 do not talk to each other.

Basically you divided the switch into to logical and separate switches.

If you did assign a "non-rout able" IP to VLAN 2 which that function is primarily for allowing the switch to directly ping devices without having to rely on a router for watchdog.

Something is going weird on your network with all those errors, curious if you have your tower grounding system bonded to your service ground? When these events occur what is the weather like?

Your going to have to better explain your network topography.

Yes, I do understand that VLAN1 and VLAN2 do not talk to each other.
The switch shows no errors until an "outage" occurs. The outage occurs regardless of weather conditions.
The VLAN1 portion of the network is for a business customer with multiple PtP links. At the other end of each PtP link are client workstations...it's very simple and flat.

It should also be noted that I did not have this issue when using an older non-POE HP Procurve switch...

I wish there was something I could say to help you but VLANs and POE have no known bugs and have been tested extensively.

Your going to need to find out what is causing the issues or give us something to look into.

I would start by looking at the logs.

Also I always tell people who have an issue to install the latest version which is v1.3.9rc14 because v1.3.8 is FINAL and no further development is being done on this version where as v1.3.9rcX is still in development.

Also look at the port details on all the interfaces that have these errors, what type of errors are they?

I have attached screen shots of two of the ports. Port23 connects to the Cisco ASR1002 and port 3 powers an AF-24HD. The AF-24HD has ping watchdog enabled and reboots itself during the outage. Any thoughts?

Logs show nothing right now, but an outage has not occurred since I last cleared...

When do you expect 1.3.9 to be final? I might wait it out...

I do not think your problem is a bug in the firmware. The reason is you are doing nothing that thousands of others are not using the switch for and have no issues, including me.

I am the first to admit when we have a bug as other people will tell you.

Personally I think something else is going on with your network.

However my statement holds true that if you have an issue you should always first try the latest code currently in development as the last FINAL version is just that, FINAL and will not be developed further.

v1.3.9rc14 is STABLE, I use it as do many others. You should read the release notes.

The reason I asked about ground was something I learned last night during the storm with static charges. Read this post for my find with wind and grounding: viewtopic.php?f=30&t=1429

I am running the same firmware (1.3.8) at multiple other locations, it looks solid everywhere else. That being the case, I agree with you on the firmware. However, if you think the upgrade might "fix" the issue, I will update.

Any ideas on what else could be causing this?

Interesting post on grounding. I'm not too impressed with the grounding setup at this location and we have plans to improve it. I will take note of weather conditions during the next outage I can catch.

zrob_12 wrote:I am running the same firmware (1.3.8) at multiple other locations, it looks solid everywhere else. That being the case, I agree with you on the firmware. However, if you think the upgrade might "fix" the issue, I will update.

Any ideas on what else could be causing this?

Interesting post on grounding. I'm not too impressed with the grounding setup at this location and we have plans to improve it. I will take note of weather conditions during the next outage I can catch.

The only other thing is always the possibility of a bad unit which is where having a spare unit to swap out and see of the problem persists or remains.