Quantcast
Channel: Zenoss Community : Popular Discussions - Forums
Viewing all 270 articles
Browse latest View live

Installation of zenoss 4.2 on ubuntu 12.04

0
0

Hi all,

Yesterday i learned that zenoss 4.2 has being released. how can't install it on ubuntu server 12.04 ?

Because i cannot see the .deb or the tar files to download on zenoss web site.


Customizing Email Notifications

0
0

Hello,

 

I'm trying to customize the e-mail notifications sent out by Zenoss Core 3.0.3. Here's what I have so far.

 

Summary:

%(device)s %(summary)s

 

Body:

Device: %(device)s
Component: %(component)s
Severity: %(severityString)s
Time: %(firstTime)s
Message:
%(message)s
<a href="%(eventUrl)s">Event Detail</a>
<a href="%(ackUrl)s">Acknowledge</a>
<a href="%(deleteUrl)s">Delete</a>
<a href="%(eventsUrl)s">Device Events</a>

This works great for most devices, however any devices that are not registered in DNS only show the IP address in the notfication. For example I have a device named BURL-SERVER-UPS. IP address 192.168.17.98

 

When the up/down notification gets sent, it gives a notification saying:

 

192.168.17.98 ip 192.168.17.98 is up

 

What field can I use so that the notification shows the Device Name rather than the IP?

HOW TO CONFIGURE WMI ACCESS ON WINDOWS FOR A NON ADMIN USER

0
0
Hi,
If you, like me have to configure WMI access on Windows servers for a non admin user in order for Zenoss to read the eventlog etc, read on...

Introduction

Zenoss is able to read & query Windows servers via WMI  in order to obtain Eventlog information. Windows Management Instrumentation  (WMI) is the infrastructure for management data and operations on Windows-based  operating systems. WMI also supplies management data to other parts of the  operating system and products like zenoss. For security purposes you can use a limited domain user account to  access the WMI infrastructure and relevant components. The domain user acount has rights to only access the  appropriate areas of the server to obtain information for Zenoss.

As the  main objective is read & query the Windows event logs via WMI. Modifications  to the windows server security will need to have access granted to the specific  account (zenwmi) at 4 different levels in order for Zenoss to function  correctly and obtain the event log information the Windows team requires to be  displayed in Zenoss.

The following information describes the 4  levels or areas that require acess to be configured for the specific user.  These 4 requirements are all needed and are in logical order as one  follows on to the next as shown in this diagram attached .


1. DCOM

DCOM stands for Distributed COM and COM stands for  Component Object Model (COM). COM is the standard method for communication  between client/server apps and highlevel APIs for Windows developers. DCOM users  Remote Procedure Call to expose COM objects on a computer to remote clients on  other computers.
Prior to XP SP2 (and the introduction of these 2 DCOM  security settings), it was difficult for an administrator to assess or control  which COM objects were available to remote users and this is even more important  since COM objects can allow anonymous access. Each COM object has its own ACL  and you would have had to look at each COM object's ACL to determine if remote  access were allowed and to whom. This policy and DCOM: Machine Access  Restrictions In Security Descriptor Definition Language (SDDL) syntax put a  system wide access check that all DCOM clients (local or remote) must pass  before hitting the individual COM object's ACLs. This system-wide DCOM check is  like share permissions on a shared folder. Many files may be accessible through  a given network share and each file may have it's own unique permissions but you  must first pass the share level permissions before the file permissions are  checked.

Security in WMI is related to connecting to a WMI namespace. WMI  uses DCOM to handle remote calls. One reason for failure to connect to a remote  computer is due to a DCOM failure, Therefore, this is the first access that must  be granted to the specific user and happily can be granted by adding the user to  the local or domain distributed COM users group on the Server. There is a  domain GPO which adds the domain user to the relevant grounds need by  Zenoss. Specific user access can be granted by following & applying the  following link.
http://msdn.microsoft.com/en-us/library/aa393266.aspx

2. WMI

Windows Management Instrumentation (WMI) is the Microsoft  implementation of Web-based Enterprise Management (WBEM), which is an industry  initiative to develop a standard technology for accessing management information  in an enterprise environment. WMI uses the Common Information Model (CIM)  industry standard to represent systems, applications, networks, devices, and  other managed components. CIM is developed and maintained by the Distributed  Management Task Force (DMTF). The ability to obtain management data from remote  computers is what makes WMI useful. Remote WMI connections are made through  DCOM.

WMI provides a uniform interface for any local or remote  applications or scripts that obtain management data from a computer system, a  network, or an enterprise. The uniform interface is designed such that WMI  client applications and scripts do not have to call a wide variety of operating  system application programming interfaces (APIs). Many APIs cannot be called by  automation clients like scripts or Visual Basic applications. Other APIs do not  make calls to remote computers.

To obtain data from WMI, an application  like Zenoss accesses WMI Classes or provides data to WMI by writing a WMI  provider.

Namespace Access Settings

