SNMP trap config

This support forum board is for support questions relating to Nagios XI, our flagship commercial network monitoring solution.
SteveBeauchemin
Posts: 524
Joined: Mon Oct 14, 2013 7:19 pm

Re: SNMP trap config

Post by SteveBeauchemin »

Look here...

https://github.com/taishin/vendor_mibs/ ... pqhost.mib

MIB files keep growing... adding new OIDS. My own MIB stops at 11019. This must be a bit newer.

Code: Select all

 cpqHoMibHealthStatusArrayChangeTrap TRAP-TYPE 
        ENTERPRISE compaq
        VARIABLES { sysName, cpqHoTrapFlags, cpqHoMibHealthStatusArray }
        DESCRIPTION
        "A change in the cpqHoMibHealthStatusArray has occurred."
              --#TYPE "Health Status Array Change occurred (11020)"
              --#SUMMARY "A change in the health status of the server has occurred, the status is now %s"
              --#ARGUMENTS {2}
              --#SEVERITY INFORMATIONAL
              --#TIMEINDEX 99
              --#SIMPLE_SEVERITY OK
              --#HWSTATUS_CATEGORY NONE
              
        ::= 11020
Just FYI.

Steve B
XI 5.7.3 / Core 4.4.6 / NagVis 1.9.8 / LiveStatus 1.5.0p11 / RRDCached 1.7.0 / Redis 3.2.8 /
SNMPTT / Gearman 0.33-7 / Mod_Gearman 3.0.7 / NLS 2.0.8 / NNA 2.3.1 /
NSClient 0.5.0 / NRPE Solaris 3.2.1 Linux 3.2.1 HPUX 3.2.1
gormank
Posts: 1114
Joined: Tue Dec 02, 2014 12:00 pm

Re: SNMP trap config

Post by gormank »

I attached cpqhost.mib.txt. .mib isn't an allowed extension.

# grep 11020 /usr/share/snmp/mibs/cpqhost.mib
--#TYPE "Health Status Array Change occurred (11020)"
::= 11020
You do not have the required permissions to view the files attached to this post.
gormank
Posts: 1114
Joined: Tue Dec 02, 2014 12:00 pm

Re: SNMP trap config

Post by gormank »

gormank wrote:I attached cpqhost.mib.txt. .mib isn't an allowed extension.

# grep 11020 /usr/share/snmp/mibs/cpqhost.mib
--#TYPE "Health Status Array Change occurred (11020)"
::= 11020
I guess one of the things confusing me is I thought I should be able to snmpwalk or snmpget using that OID for example, and get the same output from the same server. Something odd is that when I give the numerical OID, it comes back with the SNMPv2-SMI MIB.

# snmpget -v2c -c sp1der txslm2mlapp006.ilo cpqHoMibHealthStatusArrayChangeTrap
No log handling enabled - turning on stderr logging
cpqHoMibHealthStatusArrayChangeTrap: Unknown Object Identifier (Sub-id not found: (top) -> cpqHoMibHealthStatusArrayChangeTrap)

# snmpget -v2c -c sp1der txslm2mlapp006.ilo 1.3.6.1.4.1.232.0.11020
SNMPv2-SMI::enterprises.232.0.11020 = No Such Object available on this agent at this OID
User avatar
tgriep
Madmin
Posts: 9190
Joined: Thu Oct 30, 2014 9:02 am

Re: SNMP trap config

Post by tgriep »

Couple of things could cause it, either the device doesn't allow polling of that OID or the MIB file is corrupted.
Can you do a snmpwalk on it and post the /tmp/walk.txt file?

Code: Select all

snmpwalk -v2c -c sp1der txslm2mlapp006.ilo >/tmp/walk.txt
Also, run the following and post the output.

Code: Select all

ls -l /usr/share/snmp/mibs/
Thanks.
Be sure to check out our Knowledgebase for helpful articles and solutions!
SteveBeauchemin
Posts: 524
Joined: Mon Oct 14, 2013 7:19 pm

Re: SNMP trap config

Post by SteveBeauchemin »

Please

You cannot SNMP Get a Trap

