236 Configuring network domains

NN47250-500 (Version 03.01)

Network domain seed affinity

When there are multiple Network Domain seeds in an installation, a Network Domain member connects to the seed with
which it has the highest configured affinity. If that seed is unavailable, the Network Domain member connects to the seed
with which it has the next-highest affinity.
Figure 6 illustrates how a WSS connects to a Network Domain seed based on its configured affinity for the seed.

Figure 6. Configuring aWSS’s affinity for a network domain seed

In the example above, a WSS in the Mobility Domain at the corporate office is configured as a member of a Network
Domain that has a local seed, as well as seeds at the two branch offices and the three sales offices. The WSS has an
affinity value of 10 (highest) for the local seed, and an affinity value of 7 for the seed at Branch Office 1. The WSS has
an affinity of 5 (the default) for the other seeds in the Network Domain.
In the event that the local Network Domain seed becomes unavailable, the WSS then attempts to connect to the seed at
Branch Office 1, its next-highest-affinity seed. Once connected to this seed, the WSS then periodically attempts to
connect to the local seed. When the WSS is able to connect to the local seed again, it drops the connection to the seed at
Branch Office 1.
When you configure a WSS to be a member of a Network Domain, you specify the seed(s) to which it can connect. As
part of this configuration, you can also specify the affinity the WSS has for each seed.
Sales Office A Sales Office B Sales Office C
Branch Office 2Branch Office 1
Layer 2-3
Layer 2-3 Layer 2-3
Corporate Office
Bob
ND Seed
Peer
ND Seed
Peer
Local
ND Seed
ND Seed
Peer
ND Seed
Peer
ND Seed
Peer
WAN Link
ND Affinity configuration on WSS:
For Local ND Seed = 10
For ND Peer at Branch 1 = 7
For all other ND Peers = 5
When Local ND Seed goes down,
then ND Peer at Branch 1 is used.