What to do if MID Server Consumer is started & still logs are not flowing to the destination endpoint? - Support and Troubleshooting

What to do if MID Server Consumer is started & still logs are not flowing to the destination endpoint? Summary .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Troubleshooting:

Step 1 : Run these commands to check if the ports are open or not

For Windows user on powershell (admin privileges needed):

Test-NetConnection -ComputerName -Port telnet

Test-NetConnection -ComputerName xxx.service-now.com -Port 4100 Test-NetConnection -ComputerName xxx.service-now.com -Port 4101 Test-NetConnection -ComputerName xxx.service-now.com -Port 4102 Test-NetConnection -ComputerName xxx.service-now.com -Port 4103 Test-NetConnection -ComputerName xxx.service-now.com -Port 4200 Test-NetConnection -ComputerName xxx.service-now.com -Port 4201 Test-NetConnection -ComputerName xxx.service-now.com -Port 4202 Test-NetConnection -ComputerName xxx.service-now.com -Port 4203 telnet xxx.service-now.com 4100 telnet xxx.service-now.com 4101 telnet xxx.service-now.com 4102 telnet xxx.service-now.com 4103 telnet xxx.service-now.com 4100 telnet xxx.service-now.com 4201 telnet xxx.service-now.com 4202 telnet xxx.service-now.com 4203 For Mac users (ports will be changed as per above commands):

nc -zv nc -zv xxx.service-now.com 4100

The output of these commands should show successful network connection. If it shows Unsuucessful then ask customer to open their ports so that MID Server can connect with the Kafka Client.

Note : These commands only validate basic TCP connectivity. If there are questions about required ports, port ranges, or Hermes connectivity expectations, please engage the Hermes team for confirmation. (Assignment Group : Dev-Hermes )

Step 2 : If you had already ran these commands and you see ports are open still you are facing the same issue, then try this OpenSSL command to confirm that the ports are accessible through the firewall :

openssl s_client -connect .service-now.com: -servername .service-now.com

Producer: 4000-4050 Consumer1: 4100-4150 Consumer2: 4200-4250 Change the service-now.com domain if your instance uses a different domain name.

Complete the test using ports from each of the three port ranges. For example: test 4000-4003, 4100-4103, and 4200-4203.

Reference KB : https://www.servicenow.com/docs/r/yokohama/servicenow-platform/multi-instance-framework-hermes/producing-consuming-hermes.html

Output :

1. If the output is success you will see something like this :

2. If the output is failure you will see something like this :

Solution : In case of failure, please engage the Network team (Assignment Group : Network Engineering) to verify. Or please ask the customer to check with their network administrator to verify whether the required ports are open on their firewall.

Step 3 : Just check the MID Server properties : It should contain all the 13 properties.

Note : For other MID Server related issues we can follow this KB : https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2395146 You can reach out to LES team if there is any other issue from MID Server Consumer (Assignment Group – Dev-Platform Data_Defense_Boost )

Release .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } TBD