Basic Networking

Overview
After completing this module, you will be able to:
Identify basic NetScaler networking architecture.
Identify the IP address types that can be assigned to a NetScaler and the purpose of each
address.
Explain how the NetScaler fits in your network topology.
Identify deployment considerations and the advantages and disadvantages of specific deployment
considerations
Configure virtual LANs (VLANs) and determine when to split your LAN into multiple VLANs.
Identify the IP routing methods best suited for an environment.
2

2015 Citrix Systems

OSI Networking Model

Physical Layer (1)
Data Link Layer (2)
The Networking Layer (3)
The Transport Layer (4)
The Session Layer (5)
The Presentation Layer (6)
The Application Layer (7)

2015 Citrix Systems

NetScaler Architecture Overview

2015 Citrix Systems

NetScaler-owned IP Addresses
The NetScaler system uses different types of IP addresses for management and
proxying connections to the server
These IP addresses are:
NetScaler IP (NSIP) addresses
Mapped IP (MIP) addresses
Subnet IP (SNIP) addresses
Virtual IP (VIP) addresses

2015 Citrix Systems

2015 Citrix Systems

2015 Citrix Systems

2015 Citrix Systems

NetScaler IP Address
The NetScaler IP address (NSIP) is the primary address for management and
general system access
The default IP address and netmask is 192.168.100.1/16 (255.255.0.0)

2015 Citrix Systems

Mapped IP Address
A mapped IP (MIP) address is used for external connections from the NetScaler
system
The MIP address should be available across all subnets and should never be
bound to a VLAN

10

2015 Citrix Systems

Subnet IP Address
The subnet IP (SNIP) address is used in connection management and server
monitoring
A SNIP address provides the NetScaler system with an Address Resolution
Protocol (ARP) presence in subnets to which the system may not be directly
connected
A NetScaler system should have a SNIP address configured for every directly
connected subnet

11

2015 Citrix Systems

Virtual IP Address
VIP addresses are used for client-to-NetScaler-system communication
When the VIP address is a public IP address, it usually corresponds to the DNS
entry for a domain
A VIP address is automatically created when a virtual server is added

12

2015 Citrix Systems

Network Topology
You can deploy the NetScaler system in the following network topologies:
One-arm mode
Two-arm mode

13

2015 Citrix Systems

One-Arm Mode
A one-arm mode configuration allows:
A simple configuration with one physical interface and no risk of bridge loops
One or many VLANs with 802.1q tagging
Link aggregation to satisfy bandwidth requirements

14

2015 Citrix Systems

One-Arm Mode

15

2015 Citrix Systems

Two-Arm Mode

16

2015 Citrix Systems

NetScaler Gateway Deployment

You can deploy NetScaler Gateway in the following locations on your network:
In the network perimeter
In a secure network that does not have a perimeter network
With additional NetScaler Gateway appliances to support load balancing and failover

17

2015 Citrix Systems

NetScaler Gateway Deployment in the Perimeter Network

18

2015 Citrix Systems

NetScaler Gateway Deployment with XenMobile, XenApp and

XenDesktop

19

2015 Citrix Systems

Virtual Local Area Networks (VLANs)

A NetScaler system supports layer-2 port and IEEE 802.1q tagged VLANs
VLAN configurations are useful when you need to restrict traffic to certain groups
of stations

20

2015 Citrix Systems

VLAN Configuration
You can implement VLANs in the following environments:
Single subnet
Multiple subnets
VLANs (no tagging)
VLANs (802.1q tagging)

21

2015 Citrix Systems

Port-based VLANs
The membership of a port-based VLAN is defined by a set of network interfaces that share a
common, exclusive layer-2 broadcast domain
You can configure multiple port-based VLANs
Port-Based VLANs
Lets add a new VLAN to the NetScaler (VLAN 10). This new VLAN is created with the following command: add vlan 10
Then lets bind interface 10/1 to the newly created VLAN 10 natively. This is accomplished with the following command:
bind vlan 10 -ifnum 10/1
When bound natively, interface 10/1 is removed automatically from VLAN 1, the current native VLAN. It is then added to
VLAN 10. When this configuration is implemented the following rules will then apply:

22

2015 Citrix Systems

Tagged VLANs
VLAN tagging inserts an additional header between the layer-2 and layer-3 headers in the packet
The additional header contains a protocol ID and a VLAN ID
The virtual network with which the packet is associated is identified by the VLAN ID
Tagged VLANs
Lets add a tagged VLAN to the NetScaler (VLAN 30). This new VLAN is created with the following command: add vlan 30
Then lets bind interface 10/2 to the newly created VLAN 30 as a tagged member. This is accomplished with the following
command: bind vlan 30 -ifnum 10/2 tagged
When VLAN 30 is bound as a tagged member of interface 10/2, it is kept in VLAN 1 as a native member, but also added to
VLAN 30 as a tagged member. When this configuration is implemented the following rules will then apply.

23

2015 Citrix Systems

TAGALL
The Interface TAGALL Configuration

The TAGALL configuration on the NetScaler is specific only to the interface. The following rules
apply when leveraging the TAGALL feature:

24

2015 Citrix Systems

NSVLAN
NSVLAN is the VLAN to which the NetScaler management IP (NSIP) addresss
subnet is bound
By default, NSVLAN has a VLAN ID (VID) of 1

25

2015 Citrix Systems

IP Address Routing
The NetScaler system supports both dynamic and static routing
Most NetScaler implementations use some static routes to reduce routing
overhead
You can create backup static routes and monitor routes to enable automatic
switchover if a static route goes down

26

2015 Citrix Systems

Static Routes
Static routes are manually created to improve the performance of your network.
You can:
Monitor static routes to avoid service disruptions
Create null routes to prevent routing loops

27

2015 Citrix Systems

Layer-3 Mode
The layer-3 and layer-2 modes:
Determine how the NetScaler system handles packets that are sent to an IP address that it does
NOT own
Determine whether the NetScaler system should act as a switch and bridge the packets (layer-2
mode)
Determine whether the NetScaler system should act as a router and forward the packets (layer-3
mode)

28

2015 Citrix Systems

MAC-based Forwarding Mode

29

2015 Citrix Systems

Determining the Source IP Address

By default, the NetScaler does not use the IP address of the client
Source IP addresses of a connection are selected from a pool of MIPs and SNIPs
The NetScaler determines whether a MIP or SNIP should be used

30

2015 Citrix Systems

Sending a Client IP Address to Servers

The NetScaler system usually functions in a transparent proxy configuration.
Clients initiate connections to the NetScaler system using a VIP address
The NetScaler system terminates the connection from the client
The NetScaler system processes the packet
The NetScaler system initiates a connection to the appropriate server on behalf of the client

31

2015 Citrix Systems

Use Source IP Mode

Use Source IP (USIP) mode is a networking mode in which the NetScaler system
uses the actual client IP address to connect to the server and does not replace
the source IP address in packets sent to the server with a MIP or SNIP address.

32

2015 Citrix Systems

Link Aggregation
Link Aggregation combines data from multiple ports into a single high-speed link.

33

2015 Citrix Systems

Network Address Translation

Network address translation involves modification of the source IP address,
destination IP addresses or the TCP/UDP port numbers of IP packets that pass
through the NetScaler system.
The NetScaler system supports the following types:
Inbound network address translation
Reverse network address translation

34

2015 Citrix Systems

Lab Exercises
Complete the following lab exercises:
Exercise 2-1: Configuring Basic Networking

35

2015 Citrix Systems

WORK BETTER. LIVE BETTER.

36

2015 Citrix Systems