Closed
Bug 1256653
Opened 10 years ago
Closed 10 years ago
Broadcast ateam SSID in all offices
Categories
(Infrastructure & Operations Graveyard :: NetOps: Office Other, task)
Infrastructure & Operations Graveyard
NetOps: Office Other
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jbarnell, Assigned: dcurado)
Details
As part of our efforts to support the connected devices team we need to broadcast the ateam ssid in all offices. This should allow for support of the consumer wireless devices they are working on as well as provide appropriate segregation from the production networks.
| Assignee | ||
Comment 1•10 years ago
|
||
this work has been done in TPE1 previously...
https://bugzilla.mozilla.org/show_bug.cgi?id=1161398
We should be able to follow those steps to put the 'ateam' ssid in all offices.
| Assignee | ||
Comment 2•10 years ago
|
||
steps:
- ensure that 'ateam' is present as a vlan on all office switches (done)
- ensure that the 'ateam' vlan is trunked to the wap interface range
- ensure that the 'ateam' vlan is connected/trunked to the firewall in each office (done)
- configure the wifi controllers
(blatantly stealing this config snippet from Van)
wifi1.ops.tpe1.mozilla.net#
set radio-profile tpe1 service-profile ateam
set service-profile ateam ssid-name ateam
set service-profile ateam proxy-arp enable
set service-profile ateam auth-fallthru last-resort
set service-profile ateam psk-encrypted XXXXXXXXXXXXXXXXXXXXXXXXXXX
set service-profile ateam load-balancing-exempt enable
set service-profile ateam 11n mode-na disable
set service-profile ateam 11n mode-ng disable
set service-profile ateam wpa-ie auth-dot1x disable
set service-profile ateam rsn-ie cipher-ccmp enable
set service-profile ateam rsn-ie auth-psk enable
set service-profile ateam rsn-ie auth-dot1x disable
set vlan-profile corp vlan ateam tag 120
set service-profile ateam rsn-ie enable
set vlan 120 name ateam
set vlan 120 port 2 tag 120
set igmp disable vlan 120
| Assignee | ||
Comment 3•10 years ago
|
||
Michal` - in lieu of a sec-review flag, can you please take a look at this proposed change and give it your security blessing?
Please note that some offices (TOR1 and TPE1) already have this ssid advertised.
Thank you!
Flags: needinfo?(mpurzynski)
| Assignee | ||
Updated•10 years ago
|
Assignee: network-operations → dcurado
Status: NEW → ASSIGNED
Comment 4•10 years ago
|
||
The change looks sane, we already have those devices in a separate Vlan, with firewall policies that allow access from corp -> ateam/QA and do NOT allow connections to be initiated from QA/Ateam -> corp.
So that's not really different from TOR1/TPE1.
Flags: needinfo?(mpurzynski)
| Assignee | ||
Comment 5•10 years ago
|
||
I have trunked the ateam vlan to the wap interface range in all the offices where it was not already there.
I believe all there to do now is the wifi controller part.
| Assignee | ||
Comment 6•10 years ago
|
||
Talked to Van, he is going to do the wifi controller part this weekend.
| Assignee | ||
Comment 7•10 years ago
|
||
Here's the list of switches I modified to include 'ateam' in the wap interface-range...
switch1.df701-1.ops.sfo1.mozilla.net
switch1.df101-1.ops.sfo1.mozilla.net
switch1.df102-1.ops.sfo1.mozilla.net
switch1.df301-1.ops.sfo1.mozilla.net
switch1.ops.pdx1.mozilla.net
switch1.ops.yvr1.mozilla.net
switch1.ops.lon1.mozilla.net
switch1.df101-1.ops.par1.mozilla.net
switch1.df001.ops.par1.mozilla.net
switch1.df102.ops.par1.mozilla.net
switch2.df103.ops.par1.mozilla.net
switch1.r201-1.ops.ber1.mozilla.net
switch1.df101-1.ops.ber2.mozilla.net
switch1.ops.akl1.mozilla.net
Comment 8•10 years ago
|
||
NA and EU offices should now be broadcasting the ateam SSID. will need someone in the offices to confirm connectivity. APAC currently has network issues so I'll look into configuring the ateam SSID tonight or when the network recovers.
11:11 AM <@nagios-scl3> Sat 11:11:13 PDT [5238] fw1.ops.tpe1.mozilla.net (10.247.0.1) is DOWN :PING CRITICAL - Packet loss = 100%
Comment 9•10 years ago
|
||
NA and EU offices should now be broadcasting the ateam SSID. will need someone in the offices to confirm connectivity. APAC currently has network issues so I'll look into configuring the ateam SSID tonight or when the network recovers.
11:11 AM <@nagios-scl3> Sat 11:11:13 PDT [5238] fw1.ops.tpe1.mozilla.net (10.247.0.1) is DOWN :PING CRITICAL - Packet loss = 100%
Comment 10•10 years ago
|
||
>Talked to Van, he is going to do the wifi controller part this weekend.
configs added to controllers, ateam ssid should be broadcasting to all offices now.
| Assignee | ||
Updated•10 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Updated•3 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
•