Shulou(Shulou.com)06/01 Report--

This article introduces the knowledge of "what do you need to pay attention to in the deployment of Azure Redis cache". Many people will encounter this dilemma in the operation of actual cases, so let the editor lead you to learn how to deal with these situations. I hope you can read it carefully and be able to achieve something!

When deploying the Azure Redis cache to the resource manager VNet

The cache must be in a private subnet, which can only contain Azure Redis cache instances and no other resources.

If you try to deploy the Azure Redis cache to a resource manager VNet subnet that contains other resources, the deployment will fail.

When hosting the Azure Redis cache in VNet, the designated port of the AZure is used.

Blocking one or more of the designated ports is the most common misconfiguration problem when using Azure Redis caching in VNet.

There are seven requirements for outbound ports:

All outbound connections to the Internet can be established through the client's local audit device.

Three of these ports route traffic to Azure endpoints that serve Azure storage and Azure DNS.

The remaining port range, which is used for internal Redis subnet communication. Subnet NSG rules are not required for internal Redis subnet communication.

There are eight requirements for the inbound port range:

Inbound requests in these ranges are inbound from other services hosted in the same VNET, or internal requests for communication in the Redis subnet.

When connecting to an Azure Redis cache instance hosted in VNET, the cache client must be in the same VNET or in a VNET with VNET peer interconnect enabled.

This includes any testing applications or diagnostic ping tools.

No matter where the client application is hosted, the network security group must be configured so that the client's network traffic can reach the Redis instance.

Peer port requirements for offsite replication:

If you use offsite replication between caches in an Azure virtual network

Please note that the recommended configuration is to unblock ports 15000-15999 for the entire subnet in the inbound and outbound directions of the two caches

In this way, even if an offsite failover occurs in the future, all replica components in the subnet can communicate directly with each other.

This is the end of the content of "what to pay attention to in Azure Redis cache deployment". Thank you for reading. If you want to know more about the industry, you can follow the website, the editor will output more high-quality practical articles for you!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.