zenoss a komponenty

[Petr Hvězda]

Odpovim si sam.

Je nutne nejprve zadat subnet, ve kterem jsou dane zarizeni, ktere chceme
monitorovat. Nasledne spustit auto-disovery. Samo si to vsechny zarizeni
prida a taky nakonfiguruje.

Nastaveni snmpd.conf napr. vzdalene monitorovaneho linux server musi byt
nasledujici:

# First, map the community name "public" into a "security name"

#       sec.name  source          community
com2sec notConfigUser  default       public

####
# Second, map the security name into a group name:

#       groupName      securityModel securityName
group   notConfigGroup v1           notConfigUser
group   notConfigGroup v2c           notConfigUser

####
# Third, create a view for us to let the group have rights to:

# Make at least  snmpwalk -v 1 localhost -c public system fast again.
#       name           incl/excl     subtree         mask(optional)
view    systemview    included   .1

####
# Finally, grant the group read-only access to the systemview view.

#       group          context sec.model sec.level prefix read   write  notif
access  notConfigGroup ""      any       noauth    exact  systemview none
none


--
Petr Hvezda



> resim ted monitoring pomoci Zenoss a SNMP protokolu. Zda se, ze mam vse
> nastavene spravne, nicmene nejsem schopen k Device (tedy monitorovanemu
> zarizeni) dostat komponenty, ktere sleduji napr. CPU, obsazeni HDD, nebo
> traffic. Proste at delam co delam, mam tam "No records found".
>
> Nasel by se zde nekdo, kdo by me radne nakopnul ?