- Xymon - Xymon mailman web

Using the internal temperature status and graph
by jkincl1＠lsu.edu 23 Jun '11

23 Jun '11

Hi, So I wanted to graph a temperature monitor that is hooked up to a machine and I have the script sending the status as temperature so that I can take advantage of the graph definition that is shipped with xymon. We are using Xymon 4.3.0. I found in the source code how to format the status so that the xymon RRD library for temperature can read it and it is graphing but I am finding that the graph is missing quite a few values, it seems random and there are large holes in my graph where data did not get received. I am logging and the machine is sending the data and all of the other graphs for the machine are solid and contain all data points. Is this a documented bug? Am I doing something wrong? This seems to be an intermittent issue so I am not sure what is causing the problem. Thanks, -------------------- Jason Kincl

1 0

RRD error Creating
by willowbrookmagic＠hotmail.com 23 Jun '11

23 Jun '11

I'm having some promlems with alot of my host not being able to create graphs Here is the rotating cyle with many different hosts in rrd-data.log 2011-06-20 10:19:26 RRD error creating /opt/admin/xymon/linux/current/data/rrd/server1/netstat.rrd: can't parse argument 'TITLE TCP/IP statistics' 2011-06-20 10:19:26 RRD error creating /opt/admin/xymon/linux/current/data/rrd/server1/ifstat.127.0.0.1.rrd: can't parse argument 'FNPATTERN ifstat.(.+).rrd' 2011-06-20 10:19:26 RRD error creating /opt/admin/xymon/linux/current/data/rrd/xymonserver/netstat.rrd: can't parse argument 'TITLE TCP/IP statistics' 2011-06-20 10:19:26 RRD error creating /opt/admin/xymon/linux/current/data/rrd/xymonserver/ifstat.eth0.rrd: can't parse argument 'FNPATTERN ifstat.(.+).rrd' 2011-06-20 10:19:26 RRD error creating /opt/admin/xymon/linux/current/data/rrd/xymonserver/vmstat.rrd: unknown option 'u' Also in rrd.status.log 2011-06-20 15:29:56 RRD error creating /opt/admin/xymon/linux/current/data/rrd/host1/if_load.Fa0_1.rrd: can't parse argument 'FNPATTERN if_load.(.*).rrd' 2011-06-20 15:29:56 RRD error creating /opt/admin/xymon/linux/current/data/rrd/host2/if_load.GigabitEthernet0_0.240.rrd: can't parse argument 'FNPATTERN if_load.(.*).rrd' 2011-06-20 15:29:56 RRD error creating /opt/admin/xymon/linux/current/data/rrd/host3/if_load.GigabitEthernet0_0.240.rrd: can't parse argument 'FNPATTERN if_load.(.*).rrd' 2011-06-20 15:29:58 RRD error creating /opt/admin/xymon/linux/current/data/rrd/host4/memory.real.rrd: unknown option 'u' 2011-06-20 15:29:58 RRD error creating /opt/admin/xymon/linux/current/data/rrd/host4/memory.swap.rrd: unknown option 'u' 2011-06-20 15:29:58 RRD error creating /opt/admin/xymon/linux/current/data/rrd/host4/if_load.Fa0_47.rrd: can't parse argument 'FNPATTERN if_load.(.*).rrd' 2011-06-20 15:29:58 RRD error creating /opt/admin/xymon/linux/current/data/rrd/ny134544swr1a/if_load.Fa0_48.rrd: can't parse argument 'FNPATTERN if_load.(.*).rrd' 2011-06-20 15:30:56 RRD error creating /opt/admin/xymon/linux/current/data/rrd/host5/temp.I_OContOutlet.rrd: can't parse argument 'FNPATTERN temp.(.*).rrd' 2011-06-20 15:30:56 RRD error creating /opt/admin/xymon/linux/current/data/rrd/host5/temp.NPEInlet.rrd: can't parse argument 'FNPATTERN temp.(.*).rrd' In graph.cfg [netstat] TITLE TCP/IP statistics YAXIS Packets/second DEF:tcpInInorderPackets=netstat.rrd:tcpInInorderPackets:AVERAGE DEF:tcpOutDataPackets=netstat.rrd:tcpOutDataPackets:AVERAGE DEF:tcpRetransPackets=netstat.rrd:tcpRetransPackets:AVERAGE LINE3:tcpInInorderPackets#00FF00:In LINE1:tcpOutDataPackets#0000FF:Out LINE2:tcpRetransPackets#FF0000:Retrans COMMENT:\n GPRINT:tcpInInorderPackets:LAST:In \: %5.1lf%s (cur) GPRINT:tcpInInorderPackets:MAX: \: %5.1lf%s (max) GPRINT:tcpInInorderPackets:MIN: \: %5.1lf%s (min) GPRINT:tcpInInorderPackets:AVERAGE: \: %5.1lf%s (avg)\n GPRINT:tcpOutDataPackets:LAST:Out \: %5.1lf%s (cur) GPRINT:tcpOutDataPackets:MAX: \: %5.1lf%s (max) GPRINT:tcpOutDataPackets:MIN: \: %5.1lf%s (min) GPRINT:tcpOutDataPackets:AVERAGE: \: %5.1lf%s (avg)\n GPRINT:tcpRetransPackets:LAST:Retrans \: %5.1lf%s (cur) GPRINT:tcpRetransPackets:MAX: \: %5.1lf%s (max) GPRINT:tcpRetransPackets:MIN: \: %5.1lf%s (min) GPRINT:tcpRetransPackets:AVERAGE: \: %5.1lf%s (avg)\n [ifstat] FNPATTERN ^ifstat.(.+).rrd TITLE Network Traffic YAXIS Bits/second DEF:inbytes at RRDIDX@=@RRDFN@:bytesReceived:AVERAGE CDEF:in at RRDIDX@=inbytes at RRDIDX@,8,* DEF:outbytes at RRDIDX@=@RRDFN@:bytesSent:AVERAGE CDEF:out at RRDIDX@=outbytes at RRDIDX@,8,* LINE2:in at RRDIDX@#@COLOR@:@RRDPARAM@ inbound GPRINT:in at RRDIDX@:LAST: \: %10.1lf (cur) GPRINT:in at RRDIDX@:MAX: \: %10.1lf (max) GPRINT:in at RRDIDX@:MIN: \: %10.1lf (min) GPRINT:in at RRDIDX@:AVERAGE: \: %10.1lf (avg)\n LINE2:out at RRDIDX@#@COLOR@:@RRDPARAM@ outbound GPRINT:out at RRDIDX@:LAST: \: %10.1lf (cur) GPRINT:out at RRDIDX@:MAX: \: %10.1lf (max) GPRINT:out at RRDIDX@:MIN: \: %10.1lf (min) GPRINT:out at RRDIDX@:AVERAGE: \: %10.1lf (avg)\n [vmstat] TITLE CPU Utilization YAXIS % Load -u 100 -r DEF:cpu_idl=vmstat.rrd:cpu_idl:AVERAGE DEF:cpu_usr=vmstat.rrd:cpu_usr:AVERAGE DEF:cpu_sys=vmstat.rrd:cpu_sys:AVERAGE AREA:cpu_sys#FF0000:System STACK:cpu_usr#FFFF00:User STACK:cpu_idl#00FF00:Idle COMMENT:\n GPRINT:cpu_sys:LAST:System \: %5.1lf (cur) GPRINT:cpu_sys:MAX: \: %5.1lf (max) GPRINT:cpu_sys:MIN: \: %5.1lf (min) GPRINT:cpu_sys:AVERAGE: \: %5.1lf (avg)\n GPRINT:cpu_usr:LAST:User \: %5.1lf (cur) GPRINT:cpu_usr:MAX: \: %5.1lf (max) GPRINT:cpu_usr:MIN: \: %5.1lf (min) GPRINT:cpu_usr:AVERAGE: \: %5.1lf (avg)\n GPRINT:cpu_idl:LAST:Idle \: %5.1lf (cur) GPRINT:cpu_idl:MAX: \: %5.1lf (max) GPRINT:cpu_idl:MIN: \: %5.1lf (min) GPRINT:cpu_idl:AVERAGE: \: %5.1lf (avg)\n [ram] TITLE RAM Utilization YAXIS % Used DEF:p=memory.real.rrd:realmempct:AVERAGE LINE2:p#0000FF:% RAM used -u 100 -b 1024 GPRINT:p:LAST: \: %5.1lf (cur) GPRINT:p:MAX: \: %5.1lf (max) GPRINT:p:MIN: \: %5.1lf (min) GPRINT:p:AVERAGE: \: %5.1lf (avg)\n [swap] TITLE Swap Utilization YAXIS % Used DEF:p=memory.swap.rrd:realmempct:AVERAGE LINE2:p#0000FF:% Swap used -u 100 -b 1024 GPRINT:p:LAST: \: %5.1lf (cur) GPRINT:p:MAX: \: %5.1lf (max) GPRINT:p:MIN: \: %5.1lf (min) GPRINT:p:AVERAGE: \: %5.1lf (avg)\n