You can change the access to a WMI namespace using the WMI  Control or programmatically.
TermDescription
Execute MethodsPermits the user to execute  methods defined on WMI classes. Corresponds to the WBEM_METHOD_EXECUTE access  permission constant.
Full WritePermits full read, write,  and delete access to WMI classes and class instances, both static and dynamic.  Corresponds to the WBEM_FULL_WRITE_REP access permission constant.
Partial WritePermits write access to  static WMI class instances. Corresponds to the WBEM_PARTIAL_WRITE_REP access  permission constant.
Provider WritePermits write access to  dynamic WMI class instances. Corresponds to the WBEM_WRITE_PROVIDER access  permission constant.
Enable AccountPermits read  access to WMI class instances. Corresponds to the WBEM_ENABLE access permission  constant.
Remote EnablePermits access to  the namespace by remote computers. Corresponds to the WBEM_REMOTE_ACCESS access  permission constant.
Read SecurityPermits read-only access to  DACL settings. Corresponds to the READ_CONTROL access permission constant.
Edit SecurityPermits write access to  DACL settings. Corresponds to the WRITE_DAC access permission  constant.


This is the second access requirement that is  needed for Zenoss. For the DMSI Windows team, the zenwmi domain user is manually  given Remote Enable & Enable Account permissions to the CIMV2 class. This is  done by a user written program, WMISecurity that can be run in a command line.
The syntax is as follows:
WmiSecurity.exe /C="%computername%" /A /N=Root/CIMV2 /M=" DOMAIN\USER:REMOTEACCESS" /R

Specific user access can be granted by following &  applying the following link.
http://technet.microsoft.com/en-us/library/cc787533%28WS.10%29.aspx

3.  Service Control Manager

The service control manager (SCM) is started at system  boot. It is a remote procedure call (RPC) server, so that service configuration  and service control programs can manipulate services on remote machines. SCM  maintains a database of the installed services and driver services that allow  the operating system to start successfully, and provides a unified and secure  means of controlling them. The database, which is stored in the Windows system  registry, includes configuration and security information about each service or  driver service.

System administrators should use the Services snap-in or  the sc.exe command-line tool to query or configure services.

The service  functions provide an interface for the following tasks performed by the  SCM:

Maintaining the database of installed services.
Starting services  and driver services either upon system startup or upon demand.
Enumerating  installed services and driver services.
Maintaining status information for  running services and driver services.
Transmitting control requests to  running services.
Locking and unlocking the service database.

Zenoss  requires access to this manager in order to scan the machine for which windows  services are installed on it and subsequently provide status information on the  event page besides gaining access to the eventlog (which is a service). This is  the third access requirement which needs to be modified for Zenoss. This is  configured by command line (sc.exe) and is also included in the tasks section of  the automatic network install. Specific user access is the only method of  configuration for this type of access & can be granted by following &  applying the following link.
http://support.microsoft.com/kb/907460

The command line used for Windows servers is:
sc sdset  SCMANAGER  D:(A;;CC;;;AU)(A;;CCLCRPWPRC;;;SY)(A;;KA;;;BA)(A;;CCLCRPRC;;;IU)(A;;CCLCRPRC;;;SU)(A;;CCLCRPRC;;;S-1-5-21-1248577188-10479689-3873521419-99999)S:(AU;FA;KA;;;WD)(AU;OIIOFA;GA;;;WD)

4. Event  Log Permissions

Finally to read and list the Windows events in Zenoss  event page, the user defined in the properties of Zenoss Orangiser has to be  given rights to read the log. Unfortuntely as you have just read, you are not  able to just add the rights to the event log and be done with it, the above  modifications needed to have been actioned beforehand. The easiest way to perfom  this task for the hundreds of Windows servers at Sopra was to create a domain  wide GPO.

A policy setting determines which user accounts have access  to log files and what usage rights are granted. Individual setting may be  specified for each of the Application, Security, Setup, and System event log  channels. For Zenoss each Log must by modified in order the the ZenEventlog  connection is UP.

Enabling this setting allows you to enter a security  descriptor for the log file. The security descriptor controls who can read,  write, or clear the event log. You enter the security descriptor using Security  Definition Description Language (SDDL) as we have read above. The following link  explains how to add specific user access to the Eventlog via a GPO
http://support.microsoft.com/default.aspx/kb/323076

The structure of the Eventlog key is as follows:

  • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog\Application,Security,System,CustomLog

Note that domain controllers record events in the  Directory service and File Replication service logs and DNS servers record  events in the DNS server.

CustomSD Restricts access to the event log.  This value is of type REG_SZ. The format used is Security Descriptor Definition  Language (SDDL). Construct an ACL that grants one or more of the following  rights:

  • Read (0x0001)
  • Write (0x0002)
  • Clear (0x0004)

To be a syntactically valid SDDL, the CustomSD value  must specify an owner and a group owner (for example, O:BAG:SY), but the owner  and group owner are not used. If CustomSD is set to a wrong value, an event is  fired in the System event log when the event log service starts, and the event  log gets a default security descriptor which is identical to the original  CustomSD value for the Application log. SACLs are not supported.

The SDDL  permissions used for Windows servers  is:
O:BAG:SYD:(D;;0xf0007;;;AN)(D;;0xf0007;;;BG)(A;;0xf0007;;;SY)(A;;0x7;;;BA)(A;;0x7;;;SO)(A;;0x3;;;IU)(A;;0x3;;;SU)(A;;0x3;;;S-1-5-3)(A;;0x1;;;S-1-5-21-1248577188-10479689-3873521419-99999)

Error  Summary

I have figured out the following after lots of trial and  error. It is a logical process, almost like walking through one security door  after another to get to the windows Eventlog. If you see the following  ZenWinor ZenEventlogerrors in the event page you need to check the  relevant section or link to determine where the fault  lies.


