1. Create L7 method named “http.condition” in AppDirector -> Layer 7 Farm Selection -> Method with these parameters:
- Method Name – http.condition - Method Type – Text
- Arguments – https
2. Create L7 method named “http.modification” in AppDirector -> Layer 7 Farm Selection -> Method with these parameters:
- Method Name – http.modification - Method Type – Text
- Arguments – http
3. Create L7 method named “http.cwa” in AppDirector -> Layer 7 Farm Selection -> Method with these parameters:
- Method Name – http.cwa - Method Type – Text
- Arguments – http://cwa.lyncradware.com -
4. Create L7 method named “https.cwa” in AppDirector -> Layer 7 Farm Selection -> Method with these parameters:
- Method Name – https.cwa - Method Type – Text
- Arguments – https://cwa.lyncradware.com
5. Create L7 Modification named “http.to.https” in AppDirector -> Layer 7 Modification -> Rules with these parameters:
- Name – http.to.https - Index – 1
- Farm – CWA.Servers - Admin Status - Enabled
- Modification Scope – Header and Body - Direction – Request
- Header & Body Condition - http.cwa - Header & Body Modification – https.cwa
6. Create L7 Modification named “https.to.http” in AppDirector -> Layer 7 Modification -> Rules with these parameters:
- Name – https.to.http - Index – 2
- Farm – CWA.Servers - Admin Status - Enabled
- Modification Scope – Header and Body - Direction – Reply
- Header & Body Condition - https.cwa - Header & Body Modification – http.cwa
7. Create L7 Modification named “all.http” in AppDirector -> Layer 7 Modification -> Rules with these parameters:
- Name – all.http - Index – 3
- Farm – CWA.Servers - Admin Status - Enabled
- Modification Scope – Header and Body - Direction – Request
- Header & Body Condition - http.condition - Header & Body Modification – http.modification
Compression Configuration
1. Create a compression policy named “comp.policy” in AppDirector -> Servers ->
Layer4 Traffic configuration -> Compression Policy with these parameters:
- Policy Name – comp.policy - Algorithm – GZIP
- Compression lever – 1 - Minimum Content Length – 1
- Maximum Content length - 10485760 - Leave all other fields as default
SSL Policy Configuration
1. Create an SSL policy in AppDirector -> L4 Traffic Redirection -> SSL Policy with these parameters:
- Policy name – cwa.pol - Certificate – cwa
- Listening Server Port – 80
- HTTP Redirection Conversion State - Enabled - Leave all other fields as default
Note: The cwa certificate needs to be imported from the Lync servers. For more information on exporting, importing, or creating a certificate, see the AppDirector User Guide.
Layer 4 Configuration
1. Create a Layer 4 policy named “directors.5060” in AppDirector -> Layer 4 Traffic Redirection -> Layer 4 Policies with these parameters:
- L4 Policy Name – directors.5060 - Virtual IP – 192.168.1.160 - L4 Protocol – TCP
- L4 Port – 5060 - Application - any
- Farm Name – director.servers - Leave all other fields as default
2. Create a Layer 4 policy named “directors.5061” in AppDirector -> Layer 4 Traffic Redirection -> Layer 4 Policies with these parameters:
- L4 Policy Name – directors.5061 - Virtual IP – 192.168.1.160 - L4 Protocol – TCP
- L4 Port – 5061 - Application - any
- Farm Name – director.servers - Leave all other fields as default
3. Create a Layer 4 policy named “cwa.443” in AppDirector -> Layer 4 Traffic Redirection -> Layer 4 Policies with these parameters:
- L4 Policy Name – cwa.443
- Compression Policy – comp.policy - Leave all other fields as default
4. Create a Layer 4 policy named “proxy.to.fe.4443” in AppDirector -> Layer 4 Traffic Redirection -> Layer 4 Policies with these parameters:
- L4 Policy Name – proxy.to.fe.4443 - Virtual IP – 192.168.1.200
- L4 Protocol – TCP - L4 Port – 4443 - Application - any
- Farm Name – fe.servers
- Leave all other fields as default
5. Create a Layer 4 policy named “fe.im.req.8057” in AppDirector -> Layer 4 Traffic Redirection -> Layer 4 Policies with these parameters:
- L4 Policy Name – fe.im.req.8057
- Leave all other fields as default
6. Create a Layer 4 policy named “fe.dcom.135” in AppDirector -> Layer 4 Traffic Redirection -> Layer 4 Policies with these parameters:
- L4 Policy Name – fe.dcom.135
- Leave all other fields as default
7. Create a Layer 4 policy named “fe.web.services.8080” in AppDirector -> Layer 4 Traffic Redirection -> Layer 4 Policies with these parameters:
- L4 Policy Name – fe.web.services.8080 - Virtual IP – 192.168.1.200
- L4 Protocol – TCP - L4 Port – 8080 - Application - any
- Farm Name – fe.servers
- Leave all other fields as default
8. Create a Layer 4 policy named “fe.https.443” in AppDirector -> Layer 4 Traffic Redirection -> Layer 4 Policies with these parameters:
- L4 Policy Name – fe.https.443
- Leave all other fields as default -
9. Create a Layer 4 policy named “fe.conf.444” in AppDirector -> Layer 4 Traffic Redirection -> Layer 4 Policies with these parameters:
- L4 Policy Name – fe.conf.444
- Leave all other fields as default
10. Create a Layer 4 policy named “fe.call.admin.448” in AppDirector -> Layer 4 Traffic Redirection -> Layer 4 Policies with these parameters:
- L4 Policy Name – fe.call.admin.448 - Virtual IP – 192.168.1.200
- L4 Protocol – TCP - L4 Port – 448 - Application - any
- Farm Name – fe.servers
- Leave all other fields as default
11. Create a Layer 4 policy named “fe.sip.5060” in AppDirector -> Layer 4 Traffic Redirection -> Layer 4 Policies with these parameters:
- L4 Policy Name – fe.sip.5060 - Virtual IP – 192.168.1.200 - L4 Protocol – TCP
L4 Port – 5060
- Application - any
- Farm Name – fe.servers
- Leave all other fields as default
12. Create a Layer 4 policy named “fe.mtls.5061” in AppDirector -> Layer 4 Traffic Redirection -> Layer 4 Policies with these parameters:
- L4 Policy Name – fe.mtls.5061
- Leave all other fields as default
13. Create a Layer 4 policy named “fe.app.share.5065” in AppDirector -> Layer 4 Traffic Redirection -> Layer 4 Policies with these parameters:
- L4 Policy Name – fe.app.share.5065 - Virtual IP – 192.168.1.200
- L4 Protocol – TCP - L4 Port – 5065 - Application - any
- Farm Name – fe.servers
- Leave all other fields as default
14. Create a Layer 4 policy named “fe.monitoring.5069” in AppDirector -> Layer 4 Traffic Redirection -> Layer 4 Policies with these parameters:
- L4 Policy Name – fe.monitoring.5069 - Virtual IP – 192.168.1.200
- L4 Protocol – TCP - L4 Port – 5069 - Application - any
- Farm Name – fe.servers
- Leave all other fields as default
15. Create a Layer 4 policy named “fe.res.group.5071” in AppDirector -> Layer 4 Traffic Redirection -> Layer 4 Policies with these parameters:
- L4 Policy Name – fe.res.group.5071 - Virtual IP – 192.168.1.200
- L4 Protocol – TCP - L4 Port – 5071 - Application - any
- Farm Name – fe.servers
- Leave all other fields as default
16. Create a Layer 4 policy named “fe.sip.req.5072” in AppDirector -> Layer 4 Traffic Redirection -> Layer 4 Policies with these parameters:
- L4 Policy Name – fe.sip.req.5072 - Virtual IP – 192.168.1.200 - L4 Protocol – TCP
- L4 Port – 5072 - Application - any
- Farm Name – fe.servers
- Leave all other fields as default
17. Create a Layer 4 policy named “fe.conf.anoun.5073” in AppDirector -> Layer 4 Traffic Redirection -> Layer 4 Policies with these parameters:
- L4 Policy Name – fe.conf.anoun.5073
- Leave all other fields as default
18. Create a Layer 4 policy named “fe.sip.req.call.park.5075” in AppDirector ->
Layer 4 Traffic Redirection -> Layer 4 Policies with these parameters:
- L4 Policy Name – fe.sip.req.call.park.5075 - Virtual IP – 192.168.1.200
- L4 Protocol – TCP - L4 Port – 5075 - Application - any
- Farm Name – fe.servers
- Leave all other fields as default
19. Create a Layer 4 policy named “fe.audio.test.5076” in AppDirector -> Layer 4 Traffic Redirection -> Layer 4 Policies with these parameters:
- L4 Policy Name – fe.audio.test.5076 - Virtual IP – 192.168.1.200
- L4 Protocol – TCP - L4 Port – 5076 - Application - any
- Farm Name – fe.servers
- Leave all other fields as default
20. Create a Layer 4 policy named “fe.av.age.turn.traff.5080” in AppDirector ->
Layer 4 Traffic Redirection -> Layer 4 Policies with these parameters:
- L4 Policy Name – fe.av.age.turn.traff.5080 - Virtual IP – 192.168.1.200
- L4 Protocol – TCP - L4 Port – 5080 - Application - any
- Farm Name – fe.servers
- Leave all other fields as default
21. Create a Layer 4 policy named “edge.replication.4443” in AppDirector -> Layer 4 Traffic Redirection -> Layer 4 Policies with these parameters:
- L4 Policy Name – edge.replication.4443 - Virtual IP – 192.168.1.230
- L4 Protocol – TCP - L4 Port – 4443 - Application - any
- Farm Name – edge.internal.servers - Leave all other fields as default
22. Create a Layer 4 policy named “edge.int.443” in AppDirector -> Layer 4 Traffic Redirection -> Layer 4 Policies with these parameters:
- L4 Policy Name – edge.int.443 - Virtual IP – 192.168.1.230 - L4 Protocol – TCP
- L4 Port – 443 - Application - any
Farm Name – edge.internal.servers
- Leave all other fields as default
23. Create a Layer 4 policy named “edge.int.5061” in AppDirector -> Layer 4 Traffic Redirection -> Layer 4 Policies with these parameters:
- L4 Policy Name – edge.int.5061 - Virtual IP – 192.168.1.230 - L4 Protocol – TCP
- L4 Port – 5061 - Application - any
- Farm Name – edge.internal.servers - Leave all other fields as default
24. Create a Layer 4 policy named “edge.int.5062” in AppDirector -> Layer 4 Traffic Redirection -> Layer 4 Policies with these parameters:
- L4 Policy Name – edge.int.5062 - Virtual IP – 192.168.1.230 - L4 Protocol – TCP
- L4 Port – 5062 - Application - any
- Farm Name – edge.internal.servers - Leave all other fields as default
25. Create a Layer 4 policy named “edge.int.udp.stun.3478” in AppDirector -> Layer 4 Traffic Redirection -> Layer 4 Policies with these parameters:
- L4 Policy Name – edge.int.udp.stun.3478 - Virtual IP – 192.168.1.230
- L4 Protocol – UDP - L4 Port – 3478 - Application - any
- Farm Name – edge.internal.servers - Leave all other fields as default
AppDirector Health Monitoring
1. Enable Health Monitoring in Health Monitoring -> Global Parameters.
2. Create a check for HTTP on server 192.168.1.40 in Health Monitoring -> Check Table with these parameters:
- Check name – cwa.server.1 - Method – HTTP
- Dest IP – 192.168.1.40 - Dest Port – 80
3. Create a check for HTTP on server 192.168.1.41 in Health Monitoring -> Check Table with these parameters:
- Check name – cwa.server.2 - Method – HTTP
- Dest IP – 192.168.1.41 - Dest Port – 80
4. Create a check for TCP port 5061 on server 192.168.1.23 in Health Monitoring
-> Check Table with these parameters:
- Check name – director.server.1 - Method – TCP.Port
- Dest IP – 192.168.1.23 - Dest Port – 5061
5. Create a check for TCP port 5061 on server 192.168.1.24 in Health Monitoring
-> Check Table with these parameters:
- Check name – director.server.2 - Method – TCP.Port
- Dest IP – 192.168.1.24 - Dest Port – 5061
6. Create a check for TCP port 5061 on server 11.1.11.1 in Health Monitoring ->
Check Table with these parameters:
- Check name – edge.internal.server.1 - Method – TCP.Port
- Dest IP – 11.1.11.1 - Dest Port – 5061
7. Create a check for TCP port 5061 on server 11.1.11.2 in Health Monitoring ->
Check Table with these parameters:
- Check name – edge.internal.server.2 - Method – TCP.Port
- Dest IP – 11.1.11.2 - Dest Port – 5061
8. Create a check for TCP port 5061 on server 192.168.1.21 in Health Monitoring
-> Check Table with these parameters:
- Check name – fe.server.1 - Method – TCP.Port
- Dest IP – 192.168.1.21 - Dest Port – 5061
9. Create a check for TCP port 5061 on server 192.168.1.22 in Health Monitoring
-> Check Table with these parameters:
- Check name – fe.server.2 - Method – TCP.Port
- Dest IP – 192.168.1.22 - Dest Port – 5061
10. Bind the check fe.server.1 to Server ‘fe.servers – 192.168.1.21’ in Health Monitoring -> Binding Table.
11. Bind the check fe.server.2 to Server ‘fe.servers – 192.168.1.22’ in Health Monitoring -> Binding Table.
12. Bind the check cwa.server.1 to Server ‘cwa.servers – 192.168.1.40’ in Health Monitoring -> Binding Table.
13. Bind the check cwa.server.2 to Server ‘cwa.servers – 192.168.1.41’ in Health Monitoring -> Binding Table.
14. Bind the check director.server.1 to Server ‘director.servers – 192.168.1.23’ in Health Monitoring -> Binding Table.
15. Bind the check director.server.2 to Server ‘director.servers – 192.168.1.24’ in Health Monitoring -> Binding Table.
16. Bind the check edge.internal.server.1 to Server ‘edge.internal.servers – 11.1.11.1’
in Health Monitoring -> Binding Table.
17. Bind the check edge.internal.server.2 to Server ‘edge.internal.servers – 11.1.11.2’
in Health Monitoring -> Binding Table.
VRRP Configuration
1. Enable VRRP in AppDirector -> Redundancy -> Global Configuration with these parameters:
- IP Redundancy Admin Status – VRRP - Interface Grouping – Enable
- ARP with interface grouping – Send - Backup Fake ARP – Enable
- Backup Interface Grouping – Enable - Leave all other fields as default
2. Create Virtual Router interfaces in AppDirector -> Redundancy -> VRRP ->
Virtual Router Table with these parameters:
- IF Index – 1 - VR ID – 101
- Priority – 255 (Highest number is Active device) - Primary IP – 192.168.1.1
- Leave all other options as default
3. Create Associated IP Addresses in AppDirector -> Redundancy -> VRRP ->
Associated IP Addresses with these parameters:
- IF Index – 1, VR ID – 101, Associated IP 192.168.1.1 - IF Index – 1, VR ID – 101, Associated IP 192.168.1.99 - IF Index – 1, VR ID – 101, Associated IP 192.168.1.100 - IF Index – 1, VR ID – 101, Associated IP 192.168.1.101 - IF Index – 1, VR ID – 101, Associated IP 192.168.1.102 - IF Index – 1, VR ID – 101, Associated IP 192.168.1.103 - IF Index – 1, VR ID – 101, Associated IP 192.168.1.160 - IF Index – 1, VR ID – 101, Associated IP 192.168.1.170 - IF Index – 1, VR ID – 101, Associated IP 192.168.1.200 - IF Index – 1, VR ID – 101, Associated IP 192.168.1.201 - IF Index – 1, VR ID – 101, Associated IP 192.168.1.202 - IF Index – 1, VR ID – 101, Associated IP 192.168.1.203 - IF Index – 1, VR ID – 101, Associated IP 192.168.1.204 - IF Index – 1, VR ID – 101, Associated IP 192.168.1.230
Mirroring Configuration
4. Enable Mirroring in AppDirector -> Redundancy -> Mirroring -> Active Device Parameters with these parameters:
- Client Table Mirroring – Enable - Session Id Table Mirroring – Enable - Leave all other fields as default
5. Add Mirror device in AppDirector -> Redundancy -> Mirroring -> Mirror Device Parameters with these parameters:
- Mirror Device IP – 192.168.1.2
AppDirector Internal Backup
The following are the settings for the Backup AppDirector:
Network Configuration
1. Create IP 192.168.1.2/24 on port 1 2. Peer Address 192.168.1.1
3. Create default route to 192.168.1.254
Auto Generating the Backup Configuration from the Primary AppDirector
1.
From the web interface menu of the Primary AppDirector, select File -> Configuration -> Receive from Device and choose Backup (Active-Backup) save the file on your computer and call it AppDirector.backup.txt.2.
Open the browser on the AppDirector backup device and upload the saved configuration (AppDirector.backup.txt) in File -> Configuration -> Send to Device3.
Reboot the AppDirector Backup deviceConfiguration Settings
AppDirector DMZ Active Network Configuration
1. Create IP 11.1.21.10/24 on port 1 - Peer Address 11.1.21.11 2. Create IP 11.1.10.10/24 on port 2 - Peer Address 11.1.10.11 3. Create default route to 11.1.21.254
4. Static route for network 192.168.1.0/24 to 11.1.10.254
Farm Configuration
5. Create a farm named “edge.sip.443” in AppDirector -> Farms -> Farm Table with these parameters:
- Farm Name – edge.sip.443 - Aging Time - 1800
- Session mode – RemoveOnSessionEnd-SPS
- Dispatch Method – Fewest Number of Users - Local - Connectivity checks – No Checks
- Leave all other fields as default
6. Create a farm named “edge.lm.443” in AppDirector -> Farms -> Farm Table with these parameters:
- Farm Name – edge.lm.443 - Aging Time - 1800
- Session mode – RemoveOnSessionEnd-SPS
- Dispatch Method – Fewest Number of Users - Local - Connectivity checks – No Checks
- Leave all other fields as default
7. Create a farm named “edge.meeting.443” in AppDirector -> Farms -> Farm Table with these parameters:
- Farm Name – edge.meeting.443 - Aging Time - 1800
- Session mode – RemoveOnSessionEnd-SPS
- Dispatch Method – Fewest Number of Users - Local - Connectivity checks – No Checks
- Leave all other fields as default
8. Create a farm named “edge.av.443” in AppDirector -> Farms -> Farm Table with these parameters:
- Farm Name – edge.av.443 - Aging Time - 1800
- Session mode – RemoveOnSessionEnd-SPS
- Dispatch Method – Fewest Number of Users - Local - Connectivity checks – No Checks
- Leave all other fields as default
9. Create a farm named “cwa.service.443” in AppDirector -> Farms -> Farm Table with these parameters:
- Farm Name – cwa.service.443 - Aging Time - 1800
- Session mode – RemoveOnSessionEnd-SPS
- Dispatch Method – Fewest Number of Users - Local - Connectivity checks – No Checks
- Leave all other fields as default
Client NAT Configuration
1. Enable Client NAT in AppDirector -> NAT -> Client NAT -> Global Parameters with these parameters:
- Client NAT – Enabled
2. Create Client Address IP’s in AppDirector -> NAT -> Client NAT -> Client NAT Address Table with these parameters:
- From IP – 11.1.10.170 to 11.1.10.170
3. Create Client NAT Intercept in AppDirector -> NAT -> Client NAT -> Client NAT Intercept Table with these parameters:
- From IP – 10.1.0.0 to 10.1.255.255
Extended Farm Configuration
1. Edit farm named “edge.sip.443” in AppDirector -> Farms -> Extended Parameters with these parameters:
- Client NAT – 11.1.10.170 - Leave all other fields as default
2. Edit farm named “edge.lm.443” in AppDirector -> Farms -> Extended Parameters with these parameters:
- Client NAT – 11.1.10.170 - Leave all other fields as default
3. Edit farm named “edge.meeting.443” in AppDirector -> Farms -> Extended Parameters with these parameters:
- Client NAT – 11.1.10.170 - Leave all other fields as default
4. Edit farm named “cwa.service.443” in AppDirector -> Farms -> Extended Parameters with these parameters:
- Client NAT – 11.1.10.170 - Leave all other fields as default
Servers Configuration
1. Create a server named “edge.sip.server.1” and attach it to the farm
“edge.sip.443” in AppDirector -> Servers -> Application Servers -> Table with these parameters:
- Server Name – edge.sip.server.1 - Farm Name – edge.sip.443 - Server Address – 11.1.10.1 - Client NAT – Enabled
- Client NAT Address Range – 11.1.10.170 - Leave all other fields as default
2. Create a server named “edge.sip.server.2” and attach it to the farm
“edge.sip.443” in AppDirector -> Servers -> Application Servers -> Table with these parameters:
- Server Name – edge.sip.server.2 - Farm Name – edge.sip.443 - Server Address – 11.1.10.2 - Client NAT – Enabled
- Client NAT Address Range – 11.1.10.170 - Leave all other fields as default
3. Create a server named “lync.content.server” and attach it to the farm
“edge.lm.443” in AppDirector -> Servers -> Application Servers -> Table with these parameters:
- Server Name – lync.content.server - Farm Name – edge.lm.443
- Server Address – 192.168.1.200 - Server Port - 4443
- Client NAT – Enabled
- Client NAT Address Range – 11.1.10.170 - Leave all other fields as default
4. Create a server named “meeting.server.1” and attach it to the farm
“edge.meeting.443” in AppDirector -> Servers -> Application Servers ->
Table with these parameters:
- Server Name – meeting.server.1 - Farm Name – edge.meeting.443 - Server Address – 11.1.10.5 - Client NAT – Enabled
- Client NAT Address Range – 11.1.10.170 - Leave all other fields as default
5. Create a server named “meeting.server.2” and attach it to the farm
“edge.meeting.443” in AppDirector -> Servers -> Application Servers ->
Table with these parameters:
- Server Name – meeting.server.2
- Farm Name – edge.meeting.443 - Server Address – 11.1.10.6 - Client NAT – Enabled
- Client NAT Address Range – 11.1.10.170 - Leave all other fields as default
6. Create a server named “av.server.1” and attach it to the farm “edge.av.443” in AppDirector -> Servers -> Application Servers -> Table with these
parameters:
- Server Name – av.server.1 - Farm Name – edge.av.443 - Server Address – 11.1.10.3 - Client NAT – Enabled
- Client NAT Address Range – 11.1.10.170 - Leave all other fields as default
7. Create a server named “av.server.2” and attach it to the farm “edge.av.443” in AppDirector -> Servers -> Application Servers -> Table with these
parameters:
- Server Name – av.server.2 - Farm Name – edge.av.443 - Server Address – 11.1.10.4 - Client NAT – Enabled
- Client NAT Address Range – 11.1.10.170 - Leave all other fields as default
8. Create a server named “cwa.server” and attach it to the farm “cwa.service.443” in AppDirector -> Servers -> Application Servers -> Table with these
parameters:
- Server Name – cwa.server - Farm Name – cwa.service.443 - Server Address – 192.168.1.170 - Client NAT – Enabled
- Client NAT Address Range – 11.1.10.170 - Leave all other fields as default
Layer 4 Configuration
1. Create a Layer 4 policy named “cwa.443.service” in AppDirector -> Layer 4 Traffic Redirection -> Layer 4 Policies with these parameters:
- L4 Policy Name – cwa.443.service - Virtual IP – 11.1.21.170
- L4 Protocol – TCP - L4 Port – 443 - Application - any
- Farm Name – cwa.service.443 - Leave all other fields as default
2. Create a Layer 4 policy named “edge.sip.443.service” in AppDirector -> Layer 4 Traffic Redirection -> Layer 4 Policies with these parameters:
- L4 Policy Name – edge.sip.443.service - Virtual IP – 11.1.21.200
- L4 Protocol – TCP - L4 Port – 443 - Application - any
- Farm Name – edge.sip.443 - Leave all other fields as default
3. Create a Layer 4 policy named “edge.av.443.service” in AppDirector -> Layer 4 Traffic Redirection -> Layer 4 Policies with these parameters:
- L4 Policy Name – edge.av.443.service - Virtual IP – 11.1.21.201
- L4 Protocol – TCP - L4 Port – 443 - Application - any
- Farm Name – edge.av.443 - Leave all other fields as default
4. Create a Layer 4 policy named “edge.stun.3478.service” in AppDirector -> Layer 4 Traffic Redirection -> Layer 4 Policies with these parameters:
- L4 Policy Name – edge.stun.3478.service - Virtual IP – 192.168.1.201
- L4 Protocol – UDP - L4 Port – 3478 - Application - any
- Farm Name – edge.av.443 - Leave all other fields as default
5. Create a Layer 4 policy named “edge.meeting.443.service” in AppDirector ->
Layer 4 Traffic Redirection -> Layer 4 Policies with these parameters:
- L4 Policy Name – edge.meeting.443.service - Virtual IP – 192.168.1.202
- L4 Protocol – TCP - L4 Port – 443 - Application - any
- Farm Name – edge.meeting.443 - Leave all other fields as default
6. Create a Layer 4 policy named “content.443.service” in AppDirector -> Layer 4 Traffic Redirection -> Layer 4 Policies with these parameters:
- L4 Policy Name – content.443.service - Virtual IP – 192.168.1.203
- L4 Protocol – TCP - L4 Port – 443 - Application - any
- Farm Name – edge.lm.443 - Leave all other fields as default
AppDirector Health Monitoring
1. Enable Health Monitoring in Health Monitoring -> Global Parameters.
1. Enable Health Monitoring in Health Monitoring -> Global Parameters.