Overview
Advanced Matrix Programmer provides a path forward for all legacy installations configured using JADConfig in a stacked topology using two or more switches.
This article covers the steps required to migrate from Stacking to Trunking, combining or replacing any existing legacy multi-switch models at the job-site with any current multi-switch model of the same manufacturer.
For all examples, we will be running a 3-switch system with two Luxul 4424P's and a single SW-610-24P.
Supported Switches
Luxul
Model | Ports On | POE Devices per Switch | SFP+ Ports |
---|---|---|---|
AMS-4424P | Rear | 24 | 2 |
XMS-7048P | Front | 48 | 2 |
SW-610-24P-R | Rear | 24 | 4 |
SW-610-48P-F | Front | 48 | 4 |
Cisco
Not available at this time.
Supported Just Add Power Hardware
Generation | Supported |
---|---|
2G | No |
2GΩ/3G | Yes |
3G | Yes |
MaxColor | Yes |
DISCLAIMER: 2G Installations with 2GΩ/3G & 3G Hardware are not supported!!!
Instructions
*Requires Local or Data Network Up-link accessibility at each switch location*
*When disabling Stacking, all switches will use the SAME IP Address*
Run JADConfig "Read Switch Config" for a report file before getting started.
See JADConfig Report File for SWITCH ID to MAC Address association.
Generate Discovery Configuration Files
- Run AMP VLAN
- Configure
- Name "Project" after job-site
- Choose Switch Manufacturer
- Use the "+' symbol to assign multiple switches'
- Assign Switch Models
- See JADConfig Report file to confirm switch order.
- Assign Network IP Addresses
- All secondary switches are assigned IP addresses in sequential order starting from the primary switch.
- Example:
Switch #1: 192.168.0.100, 255.255.255.0, 192.168.0.1
Switch #2: 192.168.0.101, 255.255.255.0, 192.168.0.1
Switch #3: 192.168.0.102, 255.255.255.0, 192.168.0.1
- Generate Configuration Files
- Save .txt files to Desktop for ease of access
- Do not click "Discovery Config Uploaded"
Setup Existing AMS-4424/XMS-7048 Switches
- Remove SFP+ cables from all switches in the stack.
- Login to Stack Switch via web browser using the Switch Stack IP Address.
- Navigate to: Configuration > Stack
- Uncheck "Stacking Enabled."
- Set Switch ID to "1"
- Set Priority to "1"
- Check to Delete any extra switches listed.
- Click Save
- Navigate to: Administration > Configuration > Upload
- Choose file: "dc_1_[Switch Model]_[SwitchIP].txt"
- Select bubble for "startup-config"
- If "startup-config" is not listed, use "Create New File" and name it "startup-config"
- Select Upload Configuration
- Reboot Switch
- Disconnect Local/Data Network from Stack 1 & Reconnect to Stack 2, Port 1.
- Login to Stack Switch via web browser using Switch Stack IP Address
- Navigate to: Configuration > Stack
- Uncheck "Stacking Enabled."
- Set Switch ID to "1"
- Set Priority to "1"
- Check to Delete any extra switches listed.
- Click Save
- Navigate to: Administration > Configuration > Upload
- Choose file: "dc_2_[Switch Model]_[SwitchIP].txt"
- Select bubble for "startup-config"
- If "startup-config" is not listed, use "Create New File" and name it "startup-config"
- Select Upload Configuration
- Navigate to: Administration > Reboot
- Reboot the Switch.
- Repeat steps above for additional switches.
Adding a SW-610-24P/48P
- Connect Local or Data Network Up-link to the last port of the switch.
- Open the Webui of the switch.
- Choose File: "dc_[#]_[SW-610-24P/48P]_[SwitchIP].txt"
- Select bubble for "startup-config
- If "startup-config" is not listed, use "Create New File" and name it "startup-config"
- Select Upload Configuration
- Reboot the Switch
Continue with AMP
- Reconnect SFP+'s
- Connect one SFP+ Cable between each switch.
- Switch 1 Connects to Switch 2.
- Switch 2 Connects to Switch 3.
- Repeat until last switch is connected.
- Optional: Connect the first switch to the last switch for redundancy.
- Move Local or Data Up-link to the last port of switch 1. (See diagram below)
- Return to AMP
- Click "Uploaded Discovery Config"
- Read the JADConfig Report file to confirm the number of Transmitters and Receivers per switch.
- Physical Layout of Transmitters and Receivers are reversed in AMP.
**DISCLAIMER!! It is recommended to label all network runs before re-patching, otherwise re-configuring the control system might be difficult if runs are patch out of sequential order.**