• No results found

Network Definitions

In document Implementation Guide X6 1.9.96 13 (Page 39-45)

5.6.1 Numbering conventions

Network IP-Interf. VLAN LACP-Key VLAG-Key Tier-ID Network

MGMT (G8264) 128 4095* - - -

-MGMT (G8272) 128 4095* - - -

-MGMT (G8296) 128 4095* - - -

-MGMT (G8124) 128 4095* - - -

-MGMT (G8052) 128 4092** - - -

-ISL - 4094 VLAN+1000 LACP Key 10

-GPFS - 100(++) port#+1000 LACP-Key - 192.168.10.0/24

HANA - 200(++) port#+1000 LACP-Key - 192.168.20.0/24

IMM (BMC) - 300(++) port#+1000 LACP-Key - 192.168.30.0/24

* VLAN 4095 is internally assigned to the management port(s) and cannot be changed.

** VLAN 4092 is a suggestion for the management VLAN.

Table 16: Numbering conventions

Note

The "(++)" in the table above indicates that +1 should be added for every new network in case of multiple GPFS, HANA or IMM LANs.

5.6.2 Internal Networks – Option 1 G8264 RackSwitch 10Gbit

This option is defined to use the G8264 RackSwitch 10Gbit Ethernet switch as a private network landscape for IBM GPFS and SAP HANA. This allows up to 24 Lenovo Solution servers (or 26 servers with "40G -> 4x 10G" breakout cable on ports 9 or 13) to be connected. The setup is as follows:

18,20,22,24,26,28...64 (HANA) .---,5_____

MGMT| G8264 Switch |1_____\__ Inter-Switch 40Gb Link (ISL)

‘---’ \_\_____Port 5 bonded ISL 17,19,21,23,25,27...63 (GPFS) / \

18,20,22,24,26,28...64 (HANA)/ \___Port 1 bonded ISL .---,5____/ /

MGMT| G8264 Switch |1_________/

‘---’

17,19,21,23,25,27...63 (GPFS)

Figure 9: G8264 RackSwitch front view

This guide defines the IBM GPFS network to be used as 192.168.10.0/24 and the SAP HANA network to be used as 192.168.20.0/24. If the customer wants to use a different IP range he may do so, but it should be used consistently as the internal (private) network within this guide.

Switch Port VLAN IP Address Hostname Server NIC g8264-1 MGMT 4095 <customer-mgmt IP1> <switch1> n/a

g8264-1 17 100 192.168.10.101 gpfsnode01 bond0

g8264-1 18 200 192.168.20.101 hananode01 bond1

g8264-1 19 100 192.168.10.102 gpfsnode02 bond0

g8264-1 20 200 192.168.20.102 hananode02 bond1

... ... ... ... ... ...

g8264-1 63 100 192.168.10.124 gpfsnode24 bond0

g8264-1 64 200 192.168.20.124 hananode24 bond1

g8264-2 MGMT 4095 <customer-mgmt IP2> <switch2> n/a

g8264-2 17 100 192.168.10.101 gpfsnode01 bond0

g8264-2 18 200 192.168.20.101 hananode01 bond1

g8264-2 19 100 192.168.10.102 gpfsnode02 bond0

g8264-2 20 200 192.168.20.102 hananode02 bond1

... ... ... ... ... ...

g8264-2 63 100 192.168.10.124 gpfsnode24 bond0

g8264-2 64 200 192.168.20.124 hananode24 bond1

Table 17: G8264 RackSwitch port assignments Note

There is no public network attached to these switches.

5.6.3 Internal Networks – Option 2 G8124 RackSwitch 10Gbit

This option is defined to use the G8124 RackSwitch 10Gbit Ethernet switch as a private network landscape for IBM GPFS and SAP HANA. This allows up to 7 Lenovo Solution servers to be connected. The setup is as follows:

2,4,6,8,10,12,14 (HANA) .---,24____

MGMT| G8124 Switch |23____\__ Inter-Switch 10Gb Link (ISL)

‘---’ \_\_____Port 24 bonded ISL 1,3,5,7,9,11,13 (GPFS) / \

2,4,6,8,10,12,14 (HANA)/ \___Port 23 bonded ISL .---,24___/ /

MGMT| G8124 Switch |23________/

‘---’

1,3,5,7,9,11,13 (GPFS)

Figure 10: G8124 RackSwitch front view

