Db2 (On Premises and Cloud)

 View Only

Integrating IBM PureData System for Transactions into a data center network

By Ashley Bassman posted Thu September 29, 2022 10:27 PM

  

IBM PureData System for Transactions is an expertly integrated system to help deploy optimized and continuously available mission-critical databases. This paper covers the network requirements for integrating PureData System for Transactions into a data center environment and provides popular sample network topologies.

Developed by: 
Charles Lai Software Developer, Core Engineering Team
Philip Cho Software Developer, Core Engineering Team
Mike Law Test/Network Architect
Ian Hakes Senior Technical Writer

Network environment in IBM PureData System for Transactions

This section provides and introduction to basic networking concepts and describes the networking environment in IBM PureData System for Transactions.

Basic networking concepts
To integrate PureData System for Transactions with your data center, you need an understanding of basic networking concepts. The following concepts are used throughout this paper

Virtual Local Area Network (VLAN): A VLAN is an isolated broadcast domain that is created within a physical switch. Traffic passes from one VLAN to another only if you add a routing device. 

Port VLAN identifier (PVID): A PVID is a default VLAN identifier that is assigned to an access port. VLAN segments designate a PVID to ports that are connected to the VLAN. No-tagging (access) mode: In this mode, raw Ethernet frames are sent without any VLAN tagging information in the frame header. Only one VLAN is supported, and the PVID matches the VLAN for the port.

Tagging (trunk) mode: In this mode, a VLAN identifier is placed in the frame header of a packet when it is sent. Tagged packets can pass traffic across multiple VLANs on a single port.

Link aggregation: Link aggregation combines multiple network links into a single link to increase bandwidth and to improve redundancy. Examples of link aggregation methods are EtherChannel, which is used for static grouping, and Link Aggregation Control Protocol (LACP), which is used for dynamic grouping.

Virtual Link Aggregation Group (VLAG): A VLAG allows for multichassis link aggregation and facilitates active-active uplinks of access layer switches. Using a VLAG with the Spanning Tree Protocol often helps avoid the wasted bandwidth that is associated with links that are blocked by the protocol.

Spanning Tree Protocol: The Spanning Tree Protocol can prevent broadcast loops when multiple paths exist between two points on a network. One example of the protocol is Per VLAN Rapid Spanning Tree (PVRST).

Layer 2: This data link layer is considered the switching layer and is processed by hardware. Layer 2 activities occur in the same broadcast domain or local network. Layer 2 finds adjacent partners by using MAC addresses.

Layer 3: This network layer is considered the routing layer and is processed by software. This layer understands how to traverse multiple networks. Layer 3 finds adjacent partners by using IP addresses.

Domain name server (DNS): A DNS translates domain names to IP addresses and vice versa. The DNS serves all devices that are connected to a data center’s network.

Network Time Protocol (NTP): The Network Time Protocol is used by system software to synchronize the date and time for all devices that are connected to a data center’s network.

Gateway server: A gateway server is a router or proxy server that routes data between a private network and the external network that is connected to the data center.

Best practices

To integrate IBM PureData System for Transactions into a data center network, select one of the sample network topologies in this paper.

Confirm that the reserved IP addresses and VLANs do not conflict with the data center network. Verify that the NTP server is available on the customer management network.

Verify that the DNS is available on both the customer data and management networks. Configure it with both forward and reverse lookup for the host names and IP addresses.

Ensure that the configuration of the core switches corresponds to the network options that you selected in the TDA.

Verify that the ports that you require for IBM PureData System for Transactions are opened on the firewall.
Download the pdf report to learn more! 

#Database
#Db2LUW
#PureDataSystemforAnalytics
#Db2LinuxUNIXWindows
0 comments
14 views

Permalink