IBM ESS 3000, Hardware Planning And Installation Manual

Page: 29 / 108

ESS 3000 Networking
ESS Mgmt Node (EMS)
GUI Server
Health Monitor
Call Home
ESS-3000 So!ware
- RHEL 7.6/7.7
- xCAT
- Ansible
- Repos for RHEL 8.0,
Scale and MOFED
Container
Admin
GUI
Browser
Front View
Rear View
SSR Access (1Gb)
Fixed IP from
factory
Management (1Gb/10Gb)
Configuration
Upgrade
Deployment
High Speed Network
(100GbE/100Gb EDR)
RHEL 8.0
Scale
EMS
ess3001
1
Figure 3. ESS 3000 Networking
ess30013
ESS 3000 Sharing Existing Networks
Dedicated mgmt.
VLAN for ESS 3000
MGMT LAN shared with ESS
- One DHCP server at a time
ESS 3000
C10-T1
I/O Server – gssio1
I/O Server – gssio2
FSP
FSP
FSP
FSP Service
Network
(10.0.0.10 –
10.0.0.128)
Management/Provisioning
Network (192.168.x.x)
Clustering/
Data
Network
100 Gb EDR
100 GbE
External/Campus
Network
EMS – ems1
HMC 1
HMC 1
HMC 1
C10-T3
C10-T4
(10.0.0.1)
C10-T2
Container
Bridge
Figure 4. ESS 3000 Sharing Existing Networks
NVMe transport protocol in Elastic Storage System 3000
The Elastic Storage System 3000 systems uses the Non-Volatile Memory express (NVMe) drive transport
protocol.
• NVMe is designed specifically for flash technologies. It is a faster, less complicated storage drive
transport protocol than SAS.
• The NVMe-attached drives support multiple queues so that each CPU core can communicate directly
with the drive. This avoids the latency and overhead of core-to-core communication, to give the best
performance.
• NVMe offers better performance and lower latencies exclusively for solid-state drives through multiple
I/O queues and other enhancements.
Chapter 2. Technical overview 17