HP Carrier-grade cc2300 Intel Server Management (ISM) Installation and User&am - Page 18

Customizing Windows Servers After Setup, Customizing Linux Servers After Setup

Page 18 highlights

Intel Server Management (ISM) Installation and User's Guide Intel Server Management (ISM) Concepts In order to receive SNMP traps for network interface card (NIC) events, you must install specific NIC SNMP software from the following Intel web site: http://support.intel.com/support/network/adapter/1000/software.htm Download the Native SNMP software for your operating system and follow the installation and configuration instructions included in the download package. Customizing Windows Servers After Setup • The set action of some SNMP attributes causes the server to shutdown/power off. To globally disallow all set requests: • Change the ReadOnly entry in the %ISMPATH%\bin\sdlink.cfg file to True. • Reboot the server. Customizing Linux Servers After Setup The following items should be checked. (By default, the community string is public - not secure.) You should change the community string for improved security. 1. Verify that the dmi2snmp and ucd-snmp packages are installed by typing rpm -qa | grep snmp. (For example, the files dmi2snmp-1.0-15.i386.rpm and ucd-snmp-4.2.6-1.i386.rpm could represent the dmi2snmp and ucd-snmp packages, respectively.) 2. Open the file /etc/snmp/snmpd.conf. You can use any available editor such as vi, emacs, or a linux editor. 3. Search for com2sec and set the community string to the proper setting for your network. ## sec.name source community com2sec notConfigGroup default mycommunitystring 4. Search for group and verify that the following lines are present: # groupName securityModel group notConfigGroup v1 group notConfigGroup v2 securityName notConfigUser notConfigUser 5. Search for view and specify the desired subtree range (suggested range shown in bold below). ## view incl/excl subtree mask view all included .1 80 6. Search for access and set the read column to whatever you specified in the incl/excl column of the view line (step 4 above). # group context sec.model sec.level prefix read write notif #access notConfigGroup "" any noauth exact systemview all none access notConfigGroup "" any noauth exact all all none 7. Add a trapsink line at the end of the file for each ISM console that receives traps from the managed server. Use the following syntax when adding the line: trapsink localhost Be sure to substitute appropriate strings for the host name and domain. Add trapsink lines for any additional hosts that will be receiving trap messages from the managed server. 8. Insert the following text above the trapsink line you added in the previous step. smuxpeer .1.3.6.1.4.1.412 commander smuxpeer .1.3.6.1.4.1.412.1.2 trapper 18

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102

Intel Server Management (ISM) Installation and User's Guide
Intel Server Management (ISM) Concepts
18
In order to receive SNMP traps for network interface card (NIC) events, you must install specific NIC SNMP
software from the following Intel web site:
Download the Native SNMP software for your operating system and follow the installation and configuration
instructions included in the download package.
Customizing Windows Servers After Setup
The set action of some SNMP attributes causes the server to shutdown/power off.
To globally disallow
all set requests:
Change the
ReadOnly
entry in the
%ISMPATH%\bin\sdlink.cfg
file to
True
.
Reboot the server.
Customizing Linux Servers After Setup
The following items should be checked. (By default, the community string is public – not secure.) You should
change the community string for improved security.
1.
Verify that the dmi2snmp and ucd-snmp packages are installed by typing
rpm -qa | grep snmp
. (For
example, the files
dmi2snmp-1.0-15.i386.rpm
and
ucd-snmp-4.2.6-1.i386.rpm
could represent
the dmi2snmp and ucd-snmp packages, respectively.)
2.
Open the file
/etc/snmp/snmpd.conf
. You can use any available editor such as vi, emacs, or a linux
editor.
3.
Search for com2sec and set the community string to the proper setting for your network.
##
sec.name
source
community
com2sec notConfigGroup
default
mycommunitystring
4.
Search for group and verify that the following lines are present:
#
groupName
securityModel
securityName
group
notConfigGroup
v1
notConfigUser
group
notConfigGroup
v2
notConfigUser
5.
Search for view and specify the desired subtree range (suggested range shown in bold below).
##
view
incl/excl subtree
mask
view
all
included
.1
80
6.
Search for access and set the read column to whatever you specified in the incl/excl column of the view
line (step 4 above).
#
group
context sec.model sec.level prefix read
write notif
#access notConfigGroup “”
any
noauth
exact systemview all none
access notConfigGroup “”
any
noauth
exact all
all none
7.
Add a trapsink line at the end of the file for each ISM console that receives traps from the managed
server. Use the following syntax when adding the line:
trapsink localhost
Be sure to substitute appropriate strings for the host name and domain. Add trapsink lines for any
additional hosts that will be receiving trap messages from the managed server.
8.
Insert the following text above the trapsink line you added in the previous step.
smuxpeer .1.3.6.1.4.1.412 commander
smuxpeer .1.3.6.1.4.1.412.1.2 trapper