Comware

Can you automate diagnostic testing in the v1910 switch series?
I'm thinking having a switch run three pings every five minutes and logging the results.

Hi"

I don't understand your question.

Can you explain better what you need?

Can you tell a v1910 switch to perform certain tasks at a later time,
and/or repeatedly?
And can those tasks include performing an icmp network probe, i e a "ping".



Hans J. Albertsson
>From my Nexus 5

Why would you want to do this in the first place?

Wouldnt you just monitor the switch is 'alive' from your NMS?

 

If you do need to have some scheduled commands, see if this helps.....

https://www.manualslib.com/manual/904205/Hp-5800-Series.html?page=173#manual

Is that document relevant to v1910?

 

As to why: it would enable you to see if certain routes went down. It would have to log the ping result, too. Or alert me. Which I suppose would be unlikely.

I no longer think it would be feasible.

I only have 1920's and had a quick look and the 'job' command is certainly available, although I must admit I didnt go any further having established that.

 

I personally think you are attacking this from the wrong angle. It should be your central NMS that monitors the general health of your network. Then your NMS should be configured to alert you by whaterever means necessary (visually, audibly, e-mail etc etc).

Is that document relevant to v1910?

 

As to why: it would enable you to see if certain routes went down. It would have to log the ping result, too. Or alert me. Which I suppose would be unlikely.

I no longer think it would be feasible.

Pinging from the NMS only tests the route NMS to switch. And we've had incidents where particular switches lost one particular route for a few minutes. This happens with three different brand switches. So a need exists for automated testing of lots of different routes.

If you are losing routes on a L2 switch then I would be looking at the uplinks and checking these via the NMS - are they flapping / is the any STP recovergence etc.

TIme for me to shoot off home, hope you get to the bottom of the issue, but if you have the problem on three difference switches then my gut feel would be the problem is elsewhere :)

 

 

 

 

Routes on a L2 switch.....have no value, as all forwarding is L2 based , on destination MAC.
The 1910 has limited L3 functionality, maybe you're using it.

You could glue together SNMP query to get routes present,  snmpwalk OID range below gives you routing table size:

$oidrange="-os:.1.3.6.1.2.1.4.21.1.2.0 -op:.1.3.6.1.2.1.4.21.1.3.0"