Component: ZenWin
Message: Could not read the status of  Windows services (NT_STATUS_ACCESS_DENIED). Check your  username/password settings and verify network connectivity.

Component:  ZenEventlog
Message: Could not read the Windows event log (NT_STATUS_ACCESS_DENIED). Check your  username/password settings and verify network connectivity.

This error  relates to the DCOM Permissions& is  resolved by implementing
http://msdn.microsoft.com/en-us/library/aa393266.aspx, check that the ZenWMI user is a member of the Distributed COM users  group on the server.


Component: ZenWin
Message: Could not read the  status of Windows services (NT code  0x80041003). Check your username/password settings and verify network  connectivityconnectivity.

Component: ZenEventlog
Message: Could not  read the Windows event log (NT code  0x80041003). Check your username/password settings and verify network  connectivity

This error relates to the WMI  Permissions& is resolved by implementing
http://technet.microsoft.com/en-us/library/cc787533.aspx, Check to see that the ZenWMI users has Enable Account & Remote  Enable access to the CIMV2 namespace in WMI Control on the  server

Component: ZenWin
Message: Could not read the status of Windows  services (NT code 0x80041001). Check  your username/password settings and verify network connectivity

This  error relates to the SCM Permissions& is  resolved by implementing
http://support.microsoft.com/kb/907460, check to see if the ZenWMI user Unique SID has been added to the  SCM SSDL, type "sc sdhow scmanager", if not copy and pase the above command,  once this is done you should get a cleared "zenwin wmi connection is up"  message

Component: ZenWin
Message: Could not read the status of  Windows services (NT code 0xc002001b). Check your username/password settings and verify network  connectivity.

Component: ZenEventlog
Message: Could not read the  Windows event log (NT code  0xc002001b). Check your username/password settings and verify network  connectivity.

This error relates to the Eventlog Permissions& is resolved by  implementing
http://support.microsoft.com/kb/323076,  As this is set by GPO, check to see if the GPO was correctly enforced and use  the regisitry editior to check that the above SDDL is present, goto  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog\"LOG" and read the  Custom SD string value, once this is modified correctly, you should get a  cleared "zeneventlog wmi connection is up" message

Other  Errors

Component: ZenEventlog
Message: Could not read the  Windows event log (ExecNotificationQuery  (WBEM_E_ACCESS_DENIED)). Check your username/password settings and  verify network connectivity.

This usually relates to an missing EventLog  permission and that the SSDL has not been applied to all the event logs,  application system, security, etc.

Component: ZenPerfwmi
Message:  Could not read the WMI value (NT code  0x80010105). Check your username/password settings and verify network  connectivity.

I forget.. will have to recall how I fixed it... I think it  was due to the "users" group being removed the right to log
onto the computer in the local policy..

Component:  ZenPerfwmi
Message: Could not read the WMI value (NT code 0x80041010). Check your  username/password settings and verify network connectivity.

This usually  relates to a missing WMI namespace, check that Service pack 2 is installed,or  recreate/reset the WMI namespaces.
The command  winnts2k\system32\wbem\wmiadap.exe /f will often restore missing WMI performance  counters.

Sources:
http://msdn.microsoft.com/en-us/library/aa392740%28VS.85%29.aspx
http://support.microsoft.com/kb/820847
http://msdn.microsoft.com/en-us/library/aa394528%28VS.85%29.aspx

Final thanks to all the forum members for their help and input over time.

Alzoo

Can't keep zenhub running

0
0

I sure hope someone can help me figure this out.  Been through all the logs, forums, and anything else I can think of, so as a last resort, I'm reaching out the community.  I'm not a power linux user by any means, but  know enough to be dangerous, to give you some background.   All we need is simple monitoring and alerting, but without Zenhub, we don't get alerts, which isn't good.  Zenhub won't stay running for a more than 2-3 days at this point, and it's been that way for months.  There's nothing in the zenhub log.  It just stops.  I found this in zencommand log, which is the most information I can find on the issue.

 

2012-08-10 21:35:52,849 ERROR zen.zencommand: ZenHub is down

Traceback (most recent call last):

  File "/usr/local/zenoss/zenoss/Products/ZenRRD/zencommand.py", line 704, in doFetchConfig

    self.setPropertyItems(driver.next())

  File "/usr/local/zenoss/zenoss/Products/ZenUtils/Driver.py", line 64, in result

    raise ex

HubDown: ZenHub is down

2012-08-10 21:35:53,342 ERROR zen.zencommand: ZenHub is down

Traceback (most recent call last):

  File "/usr/local/zenoss/zenoss/Products/ZenRRD/zencommand.py", line 752, in start

    driver.next()

  File "/usr/local/zenoss/zenoss/Products/ZenUtils/Driver.py", line 64, in result

    raise ex

HubDown: ZenHub is down

2012-08-11 03:35:53,484 ERROR zen.zencommand: ZenHub is down

Traceback (most recent call last):

  File "/usr/local/zenoss/zenoss/Products/ZenRRD/zencommand.py", line 704, in doFetchConfig

    self.setPropertyItems(driver.next())

  File "/usr/local/zenoss/zenoss/Products/ZenUtils/Driver.py", line 64, in result

    raise ex

HubDown: ZenHub is down

2012-08-11 03:35:53,685 ERROR zen.zencommand: ZenHub is down

