Goline Logo

News

  • Route RPKI validation April 1st, 2022
    RPKI is a security framework by which network owners can validate and secure the critical route updates or Border Gateway Protocol (BGP) announcements between public Internet networks. BGP is essentially the central nervous system of the Internet and one of its fundamental building blocks. The main function of BGP is to facilitate efficient routing between Autonomous Systems (AS), by building and maintaining the Internet routing table. The Internet routing table is effectively the navigation system of the Internet and without it, traffic would be unable to flow between its constituent networks. Unfortunately, routing equipment alone cannot distinguish between legitimate and malicious routing announcements,...
  • RIPE – Atlas Anchor February 17th, 2022
    We have become an even more integral part of the RIPE Atlas project by hosting an anchor, a device that allows for latency analysis of traffic between autonomous systems.https://atlas.ripe.net/probes/7073/RIPE Atlas anchors play an integral role in the RIPE Atlas network by acting both as enhanced RIPE Atlas probes with more measurement capacity, as well as regional measurement targets within the greater RIPE Atlas network. Anchors are able to perform many more measurements than a regular RIPE Atlas probe, and the large amount of data they collect is made available to everyone. In addition, anchors act as powerful targets that can...
  • MANRS June 20th, 2020
    GOLINE firmly believes in initiatives to protect networks, improve security and resilience of the global routing system. Therefore we decided to support the MANRS project and join as participants.Mutually Agreed Norms for Routing Security (MANRS) is a global initiative, supported by the Internet Society, that provides crucial fixes to reduce the most common routing threats. MANRS offers specific actions via four programs for Network Operators, Internet Exchange Points, CDN and Cloud Providers, and Equipment Vendors. Requirements for Participation Please read the full MANRS Actions document before applying. You can become a participant if you meet these requirements: You (or your company) support...

MS Exchange DAG Maintenance error (exiting from script)

Caparrelli Paolo Exchange Server 22 June 2022

Exchange DAG Maintenance – cluster.exe issue (5058)

 

Today, on a DAG maintenance of an Exchange 2016, I ran into the problem that after executing the script StopDagServerMaintenance.ps1 a warning was displayed.

 

Call-ClusterExe: cluster.exe did not succeed, but 5058 was not a retry-able error code. Not attempting any other servers. This may be an expected error by the caller.

 

 
 
 

 

After a little troubleshooting I found that after running the scripts StartDag ServerMaintenance.ps1, the cluster node has not been paused and in the StopDagMaintenance.ps1 script, this will be checked and reseted so the cluster node is up again – what causes an error.

 

 
 
 

 

I will show you the problem and how I (and you too) could fix it.

 

Note: You need to always run the Exchange Management Shell as administrator.

 

 

After I got the problem, I looked at the script more closely and found that Microsoft has set a $false for the pauseClusterNode instead of a $true.

 

 
 
 

 

I have changed this to $true and saved the script.

 

Note: To do this, run the PowerShell ISE as administrator and open the script.

 

 
 
 

 

I then executed the script again and checked the state using Get-ClusterNode and now the cluster node was paused.

 

 
 
 

 

Now, when I run the StopDagServerMaintenance.ps1 script, the error no longer occurred.

 

 
 
 

 

Enjoy and take care!

0 0 votes
Article Rating
Subscribe
Notify of
guest
0 Comments
Inline Feedbacks
View all comments
0
Would love your thoughts, please comment.x
()
x