Small Mosaic


Categories:

books
career
codinghorrors
comics
events
geekstuff
justdont
languages
languages/bash
linkshot
magazines
meta
misctech
movies
nottech
operatingsystems
operatingsystems/linux
operatingsystems/linux/debian
operatingsystems/solaris
paranoidadmin
perl
ruby
security
security/apache
security/tools
serversmells
sites
specifications
sysadmin
tools
tools/commandline
tools/firefox
tools/gui
tools/network
tools/online
tools/online/greasemonkey
unixdaemon

Archives:

April 20084
March 20081
February 20081
January 200815
August 20072
June 20079
May 20076
April 20078
March 200731
February 20073
January 200721
December 20061
November 20064
October 20066
September 200632
August 200617
July 200614
June 20069
May 200613
March 200611
February 200616
January 200611
December 20051
November 20056
October 200519
September 200525
August 200516
July 200516
June 200513
May 20052
April 200519
March 200531
February 200520
January 200531
December 200421
November 200430
October 200432
September 200418
August 20047
July 200414
June 20045

Sat, 09 Oct 2004

WS-Management, an SNMP Replacement?
I hate to jump on any bandwagon that starts at Slashdot, although even a broken clock is right twice a day, but I find myself agreeing with a number of the Slashdot comments made about the new WS-Management spec. Firstly, and most importantly, SNMP is still the most widely used management protocol in production. Secondly it has survived the invention of a number of replacements, WBEM and CIM spring to mind as standards chosen to replace a lot of the functionality it provides; oddly enough those specs were also backed by Microsoft and Sun.

I'd be among the first to agree that SNMP isn't a perfect solution, it has a bad security model, version 3 has never been widely adopted and it can be immensely confusing to set up and run in an enterprise due to the poor documentation and propriety OID layouts. It isn't however going to be easily replaced by an XML/SOAP protocol, even if they get SOAP over UDP working correctly.

SNMP is used in a number of small embedded devices that are limited in memory, CPU and bandwidth. Adding enough of a webservices stack to allow these machines to communicate like this is going to require a pretty serious beefing up of the hardware used in these tasks. As an aside it is quite interesting to note that Cisco, Nortel and Juniper are all absent from that spec, I find it hard to consider any replacement to SNMP that lacks their backing.

I'm all for innovation and progress but lets not try and shoehorn XML and webservices into everything; please.

Like this post? - Digg Me! | Add to del.icio.us! | reddit this!

Posted: 2004/10/09 15:45 | /specifications | Permanent link to this entry | This entry + same date


books career codinghorrors events geekstuff justdont languages/bash linkshot magazines meta misctech movies nottech operatingsystems/linux operatingsystems/linux/debian operatingsystems/solaris perl ruby security security/apache security/tools serversmells sites specifications sysadmin tools/commandline tools/firefox tools/gui tools/network tools/online tools/online/greasemonkey unixdaemon

Copyright © 2000-2005 Dean Wilson XML feed logo