Traceback (most recent call last):

  File "/usr/local/zenoss/zenoss/Products/ZenRRD/zencommand.py", line 752, in start

    driver.next()

  File "/usr/local/zenoss/zenoss/Products/ZenUtils/Driver.py", line 64, in result

    raise ex

 

We are running this on Ubuntu Linux 12.04.1 and Zenoss is the latest version: Zenoss 3.2.1.

 

I'd truly appreciate some help in getting this fixed.  Please let me know if there is any other information I can provide.  Thank you in advance.

4.2 Install Script for Ubuntu 12.04 (Working)

0
0

Hello,

 

My ties with Ubuntu are deep, so I decided to write and share an install script for Zenoss 4.2.0. I've tested it with multiple installations, and so far everything is working like it should.

 

Any beta testers?

 

Notes: Ubuntu 12.04.1 x64 Server, fresh install, fully patched

 

Links: Blog Post with notes and full script

 

 

What would be the proper method to get Ubuntu as a supported operating system? I'm new to this community.

Zenoss 4.2 Maps Portlet error "OVER_QUERY_LIMIT"

0
0

Having tried Zenoss and loving it i'm begining to fill it with routers i'm monitoring on the internet.
Als goes well and there's lots of info when something doesnt work or when you don't no how.
Great Community ;-)

 

But now i'm running in to an error i can't find on the forum and don't know how so solve.


I now have 30 routers on 30 diferent locations set up in Zenoss.
But now the Google Maps Portlet gives when the counter hits 14 of 30 the error :


"Google could not process addresses. Reason: OVER_QUERY_LIMIT"

 

My first thought. The google maps rquest limit of 25k (I don't have that many mappoint yet but maybee through some error)

But that was'nt the case. The report says about 100 query's on the google page for the first two days of testing.


I see somebody mentions(but for a complete different application) that there is a limit of adresses you can send to google in 1 or 2 seconds.

Kan this be limited in Zenoss so there will be a small delay in geo looking up. Or does anybody know where this error coems from

 

 

 

Also, if i'm not mistaking . Zenoss should cache the adresses so it doesn't have to look them up all the time , right ?

Everytime i get to the dashboard it starts over again with lookip up 1 0f 30 2 of 30 until 13 or 14 and then the error.


I already dit al clear geocache in the Infrastructure menu and also restarted zenoss a couple of times

 

 

Any help is welkom, i'm setting this up to convince my superior to switch to Zenoss in stead of OpenNMS an Nagios ;-)

 

 

Picture of error is attached

 

 

LITTLE UPDATE:

 

 

As far as i can check it should not re-geolocate every adres everytime.
I made a sub location container with 5 adresses. This works because i don't hit the 13 limit.
But ervery time i switch from and back to the dashboard is re-geolocates the adresses.So no cache is being used what so ever.
If i hit the 14 in this container i also get the query limit error again. But if it would cache i would have 3 times the error and then it would use the cached location

 

So where can i find the file or database entry where the cache is beining supposed to be build up, anyone ?

New IP-SLA Enumeration/Monitoring ZenPack

0
0
Thanks to Shane Scott for providing his new IP-SLA Enumeration/
Monitoring ZenPack. The ZenPack discovers, enumerates and allows
monitoring of SLAs. SLA objects are children of the parent SLA
appliance. The ZenPack provides 3 templates HTTP, New_SLA and VoIP
under the device class /Devices/Network/IPSLA.

IP-SLA Enumeration/Monitoring: http://www.zenoss.com/community/projects/zenpacks/ip_sla
IP-SLA Enumeration/Monitoring Wiki: http://community.zenoss.org/trac-zenpacks/wiki/ZenPacksipSLASLADevice

Thanks Shane!

Thanks,Matt Ray
Zenoss Community Manager
community.zenoss.com
mray@zenoss.com






_______________________________________________
zenoss-zenpacks mailing list
zenoss-zenpacks@zenoss.org
http://lists.zenoss.org/mailman/listinfo/zenoss-zenpacks

Help with Custom Map Zenpack

0
0
I have been working on a zenpack that will allow a user to create arbitrary custom maps somewhat in the style of zabbix. Some of the features I have been aiming for:
  • Maps can have arbitrary images as backgrounds.
  • Maps can contain devices or submaps
  • ZenPack contains drag and drop editor
  • Nodes images can be set to user icons, and their labels can be positioned on any side of the icon, or ommitted entirely
  • Portlet allows you to navigate through the maps, and updates itself
  • A map's status is dependant on the status of any nodes or submaps on it.
  • Edges can be plain lines, or arrows showing the amount of bandwidth on the interface they represent

 

The actual implementation of the portlet and the map editor is fairly solid right now. We are currently monitoring about 1800 devices, most of which have placed into these hand-drawn maps. The individual maps load very quickly, and the portlet updates the map image seamlessly every 30 seconds.

 

I am not very familiar with zope, and the more I try to learn, the less it makes sense to me. There are a number of issues I am trying to solve that I would love some help with:

  • The map editor is implemented as a tab in the Locations section. Each Location has a custom_map property that contains all the information needed to draw a map. I seem unable to make the tab show up consistently though. When I set a recursive function to add it to all the Location objects, it works on some and not the others.
  • I would like to find a way to make the tab show up for new Locations as well. I have tried monkey patching the base Location as well as the class it derives from, but neither seems to work.
  • The map drawing code relies on PIL. There is a namespace conflict between one of the PIL modules (ImageFile) and zenoss. I had to modify PIL slightly to avoid the conflict. Is there some way I can include this with the zenpack? Or is there some other api I should be using to draw the images.

New ZenPacks in the Community

How to run a script on remote windows machine?

0
0

I need to run a script on remote MS Win machine. The command I use locally is somethig like:

 

cscript d:\someuser\ConnectionTest.wsf

How I can run this from Zenoss? I have both ssh (cygwin) and WMI access from my Zenoss server to MS Win, but for some  reason all my tries were unsuccessful :-(

TIA,

Vitaly

Quick start: Hyper-V/Centos 6.3/Zenos Core 4.2.0 sp 1

0
0

When I wanted to make the jump from the demo VM to a real Hyper-V VM, I found that the instructions were a bit all over the place and sometimes outdated.  I want to write up a nice one, but until then I'm putting a more basic walkthrough here.  Hope it helps someone.  While I put the exact versions and environment, some of this is probably applicable to slightly different ones.

 

 

Installing a Centos 6.3/Zenoss Core 4.2.0 sp 1 VM from scratch on Windows Server 2008 R2 (System Center 2012)

 

 

A) Prepare the VM

  1. Get CentOS-6.3-x86_64-LiveCD.iso from one of the mirrors at http://isoredirect.centos.org/centos/6/isos/x86_64/
  2. Get Linux IC v3.4.iso from http://www.microsoft.com/en-us/download/details.aspx?id=34603
  3. Create hyper-v VM (I set it to Other Linux (64 bit) but that may not be necessary)
  4. Use non-legacy network card.
  5. This guide will assume you are making your VM visible on your internet network (bridged).
  6. Change to Connected to and choose the appropriate settings for your host network config
  7. Attach CentOS-6.3-x86_64-LiveCD.iso to the virtual CD/DVD drive

 

 

B) Install CentOS and Hyper-V Integration

  1. Power on, connect and login as root
  2. Ctrl-Alt-D to get to desktop
  3. run Install LiveCD to Hard Drive
  4. Alt-F1, tab over to System -> Shutdown (not reboot)
  5. Attach Linux IC v3.4.iso to the virtual CD/DVD drive
  6. Power on and connect
  7. Finish setup (and reboot if it makes you)
  8. Alt-F1, System Tools -> Terminal
  9.   cd /media/CDROM/RHEL63
  10.   rpm -Uvh --nodeps kmod-microsoft-hyper-v-rhel63.3.4-1.20120727.x86_64.rpm
  11.   rpm -Uvh –-nodeps microsoft-hyper-v-rhel63.3.4-1.20120727.x86_64.rpm
  12.   shutdown -h 0
  13. Remove the ISO from the VM
  14. Power on, connect and login as root
  15. Mouse should work now
  16. Go to System -> Preferences -> Network Connections
  17. You should see Auto eth0.  You can now change it to a static ip if necessary.
  18. Open a terminal window and type ifconfig to see your network card.
  19. You may need to issue "service network restart" to apply your changes.
  20. You should now be able to ping and be pinged.

 

