Home > Storage > Unity XT > Storage Admin > Dell Unity: NAS Capabilities > Packet reflect
Packet reflect, available starting in OE version 4.1, is a feature that ensures outbound (reply) packets are sent back to the same host or router as the inbound (request) packet. This enables the NAS server to bypass routing and ARP table lookups when replying to a packet, so no routing configuration is required. With packet reflect, information including the local IP, remote IP, and next-hop MAC address are cached from the incoming packet. When the NAS server replies to that packet, it leverages this information to send the outbound packet to the proper location.
With packet reflect enabled, reply packets are always returned to the local MAC interface from which the request packet was sent, regardless of the destination IP address. For example, if a packet is received from a local gateway that is unknown to the NAS server’s routing table, the reply packet will be returned to that unknown gateway, independent of the destination IP address. The return path is not influenced by the routing table. However, with packet reflect disabled, the reply packet path is determined by the destination IP address and the routing table. In this scenario, reply packets are returned using the routes defined in the routing table. The chosen path could be different than that of the originating unknown local gateway. This feature can be disabled (default) or enabled at the NAS server level and takes effect immediately.
Packet reflect enables dynamic routing automatic configuration and does not require any changes to the infrastructure. An example is if there is a router failure, replacement, or IP change. In these scenarios, packets may still be able to reach the Dell Unity system through a different router. Packet reflect enables the Dell Unity system to seamlessly adapt by sending the reply packets to the new router, since that is where the request packet was received from. This is an advantage compared to static routes, which must be manually managed by the network administrator.
Although Packet Reflect works for most of the communication to a NAS server, such as client-initiated file system IO, it is important to note that it does not work for communication initiated by the NAS server. For example, communication to a DNS or LDAP server still requires routing and ARP table lookups since there is no inbound packet to cache the necessary information from. Regardless of whether Packet Reflect is enabled, it is important to configure the appropriate routes on the Routes to External Services page to allow the NAS server to access these services.