RPC over HTTPS
Issue: After upgrading the software of the appliance to release 7.3, the monitoring reports do not have a special category for RPC over HTTPS connections.
Cause: When you upgrade the appliance to release 7.3, the RPC over HTTPS applications do not belong to their own service class. As a result, all RPC over HTTPS connections are listed as TCP Other connections in the reports.
Resolution: To categorize these connections as RPC over HTTPS connections, create a service class for them applications.
Issue: After creating a service class for RPC over HTTPS, all HTTP and HTTPS traffic is categorized as RPC over HTTP.
Cause: You have not added the destination IP address to the service class you have created for RPC over HTTPS applications.
Resolution: Modify the service class you have created for RPC over HTTPS applications, by adding the destination IP addresses of your servers.