Links dropping during gaming time

[Lifepuzzler]

@nissan
172.18.1.7 is part of wms I think. It shows on all ospf RB’s

[nissan]

@Lifepuzzler

172.18.1.7 is part of wms I think. It shows on all ospf RB’s

@Lifepuzzler
Thanks for ure reply and enlightenment . . .
Much Appreciated . .

[TheClown]

If someone wants to put this on the wiki you are most welcome.

[spin]

@nissan

However . . . Udp Method paints a different picture which starts off like this

That UDP trace was done on port 33434.

Game time queues prioritises certain ports and protocols. You can see which ones when looking here under \ip firewall mangle on any OSPF router. Those are the rules that categorise traffic and then the traffic gets queued. Your trace is done on a port that is not listed and therefore not prioritised by default. So it is likely to be throttled by queues along the way. The other aspect to realise is that UDP traffic is designed to deal with loss. TCP is made to recover from lost packets.

There is no point in tracing on that port as it’s not a gaming port and therefore you are likely to see packet loss as it gets dropped by the queues. It is equivalent to tracing on port 7000 during game time.

ICMP (regular pings) get prioritised by the gametime scripts and should have similar performance to packets on any of the prioritised protocols and ports.

@nissan

I checked the Logs first to see if there were any changes made recently . . . Noticed the entry below in Yellow - Not sure if this is a script and what it’s purpose is but I was unable to determine the user at ip ==> 172.18.1.7
I suspected it to be an automated script because it appeared every evening at 20H46 from the same ip.
Could someone maybe explain to me as I am not to familiar with scripting. . . and would appreciate it I could be enlightened for a clearer understanding as to the purpose of this Login occurrences.

That IP is for bastion. That is one of our services and it hosts WMS. The same server also has the IP 172.18.1.10. It also hosts the housekeeping script. Everyday at 20h45 it checks all routers and then it creates a post on the forum in this thread:

Housekeeping

CTWUG Committee have noted several problems creeping into the our wug and many of these can be avoided with a little housekeeping. We are talking about things like: [ul] [li]OSPF routers not having hostnames[/li] [li]OSPF routers not having relevant logins[/li] [li]OSPF routers not having the right WMS scripts etc.[/li] [/ul] These issues make it a hassle to manage the CTWUG and means we can do less of the fun stuff. We are doing a little housekeeping with Project Spring Clean. Rather …

That is the logins you saw.