Forum Discussion

Jim_Schwartzmei's avatar
Jim_Schwartzmei
Icon for Nimbostratus rankNimbostratus
Dec 21, 2017

Trouble with tmsh command using incorrect route domain

I am trying to automate an SSL CRL update. I have the correct command tmsh modify /sys file ssl-crl testca.crl source-path https://10.11.248.22/web/cert/testca.pem, which is working in a sandbox environment with a single route-domain.

 

I cannot get this to function in production where there are multiple route-domains. 10.11.248.0/24 is directly connected to the F5 in RD2. I have verified that I am able to curl the path.

 

rdexec 2 curl -k https://10.11.248.22/web/cert/testca.pem goes out the correct interface and returns the pem file.

 

However, modify /sys file ssl-crl testca.crl source-path https://10.11.248.22/web/cert/testca.pem, that uses RD 0 interface and this is NOT routeable to the 10.11.248.0/24 network.

 

I have attempted rdexec 2 tmsh modify /sys file ssl-crl testca.crl source-path https://10.11.248.22/web/cert/testca.pem But that also attempts to connect through the RD 0 interface.

 

I am stumped on this one. How can I tell the tmsh command modify /sys file ssl-crl to use RD 2?

 

application delivery
LTM
TMSH

1 Reply

Sort By
  • nitass's avatar
    nitass
    Icon for Employee rankEmployee
    Dec 21, 2017

    this is not supported currently. it is tracked as ID692064 TMSH: FileObjectCmd does not support route domain.

    can you try this as a workaround?

    net route custom {
    gw %2
    network 10.11.248.0%0/24
}