M
M
murad882014-09-24 21:40:32
SSH
murad88, 2014-09-24 21:40:32

Which way to manage the switch should I choose?

I'm going to write a program in C# to monitor switches (which ports are active, enable/disable a given port, is the cooler running on the switch, etc.).
As I understand it, switches can be managed using the SNMP, Telnet, SSH protocols.
Since I have not encountered similar tasks before, I do not know which one is better to use.
There is also such a moment that .NET does not have built-in support for these protocols, and you will have to use third-party libraries, which may turn out to be crooked.
Would love to hear any advice on this.

Answer the question

In order to leave comments, you need to log in

2 answer(s)
T
throughtheether, 2014-09-25
@murad88

SNMP (start with v2c, implement v3 with enhanced security if possible) for retrieving data like interface statistics, CPU usage, etc. Using SNMP, you can try to change the configuration (enable / disable the interface), but in this case, you should take care of security issues (i.e. use SNMPv3 with authentication and / or encryption). If something cannot be done via SNMP, then use SSH and the corresponding cli commands.
As for telnet, I don't think that this protocol should be used in "production" at all (data is transmitted in clear text).
What switches are used (vendor/line)?

V
Valentine, 2014-09-25
@vvpoloskin

For typical tasks, of course, snmp is better - input is faster, the output is almost structured information. On the more difficult ssh/telnet. But this is if you need to run all sorts of tracers, lookups, pings...

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question