Configuring Outlet Sequencing with SynLink SP and netBooter DX PDUs

Synaccess SynLink SP and netBooter DX PDUs support sequenced and timed outlet operations. This feature is especially useful when you need to reboot outlets in a specific order, with delays between each step—either manually or through automation.

For example, if your network stack freezes, you may want to reboot the modem first, then the router, then downstream switches or other devices, with delays between each reboot to allow time for recovery.

There are two main ways to accomplish this:

1. Outlet Grouping
2. Individually Configured AutoPing Events with varying failure interval conditions

‍

‍

Option 1: Outlet Grouping

Outlet grouping allows you to predefine a set of outlets that will be rebooted in sequence, with a configurable delay between each step.

Example Configuration:

• Outlet 1: Modem
• Outlet 2: Router
• Outlet 3: Switch
  
  

You could create an outlet group called “Core Network Connectivity Equipment” with a 60-second delay between each reboot.

If you trigger a reboot of this group (manually or via automation such as AutoPing), the following sequence occurs:

1. Reboot Outlet 1 (Modem)
2. Wait 60 seconds
3. Reboot Outlet 2 (Router)
4. Wait 60 seconds
5. Reboot Outlet 3 (Switch)
   
   

Advantages:

• Compact configuration of all critical devices in the right order, reusable in both manual and automated settings
• Easy to trigger manually or automatically.
  
  

Limitations:

• All devices in the group will reboot, even if only one device is causing the issue.
  ‍

‍

Option 2: Individual Event Triggers

If you want more granular control—for example, rebooting one device at a time only if connectivity is not restored—you can use individual AutoPing events with different failure timers.

Scenario Example:

• Outlet 1: Modem
• Outlet 2: Router
• Outlet 3: Switch

‍

Desired Logic:

• If the network is down for 60 seconds → Reboot Modem.
• If still down after 180 seconds total → Reboot Router.
• If still down after 240 seconds total → Reboot Switch.
  
  

Configuration Steps (CMP):

1. Navigate to the Devices page.
   
2. Select the PDU and open the Alerts tab.
   
3. Click Create New Alert Event.
   
4. Configure three separate events, one per outlet, all using the same IP address to ping.
   
   

Example Settings:

• Event 1: Fail after 60 pings → Reboot Outlet 1 (Modem).
  
• Event 2: Fail after 180 pings → Reboot Outlet 2 (Router).
  
• Event 3: Fail after 240 pings → Reboot Outlet 3 (Switch).

(Note that by default, 1 ping happens per second)

‍

Behavior:

• If the modem reboot restores connectivity, later events (router/switch) will not trigger.
  
• If the modem does not fix the issue, subsequent events will continue firing as downtime persists.

‍‍

‍Configuring Outlet Groups in CMP

CMP now supports outlet grouping, though ordering is currently based on outlet number (1, 2, 3, etc.). Ordering customization will be released in September 2025. The local PDU UI already supports outlet reordering.

Example Setup:

• Outlets: Modem (1), Router (2), Switch (3)
  
• Action: Reboot all three outlets when connectivity is lost.
  
• Delay: 120 seconds between each reboot.
  
  

Configuration Steps:

1. In CMP, go to the Devices page and select your PDU.
   
2. Open the Manage Outlets tab.
   
3. Click Select an Outlet Group → Create New Group.
   
   

Group Fields:

• Group Name: Choose a descriptive name.
  
• Reboot Sequence Delay: Set the delay (in seconds) between each outlet reboot.
  
• Outlet Selection: Enable the outlets to include in the group.
  
  

Example Outcome (Delay = 5s):

• Reboot Outlet 1 (Modem) immediately.
  
• Wait 5s.
  
• Reboot Outlet 2 (Router).
  
• Wait 5s.
  
• Reboot Outlet 3 (Switch).
  

(Unselected outlets will not be affected.)

‍

Summary

• Use Outlet Groups if you want a simple, predefined sequence that always reboots all selected outlets.
  
• Use Individual Event Triggers if you want conditional, cascading reboots that stop once connectivity is restored.