Steve B
XI 5.7.3 / Core 4.4.6 / NagVis 1.9.8 / LiveStatus 1.5.0p11 / RRDCached 1.7.0 / Redis 3.2.8 /
SNMPTT / Gearman 0.33-7 / Mod_Gearman 3.0.7 / NLS 2.0.8 / NNA 2.3.1 /
NSClient 0.5.0 / NRPE Solaris 3.2.1 Linux 3.2.1 HPUX 3.2.1
gormank
Posts: 1114
Joined: Tue Dec 02, 2014 12:00 pm

Re: SNMP trap config

Post by gormank »

Actually, that's a good point about not being able to snmpget a trap. But the underlying issue remains, and that is how can I get the info that's in the trap? As we can see from snmpwalk below, hardware status isn't in those 6 lines.

Simply sitting around and waiting for traps in Nagios has a few problems, not the least of which is a new trap replaces the last trap. So if a normal trap arrives after a critical, Nagios turns the service green. I'll recieve 10k login success/failures today so any hardware problems will be masked by these traps.

Then there's proving to my management that for condition X, I get a traps saying so. HP and countless web searches haven't has been able to come up with good info on what data is in a trap, or how to get the info.

# snmpget -v2c -c sp1der txslm2mlapp006.ilo SNMPv2-MIB::sysDescr.0
SNMPv2-MIB::sysDescr.0 = STRING: Integrated Lights-Out 4 2.00 Jul 30 2014

# snmpwalk -v2c -c sp1der txslm2mlapp006.ilo
SNMPv2-MIB::sysDescr.0 = STRING: Integrated Lights-Out 4 2.00 Jul 30 2014
SNMPv2-MIB::sysObjectID.0 = OID: SNMPv2-SMI::enterprises.232.9.4.10
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (3901337205) 451 days, 13:02:52.05
SNMPv2-MIB::sysContact.0 = STRING:
SNMPv2-MIB::sysName.0 = STRING: ILOUSE407RSB9.
SNMPv2-MIB::sysLocation.0 = STRING: unknown

