MVPIs it common to have 'standard' http, tcp, oneconnect profiles that every similar vip uses? Or do people usually create a specific one for each app? How about monitors? I have lots of apps that just need a simple GET to the root and return a 200. Can I use the same monitor for many different pools? Any concerns?
Cirrostratushi,
Normally, we can use different monitors,http,tcp profiles for each vip but i would think of thats waste of resources to configure each vip wise until any special requirement like some apps need more idle timeout,some apps x-forword proto enable or troubleshooting...but most cases we can default profiles..
The best approach would be configure one custom profile each profile wise and use that instead of default profile.
health monitors and SSL profile should be each diff vip wise becuase,SSL profile will help traffic stats and monitor more help troubleshooting.
Thx
Srini