1 2

msgcache for Windows Clients?
by hj.beckers＠kreis-steinfurt.de 22 Jun '11

22 Jun '11

I'm using msgcache for 2 linux xymon clients in a dmz and it works well since a few years. Now we add two Windows clients into the dmz and would like to monitor them as well using bbwin 0.12. But there is no msgcache functionality for Windows? Would the following solution work? I would install/activate xymonproxy on one ot the linux clients and point it to the msgcache on the same linux client (using different ports). And the windows clients will report to the xymonproxy process on this linux client? Any comments/tips? Yours hjb

1 1

BBWin in centralized mode
by lebarber＠gmail.com 21 Jun '11

21 Jun '11

I recently converted a few Windows boxes over to centralized collecting mode. Now the application log in those machines is being filled up with messages like this: BBWin failed to send the client data successfuly to the hobbit server. The error was : Can't receive query answer : An existing connection was forcibly closed by the remote host.. every time BBWin sends data to my Xymon server. Has anybody else seen this? Any recommendations as how to stop this? This is with BBWin 0.12 clients and Xymon 4.3.3 for the server. Thanks, Larry Barber

1 0

Flapping Status
by David.Raymond＠ca.ebarrette.com 20 Jun '11

20 Jun '11

Hi all, I don't know if you share the same idea as me, but could we add "Flapping Status" as an option in xymonserver.cfg ? We can set it as "yes or no" or other setting, or simply add a flappingstatus.cfg and add system that we want to manage. It is possible ? Keep going good work.

