Forum Discussion
jake_52679
Nimbostratus
Nimbostratusicmp to the management port
Hi fairly new to BIG IP and I have this minor issue.
BIG-IP 9.4.6
We require monitoring of our management port via snmp (works great) and icmp (only works when the icmp source is located in the same subnet as the management port).
I can't understand why this would be the case, and can't find anywhere to change this in the GUI.
Help please
3 Replies
- JRahm
Admin
most likely this is due to the lack of a management route to your source system. Mgmt routes are handled only at the command line, which can be accessed from the GUI by going to System->Console, then entering the appropriate mgmt route (bigpipe is already supplied for you in the GUI console, at the command line you will need to add it)
mgmt route / gateway
HTH...Jason 
jake_52679Hi thanks,
Originally we had this:
[root@DC2-F5-01:Active] config bigpipe mgmt route
MGMT ROUTE default inet
| GATEWAY 10.131.7.254 MTU 0
So I added a route for the local subnet:
[root@DC2-F5-01:Active] config bigpipe mgmt route
MGMT ROUTE 10.131.7.0/24
| GATEWAY 10.131.7.254 MTU 0
MGMT ROUTE default inet
| GATEWAY 10.131.7.254 MTU 0
[root@DC2-F5-01:Active] config
Now I am very confused as I still cannot ping the management port from anywhere but the local subnet though??- jake_52679
So I added a route to the ICMP source subnet:
[root@DC2-F5-01:Active] config bigpipe mgmt route
MGMT ROUTE 10.135.7.0/24
| GATEWAY 10.131.7.254 MTU 0
MGMT ROUTE default inet
| GATEWAY 10.131.7.254 MTU 0
[root@DC2-F5-01:Active] config
and that worked!
