create a node => a pool => an HTTP monitor => Attach the monitor to a pool => Create a virtual server

 On F5 BIG-IP, you can manage most LTM resources in two main ways:

• Configuration utility — the web-based GUI, useful for interactive administration.

• TMSH (TMOS Shell) — the command-line interface, useful for repeatable administration, scripting, and automation.

Common BIG-IP resource management

Resource	Configuration utility	TMSH examples
Virtual server	Local Traffic → Virtual Servers → Virtual Server List	tmsh list ltm virtual
Pool	Local Traffic → Pools → Pool List	tmsh list ltm pool
Pool member	Local Traffic → Pools → Pool List → Members	tmsh list ltm pool <pool-name> members
Node	Local Traffic → Nodes → Node List	tmsh list ltm node
Profiles	Local Traffic → Profiles	tmsh list ltm profile
Monitors	Local Traffic → Monitors	tmsh list ltm monitor

Example: create a node

tmsh create ltm node web01 address 10.10.10.11

Create a pool

tmsh create ltm pool web_pool \
    members add { web01:80 }

Or create the node and pool member separately:

tmsh create ltm node web02 address 10.10.10.12
tmsh modify ltm pool web_pool members add { web02:80 }

Create an HTTP monitor

tmsh create ltm monitor http web_http_monitor \
    destination *:80 \
    send "GET / HTTP/1.1\r\nHost: example.com\r\nConnection: close\r\n\r\n" \
    recv "200 OK"

Attach the monitor to a pool

tmsh modify ltm pool web_pool monitor web_http_monitor

Create a virtual server

For example, a TCP/HTTP virtual server listening on 192.0.2.10:80:

tmsh create ltm virtual web_vs \
    destination 192.0.2.10:80 \
    ip-protocol tcp \
    pool web_pool \
    profiles add { tcp http }

Inspect configuration

tmsh list ltm virtual web_vs
tmsh list ltm pool web_pool
tmsh list ltm node web01
tmsh list ltm monitor http web_http_monitor

For a more compact view:

tmsh show ltm virtual web_vs
tmsh show ltm pool web_pool
tmsh show ltm node web01

Save the configuration

After making changes:

tmsh save sys config

You can also use:

tmsh save sys config partitions all

The exact available properties and syntax vary somewhat by BIG-IP/TMOS version and resource type.

Create a Load Balancing VIP on F5

On an F5 BIG-IP LTM, a VIP (Virtual IP) is typically created as a Virtual Server. 

It listens on a client-facing IP/port and sends traffic to a pool of backend servers.

Traffic flow

Client

HTTPS 10.10.10.100:443
            v
+------------------+
|   F5 BIG-IP LTM  |
|   Virtual Server   |
| 10.10.10.100:443 |
+------------------+

          |

          v

      web_pool

       /     \

      v       v

10.20.20.11  10.20.20.12

Example
Suppose you have:

VIP: 10.10.10.100
Port: 443
Protocol: HTTPS
Pool: web_pool
Backend servers:
10.20.20.11:443
10.20.20.12:443

Using the F5 GUI
Log in to the F5 BIG-IP management interface.
Go to Local Traffic → Virtual Servers → Virtual Server List.
Click Create.

Configure the main settings:
Name: vs_web_https
Destination Address/Mask: 10.10.10.100
Service Port: HTTPS (443)
Protocol: TCP

Under Configuration, select:

HTTP Profile: http if you want F5 to inspect/process HTTP

SSL Profile (Client): your client-side SSL certificate/profile if F5 terminates HTTPS

Source Address Translation: commonly Auto Map if the backend servers don't have a route back through the F5

Under Resources → Default Pool, select your backend pool.

Click Finished.

If you haven't created the pool yet
Go to:

Local Traffic → Pools → Pool List → Create

For example:
Pool Name: web_pool
Members:
10.20.20.11:443
10.20.20.12:443

You should also configure an appropriate health monitor, such as HTTPS or TCP, so F5 knows which members are available.

Using the F5 GUI

Log in to the F5 BIG-IP management interface.
Go to Local Traffic → Virtual Servers → Virtual Server List.
Click Create.

Configure the main settings:
Name: vs_web_https
Destination Address/Mask: 10.10.10.100
Service Port: HTTPS (443)
Protocol: TCP

Under Configuration, select:

HTTP Profile: http if you want F5 to inspect/process HTTP

SSL Profile (Client): your client-side SSL certificate/profile if F5 terminates HTTPS

Source Address Translation: commonly Auto Map if the backend servers don't have a route back through the F5

Under Resources → Default Pool, select your backend pool.

Click Finished.

General Properties

Name: vs_testbluesftp-443
Partition /Path : Common
Type: Performance (Layer 4)
Source Address: Host
                0.0.0.0/0

Destination Address/Mask: Host
                    10.25.246.60


Service Port: 443  Https

Notify Status to Virtual Address: Checked

CREATE A POOL 

If you haven't created the pool yet

Go to:

Local Traffic → Pools → Pool List → Create

For example:
Pool Name: web_pool
Members:
10.20.20.11:443
10.20.20.12:443

You should also configure an appropriate health monitor, such as HTTPS or TCP, so F5 knows which members are available.

Important distinction

If by VIP you mean a floating/self IP or you're working with an F5 HA pair, that's different from creating a Virtual Server. A typical HA setup has Self IPs, floating Self IPs, and Virtual Servers/VIPs.

If you tell me whether you're using F5 BIG-IP TMOS via GUI or CLI, and whether the VIP is HTTP, HTTPS, TCP, or UDP, I can give you the exact configuration steps/CLI commands.