Deploying BIG-IP Telemetry Streaming with Azure Sentinel as its consumer.
Published Oct 26, 2020
Version 1.0Was this article helpful?
antonym I figured this out, somehow. I needed to add a static route to the route table for the 255.255.255.254/32 address pointing to one of my existing VLANs. This is my config for the route table, which allows the TCP monitor to work correctly:
net route InternalTraffic {
gw 10.133.7.17
network 10.0.0.0/8
}
net route external_default_gateway {
gw 10.133.5.1
network default
}
net route telemetry {
description "Allows monitor to work"
interface /Common/internal
network 255.255.255.254/32
}