Sun Microsystems, Inc.  Sun System Handbook - ISO 3.4 June 2011 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-72-1006890.1
Update Date:2009-12-01
Keywords:

Solution Type  Problem Resolution Sure

Solution  1006890.1 :   Sun StorEdge[TM] 9900 TrueCopy paircreate fails due to incorrect MTU settings on IP router.  


Related Items
  • Sun Storage 9990V System
  •  
  • Sun Storage 9970 System
  •  
  • Sun Storage 9990 System
  •  
  • Sun Storage 9960 System
  •  
  • Sun Storage 9985 System
  •  
  • Sun Storage 9980 System
  •  
Related Categories
  • GCS>Sun Microsystems>Storage - Disk>Datacenter Disk
  •  

PreviouslyPublishedAs
209555


Symptoms
The customer was able to successfully create the RCU link between the MCU and RCU. However, when they attempted to run a paircreate on the entire consistency group (CTG) the command failed immediately from CCI. The first two devices in the CTG showed Copy status:

/usr/bin/paircreate -g na3-arch-dgt -f async 5 -vl
paircreate: [EX_CMDRJE] An order to the control/command device was rejected Refer to the command log(/HORCM/log120/horcc_ops-stgmgt1-1-sjl.log) for details.

/usr/bin/pairvolchk -g na3-arch-dgt
pairvolchk : execution error.
pairvolchk: [EX_ENQCTG] Unmatched CTGID within the group
Refer to the command log(/HORCM/log120/horcc_ops-stgmgt1-1-sjl.log) for details.

