02-13-2012 01:35 PM
I think you read too fast ![]()
The steelhead auxiliary interface is UP.
The (RSP) SMC primary interface is mapped to the steelhead auxiliary interface
The SMC primary is shown DOWN.
So no it is not solved !
I opened a case and your support team didn't find a solution.
I am thinking about a different solution.For the SMC, is it possible to configure the primary interface only for the management, and the auxiliary interface for the IP address reachable by the mobile client ?
Sure that other customers met this problem :
How to host the SMC (which should be available from remote mobile client) to a different VLAN than the management VLAN of the steelhead primary interface ?
Regards.
02-10-2012 02:14 PM
02-10-2012 12:58 AM - last edited on 02-10-2012 01:10 AM
It's too late, we don't have the license ...
whats is curious, is that the aux interface is UPand is working from the applpiance. However, it is not working in the SMC. I see the primary interface UP( no shut) but the link is down ...
02-10-2012 12:12 AM
If your customer has ESX servers, why not install the ESX version of SMC instead?
02-09-2012 09:54 AM - last edited on 02-10-2012 01:09 AM
Hi,
I am installing a SMC-VE (in RSP). By default, the physical primary interface is mapped to the SMC primary interface. It seems that it is a bridged link.
The problem is that the customer wants to put the SMC (which should be available from remote mobile client) to a different VLAN than the management VLAN of the steelhead primary interface. Is it possible ?
I am trying to map the SMC primary interface to the auxiliary physical interface. It didn't work ...
What are the solutions ?
Regards
© Copyright 2012 Riverbed Technology. All rights reserved Riverbed.com | Contact Us | Technical Support | Terms & Conditions | Privacy Policy