At this stage, we have an Active Directory with some groups and member users defined; however, now we need to add member computers to the domain. In the next step, we join the domain from our client computer and login with one of the users we have created. Read more »
Open Server Manager.
Select AD DS to verify post installation. Read more »
For centralized management of the users, resources, and group policies we need to promote the Window Server machine from a member server to an Active Directory (AD) Domain Controller (DC). Read more »
Microsoft publishes hardware minimum requirements for the software it sells. For Windows Server 2012, the minimum requirements are:
Processor: Minimum: 1.4 GHz 64-bit processor
Ram: Minimum: 512 MB
Disk Space: Minimum: 32 GB
Other requirements:
DVD drive
Super VGA (800 x 600) or higher-resolution monitor
Keyboard and Microsoft® mouse (or other compatible pointing device)
Internet access
Server 2012 Installation
Insert the server 2012 DVD in the server and to through the following steps:
- Once you get the following message press Enter to boot from the setup.Insert the server 2012 DVD in the server and to through the following steps:
- Wait for a while till the setup loads all necessary files (Depending on your machine, it will take couple of minutes)
- Once the setup files are loaded, the setup will start with the following screen. You can change these to meet your needs (the default values should be fine for now).
- Once you click Next, you can start the installation, click “Install now”.
- You will see the following screen, wait until it finishes loading.
- In the following setup screen, you will see four options. Select Windows Server 2012 DataCenter Evaluation (Server With GUI).
- After you click Next from previous screen, Read the License terms, tick the “I accept the license terms” and click Next.
- Now It will ask you for the drive (or partition) you want to install Windows on. Here we will install it on the one partition we have.
[bs_icon name=”glyphicon glyphicon-exclamation-sign”] NOTE: This will remove the contents on the partition. Either you create a partition to install windows on, or you can test this on a testing machine.
- Now once we picked our partition, clicking on next from previous screen will start the setup. This process might take a while.
- Once the setup is done, it will restart and start your Windows Server 2012 for the first time. It will ask you then to set up a password for the Administrator user.
- The setup will finalize your settings, might take a couple of minutes.
- Once the setup is done, you can log in for the first time to your Windows Server, as the screen says, press Ctrl+Alt+Delete to log in, and use the password you set in the setup process.
- Once you Log in, Windows Server 2012 will show the Server Manager.
To Become Microsoft Certified please Check out the Link;
In this step, you’ll use the Amazon VPC wizard in the Amazon VPC console to create a VPC. The wizard performs the following steps for you: Read more »
Taking a Network+ exam? Follow us on Facebook and ask us about our study group.
The (Open Systems Interconnection) OSI has been developed by International Organization for Standardization (ISO). The OSI model provides a framework for creating and implementing networking standards and devices and describes how network applications on different computers can communicate through the network media. In this post, each of the seven layers of the OSI model will be explained in simple terms.
Layer 1 – Physical layer
Physical layer defines the physical medium itself. It details how cables, connectors and network interface cards are supposed to work and how to send and receive bits. When a networking problem occurs, many networking pros go right to the physical layer to check that all of the cables are properly connected and that the power plug hasn’t been pulled from the router, switch or computer, for example.
Layer 2 – Data Link
Data Link layer defines the format of data on the network. The data link layer is divided into two sub layers: The Media Access Control (MAC) layer and the Logical Link Control (LLC) layer. MAC layer is used for hardware addressing and for controlling the access method. The LLC layer is used for used for flow control and error detection.
Layer 3 – Network
Network Layer defines device addressing, routing, and path determination. Network layer acts as a boundary between the host and the subnet. It deals with routing issues, deadlock and conjestion issues caused by increased number of packet data transfer and decreasing the performance etc.
NFS uses Internetwork Protocol (IP) as its network layer interface. IP is responsible for routing, directing datagrams from one network to another. Even though IP packets are addressed using IP addresses, hardware addresses must be used to actually transport data from one host to another. The Address Resolution Protocol (ARP) is used to map the IP address to the hardware address.
Layer 4 – Transport
Transport layer is responsible for getting the entire message across, establishes and terminates connections between two computers and keeping track of fragmentation and out-of-order packets. Used for flow control and data recovery.
Two transport protocols, Transmission Control Protocol (TCP) and User Datagram Protocol (UDP), sits at the transport layer.
TCP establishes connections between two hosts on the network through ‘sockets’ which are determined by the IP address and port number.
UDP on the other hand provides a low overhead transmission service, but with less error checking.
Layer 5 – Session
This layer defines how to establish, manage and terminate connections between applications.
Layer 6 – Presentation
The Presentation layer defines the data formats. The compression and encryption are also defined at this layer.
Layer 7 – Application
This layer provides network services to the end-users. In general: Layer 7 is the layer that users interact with directly, for example, users browse applications like web browsers (Google Chrome, Firefox, Safari, etc.), Email Applications (Outlook, Thunderbird, etc.), Chat Applications ( WhatsApp, Skype, Viber, etc.) directly are the examples of layer 7 applications.
References: Network World
Want more information on how to become CompTIA Network+ Certified? Learn more!
Taking a Network+ exam? Follow us on Facebook and ask us about our study group.
WiFi is not an acronym but a brand name created by a marketing firm that’s meant to serve as an interoperability seal for marketing efforts. WiFi technology however provides wireless Internet access via the use of radio waves which transmit a signal to a wireless enabled device. You can access this type of connection from up to one hundred feet away and the performance of the connection can vary according to the 802.11 standard being used and the number of devices connecting to the router simultaneously. The standard known as the 802.11 offers a number of different levels of bandwidth usage symbolized by a letter.
The IEEE naming scheme for the standard is a little tough to get used to, and in an effort to make it easier to understand, the Wi-Fi Alliance has come up with some simpler names.
802.11a
The first “letter” following the June 1997 approval of the 802.11 standard, this one provided for operation in the 5GHz frequency which makes it less prone to interference and with data rates up to 54Mbps. It introduced a more complex technique, known as OFDM (orthogonal frequency division multiplexing) for generating the wireless signal.
802.11b
Released in September 1999, it’s most likely that your first home router was 802.11b, which operates in the 2.4GHz frequency and provides a data rate up to 11 Mbps and has a range up to 150 feet. 802.11b components are cheap, but the standard has the slowest maximum speed of all the 802.11 standards.
802.11g
Approved in June 2003, 802.11g was the successor to 802.11b, able to achieve up to 54Mbps rates in the 2.4GHz band, matching 802.11a speed but within the lower frequency range. 802.11g standard uses the same OFDM technology introduced with 802.11a. 802.11g is backward compatible with 802.11b devices: an 802.11b device can connect to an 802.11g access point (but at 802.11b speeds).
802.11n (Wi-Fi 4)
The first standard to specify MIMO (Multiple Input Multiple Output), 802.11n was approved in October 2009 and allows for usage in two frequencies – 2.4GHz and 5GHz, with speeds up to 600Mbps. When you hear wireless LAN vendors use the term “dual-band”, it refers to being able to deliver data across these two frequencies.
802.11ac (Wi-Fi 5)
Current home wireless routers are likely 802.1ac-compliant, and operate in the 5 GHz frequency space. With Multiple Input, Multiple Output (MIMO) – multiple antennas on sending and receiving devices to reduce error and boost speed – this standard supports speeds ranging from 433 Mbps all the way up to 3.46Gbps. Some router vendors include technologies that support the 2.4GHz frequency via 802.11n, providing support for older client devices that may have 802.11b/g/n radios, but also providing additional bandwidth for improved data rates.
Pending Wi-Fi standards
802.11aj
Also known as China Millimeter Wave, this defines modifications to the 802.11ad physical layer and MAC layer to enable operation in the China 59-64GHz frequency band. The goal is to maintain backward compatibility with 802.11ad (60GHz) when it operates in that 59-64GHz range and to operate in the China 45GHz band, while maintaining the 802.11 user experience. Final approval was expected in November 2017.
802.11ak
There are some products in the home-entertainment and industrial-control spaces that have 802.11 wireless capability and 802.3 Ethernet function. The goal of this standard is to help 802.11 media provide internal connections as transit links within 802.1q bridged networks, especially in the areas of data rates, standardized security and quality-of-service improvements. It reached draft status in November 2017.
802.11ax (Wi-Fi 6)
Known as High Efficiency WLAN, 802.11ax aims to improve the performance in WLAN deployments in dense scenarios, such as sports stadiums and airports, while still operating in the 2.4GHz and 5GHz spectrum. The group is targeting at least a 4X improvement in throughput compared to 802.11n and 802.11ac., through moreefficient spectrum utilization. Approval is estimated to be in July 2019.
802.11ay
Also known as Next Generation 60GHz, the goal of this standard is to support a maximum throughput of at least 20Gbps within the 60GHz frequency (802.11ad currently achieves up to 7Gbps), as well as increase the range and reliability. The standard is expected to be approved between September and November 2019.
802.11az
Called Next Generation Positioning (NGP), a study group was formed in January 2015 to address the needs of a “Station to identify its absolute and relative position to another station or stations it’s either associated or unassociated with.” The goals of the group would be to define modifications to the MAC and PHY layers that enable “determination of absolute and relative position with better accuracy with respect to the Fine Timing Measurement (MTM) protocol executing on the same PHY-type, while reducing existing wireless medium use and power consumption, and is scalable to dense deployments.” The current estimate on approval of this standard is March 2021.
802.11ba
Otherwise known as “Wake-Up Radio” (WUR), this isn’t a crazy morning zoo-crew thing, but rather a new technology aimed at extending the battery life of devices and sensors within an Internet of Things network. The goal of the WUR is to “greatly reduce the need for frequent recharging and replacement of batteries while still maintaining optimum device performance.” This is currently expected to be approved in July 2020.
References
actiontec. (n.d.). The evolution of WiFi standards: a look at 802.11a/b/g/n/ac. Retrieved from actiontec.com: https://www.actiontec.com/wifihelp/evolution-wi-fi-standards-look-802-11abgnac/
Cisco. (n.d.). What Is Wi-Fi? Retrieved from www.cisco.com: https://www.cisco.com/c/en/us/products/wireless/what-is-wifi.html
Phillips, G. (n.d.). What Are Wi-Fi Standards? Retrieved from www.makeuseof.com: https://www.makeuseof.com/tag/understanding-common-wifi-standards-technology-explained/
Want more information on how to become CompTIA Network+ Certified? Learn more!
When you buy brand new switches all we need connect the PC to switch port and then PC can talk to each other ; but I can take a Switch like Cisco Switch and create a few VLAN ; such as
(Here is general Idea of VLAN)
VLAN 10 = Publishing
VLAN 20= Accounting
VLAN 30= security
Vlan | Name | Status | Ports |
1 | Default | Active | Fa0/1, Fa0/2, Fa0/3, Fa0/4 Fa0/5, Fa0/6, Fa0/7, Fa0/8Fa0/9, Fa0/10, Fa0/11, Fa0/12
Fa0/13, Fa0/14, Fa0/15, Fa0/16 Fa0/17, Fa0/18, Fa0/19, Fa0/20 Fa0/21, Fa0/22, Fa0/23, Fa0/24 Gig0/1, Gig0/2 |
as we see all the ports are located in default VLAN one ; now I will create
two VLAN and assigned the port as follow
VLAN 2 EGR f0/1,f0/2
VLAN 3 Sales f0/4,F0/5
Here is the result after I have done above
Switch#show vlan brief
Vlan | Name | Status | Ports |
1 | Default | Active | Fa0/3, Fa0/6, Fa0/7, Fa0/8Fa0/9, Fa0/10, Fa0/11, Fa0/12
Fa0/13, Fa0/14, Fa0/15, Fa0/16 Fa0/17, Fa0/18, Fa0/19, Fa0/20 Fa0/21, Fa0/22, Fa0/23, Fa0/24 |
2 | EGR | Active | Fa0/1, Fa0/2 |
3 | sales | Active | Fa0/4 Fa0/5, |
As we see now PC1 can talk to PC2 , and PC4 can talk to PC5 , but PC1 can not ping PC4 or PC5 since I need to have a router between them.
Here is the diagram after I put the router between them. Make sure give ip address of
10.10.10.100 to f0/0
20.20.20.100 to f0/1 and make sure turn on the port ; since by default all the ports are in shut down mode
Now lets look see if from PC1 can ping PC4.
As we see PC1 can not ping PC4 , so lets try to troubleshoot , go to PC1 and see if you can ping the
DG=10.10.10.100
PC>ipconfig
FastEthernet0 Connection:(default port)
Link-local IPv6 Address………: FE80::230:F2FF:FEA7:AB9D
IP Address………………….: 10.10.10.1
Subnet Mask…………………: 255.255.255.0
Default Gateway……………..: 10.10.10.100
PC>ping 10.10.10.100
Pinging 10.10.10.100 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 10.10.10.100:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
As we see we cannot ping the DG
Why ?
Think of OSI Layer model .
Remember IP address is located on layer 3
- Physical Layer
- Data Link Layer ( look at your Switch)
- Network Layer
Now when I look at Switch and I type
Switch#show vlan brief
Vlan | Name | Status | Ports |
1 | Default | Active | Fa0/7, Fa0/8Fa0/9, Fa0/10, Fa0/11, Fa0/12
Fa0/13, Fa0/14, Fa0/15, Fa0/16 Fa0/17, Fa0/18, Fa0/19, Fa0/20 Fa0/21, Fa0/22, Fa0/23, Fa0/24 |
2 | EGR | Active | Fa0/1, Fa0/2, Fa0/3, |
3 | sales | Active | Fa0/4, Fa0/5,Fa0/6, |
Now I should be able to ping from PC1 =10.10.10.1 to Pc4=20.20.20.4
PC>ping 20.20.20.4
Pinging 20.20.20.4 with 32 bytes of data:
Reply from 20.20.20.4: bytes=32 time=1ms TTL=127
Reply from 20.20.20.4: bytes=32 time=1ms TTL=127
Reply from 20.20.20.4: bytes=32 time=1ms TTL=127
Reply from 20.20.20.4: bytes=32 time=0ms TTL=127
Ping statistics for 20.20.20.4:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 1ms, Average = 0ms
Now lets say instead of two VLAN , we have three or four VLAN ; in that case I can not out so many router between each VLAN , so cisco came with idea of Multi layer switch ( Cisco 3550, 3560 ,3575 and above) that allows you to be a layer 2 (switch) and layer 3 device (act as router) in that case we do not need a router ; which is but a Cisco 3550 and above then I can route packet from one vlan to another vlan. ( CCNA/CCNP concept)
Here how it looks like at Cisco Switch; when you buy brand new Switch (without configuration)
Want more information on how to become CompTIA Network+ Certified? Learn more!
(Domain Name System) The Internet’s system for converting alphabetic names into numeric IP addresses. For example, when a Web address (URL) is typed into a browser, DNS servers return the IP address of the Web server associated with that name. In this made-up example, the DNS converts the URL www.company.com into the IP address 204.0.8.51. Without DNS, you would have to type the series of four numbers and dots into your browser to retrieve the website, which you actually can do.
A Hierarchy of Servers
The DNS system is a hierarchy of duplicated database servers worldwide that begin with the “root servers” for the top-level domains (.com, .net, .org, etc.). The root servers point to the “authoritative” servers located in ISPs, as well as in large companies, that turn the names into IP addresses; the process known as “name resolution.” Using our www.company.com example, COMPANY.COM is the domain name, and WWW is the hostname. The domain name is the organization’s identity on the Web, and the hostname is the name of the Web server within that domain
Want more information on how to become CompTIA Network+ Certified? Learn more!
From Wikipedia
Want more information on how to become CompTIA Network+ Certified? Learn more!
The NAT Instance
- Install the NAT instance from Community AMI
- When creating a NAT instance , make sure Disable source/destination check
- Nat Instance must be in public subnet
- There must be route out of private subnet and pointed to NAT instance
- You Need to have a Security group for NAT instance
- The amount of traffic that NAT instance supports depends on the instance size
NAT Gateways
- It is New ,
- Preferred by Enterprise
- Scale automatically up to 10Gbps
- No need to patch ( Amazon will take care of it)
- No need to have a security group
- Automatically assigned a public Ip address
- Remember to update your Route table
- No Need to disable Source/Destination checks
Want more information on how to become Amazon AWS Certified? Learn more!
From Wikipedia
Type |
Description |
Function |
A | Address Record | Returns a 32-bit IPv4 address, most commonly used to map hostnames to an IP address of the host,but it is also used for DNSBLs, storing subnet masks in RFC 1101, etc. |
CNAME | Canonical Name Record | Alias of one name to another: the DNS lookup will continue by retrying the lookup with the new name. |
MX | Mail Exchange Record | Maps a domain name to a list of message transfer agents for that domain |
AAAA | IPv6 Address Record | Returns a 128-bit IPv6 address, most commonly used to map hostnames to an IP address of the host. |
TXT | Text Record | Originally for arbitrary human-readable text in a DNS record. Since the early 1990s, however, this record more often carriesmachine-readable data, such as specified by RFC 1464, opportunistic encryption, Sender Policy Framework, DKIM, DMARC, DNS-SD, etc. |
PTR | Pointer Record | Pointer to a canonical name. Unlike a CNAME, DNS processing stops and just the name is returned. The most common use is for implementing reverse DNS lookups, but other uses include such things as DNS-SD. |
SRV | Service locator | Generalized service location record, used for newer protocols instead of creating protocol-specific records such as MX. |
SPF | Sender Policy Framework | SPF(99) (from RFC 4408) was specified as part of the Sender Policy Framework protocol as an alternative to storing SPF data in TXT records, using the same format. It was later found that the majority of SPF deployments lack proper support for this record type, and support for it was discontinued in RFC 7208. |
NS | Name Server record | Delegates a DNS zone to use the given authoritative name servers |
SOA | Start of [a zone of] Authority Record | Specifies authoritative information about a DNS zone, including the primary name server, the email of the domain administrator, the domain serial number, and several timers relating to refreshing the zone. |
Want more information on how to become Amazon AWS Certified? Learn more!
From Wikipedia
Type |
Description |
Function |
A | Address Record | Returns a 32-bit IPv4 address, most commonly used to map hostnames to an IP address of the host,but it is also used for DNSBLs, storing subnet masks in RFC 1101, etc. |
CNAME | Canonical Name Record | Alias of one name to another: the DNS lookup will continue by retrying the lookup with the new name. |
MX | Mail Exchange Record | Maps a domain name to a list of message transfer agents for that domain |
AAAA | IPv6 Address Record | Returns a 128-bit IPv6 address, most commonly used to map hostnames to an IP address of the host. |
TXT | Text Record | Originally for arbitrary human-readable text in a DNS record. Since the early 1990s, however, this record more often carriesmachine-readable data, such as specified by RFC 1464, opportunistic encryption, Sender Policy Framework, DKIM, DMARC, DNS-SD, etc. |
PTR | Pointer Record | Pointer to a canonical name. Unlike a CNAME, DNS processing stops and just the name is returned. The most common use is for implementing reverse DNS lookups, but other uses include such things as DNS-SD. |
SRV | Service locator | Generalized service location record, used for newer protocols instead of creating protocol-specific records such as MX. |
SPF | Sender Policy Framework | SPF(99) (from RFC 4408) was specified as part of the Sender Policy Framework protocol as an alternative to storing SPF data in TXT records, using the same format. It was later found that the majority of SPF deployments lack proper support for this record type, and support for it was discontinued in RFC 7208. |
NS | Name Server record | Delegates a DNS zone to use the given authoritative name servers |
SOA | Start of [a zone of] Authority Record | Specifies authoritative information about a DNS zone, including the primary name server, the email of the domain administrator, the domain serial number, and several timers relating to refreshing the zone. |
Want more information on how to become CompTIA Network+ Certified? Learn more!
Source By: <docs.aws.amazon.com>
Getting Started with Elastic Load Balancing
This tutorial provides a hands-on introduction to Application Load Balancers through the AWS Management Console, a web-based interface. To create your first Application Load Balancer, complete the following steps.
Tasks
- Before You Begin
- Step 1: Select a Load Balancer Type
- Step 2: Configure Your Load Balancer and Listener
- Step 3: Configure a Security Group for Your Load Balancer
- Step 4: Configure Your Target Group
- Step 5: Register Targets with Your Target Group
- Step 6: Create and Test Your Load Balancer
- Step 7: Delete Your Load Balancer (Optional)
Before You Begin
- Decide which two Availability Zones you will use for your EC2 instances. Verify that your virtual private cloud (VPC) has at least one public subnet in each of these Availability Zones.
- Launch at least one EC2 instance in each Availability Zone. For this exercise, you can simply use the public subnets. Be sure to install a web server, such as Apache or Internet Information Services (IIS), on each EC2 instance.
- Ensure that the security group for your EC2 instances allows HTTP access on port 80. To test the web server, copy the DNS name of the instance into the address field of an Internet-connected web browser and verify that the browser displays the default page of the web server.
Step 1: Select a Load Balancer Type
Elastic Load Balancing supports two types of load balancers: Application Load Balancers and Classic Load Balancers. For this tutorial, you create an Application Load Balancer.
To create an Application Load Balancer
- Open the Amazon EC2 console at https://console.aws.amazon.com/ec2/.
- On the navigation bar, choose a region for your load balancer. Be sure to select the same region that you used for your EC2 instances.
- On the navigation pane, under LOAD BALANCING, choose Load Balancers.
- Choose Create Load Balancer.
- Choose Application Load Balancer, and then choose Continue.
Step 2: Configure Your Load Balancer and Listener
On the Configure Load Balancer page, complete the following procedure.
To configure your load balancer and listener
- For Name, type a name for your load balancer.The name of your Application Load Balancer must be unique within your set of Application Load Balancers for the region, can have a maximum of 32 characters, can contain only alphanumeric characters and hyphens, and must not begin or end with a hyphen.
- For Scheme, keep the default value, internet-facing.
- For IP address type, select ipv4 if your instances support IPv4 addresses or dualstack if they support IPv4 and IPv6 addresses.
- For Listeners, keep the default, which is a listener that accepts HTTP traffic on port 80.
- For Availability Zones, select the VPC that you used for your EC2 instances. For each of the two Availability Zones that contain your EC2 instances, select the Availability Zone and then select the public subnet for that Availability Zone.
- Choose Next: Configure Security Settings.
- For this tutorial, you are not using a secure listener. Choose Next: Configure Security Groups.
Step 3: Configure a Security Group for Your Load Balancer
The security group for your load balancer must allow it to communicate with registered targets on both the listener port and the health check port. The console can create security groups for your load balancer on your behalf, with rules that specify the correct protocols and ports.
Note
If you prefer, you can create and select your own security group instead.
On the Configure Security Groups page, complete the following procedure to have Elastic Load Balancing create a security group for your load balancer on your behalf.
To configure a security group for your load balancer
- Choose Create a new security group.
- Type a name and description for the security group, or keep the default name and description. This new security group contains a rule that allows traffic to the load balancer listener port that you selected on the Configure Load Balancer page.
- Choose Next: Configure Routing.
Step 4: Configure Your Target Group
Create a target group, which is used in request routing. The default rule for your listener routes requests to the registered targets in this target group. The load balancer checks the health of targets in this target group using the health check settings defined for the target group. On the Configure Routing page, complete the following procedure.
To configure your target group
- For Target group, keep the default, New target group.
- For Name, type a name for the new target group.
- Keep Protocol as HTTP and Port as 80.
For Health checks, keep the default protocol and ping path.
- Choose Next: Register Targets.
Step 5: Register Targets with Your Target Group
On the Register Targets page, complete the following procedure.
To register targets with the target group
- For Instances, select one or more instances.
- Keep the default port, 80, and choose Add to registered.
- If you need to remove an instance that you selected, for Registered instances, select the instance and then choose Remove.
- When you have finished selecting instances, choose Next: Review.
Step 6: Create and Test Your Load Balancer
Before creating the load balancer, review the settings that you selected. After creating the load balancer, verify that it’s sending traffic to your EC2 instances.
To create and test your load balancer
- On the Review page, choose Create.
- After you are notified that your load balancer was created successfully, choose Close.
- On the navigation pane, under LOAD BALANCING, choose Target Groups.
- Select the newly created target group.
- On the Targets tab, verify that your instances are ready. If the status of an instance is initial, it’s probably because the instance is still in the process of being registered, or it has not passed the minimum number of health checks to be considered healthy. After the status of at least one instance is healthy, you can test your load balancer.
- On the navigation pane, under LOAD BALANCING, choose Load Balancers.
- On the Description tab, copy the DNS name of the load balancer (for example, my-load-balancer-1234567890.us-west-2.elb.amazonaws.com). Paste the DNS name into the address field of an Internet-connected web browser. If everything is working, the browser displays the default page of your server.
Step 7: Delete Your Load Balancer (Optional)
As soon as your load balancer becomes available, you are billed for each hour or partial hour that you keep it running. When you no longer need a load balancer, you can delete it. As soon as the load balancer is deleted, you stop incurring charges for it. Note that deleting a load balancer does not affect the targets registered with the load balancer. For example, your EC2 instances continue to run.
To delete your load balancer
- Open the Amazon EC2 console at https://console.aws.amazon.com/ec2/.
- On the navigation pane, under LOAD BALANCING, choose Load Balancers.
- Select the load balancer, and then choose Actions, Delete.
- When prompted for confirmation, choose Yes, Delete.
To Become AWS Certified please Check out this link;
Source By: <docs.aws.amazon.com>
What Is Elastic Load Balancing?
Elastic Load Balancing distributes incoming application traffic across multiple EC2 instances, in multiple Availability Zones. This increases the fault tolerance of your applications.
The load balancer serves as a single point of contact for clients, which increases the availability of your application. You can add and remove instances from your load balancer as your needs change, without disrupting the overall flow of requests to your application. Elastic Load Balancing scales your load balancer as traffic to your application changes over time, and can scale to the vast majority of workloads automatically.
You can configure health checks, which are used to monitor the health of the registered instances so that the load balancer can send requests only to the healthy instances. You can also offload the work of encryption and decryption to your load balancer so that your instances can focus on their main work.
Features of Elastic Load Balancing
Elastic Load Balancing supports two types of load balancers: Application Load Balancers and Classic Load Balancers. Choose the load balancer type that meets your needs.
Feature | Classic Load Balancer | Application Load Balancer |
---|---|---|
Protocols | HTTP, HTTPS, TCP, SSL | HTTP, HTTPS |
Platforms | EC2-Classic, EC2-VPC | EC2-VPC |
Sticky sessions (cookies) | ✔ | load balancer generated |
Back-end server authentication | ✔ | |
Back-end server encryption | ✔ | ✔ |
Idle connection timeout | ✔ | ✔ |
Connection draining | ✔ | ✔ |
Cross-zone load balancing † | ✔ | Always enabled |
Health checks † † | ✔ | Improved |
CloudWatch metrics | ✔ | Improved |
Access logs | ✔ | Improved |
Path-based routing | ✔ | |
Route to multiple ports on a single instance | ✔ | |
HTTP/2 support | ✔ | |
Websockets support | ✔ | |
Load balancer deletion protection | ✔ |
† Cross-zone load balancing is always enabled for an Application Load Balancer. For a Classic Load Balancer, it is disabled by default, but can be enabled and disabled as needed.
† † For an Application Load Balancer, you can specify the HTTP codes that indicate a successful health check response. An Application Load Balancer returns improved information about the cause of health check failures.
Accessing Elastic Load Balancing
You can create, access, and manage your load balancers using any of the following interfaces:
- AWS Management Console— Provides a web interface that you can use to access Elastic Load Balancing.
- AWS Command Line Interface (AWS CLI) — Provides commands for a broad set of AWS services, including Elastic Load Balancing, and is supported on Windows, Mac, and Linux.
- AWS SDKs — Provides language-specific APIs and takes care of many of the connection details, such as calculating signatures, handling request retries, and error handling.
- Query API— Provides low-level API actions that you call using HTTPS requests. Using the Query API is the most direct way to access Elastic Load Balancing, but it requires that your application handle low-level details such as generating the hash to sign the request, and error handling. For more information, see the following:
- Application Load Balancers — API version 2015-12-01
- Classic Load Balancers — API version 2012-06-01
Related Services
Elastic Load Balancing works with the following services to improve the availability and scalability of your applications.
- Amazon EC2 — Virtual servers that run your applications in the cloud. You can configure your load balancer to route traffic to your EC2 instances.
- Amazon ECS — Enables you to run, stop, and manage Docker containers on a cluster of EC2 instances. You can configure your load balancer to route traffic to your containers.
- Auto Scaling — Ensures that you are running your desired number of instances, even if an instance fails, and enables you to automatically increase or decrease the number of instances as the demand on your instances changes. If you enable Auto Scaling with Elastic Load Balancing, instances that are launched by Auto Scaling are automatically registered with the load balancer, and instances that are terminated by Auto Scaling are automatically de-registered from the load balancer.
- Amazon CloudWatch — Enables you to monitor your load balancer and take action as needed.
- Amazon Route 53 — Provides a reliable and cost-effective way to route visitors to websites by translating domain names (such as www.example.com) into the numeric IP addresses (such as 192.0.2.1) that computers use to connect to each other. AWS assigns URLs to your resources, such as load balancers. However, you might want a URL that is easy for users to remember. For example, you can map your domain name to a load balancer.
To Become AWS Certified please Check out this link;
In this exercise, you’ll create a VPC and subnet, and launch a public-facing instance into your subnet. Read more »
Source By: <docs.aws.amazon.com>
Amazon Virtual Private Cloud (Amazon VPC) enables you to launch Amazon Web Services (AWS) resources into a virtual network that you’ve defined. Read more »
If you’ve already signed up for Amazon Web Services (AWS), you can start using Amazon EC2 immediately. You can open the Amazon EC2 console, click Launch Instance, and follow the steps in the launch wizard to launch your first instance. Read more »
Amazon Elastic Compute Cloud (Amazon EC2) provides scalable computing capacity in the Amazon Web Services (AWS) cloud. Using Amazon EC2 eliminates your need to invest in hardware up front, so you can develop and deploy applications faster. Read more »


