IBM RS/6000 SP manual If the cabling does not match, correct the cabling

				Switch Function (MAP 0620)
Table 1-6. SP Switch2 error conditions (continued)
Error #	Device Message	Link Message	Description and Action
−4	Device has been	Link has been	Description: Switch network not wired as specified in switch
	removed from	removed from	topology or problem with connection between switch and
	network, faulty	network or miswire,	device.
		faulty	Note: You may get this error number for a jack which could
			connect to a node, but instead has a wrap plug. In this case,
			this message is a warning only and can be ignored.
			Action:
			1.	Check the cable_miswire file in
				var/adm/SPlogs/cssX/p0 (where X=0 or 1) and rewire
				the cable as needed.
			2.	If the cabling does not match, correct the cabling
				problem, then go to step 5 below.
			3.	If this occurs on all nodes of a frame, check for a
				logical-to-physical frame number mismatch.
			4.	If there is a mismatch, have the customer update the
				configuration, or you can correct the cabling, as
				appropriate.
			5.	Go to ªStep 0620-004º on page 1-22.
−5	Device has been	Link has been	Description: Node was fenced from the network.
	removed from	removed from	Action: run Eunfence for the node.
	network by system	network by system
	administrator	administrator
−6	Device has been	Link has been	Description: AUTOJOIN was not selected for node during
	removed from	removed from	removal.
	network, no	network, no	Action:
	AUTOJOIN	AUTOJOIN
			1.	If there is an obvious problem, like node powered off or
				disconnected, fix that problem first. Then issue
				Eunfence for this processor node.
			2.	If problem was resolved, repeat ªStep 0620-001ºon
				page 1-17for next problem or go to ªStep 0620-021ºon
				page 1-27to verify fix.
			3.	If problem was not resolved, go to ªStep 0620-004ºon
				page 1-22.
−7	Device has been	Link has been	Description: Possible hardware problem.
	removed from	removed from	Action: Go to ªStep 0620-004º on page 1-22.
	network for not	network, fenced
	responding
−8	Device has been	Link has been	Description: Initialization of this link detected a different
	removed from	removed from	switch node number than the one expected.
	network because	network, probable	Action:
	of a miswire	miswire
			1.	Check the cable_miswire file in
				var/adm/SPlogs/cssX/p0 (where X=0 or 1) and rewire
				the cable as needed.
			2.	If the cabling does not match, correct the cabling
				problem, then go to step 5.
			3.	If this occurs on all nodes of a frame, check for a
				logical-to-physical frame number mismatch.
			4.	Have the customer update the configuration, or you can
				correct the cabling, as appropriate.
			5.	Repeat ªStep 0620-001º on page 1-17 for next problem
				or go to ªStep 0620-021º on page 1-27 to verify fix.

Chapter 1. Maintenance Analysis Procedures (MAPs) 1-21