Unsolved
This post is more than 5 years old
12 Posts
0
2941
CENTERA COPY DATA USING CIFS
ALL OF SUDDEN DATA COYPING USING CIFS IS VERY SLOW. TAKEN 5 DAYS TO COPY 30GB DATA. WHICH WAS TAKING 10MINS EARIER.
NO CONFIGURATION CHANGE. PLEASE SOME HELP ON THIS ISSUE.
BhumiNetworks
12 Posts
0
December 4th, 2012 06:00
HELLO SATISH,
I AM USING CUA WITH CIFS SHARE TO WRITE DATA INTO CENTERA. I SEE NODE C001N07 GOES OFFLINE AND COMES BACK ONLINE..WHENEVER I START DATA COPY USING CIFS.
JUST NOW IT WAS OFFLINE AND NOW BACK TO ONLINE...
SWITCH IS FINE.
Config# show node status all
Cabinet Node Roles Model Rail Status Failures
------------------------------------------------------------------------------------------------
1 c001n01 A,M,R,S - ATS on eth2:connected
1 c001n02 A,M,R,S - ATS on switch0, switc
h1, eth2:conne
cted
1 c001n03 A,M,R,S - ATS on eth2
1 c001n04 A,S - ATS on switch0, switc
h1, eth2
1 c001n05 A,S - ATS on eth2
1 c001n06 A,S - ATS on eth2
1 c001n07 A,S - ATS on eth2
1 c001n08 A,S - ATS on eth2
------------------------------------------------------------------------------------------------
Roles: A(ccess), M(anagement), R(eplication), S(torage)
Satish_Kutty
216 Posts
0
December 4th, 2012 06:00
Hi,
I beleive that you are using FMA or CTA to write data in to centera. Could you let me know if there are any hardware faults on Centera like node or switch failure?
Regards
Satish.N.Kutty
BhumiNetworks
12 Posts
0
December 4th, 2012 06:00
IGNORE THE FAILURES. I AM NOT USING ETH2 AND SWITCH0...
Config# SHOW SUMMARY
**************************** Show Config Warnings *****************************
The following cluster configuration issues were detected:
Warning: node c001n03: subnet mask not configured.
Warning: node c001n04: subnet mask not configured.
Warning: node c001n06: subnet mask not configured.
Warning: node c001n07: subnet mask not configured.
Warning: node c001n08: subnet mask not configured.
Warning: access role: nodes c001n01, c001n02 do not have the same mask as c001n05.
Warning: access role: nodes c001n01, c001n02 are not on the same subnet as c001n05.
*************************** Show Replication Detail ***************************
Centera Replication Detail Report
More? (yes, no) [yes]: YES
--------------------------------------------------------
Generated on Tuesday, December 4, 2012 8:12:40 PM GMT+05:30
Replication is disabled.
****************************** Show Security All ******************************
Cube Node Roles Status Locked Compliance
--------------------------------------------------------------------------
1 c001n01 A,M,R,S on No Basic
1 c001n02 A,M,R,S on Yes Basic
1 c001n03 A,M,R,S on Yes Basic
1 c001n04 A,S on Yes Basic
1 c001n05 A,S on Yes Basic
1 c001n06 A,S on Yes Basic
1 c001n07 A,S on Yes Basic
1 c001n08 A,S on No Basic
--------------------------------------------------------------------------
Roles: A(ccess), M(anagement), R(eplication), S(torage)
******************************** Show Features ********************************
Feature State
data-shredding off
storage-strategy capacity
storageonaccess on
******************************* Show Protection *******************************
Write Fallback
------------------------------------------
Mirror 0 B -
Parity 250 KB -
------------------------------------------
******************************* Show Ip Detail ********************************
Node c001n01
Configuration mode (Manual/DHCP): M
External IP address: 192.168.1.51
Subnet mask: 255.255.248.0
IP address of default gateway: 192.168.1.5
IP address of Domain Name Server: 202.54.12.164
Status: on
Link speed: 1000 Mb/s (automatic)
More? (yes, no) [yes]: YES
Duplex settings: F
Eth0: 00:E0:81:71:F9:A6
Eth1: 00:E0:81:71:F9:A7
Eth2: 00:E0:81:71:F9:A4 (UTP)
Node c001n02
Configuration mode (Manual/DHCP): M
External IP address: 192.168.1.52
Subnet mask: 255.255.248.0
IP address of default gateway: 192.168.1.5
IP address of Domain Name Server: 202.54.29.5
Status: on
Link speed: 1000 Mb/s (automatic)
Duplex settings: F
Eth0: 00:E0:81:71:C5:38
Eth1: 00:E0:81:71:C5:39
Eth2: 00:E0:81:71:C5:36 (UTP)
Node c001n03
Configuration mode (Manual/DHCP): D
External IP address:
Subnet mask: not configured
IP address of default gateway: not configured
IP address of Domain Name Server:
Status: on
Link speed: Unknown Mb/s
Duplex settings: Unknown
Eth0: 00:E0:81:71:CF:B4
Eth1: 00:E0:81:71:CF:B5
Eth2: 00:E0:81:71:CF:B2 (UTP)
Node c001n04
Configuration mode (Manual/DHCP): M
External IP address: 10.255.0.1
Subnet mask: not configured
IP address of default gateway: not configured
More? (yes, no) [yes]: YES
IP address of Domain Name Server: not configured
Status: on
Link speed: Unknown Mb/s
Duplex settings: Unknown
Eth0: 00:E0:81:72:56:44
Eth1: 00:E0:81:72:56:45
Eth2: 00:E0:81:72:56:42 (not configured)
Node c001n05
Configuration mode (Manual/DHCP): M
External IP address: 10.255.0.1
Subnet mask: 255.255.255.252
IP address of default gateway: not configured
IP address of Domain Name Server:
Status: on
Link speed: Unknown Mb/s
Duplex settings: Unknown
Eth0: 00:E0:81:72:25:FC
Eth1: 00:E0:81:72:25:FD
Eth2: 00:E0:81:72:25:FA (UTP)
Node c001n06
Configuration mode (Manual/DHCP): M
External IP address: 10.255.0.1
Subnet mask: not configured
IP address of default gateway: not configured
IP address of Domain Name Server: not configured
Status: on
Link speed: Unknown Mb/s
Duplex settings: Unknown
Eth0: 00:E0:81:72:51:D0
Eth1: 00:E0:81:72:51:D1
Eth2: 00:E0:81:72:51:CE (not configured)
Node c001n07
Configuration mode (Manual/DHCP): M
More? (yes, no) [yes]: YES
External IP address:
Subnet mask: not configured
IP address of default gateway: not configured
IP address of Domain Name Server: not configured
Status: on
Link speed: Unknown Mb/s
Duplex settings: Unknown
Eth0: 00:E0:81:72:6A:1E
Eth1: 00:E0:81:72:6A:1F
Eth2: 00:E0:81:72:6A:1C (not configured)
Node c001n08
Configuration mode (Manual/DHCP): M
External IP address: 10.255.0.1
Subnet mask: not configured
IP address of default gateway: not configured
IP address of Domain Name Server: not configured
Status: on
Link speed: Unknown Mb/s
Duplex settings: Unknown
Eth0: 00:E0:81:72:3D:50
Eth1: 00:E0:81:72:3D:51
Eth2: 00:E0:81:72:3D:4E (not configured)
********************************** Show ICMP **********************************
ICMP enabled: Enabled
********************************** Show SNMP **********************************
SNMP enabled: Disabled
Management Station: unknown:162
Community name: public
Heartbeat trap interval: 1 minute
****************************** Show Profile List ******************************
Profile Name Home Pool Enabled Roles
-----------------------------------------------------------------------------
anonymous default yes Monitor
admin default yes Monitor, Replication, Aud
it, Compliance, Configura
tion, Accesscontrol
More? (yes, no) [yes]: YES
console ConsoleArchive yes Monitor
default default yes Monitor, Profile-metadata
-----------------------------------------------------------------------------
****************************** Show Domain List *******************************
Domain name: Default
Cluster Access Nodes
-----------------------------------------------------------------
DefaultCluster 10.255.0.1:3682, 192.168.1.51:3682, 192.168
.1.52:3682, 192.168.3.11:3218, 192.168.3.11
:3682, 192.168.3.12:3218, 192.168.3.12:3682
-----------------------------------------------------------------
******************************* Show Pool List ********************************
Pool Name ID Profiles Mask
-------------------------------------------------------------------------------
cluster cluster 0 rdqeDcp-
default default 2 rdqeDcw-
AuditArchive dbd383e0-1dd1-11b2-b64c-e8dc585e0da6-3 0 rdqeDcw-
ConsoleArchive dbd383e0-1dd1-11b2-b64c-e8dc585e0da6-2 1 rdqeDcw-
SystemArchive dbd383e0-1dd1-11b2-b64c-e8dc585e0da6-4 0 rdqeDcw-
-------------------------------------------------------------------------------
***************************** Show Retention All ******************************
No retention settings found
*********************** Show Node Mode Maintenance All ************************
Node Maintenance
----------------------
c001n01 off
c001n02 off
c001n03 off
c001n04 off
c001n05 off
c001n06 off
c001n07 off
c001n08 off
----------------------
***************************** Show EDM Status All *****************************
Satish_Kutty
216 Posts
0
December 7th, 2012 08:00
Hi,
The cluster appears to be in good health apart from fact that the node c001n07 goes offline once you start writing data into it. Does the node bounce every time when you start writing data into it or is just happens when the load is heavy.
Regards
Satish.N.Kutty
BhumiNetworks
12 Posts
0
December 11th, 2012 05:00
CAN SOME ONE HELP ME PLEASE ON THIS ISSUE BEFORE I GIVE UP WITH EMC CENTERA FOR EVER.
I HAVE SOME HOPE SOME ONE WILL HAVE SOLUTION & WILL HELP ME
IN THIS FORUM.
THANKS
BhumiNetworks
12 Posts
0
December 11th, 2012 05:00
FOR MORE INFORMATION ABOUT NODE 2&7 GOING OFFLINE SEE THE TIME IN STATE ON THIS SNAP ATTACHED WITH POST.
BhumiNetworks
12 Posts
0
December 11th, 2012 05:00
SATISH,
NODE c001n07 & c001n02 GOES OFFLINE EVERYTIME WHEN I START COPYING DATA FROM CUI USING CIFS SHARE. FROM LAST ONE WEEK I WAS ABLE TO COPY ONLY 3GB DATA. I DONT KNOW WHAT GOING WRONG WITH THIS SYSTEM.
ATLEAST HELP ME IN FINDING OUT WHATS GOING WRONG WITH COPYING DATA AND WHY ITS TAKING SO MUCH TIME. I USED TO COPY 3GB DATA IN LESSTHEN 10-20MINS.
I AM UNABLE TO FIND THE RELEASE ATLEAST.
IF NODE GOES OFFLINE , BY ITSELF COMES BACK. PLEASE LET ME KNOW IF ANY REPORTS YOU NEED.
THANKS FOR YOUR HELP.
Satish_Kutty
216 Posts
0
December 17th, 2012 01:00
Hi,
Could you let me know the available space on the nodes 2 and 7.Node 2 also is an access node so please the check the switch setting to which Node 2 is connect to the LAN.
Regards
Satish.N.Kutty
Satish_Kutty
216 Posts
0
December 17th, 2012 01:00
I also see that all the nodes have been rebooted or restarted a day ago...was it a planned reboot..
Regards
Satish.N.Kutty
Satish_Kutty
216 Posts
0
December 20th, 2012 02:00
Hi,
Any updates on the issue...
Regards
Satish.N.Kutty
holgerjakob_c0722c
337 Posts
0
December 26th, 2012 23:00
Hi
You are definitely having a stability issue on your system. Uptimes of maximum one day are not good.
As you're running Gen4 Hardware, these nodes may be really having disk issues as they are quite old.
Based on your parity setting without a fallback, when you are not having at least seven nodes up at the time you write, CUA will get a write error and retry the write. When you space on CUA becomes small you will probably run into performance problems as there is not enough space available for your writes as objects are still pending to be written to Centera.
Set at least a fallback of m2 for your parity protection scheme.
Then think of new systems and a migration as gen4 will soon the eops.
Holger