/usr/bin/pairdisplay -g na3-arch-dgt -fcx
Group PairVol(L/R) (Port#,TID, LU),Seq#,LDEV#.P/S,Status,Fence, %,P-LDEV# M
na3-arch-dgt disk0(L) (CL1-A , 0, 0)32487 0.P-VOL COPY ASYNC ,0 a00 -
na3-arch-dgt disk0(R) (CL1-R ,12, 0)23405 a00.S-VOL COPY ASYNC ,----- 0 -
na3-arch-dgt disk1(L) (CL1-A , 0, 1)32487 1.P-VOL COPY ASYNC ,0 a01 -
na3-arch-dgt disk1(R) (CL1-R ,12, 1)23405 a01.S-VOL COPY ASYNC ,----- 1 -
na3-arch-dgt disk2(L) (CL1-A , 0, 2)32487 2.SMPL ---- ------,----- ----- -
na3-arch-dgt disk2(R) (CL1-R ,12, 2)23405 a02.SMPL ---- ------,----- ----- -
na3-arch-dgt disk3(L) (CL1-A , 0, 3)32487 3.SMPL ---- ------,----- ----- -

After a few minutes the pair status changed to Suspended Error state:

/usr/bin/pairdisplay -g na3-arch-dgt -fcx
Group PairVol(L/R) (Port#,TID, LU),Seq#,LDEV#.P/S,Status,Fence, %,P-LDEV# M
na3-arch-dgt disk0(L) (CL1-A , 0, 0)32487 0.P-VOL PSUE ASYNC , 0 a00 -
na3-arch-dgt disk0(R) (CL1-R ,12, 0)23405 a00.S-VOL SSUS ASYNC , 100 0 -
na3-arch-dgt disk1(L) (CL1-A , 0, 1)32487 1.P-VOL PSUE ASYNC , 0 a01 -
na3-arch-dgt disk1(R) (CL1-R ,12, 1)23405 a01.S-VOL SSUS ASYNC , 100 1 -

They attempted to create the pair for a single device and the command was not rejected but the same symptoms followed (Copy -> PSUE/SSUS). We had the customer remove the RCU links and recreate them and then attempt to create the pairs from the TC GUI in Storage Navigator. The same symptoms occurred from the GUI as well. The paircreate would start and the first two pairs would show Copy status and then move to PSUE/SSUS status shortly after. None of the other device would even show Copy status, they still showed SMPL.



Resolution
Analysis of the autodump indicated that there were RCU link issues between the MCU and RCU arrays.

SyErr E/F MP# Date Time SSBNo R.SSB Detail Info.

C870 9F 06 07/05/14 18:29:40 20583 0 HRC/HODM stat is SUSPEND(statnoneexept)
CBBE FB 07 07/05/14 18:29:40 20584 0
C870 9F 06 07/05/14 18:29:40 20585 0 HRC/HODM stat is SUSPEND(statnoneexept)
CBBE FB 07 07/05/14 18:29:40 20587 0
CBBE FB 07 07/05/14 18:29:40 20588 0
C73C 9F 46 07/05/14 18:29:43 20589 0 RIO proc boot time exceeded(180s)
C73D 9F 46 07/05/14 18:29:43 20590 0
C828 9F 46 07/05/14 18:29:43 20591 0 SLEEP: RIO job sink(180s)-> permanenterr
C73C 9F 46 07/05/14 18:29:43 20592 0 RIO proc boot time exceeded(180s)
C73D 9F 46 07/05/14 18:29:43 20593 0
C828 9F 46 07/05/14 18:29:43 20594 0 SLEEP: RIO job sink(180s)-> permanenterr
C73C 9F 46 07/05/14 18:29:43 20595 0 RIO proc boot time exceeded(180s)

Analysis of the Cisco MD9509 FCIP switches showed that every time the paircreate command was issued the links would fail. The 9509 reported link failures issues between itself and the IP router. Further analysis of the IP router showed that the MTU was to 1500 while the MTU on the Cisco 9509 switch was set to 4000. Once the customer changed the MTU on the IP router to match the setting on the Cisco 9505 the paircreate was able to complete successfully.



Product
Sun StorageTek 9990V System
Sun StorageTek 9990 System
Sun StorageTek 9990
Sun StorageTek 9985 System
Sun StorageTek 9980 System
Sun StorageTek 9970 System
Sun StorageTek 9960 System
Sun StorageTek 9910
Sun StorageTek 9900V Series Array

Internal Comments
Sun StorEdge[TM] 9900 TrueCopy paircreate fails due to incorrect MTU settings on IP router.

To check the router MTU settings.


Cisco:

show interface fcip NUM (Requires FCIP tunnel to be up)

show tech-support details


An MTU value cannot be set manually but the PMTU flag can be set (default is on) which will attempt to discover the path MTU along the link. If PMTU is turned off, MTU reverts to 1518


Brocade 7500/FR4-18i/FC4-16i blade:

portshow ipif [slot]/geNUM

supportsave


For GE ports on a Silkworm 7500 or an FR4-18i blade in a Silkworm 48000, valid values are from 1500 to 2348. On a FC4-16i in a Silkworm 48000 valid values are from 1500 to 8256.


Brocade AP7420:

fcipshow NUM

supportshow


An MTU value cannot be set but 'Jumbo Support' can be turned on (2k/max FC frame) /off.


McData 1620/2640:

Use Element manager (browser). Advanced TCP/IP Configuration screen.
 <Document: 1002448.1> Collecting McData router information


An MTU of between 512 to 4096 (default 1508) can be manually set or use

Auto discovery (default on)


The MTU is but one of many settings that need to be carefully configured for the router link to work correctly.


truecopy, paircreate, fails, CCI, HORCM, Raid, Manager, MTU, RCU, LINK, MCU
Previously Published As
89536

Change History
Date: 2007-05-21
User Name: 31620
Action: Approved
Comment: Verified Metadata - ok
Verified Keywords - ok
Verified still correct for audience - currently set to contract
Audience left at contract as per FvF at
http://kmo.central/howto/content/voyager-contributor-standards.html
Checked review date - currently set to 2008-05-15
Checked for TM - adjusted for TrueCopy product
Publishing under the current publication rules of 18 Apr 2005:
Version: 3
Date: 2007-05-18
User Name: 31620
Action: Accept
Comment:
Version: 0
Date: 2007-05-18
User Name: 34660
Action: Approved
Comment: Looks good. Just added Internal section for how to identify the MTU for the different routers.
Version: 0


Attachments
This solution has no attachment
  Copyright © 2011 Sun Microsystems, Inc.  All rights reserved.
 Feedback