1237: fix relative links; ipam pages

Author: Nadia-JSch

docs/infrastructure-management/ipam/dns-records.mdx

@@ -6,7 +6,7 @@ sidebar_position: 8
 import ThemedImage from '@theme/ThemedImage'
 import useBaseUrl from '@docusaurus/useBaseUrl'
 
-Device42 supports A/AAAA, CNAME, MX, and PTR records. Records can be added manually or populated automatically using [DNS discovery](/auto-discovery/setup-dns-autodiscovery).
+Device42 supports A/AAAA, CNAME, MX, and PTR records. Records can be added manually or populated automatically using [DNS discovery](auto-discovery/setup-dns-autodiscovery.mdx).
 
 A/AAAA records are automatically associated with existing IP addresses, or can be associated with new IP addresses when they are created.
 

docs/infrastructure-management/ipam/dns-zones.mdx

@@ -6,7 +6,7 @@ sidebar_position: 7
 import ThemedImage from '@theme/ThemedImage'
 import useBaseUrl from '@docusaurus/useBaseUrl'
 
-DNS zones represent sections of the domain name space managed by a specific nameserver. Zones can be added manually or populated via [DNS discovery](/auto-discovery/setup-dns-autodiscovery).
+DNS zones represent sections of the domain name space managed by a specific nameserver. Zones can be added manually or populated via [DNS discovery](auto-discovery/setup-dns-autodiscovery.mdx).
 
 ## Add a DNS Zone
 

docs/infrastructure-management/ipam/index.mdx

@@ -10,10 +10,10 @@ This section covers how to organize your address space with VRF groups and VLANs
 
 Device42 can discover IP addresses and related network information through several methods:
 
-- [Network SNMP Discovery](/auto-discovery/network-auto-discovery): Discover subnets, IP-to-MAC address relationships, and MAC-to-switch-port connectivity.
-- [Windows and Hyper-V Discovery](/auto-discovery/windows-and-hyper-v-auto-discovery): Discover Windows, Linux, and UNIX devices on your network, including their IP and MAC address details.
-- [Ping Sweep](/auto-discovery/d42-ping-sweep): Keep your IP address records up to date by sweeping address ranges for active hosts.
+- [Network SNMP Discovery](auto-discovery/network-auto-discovery.mdx): Discover subnets, IP-to-MAC address relationships, and MAC-to-switch-port connectivity.
+- [Windows and Hyper-V Discovery](auto-discovery/windows-and-hyper-v-auto-discovery.mdx): Discover Windows, Linux, and UNIX devices on your network, including their IP and MAC address details.
+- [Ping Sweep](auto-discovery/d42-ping-sweep.mdx): Keep your IP address records up to date by sweeping address ranges for active hosts.
 
 ## Import IP Addresses
 
-You can import existing IP address data from Microsoft Excel or CSV spreadsheets. See [Importing Data From Existing Spreadsheets](/getstarted/using-device42/importing-data-from-existing-spreadsheets) for instructions.
+You can import existing IP address data from Microsoft Excel or CSV spreadsheets. See [Importing Data From Existing Spreadsheets](getstarted/using-device42/importing-data-from-existing-spreadsheets.mdx) for instructions.

docs/infrastructure-management/ipam/ip-addresses.mdx

@@ -66,7 +66,7 @@ View the history of changes from the **History (Audit Logs)** tab at the top of
 The **Resource** field links to the Kubernetes cluster that is currently holding that IP.
 
 :::note
-The **Configuration Resource** and **Configuration Resource Item** fields apply only to Kubernetes cloud discovery jobs (see [cloud platforms discovery](/auto-discovery/cloud-auto-discovery/index)) and are populated automatically. Do not populate these fields for a regular IP address.
+The **Configuration Resource** and **Configuration Resource Item** fields apply only to Kubernetes cloud discovery jobs (see [cloud platforms discovery](auto-discovery/cloud-auto-discovery/index.mdx)) and are populated automatically. Do not populate these fields for a regular IP address.
 :::
 
 ### Add an IP Address

docs/infrastructure-management/ipam/subnets.mdx

@@ -8,7 +8,7 @@ import useBaseUrl from '@docusaurus/useBaseUrl'
 
 A subnet can be any Layer 3 network (IPv4 or IPv6) in your organization, and it can optionally be part of a VLAN. All IP addresses in Device42 must belong to a subnet.
 
-You can create nested subnets automatically and relocate manually created subnets as nested subnets. The subnet must be part of a [VRF group](/infrastructure-management/ipam/vrf-groups) to create nested subnets. When you add an overlapping subnet within a VRF group, it is automatically positioned with the correct parent-child relationship.
+You can create nested subnets automatically and relocate manually created subnets as nested subnets. The subnet must be part of a [VRF group](infrastructure-management/ipam/vrf-groups.mdx) to create nested subnets. When you add an overlapping subnet within a VRF group, it is automatically positioned with the correct parent-child relationship.
 
 ## Subnet List Page
 

docs/infrastructure-management/ipam/switch-ports.mdx

@@ -6,7 +6,7 @@ sidebar_position: 10
 import ThemedImage from '@theme/ThemedImage'
 import useBaseUrl from '@docusaurus/useBaseUrl'
 
-Switch ports can be discovered automatically using SNMP network discovery. You can also bulk add switch ports via [switch templates](/infrastructure-management/ipam/switch-templates), or use the [Device42 RESTful APIs](https://api.device42.com/#/IPAM) to programmatically add or edit switch ports.
+Switch ports can be discovered automatically using SNMP network discovery. You can also bulk add switch ports via [switch templates](infrastructure-management/ipam/switch-templates.mdx), or use the [Device42 RESTful APIs](https://api.device42.com/#/IPAM) to programmatically add or edit switch ports.
 
 ## Ports List Page
 
@@ -56,7 +56,7 @@ Switch ports include the following properties:
 - **Asset:** If the port is part of a FEX or similar asset connected to the switch, that association can be made here. You can assign a port to either a module or an asset.
 - **Network Switch 2nd:** For stacked switches, this is the clustered switch. For paired switches, this is the second switch through which the port can be managed.
 
-The **Module**, **Asset**, and **Network Switch 2nd** associations can be configured efficiently using [switch templates](/infrastructure-management/ipam/switch-templates).
+The **Module**, **Asset**, and **Network Switch 2nd** associations can be configured efficiently using [switch templates](infrastructure-management/ipam/switch-templates.mdx).
 
 - **Up:** Whether the port is up.
 - **Up Admin:** Whether the port is administratively up.
@@ -153,7 +153,7 @@ To add a new stacked switch hardware model, navigate to **Infrastructure > Hardw
 
 ## Represent FEX Modules
 
-FEX modules can be added as an asset and then associated with a switch using asset device relations. This is easier to configure using [switch templates](/infrastructure-management/ipam/switch-templates).
+FEX modules can be added as an asset and then associated with a switch using asset device relations. This is easier to configure using [switch templates](infrastructure-management/ipam/switch-templates.mdx).
 
 To add a new asset, navigate to **Resources > All Assets** and click **+ Create**. Name the asset and set **Type** to **Fabric Extender**.