This guide defines the IBM GPFS network to be used as 192.168.10.0/24 and the SAP HANA network to be used as 192.168.20.0/24. If the customer wants to use a different IP range he may do so, but it should be used consistently as the internal (private) network within this guide.

Switch Port VLAN IP Address Hostname Server NIC g8124-1 MGMT-b 4095 <customer-mgmt IP1> <switch1> n/a

g8124-1 1 100 192.168.10.101 gpfsnode01 bond0

g8124-1 2 200 192.168.20.101 hananode01 bond1

g8124-1 3 100 192.168.10.102 gpfsnode02 bond0

g8124-1 4 200 192.168.20.102 hananode02 bond1

g8124-1 5 100 192.168.10.103 gpfsnode03 bond0

g8124-1 6 200 192.168.20.103 hananode03 bond1

... ... ... ... ... ...

g8124-1 13 100 192.168.10.107 gpfsnode07 bond0

g8124-1 14 200 192.168.20.107 hananode07 bond1

g8124-2 MGMT-b 4095 <customer-mgmt IP2> <switch2> n/a

g8124-2 1 100 192.168.10.101 gpfsnode01 bond0

g8124-2 2 200 192.168.20.101 hananode01 bond1

g8124-2 3 100 192.168.10.102 gpfsnode02 bond0

g8124-2 4 200 192.168.20.102 hananode02 bond1

g8124-2 5 100 192.168.10.103 gpfsnode03 bond0

g8124-2 6 200 192.168.20.103 hananode03 bond1

... ... ... ... ... ...

g8124-2 13 100 192.168.10.107 gpfsnode07 bond0

g8124-2 14 200 192.168.20.107 hananode07 bond1

Table 18: G8124 RackSwitch port assignments

5.6.4 Internal Networks – Option 3 G8272 RackSwitch 10Gbit

This option is defined to use the G8272 RackSwitch 10Gbit Ethernet switch as a private network landscape for IBM GPFS and SAP HANA. This allows up to 24 Lenovo Solution servers (or 32 servers with "40G -> 4x 10G" breakout cables on ports 49,50,51 or 52) to be connected. The setup is as follows:

2,4,6,8,10,12...48 (HANA) .---,54_____

MGMT| G8272 Switch |53_____\__ Inter-Switch 40Gb Link (ISL)

‘---’ \_\_____Port 54 bonded ISL 1,3,5,7,9,11...47 (GPFS) / \

2,4,6,8,10,12...48 (HANA) / \___Port 53 bonded ISL .---,54____/ /

MGMT| G8272 Switch |53_________/

‘---’

1,3,5,7,9,11...47 (GPFS)

Figure 11: G8272 RackSwitch front view

This guide defines the IBM GPFS network to be used as 192.168.10.0/24 and the SAP HANA network to be used as 192.168.20.0/24. If the customer wants to use a different IP range he may do so, but it should be used consistently as the internal (private) network within this guide.

Switch Port VLAN IP Address Hostname Server NIC g8272-1 MGMT 4095 <customer-mgmt IP1> <switch1> n/a

g8272-1 1 100 192.168.10.101 gpfsnode01 bond0

g8272-1 2 200 192.168.20.101 hananode01 bond1

g8272-1 3 100 192.168.10.102 gpfsnode02 bond0

g8272-1 4 200 192.168.20.102 hananode02 bond1

... ... ... ... ... ...

g8272-1 47 100 192.168.10.124 gpfsnode24 bond0

g8272-1 48 200 192.168.20.124 hananode24 bond1

g8272-2 MGMT 4095 <customer-mgmt IP2> <switch2> n/a

g8272-2 1 100 192.168.10.101 gpfsnode01 bond0

g8272-2 2 200 192.168.20.101 hananode01 bond1

g8272-2 3 100 192.168.10.102 gpfsnode02 bond0

g8272-2 4 200 192.168.20.102 hananode02 bond1

... ... ... ... ... ...

g8272-2 47 100 192.168.10.124 gpfsnode24 bond0

g8272-2 48 200 192.168.20.124 hananode24 bond1

Table 19: G8272 RackSwitch port assignments Note

There is no public network attached to these switches.

5.6.5 Internal Networks – Option 4 G8296 RackSwitch 10Gbit

This option is defined to use the G8272 RackSwitch 10Gbit Ethernet switch as a private network landscape for IBM GPFS and SAP HANA. This allows up to 43 Lenovo Solution servers (or 47 servers with "40G -> 4x 10G" breakout cables on ports 87 and 88) to be connected. The setup is as follows:

2,4...48/50,52...86 (HANA) .---,96_____

MGMT| G8296 Switch |95_____\__ Inter-Switch 40Gb Link (ISL)

‘---’ \_\_____Port 96 bonded ISL 1,3...47/49,51...85 (GPFS) / \

2,4...48/50,52...86 (HANA) / \___Port 95 bonded ISL .---,96____/ /

MGMT| G8296 Switch |95_________/

‘---’

1,3...47/49,51...85 (GPFS)

Figure 12: G8296 RackSwitch front view

This guide defines the IBM GPFS network to be used as 192.168.10.0/24 and the SAP HANA network to be used as 192.168.20.0/24. If the customer wants to use a different IP range he may do so, but it should be used consistently as the internal (private) network within this guide.

Switch Port VLAN IP Address Hostname Server NIC g8296-1 MGMT 4095 <customer-mgmt IP1> <switch1> n/a

g8296-1 1 100 192.168.10.101 gpfsnode01 bond0

g8296-1 2 200 192.168.20.101 hananode01 bond1

g8296-1 3 100 192.168.10.102 gpfsnode02 bond0

g8296-1 4 200 192.168.20.102 hananode02 bond1

... ... ... ... ... ...

g8296-1 85 100 192.168.10.143 gpfsnode43 bond0

g8296-1 86 200 192.168.20.143 hananode43 bond1

g8296-2 MGMT 4095 <customer-mgmt IP2> <switch2> n/a

g8296-2 1 100 192.168.10.101 gpfsnode01 bond0

g8296-2 2 200 192.168.20.101 hananode01 bond1

g8296-2 3 100 192.168.10.102 gpfsnode02 bond0

g8296-2 4 200 192.168.20.102 hananode02 bond1

... ... ... ... ... ...

g8296-2 85 100 192.168.10.143 gpfsnode43 bond0

g8296-2 86 200 192.168.20.143 hananode43 bond1

Table 20: G8296 RackSwitch port assignments Note

There is no public network attached to these switches.

5.6.6 Administrative, SAP-Access and Backup Networks – Option G8052 RackSwitch 1Gbit

The G8052 RackSwitch 1Gbit Ethernet switch is mainly used for the administrative networks. It can be used also for SAP-Access, backup network or other client specific networks. These networks are both public and private and need to be carefully separated with VLANs. The landscape is as follows:

2,4,6,8,10,12,14,...48

52.---,50______

51| G8052 Switch |49______\__ Inter-Switch 1Gb Link (ISL)

‘---’ \_\_____Port 50 bonded ISL 1,3,5,7,9,11,13,....47 (IMM) / \

2,4,6,8,10,12,14,...48 / \___Port 49 bonded ISL 52.---,50_____/ /

51| G8052 Switch |49__________/

‘---’

1,3,5,7,9,11,13,....47 (IMM)

Figure 13: G8052 RackSwitch front view

This guide defines the Integrated Management Module (IMM) Network to be 192.168.30.0/24. If the customer wants to use a different IP range for the Integrate Management Module (IMM) he may do so, but it should be used consistently within this guide.

Switch Port VLAN IP Address Hostname Server NIC

g8052-1 52 4092 <customer-mgmt IP1> <switch1> n/a g8052-1 1 300 192.168.30.101 cust-imm01.site.net sys-mgmt g8052-1 3 300 192.168.30.102 cust-imm02.site.net sys-mgmt

g8052-1 ... ... ... ... ...

g8052-1 47 300 192.168.30.124 cust-imm24.site.net sys-mgmt g8052-2 52 4092 <customer-mgmt IP2> <switch2> n/a g8052-2 1 300 192.168.30.125 cust-imm25.site.net sys-mgmt g8052-2 3 300 192.168.30.126 cust-imm26.site.net sys-mgmt

g8052-2 ... ... ... ... ...

g8052-2 47 300 192.168.30.148 cust-imm48.site.net sys-mgmt Table 21: G8052 RackSwitch port assignments

5.6.7 Network Configurations in a Clustered Environment

The networking in the clustered environment is the cornerstone of the Lenovo Solution. Therefore it is important that you ensure that the network (switches, wires, etc. ) has been set up before starting the installation of the servers. Below is one example of how to connect the customers network infrastructure with the clustered environment, see figure 14.

In document Implementation Guide X6 1.9.96 13 (Page 39-45)