CentOS 6.3 should be installed properly.  Now might be a good time to shut down and make a checkpoint/backup!

 

 

C) Install Zenoss 4.2.0

  1. Login as root
  2. Open a Terminal window
  3.   yum -y remove mysql-libs
  4.   wget --no-check-certificate https://raw.github.com/zenoss/core-autodeploy/master/core-autodeploy-4.2.sh
  5.   chmod +x core-autodeploy-4.2.sh
  6.   ./core-autodeploy-4.2.sh
  7.   iptables -I INPUT 1 -p tcp --dport 8080 -j ACCEPT
  8.   iptables -I INPUT 1 -p tcp --dport memcache -j ACCEPT
  9.   iptables -I INPUT 1 -p udp --dport memcache -j ACCEPT
  10.   iptables -I INPUT 1 -p tcp --dport syslog -j ACCEPT
  11.   iptables -I INPUT 1 -p tcp --dport snmptrap -j ACCEPT
  12. And if you want ssh (you can do this earlier in the process as well):
  13.   iptables -I INPUT 1 -p tcp --dport ssh -j ACCEPT
  14.   Go to System -> Administration -> Services and enable and then start sshd
  15.   It's a lot easier to ssh (PuTTY is a good, free ssh client) than to use the GUI for some of the following.
  16. Finish with:
  17.   service iptables save

 

Zenoss 4.2.0 should be installed properly.  Now might be another good time to shut down and make a checkpoint/backup!

 

 

D) Update to 4.2.0 sp 1

  1. Login as root
  2. Issue the following commands via terminal or ssh (answer "y" to all prompts):
  3.   yum --enablerepo=epel install git
  4.   yum install patch
  5.   yum install unzip
  6.   su zenoss
  7.   cd /var/tmp
  8.   git clone git://github.com/zenoss/CoreServicePacks.git
  9.   cd CoreServicePacks/4.2.0-SP1
  10.   ./apply.sh
  11.   zenoss start

 

E) Miscellaneous

  1. Login as root
  2. Open up snmp so you can monitor the zenoss server's performance:
  3.   Edit /etc/snmp/snmpd.conf
  4.   Comment out the following lines by putting a # in front of them:
  5.     view    systemview    included    .1.3.6.1.2.1.1
  6.     view    systemview    included    .1.3.6.1.2.1.25.1.1
  7.   Add this line at the end of the file:
  8.     view    systemview    included    .1

 

