Skip to main content

Sub-netting: Divide a network into 2 or more networks

Points to keep in mind:
1. Computers that belong to a subnet are addressed with an identical most-sig bit group in the IP addresses
2. IP is logically divided into NetworkIdentifier/Routingprefix and Restfield/HostIdentifier
3. Routing prefix can be expressed as CIDR (Classless Inter-Domain Routing) notation. Ex. 198.51.100.0/24
Implies
NetworkIdentifier has 24 bits allocated and Rest field has 8 bits allocated
4. A network is characterized by subnet mask or netmask, applied by bitwise AND operation
Ex. For 198.51.100.0/24, the subnet mask is 255.255.255.0
Subnet masks are used to identify the networks
*If 198.51.100.0 is NetworkIdentifier, then 198.51.100.255 is BroadcastIdentifier

For Class A, mask is 255.0.0.0; Class B, mask is 255.255.0.0; Class C, mask is 255.255.255.0

5. Traffic is exchanged between subnets through routers, when the routing prefixes of the source and destination addresses differ; A router serves as a logical boundary between the subnets.


Advantages:
1. Enhances routing efficiency
2. Enhanced control over network
3. Organization's network address space can be organized hierarchically

Source: Wikipedia

Comments

Popular posts from this blog

Essential GCP services for a new age application

Identity and resource management IAM  Identity aware proxy Resource Manager Stackdriver Monitoring Stackdriver Monitoring: Infrastructure and application monitoring Stackdriver Logging: Centralized logging Stackdriver Error Reporting: Application error reporting Stackdriver Trace: Application performance insights (latency) Stackdriver Debugger: Live production debugging Development management Cloud Deployment Manager: Templated Infrastructure deployment Cloud Console: Web based management console Cloud shell: Browser based terminal/CLI Development tools Cloud SDK: CLI for GCP Container registry: Private container registry Container builder: Build/Package container artifacts Cloud source repository: Hosted private git repository Database services Cloud SQL: Managed MySQL and PostgreSQL Cloud BigTable: HBase compatible non-relational DB Cloud Datastore: Horizontally scalable non-relational (ACID) Cloud Spanner: Horizontally scalable relation...

GCP - BigQuery Roles

GCP BigQuery Roles (Quick view)

RAID Levels: Redundant Array of Independent Disks

Standard RAID levels comprise of configurations that employ the techniques of * STRIPING * MIRRORING * PARITY  to create large reliable data stores using general purpose HDDs. Levels are standardized by SNIA (Storage Networking Industry Association) in Common RAID Disk Drive Format (DDF) RAID 0 >> STRIPING (No fail-over, No Redundancy, Total loss of information if disk fails, each disk size will be of smallest disk size in the set of the disks) RAID 1 and its variants >> MIRRORING (Copy of write will be in more than one disk, Redundancy, less performant) RAID 5 >> Distributed PARITY RAID 6 >> Dual PARITY Source:   Wikipedia