Forum Discussion
UDP Virtual server (port 162) not working
- Mar 08, 2017
To finish this topic, there was nothing wrong with the VS definition nor in the software release. The problem was in a wrong pool member health monitor configuration, that was causing the VS to become not available.
Thanks to all replies.
PS - lesson learned: an udp health monitor was not enough to monitor the pool for this specific case, as this monitor is always "green" even if port 162 is not listening in the pool member. This was corrected by adding a second monitor and hence, truly determining the status of the pool member.
Hi Kees, thanks for replying. Yes, here it goes:
ltm virtual OAM_INT_CN_MON_ALARM_INT_VS_162 {
destination 192.168.30.242:snmptrap
ip-protocol udp
mask 255.255.255.255
pool OAM_INT_CN_MON_ALARM_INT_Pool
profiles {
udp { }
}
source 0.0.0.0/0
source-address-translation {
type automap
}
vlans {
VLAN_333_OAM_INT
}
vlans-enabled
vs-index 203
}
Also some info on the SW version:
Main Package
Product BIG-IP
Version 11.4.1
Build 711.0
Edition Hotfix HF11
Date Tue Aug 30 12:18:51 PDT 2016
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com