1 0

Xymon capabilities
by gbolly_bolly＠yahoo.com 20 Jun '11

20 Jun '11

Hello, Could you please confirm the following for me on the functionality of the Xymon system We are evaluating the features of Xymon in my company (Novodisk Ultima Solutions..ITIL Certified) 1. Can Xymon do Out of band monitoring? 2. Bola Al Olaniyi Mobile:+1(403)-702-6061 Home: :+1(403)-800-2798 *Email: olaniyi at telus.net

3 2

Showing alerts for rules with GROUP tag on the info page
by Raymond.Lee＠qwest.com 17 Jun '11

17 Jun '11

One of the features that I like about Xymon is being able to click on the "info" column for a host to see all the logistics of who gets alerted for which tests. However, if you've got rules tagged with something like this in analysis.cfg: HOST=jdoeserver DISK /usr 85 90 GROUP=pagejdoe and then add an entry to alerts.cfg that looks something like this: GROUP=pagejdoe COLOR=red MAIL jdoe at company.com then the info page doesn't show the alerting that goes to jdoe at company.com (even though the mail does go out). So the functionality of GROUP tagging works fine, but the presentation of it on the info page is lacking. Is there a patch or workaround to achieve what I'm asking for? Thanks, Ray This communication is the property of Qwest and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments.

2 1

xymon MQ monitoring
by unixdude＠hotmail.co.uk 17 Jun '11

17 Jun '11