# ls -l /usr/share/snmp/mibs/
total 4908
-rw-r--r-- 1 root nagios 17455 Oct 8 20:49 AGENTX-MIB.txt
-rw-r--r-- 1 root nagios 4030 Oct 8 20:49 bcCustomOperation.mib
-rw-r--r-- 1 root nagios 10323 Oct 8 20:49 bd.mib
-rw-r--r-- 1 root nagios 9405 Oct 8 20:49 brcdfcip.mib
-rw-r--r-- 1 root nagios 2890 Oct 8 20:49 BRCD_REG.mib
-rw-r--r-- 1 root nagios 2401 Oct 8 20:49 BRCD_TC.mib
-rw-r--r-- 1 root nagios 50948 Oct 8 20:49 BRIDGE-MIB.txt
-rw-r--r-- 1 root nagios 7876 Oct 8 20:49 BROCADE-MAPS-MIB.mib
-rw-r--r-- 1 root nagios 2887 Oct 8 20:49 brocade-reg-mib.mib
-rw-r--r-- 1 root nagios 2397 Oct 8 20:49 brocade-tc.mib
-rw-rw-r-- 1 root nagios 30908 Oct 8 20:49 CAAD.mib
-rw-r--r-- 1 root nagios 264569 Oct 8 20:49 cpqfca.mib
-rw-r--r-- 1 root nagios 3456 Oct 8 20:49 cpqgen.mib
-rw-r--r-- 1 root nagios 263828 Oct 8 20:49 cpqhlth.mib
-rw-r--r-- 1 root nagios 8969 Oct 8 20:49 cpqhostb.mib
-rw-r--r-- 1 root nagios 116140 Oct 8 20:49 cpqhost.mib
-rw-r--r-- 1 root nagios 456806 Oct 8 20:49 cpqida.mib
-rw-r--r-- 1 root nagios 75443 Oct 8 20:53 cpqide.mib
-rw-r--r-- 1 root nagios 103304 Oct 8 20:49 cpqnic.mib
-rw-r--r-- 1 root nagios 274866 Oct 8 20:49 cpqrack.mib
-rw-r--r-- 1 root nagios 263690 Oct 8 20:49 cpqscsi.mib
-rw-r--r-- 1 root nagios 163748 Oct 8 20:49 cpqsinfo.mib
-rw-r--r-- 1 root nagios 145092 Oct 8 20:49 cpqsm2.mib
-rw-r--r-- 1 root nagios 16721 Oct 8 20:49 cpqstat.mib
-rw-r--r-- 1 root nagios 218069 Oct 8 20:51 cpqstdeq.mib
-rw-r--r-- 1 root nagios 172969 Oct 8 20:49 cpqstsys.mib
-rw-r--r-- 1 root nagios 36833 Oct 8 20:49 cpqthrsh.mib
-rw-r--r-- 1 root nagios 68104 Oct 8 20:49 DISMAN-EVENT-MIB.txt
-rw-r--r-- 1 root nagios 24613 Oct 8 20:49 DISMAN-SCHEDULE-MIB.txt
-rw-r--r-- 1 root nagios 64311 Oct 8 20:49 DISMAN-SCRIPT-MIB.txt
-rw-r--r-- 1 root nagios 59229 Oct 8 20:49 ENTITY-MIB.txt
-rw-r--r-- 1 root nagios 84492 Oct 8 20:49 EtherLike-MIB.txt
-rw-r--r-- 1 root nagios 10932 Oct 8 20:49 faext.mib
-rw-r--r-- 1 root nagios 107945 Oct 8 20:49 FA.mib
-rw-r--r-- 1 root nagios 24171 Oct 8 20:49 FICON.mib
-rw-r--r-- 1 root nagios 14856 Oct 8 20:49 fod.mib
-rw-r--r-- 1 root nagios 12703 Oct 8 20:49 HA.mib
-rw-r--r-- 1 root nagios 4660 Oct 8 20:49 HCNUM-TC.txt
-rw-r--r-- 1 root nagios 52544 Oct 8 20:49 HOST-RESOURCES-MIB.txt
-rw-r--r-- 1 root nagios 10583 Oct 8 20:49 HOST-RESOURCES-TYPES.txt
-rw-r--r-- 1 root nagios 4819 Oct 8 20:49 IANA-ADDRESS-FAMILY-NUMBERS-MIB.txt
-rw-r--r-- 1 root nagios 29665 Oct 8 20:49 IANAifType-MIB.txt
-rw-r--r-- 1 root nagios 4299 Oct 8 20:49 IANA-LANGUAGE-MIB.txt
-rw-r--r-- 1 root nagios 3513 Oct 8 20:49 IANA-RTPROTO-MIB.txt
-rw-r--r-- 1 root nagios 57576 Oct 8 20:49 IbmBladeCenter.mib
-rw-r--r-- 1 root nagios 5066 Oct 8 20:49 IF-INVERTED-STACK-MIB.txt
-rw-r--r-- 1 root nagios 71691 Oct 8 20:49 IF-MIB.txt
-rw-r--r-- 1 root nagios 16782 Oct 8 20:49 INET-ADDRESS-MIB.txt
-rw-r--r-- 1 root nagios 46286 Oct 8 20:49 IP-FORWARD-MIB.txt
-rw-r--r-- 1 root nagios 185667 Oct 8 20:49 IP-MIB.txt
-rw-r--r-- 1 root nagios 15936 Oct 8 20:49 IPV6-ICMP-MIB.txt
-rw-r--r-- 1 root nagios 48703 Oct 8 20:49 IPV6-MIB.txt
-rw-r--r-- 1 root nagios 7257 Oct 8 20:49 IPV6-TCP-MIB.txt
-rw-r--r-- 1 root nagios 2367 Oct 8 20:49 IPV6-TC.txt
-rw-r--r-- 1 root nagios 4400 Oct 8 20:49 IPV6-UDP-MIB.txt
-rw-r--r-- 1 root nagios 5931 Oct 8 20:49 LM-SENSORS-MIB.txt
-rw-r--r-- 1 root nagios 42375 Oct 8 20:49 MTA-MIB.txt
-rwxr-xr-x 1 root nagios 19141 Oct 8 20:49 NAGIOS-NOTIFY-MIB.txt
-rwxr-xr-x 1 root nagios 2006 Oct 8 20:49 NAGIOS-ROOT-MIB.txt
-rw-r--r-- 1 root nagios 15732 Oct 8 20:49 NET-SNMP-AGENT-MIB.txt
-rw-r--r-- 1 root nagios 9160 Oct 8 20:49 NET-SNMP-EXAMPLES-MIB.txt
-rw-r--r-- 1 root nagios 9198 Oct 8 20:49 NET-SNMP-EXTEND-MIB.txt
-rw-r--r-- 1 root nagios 2036 Oct 8 20:49 NET-SNMP-MIB.txt
-rw-r--r-- 1 root nagios 3351 Oct 8 20:49 NET-SNMP-PASS-MIB.txt
-rw-r--r-- 1 root nagios 4686 Oct 8 20:49 NET-SNMP-TC.txt
-rw-r--r-- 1 root nagios 5039 Oct 8 20:49 NET-SNMP-VACM-MIB.txt
-rw-r--r-- 1 root nagios 21006 Oct 8 20:49 NETWORK-SERVICES-MIB.txt
-rw-r--r-- 1 root nagios 24694 Oct 8 20:49 NOTIFICATION-LOG-MIB.txt
-rw-r--r-- 1 root nagios 3067 Oct 8 20:49 RFC1155-SMI.txt
-rw-r--r-- 1 root nagios 79667 Oct 8 20:49 RFC1213-MIB.txt
-rw-r--r-- 1 root nagios 1174 Oct 8 20:49 RFC-1215.txt
-rw-r--r-- 1 root nagios 147822 Oct 8 20:49 RMON-MIB.txt
-rw-r--r-- 1 root nagios 45323 Oct 8 20:49 SCTP-MIB.txt
-rw-r--r-- 1 root nagios 4595 Oct 8 20:49 SMUX-MIB.txt
-rw-r--r-- 1 root nagios 15490 Oct 8 20:49 SNMP-COMMUNITY-MIB.txt
-rw-r--r-- 1 root nagios 22342 Oct 8 20:49 SNMP-FRAMEWORK-MIB.txt
-rw-r--r-- 1 root nagios 5496 Oct 8 20:49 SNMP-MPD-MIB.txt
-rw-r--r-- 1 root nagios 20014 Oct 8 20:49 SNMP-NOTIFICATION-MIB.txt
-rw-r--r-- 1 root nagios 9106 Oct 8 20:49 SNMP-PROXY-MIB.txt
-rw-r--r-- 1 root nagios 22769 Oct 8 20:49 SNMP-TARGET-MIB.txt
-rw-r--r-- 1 root nagios 39201 Oct 8 20:49 SNMP-USER-BASED-SM-MIB.txt
-rw-r--r-- 1 root nagios 2205 Oct 8 20:49 SNMP-USM-AES-MIB.txt
-rw-r--r-- 1 root nagios 21101 Oct 8 20:49 SNMP-USM-DH-OBJECTS-MIB.txt
-rw-r--r-- 1 root nagios 8263 Oct 8 20:49 SNMPv2-CONF.txt
-rw-r--r-- 1 root nagios 29305 Oct 8 20:49 SNMPv2-MIB.txt
-rw-r--r-- 1 root nagios 8924 Oct 8 20:49 SNMPv2-SMI.txt
-rw-r--r-- 1 root nagios 38034 Oct 8 20:49 SNMPv2-TC.txt
-rw-r--r-- 1 root nagios 5775 Oct 8 20:49 SNMPv2-TM.txt
-rw-r--r-- 1 root nagios 34162 Oct 8 20:49 SNMP-VIEW-BASED-ACM-MIB.txt
-rw-rw-r-- 1 root nagios 5788 Oct 8 20:49 SOL19881_SOL19881_intrust_mib.txt
-rw-r--r-- 1 root nagios 148752 Oct 8 20:49 SW.mib
-rw-r--r-- 1 root nagios 28564 Oct 8 20:49 TCP-MIB.txt
-rw-r--r-- 1 root nagios 10472 Oct 8 20:49 ThreeParMIB.txt
-rw-r--r-- 1 root nagios 16418 Oct 8 20:49 TRANSPORT-ADDRESS-MIB.txt
-rw-r--r-- 1 root nagios 2163 Oct 8 20:49 UCD-DEMO-MIB.txt
-rw-r--r-- 1 root nagios 4402 Oct 8 20:49 UCD-DISKIO-MIB.txt
-rw-r--r-- 1 root nagios 3010 Oct 8 20:49 UCD-DLMOD-MIB.txt
-rw-r--r-- 1 root nagios 8118 Oct 8 20:49 UCD-IPFWACC-MIB.txt
-rw-r--r-- 1 root nagios 46150 Oct 8 20:49 UCD-SNMP-MIB.txt
-rw-r--r-- 1 root nagios 265 Oct 8 20:49 UCD-TRAP-TEST-MIB.txt
-rw-r--r-- 1 root nagios 20882 Oct 8 20:49 UDP-MIB.txt
ssax
Dreams In Code
Posts: 7682
Joined: Wed Feb 11, 2015 12:54 pm

