Connection failures between a Smart Access Gateway (SAG) device and a switch fall into three categories: physical layer (faulty cable), link layer (disabled port), or network layer (IP misconfiguration or OSPF parameter mismatch). Work through the checks in order until the connection is restored.
Symptoms
One or more of the following indicate a connection failure:
You cannot ping the SAG device ports through the switch.
On the Port Alloc page of the web console, the port indicators are red.
When Open Shortest Path First (OSPF) is configured for dynamic routing, the indicators on the OSPF configuration page are red.
On the Home page of the web console, no route type is configured for the target CIDR block.
Solutions
Step 1: Check the cable
Check whether the cable that connects the SAG device and the switch is faulty. Make sure that the indicators of the ports are on.
Step 2: Check whether the switch port is enabled
Verify that the switch port connected to the SAG device is enabled. Check the port configuration section of your switch management interface or CLI. Enable the port if it is disabled.
Step 3: Verify IP addresses are in the same CIDR block
Confirm that the IP address of the switch port and the IP address of the SAG device port belong to the same CIDR block. A subnet mismatch prevents Layer 3 communication between the two devices.
Step 4: Verify OSPF parameters (if OSPF is configured)
If OSPF is configured for dynamic routing, all parameters on the SAG device port and the directly connected switch port must match. Check each of the following parameters:
| Parameter | Requirement |
|---|---|
| Area ID | Must be identical on both sides of the link |
| Hello Time | Must match on both sides |
| Dead Time | Must match on both sides |
| Authentication Type | Must match on both sides |
| Router ID | Must match on both sides |
| Area Type | Must match on both sides |
Also confirm that all directly connected CIDR blocks have advertised routes in the OSPF configuration.