@Papaul looks good! Nothing jumping out at me as problematic in terms of the connectivity plan.

I don't think it makes sense to use 40G though, we should use 100G links between the switches and the CRs. 100G DAC/AOC/SR4/CWDM4/FR are all valid options. We're already using CWDM4 / duplex SMF between cr3-ulsfo and cr4-ulsfo if it helps to keep it standard. Or possibly use those for inter-rack and DAC/AOC for in-rack?

As the CRs are acting as Spines this gives us more bandwidth between servers in each of the racks. Not essential given our bandwidth usage, but 40G is effectively dead tech we shouldn't plan on using more of it.

@cmooney thanks for the feedback, I will upgrade the diagram to match the 100G links between the core routers and the switches and the type of transceivers needed.

Lots great thanks !

Not sure how best to show it on the diagram, but we also need to remove the 10G link between cr3 and cr4. Maybe you can show the 100G between cr3 and cr4 while mentioning it's already there.

Next step is to write a step by step guide on how to get from the current design to the wanted one. Possibly with intermediate diagrams.

For mr1, now that it's already configured with BGP, an option could be to move one of its upstream ports to one of the Nokias in advance. Until the Nokia is configured, it will only have 1 uplink but but will allow us to seamlessly transition it.

@ayounsi for the feed back i will work on it

@RobH I update the task description with all the connections that we need for phase 1 in December. Please don't forget the Cable ID's. Please let me know if you have any questions. Thanks

@ayounsi I need you input here.
et-0/0/1 on cr3/4-ulsfo are connected to asw2-22/23 the goal was to wait until phase 2 to move et-0/0/1 to the new Nokia switches, by doing this we will have no connection going to asw1-22-ulsfo during the initial setup and configuration. What I will like to do is to temporally using et-0/0/3 to do the initial setup/config and make sure all works from both cr's and asw1-22-ulsfo and during the final phase (migration) we can change move the link from et-0/0/3 to et-0/0/1. See more details in the task description. Thanks

Created ticket Case Order #01144222 for initial racking and wiring of the new Nokia switches.

The first step was completed by remote hands yesterday but the port number and the cable ID's were not given to me so I just got the information today. Both switches are now in Netbox I will start the initial config.

Initial configuration done on both switches. what left on the switches :

• user homer password
• sre.network.tls cookbook

I will work on this next week.

Change #1242429 had a related patch set uploaded (by Papaul; author: Papaul):

[operations/homer/public@master] Add new Nokia switches for initial homer run

https://gerrit.wikimedia.org/r/1242429

Change #1242429 merged by Papaul:

[operations/homer/public@master] Add new Nokia switches for initial homer run

https://gerrit.wikimedia.org/r/1242429

User homer password set on both switches and sre.network.tls.cookbook failed on asw1-23-ulsfo. first homer run on asw1-22-ulsfo is giving the error below. Error is about "evpn" since we are not using EVPN on those.

Traceback (most recent call last):
  File "/srv/deployment/homer/venv-1770131771/lib/python3.11/site-packages/homer/templates.py", line 115, in render
    instance = module.python_renderer(data)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/srv/homer/public/modules/nokia_asw.py", line 12, in __init__
    self._data = self._get_asw_data(data)
                 ^^^^^^^^^^^^^^^^^^^^^^^^
  File "/srv/homer/public/modules/nokia_asw.py", line 43, in _get_asw_data
    data["evpn"] = data["netbox"]["device_plugin"]["ibgp_config"]["evpn"]
                   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^
**KeyError: 'evpn'**

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/srv/deployment/homer/venv-1770131771/lib/python3.11/site-packages/homer/__init__.py", line 356, in _execute
    device_config = self._renderers[device.metadata.get('renderer', 'jinja')].render(
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/srv/deployment/homer/venv-1770131771/lib/python3.11/site-packages/homer/templates.py", line 126, in render
    raise HomerError(f'Error while trying to render JSON-RPC configuration: {e}') from e
homer.exceptions.HomerError: Error while trying to render JSON-RPC configuration: 'evpn'

Both switches are now running version 25.10.2. Still can not get the Cookbook sre.network.tls to pass on asw1-23-ulsfo.

@ayounsi yes I can do that. Do we have like some Documentation on how to factory reset the the Nokia switch somewhere or it is just "delete /" and reboot it?

@ayounsi factory reset the switch same issue.

I think the factory reset helped. I then temporarily copied the TLS config from asw1-22, and ran the TLS cookbook and we're all good.

So now homer runs fine. Now the next step is to convert the relevant routing policies from Junos to Nokia.