© 1999-2017 Citrix Systems, Inc. All rights reserved. p.108https://docs.citrix.com
show vlan <id> bind vlan 20 -ifnum 10/2
Add a SNIP address. add ns ip <IPAddress>
<netmask> -type SNIP
show ns ip
add ns ip 198.51.100.18
255.255.255.0 -type SNIP
Create services representing SIP servers. add service <serviceName>
show service <name>
add service SVC-S1
198.51.100.19 SIP_UDP 5060
dd service SVC-S2
198.51.100.20 SIP_UDP 5060
Create SIP load balancing virtual servers and bind the
services to it
add lb vserver <name>
bind lb vserver <vserverName>
<serviceName>
show lb vserver <name>
add lb vserver LBVS-1 SIP_UDP
203.0.113.15 5060
bind lb vserver LBVS-1 SVC-S1
bind lb vserver LBVS-1 SVC-S2
bind lb vserver LBVS-1 SVC-S2 save ns config
show ns config
Tasks NetScaler Command Syntax Examples
Use Case: Non-Jumbo to Jumbo Setup
Updated: 2015-02-06
Consider an example of a non-jumbo to jumbo setup in which load balancing virtual server LBVS1, configured on a NetScaler
instance NS1, is used to load balance traffic across servers S1 and S2. The connection between client CL1 and NS1 supports
non-jumbo frames, and the connection between NS1 and the servers supports jumbo frames.
Interface 10/1 of NS1 receives or sends traffic from or to client CL1. Interface 10/2 of NS1 receives or sends traffic from or
to server S1 or S2.
Interfaces 10/1 and 10/2 of NS1 are part of VLAN 10 and VLAN 20, respectively. For supporting only non-jumbo frames
between CL1 and NS1, the MTU is set to the default value of 1500 for both interface 10/1 and VLAN 10.
For supporting jumbo frames between NS1 and the servers, the MT U is set to 9000 for interface 10/2 and VLAN 20.
Servers and all other network devices between NS1 and the servers are also configured for supporting jumbo frames. Since
HTTP traffic is based on TCP, MSSs are set accordingly at each end point for supporting jumbo frames:
For the connection between CL1 and virtual server LBVS1 of NS1, the MSS on NS1 is set in a TCP profile, which is then
bound to LBVS1.
For the connection between a SNIP address of NS1 and S1, the MSS on NS1 is set in a TCP profile, which is then bound
to the service (SVC-S1) representing S1 on NS1.
To Next Page
Loading...
Need help?
General
