Jump to content
Welcome to our new Citrix community!

SVM and NSIP in different subnets.


Abhijith KS

Recommended Posts

Hi All,

 

I have a scenario where my SVM is in OOB subnet and I need to configure my VPX in a different subnet.  I tried, to use next hop to management service but it would not work. 

 

My SVM IP is 10.111.145.6 ( OOB Subnet )
Gateway : 10.111.145.1

 

Desired VPX subnet : 10.111.20.6 

Gateway : 10.111.20.1 

 

How do I use next hop to management service to get this to work ? 

 

PS : I am running 11.1 build and there are no vlan's configured on the SDX. 

 

Request you all to kindly assist.

 

Link to comment
Share on other sites

10 hours ago, Carl Stalhood1709151912 said:

In SDX 13 and ADC 13, SVM-to-NSIP communication happens in the backplane (no network needed).

 

Prior to 13, make sure SVM can connect to the NSIP on 443 and 22. Reverse direction for SNMP Traps.

Thanks Carl, I am running 11.1. 443 and 22 are open bi-directionally, but the SVM can't communicate with NSIP. What should I configure in next hop to management service ?

Link to comment
Share on other sites

1 hour ago, Abhijith KS said:

Thanks Carl, I am running 11.1. 443 and 22 are open bi-directionally, but the SVM can't communicate with NSIP. What should I configure in next hop to management service ?

11.1 is outdated and supported no more. I'd strongly suggest considdering to update to 12.1 or 13.0 (13.1 will come soon, so 13.0 will soon be my first choice)

 

Greetings

 

Johannes Norz

CTA, CCI, CCE-N

https://blog.norz.at

https://wonderkitchen.network

Link to comment
Share on other sites

"Next hop to management service" is designed for VPX routing tables where the normal route in the routing table does not route to the SVM. This typically occurs with NSIP on dedicated management networks. The idea is that when NSIP replies to the SVM it needs to send the reply to a different router than the normal routing table entries (e.g. default route). Another option is to configure PBRs on the VPX to route all traffic sourced by the NSIP to a NSIP-specific router.

  • Like 1
Link to comment
Share on other sites

9 hours ago, Johannes Norz said:

11.1 is outdated and supported no more. I'd strongly suggest considdering to update to 12.1 or 13.0 (13.1 will come soon, so 13.0 will soon be my first choice)

 

Greetings

 

Johannes Norz

CTA, CCI, CCE-N

https://blog.norz.at

https://wonderkitchen.network

Thanks for the reply John, will plan for an upgrade to 13. I think it is better to upgrade to 13 and then start planning my design in a 3-arm mode.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...