- observium - lists.observium.org

incorrect uptimes shown
by Pieter Meyer 25 Sep '19

25 Sep '19

Hi We have observed that the wrong uptime are shown by Obsevium see below example, I have seen >From SSH shell @storage01:~# uptime 07:23:42 up 818 days, 15:34, 1 user, load average: 0.37, 0.46, 0.43 >From observium Linux storage01 3.2.0-4-amd64 #1 SMP Debian 3.2.88-1 x86_64 Hardware Generic x86 [64bit] Operating system Linux 3.2.0-4-amd64 System name storage01 Contact Converged Telecoms isp(a)convergedgroup.net Location Isando, JHB, South Africa Load average 0.35, 0.51, 0.43 Uptime 1 year, 54 days, 8h 8m 31s Last reboot 2018-08-01 23:13:34 In another place on a netgear M4300 stack it show more uptime than what is actually up for. >From switch System Up time 61 days 7 hrs 25 mins 56 secs >From observium Vendor/Hardware Netgear M4300-24X24F Operating system Netgear Managed Switch (FastPath) 12.0.2.15 (QOS IP Multicast IPv6 Stacking) System name edge1.converged.local Location Isando, Johannesburg, South Africa Serial 4G52687G80066 Uptime 268 days, 12h 35m 33s Last reboot 2018-12-30 18:44:30 Regards Pieter Meyer

2 1

HP PDU cosmetic bug
by Laszlo Nemeth 24 Sep '19

24 Sep '19

Hello, I am happy that the Observium can monitoring the our HP PDUs too! But i found a cosmetic problem. Here is what the PDU shows: [cid:part1.B3B09EA5.D2E13E98@emarsys.com] And what the Observium (9906) shows me: [cid:part2.3649AB3C.D055B67A@emarsys.com] So the "Total Load Feed" looks like need to divide by 10. If the mouse is over the "Power" green value (that is now 2.59kW) the popup shows me: "Normal state 64.31685344686dBm" There is any option to shows the segments too not just the summarized power feed ? (like Load Segment 1..6) Thanks Laszlo

3 7

Mixed authentication (subscribed version)
by FRANKS, Andy (SHREWSBURY AND TELFORD HOSPITAL NHS TRUST) 23 Sep '19

23 Sep '19

Hi all, I don't suppose there's any plans to do a "mixed authentication" feature? We'd like to provide granular access to customer's devices, but centralise all our logins via radius which seemingly can't provide granular access; I can log users in with a '1' permission level, but then I would need to permit access to certain devices, which I can't do since there's no DB-side record of their user id. I see lots of systems which contain an internal database of user IDs matching an external authentication mechanism which then contain the granular bits but don't think Observium does anything like this atm? Maybe even a fallback of "radius,mysql" if we expressly denied the radius auth first? Thanks Andy ******************************************************************************************************************** This message may contain confidential information. If you are not the intended recipient please inform the sender that you have received the message in error before deleting it. Please do not disclose, copy or distribute information in this e-mail or take any action in relation to its contents. To do so is strictly prohibited and may be unlawful. Thank you for your co-operation. NHSmail is the secure email and directory service available for all NHS staff in England and Scotland. NHSmail is approved for exchanging patient data and other sensitive information with NHSmail and other accredited email services. For more information and to find out how you can switch, https://portal.nhs.net/help/joiningnhsmail

1 0

Are 802.1ag or Y.1731 monitored?
by Adam Thompson 23 Sep '19

23 Sep '19

I’ll be deploying some switches Real Soon Now that will be running 802.1ag / MEF OAM-CFM / Y.1731 protocols to get fine-grained as-measured QoS data about the underlying carrier. Is any of that monitored automatically by Observium? Specifically, I’m referring to the counters found in IEEE8021-CFM-MIB and MEF-SOAM-PM-MIB. I’ll be running a small enough number of Management Domains (in IEEE/MEF/ITU-speak) that I can do custom graphs if I have to… but it would sure be nice to not have to! Thanks, -Adam Adam Thompson Consultant, Infrastructure Services [[MERLIN LOGO]]<https://www.merlin.mb.ca/> 100 - 135 Innovation Drive Winnipeg, MB, R3T 6A8 (204) 977-6824 or 1-800-430-6404 (MB only) athompson(a)merlin.mb.ca<mailto:athompson@merlin.mb.ca> www.merlin.mb.ca<http://www.merlin.mb.ca/>

