cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1621
Views
0
Helpful
1
Replies

n1kv & netscaler vpath integration

hando_gin
Level 1
Level 1

Hi all,

I'm having trouble integrating this - I have followed the available documentation but to be honest it is extremly vague (or maybe I'm being unfair!).

I have 3 subnets, all located on the same switch, each with an SVI:

Routeable Net 1: 10.1.1.0/25 - 10.1.1.1 - VLAN 1233

Routeable Net 2: 10.1.1.128/25 - 10.1.1.129 - VLAN 1234

non-Routeable Net 3: 172.16.220.0/24 - 172.16.220.1 - VLAN 2234

My VSM IP is configured in Net 2 with my ESXi VEM modules in Net 1, so that's the L3 side of things sorted out in terms of VSM > VEM communication, I have a VSG which is also working fine and I have Cisco Prime running too so I know the platform itself is fine.

Mod  Ports  Module-Type                       Model               Status

---  -----  --------------------------------  ------------------  ------------

1    0      Virtual Supervisor Module         Nexus1000V          active *

2    0      Virtual Supervisor Module         Nexus1000V          ha-standby

3    332    Virtual Ethernet Module           NA                  ok

4    332    Virtual Ethernet Module           NA                  ok

5    332    Virtual Ethernet Module           NA                  ok

7    332    Virtual Ethernet Module           NA                  ok

8    332    Virtual Ethernet Module           NA                  ok

9    332    Virtual Ethernet Module           NA                  ok

10   332    Virtual Ethernet Module           NA                  ok

11   332    Virtual Ethernet Module           NA                  ok

12   332    Virtual Ethernet Module           NA                  ok

13   332    Virtual Ethernet Module           NA                  ok

15   332    Virtual Ethernet Module           NA                  ok

16   332    Virtual Ethernet Module           NA                  ok

17   332    Virtual Ethernet Module           NA                  ok

As you can see, all up and running.

I have installed the Netscaler using the OVA, in more than one way and using different interface configurations, but for the benefit of accuracy, following the document requires 2 interfaces configured as part of the VEM network, which I did, but the NetScaler doesn't work in L2 Adjacency mode as suggested in the manual - therefore I moved it to Net2.

vsm#

vservice node NS1 type adc

  ip address 10.1.1.143

  adjacency l3

  fail-mode open

And on the NetScaler

> show vpathparam

        Source IP: 10.1.1.143

        Global EncapMode: L3

I have this configured back in the VSM on the port-profile as suggested:

vsm#

port-profile type vethernet public-1234

  vmware port-group

  switchport mode access

  switchport access vlan 1234

  no shutdown

  system vlan 1234

  state enabled

However if I issue the 'show vservice brief' command I see the following:

ID Name                     Type   IP-Address      Mode   State   Module

  2 NS1                      adc    10.1.1.143     l3     Unreach 3,4,7,8,9,10,11,12,13,15,16,17,

So - vPath definitely not working, I can't even add a DNS server to the NetScaler as I can't get any packets too or from it - I can manage it from it's correct NSIP which is 10.1.1.150

NOTE: All IPs and VLANs have been updated but they relflect the idea.

Has anyone got a working config, example or have any experience integrating the NetScaler (I know this is a longshot since it was only released a week or so back, but I really need to see it working for a POC we're doing).

Please don't hesitate to ask for more info if you can help.

Thanks
Phil

1 Reply 1

andras bellak
Level 1
Level 1

You aren't being unfair about the documentation at all. I've probably spent 72 hours on the phone with TAC & Citrix on this, and have received very little guidance. At this point I'm about to give them one more shot, and then the 1000V netscalers are gone. I don't have time to keep screwing around with such a poorly documented and supported environment.

 

If I get this working after this call (about to start it up) I'll leave the info here.