Add an arm to my test VPX
For testing purpose, I wanted to add another XenApp Farm in a separated subnet in my lab environment. As I already configured a NetScaler VPX in my lab, I decided to add an interface to this VPX connected to my new subnet. Here is how I did.
I added a new interface to my VPX (running on Hyper-V). Now I see the new interface :
> sh interface 1) Interface 0/1 (NetScaler Virtual Interface) #0 flags=0x8060 <ENABLED, UP, UP> MTU=1514, native vlan=1, MAC=00:##:##:##:##:#0, uptime 0h24m08s RX: Pkts(6000) Bytes(740378) Errs(0) Drops(1701) Stalls(0) TX: Pkts(9547) Bytes(11098923) Errs(0) Drops(0) Stalls(0) NIC: InDisc(0) OutDisc(0) Fctls(0) Stalls(0) Hangs(0) Muted(0) Bandwidth thresholds are not set. 2) Interface 1/1 (NetScaler Virtual Interface) #1 flags=0x8060 <ENABLED, UP, UP> MTU=1514, native vlan=1, MAC=00:##:##:##:##:#1, uptime 0h24m08s RX: Pkts(93) Bytes(20734) Errs(0) Drops(25) Stalls(0) TX: Pkts(327) Bytes(13858) Errs(0) Drops(0) Stalls(0) NIC: InDisc(0) OutDisc(0) Fctls(0) Stalls(0) Hangs(0) Muted(0) Bandwidth thresholds are not set. 3) Interface LO/1 (Netscaler Loopback interface) #2 flags=0x20008020 <ENABLED, UP, UP> MTU=1514, native vlan=1, MAC=00:##:##:##:##:#2, uptime 0h24m08s RX: Pkts(17648) Bytes(13984043) Errs(0) Drops(0) Stalls(0) TX: Pkts(20461) Bytes(8466374) Errs(0) Drops(0) Stalls(0) Bandwidth thresholds are not set.
I want to plug that new arm to a specific subnet. But, as you can see in the following command, I still have only one VLAN :
> sh vlan 1) VLAN ID: 1 Interfaces : 0/1 1/1 LO/1
I add my new VLAN :
> add vlan 2 -aliasName "Protected Network 1"
… Bind it to my new interface (identified by 1/1) :
> bind vlan 2 -ifnum 1/1
An IP is needed to bind with the VLAN . I declare it as subnet IP (SNIP) :
> add ns ip 192.168.1.254 255.255.255.0 -type SNIP
Then, I can bind my VLAN to the new IP Address :
> bind vlan 2 -IPAddress 192.168.1.254 255.255.255.0
…Done. I can now add services as Load Balancers or Access Gateways with their own Virtual IP (VIP). They will be automatically routed to the correct Interface.
sources : http://support.citrix.com/proddocs/topic/ns-system-10-map/ns-nw-interfaces-creatng-or-mdyfng–vlan-tsk.html