The following monitoring tools were used to give information on the VO status but they can't be assumed 100% reliable now. In any case problems should be reproduced manually before a GGUS ticket is submitted.
Note: ARGO probes are launched using a robot certificate with DN /DC=EU/DC=EGI/C=HR/O=Robots/O=SRCE/CN=Robot:argo-egi@cro-ngi.hr that requires to be a Biomed member. We need to check regularly that membership has not expired, and in case it has, sign Biomed AUP in the name of the user (this is possible as VOMS admin) on https://cclcgvomsli01.in2p3.fr:8443/voms/biomed/ (last renewed early March 2020)
This list is consolidated from 2 sources:
lcg-infosites
tool that is used to query the BDII has version > 2.6.9, that comes with gLite 3.2. rpm -qa | grep infosites
For Biomed it is advised to refer to the top BDII in IN2P3
export LCG_GFAL_INFOSYS=cclcgtopbdii02.in2p3.fr:2170
The script below may help you detect inconsistencies between top BDIIs:
#!/bin/bash # This script compares the list of BIOMED SEs returned by 2 top BDIIs: CERN and IN2P3 lcg-infosites --vo biomed --is cclcgtopbdii02.in2p3.fr se | cut -f2 | sort > /tmp/list_se_bdi_in2p3 lcg-infosites --vo biomed --is lcg-bdii.cern.ch se | cut -f2 | sort > /tmp/list_se_bdi_cern diff /tmp/list_se_bdi_in2p3 /tmp/list_se_bdi_cern</tt>