summaryrefslogtreecommitdiff
path: root/docs/fapi.1
diff options
context:
space:
mode:
Diffstat (limited to 'docs/fapi.1')
-rw-r--r--docs/fapi.140
1 files changed, 21 insertions, 19 deletions
diff --git a/docs/fapi.1 b/docs/fapi.1
index 1dc317f..c47300d 100644
--- a/docs/fapi.1
+++ b/docs/fapi.1
@@ -124,7 +124,7 @@
.\" ========================================================================
.\"
.IX Title "FAPI 1"
-.TH FAPI 1 "2014-05-16" "fapi 0.7.0" "User Commands"
+.TH FAPI 1 "2014-05-16" "fapi 0.7.3" "User Commands"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
@@ -245,23 +245,13 @@ If you want to list all configured objects on your partition just run
.IX Subsection "Setting up a simple nPath Service"
A simple nPath service can be created as follows.
.PP
-.Vb 3
-\& # Create a nPath HTTP vserver, \*(AqnPath\*(Aq also auto disables NAT and PAT
-\& # fapi auto resolves the IP address.
+.Vb 2
\& fapi vserver myvserver.example.com:80 create PROTOCOL_TCP nPath
-\&
-\& # Add the pool to the vserver. The vservers name inside of BigIP will be
-\& # the FQDN followed by _PORT. In this case it would be:
-\& # myvserver.example.com_80 (or full: /Partition/myvserver.example.com_80)
-\& # The reason is that : are not allowed in vserver names.
\& fapi vserver myvserver.example.com:80 set pool foopool
\&
-\& # Add a nPath HTTPS vserver
-\& fapi vserver myvserver.example.com:443 create PROTOCOL_TCP nPath
-\& fapi vserver myvserver.example.com:443 set pool foopool
-\&
-\& # Restrict the vserver to a specific VLAN (IMPORTANT! security
+\& # Restrict the vservers to a specific VLAN (IMPORTANT! security
\& # hole otherwise!)
+\& fapi vserver myvserver.example.com:80 set vlan VLANNAME
\& fapi vserver myvserver.example.com:443 set vlan VLANNAME
\&
\& # Put the VirtualAddress of the vserver into a specific traffic group
@@ -281,15 +271,27 @@ And everything can be deleted as folows:
\& fapi node fooserver1.example.com delete
\& fapi node fooserver2.example.com delete
.Ve
-.SS "Setting up simple \s-1NAT\s0 Services"
-.IX Subsection "Setting up simple NAT Services"
-.Vb 1
-\& (Docu to be written)
+.SS "Setting up simple \s-1HTTP\s0 \s-1NAT\s0 Services"
+.IX Subsection "Setting up simple HTTP NAT Services"
+A simple \s-1HTTP\s0 NATed service can be created as follows.
+.PP
+.Vb 3
+\& fapi vserver myvserver.example.com:80 create PROTOCOL_TCP /Common/http
+\& fapi vserver myvserver.example.com:80 set vlan VLANNAME
+\& fapi vserver myvserver.example.com:80 set pool foopool
.Ve
+.PP
+In order to make this work your application servers need to have setup a
+default route to the loadbalancers floating self \s-1IP\s0.
.SS "Setting up simple \s-1SNAT\s0 Services"
.IX Subsection "Setting up simple SNAT Services"
+Same as setting up a NATed services, but you don't need to configure default
+routes from your application servers to the loadbalancers floating self \s-1IP\s0.
+.PP
+You need also to set the \s-1SNAT\s0 flag as follows:
+.PP
.Vb 1
-\& (Docu to be written)
+\& fapi vserver myvserver.example.com:80 set snat automap
.Ve
.SS "About the \s-1NAME\s0 argument"
.IX Subsection "About the NAME argument"