Good idea, before we start entering data we need to add validators to prevent entry mistakes (regex for the format, maybe coherence in the numbering) and prevent ID-less racks in the relevant sites.

Good idea, before we start entering data we need to add validators to prevent entry mistakes (regex for the format, maybe coherence in the numbering) and prevent ID-less racks in the relevant sites.

@wiki_willy can you ask for credits on that one too ? HE ticket 7282921 for circuit dc4841.dal5.sin1 showing issues between 2026-10-02 06:20 and 2026-10-03 04:40 with a 4h improvement window in the middle.

Thank you for this report. There is currently maintenance being performed on some of our trans-Pacific circuits which may be impacting your traffic. It should be completed by 1300 UTC.

Please open a new ticket, the person in charge of access requests changes every 7 days (it's now @herron)

@Papaul, are you (or someone else in DCops) ok to take care of mr1-eqiad?

The new JTAC recommended version for the SRX300 is now Junos 24.4R2-S3.

Let's use the upgrade opportunity to enable BGP RIB sharding on one of the two routers T320264: Junos: investigate BGP rib sharding

Let's use the upgrade opportunity to enable BGP RIB sharding on cr2-eqsin T320264: Junos: investigate BGP rib sharding

Give it 30min for the change to propagate and you should be good. Please re-open if there is any issue.

All done, give it 30min for the removal to propagate. Please reopen if any issue.

@LSobanski is that something you can help with ?

Give it 30min for the change to propagate. Please re-open the task if you have any issue.

Give it ~30min for the change to propagate and give it a try. Please re-open the task if any issue. Thanks

@eniroomand Please familiarize yourself with https://wikitech.wikimedia.org/wiki/Data_Platform/Data_access#User_responsibilities
Could you also get your manager's approval on this task ?

Deployed!

Great point, I sent https://gerrit.wikimedia.org/r/c/operations/alerts/+/1345934 for that.

Marking it as stalled until we have upgraded all the devices.

All done!

Well, CyrusOne took care of the reboot with the power outage.

Going to close that one, the pool and depool actions have been tested, now supports also the "manual" policy. Some roles don't have policies, (for example backup or lvs hosts) but that's up to the service owners if they want to document it.

In T439143#12363934, @GOlson-WMF wrote:

@ayounsi I just had one (ed25519) already for other access, figured it would be a little easier for me to have the two separate style ones!

@GOlson-WMF could you use an ed25519 ssh key? Or detail why you can't use one.

@thcipriani @dancy do you approve this request ?
@Tsevener can you sign https://phabricator.wikimedia.org/L3 ?

Randomly found this task.

There is an outstanding change on the switch for that host:

Change for lsw1-e5-eqiad.mgmt.eqiad.wmnet:

Looks like some of the checks are not alerting correctly: https://netbox.wikimedia.org/extras/scripts/results/398218/

[clinic duty] boldly assigning the task to Tiziano as they sent a patch.

Working on an alerting feature for one of "my" cookbooks (https://gerrit.wikimedia.org/r/c/operations/cookbooks/+/1343990) I was wondering if o11y was planning on improving the remove-downtime cookbook? (@hnowlan ?)
The ideal would be to be able to only remove downtime that were set for a specific context in AlertManager.

I feel like as this is something not done at a high frequency, the priority to fully automate them will be lower than other projects. If that's the case the priority will depends on the complexity.

All done.

Deployed the workaround on asw1-b3-magru (not showing signs of issues yet)

The most likely fix to move forward is to move the bgpalerter instance on the netmon hosts as they have direct internet connectivity.

Junos recommended for the SRX300 is now 24.4 so hopefully next year for 25.4, unless we decide to upgrade sooner.

There is unfortunately a catch that's going to warrant larger discussions: 2.0.0 removed proxy support, on which we rely :(

All done.

Are you currently experiencing any issues with LibreNMS??