Hi, I am trying to use xymon to get a view on MQ queues and channels but am not enjoying any success. Here’s my setup: - Server OS Centos 5.6 Xymon Server 4.3.3 Client OS AIX 5300-9 Hobbit client 4.2.0-9 I have MQ version 6.0.2.8 running on the client. Client-side; I seem to be okay. The client is sending information about MQ to the xymon server. The data looks like: - client/mqcollect ukclaqh01.mqcollect mqcollect 5724-H72 (C) Copyright IBM Corp. 1994, 2005. ALL RIGHTS RESERVED. Starting MQSC for queue manager PCMS1. 1 : display qlocal(*) curdepth AMQ8409: Display Queue details. QUEUE(AMQ.MQEXPLORER.66061296) TYPE(QLOCAL) CURDEPTH(0) AMQ8409: Display Queue details. QUEUE(CUSTOMER.CMSADDRESS.UPDATE.LQ) TYPE(QLOCAL) CURDEPTH(0) AMQ8409: Display Queue details. QUEUE(CUSTOMER.CMSLEDGER.TRANSACTION.CREATE.LQ) TYPE(QLOCAL) CURDEPTH(0) … … … AMQ8409: Display Queue details. QUEUE(SYSTEM.PENDING.DATA.QUEUE) TYPE(QLOCAL) CURDEPTH(0) One MQSC command read. No commands have a syntax error. All valid MQSC commands were processed. I’ve highlighted the first line as I think that this may be important. At the xymon server I have added the following stanza to the analysis.cfg file: - HOST=ukclaqh01 # MQ_QUEUE CUSTOMER.* MQ_QUEUE "CUSTOMER.CMSADDRESS.UPDATE.LQ" MQ_QUEUE SYSTEM.CLUSTER.REPOSITORY.QUEUE [depth-warning=1] MQ_CHANNEL * But… no joy! Any help would be gratefully received. Ross

1 0

xymon MQ monitoring
by Ross.Bradley＠express-gifts.co.uk 17 Jun '11

17 Jun '11

Hi, I am trying to use xymon to get a view on MQ queues and channels but am not enjoying any success. Here's my setup: - Server OS Centos 5.6 Xymon Server 4.3.3 Client OS AIX 5300-9 Hobbit client 4.2.0-9 I have MQ version 6.0.2.8 running on the client. Client-side; I seem to be okay. The client is sending information about MQ to the xymon server. The data looks like: - client/mqcollect ukclaqh01.mqcollect mqcollect 5724-H72 (C) Copyright IBM Corp. 1994, 2005. ALL RIGHTS RESERVED. Starting MQSC for queue manager PCMS1. 1 : display qlocal(*) curdepth AMQ8409: Display Queue details. QUEUE(AMQ.MQEXPLORER.66061296) TYPE(QLOCAL) CURDEPTH(0) AMQ8409: Display Queue details. QUEUE(CUSTOMER.CMSADDRESS.UPDATE.LQ) TYPE(QLOCAL) CURDEPTH(0) AMQ8409: Display Queue details. QUEUE(CUSTOMER.CMSLEDGER.TRANSACTION.CREATE.LQ) TYPE(QLOCAL) CURDEPTH(0) ... ... ... AMQ8409: Display Queue details. QUEUE(SYSTEM.PENDING.DATA.QUEUE) TYPE(QLOCAL) CURDEPTH(0) One MQSC command read. No commands have a syntax error. All valid MQSC commands were processed. I've highlighted the first line as I think that this may be important. At the xymon server I have added the following stanza to the analysis.cfg file: - HOST=ukclaqh01 # MQ_QUEUE CUSTOMER.* MQ_QUEUE "CUSTOMER.CMSADDRESS.UPDATE.LQ" MQ_QUEUE SYSTEM.CLUSTER.REPOSITORY.QUEUE [depth-warning=1] MQ_CHANNEL * But... no joy! Any help would be gratefully received. Ross Name & Registered Office: EXPRESS GIFTS LIMITED, 2 GREGORY ST, HYDE, CHESHIRE, ENGLAND, SK14 4TH, Company No. 00718151. Express Gifts Limited is authorised and regulated by the Financial Services Authority ------------ NOTE: This email and any information contained within or attached in a separate file is confidential and intended solely for the Individual to whom it is addressed. The information or data included is solely for the purpose indicated or previously agreed. Any information or data included with this e-mail remains the property of Findel PLC and the recipient will refrain from utilising the information for any purpose other than that indicated and upon request will destroy the information and remove it from their records. Any views or opinions presented are solely those of the author and do not necessarily represent those of Findel PLC. If you are not the intended recipient, be advised that you have received this email in error and that any use, dissemination, forwarding, printing, or copying of this email is strictly prohibited. No warranties or assurances are made in relation to the safety and content of this e-mail and any attachments. No liability is accepted for any consequences arising from it. Findel Plc reserves the right to monitor all e-mail communications through its internal and external networks. If you have received this email in error please notify our IT helpdesk on +44(0) 1254 303030

1 0

FW: hobbitd.log and rrd-status.log
by tm＠freedom.com 17 Jun '11

