Hello, it looks like I was close to the ideal setup, but there are some serious considerations that may make this undesirable. From left to right, I'll refer to the PTP820's as 820-1, 820-2, 820-3, and 820-4. I've also attached some pictures that may help.
Assuming in band management (payload and management traffic on ETH1), this becomes burdensome if you have many VLAN's going through the radios.
- Reconfigure 820-1 as a P2P service with two service points:
- Radio Slot 2 Port 1 = SNP S-Tag 10
- ETH1 = SAP Bundle-C
- Attach all of the allowed VLAN's to this service point.
- This is where it becomes difficult since your diagram references 4000+ vlans and we can't specify a range (you will end up with a line item for each VLAN)
- Reconfigure 820-2 as a MP service with three service points:
- Radio Slot 2 Port 1 = SNP S-Tag 10
- ETH1 = SAP Bundle-C
- Attach all of the allowed VLAN's to this service point.
- This is where it becomes difficult since your diagram references 4000+ vlans and we can't specify a range
- ETH2 = SAP dot1q C-VLAN 20
If you are doing Out of band management (dedicated cable into the MNG port), then this design becomes more simple.
- Reconfigure 820-1 as a P2P service with two service points:
- Radio Slot 2 Port 1 = SNP S-Tag 10
- ETH1 = SAP All-2-one
- Reconfigure 820-2 as a MP service with three service points:
- Radio Slot 2 Port 1 = SNP S-Tag 10
- ETH1 = SAP All-2-one
- ETH2 = SAP dot1q C-VLAN 20
- A phyical network cable is needed between Core and 820-1, and 820-2 and 820-3 (and possibly between 820-4 and PMP450/onsite switch)
Ideally we would test in a lab first, and I would recommend taking a backup of the current configuration as a fall-back. Changes like this will most likely require you to be onsite, plugged into the MNG port on the radio. You will need the extra license, that I referenced before, on 820-2, but no other licensing for either setup. I've attached some management considerations. Hope this helps.