1 0

504 Gateway Time-out
by Wissen, Tobias (EDV) 23 Sep '19

23 Sep '19

Hi there, since today, i get an 504 by adding new hosts. Can anybody give me an advice oft he reason? [cid:image001.png@01D571ED.88CA8820] Mit freundlichen Grüßen Tobias Wissen BERDING BETON GmbH Verwaltung Steinfeld * EDV * Industriestr. 6 * 49439 Steinfeld Tel: 05492 87 290 * Mobil: 0151-14823618 * Fax: 05492 87 295 * E-Mail: t.wissen(a)berdingbeton.de<mailto:t.wissen@berdingbeton.de> Gf: Georg Berding sen., Georg Berding jun., Matthias Hansen, Gert Waltermann * Sitz: 49439 Steinfeld * Registergericht AG Oldenburg: HRB 110334 * USt-ID-Nr.: DE 811247624 * Der Inhalt dieser E-Mail kann vertrauliche und/oder rechtlich geschützte Informationen enthalten und ist ausschließlich für den bezeichneten Adressaten bestimmt. Wenn Sie nicht der vorgesehene Adressat dieser E-Mail oder dessen Vertreter sein sollten, informieren Sie bitte den Absender und löschen Sie die E-Mail. Das unerlaubte Kopieren, Veröffentlichen sowie die unbefugte Weitergabe ist nicht gestattet. ________________________________

1 1

RRD / Graphs
by Wissen, Tobias (EDV) 23 Sep '19

23 Sep '19

How do you do? maybe somebody can help me. since a few days I have the problem that he doesn't create graphs for me anymore. Can somebody tell me what to control to make it work again ? [cid:image001.png@01D56F00.2311A620] Mit freundlichen Grüßen Tobias Wissen

2 5

Question about Cisco 3650 CPU polling
by Svensson Fredrik A 20 Sep '19

20 Sep '19

Hello! Cisco has big problems with 3650 with severalt bugs with high utilization of CPU and memory-leaks. Unfortunally this problem with CPU isnt seen in Observium. The graph is showing the output from sh cpu platform, stable at 49-50% for example: CPU utilization for five seconds: 48%, one minute: 49%, five minutes: 49% Core 0: CPU utilization for five seconds: 50%, one minute: 49%, five minutes: 49% Core 1: CPU utilization for five seconds: 48%, one minute: 51%, five minutes: 49% Core 2: CPU utilization for five seconds: 47%, one minute: 47%, five minutes: 49% Core 3: CPU utilization for five seconds: 49%, one minute: 48%, five minutes: 49% In the meantime we have extreamly high cpu sh processes cpu CPU utilization for five seconds: 95%/29%; one minute: 96%; five minutes: 96% The High cpu causes at least that the device is alerting as down since it cant answer snmp-polling. Is this fixable so we can get alerts from high CPU? Regards Fredrik Svensson Från: observium [mailto:observium-bounces@observium.org] För Laszlo Nemeth via observium Skickat: den 18 september 2019 14:34 Till: Observium <observium(a)observium.org> Kopia: Laszlo Nemeth <lnemeth(a)emarsys.com> Ämne: [Observium] dashboard - alert status widget slider missed Hello In the latest version (r10023 - but may be it was never worked) the Alert status widget does not contain slider on the right side if the alerts are more than it fit to the widget's size. Added a picture where You can see the slider is present in the right side of the Status warning widget but missed in the Alert Status widget. The right table shows that there are more alerts than shows the widget. I use Firefox 69.0. [cid:image001.png@01D56EC2.9ADB1EE0] Thanks Laszlo

2 1

API question
by Serghei Golipad 19 Sep '19

19 Sep '19

Hi Guys, Has anyone got an issue with API, ports in particular not returning any data (devices/alerts and everything else does): uk1soc-hopoff01:~$ curl -u username:password http://10.200.252.10/api/v0/ports uk1soc-hopoff01:~$ If I provide port ID, it does return a response. This is on rolling release 10029 Thank you PLEASE CONSIDER THE ENVIRONMENT BEFORE PRINTING THIS EMAIL. CDW Limited is a Company registered in England and Wales. This email is sent for and on behalf of CDW Finance Holdings Limited. CDW Finance Holdings Limited is the UK holding company for CDW Limited trading as CDW. The registered office for CDW Finance Holdings Limited (Company Number 05872067) and its UK group undertakings is 10 Fleet Place, London, EC4M 7RB. VAT Registration 902 1949 39. Confidentiality: This e-mail contains proprietary information, some or all of which may be confidential and/or legally privileged. It is for the intended recipient only. If an addressing or transmission error has misdirected this e-mail, please notify the author by replying to this e-mail and then delete the original. If you are not the intended recipient you may not use, disclose, distribute, copy, print or rely on any information contained in this e-mail. You must not inform any other person other than CDW or the sender of its existence. For more information about CDW please visit www.uk.cdw.com

