Forum Discussion

Fabio_124017's avatar
Fabio_124017
Icon for Nimbostratus rankNimbostratus
Jun 06, 2013

edit and load bigip_base.conf

hi everybody,

 

 

i just edit bigip_base.conf with vi editor to change a netmask of ip address local and self-ip.

 

before i backup the file copy in bigip_base.conf.old .

 

how can i re-load the configuration without reboot the Viprion?

 

my version is 11.1 and the command bigpipe load is not supported and with the command tmsh sys load i have problems..

 

 

can someone help me ?

 

 

fabio

 

dev
TMSH

2 Replies

  • Fabio_124017's avatar
    Fabio_124017
    Icon for Nimbostratus rankNimbostratus
    Jun 06, 2013

    sorry guys .. i have reload anyway the Viprion ( it's virtual ) but the configuration in the GUI it's not changed....

     

    the netmask it's old value .. but in command line the bigip_base.conf has the new value... i don't understand ... :(

     

     

    so the question is how can i change the netmask in command line.. ? and loading to take new effects ?

     

    my real problem it's in two Viprion ( active/passive) in production, which i have need to change the netmask not only to local ip but also in the other self ip traffic-groups ...

     

     

    help me

     

    This Viprion is "BIG-IP 11.1.0 Build 2027.0 Hotfix HF2 "

     

     

     

     

  • StephanManthey's avatar
    StephanManthey
    Icon for Nacreous rankNacreous
    Sep 10, 2013

    I´m a bit late to the party, sorry.

    As far as I understand, your approach to modify these parameters directly in the configuration file is not supported by F5.

    The command 
    tmsh load sys config
    should load the configuration files indeed.

    But as there is a potential conflicting information with the current configuration, it will not be applied. Instead you run the risk of an inconsistent configuration (text configuration files and binary configuration files).

    Details on the subject can be found on AskF5 SOL13030. Reboot required ...

    Please keep in mind, that a change on self IPs may break your device group setup. Putting one unit in 'forced offline' mode will prevent a potential active / active state.