Re: SNMP trap config

Post by ssax »

Unfortunately, the only way that you can see if they may have that data available via SNMP get is by doing a walk of the device and looking through the values. (This can be very tedious but should be doable as long as the OIDs are viewable)

If you are only seeing these values from the walk:

Code: Select all

SNMPv2-MIB::sysDescr.0 = STRING: Integrated Lights-Out 4 2.00 Jul 30 2014
SNMPv2-MIB::sysObjectID.0 = OID: SNMPv2-SMI::enterprises.232.9.4.10
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (3901337205) 451 days, 13:02:52.05
SNMPv2-MIB::sysContact.0 = STRING:
SNMPv2-MIB::sysName.0 = STRING: ILOUSE407RSB9.
SNMPv2-MIB::sysLocation.0 = STRING: unknown
Then the SNMP daemon on the HP/Compaq system is not setup to allow other OIDs to be viewed, there might be an option in the configuration for that but that's not something we would know.

Your best option is to contact their support and figure out what OIDs/MIBs you need and then we can help you get it configured from there.

Thank you
SteveBeauchemin
Posts: 524
Joined: Mon Oct 14, 2013 7:19 pm

Re: SNMP trap config

Post by SteveBeauchemin »

If I were working on getting the SNMP data, these are the initial steps I would take.

