Unsolved
This post is more than 5 years old
1 Rookie
•
20 Posts
0
1025
December 20th, 2017 12:00
Can we use different subnet IPs for Cube1 and Cube 2 nodes in the same Centera cluster?
Hello Team, as i am very new to Centera, your inputs will really help me to plan the configuration.
Centera Current Setup:-
Total no of Nodes = 12 [ 4 * in Multi role and 8 in Storage role / node]
New Upgraded Nodes = 8 [ 4 * added to the Cube1 as a storage nodes and 4 added to the new Cube2 (2 * will be configured as Access nodes and 2 * will be configured as storage node)]
there is an challenge in getting new IPs as like the Cube1 node assigned IPs for new Centera Access Nodes in the new Cube (2).
So - Can we use different segment / subnet IPs for the Access nodes Or Can we use all new nodes as storage nodes in the new Cube (2).
Doing so is there any impact? what is the best practice.
2. Does encryption enabled by default in Centera? if so, any command to check the same?
3. How to expand the storage pool capacity post the new nodes added? (If any standard procedure along with command will really help me)
The below output may give some information with the current configuration...!!!!
Network | Node | IP address | Gateway | Subnetmask | Failover address |
--------------------------------------------------------------------------------------------------------------------
default | c001n01 | 172.x.x.x | 172.x.x.x | 255.x.x.x | - |
default | c001n03 | 172.x.x.x | 172.x.x.x | 255.x.x.x | - |
default | c001n04 | 172.x.x.x | 172.x.x.x | 255.x.x.x | - |
default | c001n02 | 172.x.x.x | 172.x.x.x | 255.x.x.x | - |
--------------------------------------------------------------------------------------------------------------------
**************************** Show Config Warnings *****************************
There were no cluster configuration issues detected.
*************************** Show Replication Detail ***************************
Centera Replication Detail Report
--------------------------------------------------------
More? (yes, no) [yes]:
Generated on Thursday, December
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 | No | Basic |
1 | c001n03 A,M,R,S | on | No | Basic |
1 | c001n04 A,M,R,S | on | No | Basic |
1 | c001n05 S | on | No | Basic |
1 | c001n06 S | on | No | Basic |
1 | c001n07 S | on | No | Basic |
1 | c001n08 S | on | No | Basic |
1 | c001n09 S | on | No | Basic |
1 | c001n10 S | on | No | Basic |
1 | c001n11 S | on | No | Basic |
1 | c001n12 S | on | No | Basic |
--------------------------------------------------------------------------
Roles: A(ccess), M(anagement), R(eplication), S(torage)
******************************** Show Features ********************************
Feature | State |
data-shredding | off |
storage-strategy | performance |
performance: full | |
threshold: 256 KB |
******************************* Show Protection *******************************
Write | Fallback |
------------------------------------------
Mirror | 0 B | - |
Parity | disabled | - |
------------------------------------------
***************************** Show EDM Status All *****************************
Node | EDM-Status |
---------------------
c001n01 enabled
c001n02 enabled
c001n03 enabled
c001n04 enabled
c001n05 enabled
c001n06 enabled
c001n07 enabled
c001n08 enabled
c001n09 enabled
c001n10 enabled
c001n11 enabled
c001n12 enabled
---------------------