Now I will do small Lab:
R4=10.10.10.4
R10=10.10.10.10 connected via LAN link
Read more »
Follow @ASM_Educational
Source Logical Operations
Get our complete tutorial in PDF
Related Links:
Configuring IPv4
Configuring IPv6
Want more information on how to become Cisco CCNA Certified? Learn more!
Join our Cisco CCNA facebook study group!
Follow @ASM_Educational
Source Logical Operations
Get our complete tutorial in PDF
Configuring IPv6
- Overview of IPv6
- Implement IPv6 Addressing
- Implement IPv6 and IPv4
- Transition from IPv4 to IPv6
Follow @ASM_Educational
Source Logical Operations
Get our complete tutorial in PDF
Configuring IPv6
- Overview of IPv6
- Implement IPv6 Addressing
- Implement IPv6 and IPv4
- Transition from IPv4 to IPv6
Follow @ASM_Educational
Source Logical Operations
Get our complete tutorial in PDF
Configuring IPv4
- Overview of the TCP/IP Protocol Suite
- Describe IPv4 Addressing
- Implement Subnetting and Supernetting
- Configure and Troubleshoot IPv4
Description of OSI layers
The recommendation X.200 describes seven layers, labeled 1 to 7. Layer 1 is the lowest layer in this model.

The Trunk port between the router and switch had to be manually configured using sub-interfaces. Note, however, that the DATA vlan traffic and the phone VOICE vlan traffic for each host is carried over the same link (multiple vlan traffic over the same port). Read more »