Zenoss 4.2.0 sp 1 should be installed properly.  You know what it's a good time for by this point.

Installation of zenoss 4.2 on ubuntu 12.04

0
0

Hi all,

Yesterday i learned that zenoss 4.2 has being released. how can't install it on ubuntu server 12.04 ?

Because i cannot see the .deb or the tar files to download on zenoss web site.

Zenoss + Apache mod_proxy

Zenoss Core 4.2 Autodeploy: Command failure: /sbin/service zenoss start

0
0

Starting MySQL SUCCESS!

Zenoss not initialized. Performing first-boot initialization..

Fresh install pre steps Please confirm that the JRE in the PATH is Oracle's version.

 

 

Running CentOS Server v.6

Executed auto-deploy script

 

 

Please advice!

Cisco CatOS port name & descriptions SOLVED!!!

0
0
grin grin grin grin grin

Below is the section of code from InterfaceMap.py that I modified to get this to work:
/opt/zenoss/Products/DataCollector/plugins/zenoss/snmp/InterfaceMap.py

For those interested, in the last section of code I cycle through the ifCatOS map to find the index match with the iftable because I am not sure that they are in the same order when being read by SNMP. If they are in the same order, the code could be simplified even further. It's not elegant, but it works.

    snmpGetTableMaps = (        # If table        GetTableMap('iftable', '.1.3.6.1.2.1',                 {'.2.2.1.1': 'ifindex',                 '.2.2.1.2' : 'id',                 # -------------------------------------------------                 #           Added to get CatOS port name                 # --------------------------------------------------                 '.31.1.1.1.1': 'id',                 # --------------------------------------------------                 '.2.2.1.3': 'type',                 '.2.2.1.4': 'mtu',                 '.2.2.1.5': 'speed',                 '.2.2.1.6': 'macaddress',                 '.2.2.1.7': 'adminStatus',                 '.2.2.1.8': 'operStatus'}        ),        # ipAddrTable is the better way to get IP addresses        GetTableMap('ipAddrTable', '.1.3.6.1.2.1.4.20.1',                {'.1': 'ipAddress',                 '.2': 'ifindex',                 '.3': 'netmask'}        ),        # Use the ipNetToMediaTable as a backup to the ipAddrTable        GetTableMap('ipNetToMediaTable', '.1.3.6.1.2.1.4.22.1',                {'.1': 'ifindex',                 '.3': 'ipaddress',                 '.4': 'iptype'}        ),        # Interface Description        GetTableMap('ifalias', '.1.3.6.1',                {'.2.1.31.1.1.1.18' : 'description',                 '.2.1.31.1.1.1.15' : 'highSpeed'}        ),        # -------------------------------------------------        #           Added to get CatOS descriptions        # --------------------------------------------------        GetTableMap('ifCatOS', '.1.3.6.1.4.1.9.5.1.4.1.1',                {'.11' : 'ifindex',                 '.1'  : 'ifmodule',                 '.2'  : 'ifport',                 '.4'  : 'description',                }        ),        # --------------------------------------------------    )    #dontCollectInterfaceTypes = (1, 18, 76, 77, 81, 134)           def process(self, device, results, log):        """collect snmp information from this device"""        getdata, tabledata = results        log.info('processing %s for device %s', self.name(), device.id)        rm = self.relMap()        iptable = tabledata.get("ipAddrTable") \            or tabledata.get("ipNetToMediaTable")        iftable = tabledata.get("iftable")        ifalias = tabledata.get("ifalias")        if iptable is None or iftable is None: return        if not ifalias: ifalias = {}        # -------------------------------------------------        #           Added to get CatOS descriptions        # --------------------------------------------------        ifCatOS = tabledata.get("ifCatOS")        # --------------------------------------------------        # add interface alias (cisco description) to iftable        for ifidx, data in ifalias.items():            if not iftable.has_key(ifidx): continue            iftable[ifidx]['description'] = data.get('description', '')            # if we collect ifAlias name use it            # this is in the map subclass InterfaceAliasMap            id = data.get('id', None)            if id:                iftable[ifidx]['id'] = id            iftable[ifidx]['description'] = data.get('description', '')            # --------------------------------------------------            #           Added to get CatOS descriptions            # --------------------------------------------------            if data.get('description', '') == '':                if not ifCatOS: ifCatOS = {}                if ifCatOS <> {}:                    for ifidx2, data2 in ifCatOS.items():                        if iftable[ifidx]['ifindex'] == ifCatOS[ifidx2]['ifindex']:                            iftable[ifidx]['description'] = data2.get('description', ' ')            # --------------------------------------------------            # handle 10GB interfaces using IF-MIB::ifHighSpeed


David

Installation of zenoss 4.2 on ubuntu 12.04

0
0

Hi all,

Yesterday i learned that zenoss 4.2 has being released. how can't install it on ubuntu server 12.04 ?

Because i cannot see the .deb or the tar files to download on zenoss web site.

Customizing Email Notifications

0
0

Hello,

 

I'm trying to customize the e-mail notifications sent out by Zenoss Core 3.0.3. Here's what I have so far.

 

Summary:

%(device)s %(summary)s

 

Body:

Device: %(device)s
Component: %(component)s
Severity: %(severityString)s
Time: %(firstTime)s
Message:
%(message)s
<a href="%(eventUrl)s">Event Detail</a>
<a href="%(ackUrl)s">Acknowledge</a>
<a href="%(deleteUrl)s">Delete</a>
<a href="%(eventsUrl)s">Device Events</a>

This works great for most devices, however any devices that are not registered in DNS only show the IP address in the notfication. For example I have a device named BURL-SERVER-UPS. IP address 192.168.17.98

 

When the up/down notification gets sent, it gives a notification saying:

 

192.168.17.98 ip 192.168.17.98 is up

 

What field can I use so that the notification shows the Device Name rather than the IP?

Cisco CatOS port name & descriptions SOLVED!!!

0
0
grin grin grin grin grin

Below is the section of code from InterfaceMap.py that I modified to get this to work:
/opt/zenoss/Products/DataCollector/plugins/zenoss/snmp/InterfaceMap.py

For those interested, in the last section of code I cycle through the ifCatOS map to find the index match with the iftable because I am not sure that they are in the same order when being read by SNMP. If they are in the same order, the code could be simplified even further. It's not elegant, but it works.

    snmpGetTableMaps = (        # If table        GetTableMap('iftable', '.1.3.6.1.2.1',                 {'.2.2.1.1': 'ifindex',                 '.2.2.1.2' : 'id',                 # -------------------------------------------------                 #           Added to get CatOS port name                 # --------------------------------------------------                 '.31.1.1.1.1': 'id',                 # --------------------------------------------------                 '.2.2.1.3': 'type',                 '.2.2.1.4': 'mtu',                 '.2.2.1.5': 'speed',                 '.2.2.1.6': 'macaddress',                 '.2.2.1.7': 'adminStatus',                 '.2.2.1.8': 'operStatus'}        ),        # ipAddrTable is the better way to get IP addresses        GetTableMap('ipAddrTable', '.1.3.6.1.2.1.4.20.1',                {'.1': 'ipAddress',                 '.2': 'ifindex',                 '.3': 'netmask'}        ),        # Use the ipNetToMediaTable as a backup to the ipAddrTable        GetTableMap('ipNetToMediaTable', '.1.3.6.1.2.1.4.22.1',                {'.1': 'ifindex',                 '.3': 'ipaddress',                 '.4': 'iptype'}        ),        # Interface Description        GetTableMap('ifalias', '.1.3.6.1',                {'.2.1.31.1.1.1.18' : 'description',                 '.2.1.31.1.1.1.15' : 'highSpeed'}        ),        # -------------------------------------------------        #           Added to get CatOS descriptions        # --------------------------------------------------        GetTableMap('ifCatOS', '.1.3.6.1.4.1.9.5.1.4.1.1',                {'.11' : 'ifindex',                 '.1'  : 'ifmodule',                 '.2'  : 'ifport',                 '.4'  : 'description',                }        ),        # --------------------------------------------------    )    #dontCollectInterfaceTypes = (1, 18, 76, 77, 81, 134)           def process(self, device, results, log):        """collect snmp information from this device"""        getdata, tabledata = results        log.info('processing %s for device %s', self.name(), device.id)        rm = self.relMap()        iptable = tabledata.get("ipAddrTable") \            or tabledata.get("ipNetToMediaTable")        iftable = tabledata.get("iftable")        ifalias = tabledata.get("ifalias")        if iptable is None or iftable is None: return        if not ifalias: ifalias = {}        # -------------------------------------------------        #           Added to get CatOS descriptions        # --------------------------------------------------        ifCatOS = tabledata.get("ifCatOS")        # --------------------------------------------------        # add interface alias (cisco description) to iftable        for ifidx, data in ifalias.items():            if not iftable.has_key(ifidx): continue            iftable[ifidx]['description'] = data.get('description', '')            # if we collect ifAlias name use it            # this is in the map subclass InterfaceAliasMap            id = data.get('id', None)            if id:                iftable[ifidx]['id'] = id            iftable[ifidx]['description'] = data.get('description', '')            # --------------------------------------------------            #           Added to get CatOS descriptions            # --------------------------------------------------            if data.get('description', '') == '':                if not ifCatOS: ifCatOS = {}                if ifCatOS <> {}:                    for ifidx2, data2 in ifCatOS.items():                        if iftable[ifidx]['ifindex'] == ifCatOS[ifidx2]['ifindex']:                            iftable[ifidx]['description'] = data2.get('description', ' ')            # --------------------------------------------------            # handle 10GB interfaces using IF-MIB::ifHighSpeed


David

Quick start: Hyper-V/Centos 6.3/Zenos Core 4.2.0 sp 1

0
0

When I wanted to make the jump from the demo VM to a real Hyper-V VM, I found that the instructions were a bit all over the place and sometimes outdated.  I want to write up a nice one, but until then I'm putting a more basic walkthrough here.  Hope it helps someone.  While I put the exact versions and environment, some of this is probably applicable to slightly different ones.

 

 

Installing a Centos 6.3/Zenoss Core 4.2.0 sp 1 VM from scratch on Windows Server 2008 R2 (System Center 2012)

 

 

A) Prepare the VM

  1. Get CentOS-6.3-x86_64-LiveCD.iso from one of the mirrors at http://isoredirect.centos.org/centos/6/isos/x86_64/
  2. Get Linux IC v3.4.iso from http://www.microsoft.com/en-us/download/details.aspx?id=34603
  3. Create hyper-v VM (I set it to Other Linux (64 bit) but that may not be necessary)
  4. Use non-legacy network card.
  5. This guide will assume you are making your VM visible on your internet network (bridged).
  6. Change to Connected to and choose the appropriate settings for your host network config
  7. Attach CentOS-6.3-x86_64-LiveCD.iso to the virtual CD/DVD drive

 

 

B) Install CentOS and Hyper-V Integration

  1. Power on, connect and login as root
  2. Ctrl-Alt-D to get to desktop
  3. run Install LiveCD to Hard Drive
  4. Alt-F1, tab over to System -> Shutdown (not reboot)
  5. Attach Linux IC v3.4.iso to the virtual CD/DVD drive
  6. Power on and connect
  7. Finish setup (and reboot if it makes you)
  8. Alt-F1, System Tools -> Terminal
  9.   cd /media/CDROM/RHEL63
  10.   rpm -Uvh --nodeps kmod-microsoft-hyper-v-rhel63.3.4-1.20120727.x86_64.rpm
  11.   rpm -Uvh –-nodeps microsoft-hyper-v-rhel63.3.4-1.20120727.x86_64.rpm
  12.   shutdown -h 0
  13. Remove the ISO from the VM
  14. Power on, connect and login as root
  15. Mouse should work now
  16. Go to System -> Preferences -> Network Connections
  17. You should see Auto eth0.  You can now change it to a static ip if necessary.
  18. Open a terminal window and type ifconfig to see your network card.
  19. You may need to issue "service network restart" to apply your changes.
  20. You should now be able to ping and be pinged.

 

