英语练习
问题：The SRV1 bind9 dns service have external view and internal view, when SRV2 get dns zone from SRV1, it always get a same internal view dns zone file, so the SRV2 dns server are answer a old record.解决方案：On SRV1:generate two tsig key, the external view and internal view use different tsig key to allow SRV2 sync.On SRV2:use tsig key to sync dns zone file.
问题：On SRV1:The kea dhcp service was not allow the SRV2 device to relay the dhcp request. so the client unable get the dhcp address.解决方案：On SRV1:modify "subnet ...." to "subnet: 192.168.30.0/24" in /etc/kea/kea-dhcp4.conf, and restart kea-dhcp4-server service， and on Client，get dhcp address again.
问题：On SRV1:The dovecot lmtp socket was listend on /run/dovecot/lmtp, but postfix config was defined "/var/spool/postfix/private/dovecot-lmtp", so the users email can not send to dovecot mailbox.解决方案：modify ... to ... in /etc/dovecot/conf.d/10-master.conf file.
问题：On SRV1:the apache2 not enable remoteip module.On proxy1:the client is send a X-Forwarded-For header, but the proxy1 is not clear the header, so the backend apache2 service can not see real client address.解决方案：On SRV1:Execute the following command and reload apache2 service:a2enmod remoteipOn proxy1:Add the following line into /etc/nginx/sites-enabled/default file and reload nginx service:proxy_set_header X-Forwarded-For $remote_addr;
问题：The PE1 is import and export RT 65000:10, but PE2 is import and export RT 65000:20, their RT is different, so the route prefix can not install.解决方案：Execute the following command:...
问题：The direct route is intra route, but the MPLS VPN routes is inter route. in the ospf, intra route is prior to inter route, so the traffic always go through the direct route.# ospf prefer intra route to inter route解决方案：Execute the following command:...
问题：On Hub:Hub is not enable DMVPN phase 3, it not configure "ip nhrp redirect"Tunnel0 interface is not disable eigrp split-horizon and eigrp next-hop-self.On Spoke:Spoke is not configure "ip nhrp shortcut"解决方案：Execute the following command:...
问题：On Edge2：the bgp route exsit but it next-hop can not reachable, so the bgp route not install into route tableOn Edge1:Edge1 does not configure next-hop-self for peer.解决方案：Execute the following command:...
问题：On Server1:On IIS Service, the www.example.com site SSL certificate Subject CommonName is portal.example.com; the portal.example.com site SSL certificate Subject CommonName is www.example.com. so the client not trust the website.解决方案：On Server1:On IIS Service, change www.example.com site SSL certificate whose Subject CommonName is www.example.com.
问题：On Server1：On the AD sites and Services, Shanghai domain not create Shanghai AD subnet , so the dfs namespace can not map the client IP to shanghai.解决方案：On Server1:On the AD Sites and Services, create a AD subnet for 192.168.1.0/24.
问题：On Edge1:BGP not configure send-community parameter for peer.解决方案：On Edge1:Execute the following command:router bgp 65001 nei 1.1.1.1 send-community ext do wr
问题：On R2, OSPF redistribute route into the OSPF from EIGRP, at R3, this route will redistribute into EIGRP. vice versa. so the 1.1.1.0/24 route recive from incorrect router.解决方案：
问题：On Server1：The Prometheus target is set to 10.10.10.21:9100，but the node-exporter certificate not have 10.10.10.21 IP value, so the prometheus can not verify the node-exporter certificate.解决方案：On Server1:In /etc/prometheus/prometheus.yml, Change Prometheus target to node1.example.com:9100, and trust the root certificate.
问题：On Server1：The Sales ldap group not have permission to access /srv/samba/sales directory, because the /srv/samba/sales is 750 permission and owner is root:root. so the Sales can not access SalesShare SMB share. 解决方案：On Server1:Execute the following command:chown sales:sales /srv/samba/sales
问题：On Web NLB Cluster:the port rule Affinity is None, so the NLB randomly distribute the traffic to web1 and web2.解决方案：On Web NLB Cluster:Change NLB Affinity to Single
问题：On the router:the ipv6 forwarding is not enabled. so the client traffic can not access the internet.解决方案：On the router:execute the following commands:echo "net.ipv6.conf.all.forwarding=1" > /etc/sysctl.d/99-ipv6-forwarding.confsysctl --system
问题：On Server1：The relying party not have UPN claim，so the backend return HTTP 403.解决方案：On Server1:Add UPN claim to relying party.
问题：On Server1:The IIS Certificate is locate cert:\CurrentUser\My insted of cert:\LocalMachine\My，so the https can not binding this certificate.解决方案：On Server1:Export IIS certificate from cert:\CurrentUser\My and import it to cert:\LocalMachine\My, and binding the certificate on IIS Service www.example.com site.
问题：the backend apache2 web is name based virtualhost, it configure ServerName app.example.com, but haproxy request not have Host: app.example.com header, the apache2 match the request to default VirtualHost insted of app.example.com.解决方案：On Server1:modify the /etc/haproxy/haproxy.cfg file，and restart haproxy service:change "http-check send meth GET uri /health ver HTTP/1.1" to "http-check send meth GET uri /health ver HTTP/1.1 hdr Host app.example.com"