Build the following topology in packet tracer. After testing our configuration, we will deploy on devices.
Read more »

Layer 3 Switch
Now that we have seen how a “router on a stick” works, we can introduce the Layer 3 switch. In the “router on a stick” topology, what if we could bring the router inside the switch? Read more »

Using DHCP Server with Inter-Vlan Routing (Router on stick)
On Last Video we talked about the router on stick that is we made sure that client from Network 10.10.10.0 can communicate with Network 20.20.20.0

Setting up VLAN’s
On a new switch, all the ports are in VLAN 1 by default. We just plug in the Ethernet cables and the devices can communicate. Furthermore, all the ports are in the up/up (administratively up) mode. Read more »
In order to make troubleshooting as easy as possible, you should always use an organized methodology. Using simple best practices will do just that. Read more »
In order to keep your Linux system running smoothly, it is vital to maintain it properly.
Read more »
As with any other operating system, administration efforts are necessary for any linux system. These include the following tasks: Read more »
Configuring your Xwindows
No matter what desktop environment you chose, it is most likely that it will use the Xwindows architecture. Read more »
Media
Linux installation can be done using a variety of different media. Each installation method has different pros and cons depending on the environment you have. Here are some examples: Read more »
Linux Uses
Linux is a pretty flexible operating system. Although it has got a lot of credibility over the years as a stable server platform, it is also an excellent desktop platform. Databases, mail servers as well as many appliances can be installed. Read more »
Linux is a 32 bit open source operating system. It is based on the very popular Unix operating system and it’s code is freely available (thus explaining the “open source” label as opposed to closed source where the code is not available freely). Read more »
Amazon Simple Storage Service is storage for the Internet. It is designed to make web-scale computing easier for developers. Read more »