1 0

dashboard - alert status widget slider missed
by Laszlo Nemeth 18 Sep '19

18 Sep '19

Hello In the latest version (r10023 - but may be it was never worked) the Alert status widget does not contain slider on the right side if the alerts are more than it fit to the widget's size. Added a picture where You can see the slider is present in the right side of the Status warning widget but missed in the Alert Status widget. The right table shows that there are more alerts than shows the widget. I use Firefox 69.0. [cid:part1.39F92109.995BC4D9@emarsys.com] Thanks Laszlo

1 0

Observium alert checker - polling when devices are unresponsive
by Benedikt Sveinsson 17 Sep '19

17 Sep '19

Hi, I'm trying to create an alert for ports which have an egress percentage over 80%. It's creating false positives for devices that are down during the poll which makes the alert logging report I'm trying to generate rather useless (see a screenshot of the Alert checker below) I tried putting device_status eq 1 into the Test Conditions and requiring all conditions, if I do that, an alert is never generated [cid:image001.png@01D56D44.F618ECD0] What is the best way to achieve this? Kind regards,

2 1

Is there plans to add more severity levels than critical
by Ármann Guðjónsson 13 Sep '19

13 Sep '19

Hi I have seen this question before but I can't find the answer. Do you have plans to implement other security levels that critical for example: info, warning, error , critical Kær kveðja/Best regards ÁRMANN GUÐJÓNSSON Enterprise Network Architect IT Operations Reykjavík Airport 101 Reykjavík Iceland Tel: +354 50 50 736 armanng(a)icelandair.is<mailto:armanng@icelandair.is> www.icelandair.com [cid:image001.png@01D569C4.1881E490] Fyrirvari/Disclaimer<https://www.icelandair.com/support/terms-and-conditions/icelandair-email-di…> [Facebook]<https://www.facebook.com/Icelandair>[Twitter]<https://twitter.com/icelandair>[YouTube]<https://www.youtube.com/icelandair>

4 4

port parsing and port descriptions
by Kenneth Friend II 13 Sep '19

13 Sep '19

I'm admittedly quite the gimp when it comes to Linux and Observium, but I'm learning little by little. I have a custom port group setup to view my VMware network ports (port name / description=VMWare:SomePort). Several of these links are actually aggregated. In the HP/Aruba world they are Trunks. As far as I know, I cannot throw a description on a virtual port / trunk in HP-land. I wonder, is there a way, without being a PHP-guru to add a particular port to a custom port group when I'm unable to provide a port description? If not, that might be a neat feature at some point. Very Respectfully, Kenneth R. Friend II Sr. Systems Administrator Sonnax Transmission Company, Inc. 2 Imtec Lane, Bellows Falls, VT 05101 USA * www.sonnax.com<http://www.sonnax.com/> ken.friend(a)sonnax.com<mailto:ken.friend@sonnax.com> * (802) 463-0287 * (802) 463-9722 ________________________________ CONFIDENTIALITY NOTICE: This e-mail transmission, and any documents, files or previous e-mail message attached to it may contain confidential and proprietary material for the sole use of the intended recipient (s). Do not read this e-mail if you are not the intended recipient. Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient) you are hereby notified that any disclosure, copying, distribution or use of any of the information contained in or attached to this transmission is STRICTLY PROHIBITED and you should delete all copies of this message and its attachments without reading or saving in any manner.

2 1

Custom polling interval for a device group
by Thomas Stather 10 Sep '19

10 Sep '19

Hi We are using Observium Professional: 19.6.9946 (rolling) Interval for polling: 5 minutes I have the issue that some of our network equipment (HPE gear) generates false-positives frequently. It is marked as down, then at the next polling cycle up again. Is it possible to define a custom polling cycle (i.e. 2 minute) for a certain device match (i.e. "device.type in network")? Then, i could generate an alert checker for this with the "Delay" set to 1, so that these devices are scanned every 2 minutes, but only if they are down 2 polling cycles in a row, an alert is generated. Or how can i fix this issue otherwise? Best, Thomas -- Thomas Stather IT Services VCP4, VCP6-DCV, VCP6.5-DCV Tel: +49 6221 486 628 Fax: +49 6221 486 561