First I would get 2 snmp walks of the pertinent data. One with only OIDS, and one with full text.
Then you can compare them side by side, and get to the data that is what I call "interesting".
To do that, I walk the data 2 ways. Like this:

For numeric only (specific to your CPQHOST-MIB)...
snmpwalk -t 3 -v 2c -Cc -On -c [community] [device] .1.3.6.1.4.1.232 > /tmp/numeric.txt

For full text...
snmpwalk -t 3 -v 2c -Cc -m ALL -c [community] [device] .1.3.6.1.4.1.232 > /tmp/full.txt

(FYI - Some systems do not give up their OIDS to snmpwalk unless you specifically ask for them.
Some you can leave blank, others may need .1 and for other OIDS you may need to be more specific.
For example, at the vendor number you may get nothing .1.3.6.1.4.1.2620
But at a more specific point you may get the rest of the data you need .1.3.6.1.4.1.2620.1.1)

Once you have all the data, then I would look through the full text screen and try to find those interesting things.
If you see OIDS there, then you need to get the MIB files that are missing. Full text means full text.

Look for items that have metrics or information that can be used
over time to track status, make graphs, or use as thresholds.

Then I would open the other file and look at them side by side using vi, and line them up.
From that you can get the actual OIDS that you want to monitor and set up some check_snmp tests.

<OPINION and useless trivia>
Remember, SNMP Get is a different tool from SNMP Trap.
Different protocol, Different port, Different direction.
One is volunteered to you. One you go get.

By the time a system sends a trap, it is already too late.
Trap means something has already gone bad.
That something is wrong right now. (Use NSTI maybe?)

Using SNMP Get may let you see ahead of time what is leading up to a failure.
So set some threshold alerts, deal with a problem before it becomes an outage.
Trap is a last resort. Trap means the problem is here now. Too late. Sorry buddy.
But trap is better than nothing.
</OPINION and useless trivia>

Steve B
XI 5.7.3 / Core 4.4.6 / NagVis 1.9.8 / LiveStatus 1.5.0p11 / RRDCached 1.7.0 / Redis 3.2.8 /
SNMPTT / Gearman 0.33-7 / Mod_Gearman 3.0.7 / NLS 2.0.8 / NNA 2.3.1 /
NSClient 0.5.0 / NRPE Solaris 3.2.1 Linux 3.2.1 HPUX 3.2.1
gormank
Posts: 1114
Joined: Tue Dec 02, 2014 12:00 pm

