Conference pcbuoa::server_works

    
    
    Let me give this one a try - Chet can bail me out if I lead you astray
    too far ;-). I had an interesting discussion with Bernie a week or so
    ago to explain the issue of what ServerWORKS traps can be forwarded and
    which ones can't.  Here is my understanding...
    
    Seems that the SNMP agent that runs on
    the "client" is responsible for certain extensibility so that functions
    like the ServerWORKS features, beyond SNMP, can be recognized.  While
    the NT and Netware SNMP agents are extensible, they aren't flexible
    enough for ServerWORKS agents to pass information thru them to get to
    the Enterprise Managers like OpenView, etc.  SCO does provide the
    interface to do this. Digital Unix doesn't (yet?).  In fact Bernie said
    they tricked the NT SNMP agent into doing things that it normally
    shouldn't do (ie polling). Had something to do with MIBII compliancy,
    but I'm not sure now what that issue was.
    
    BOTTOM LINE:
    ---------------
    So it all boils down to this: The traps that can be set under
    "Environment" button on the ServerWORKS window (double click a
    ServerWORKS object) can be forwarded to Enterprise Managers.  You must
    also compile at least the two ServerWORKS MIBs - svrmgr.mib and
    svrsys.mib - in the Enterprise Manager.
    
    One exception to all this is PolyCenter NetView- you can plug
    ServerWORKS right into it and it sees all the traps just like you'd see
    in ManageWORKS.
    
    Hope this helps.
    
    
    Gary Olsen
    Atlanta CSC
    
    (How'd I do, Chet?)

    There's information available from the external web site at
    www.windows.digital.com
    
    click on products, and go down to the ServerWORKS section.
    
    
    And an internal site at akin40.ako.dec.com
    
    Click on Digital ServerWORKS.....  In there you will find product
    information and literature as well as kits.
    
    Chet White

    
    regarding my last note, I want to ensure that everyone has the correct
    pointers to get information like this.  We in the support role, are
    constantly trying to find the best way to pass information along, and
    the web is the vehicle of choice.  Understand, though, that a certain
    amount of 'self - suffeciency' is required.  The documents are there
    to read up on and get familiar with.
    
    re: Gary, you done well!!!!!   AS far as I can tell.  
    
    I will ensure that the documents for propagating a trap, and integrate
    an external application are available through the web.
    
    chet

     Chet,
    
        >I will ensure that the documents for propagating a trap, and integrate
        >an external application are available through the web.
    
        Will you put them on the External as well as the internal?
    
        Thanks,
    
        Gary
    

    
    as soon as engineering 'blesses' em as 'released' they can go out to
    the external web.
    
    
    chet

    Please review the two, and send comments back to me.  The integration
    document will become chapter 5 of the manual.....
    
    The other one, can be posted, once it's reviewed and finalized.
    
    chet

    Chet,
    
    Review the current chapter 5 "integration" document. After our
    discussion with Bernie, it seems there are a lot of misleading "sales"
    type statements.
    
    Note: next to last paragraph, page 2:
    	"...Digital servers are fully manageable via Enterprise SNMP
    console manager application".  This is true as far as SNMP is
    concerned, but not true as far as ServerWORKS extensions. That should
    be made clear
    
    Note: 1st paragraph, page 3:
    	"Most enterprise SNMP Manager (sic) allow the user to compile a new
    MIB. After compiling a MIB, the same information that displays in tahe
    ServerWORKS bdrowser can be displayed using another Enterprise manager
    browser."
    	ABSOLUTELY UNTRUE.  Should be changed to say that the same info can
    be displayed for a SCO Unix box with the SW agent, but for NW, NT and
    Digital Unix clients, only SNMP Environment information is available.
    Then explain the agent issue if you want.
    
    Should note that the way this works is after the MIB is compiled, you
    see four alarm thresholds on the console mgr - high, medium, low and
    informational.  They pick up alarms set via ServerWORKS - according to
    the rules and exceptions noted above (environment only except SCO - but
    who uses SCO anymore?)
    
    I'll help if you'd like.
    
    Gary