1 0

6500 Sensors
by Robert Williams 10 Sep '19

10 Sep '19

Hi, After no issues for ages, rather like busses, these things seem to come along at the same time!... Following a svn up earlier today to ensure we had the latest version (for a storage/snmp issue) - we now seem to have gained some sensors which are in alarm state on every single 6500 chassis. I have a really vague memory of hitting this before, like many years ago, but can't quite put my finger on it. It seems to be picking up all these new sensors (which is fine) - but one of them (clock 2 'clock-inuse') should probably be considered "false=happy" and "true=alert" - (because that means clock 1 has failed). If it helps, the new ones are all within ENTITY-SENSOR-MIB as shown above (and not CISCO-ENTITY-SENSOR-MIB which are the original ones). Some are also duplicates it seems. So, is it possible to flip the true/false alert-ness around for this Clock 2 one? Cheers! Robert Williams Custodian Data Centres https://www.CustodianDC.com

2 2

"Three months" graph annoyance
by Attila Nagy 09 Sep '19

09 Sep '19

Hi all! Is there an option to change the graph for the "Three Months" view to use the same logic to display the X axis labels as the "One Month" graph - "DoW Day Month" instead of "Week XX"? Rationale: Any metric's "Three Months" view shows the graph with the x-axis showing the week number. We find this kinda annoying, as while keeping account of and shuffling around the time, day, month, year is easy, handling the number of current week is awkward. At least here in Hungary the week number - while it is used in some places (like lottery results) -, it is mostly unused, only an interesting fact in a calendar. Thank you in advance. Best regards, Tylla

2 1

Ubuntu Storage
by Robert Williams 09 Sep '19

09 Sep '19

Hi, Only just started looking into this, but it seems that all Ubuntu 18.04 hosts which auto-update have pulled snmpd up to 5.7.3+dfsg-1.8ubuntu3.2 (from ubuntu3.1) are now no longer providing 'any' of their storage info under hrStorageEntry # /usr/bin/snmpbulkwalk -t '5' -r '3' -v2c -c *** -Pud -OQUs -m HOST-RESOURCES-MIB:HOST-RESOURCES-TYPES -M /opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp 'udp':'target-device':'161' hrStorageEntry hrStorageEntry = No Such Object available on this agent at this OID But - after a restart of SNMPD service on the target-device, the expected response returns correctly: hrStorageIndex.1 = 1 hrStorageIndex.3 = 3 hrStorageIndex.6 = 6 hrStorageIndex.7 = 7 hrStorageIndex.8 = 8 hrStorageIndex.10 = 10 hrStorageType.1 = hrStorageRam hrStorageType.3 = hrStorageVirtualMemory hrStorageType.6 = hrStorageOther hrStorageType.7 = hrStorageOther hrStorageType.8 = hrStorageOther <...> HOWEVER - a re-discovery and poll of the device by Observium kills it immediately, and it goes back to: hrStorageEntry = No Such Object available on this agent at this OID It has impacted every 18.04 device we have which auto-updates. Anyone else seen this? Robert Williams Custodian Data Centres https://www.CustodianDC.com

2 2

DB Error
by Jacek.Dabrowski＠selgros.pl 07 Sep '19

07 Sep '19

Hello, Yesterday I turned off Observium after turning on the message DB Error 1040 appears, which I can do with it ??? [cid:image001.jpg@01D5617C.C2F25CC0] Pozdrawiam Jacek Dąbrowski

6 14

svn log
by Christian Eriksson 04 Sep '19

04 Sep '19

https://www.observium.org/svn.log doesn't seem to update anymore /Christian

1 0

Email alerts:
by Farhan Razzak 03 Sep '19

03 Sep '19

Hi, Anyone aware of any known issues with email alerts as seems to be out of service for months. Test shows ok but none received? admin@observium:/opt/observium$ php test_alert.php -c 2 Observium 19.7.9962 Test Alert Notification o Notifying [email] [OK] Kind regards, Farhan Razzak The information transmitted in and with this email is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Statements and opinions expressed in this e-mail may not represent those of the Company. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender immediately and delete the material from any computer. Please also note, Vaioni filter incoming email for spam and inappropriate words. Unfortunately this does mean that sometimes genuine messages can be filtered out. Although we take measures to recover such messages, it must not be assumed that an email has been received by us and important communications should always be followed up by a phone call, fax or printed copy.

