 01ba8ebfd6
			
		
	
	01ba8ebfd6
	
	
	
		
			
			There are minor changes here, that update the content of some files here is the link to the commit on downstream http://bitbucket.wrs.com/projects/DOCS/repos/ starlingx_upstreaming/commits/3b193cc3aa566b2040c7226a9ed32d08bd91b82f Signed-off-by: Rafael Jardim <rafaeljordao.jardim@windriver.com> Change-Id: I461fce0c81f4605c200572ff71ae52cc889a856b
		
			
				
	
	
	
		
			1.9 KiB
		
	
	
	
	
	
	
	
			
		
		
	
	Convert a Duplex System to Direct Connection
On a system configured to use switch-based network connection for the management and cluster host networks, you can convert to direct (peer-to-peer) connection.
The connection type is initially configured at installation. You can change it at any time. You must use the CLI to make the change.
- Use the - system modifycommand to specify direct connection (duplex-direct).- ~(keystone_admin)]$ system modify --system_mode=duplex-direct- This raises Config-out-of-date alarm messages on both controllers. 
- Lock and then unlock the standby controller to update its configuration. - Wait for the controller to be reported as Unlocked, Available, and Online, and its Config-out-of-date alarm message to be cleared. 
- Swact the controllers. 
- Lock the new standby controller. 
- Disconnect the management and infrastructure cables from the switch. - This raises Port failed and Interface failed alarms on the active controller for the management and infrastructure interfaces. 
- Reconnect the cables in a peer-to-peer configuration. - Wait for the network interface alarms to be cleared. 
- Unlock the standby controller to update its configuration. - Wait for the controller to be reported as Unlocked, Available, and Online, and its Config-out-of-date alarm message to be cleared. 
The system is now reconfigured to use direct connections for the internal networks.