10-14-2011 04:41 AM
Hello Cris,
We dont have Steelhead Mobile yet there are plans for the future deployment therefore we would like to know if there are any limitations that we need to consider.
Regards
Igor
10-13-2011 03:26 AM
Just to be clear, you have Steelhead Mobile on your network and you are using fixed target rules to server-side Steelhead's primary interface for out of path mode?
10-11-2011 08:45 AM
Hello Chris,
Thanks to be patient with me on all my questions :) I guess we can simplify it if I'll explain exactly where my questions are coming from. We would like to deploy QUMU VNE on the RSP for Riverbed units. Due to the fact that all PRI's are already on the network we of course would like to keep using these interfaces to serve traffic from RSP based applications unfortunately I hear from some of the engineers that there are limistations and if we will be using PRI interface with RSP based images then there will be issues with Steelhead mobility solution (I assume because it will be communicating over PRI port to the steelhead appliance tohgether with the rest of the traffic from VNE)... so the question is , can we use Steelhead mobility service over AUX port? Are there any techncical reasons for not use PRI port for RSP based appliacations?
Thanks
Igor
10-06-2011 06:11 AM
If you mean to run SMC-VE as an RSP package, then you can have it use primary or aux to bind to.
10-06-2011 04:35 AM
Is the steelhead mobile has requirements to use PRI port only or it can use AUX for instance instead ?
Igor
09-30-2011 08:18 AM
You would use aux is the primary was busy doing out-of-path optimization, as one example.
09-30-2011 08:14 AM
Are there any advantages/disadvantages or preferences why AUX should be (or not) used instead of PRI for RSP support?
Regards
Igor
09-23-2011 04:28 PM
As long as each RSP package has an available interface for management, you can map the interface to the AUX on the Steelhead. This is done either in the Package Creator Tool or the 'mgmt-vni' command in the CLI. In this case the access would be L2 switched.
09-23-2011 01:01 AM
Bummer ..... I find it is pity that newer version has removed functionality of something that could be userful. OK ... We need to find a solution. Would it be possible to make all slots to be members of the same subnet (comon Layer2) so they all can be accessible via AUX which in that case should be just a physical port in to one of the network switches (which will provide default GW function) and if it is possible what kind of configuration do we need to do for the AUX to achieve this?
Thanks in advance
Igor
09-22-2011 02:52 PM
© Copyright 2012 Riverbed Technology. All rights reserved Riverbed.com | Contact Us | Technical Support | Terms & Conditions | Privacy Policy