Closed
Bug 999940
Opened 11 years ago
Closed 10 years ago
Please check flows between vlan 236 winbuild and Domain controllers 6-9
Categories
(Infrastructure & Operations Graveyard :: NetOps: DC ACL Request, task)
Infrastructure & Operations Graveyard
NetOps: DC ACL Request
x86_64
Windows 7
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: markco, Assigned: arzhel)
References
Details
We should have any:any communication between machines in vlan 236 winbuild in SCL3 and domain controllers dc6-9.releng.ad.mozilla.com, 10.22.69.18, 10.12.69.19, 10.22.69.21, 10.12.69.20.
We are currently seeing an issue with clients receiving/sending data from/to the DCs.
Assignee | ||
Comment 1•11 years ago
|
||
Was it working before?
Which host in vlan236 and destination IP/port can I use to troubleshot?
Assignee: network-operations → arzhel
Assignee | ||
Comment 2•11 years ago
|
||
I don't see any trace of dc7 or dc9 in our configuration, in witch bug those flows have been requested?
I added them to the rule allowing winbuild to dc6. Is it working as expected?
Reporter | ||
Comment 3•11 years ago
|
||
Yes this was working previously. It seem like the issue began around 4/15 or 4/16. I am going to check around and see if there has been any change in the behavior.
Reporter | ||
Comment 4•11 years ago
|
||
Things seem to be better now. So there no changes made for the flows for dc6? If that is case there is still an unknown issue there, and machines in SCL3 are failing over to one of the other DCs.
Assignee | ||
Comment 5•11 years ago
|
||
Indeed, no changes for dc6. Is it possible to know what flow is not going through and causing the issue?
Assignee | ||
Updated•10 years ago
|
Flags: needinfo?(mcornmesser)
Assignee | ||
Comment 6•10 years ago
|
||
hey, please reopen if there is still any issue.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Reporter | ||
Updated•10 years ago
|
Flags: needinfo?(mcornmesser)
Updated•2 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•