|
199 | 199 | href: expressroute-howto-gateway-migration-portal.md
|
200 | 200 | - name: Azure PowerShell
|
201 | 201 | href: expressroute-howto-gateway-migration-powershell.md
|
202 |
| - - name: Traffic Collector |
| 202 | + - name: Traffic collector |
203 | 203 | items:
|
204 | 204 | - name: Overview
|
205 | 205 | href: traffic-collector.md
|
|
213 | 213 | href: design-architecture-for-resiliency.md
|
214 | 214 | - name: High Availability
|
215 | 215 | href: designing-for-high-availability-with-expressroute.md
|
216 |
| - - name: Disaster Recovery |
| 216 | + - name: Disaster recovery |
217 | 217 | items:
|
218 |
| - - name: Private Peering |
| 218 | + - name: Private peering |
219 | 219 | href: designing-for-disaster-recovery-with-expressroute-privatepeering.md
|
220 | 220 | - name: Using VPN as a backup
|
221 | 221 | href: use-s2s-vpn-as-backup-for-expressroute-privatepeering.md
|
|
239 | 239 | href: ../vpn-gateway/site-to-site-vpn-private-peering.md?toc=/azure/expressroute/toc.json
|
240 | 240 | - name: Configure IPsec transport mode for Windows hosts
|
241 | 241 | href: expressroute-howto-ipsec-transport-private-windows.md
|
| 242 | + - name: Network security blog |
| 243 | + href: https://techcommunity.microsoft.com/category/azure-network-security/blog/azurenetworksecurityblog |
242 | 244 | - name: Operational excellence
|
243 | 245 | items:
|
244 | 246 | - name: Plan and manage costs
|
|
285 | 287 | href: ../networking/working-remotely-support.md?toc=/azure/expressroute/toc.json
|
286 | 288 | - name: Hybrid connectivity for remote users
|
287 | 289 | href: work-remotely-support.md
|
288 |
| - - name: Troubleshoot |
289 |
| - items: |
290 |
| - - name: Obtain correlation ID |
291 |
| - href: get-correlation-id.md |
292 |
| - - name: Verifying ExpressRoute connectivity |
293 |
| - href: expressroute-troubleshooting-expressroute-overview.md |
294 |
| - - name: Resolving network performance issues |
295 |
| - href: expressroute-troubleshooting-network-performance.md |
296 |
| - - name: Reset a failed circuit |
297 |
| - href: reset-circuit.md |
298 |
| - - name: Getting ARP tables |
299 |
| - href: expressroute-troubleshooting-arp-resource-manager.md |
300 |
| - - name: Getting ARP tables (Classic) |
301 |
| - href: expressroute-troubleshooting-arp-classic.md |
| 290 | +- name: Troubleshoot |
| 291 | + items: |
| 292 | + - name: Obtain correlation ID |
| 293 | + href: get-correlation-id.md |
| 294 | + - name: Verifying ExpressRoute connectivity |
| 295 | + href: expressroute-troubleshooting-expressroute-overview.md |
| 296 | + - name: Resolving network performance issues |
| 297 | + href: expressroute-troubleshooting-network-performance.md |
| 298 | + - name: Reset a failed circuit |
| 299 | + href: reset-circuit.md |
| 300 | + - name: Getting ARP tables |
| 301 | + href: expressroute-troubleshooting-arp-resource-manager.md |
| 302 | + - name: Getting ARP tables (Classic) |
| 303 | + href: expressroute-troubleshooting-arp-classic.md |
| 304 | + - name: Questions & answers |
| 305 | + href: /answers/tags/225/azure-expressroute |
302 | 306 | - name: Reference
|
303 | 307 | items:
|
304 | 308 | - name: Monitoring data reference
|
|
322 | 326 | href: expressroute-config-samples-routing.md
|
323 | 327 | - name: Router configuration samples for NAT
|
324 | 328 | href: expressroute-config-samples-nat.md
|
325 |
| - - name: Backend Connectivity Interoperability |
| 329 | + - name: Backend connectivity interoperability |
326 | 330 | items:
|
327 |
| - - name: Control Plane Analysis |
| 331 | + - name: Control plane analysis |
328 | 332 | href: ../networking/connectivity-interoperability-control-plane.md?toc=/azure/expressroute/toc.json
|
329 |
| - - name: Networking Blog |
330 |
| - href: https://azure.microsoft.com/blog/category/networking/ |
| 333 | + - name: Networking blog |
| 334 | + href: https://techcommunity.microsoft.com/category/azure/blog/azurenetworkingblog |
331 | 335 | - name: Pricing
|
332 | 336 | href: https://azure.microsoft.com/pricing/details/expressroute/
|
333 | 337 | - name: Pricing calculator
|
|
0 commit comments