For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

kev_245_28249's avatar
kev_245_28249
Icon for Nimbostratus rankNimbostratus
Jun 08, 2011

convert OID to mcpd process id - per sol11127

Hi, I would like to make use of the 'logger -p' command to generate syslog messages in order to test syslog and snmp traps. I can get this working but find it difficult to know which of the following ...
config
design
nitass's avatar
nitass
Icon for Employee rankEmployee
Jun 08, 2011
not sure i understand your question correctly.

 

 

usually i search log from /var/run/bigip_error_maps.dat first.

 

grep -i "monitor status" /var/run/bigip_error_maps.dat

 

0 LOG_NOTICE 01070638 BIGIP_MCPD_MCPDERR_POOL_MEMBER_MON_STATUS "Pool member %s:%u monitor status %s."

 

0 LOG_NOTICE 01070640 BIGIP_MCPD_MCPDERR_NODE_ADDRESS_MON_STATUS "Node %s monitor status %s."

 

0 LOG_NOTICE 01070727 BIGIP_MCPD_MCPDERR_POOL_MEMBER_MON_STATUS_UP "Pool member %s:%u monitor status up."

 

0 LOG_NOTICE 01070728 BIGIP_MCPD_MCPDERR_NODE_ADDRESS_MON_STATUS_UP "Node %s monitor status up."

 

 

then i use alert name to find oid in /etc/alertd/alert.conf.

 

grep -A3 BIGIP_MCPD_MCPDERR_POOL_MEMBER_MON_STATUS /etc/alertd/alert.conf

 

alert BIGIP_MCPD_MCPDERR_POOL_MEMBER_MON_STATUS {

 

snmptrap OID=".1.3.6.1.4.1.3375.2.4.0.10"

 

}

 

alert BIGIP_MCPD_MCPDERR_POOL_MEMBER_MON_STATUS_UP {

 

snmptrap OID=".1.3.6.1.4.1.3375.2.4.0.11"

 

}

 

 

btw, u know bigip doesn't send trap for every log message. if i don't see it in alert.conf (and i need it), i will define it in user_alert.conf.