What is Static Routing ?
As recently expressed, static courses are generally utilized in networks today. Static courses are utilized in organizations, all things considered, and are utilized alongside a dynamic directing convention. Therefore, a decent comprehension of static courses is a necessity for carrying out steering on an organization.
Arrive at Remote Networks (2.1.1.1)
A switch can find out about remote organizations in one of two ways:
Physically: Remote organizations are physically placed into the course table utilizing static courses.
Progressively: Remote courses are consequently mastered utilizing a dynamic directing convention.
Figure 2-1 gives an example situation of static directing. Figure 2-2 gives an example situation of dynamic directing utilizing EIGRP.
Figure 2-1
Figure 2-1 Static and Default Route Scenario
Figure 2-2
Figure 2-2 Dynamic Routing Scenario
An organization head can physically design a static course to arrive at a particular organization. Dissimilar to a dynamic directing convention, static courses are not consequently refreshed and should be physically reconfigured any time the organization geography changes. A static course doesn't change until the executive physically reconfigures it.
Why Use Static Routing? (2.1.1.2)
Static directing gives a few benefits over unique steering, including:
Static courses are not publicized over the organization, bringing about better security.
Static courses utilize less data transmission than dynamic directing conventions, as switches don't trade courses.
No CPU cycles are utilized to work out and impart courses.
The way a static course uses to send information is known.
Static steering has the accompanying impediments:
Introductory setup and upkeep is tedious.
Setup can be mistake inclined, particularly in huge organizations.
Overseer intercession is expected to keep up with changing course data.
Doesn't scale well with developing organizations; support becomes unwieldy.
Requires total information in general organization for legitimate execution.
In Table 2-1, dynamic and static steering highlights are thought about. Notice that the upsides of one strategy are the detriments of the other.
Table 2-1 Dynamic Routing Versus Static Routing
Dynamic Routing
Static Routing
Arrangement Complexity
For the most part autonomous of the organization size
Increments with the organization size
Geography Changes
Consequently adjusts to geography changes
Chairman intercession required
Scaling
Reasonable for basic and complex geographies
Reasonable for basic geographies
Security
Less secure
Safer
Asset Usage
Utilizes CPU, memory, interface data transmission
No additional assets required
Consistency
Course relies upon the ongoing geography
Course to objective is generally something very similar
Static courses are valuable for more modest organizations with only one way to an external organization. They likewise give security in a bigger organization for specific sorts of traffic or connections to different organizations that need more control. It is essential to comprehend that static and dynamic directing are not fundamentally unrelated. Rather, most organizations utilize a mix of dynamic directing conventions and static courses. This might bring about the switch having numerous ways to an objective organization through static courses and progressively educated courses. In any case, the regulatory distance (AD) of a static course is 1. Consequently, a static course will overshadow all progressively scholarly courses.
When to Use Static Routes (2.1.1.3)
Static steering has three essential purposes:
Giving simplicity of steering table support in more modest organizations that are not supposed to fundamentally develop.
Steering to and from stub organizations. A stub network is an organization gotten to by a solitary course, and the switch has just a single neighbor.
Utilizing a solitary default course to address a way to any organize that doesn't have a more unambiguous coordinate with one more course in the steering table. Default courses are utilized to send traffic to any objective past the following upstream switch.
Figure 2-3 shows an illustration of a stub network association and a default course association. Notice in the figure that any organization appended to R1 would just have one method for arriving at different objections, whether to networks connected to R2, or to objections past R2. This implies that network 172.16.3.0 is a stub organization and R1 is a stub switch. Running a steering convention somewhere in the range of R2 and R1 is a misuse of assets.
Figure 2-3
Figure 2-3 Stub Networks and Stub Routers
In this model, a static course can be designed on R2 to arrive at the R1 LAN. Moreover, in light of the fact that R1 has just a single method for conveying non-nearby traffic, a default static course can be designed on R1 to highlight R2 as the following bounce for any remaining organizations.
common2.jpg Activity 2.1.1.4: Identify the Advantages and Disadvantages of Static Routing
Go to the internet based course to play out this training action.
Note
The video and intuitive substance depicted in this part are simply accessible to understudies signed up for related Cisco Networking Academy courses and not in this example.
Static Route Applications (2.1.2.1)
Static courses are most frequently used to interface with a particular organization or to give a Gateway of Last Resort for a stub organization. They can likewise be utilized to:
Decrease the quantity of courses publicized by summing up a few coterminous organizations as one static course
Make a reinforcement course in the event that an essential course connect falls flat
The accompanying kinds of IPv4 and IPv6 static courses will be talked about:
Standard static course
Default static course
Outline static course
Drifting static course
Standard Static Route (2.1.2.2)
Both IPv4 and IPv6 support the arrangement of static courses. Static courses are helpful while interfacing with a particular remote organization.
Figure 2-4 demonstrates the way that R2 can be designed with a static course to arrive at the stub network 172.16.3.0/24.
Figure 2-4
Figure 2-4 Connecting to a Stub Network
NOTE
The model is featuring a stub organization, however as a matter of fact, a static course can be utilized to interface with any organization.
