Skip to content

Commit 945374f

Browse files
authored
Merge pull request #811 from ritza-co/edit-955-vrf
955: Edit text formatting, vrf-groups.mdx
2 parents 018e012 + 233d5e2 commit 945374f

1 file changed

Lines changed: 7 additions & 7 deletions

File tree

docs/infrastructure-management/ipam/vrf-groups.mdx

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -8,9 +8,9 @@ import useBaseUrl from '@docusaurus/useBaseUrl'
88

99
## About VRF Groups
1010

11-
For those wondering 'what does VRF stand for', the term "VRF Groups" is short for "Virtual Routing & Forwarding Groups". VRF Groups are often utilized by ISPs and other larger network service providers to organize and track customers' (or their own) logical networks segments, subnets, and VLANs, some of which often overlap with IP ranges in use in other VRF groups -- _but never within the same VRF group_. The reason why is quite simple: There are really only 3 IP address ranges dedicated for use in private networks: 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16; however, there are thousands of end users on these networks that need to route traffic to the internet -- and in a few special cases, to each other. VRF groups to the rescue!
11+
Virtual routing and forwarding groups (VRF groups) are often used by ISPs and other larger network service providers to organize and track customers' (or their own) logical networks segments, subnets, and VLANs, some of which often overlap with IP ranges in use in other VRF groups -- _but never within the same VRF group_. The reason why is quite simple: There are really only three IP address ranges dedicated to private network use: 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16; however, there are thousands of end users on these networks that need to route traffic to the internet -- and in a few special cases, to each other. VRF groups to the rescue!
1212

13-
Most VRF groups are designed so that they can't route between each other by default; however, all are able to route out to a larger network cloud (e.g. _the internet_), thus allowing multiple customers to assign IP addresses to end users on their own networks as they please -- without interfering with one another.
13+
Most VRF groups are designed so that they can't route between each other by default; however, all are able to route out to a larger network cloud (for example, the internet), thus allowing multiple customers to assign IP addresses to end users on their own networks as they please -- without interfering with one another.
1414

1515
<ThemedImage
1616
alt="Device42 VRF Group menu item"
@@ -20,9 +20,9 @@ Most VRF groups are designed so that they can't route between each other by defa
2020
}}
2121
/>
2222

23-
Device42 users can create VRF groups in Device42 to track and manage these overlapping IP Ranges via the main menu, _Network -> VRF Group_. Simply assign networks to VRF groups as appropriate, dividing your individual networks into VRF groups. IP addresses must be unique _per VRF group_, but **you can have overlapping subnet ranges** across VRF groups.
23+
Device42 users can create VRF groups in Device42 to track and manage these overlapping IP Ranges via the main menu, **Network > VRF Group**. Simply assign networks to VRF groups as appropriate, dividing your individual networks into VRF groups. IP addresses must be unique _per VRF group_, but _you can have overlapping subnet ranges_ across VRF groups.
2424

25-
## Add/Edit a VRF Group page
25+
## Add/Edit a VRF Group Page
2626

2727
<ThemedImage
2828
alt="Add new VRF group"
@@ -36,9 +36,9 @@ Device42 users can create VRF groups in Device42 to track and manage these overl
3636
**Description:** Free form text to enter any text.
3737
**Default:** Select this checkbox to have all subnets auto-discovered added to this VRF group automatically (going forward). This option will \*not\* add existing subnets automatically. _Note that subnets are not displayed on the edit page._
3838

39-
If you make the VRF Group the default, then subnets and IP's will be automatically assigned to this default VRF group unless otherwise specified.
39+
If you make the VRF group the default, then subnets and IPs will be automatically assigned to this default VRF group -- unless otherwise specified.
4040

41-
## View an existing VRF Group
41+
## View an Existing VRF Group
4242

4343
<ThemedImage
4444
alt="Select VRF group to view"
@@ -48,4 +48,4 @@ If you make the VRF Group the default, then subnets and IP's will be automatical
4848
}}
4949
/>
5050

51-
The VRF group view page shows all of your VRF Groups.
51+
The VRF Group view page shows all of your VRF Groups.

0 commit comments

Comments
 (0)