New release0.7.3

2 files changed, 8 insertions, 56 deletions

diff --git a/docs/fapi.1 b/docs/fapi.1
index 78b7cdb..740f5f4 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.1" "User Commands"
+.TH FAPI 1 "2014-05-16" "fapi 0.7.2" "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
@@ -286,23 +276,9 @@ And everything can be deleted as folows:
 A simple \s-1HTTP\s0 NATed service can be created as follows.
 .PP
 .Vb 3
-\&  # Create a NATed HTTP vserver
-\&  # fapi auto resolves the IP address.
 \&  fapi vserver myvserver.example.com:80 create PROTOCOL_TCP /Common/http
-\&
-\&  # Add the pool to the vserver. 
+\&  fapi vserver myvserver.example.com:80 set vlan VLANNAME
 \&  fapi vserver myvserver.example.com:80 set pool foopool
-\&
-\&  # Add a NATed HTTPS vserver
-\&  fapi vserver myvserver.example.com:443 create PROTOCOL_TCP /Common/http
-\&  fapi vserver myvserver.example.com:443 set pool foopool
-\&
-\&  # Restrict the vserver to a specific VLAN (IMPORTANT! security
-\&  # hole otherwise!)
-\&  fapi vserver myvserver.example.com:443 set vlan VLANNAME
-\&
-\&  # Put the VirtualAddress of the vserver into a specific traffic group
-\&  fapi vip myserver.example.com set tgroup some\-traffic\-group
 .Ve
 .PP
 In order to make this work your application servers need to have setup a
diff --git a/docs/fapi.txt b/docs/fapi.txt
index d875f43..93e9122 100644
--- a/docs/fapi.txt
+++ b/docs/fapi.txt
@@ -95,22 +95,12 @@ EXAMPLES
   Setting up a simple nPath Service
     A simple nPath service can be created as follows.
 
-      # Create a nPath HTTP vserver, 'nPath' also auto disables NAT and PAT
-      # fapi auto resolves the IP address.
       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
@@ -131,24 +121,10 @@ EXAMPLES
   Setting up simple HTTP NAT Services
     A simple HTTP NATed service can be created as follows.
 
-      # Create a NATed HTTP vserver
-      # fapi auto resolves the IP address.
       fapi vserver myvserver.example.com:80 create PROTOCOL_TCP /Common/http
-
-      # Add the pool to the vserver. 
+      fapi vserver myvserver.example.com:80 set vlan VLANNAME
       fapi vserver myvserver.example.com:80 set pool foopool
 
-      # Add a NATed HTTPS vserver
-      fapi vserver myvserver.example.com:443 create PROTOCOL_TCP /Common/http
-      fapi vserver myvserver.example.com:443 set pool foopool
-
-      # Restrict the vserver to a specific VLAN (IMPORTANT! security
-      # hole otherwise!)
-      fapi vserver myvserver.example.com:443 set vlan VLANNAME
-
-      # Put the VirtualAddress of the vserver into a specific traffic group
-      fapi vip myserver.example.com set tgroup some-traffic-group
-
     In order to make this work your application servers need to have setup a
     default route to the loadbalancers floating self IP.