Configuration Mode Commands : SteelHead Configuration Commands : Peering Commands : in-path peering auto
  
in-path peering auto
Enables enhanced auto-discovery (automatic peering) for serial cascade and serial cluster deployments.
Syntax
[no] in-path peering auto
Parameters
None
Usage
With enhanced auto-discovery the SteelHead automatically finds the furthest SteelHead in a network and optimization occurs there. For example, in a deployment with four SteelHeads (A, B, C, D), where D represents the appliance that is furthest from A, the SteelHead automatically finds D. This simplifies configuration and makes your deployment more scalable.
By default, enhanced auto-discovery is enabled. When enhanced auto-discovery is disabled, the SteelHead uses regular auto-discovery. With regular auto-discovery, the SteelHead finds the first remote SteelHead along the connection path of the TCP connection and optimization occurs there. For example, if you had a deployment with four SteelHeads (A, B, C, D) where D represents the appliance that is furthest from A, the SteelHead automatically finds B, then C, and finally D and optimization takes place in each.
In some deployments, enhanced auto-discovery can simplify configuration and make your deployments more scalable. For a details about deployments that require enhanced auto-discovery, see the SteelHead Deployment Guide.
RiOS 5.5.x or later supports a large number of peers (up to 32,768) per SteelHead. This feature is available only on SteelHead models 5520, 6020, 6050, and 6120. After enabling extended peer table support, you must clear the data store and stop and restart the service.
For details about enhanced auto-discovery, see the Management Console online help or the SteelHead Management Console User’s Guide.
Preventing an Unknown (or Unwanted) SteelHead from Peering
Automatic peering (enhanced auto-discovery) greatly reduces the complexities and time it takes to deploy SteelHeads. It works so seamlessly that occasionally it has the undesirable effect of peering with SteelHeads on the Internet that are not in your organization's management domain or your corporate business unit. When an unknown (or unwanted) SteelHead appears connected to your network, you can create a peering rule to prevent it from peering and remove it from your list of connected appliances. The peering rule defines what to do when a SteelHead receives an auto-discovery probe from the unknown SteelHead. To prevent an unknown SteelHead from peering you must add a pass-through peering rule that passes through traffic from the unknown SteelHead in the remote location. For details, see the Management Console online help and the SteelHead Deployment Guide.
The no command option disables enhanced auto-discovery.
Example
amnesiac (config) # in-path peering auto
Product
SteelHead CX, SteelHead EX, SteelHead-v, SteelHead-c
Related Commands
show in-path peering rules