CentOS 6.3 should be installed properly.  Now might be a good time to shut down and make a checkpoint/backup!

 

 

C) Install Zenoss 4.2.0

  1. Login as root
  2. Open a Terminal window
  3.   yum -y remove mysql-libs
  4.   wget --no-check-certificate https://raw.github.com/zenoss/core-autodeploy/master/core-autodeploy-4.2.sh
  5.   chmod +x core-autodeploy-4.2.sh
  6.   ./core-autodeploy-4.2.sh
  7.   iptables -I INPUT 1 -p tcp --dport 8080 -j ACCEPT
  8.   iptables -I INPUT 1 -p tcp --dport memcache -j ACCEPT
  9.   iptables -I INPUT 1 -p udp --dport memcache -j ACCEPT
  10.   iptables -I INPUT 1 -p tcp --dport syslog -j ACCEPT
  11.   iptables -I INPUT 1 -p tcp --dport snmptrap -j ACCEPT
  12. And if you want ssh (you can do this earlier in the process as well):
  13.   iptables -I INPUT 1 -p tcp --dport ssh -j ACCEPT
  14.   Go to System -> Administration -> Services and enable and then start sshd
  15.   It's a lot easier to ssh (PuTTY is a good, free ssh client) than to use the GUI for some of the following.
  16. Finish with:
  17.   service iptables save

 

