Goodbye SNMP? Hello, WS-Management

Laoping writes "News.com has a story about a new Web services management specification designed to simplify network administration across a wide range of devices. A bunch of a big tech companies developed it together (Microsoft, Intel, AMD, Dell and Sun). Microsoft will build support for WS-Management into an update to Windows Server, which is due late next year, and in the version of its Microsoft Operations Manager management software due in 2006. The .PDF release, that makes it clear that it is meant to be a Simple Network Management Protocol killer. Now I am all for a replacement for SNMP, but is this the way go?"

Comments

connect the dots

[Doc Ruby]

Maybe it will be OK, if it uses persistent HTTP connections, which allow several requests and replies before terminating the transaction. Otherwise the ancient HTTP/1.0 message model is too limited to map all the messaging topology to the spectrum of object management requirements.

Re:I'm not sold

[nightfire-unique]

I don't mean to pooh pooh this idea just because it's somewhat Windows specific but the only real advantage I see to this over snmp is that the delivery modes are more sophisticated and the data can be organized hierarchally.

The SNMP MIB tree is hierarchical. For example, the "version" parameter of NET-SNMP can be found by querying:

ucdavis.version.versionTag

Furthermore, these names have corresponding OID numbers, which are universally unique.

So why not just add builtin event notification to snmp?

What, like SNMP traps?

Come on.. this stuff ain't new. :)