1 0

Google map not working properly after upgrade CE 19.8.10000
by CONNECTOS - Fabio R. Kochhann 30 Aug '19

30 Aug '19

Hi. After upgrading my CE version from 18.9.9420 to 19.8.10000, the map view in the dashboard stopped working with the google-mc api. I have tried some settings in the config.php file, but to no avail. Can anyone tell me if they no longer have support for the google map or if there is another way to configure? <http://www.connectos.com.br>

2 1

question about Notification Modification
by Young, Jay 30 Aug '19

30 Aug '19

Hello, We have been using Observium for a couple of months now at our location, and it is working well.. The engineers have had one request though. The notifications that are being sent out have the hostname of the device but not the IP Address. Unfortunately, our network devices are not DNS (we are working to correct that), and to work around the issue, I have been updating the host file on the Observium server as I add devices. The notifications go out with the hostname, but not the IP, so the engineers have to hunt for the IP when they receive them. I have dug through the documentation, and have not been able to find/figure out a way of including the IP Address of the device with the notification (I have probably missed it). Can anyone assist me in adding that to the notifications? (or at least point me in the right direction) Thanks in advance for any assistance that is given -jay Jay Young Network Engineer RRH Information Services & Technology Rochester Regional Health 585-922-1051 jay.young(a)rochesterregional.org<mailto:jay.young@rochesterregional.org> Rochester Regional Health Email Disclaimer This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please delete it from your system. This footnote also confirms that this email message has been swept for the presence of computer viruses. [http://www.myrochealth.com/wp-content/uploads/rrh-logo.jpg]

2 1

Upgrade to 19.8.10000 weirdness
by Ryan Huff 29 Aug '19

29 Aug '19

I upgraded to 19.8.10000 (CE) and some how the alert contacts got goofed up. I had two webhooks when I upgraded (followed all the steps on the website to upgrade the CE and also ran discovery.php -u) and now, the "transport" selection list (for adding a new contact) is all goofed up (devnull... etc) and missing several transport types. Any thoughts would be helpful.. [cid:d8d538b7-1653-43c6-9d49-a6e842541dd7]

2 5

Add new EnvironmentSensor
by Steffen Klemer 27 Aug '19

27 Aug '19

Hey guys, we recently acquired new temperature sensors with these MIBs http://www.networktechinc.com/download/d-environment-monitor-micro.html and wanted to ask if they could be added to observium? (I already use 'custom OID' in the meantime :) ). A sample walk would be % snmpwalk -v2c -M nti -c COMMUNITY HOST iso.3.6.1.4.1.3699.1.1.12 iso.3.6.1.4.1.3699.1.1.12.1.1.1.1.1.1 = INTEGER: 1 iso.3.6.1.4.1.3699.1.1.12.1.1.1.1.1.2 = INTEGER: 2 iso.3.6.1.4.1.3699.1.1.12.1.1.1.1.1.3 = INTEGER: 3 iso.3.6.1.4.1.3699.1.1.12.1.1.1.1.2.1 = INTEGER: 1 iso.3.6.1.4.1.3699.1.1.12.1.1.1.1.2.2 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.1.1.1.2.3 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.1.1.1.3.1 = STRING: "Temperature" iso.3.6.1.4.1.3699.1.1.12.1.1.1.1.3.2 = STRING: "Humidity" iso.3.6.1.4.1.3699.1.1.12.1.1.1.1.3.3 = STRING: "Dew Point" iso.3.6.1.4.1.3699.1.1.12.1.1.1.1.4.1 = INTEGER: 264 iso.3.6.1.4.1.3699.1.1.12.1.1.1.1.4.2 = INTEGER: -2147483648 iso.3.6.1.4.1.3699.1.1.12.1.1.1.1.4.3 = INTEGER: -2147483648 iso.3.6.1.4.1.3699.1.1.12.1.1.1.1.5.1 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.1.1.1.5.2 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.1.1.1.5.3 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.1.1 = INTEGER: 1 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.1.2 = INTEGER: 2 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.1.3 = INTEGER: 3 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.1.4 = INTEGER: 4 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.1.5 = INTEGER: 5 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.1.6 = INTEGER: 6 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.1.7 = INTEGER: 7 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.1.8 = INTEGER: 8 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.1.9 = INTEGER: 9 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.1.10 = INTEGER: 10 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.1.11 = INTEGER: 11 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.1.12 = INTEGER: 12 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.1.13 = INTEGER: 13 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.1.14 = INTEGER: 14 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.1.15 = INTEGER: 15 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.1.16 = INTEGER: 16 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.1.17 = INTEGER: 17 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.1.18 = INTEGER: 18 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.1.19 = INTEGER: 19 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.1.20 = INTEGER: 20 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.1.21 = INTEGER: 21 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.1.22 = INTEGER: 22 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.1.23 = INTEGER: 23 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.1.24 = INTEGER: 24 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.2.1 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.2.2 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.2.3 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.2.4 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.2.5 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.2.6 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.2.7 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.2.8 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.2.9 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.2.10 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.2.11 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.2.12 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.2.13 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.2.14 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.2.15 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.2.16 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.2.17 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.2.18 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.2.19 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.2.20 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.2.21 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.2.22 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.2.23 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.2.24 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.3.1 = STRING: "Temperature #1" iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.3.2 = STRING: "Humidity #1" iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.3.3 = STRING: "Dew Point #1" iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.3.4 = STRING: "Temperature #2" iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.3.5 = STRING: "Humidity #2" iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.3.6 = STRING: "Dew Point #2" iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.3.7 = "" iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.3.8 = "" iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.3.9 = "" iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.3.10 = "" iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.3.11 = "" iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.3.12 = "" iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.3.13 = "" iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.3.14 = "" iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.3.15 = "" iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.3.16 = "" iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.3.17 = "" iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.3.18 = "" iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.3.19 = "" iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.3.20 = "" iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.3.21 = "" iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.3.22 = "" iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.3.23 = "" iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.3.24 = "" iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.4.1 = INTEGER: -2147483648 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.4.2 = INTEGER: -2147483648 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.4.3 = INTEGER: -2147483648 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.4.4 = INTEGER: -2147483648 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.4.5 = INTEGER: -2147483648 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.4.6 = INTEGER: -2147483648 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.4.7 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.4.8 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.4.9 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.4.10 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.4.11 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.4.12 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.4.13 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.4.14 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.4.15 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.4.16 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.4.17 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.4.18 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.4.19 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.4.20 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.4.21 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.4.22 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.4.23 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.4.24 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.5.1 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.5.2 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.5.3 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.5.4 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.5.5 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.5.6 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.5.7 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.5.8 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.5.9 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.5.10 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.5.11 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.5.12 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.5.13 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.5.14 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.5.15 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.5.16 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.5.17 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.5.18 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.5.19 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.5.20 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.5.21 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.5.22 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.5.23 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.2.1.1.5.24 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.3.1.1.1.1 = INTEGER: 1 iso.3.6.1.4.1.3699.1.1.12.1.3.1.1.1.2 = INTEGER: 2 iso.3.6.1.4.1.3699.1.1.12.1.3.1.1.2.1 = STRING: "Digital Input #1" iso.3.6.1.4.1.3699.1.1.12.1.3.1.1.2.2 = STRING: "Digital Input #2" iso.3.6.1.4.1.3699.1.1.12.1.3.1.1.3.1 = INTEGER: 1 iso.3.6.1.4.1.3699.1.1.12.1.3.1.1.3.2 = INTEGER: 1 iso.3.6.1.4.1.3699.1.1.12.1.4.1.1.1.1 = INTEGER: 1 iso.3.6.1.4.1.3699.1.1.12.1.4.1.1.1.2 = INTEGER: 2 iso.3.6.1.4.1.3699.1.1.12.1.4.1.1.1.3 = INTEGER: 3 iso.3.6.1.4.1.3699.1.1.12.1.4.1.1.1.4 = INTEGER: 4 iso.3.6.1.4.1.3699.1.1.12.1.4.1.1.2.1 = "" iso.3.6.1.4.1.3699.1.1.12.1.4.1.1.2.2 = "" iso.3.6.1.4.1.3699.1.1.12.1.4.1.1.2.3 = "" iso.3.6.1.4.1.3699.1.1.12.1.4.1.1.2.4 = "" iso.3.6.1.4.1.3699.1.1.12.1.4.1.1.3.1 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.4.1.1.3.2 = INTEGER: 130 iso.3.6.1.4.1.3699.1.1.12.1.4.1.1.3.3 = INTEGER: 190 iso.3.6.1.4.1.3699.1.1.12.1.4.1.1.3.4 = INTEGER: 201 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.1.1 = INTEGER: 1 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.1.2 = INTEGER: 2 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.1.3 = INTEGER: 3 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.1.4 = INTEGER: 4 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.1.5 = INTEGER: 5 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.1.6 = INTEGER: 6 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.1.7 = INTEGER: 7 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.1.8 = INTEGER: 8 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.1.9 = INTEGER: 9 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.1.10 = INTEGER: 10 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.1.11 = INTEGER: 11 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.1.12 = INTEGER: 12 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.1.13 = INTEGER: 13 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.1.14 = INTEGER: 14 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.1.15 = INTEGER: 15 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.1.16 = INTEGER: 16 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.1.17 = INTEGER: 17 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.1.18 = INTEGER: 18 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.1.19 = INTEGER: 19 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.1.20 = INTEGER: 20 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.1.21 = INTEGER: 21 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.1.22 = INTEGER: 22 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.1.23 = INTEGER: 23 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.1.24 = INTEGER: 24 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.1.25 = INTEGER: 25 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.1.26 = INTEGER: 26 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.1.27 = INTEGER: 27 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.1.28 = INTEGER: 28 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.1.29 = INTEGER: 29 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.1.30 = INTEGER: 30 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.1.31 = INTEGER: 31 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.1.32 = INTEGER: 32 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.2.1 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.2.2 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.2.3 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.2.4 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.2.5 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.2.6 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.2.7 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.2.8 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.2.9 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.2.10 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.2.11 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.2.12 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.2.13 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.2.14 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.2.15 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.2.16 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.2.17 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.2.18 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.2.19 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.2.20 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.2.21 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.2.22 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.2.23 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.2.24 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.2.25 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.2.26 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.2.27 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.2.28 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.2.29 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.2.30 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.2.31 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.2.32 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.3.1 = STRING: "Temperature" iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.3.2 = STRING: "Temperature" iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.3.3 = STRING: "Temperature" iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.3.4 = STRING: "Temperature" iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.3.5 = STRING: "Temperature" iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.3.6 = STRING: "Temperature" iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.3.7 = STRING: "Temperature" iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.3.8 = STRING: "Temperature" iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.3.9 = STRING: "Temperature" iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.3.10 = STRING: "Temperature" iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.3.11 = STRING: "Temperature" iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.3.12 = STRING: "Temperature" iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.3.13 = STRING: "Temperature" iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.3.14 = STRING: "Temperature" iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.3.15 = STRING: "Temperature" iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.3.16 = STRING: "Temperature" iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.3.17 = STRING: "Temperature" iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.3.18 = STRING: "Temperature" iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.3.19 = STRING: "Temperature" iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.3.20 = STRING: "Temperature" iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.3.21 = STRING: "Temperature" iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.3.22 = STRING: "Temperature" iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.3.23 = STRING: "Temperature" iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.3.24 = STRING: "Temperature" iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.3.25 = STRING: "Temperature" iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.3.26 = STRING: "Temperature" iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.3.27 = STRING: "Temperature" iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.3.28 = STRING: "Temperature" iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.3.29 = STRING: "Temperature" iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.3.30 = STRING: "Temperature" iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.3.31 = STRING: "Temperature" iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.3.32 = STRING: "Temperature" iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.4.1 = INTEGER: 264 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.4.2 = INTEGER: 264 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.4.3 = INTEGER: 264 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.4.4 = INTEGER: 264 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.4.5 = INTEGER: 264 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.4.6 = INTEGER: 264 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.4.7 = INTEGER: 264 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.4.8 = INTEGER: 264 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.4.9 = INTEGER: 264 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.4.10 = INTEGER: 264 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.4.11 = INTEGER: 264 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.4.12 = INTEGER: 264 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.4.13 = INTEGER: 264 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.4.14 = INTEGER: 264 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.4.15 = INTEGER: 264 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.4.16 = INTEGER: 264 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.4.17 = INTEGER: 264 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.4.18 = INTEGER: 264 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.4.19 = INTEGER: 264 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.4.20 = INTEGER: 264 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.4.21 = INTEGER: 264 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.4.22 = INTEGER: 264 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.4.23 = INTEGER: 264 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.4.24 = INTEGER: 264 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.4.25 = INTEGER: 264 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.4.26 = INTEGER: 264 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.4.27 = INTEGER: 264 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.4.28 = INTEGER: 264 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.4.29 = INTEGER: 264 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.4.30 = INTEGER: 264 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.4.31 = INTEGER: 264 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.4.32 = INTEGER: 264 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.5.1 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.5.2 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.5.3 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.5.4 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.5.5 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.5.6 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.5.7 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.5.8 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.5.9 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.5.10 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.5.11 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.5.12 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.5.13 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.5.14 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.5.15 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.5.16 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.5.17 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.5.18 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.5.19 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.5.20 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.5.21 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.5.22 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.5.23 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.5.24 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.5.25 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.5.26 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.5.27 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.5.28 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.5.29 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.5.30 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.5.31 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.5.32 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.6.1 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.6.2 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.6.3 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.6.4 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.6.5 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.6.6 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.6.7 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.6.8 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.6.9 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.6.10 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.6.11 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.6.12 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.6.13 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.6.14 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.6.15 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.6.16 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.6.17 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.6.18 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.6.19 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.6.20 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.6.21 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.6.22 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.6.23 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.6.24 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.6.25 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.6.26 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.6.27 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.6.28 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.6.29 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.6.30 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.6.31 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.6.32 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.7.1 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.7.2 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.7.3 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.7.4 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.7.5 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.7.6 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.7.7 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.7.8 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.7.9 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.7.10 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.7.11 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.7.12 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.7.13 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.7.14 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.7.15 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.7.16 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.7.17 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.7.18 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.7.19 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.7.20 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.7.21 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.7.22 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.7.23 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.7.24 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.7.25 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.7.26 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.7.27 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.7.28 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.7.29 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.7.30 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.7.31 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.5.1.1.7.32 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.6.1.1.1.1 = INTEGER: 1 iso.3.6.1.4.1.3699.1.1.12.1.6.1.1.2.1 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.1.6.1.1.3.1 = INTEGER: 0 iso.3.6.1.4.1.3699.1.1.12.100.1.0.1.0 = NULL iso.3.6.1.4.1.3699.1.1.12.100.1.0.1.0 = No more variables left in this MIB View (It is past the end of the MIB tree) /Steffen -- Steffen Klemer E-Mail: steffen.klemer(a)gwdg.de Tel: +49 551 201 2170 ------------------------------------------------------------------ GWDG - Gesellschaft für wissenschaftliche Datenverarbeitung mbH Göttingen Am Faßberg 11, 37077 Göttingen Service-Hotline: Tel: +49 551 201-1523 E-Mail: support(a)gwdg.de Kontakt: Tel: 0551 201-1510 Fax: 0551 201-2150 E-Mail: gwdg(a)gwdg.de WWW: https://www.gwdg.de ------------------------------------------------------------------ Geschäftsführer: Prof. Dr. Ramin Yahyapour Aufsichtsratsvorsitzender: Prof. Dr. Christian Griesinger Sitz der Gesellschaft: Göttingen Registergericht: Göttingen, Handelsregister-Nr. B 598 ------------------------------------------------------------------ Zertifiziert nach ISO 9001 ------------------------------------------------------------------

2 2

Cisco IE-1000
by Jorgo Schmitz 26 Aug '19

26 Aug '19

Hello all, I have a question regarding Cisco IE-1000-4P2S-LM switch. With following specs: Image : ie1000-universalk9-mz.spa.1.8.0.bin Version : 1.8.0 Chipset ID : VSC7428 Board Type : IE-1000-4P2S-LM Port Count : 6 Product : Cisco IE1000 Switch Code Revision : f61c61e+ Is it a supported device by observium? Because observium does not seem to be recognize the device correctly. It is also does not recognized as Cisco. Does anyone has any idea how to resolve this? Kind regards, Jorgo Schmitz Senior Engineer [cid:image001.png@01D558D6.C5712570]<https://korton.nl/>

3 4

Observium CE 19.8 Release
by adama＠observium.org 24 Aug '19

24 Aug '19

We've just released the new version of Observium CE, 19.8. This release is based on SVN revision 10000 and includes 580 separate commits covering ~50k changed lines of code since the previous release. Upgrade instructions are at https://www.observium.org/docs/updating/#upgrade-to-latest-major-release Changelog is at https://www.observium.org/svn.log Thanks, Adam.

1 0