Forum Discussion

Prakash_Krishna's avatar
Prakash_Krishna
Icon for Nimbostratus rankNimbostratus
Apr 15, 2016

Destination mask for Virtual Server accepts only "255.255.255.255"

Dear Experts,

 

While creating Virtual Server, without giving the Destination Address mask, internally the value for mask has been considered as 255.255.255.255. Even if we don't give the same value(255.255.255.255) in UI, its throwing the error. Say for example, if I give the Destination Address as "192.168.0.1' and the right mask value as "255.255.255.0", F5 GUI is throwing the error as "Invalid IP or Hostname". Is there any logic behind this or known issue with F5. Can you please help me in understanding this.

 

Regards, Prakash.K

 

cloud
iControl

3 Replies

Sort By
  • Prakash_Krishna's avatar
    Prakash_Krishna
    Icon for Nimbostratus rankNimbostratus
    Apr 15, 2016

     

    Thanks for your quick response. In LTM 12.0 version, we do not have the host/network option. whereas if I give the value as 192.168.0.1/255.255.255.255, it goes well and Virtual server is getting created. Even if we don't give the mask value, giving only the IP Address alone also getting created but in the back end value 255.255.255.255 is getting added to the subnet mask. Validated the same using iControl APIs also Without this value, not able to create the Virtual server using iControl (SOAP) API as well.

     

    • Domai's avatar
      Domai
      Icon for Altostratus rankAltostratus
      Apr 15, 2016
      Ahh this is 12 version. I see That is correct when using tmsh I usually give the mask like this - "create virtual test_vs destination 192.168.0.1:80 mask 255.255.255.255"
  • Andy_McGrath's avatar
    Andy_McGrath
    Icon for Cumulonimbus rankCumulonimbus
    Apr 15, 2016

    192.168.0.1 is a host addresses, if you want to configure a Virtual Server to listen on a subnet you need to use the Network Address.

    So try:

    Destination Address - 192.168.0.0
Destination Subnet - 255.255.255.0