Saturday Jun 21, 2014

Exalogic VLAN Planning

This blog entry describes how to plan for VLANs required by Exalogic EECS 2.0.6. The components to consider in planning are 1) Applications hosted on Exalogic, 2) Enterprise Manager Operations Center (EMOC),  3) Enterprise Manager Cloud Control Agents 4) Infrastructure Components and 5) ZFS Storage.  These components need to be mapped to either the Exalogic Gateway switch running the Client Access Network EoIB (used for Client Access), to the Cisco Switch running the 1GB Management Network (used for Management), or to a Data Center switch running a dedicated replication network (used for ZFS storage backup/replication). The diagram below shows the components and their switch mappings. Lets walk through the component mappings.


Applications

Applications run on either physical compute node(s) or on vServer(s).  Application traffic runs through the Gateway Switch to clients and there is a minimum of 1 tagged VLAN required.  If application isolation is required each application can have its own tagged VLAN.  Traffic load is dependent on the Applications

Exalogic Manager Operations Center

Enterprise Manger Operations Center is the Exalogic Controller, runs on vServers and is required only for a virtualized Exalogic.  If Exalogic is configured for physical only deployments then EMOC is not required.  The EMOC referred to here is a specialized version that is part of Exalogic Control and not the generic Data Center version that came from SUN.  EMOC traffic runs from its vServers through the Gateway to the clients.  EMOC requires a separate tagged VLAN for security since EMOC can start / stop Exalogic. EMOC traffic load is light. Users can monitor and control Exalogic through the EMOC GUI. Users can also monitor Exalogic through Enterprise Manager Cloud Control 12c GUI by installing the Enterprise Manager Cloud Control EMOC agent.

Enterprise Manager Cloud Control Agents

Enterprise Manager Cloud Control 12c (OEM) is not required as part of an Exalogic system and if used is installed on separate servers outside of Exalogic.   Agents are installed on Exalogic compute nodes or on vServers and collect/send metric data for targets back to OEM OMS. Targets can be OS, Weblogic, Applications … Agent traffic runs through the Gateway switch to the OEM OMS server.  Traffic load can be light to heavy depending on how many targets are monitored and the metric collection frequency. Agent traffic should be on a separate tagged VLAN if it fits into the data center design else it can go on any application VLAN.

Infrastructure Components

Infrastructure Components are Compute Nodes, ZFS Storage Heads, Gateway Switches, Cisco Switch, PDUs, Proxy Servers and Spine Switch.  Access to these components are through OS and/or ILOMs. Access to the OSs and ILOMs are over the Cisco Switch using an untagged / tagged VLAN. Traffic is light.

ZFS Storage

ZFS Storage device provides storage for vServer images, product binaries and application data. It can be connected directly to a Data Center 1 GbE or 10 GbE switch for backup and DR replication. Traffic depends on changes to the storage content and is generally light unless application data changes or vServer images are modified/added frequently.  vServers are not replicated to DR due to network configurations and rather need to be imported into DR.  There are 2 VLAN choices 1) Run on Cisco Switch with untagged/tagged VLAN or 2) run on customer supplied data center 10gBE switch or 1 GbE switch. Recommendation is to connect the ZFS Storage directly to the Data Center Switch for best performance.

Gateway Switch / Client Access Network

 Cisco Switch / Client Access Network

Data Center Switch / Replication Network

IP Addresses

Applications

- Min 1 tagged VLAN

- Each application may have its own tagged VLAN

      - IP’s for Applications as needed, minimum 1 IP per Bond per vServer

EMOC

     - Separate Tagged VLAN

      - 5 IP Addresses (only 1 used today, 4 in reserve)

OEM Agents

     - On a separate VLAN if fits into the data center design else it can go on the Application VLAN

- 1 IP if the agent(s) are on its own VLAN

- 0 IP if the agent(s) are on the Application VLAN

Infrastructure Components

     - Access over an untagged/tagged VLAN

      - IP: 1/8th rack – 20 IPs, ¼ rack – 28 IPs, ½ rack 45 IPs, full rack 75 IPs

ZFS Storage

     - Access over an untagged/tagged VLAN

     - Can connect to external 1 GbE switch or 10 GbE switch

Infrastructure Components IP Addresses Details

1/8th Rack - Includes

4 Compute Nodes   (1 ilom, 1 os)

2 Storage Nodes   (1 ilom, 1 os)

2 Gateway Switches (1)

1 Cisco Switch (1)

2 PDUs (1)

2 Proxy Controllers (virt only) (1)

1 EMOC (virt only) (1)

Total 20 IPs = (4 Compute Nodes * 2 IPs) + (2 ZFS storage * 2 IPs) + (2 Gateway Switches * 1 IP) + (1 Cisco switch * 1 IP) + (2 PDUs * 1 IP) + (2 Proxy Controllers * 1 IP) + (EMOC * 1 IP)

1/4 Rack - Includes

8 Compute Nodes   (1 ilom, 1 os)

2 Storage Nodes   (1 ilom, 1 os)

2 Gateway Switches (1)

1 Cisco Switch (1)

2 PDUs (1)

2 Proxy Controllers (virt only) (1)

1 EMOC (virt only) (1)

Total 28 IPs = (8 Compute Nodes * 2 IPs) + (2 ZFS storage * 2 IPs) + (2 Gateway Switches * 1 IP) + (1 Cisco switch * 1 IP) + (2 PDUs * 1 IP) + (2 Proxy Controllers * 1 IP) + (EMOC * 1 IP)

1/2 Rack - Includes

16 Compute Nodes   (1 ilom, 1 os)

2 Storage Nodes   (1 ilom, 1 os)

2 Gateway Switches (1)

1 Spine Switch (1)

1 Cisco Switch (1)

2 PDUs (1)

2 Proxy Controllers (virt only) (1)

1 EMOC (virt only) (1)

Total 45 IPs = (16 Compute Nodes * 2 IPs) + (2 ZFS storage * 2 IPs) + (2 Gateway Switches * 1 IP) + (1 Spine switch * 1 IP) + (1 Cisco switch * 1 IP) + (2 PDUs * 1 IP) + (2 Proxy Controllers * 1 IP) + (EMOC * 1 IP)

FULL Rack - Includes

30 Compute Nodes   (1 ilom, 1 os)

2 Storage Nodes   (1 ilom, 1 os)

4 Gateway Switches (1)

1 Spine Switch (1)

1 Cisco Switch (1)

2 PDUs (1)

2 Proxy Controllers (virt only) (1)

1 EMOC (virt only) (1)

Total 75 IPs = (30 Compute Nodes * 2 IPs) + (2 ZFS storage * 2 IPs) + (4 Gateway Switches * 1 IP) + (1 Spine switch * 1 IP) + (1 Cisco switch * 1 IP) + (2 PDUs * 1 IP) + (2 Proxy Controllers * 1 IP) + (EMOC * 1 IP)

Documentation:

See here for more details on networking requirements and configuration.

About

Gconti-Oracle

Search

Top Tags
Categories
Archives
« June 2014
SunMonTueWedThuFriSat
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
22
23
24
25
26
27
28
29
30
     
       
Today