Forum Discussion
5 Replies
- Matt_DierickEmployee
Hi,
Do you mean FQDN on the client side ? If yes, that means you have several IP addresses on client side (Several Virtual Servers). So you have to run the template several times.
One template run per Virtual Server (VIP).
- FulmetalNimbostratus
Hi,
As Matthieu says , one template per VS.
But If you use https , you could also try use some feature related to ssl such as SAN certificates (allowing multiple alternative names for the same ) or SNI for client who support TLS.
Regards
- Brenna_120553Nimbostratus
I'm not following. I followed the deployment guide from F5, and it's on this step in creating the iapp template vm: 8. HTTP version Unless the majority of your users are using HTTP 1.0 (not common), we recommend selecting Version 1.1 from the list. • FQDN: When you select Version 1.1, a new row appears asking for the FQDN the clients use to access SharePoint. Type it here. I have multiple web apps on SharePoint, but they sit on the same 2 web servers. So this is where I am wondering if I can additional FQDNs.
- Kevin_StewartEmployee
Are you talking about the stock SharePoint 2010 iApp template that comes with 11.3 and below, and is referencing health monitoring?
- Kevin_StewartEmployee
First things first, that HTTP/1.1 question relates to a simple monitoring configuration, and specifically what Host name the HTTP monitor sends to SharePoint in its request, because SharePoint cares about that sort of thing. The monitor only checks with a single host name and there's no facility to add or switch between host names in the iApp. You'd likely need an external monitor script to do such a thing, if you really need to.
As for a client request, the LTM VIP shouldn't get in the way of what the client sends, so assuming you have multiple host names that resolve to the same VIP, a SharePoint server that serves all of these applications, and a client makes a request for a specific host name, that same host name will arrive untouched at the SharePoint front end.