SNMP::Info - Object Oriented Perl5 Interface to Network devices and MIBs through SNMP.
SNMP::Info - Version 0.10
SNMP::Info was created at UCSC for the netdisco project (www.netdisco.org) and is written and maintained by Max Baker.
use SNMP::Info;
my $info = new SNMP::Info(
# Auto Discover more specific Device Class
AutoSpecify => 1,
Debug => 1,
# The rest is passed to SNMP::Session
DestHost => 'router',
Community => 'public',
Version => 2
) or die "Can't connect to device.\n";
my $err = $info->error(); die "SNMP Community or Version probably wrong connecting to device. $err\n" if defined $err;
$name = $info->name(); $class = $info->class(); print "SNMP::Info is using this device class : $class\n";
# Find out the Duplex status for the ports my $interfaces = $info->interfaces(); my $i_duplex = $info->i_duplex();
# Get CDP Neighbor info my $c_if = $info->c_if(); my $c_ip = $info->c_ip(); my $c_port = $info->c_port();
# Print out data per port
foreach my $iid (keys %$interfaces){
my $duplex = $i_duplex->{$iid};
# Print out physical port name, not snmp iid
my $port = $interfaces->{$iid};
# The CDP Table has table entries different than the interface tables.
# So we use c_if to get the map from cdp table to interface table.
my %c_map = reverse %$c_if;
my $c_key = $c_map{$iid};
my $neighbor_ip = $c_ip->{$c_key};
my $neighbor_port = $c_port->{$c_key};
print "$port: $duplex duplex";
print " connected to $neighbor_ip / $neighbor_port\n" if defined $remote_ip;
print "\n";
}
Please direct all support, help, and bug requests to the snmp-info-users Mailing List at <http://lists.sourceforge.net/lists/listinfo/snmp-info-users>.
SNMP::Info gives an object oriented interface to information obtained through SNMP.
This module lives at http://snmp-info.sourceforge.net Check for newest version and documentation.
This module is geared towards network devices. Subclasses exist for a number of network devices and common MIBs.
The idea behind this module is to give a common interface to data from network devices, leaving the device-specific hacks behind the scenes in subclasses.
In the SYNOPSIS example we fetch the name of all the ports on the device and the duplex
setting for that port with two methods -- interfaces() and i_duplex().
The information may be coming from any number of MIB files and is very vendor specific. SNMP::Info provides you a common method for all supported devices.
Adding support for your own device is easy, and takes little SNMP knowledge.
The module is not limited to network devices. Any MIB or device can be given an objected oriented front-end by making a module that consists of a couple hashes. See EXTENDING SNMP::INFO.
DO NOT INSTALL SNMP:: or Net::SNMP from CPAN!
The SNMP module is matched to an install of net-snmp, and must be installed from the net-snmp source tree.
The Perl module SNMP is found inside the net-snmp distribution. Go to the perl/ directory
of the distribution to install it, or run ./configure --with-perl-modules from the top directory
of the net-snmp distribution.
Net-SNMP can be found at http://net-snmp.sourceforge.net
Version 5.1.2 or greater is recommended.
Various version 4's and 5.0 and 5.1 series will work. 5.0.1 is kinda flaky on the Perl side.
Redhat Users: Certain versions that comes with certain versions of Redhat/Fedora doesn't have the Perl library installed. Uninstall the RPM and install by hand.
If you are using SNMP::Info separate from Netdisco, download the Netdisco-MIB package at
http://sourceforge.net/project/showfiles.php?group_id=80033&package_id=135517
Make sure that your snmp.conf is updated to point to your MIB directory and that the MIBs are world-readable.
To do it by hand:
Then run snmpconf and setup that directory as default. Move snmp.conf
into /usr/local/share/snmp when you are done.
To install them :
mkdir -p /usr/local/share/snmp/mibs && cd /usr/local/share/snmp/mibs && tar xvfz /path/to/v2.tar.gz
Extract
by running
mkdir -p /usr/local/share/snmp/mibs cd /usr/local/share/snmp/mibs tar xvfz /path/to/v1.tar.gz BRIDGE-MIB.my SNMP-REPEATER-MIB.my ESSWITCH-MIB.my TOKEN-RING-RMON-MIB.my
Check below under each subclass for requirements.
23
SNMP::Info will ask for RFC1213-MIB::ifType and will get back ppp.
Or you can override any existing methods from a parent class by making a short subroutine.
See the section EXTENDING SNMP::INFO for more details.
When you make a new subclass for a device, please be sure to send it back to the developers (via Source Forge or the mailing list) for inclusion in the next version.
These are the subclasses that implement MIBs and support devices:
Required MIBs not included in the install instructions above are noted here.
These subclasses implement method to access one or more MIBs. These are not used directly, but rather inherited from device subclasses.
For more info run perldoc on any of the following module names.
These subclasses inherit from one or more classes to provide a common interface to data obtainable from network devices.
All the required MIB files are included in the netdisco-mib package. (See Above).
Requires ATI-MIB
See SNMP::Info::Layer1::Allied for where to get MIBs required.
Requires ASANTE-HUB1012-MIB
See SNMP::Info::Layer1::Asante for where to get MIBs required.
See SNMP::Info::Layer1::Bayhub for where to get MIBs required.
See SNMP::Info::Layer2::Baystack for where to get MIBs required.
wsc. Note that this class
does not support everything that has the name Catalyst.
See SNMP::Info::Layer2::Centillion for where to get MIBs required.
Requires HP-ICF-OID and ENTITY-MIB downloaded from HP.
See SNMP::Info::Layer2::HP for more info.
See SNMP::Info::Layer2::NAP222x for where to get MIBs required.
MIBs for these devices now included in v2.tar.gz available from ftp.cisco.com.
Note Layer2::Aironet
See SNMP::Info::Layer3::AlteonAD for where to get MIBs required.
See SNMP::Info::Layer3::BayRS for where to get MIBs required.
See SNMP::Info::Layer3::Contivity for where to get MIBs required.
Requires FOUNDRY-SN-ROOT-MIB.
See SNMP::Info::Layer3::Foundry for more info.
See SNMP::Info::Layer3::Passport for where to get MIBs required.
Thanks for testing and coding help (in no particular order) to : Andy Ford, Brian Wilson, Jean-Philippe Luiggi, Dána Watanabe, Bradley Baetz, Eric Miller, and people listed on the Netdisco README!
new()
my $info = new SNMP::Info( 'Debug' => 1,
'AutoSpecify' => 1,
'BigInt' => 1,
'BulkWalk' => 1,
'BulkRepeaters'=> 20,
'DestHost' => 'myrouter',
'Community' => 'public',
'Version' => 2,
'MibDirs' => ['dir1','dir2','dir3'],
) or die;
SNMP::Info Specific Arguments :
(default on)
(default off)
0 to turn off BULKWALK commands for SNMPv2 connections.
Note that BULKWALK is turned off for Net-SNMP versions 5.1.x because of a bug.
(default on)
perldoc SNMP -> bulkwalk() for more info.
(default 20)
(default off)
(default use net-snmp settings only)
(default true)
(default creates session automatically)
See SNMP::Session for a list of other possible arguments.
A Note about the wrong Community string or wrong SNMP Version:
If a connection is using the wrong community string or the wrong SNMP version,
the creation of the object will not fail. The device still answers the call on
the SNMP port, but will not return information. Check the error() method after
you create the device object to see if there was a problem in connecting.
A note about SNMP Versions :
Some older devices don't support SNMP version 2, and will not return anything when a connection under Version 2 is attempted.
Some newer devices will support Version 1, but will not return all the data they might have if you had connected under Version 1
When trying to get info from a new device, you may have to try version 2 and then fallback to version 1.
Methods and subroutines requesting data from a device will only load the data once, and then return cached versions of that data.
Run $info->load_METHOD() where method is something like 'i_name' to reload data from a
table method.
Run $info->clear_cache() to clear the cache to allow reload of both globals and table methods.
These are for package related data, not direcly supplied from SNMP.
clear_cache()debug(1)device_type()SNMP::Info is returned if no more
specific class is available.
First the device is checked for Layer 3 support and a specific subclass, then Layer 2 support and subclasses are checked for.
This means that Layer 2 / 3 switches and routers will fall under the SNMP::Info::Layer3 subclasses.
If the device still can be connected to via SNMP::Info, then SNMP::Info is returned.
Algorithm for Subclass Detection:
Layer3 Support -> SNMP::Info::Layer3
Aironet (BR500,AP340,350,1200) -> SNMP::Info::Layer3::Aironet
AP4800... All Non IOS
Catalyst 3550,3548,3560 -> SNMP::Info::Layer3::C3550
Catalyst 6500, 4000, 3750 -> SNMP::Info::Layer3::C6500
Cisco Generic L3 IOS device -> SNMP::Info::Layer3::Cisco
Foundry -> SNMP::Info::Layer3::Foundry
Nortel Passport LAN -> SNMP::Info::Layer3::Passport
Alteon Ace Director -> SNMP::Info::Layer3::AlteonAD
Nortel Contivity -> SNMP::Info::Layer3::Contivity
Nortel BayRS Router -> SNMP::Info::Layer3::BayRS
Elsif Layer2 (no Layer3) -> SNMP::Info::Layer2
Aironet - IOS Devices -> SNMP::Info::Layer2::Aironet
Catalyst 1900 -> SNMP::Info::Layer2::C1900
Catalyst 2900XL,2950,3500XL -> SNMP::Info::Layer2::C2900
Catalyst 2970 -> SNMP::Info::Layer3::C6500
Catalyst 3550/3548 -> SNMP::Info::Layer3::C3550
Catalyst WS-C 2926,5xxx -> SNMP::Info::Layer2::Catalyst
HP Procurve -> SNMP::Info::Layer2::HP
Nortel/Bay Centillion ATM -> SNMP::Info::Layer2::Centillion
Nortel/Bay Baystack -> SNMP::Info::Layer2::Baystack
Nortel AP 222x -> SNMP::Info::Layer2::NAP222x
Orinco AP -> SNMP::Info::Layer2::Orinoco
Elsif Layer1 Support -> SNMP::Info::Layer1
Allied -> SNMP::Info::Layer1::Allied
Asante -> SNMP::Info::Layer1::Asante
Nortel/Bay Hub -> SNMP::Info::Layer1::Bayhub
Else -> SNMP::Info
ZyXEL_DSLAM -> SNMP::Info::Layer2::ZyXEL_DSLAM
error(no_clear)Reading the error will clear the error unless you set the no_clear flag.
has_layer(3)Returns undef if the device doesn't support the layers() call.
snmp_comm()snmp_ver()specify()my $info = new SNMP::Info(...); # Returns more specific object type $info = $info->specific();
Usually this method is called internally from new(AutoSpecify => 1)
See device_type() entry for how a subclass is chosen.
cisco_comm_indexing()See ftp://ftp.cisco.com/pub/mibs/supportlists/wsc5000/wsc5000-communityIndexing.html
These are methods to return scalar data from RFC1213.
Some subset of these is probably available for any network device that speaks SNMP.
uptime()(sysUpTime)
contact()name()location()layers()
eg: 01000010 means layers 2 (physical) and 7 (Application)
are served.
Note: This string is 8 digits long.
See $info->has_layer()
(sysServices)
ports()Not too useful as the number of SNMP interfaces usually does not correspond with the number of physical ports
(ifNumber)
Each of these methods returns a hash_reference to a hash keyed on the interface index in SNMP.
Example : $info->interfaces() might return
{ '1.12' => 'FastEthernet/0',
'2.15' => 'FastEthernet/1',
'9.99' => 'FastEthernet/2'
}
The key is what you would see if you were to do an snmpwalk, and in some cases changes between reboots of the network device.
If you want to get only a part of an SNMP table and you know the IID for the part of the table that you want, you can specify it in the call:
$local_routes = $info->ipr_route('192.168.0');
This will only fetch entries in the table that start with 192.168.0, which in this case are routes on the local
network.
Remember that you must supply the partial IID (a numeric OID).
Partial table results are not cached.
interfaces()if_ignore()Ignored interfaces are ones that are usually not physical ports or Virtual Lans (VLANs) such as the Loopback interface, or the CPU interface.
i_index()(ifIndex)
i_description()(ifDescr)
i_type()(ifType)
i_mtu()(ifMtu)
i_speed()munge_speed() later in document for details.
(ifSpeed)
i_mac()(ifPhysAddress)
i_up()(ifOperStatus)
i_up_admin()(ifAdminStatus)
i_lastchange()(IfLastChange)
i_name()(ifName)
i_alias()(ifAlias)
i_octets_out64()Number of octets sent/received on the interface including framing characters.
64 bit version may not exist on all devices.
NOTE: To manipulate 64 bit counters you need to use Math::BigInt, since the values
are too large for a normal Perl scalar. Set the global $SNMP::Info::BIGINT to 1 , or
pass the BigInt value to new() if you want SNMP::Info to do it for you.
(ifInOctets) (ifOutOctets) (ifHCInOctets) (ifHCOutOctets)
i_errors_out()(ifInErrors) (ifOutErrors)
i_pkts_ucast_out64()64 bit version may not exist on all devices.
(ifInUcastPkts) (ifOutUcastPkts) (ifHCInUcastPkts) (ifHCOutUcastPkts)
These methods are depricated by i_pkts_multi_in() and i_pkts_bcast_in()
according to IF-MIB. Actual device usage may vary.
(ifInNUcastPkts) (ifOutNUcastPkts)
i_pkts_multi_in() $info->i_pkts_multi_out(),
$info->i_pkts_multi_in64(), $info->i_pkts_multi_out64()64 bit version may not exist on all devices.
(ifInMulticastPkts) (ifOutMulticastPkts) (ifHCInMulticastPkts) (ifHCOutMulticastPkts)
i_pkts_bcast_in() $info->i_pkts_bcast_out(),
$info->i_pkts_bcast_in64() $info->i_pkts_bcast_out64()64 bit version may not exist on all devices.
(ifInBroadcastPkts) (ifOutBroadcastPkts) (ifHCInBroadcastPkts) (ifHCOutBroadcastPkts)
Each entry in this table is an IP address in use on this device. Usually this is implemented in Layer3 Devices.
ip_index()(ipAdEntIfIndex)
ip_table()(ipAdEntAddr)
ip_netmask()(ipAdEntNetMask)
ip_broadcast()(ipAdEntBcastAddr)
ipr_route()(ipRouteDest)
ipr_if()interfaces() to map.
(ipRouteIfIndex)
ipr_1()(ipRouteMetric1)
ipr_2()(ipRouteMetric2)
ipr_3()ipRouteMetric3)
ipr_4()ipRouteMetric4)
ipr_5()ipRouteMetric5)
ipr_dest()"The IP address of the next hop of this route. (In the case of a route bound to an interface which is realized via a broadcast media, the value of this field is the agent's IP address on that interface.)"
(ipRouteNextHop)
ipr_type()
other(1), -- none of the following
invalid(2), -- an invalidated route
-- route to directly
direct(3), -- connected (sub-)network
-- route to a non-local
indirect(4) -- host/network/sub-network
"The type of route. Note that the values
direct(3) and indirect(4) refer to the notion of
direct and indirect routing in the IP
architecture.
Setting this object to the value invalid(2) has
the effect of invalidating the corresponding entry
in the ipRouteTable object. That is, it
effectively disassociates the destination
identified with said entry from the route
identified with said entry. It is an
implementation-specific matter as to whether the
agent removes an invalidated entry from the table.
Accordingly, management stations must be prepared
to receive tabular information from agents that
corresponds to entries not currently in use.
Proper interpretation of such entries requires
examination of the relevant ipRouteType object."
(ipRouteType)
ipr_proto()
other(1), -- none of the following
-- non-protocol information,
-- e.g., manually configured
local(2), -- entries
-- set via a network
netmgmt(3), -- management protocol
-- obtained via ICMP,
icmp(4), -- e.g., Redirect
-- the remaining values are
-- all gateway routing
-- protocols
egp(5),
ggp(6),
hello(7),
rip(8),
is-is(9),
es-is(10),
ciscoIgrp(11),
bbnSpfIgp(12),
ospf(13),
bgp(14)
(ipRouteProto)
ipr_age()(ipRouteAge)
ipr_mask()(ipRouteMask)
ipr_info()(ipRouteInfo)
This section explains how to use SNMP::Info to do SNMP Set operations.
set_METHOD($value)Returns undef if failed, or the return value from SNMP::Session::set() (snmp_errno)
$info->set_location("Here!");
set_METHOD($value,$iid)Returns undef if failed, or the return value from SNMP::Session::set() (snmp_errno)
# Disable a port administratively
my %if_map = reverse %{$info->interfaces()}
$info->set_i_up_admin('down', $if_map{'FastEthernet0/0'})
or die "Couldn't disable the port. ",$info->error(1);
NOTE: You must be connected to your device with a ReadWrite community string in order
for set operations to work.
NOTE: This will only set data listed in %FUNCS and %GLOBALS. For data acquired from
overriden methods (subroutines) specific set_METHOD() subroutines will need to be
added if they haven't been already.
SNMP::Info will not chirp anything to STDOUT unless there is a serious error (in which case it will probably die).
To get lots of debug info, set the Debug flag when calling new() or call $info->debug(1);
When calling a method check the return value. If the return value is undef then check $info->error()
Beware, calling $info->error() clears the error.
my $name = $info->name() or die "Couldn't get sysName!" . $name->error();
A class inheriting this class must implement these data structures :
When choosing the name for the methods, be aware that other new Sub Modules might inherit this one to get it's features. Try to choose a prefix for methods that will give it's own name space inside the SNMP::Info methods.
('MIB-NAME' => 'itemToTestForPresence')
The value for each entry should be a MIB object to check for to make sure that the MIB is present and has loaded correctly.
$info->init() will throw an exception if a MIB does not load.
Sample %MUNGE:
(my_ip => \&munge_ip, my_mac => \&munge_mac, my_layers => \&munge_dec2bin )
Let's make a sample Layer 2 Device subclass. This class will inherit the Cisco Vlan module as an example.
----------------------- snip --------------------------------
# SNMP::Info::Layer2::Sample
package SNMP::Info::Layer2::Sample;
$VERSION = 0.1;
use strict;
use Exporter; use SNMP::Info::Layer2; use SNMP::Info::CiscoVTP;
@SNMP::Info::Layer2::Sample::ISA = qw/SNMP::Info::Layer2
SNMP::Info::CiscoVTP Exporter/;
@SNMP::Info::Layer2::Sample::EXPORT_OK = qw//;
use vars qw/$VERSION %FUNCS %GLOBALS %MIBS %MUNGE $AUTOLOAD $INIT $DEBUG/;
%MIBS = (%SNMP::Info::Layer2::MIBS,
%SNMP::Info::CiscoVTP::MIBS,
'SUPER-DOOPER-MIB' => 'supermibobject'
);
%GLOBALS = (%SNMP::Info::Layer2::GLOBALS,
%SNMP::Info::CiscoVTP::GLOBALS,
'name' => 'supermib_supername',
'favorite_color' => 'supermib_fav_color_object',
'favorite_movie' => 'supermib_fav_movie_val'
);
%FUNCS = (%SNMP::Info::Layer2::FUNCS,
%SNMP::Info::CiscoVTP::FUNCS,
# Super Dooper MIB - Super Hero Table
'super_hero_index' => 'SuperHeroIfIndex',
'super_hero_name' => 'SuperHeroIfName',
'super_hero_powers' => 'SuperHeroIfPowers'
);
%MUNGE = (%SNMP::Info::Layer2::MUNGE,
%SNMP::Info::CiscoVTP::MUNGE,
'super_hero_powers' => \&munge_powers
);
# OverRide uptime() method from %SNMP::Info::GLOBALS
sub uptime {
my $sample = shift;
my $name = $sample->name();
# this is silly but you get the idea
return '600' if defined $name ;
}
# Create our own munge function
sub munge_powers {
my $power = shift;
# Take the returned obscure value and return something useful.
return 'Fire' if $power =~ /reallyhot/i;
return 'Ice' if $power =~ /reallycold/i;
# Else
return $power;
}
# Copious Documentation here!!! =head1 NAME =head1 AUTHOR =head1 SYNOPSIS =head1 DESCRIPTION =head2 Inherited Classes =head2 Required MIBs =head1 GLOBALS =head2 Overrides =head1 TABLE METHODS =head2 Overrides =cut
1; # don't forget this line ----------------------- snip --------------------------------
Be sure and send the debugged version to snmp-info-users@lists.sourceforge.net to be included in the next version of SNMP::Info.
Internal data is stored with bareword keys. For example $info->{debug}
SNMP Data is stored or marked cached with keys starting with an underscore. For example $info->{_name} is the cache for $info->name().
Cached Table data is stored in $info->store() and marked cached per above.
These set the default value for an object upon creation.
new() unless 'Debug' argument passed in new(). Change objects' debug status with
$info->debug().
new()
to do it on an object scope.
perldoc SNMP for more info. Can change
by passing BulkRepeaters option in new()
munge_speed()
%SPEED_MAP = (
'56000' => '56 kbps',
'64000' => '64 kbps',
'1500000' => '1.5 Mbps',
'1536000' => 'T1',
'1544000' => 'T1',
'2000000' => '2.0 Mbps',
'2048000' => '2.048 Mbps',
'3072000' => 'Dual T1',
'3088000' => 'Dual T1',
'4000000' => '4.0 Mbps',
'10000000' => '10 Mbps',
'11000000' => '11 Mbps',
'20000000' => '20 Mbps',
'16000000' => '16 Mbps',
'16777216' => '16 Mbps',
'44210000' => 'T3',
'44736000' => 'T3',
'45000000' => '45 Mbps',
'45045000' => 'DS3',
'46359642' => 'DS3',
'64000000' => '64 Mbps',
'100000000' => '100 Mbps',
'149760000' => 'ATM on OC-3',
'155000000' => 'OC-3',
'155519000' => 'OC-3',
'155520000' => 'OC-3',
'400000000' => '400 Mbps',
'599040000' => 'ATM on OC-12',
'622000000' => 'OC-12',
'622080000' => 'OC-12',
'1000000000' => '1.0 Gbps',
)
munge_ip()munge_mac()munge_octet2hex()munge_dec2bin()
init()args()class()error()
If $info->debug() is true, then the error message is carped too.
funcs()globals()mibs()munge()nosuch()new()
session()store(new_store)Store is a hash reference in this format :
$info->store = { attribute => { iid => value , iid2 => value2, ... } };
_global()Example: $info->name() calls autoload which calls $info->_global('name').
_set(attr,val,iid)Example: $info->set_name('dog',3) uses autoload to resolve to $info->_set('name','dog',3);
load_all()Runs $info->load_METHOD() for each entry in $info->funcs();
Note return value has changed since version 0.3
all()load_all() once then returns $info->store();
Use $info->load_all() to reload the data.
Note return value has changed since version 0.3
_load_attr()Called from $info->load_METHOD();
_show_attr()Called like $info->METHOD().
The first time ran, it will call $info->load_METHOD(). Every time after it will return cached data.
Each entry in either %FUNCS or %GLOBALS is used by AUTOLOAD() to create dynamic methods.
Note that this AUTOLOAD is going to be run for all the classes listed in the @ISA array in a subclass, so will be called with a variety of package names. We check the %FUNCS and %GLOBALS of the package that is doing the calling at this given instant.
_global(method) unless already cached._load_attr(method) if not cachedOverride any dynamic method listed in one of these hashes by creating a subroutine with the same name.
For example to override $info->name() create `` sub name {...}'' in your subclass.
Changes from SNMP::Info Version 0.7 and on are: Copyright (c)2003, 2004 Max Baker - All rights reserved.
Original Code is: Copyright (c) 2002-3, Regents of the University of California All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
* Redistributions of source code must retain the above copyright notice,
this list of conditions and the following disclaimer.
* Redistributions in binary form must reproduce the above copyright notice,
this list of conditions and the following disclaimer in the documentation
and/or other materials provided with the distribution.
* Neither the name of the University of California, Santa Cruz nor the
names of its contributors may be used to endorse or promote products
derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.