17 Jun '11

________________________________________ From: Tim McCloskey Sent: Friday, June 17, 2011 8:55 AM To: Nordquist, Daniel Subject: RE: hobbitd.log and rrd-status.log The Oversize status msg can be fixed by increasing the MAXMSG_STATUS var in hobbitserver.cfg (or the equiv xymon named file). the rrdtool errors appear to be claiming that not enough time has lapsed between updates (min 1 second) though I don't have an immediate answer to that one.... ________________________________________ From: xymon-bounces at xymon.com [xymon-bounces at xymon.com] On Behalf Of Nordquist, Daniel [Daniel.Nordquist at orlandohealth.com] Sent: Friday, June 17, 2011 8:23 AM To: xymon at xymon.com Subject: [Xymon] hobbitd.log and rrd-status.log Pasting the tail of these logs for examples of log data causing these files to grow very fast and get huge… Any settings anyone knows about that can help with these? Thanks, Dan myhobbitserver:/xymon/server/etc # ll ../../log/ total 506269 -rw-r--r-- 1 xymon xymon 9595 Jun 17 07:55 acknowledge.log -rw-r--r-- 1 xymon xymon 1341 Jan 30 18:10 bb-display.log -rw-r--r-- 1 xymon xymon 18029503 Jun 17 11:01 bb-network.log -rw-r--r-- 1 xymon xymon 246218 Jun 14 16:36 bb-retest.log -rw-r--r-- 1 xymon xymon 0 Nov 17 2010 bbcombotest.log -rw-r--r-- 1 xymon xymon 1463 Jun 13 08:33 clientdata.log -rw-r--r-- 1 xymon xymon 675989 Jun 16 03:37 history.log -rw-r--r-- 1 xymon xymon 4167 Apr 3 02:31 hobbitclient.log -rw-r--r-- 1 xymon xymon 27027329 Jun 17 11:04 hobbitd.log -rw-r--r-- 1 xymon xymon 5 Jun 13 08:33 hobbitd.pid -rw-r--r-- 1 xymon xymon 7776 Jun 13 08:33 hobbitlaunch.log -rw-r--r-- 1 xymon xymon 5 Jun 13 08:33 hobbitlaunch.pid -rw-r--r-- 1 xymon xymon 1161 Jun 13 08:33 hostdata.log -rw-r--r-- 1 xymon xymon 173370 Jun 17 10:58 notifications.log -rw-r--r-- 1 xymon xymon 41163 Jun 13 08:33 page.log -rw-r--r-- 1 xymon xymon 87301 Jun 15 22:10 rrd-data.log -rw-r--r-- 1 xymon xymon 472091224 Jun 17 11:04 rrd-status.log myhobbitserver:/xymon/server/etc # tail ../../log/rrd-status.log 2011-06-17 11:06:07 RRD error updating /xymon/data/rrd/aserverwehavexoxo/disk,Replica.rrd from 0.0.0.0: /xymon/data/rrd/aserverwehavexoxo/disk,Replica.rrd: illegal attempt to update using time 1308323167 when last update time is 1308323167 (minimum one second step) 2011-06-17 11:06:07 RRD error updating /xymon/data/rrd/aserverwehavexoxo/disk,Replica.rrd from 0.0.0.0: /xymon/data/rrd/aserverwehavexoxo/disk,Replica.rrd: illegal attempt to update using time 1308323167 when last update time is 1308323167 (minimum one second step) 2011-06-17 11:06:07 RRD error updating /xymon/data/rrd/aserverwehavexoxo/disk,Replica.rrd from 0.0.0.0: /xymon/data/rrd/aserverwehavexoxo/disk,Replica.rrd: illegal attempt to update using time 1308323167 when last update time is 1308323167 (minimum one second step) 2011-06-17 11:06:07 RRD error updating /xymon/data/rrd/aserverwehavexoxo/disk,Replica.rrd from 0.0.0.0: /xymon/data/rrd/aserverwehavexoxo/disk,Replica.rrd: illegal attempt to update using time 1308323167 when last update time is 1308323167 (minimum one second step) 2011-06-17 11:06:07 RRD error updating /xymon/data/rrd/aserverwehavexoxo/disk,Replica.rrd from 0.0.0.0: /xymon/data/rrd/aserverwehavexoxo/disk,Replica.rrd: illegal attempt to update using time 1308323167 when last update time is 1308323167 (minimum one second step) 2011-06-17 11:06:07 RRD error updating /xymon/data/rrd/aserverwehavexoxo/disk,Replica.rrd from 0.0.0.0: /xymon/data/rrd/aserverwehavexoxo/disk,Replica.rrd: illegal attempt to update using time 1308323167 when last update time is 1308323167 (minimum one second step) 2011-06-17 11:06:07 RRD error updating /xymon/data/rrd/aserverwehavexoxo/disk,Replica.rrd from 0.0.0.0: /xymon/data/rrd/aserverwehavexoxo/disk,Replica.rrd: illegal attempt to update using time 1308323167 when last update time is 1308323167 (minimum one second step) 2011-06-17 11:06:16 RRD error updating /xymon/data/rrd/aserverwehavexoxoDB/disk,ArcData.rrd from 0.0.0.0: /xymon/data/rrd/aserverwehavexoxoDB/disk,ArcData.rrd: illegal attempt to update using time 1308323176 when last update time is 1308323176 (minimum one second step) 2011-06-17 11:06:16 RRD error updating /xymon/data/rrd/aserverwehavexoxoDB/disk,ArcData.rrd from 0.0.0.0: /xymon/data/rrd/aserverwehavexoxoDB/disk,ArcData.rrd: illegal attempt to update using time 1308323176 when last update time is 1308323176 (minimum one second step) 2011-06-17 11:06:16 RRD error updating /xymon/data/rrd/aserverwehavexoxoDB/disk,ArcData.rrd from 0.0.0.0: /xymon/data/rrd/aserverwehavexoxoDB/disk,ArcData.rrd: illegal attempt to update using time 1308323176 when last update time is 1308323176 (minimum one second step) myhobbitserver:/xymon/server/etc # tail ../../log/hobbitd.log 2011-06-17 11:05:30 Oversize status msg from 0.0.0.0 for aserverwehave02:msgs truncated (n=4395866, limit=262144) 2011-06-17 11:05:33 Oversize page/ack/notify msg from 0.0.0.0 for aserverwehave07:msgs truncated (n=397060, limit=262144) 2011-06-17 11:05:33 Oversize status msg from 0.0.0.0 for aserverwehavew07:msgs truncated (n=397047, limit=262144) 2011-06-17 11:05:44 Oversize status msg from hobbitd for aserverwehaveO03:msgs truncated (n=2949154, limit=262144) 2011-06-17 11:06:11 Oversize page/ack/notify msg from 0.0.0.0 for aserverwehavefs02:msgs truncated (n=792109, limit=262144) 2011-06-17 11:06:11 Oversize status msg from 0.0.0.0 for aserverwehaves02:msgs truncated (n=792097, limit=262144) 2011-06-17 11:06:22 Oversize page/ack/notify msg from 0.0.0.0 for aserverwehavexk:msgs truncated (n=318828, limit=262144) 2011-06-17 11:06:22 Oversize status msg from 0.0.0.0 for aserverwehavexank:msgs truncated (n=318794, limit=262144) 2011-06-17 11:06:26 Oversize page/ack/notify msg from 0.0.0.0 for aserverwehaves02:msgs truncated (n=365810, limit=262144) 2011-06-17 11:06:26 Oversize status msg from 0.0.0.0 for aserverwehavesv02:msgs truncated (n=365792, limit=262144) myhobbitserver:/xymon/server/etc # Note – I changed the IP’s to 0.0.0.0 and server names to garbage. ________________________________ This e-mail message and any attached files are confidential and are intended solely for the use of the addressee(s) named above. If you are not the intended recipient, any review, use, or distribution of this e-mail message and any attached files is strictly prohibited. This communication may contain material protected by Federal privacy regulations, attorney-client work product, or other privileges. If you have received this confidential communication in error, please notify the sender immediately by reply e-mail message and permanently delete the original message. To reply to our email administrator directly, send an email to: postmaster at orlandohealth.com . If this e-mail message concerns a contract matter, be advised that no employee or agent is authorized to conclude any binding agreement on behalf of Orlando Health by e-mail without express written confirmation by an officer of the corporation. Any views or opinions presented in this e-mail are solely those of the author and do not necessarily represent those of Orlando Health.

1 0