Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All

    SSR Cluster Planning Worksheets

    Use the worksheet shown in Table 1 to plan your SSR Starter Kit cluster. The worksheet allows you to record IP addresses and node IDs for the four C Series Controllers. Record the node IDs after the SRC software has assigned them. If you use more nodes, see the worksheet in Table 2 for the Expansion Kit.

    Table 1: SSR Starter Kit Cluster Worksheet

    Nodes and Hosted Components

    Node IP Address

    Bonded IP Address

    Node ID Assigned to Component

    Client node hosting:

    • Database front-end component (SQL)
    • Management server component
    • Client component
       

    Client node hosting:

    • Database front-end component (SQL)
    • Management server component
    • Client component
       

    Data node hosting:

    • back-end data component
       

    Data node hosting:

    • back-end data component
       

    A cluster can include either two or four data nodes, up to three management servers and up to twenty-four client nodes, each hosting SSR client components such as the SIC, SAE and so on. The worksheet in Table 2 provides locations for you to record the IP addresses and node IDs for this maximum configuration.

    Table 2: Expanded SSR Cluster Planning Worksheet

    Product Name

    Nodes and Hosted Components

    Node IP Address

    Bonded IP Address

    Node ID Assigned to Component

    Data Node Expansion Kit

    Data node hosting:

    • Back-end data component
       

    Data node hosting:

    • Back-end data component
       

    Management Server Expansion Kit

    Management server component

       

    Additional client nodes

     

    Client node hosting:

    • Database front-end component
    • Client component
       

    Client node hosting:

    • Database front-end component
    • Client component
       

    Client node hosting:

    • Database front-end component
    • Client component
       

    Client node hosting:

    • Database front-end component
    • Client component
       

    Client node hosting:

    • Database front-end component
    • Client component
       

    Client node hosting:

    • Database front-end component
    • Client component
       

    Client node hosting:

    • Database front-end component
    • Client component
       

    Client node hosting:

    • Database front-end component
    • Client component
       

    Client node hosting:

    • Database front-end component
    • Client component
       

    Client node hosting:

    • Database front-end component
    • Client component
       

    Client node hosting:

    • Database front-end component
    • Client component
       

    Client node hosting:

    • Database front-end component
    • Client component
       

    Client node hosting:

    • Database front-end component
    • Client component
       

    Client node hosting:

    • Database front-end component
    • Client component
       

    Client node hosting:

    • Database front-end component
    • Client component
       

    Client node hosting:

    • Database front-end component
    • Client component
       

    Client node hosting:

    • Database front-end component
    • Client component
       

    Client node hosting:

    • Database front-end component
    • Client component
       

    Client node hosting:

    • Database front-end component
    • Client component
       

    Client node hosting:

    • Database front-end component
    • Client component
       

    Client node hosting:

    • Database front-end component
    • Client component
       

    Client node hosting:

    • Database front-end component
    • Client component
       

    Published: 2014-06-19