[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference pcbuoa::server_works

Title:Server_works
Moderator:PCBUOA::IS_SYSTEM
Created:Fri Jun 30 1995
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:291
Total number of notes:1063

224.0. "SW only sees Public SNMP Community" by ALFSS2::OLSEN_G (Hey y'all, how y'all doin'?) Mon Mar 10 1997 12:12

    Customer is trying to integrate serverworks and NetView. Within
    netview, he sees the yellow Digital Server icon and, when the server
    he's browsing is in the public snmp community, it works fine. If he
    changes the community name to something else, (NT - changes the
    community name in snmp service) then he can only; see the host name and
    ip address.
    
    I'm sure he didn't change something.
    
    In Manageworks/serverworks - I look at General Properties on an agent
    that shows up and I see an option to change the community name.
    
    ---Is that changing the community name on the remote agent?
    
    He says in Netview he doesn't see that and there's functionality that's
    missing.  
    
    Questions:
    
    1. Question above on changing the community name 
    2. What pieces need to be changed to set a new community name?
    	I assume change the NT SNMP Service params AND change the community
        name on the NT SW Agent.  Details?
    
    3. Surely, SW doesn't restrict them to Public? the SW Readme.txt file
       says you; can use any community name.
    
    Thanks in advance,
    
    Gary
T.RTitleUserPersonal
Name		DateLines
224.1Community Name setup for Security?PCBUOA::BRACKENTue Mar 11 1997 07:479
    Community Names are somewhat a security measure in SNMP. The Agent is
    setup in NT within the Network Control Panel SNMP configuration.
    In order to communicate via SNMP with the agent you need to change the
    client side with the matching get and set community strings. In M/W
    Server Works the General Properties have it. If there is anyting in
    Netview we'll have to wait for a response from that expert.
    
    Rich
224.2Anything else?ALFSS2::OLSEN_GHey y'all, how y'all doin'?Tue Mar 11 1997 08:2715
    Rich,
    
    >In order to communicate via SNMP with the agent you need to change the
    >    client side with the matching get and set community strings. In M/W
    >    Server Works the General Properties have it. 
    
    When you change the community name here, does it actually configure the 
    Agent on the remote client?  I assume it does.  
    
    Are those two pieces all that is required?
    
    
    Thanks,
    
    Gary
224.3Community Names needed on both endsPCBUOA::BRACKENTue Mar 11 1997 13:239
    When you change the General Properties in Manageworks it is only
    telling SNMP the community names to use on all get and set requests.
    It would be a security breach if it changes the agent's community
    string. Therefore, on NT you must change the community string that the
    agent will accept on all sets and gets. In SCO it is in /etc/snmp.peers
    and in Netware it would be a line in the autoexec.ncf.
    See the OS manufacturer documentation for details.
    
    Rich
224.4O/S config = Agent config?ALFSS2::OLSEN_GHey y'all, how y'all doin'?Thu Mar 13 1997 13:1410
    Rich,
    
    Just one further clarification - if I set the community name in NT in
    the SNMP services config, then is that what you are referring to as
    configuring the agent?  We did that - but I thought there was something
    we had to do with the actual ServerWORKS agent itself. 
    
    Thanks again,
    
    Gary
224.5SNMP Community NamePCBUOA::BRACKENThu Mar 13 1997 13:461
    Community Name is for all of SNMP and not particular to any agent.