Zenoss 4.2.0 should be installed properly.  Now might be another good time to shut down and make a checkpoint/backup!

 

 

D) Update to 4.2.0 sp 1

  1. Login as root
  2. Issue the following commands via terminal or ssh (answer "y" to all prompts):
  3.   yum --enablerepo=epel install git
  4.   yum install patch
  5.   yum install unzip
  6.   su zenoss
  7.   cd /var/tmp
  8.   git clone git://github.com/zenoss/CoreServicePacks.git
  9.   cd CoreServicePacks/4.2.0-SP1
  10.   ./apply.sh
  11.   zenoss start

 

E) Miscellaneous

  1. Login as root
  2. Open up snmp so you can monitor the zenoss server's performance:
  3.   Edit /etc/snmp/snmpd.conf
  4.   Comment out the following lines by putting a # in front of them:
  5.     view    systemview    included    .1.3.6.1.2.1.1
  6.     view    systemview    included    .1.3.6.1.2.1.25.1.1
  7.   Add this line at the end of the file:
  8.     view    systemview    included    .1

 

Zenoss 4.2.0 sp 1 should be installed properly.  You know what it's a good time for by this point.

Could not read the WMI value (NT code 0x80041010)

0
0

Hi,

 

I'm getting this error when I bind the WMITerminalServer Template to my organiser to view Terminal sessions performance information.

 

Could not read the WMI value (NT code 0x80041010). Check your username/password settings and verify network connectivity.

 

This zenpack uses the following WQL command to receive the information.

 

ZenPacks.community.WMIPerf_TerminalServer
Version1.0
AuthorJohan Keskitalo

 

SELECT ActiveSessions,InactiveSessions,TotalSessions FROM Win32_PerfRawData_TermService_TerminalServices

 

As soon as I unbind the template, the error stops.

 

The WMIPerformanceMonitor Zenpack uses the below command to obtain the same information and the error does not appear.

 

NameWMIPerformanceMonitor
Version
Author

 

$$ZENHOME/Products/WMIPerformanceMonitor/libexec/wmi_stats.pl TS "${dev/id}" "${dev/manageIp}" "${dev/zWinUser}" '${dev/zWinPassword}'

 

Can anyone tell me why this error appears with a WQL command

 

The servers are Windows 2003 Standard x64 and besides receiving the error, the performance counters to appear in the Graph

Viewing all 270 articles
Browse latest View live




Latest Images