554 Implementing the IBM Storwize V7000 with IBM Spectrum Virtualize V8.2.1
11.8.6  States of IP partnership
The different partnership states in IP partnership are listed in Table 11-13. 
Table 11-13   States of IP partnership
The following steps must be completed to establish two systems in the IP partnerships:
1. The administrator configures the CHAP secret on both the systems. This step is not 
mandatory, and users can choose to not configure the CHAP secret. 
2. The administrator configures the system IP addresses on both local and remote systems 
so that they can discover each other over the network.
3. If you want to use VLANs, configure your LAN switches and Ethernet ports to use VLAN 
tagging. 
IP partnership or partnership over native IP links These terms are used to describe the IP partnership feature. 
Discovery Process by which two IBM Spectrum Virtualize systems 
exchange information about their IP address configuration. For 
IP-based partnerships, only IP addresses configured for 
Remote Copy are discovered. 
For example, the first Discovery takes place when the user is 
running the mkippartnership CLI command. Subsequent 
Discoveries can take place as a result of user activities 
(configuration changes) or as a result of hardware failures (for 
example, node failure, ports failure, and so on).
IP partnership terminology Description 
State Systems 
connected
Support for 
active remote 
copy I/O 
Comments
Partially_Configured_Local No No This state indicates that the initial 
discovery is complete.
Fully_Configured Yes Yes Discovery successfully completed 
between two systems, and the two 
systems can establish remote copy 
relationships. 
Fully_Configured_Stopped Ye s Yes The partnership is stopped on the system. 
Fully_Configured_Remote_Stopped Yes No The partnership is stopped on the remote 
system. 
Not_Present Yes No The two systems cannot communicate 
with each other. This state is also seen 
when data paths between the two systems 
are not established. 
Fully_Configured_Exceeded Yes No Ther e are too many systems in the 
network, and the partnership from the local 
system to remote system is disabled. 
Fully_Configured_Excluded No No The conn ection is excluded because of too 
many problems, or either system cannot 
support the I/O work load for the Metro 
Mirror and Global Mirror relationships.