Troubleshooting MCR When Down or Unavailable
If your Megaport Cloud Router (MCR) is down, the root cause could be the status of your attached Ports or VXCs, the BGP configuration, or the interface settings. Step through these troubleshooting actions to isolate the issue.
You can verify MCR status from the Megaport Portal. On the Services page in the Portal, find the MCR and mouse over its icon. A message displays the status of the service. (The color of the icon also indicates the service status.)
|Perform a pingA ping test transmits data packets to a specific IP address and either confirms or denies connectivity between IP-networked devices. test from the MCR
|Run ping tests from MCR to the following destinations:
|Verify Layer 2 connectivity (ARP)
|Confirm that the IP address of the MCR is mapped correctly to the MAC address in the Address Resolution Protocol (ARP) table. For example, enter show ip arp. Layer 2 controls the flow of data between nodes on WAN or LAN segments, and is also responsible for detecting and possibly correcting Layer 1The electrical and mechanical layer of the OSI model that conveys the bit stream (electrical impulse, light or radio signal) through the network. L1 provides the hardware means of sending and receiving data on a carrier. errors. Layer 2The data link layer of the OSI model. L2 provides node-to-node data transfer (a link between two directly connected nodes). Most Megaport Virtual Cross Connects (VXCs) operate at L2. connectivity issues can affect the functionality of your VXCs, which connect to your MCR. When connecting to a Cloud Service Provider (CSP), ensure that the VLAN configuration details are correct. Use particular caution when connecting to Azure, as you will be using Q-in-Q802.1Q tunneling (also known as Q-in-Q or 802.1ad) is a technique used by OSI Layer 2 providers for customers. 802.1ad provides for both an inner and an outer tag whereby the outer (S-tag) can be removed to expose the inner (C-tag) tags that segment the data.. For additional guidance, reach out to your Account Manager and request a meeting with a Megaport Solution Architect.
|Verify ACL/FW rules on your devices
|During some troubleshooting sessions where the circuit is up but you cannot ping between Layer 3 endpoints, there might be a firewall or ACLAccess control list.
A list of rules that either allow access to a computer environment or deny it. in between.
On many devices, it is possible to set an interface to filter or ignore ICMP requests on many devices, leading to a failed ping, while other traffic may pass without problems.
It is essential to know the ping source, its destination, the path, and any intermediate devices it traverses. Megaport requires customers to provide a network diagram and the tracerouteA diagnostic tool that examines how data moves through the internet to determine if a destination is reachable. result before investigation and troubleshooting. Inaccurate information may lead to wrong troubleshooting results and inappropriate solutions.
Perform these checks before opening a ticket with Megaport support:
If the troubleshooting actions do not resolve your issue, contact support. Before contacting support for assistance, provide details of all troubleshooting steps. For example, if loops were placed, note where they were located and their direction.
When a field service technician is needed onsite at the data center, see Customer Field Services for details.