Do you want to allow SNMPv3 read-only user
Do you want to allow SNMPv3 read-only user based access (default = y): Do you want to allow SNMPv1/v2c read-write community access (default = y): ………………………………………………………………………………………. SNMP version 3 is fairly advanced stuff, and far beyond what we need for basic monitoring. Also, we are not using read-write SNMP; we want our monitor to only be able to read information, not issue commands on the system! Answer n to all of the above. You’ll get your read-only access by answering y to the next option. ………………………………………………………………………………………. Do you want to allow SNMPv1/v2c read-only community access (default = y): y Configuring: rocommunity Description: a SNMPv1/SNMPv2c read-only access community name arguments: community [default|hostname|network/bits] [oid] The community name to add read-only access for: ………………………………………………………………………………………. Those of you experienced with SNMP are familiar with the default communities of “public” and private, but don’t use them: they’re the first thing an intruder will look for. Choose community names like you would a good password; don’t use ones that are easily guessed, and don’t use common words; do mix letters and other characters, and so on. If you don’t intend to allow anyone to write SNMP commands on your system, then you probably only need one community name. ………………………………………………………………………………………. The hostname or network address to accept this community name from [RETURN for all]: ………………………………………………………………………………………. Enter the IP address of your network monitoring system as the answer to the preceding question. If you’re monitoring only this machine, from itself, put the loopback IP address (127.0.0.1). You can list an entire network in the standard slash format discussed in Chapter 5 (for example, 192.168.0.0/16). Finally, if you put “0.0.0.0/0″, anyone on the Internet can read SNMP values from your system if they have (or guess) the correct community name. ………………………………………………………………………………………. The OID that this community should be restricted to [RETURN for no-restriction]: ………………………………………………………………………………………. You can restrict different SNMP communities to subportions of the MIB tree. Though you don’t need to bother doing so for our purposes, you might choose to restrict communities in more complex setups than this one. ………………………………………………………………………………………. Finished Output: rocommunity public 127.0.0.1 Do another rocommunity line? (default = y): ………………………………………………………………………………………. If you’re doing only the monitoring we discuss in this chapter, you only need one SNMP community. Answer n to the preceding question. ………………………………………………………………………………………. **************************************** *** Beginning trap destination setup *** **************************************** Do you want to configure where and if the agent will send traps? (default = y): ………………………………………………………………………………………. 439
Note: If you are looking for good and high quality web space to host and run your application check Lunarwebhost Linux Web Hosting services