Re: SNMP trap config

Post by gormank »

Ok, that had info No one else has been able to provide... The key is the host not volunteering its proprietary OIDs, and the example walks are great too.
I'm aware that we wait passively for traps and go hunt with get, but good points.

I see now that for example

Code: Select all

  cpqHoMibHealthStatusArrayChangeTrap TRAP-TYPE
        ENTERPRISE compaq
        VARIABLES { sysName, cpqHoTrapFlags, cpqHoMibHealthStatusArray }
        DESCRIPTION
        "A change in the cpqHoMibHealthStatusArray has occurred."
              --#TYPE "Health Status Array Change occurred (11020)"
              --#SUMMARY "A change in the health status of the server has occurred, the status is now %s"
              --#ARGUMENTS {2}
              --#SEVERITY INFORMATIONAL
              --#TIMEINDEX 99
              --#SIMPLE_SEVERITY OK
              --#HWSTATUS_CATEGORY MANAGEMENTPROCESSOR

        ::= 11020
is explained by

Code: Select all

cpqHoMibHealthStatusArray OBJECT-TYPE
	SYNTAX OCTET STRING (SIZE(1..256))
	ACCESS read-only
	STATUS mandatory
	DESCRIPTION "The MIB Health Status Array is an array of status values representing an
overall status in element 0 follwed by server and storage status values as follows:

Octet   Element   Field
======== ======= =========
0        0    Aggregated Status of array elements
1        1    Status of element 1
2        2    Status of element 2
.
.
.
n        n    Status of element n

Status         0 - Not available
1 - Other
2 - OK
3 - Degraded
4 - Failed
.
.
Mibs are assigned an array element as follows.  New items are added at the end.
0 -  System Health Status (overall status as reported by who is reporting (agents or iLO))
1 -  Total Aggregate (Includes IML Status)
2 -  Processors    (TBD 232.1.2.2.4:cpqSeCpuCondition)
3 -  Memory        (232.6.2.14.4:cpqHeResilientMemCondition)
4 -  Cooling       (232.6.2.6.4:cpqHeThermalSystemFanStatus)
5 -  Sensors       (232.6.2.6.3:cpqHeThermalTempStatus)
6 -  Power         (232.6.2.9.1:cpqHeFltTolPwrSupplyCondition)
7 -  ProLiant Logs (232.6.2.11.2:cpqHeEventLogCondition)
8 -  ASR           (232.6.2.5.17:cpqHeAsrCondition)
9 -  Drive Array   (232.3.1.3:cpqDaMibCondition)
10 - SCSI          (232.5.1.3:cpqScsiMibCondition)
11 - Storage Enclosures (232.8.1.3:cpqSsMibCondition)
12 - IDE           (232.14.1.3:cpqIdeMibCondition)
13 - FC            (232.16.1.3:cpqFcaMibCondition)
14 - Networks      (232.18.1.3:cpqNicMibCondition)
15 - MP            (232.9.1.3:cpqSm2MibCondition)
16 - HW/BIOS       (232.6.2.16.1:cpqHeHWBiosCondition)
17 - Battery       (232.6.2.17.1:cpqHeSysBackupBatteryCondition)"
	::= { cpqHoSystemStatus 7 }
So now I can ask about my CPUs for example:

# snmpwalk -t 3 -v 2c -Cc -m ALL -c sp1der cocsm2mlapp006.ilo 1.3.6.1.4.1.232.1.2.2.4
CPQSTDEQ-MIB::cpqSeCpuCondition.0 = INTEGER: ok(2)

# snmpwalk -t 3 -v 2c -Cc -m ALL -c sp1der cocsm2mlapp006.ilo CPQSTDEQ-MIB::cpqSeCpuCondition.0
CPQSTDEQ-MIB::cpqSeCpuCondition.0 = INTEGER: ok(2)


This is great.
Thanks!
User avatar
Box293
Too Basu
Posts: 5126
Joined: Sun Feb 07, 2010 10:55 pm
Location: Deniliquin, Australia
Contact:

Re: SNMP trap config

Post by Box293 »

Thanks for helping @SteveBeauchemin. SNMP is a complicated subject and sometimes it' easy to forget to explain some of the basics.

@gormank do you have any more questions on this topic?
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
Locked