Skip to content

Commit

Permalink
cleanup guides
Browse files Browse the repository at this point in the history 
* remove dups
  • Loading branch information
@up-n-atom
up-n-atom committed Dec 1, 2024
1 parent 99f1a62 commit 6d00023
Show file tree
Hide file tree
Showing 9 changed files with 315 additions and 432 deletions.
104 changes: 43 additions & 61 deletions ...rade-as-the-att-inc-bgw320-500-505-on-xgs-pon-with-the-bfw-solutions-was-110.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -137,89 +137,71 @@ identifiers are available on the bottom label of the BGW320-500/505, color-coord

4. __Save__ changes and reboot from the __System__ menu.

Once rebooted, the SC/APC cable can safely be plugged into the WAS-110 and immediately receive O5 operational status.
### from the shell

!!! tip "Clone the BGW320-500/505 :purple_circle: MAC address on the router's DHCP WAN interface to avoid waiting for the 20 minute lease to expire."

For troubleshooting, please read:
1. Login over secure shell (SSH).

[Troubleshoot connectivity issues with the BFW Solutions WAS-110]
``` sh
ssh [email protected]
```

!!! note "Do not be alarmed..."
If you receive an e-mail and/or text informing you to:
2. Configure the 8311 U-Boot environment.

> Check your AT&T Fiber equipment since you might be offline currently.
!!! reminder "Highlighted lines are <ins>mandatory</ins>"
<ins>Replace</ins> the mandatory :blue_circle: __8311_gpon_sn__ with the provisioned value on the bottom
[label] of the BGW320-500/505.

The BGW-500/505 sends telemetry data to *better* the customer experience.
=== "BGW320-500"

### from the shell
``` sh hl_lines="1 7"
fwenv_set -8 gpon_sn HUMA... # (1)!
fwenv_set -8 equipment_id iONT320500G
fwenv_set -8 hw_ver BGW320-500_2.1
fwenv_set -8 cp_hw_ver_sync 1
fwenv_set -8 sw_verA BGW320_4.27.7
fwenv_set -8 sw_verB BGW320_4.27.7
fwenv_set -8 fix_vlans 1
```

<h4>Login over SSH</h4>
1. :blue_circle: ONT ID

``` sh
ssh [email protected]
```
=== "BGW320-505"

<h4>Configure 8311 U-Boot environment</h4>
``` sh hl_lines="1 7"
fwenv_set -8 gpon_sn NOKA... # (1)!
fwenv_set -8 equipment_id iONT320505G
fwenv_set -8 hw_ver BGW320-505_2.2
fwenv_set -8 cp_hw_ver_sync 1
fwenv_set -8 sw_verA BGW320_4.27.7
fwenv_set -8 sw_verB BGW320_4.27.7
fwenv_set -8 fix_vlans 1
```

!!! reminder "Highlighted lines are <ins>mandatory</ins>"
<ins>Replace</ins> the mandatory :blue_circle: __8311_gpon_sn__ with the provisioned value on the bottom
[label] of the BGW320-500/505.
1. :blue_circle: ONT ID

=== "BGW320-500"
!!! info "Additional details and variables are described at the original repository [^1]"
`/usr/sbin/fwenv_set` is a helper script that executes `/usr/sbin/fw_setenv` twice consecutively.

``` sh hl_lines="1 7"
fwenv_set -8 gpon_sn HUMA... # (1)!
fwenv_set -8 equipment_id iONT320500G
fwenv_set -8 hw_ver BGW320-500_2.1
fwenv_set -8 cp_hw_ver_sync 1
fwenv_set -8 sw_verA BGW320_4.27.7
fwenv_set -8 sw_verB BGW320_4.27.7
fwenv_set -8 fix_vlans 1
```
The WAS-110 functions as an A/B system, requiring the U-Boot environment variables to be set twice, once for each
environment.

1. :blue_circle: ONT ID
The `-8` option prefixes the U-Boot environment variable with `8311_`.

=== "BGW320-505"
3. Verify the 8311 U-boot environment and reboot.

``` sh hl_lines="1 7"
fwenv_set -8 gpon_sn NOKA... # (1)!
fwenv_set -8 equipment_id iONT320505G
fwenv_set -8 hw_ver BGW320-505_2.2
fwenv_set -8 cp_hw_ver_sync 1
fwenv_set -8 sw_verA BGW320_4.27.7
fwenv_set -8 sw_verB BGW320_4.27.7
fwenv_set -8 fix_vlans 1
``` sh
fw_printenv | grep ^8311
reboot
```

1. :blue_circle: ONT ID

!!! info "Additional details and variables are described at the original repository [^1]"
`/usr/sbin/fwenv_set` is a helper script that executes `/usr/sbin/fw_setenv` twice consecutively.

The WAS-110 functions as an A/B system, requiring the U-Boot environment variables to be set twice, once for each
environment.

The `-8` option prefixes the U-Boot environment variable with `8311_`.

<h4>Verify and reboot</h4>
After rebooting, the SC/APC cable can safely be plugged into the [WAS-110] and immediately receive O5
operational status. For troubleshooting, please read:

Prior to rebooting, verify that the 8311 environment variables are set correctly. If not, proceed to correct them with
the `fwenv_set` command as before.

``` sh
fw_printenv | grep ^8311
reboot
```

Once rebooted, the SC/APC cable can safely be plugged into the WAS-110 and immediately receive O5 operational status.
[Troubleshoot connectivity issues with the BFW Solutions WAS-110]

!!! tip "Clone the BGW320-500/505 :purple_circle: __MAC address__ on the router's DHCP WAN interface to avoid waiting for the 20 minute lease to expire."

For troubleshooting, please read:

[Troubleshoot connectivity issues with the BFW Solutions WAS-110]

!!! note "Do not be alarmed..."
If you receive an e-mail and/or text informing you to:

Expand Down
83 changes: 32 additions & 51 deletions ...masquerade-as-the-bce-inc-giga-hub-on-xgs-pon-with-the-bfw-solutions-was-110.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -171,65 +171,46 @@ identifiers are available on the back label of the Giga Hub, color-coordinated i

4. __Save__ changes and reboot from the __System__ menu.

Once rebooted, the SC/APC cable can safely be plugged into the WAS-110 and immediately receive O5
operational status.

For troubleshooting, please read:

[Troubleshoot connectivity issues with the BFW Solutions WAS-110]

### from the shell

<h4>Login over SSH</h4>

``` sh
ssh [email protected]
```

<h4>Configure 8311 U-Boot environment</h4>

!!! reminder "Highlighted lines are <ins>mandatory</ins>"
<ins>Replace</ins> the mandatory :blue_circle: __8311_gpon_sn__ and optional :purple_circle:
__8311_iphost_mac__ with the provisioned values on the back [label] of the Giga Hub.

``` sh hl_lines="1 3 9 10"
fwenv_set mib_file
fwenv_set -8 iphost_mac 40:65:A3:FF:A7:B1 # (1)!
fwenv_set -8 gpon_sn SMBS... # (2)!
fwenv_set -8 equipment_id 5690
fwenv_set -8 hw_ver Fast5689EBell
fwenv_set -8 cp_hw_ver_sync 1
fwenv_set -8 sw_verA SGC8400058 # (3)!
fwenv_set -8 sw_verB SGC8400058
fwenv_set -8 mib_file /etc/mibs/prx300_1V_bell.ini
fwenv_set -8 fix_vlans 1
```
1. Login over secure shell (SSH).

1. :purple_circle: @MAC + 1, e.g. `40:65:A3:FF:A7:B0` becomes `40:65:A3:FF:A7:B1`
2. :blue_circle: ONT S/N
3. [Version listing]

!!! info "Additional details and variables are described at the original repository [^2]"
`/usr/sbin/fwenv_set` is a helper script that executes `/usr/sbin/fw_setenv` twice consecutively.

The WAS-110 functions as an A/B system, requiring the U-Boot environment variables to be set twice, once for each
environment.

The `-8` option prefixes the U-Boot environment variable with `8311_`.
``` sh
ssh [email protected]
```

<h4>Verify and reboot</h4>
2. Configure the 8311 U-Boot environment.

!!! reminder "Highlighted lines are <ins>mandatory</ins>"
<ins>Replace</ins> the mandatory :blue_circle: __8311_gpon_sn__ and optional :purple_circle:
__8311_iphost_mac__ with the provisioned values on the back [label] of the Giga Hub.

``` sh hl_lines="1 3 9 10"
fwenv_set mib_file
fwenv_set -8 iphost_mac 40:65:A3:FF:A7:B1 # (1)!
fwenv_set -8 gpon_sn SMBS... # (2)!
fwenv_set -8 equipment_id 5690
fwenv_set -8 hw_ver Fast5689EBell
fwenv_set -8 cp_hw_ver_sync 1
fwenv_set -8 sw_verA SGC8400058 # (3)!
fwenv_set -8 sw_verB SGC8400058
fwenv_set -8 mib_file /etc/mibs/prx300_1V_bell.ini
fwenv_set -8 fix_vlans 1
```

Prior to rebooting, verify that the 8311 environment variables are set correctly. If not, proceed to correct them with
the `fwenv_set` command as before.
1. :purple_circle: @MAC + 1, e.g. `40:65:A3:FF:A7:B0` becomes `40:65:A3:FF:A7:B1`
2. :blue_circle: ONT S/N
3. [Version listing]

``` sh
fw_printenv | grep ^8311
reboot
```
3. Verify the 8311 U-boot environment and reboot.

Once rebooted, the SC/APC cable can safely be plugged into the WAS-110 and immediately receive O5 operational status.
``` sh
fw_printenv | grep ^8311
reboot
```

For troubleshooting, please read:
After rebooting, the SC/APC cable can safely be plugged into the [WAS-110] and immediately receive O5
operational status. For troubleshooting, please read:

[Troubleshoot connectivity issues with the BFW Solutions WAS-110]

Expand Down
82 changes: 32 additions & 50 deletions ...erade-as-the-bce-inc-home-hub-4000-on-xgs-pon-with-the-bfw-solutions-was-110.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -179,64 +179,46 @@ identifiers are available on the back label of the Home Hub 4000, color-coordina

4. __Save__ changes and reboot from the __System__ menu.

Once rebooted, the SC/APC cable can safely be plugged into the WAS-110 and immediately receive O5 operational status.

For troubleshooting, please read:

[Troubleshoot connectivity issues with the BFW Solutions WAS-110]

### from the shell

<h4>Login over SSH</h4>

``` sh
ssh [email protected]
```

<h4>Configure 8311 U-Boot environment</h4>

!!! reminder "Highlighted lines are <ins>mandatory</ins>"
<ins>Replace</ins> the mandatory :blue_circle: __8311_gpon_sn__ and optional :purple_circle:
__8311_iphost_mac__ with the provisioned values on the back [label] of the Home Hub 4000.

``` sh hl_lines="1 3 9 10"
fwenv_set mib_file
fwenv_set -8 iphost_mac 40:65:A3:FF:A7:B1 # (1)!
fwenv_set -8 gpon_sn SMBS... # (2)!
fwenv_set -8 equipment_id 5689
fwenv_set -8 hw_ver Fast5689Bell
fwenv_set -8 cp_hw_ver_sync 1
fwenv_set -8 sw_verA SGC8210154 # (3)!
fwenv_set -8 sw_verB SGC8210154
fwenv_set -8 mib_file /etc/mibs/prx300_1V_bell.ini
fwenv_set -8 fix_vlans 1
```
1. Login over secure shell (SSH).

1. :purple_circle: @MAC + 1, e.g. `40:65:A3:FF:A7:B0` becomes `40:65:A3:FF:A7:B1`
2. :blue_circle: ONT S/N
2. [Version listing]

!!! info "Additional details and variables are described at the original repository [^2]"
`/usr/sbin/fwenv_set` is a helper script that executes `/usr/sbin/fw_setenv` twice consecutively.

The WAS-110 functions as an A/B system, requiring the U-Boot environment variables to be set twice, once for each
environment.

The `-8` option prefixes the U-Boot environment variable with `8311_`.
``` sh
ssh [email protected]
```

<h4>Verify and reboot</h4>
2. Configure the 8311 U-Boot environment.

!!! reminder "Highlighted lines are <ins>mandatory</ins>"
<ins>Replace</ins> the mandatory :blue_circle: __8311_gpon_sn__ and optional :purple_circle:
__8311_iphost_mac__ with the provisioned values on the back [label] of the Home Hub 4000.

``` sh hl_lines="1 3 9 10"
fwenv_set mib_file
fwenv_set -8 iphost_mac 40:65:A3:FF:A7:B1 # (1)!
fwenv_set -8 gpon_sn SMBS... # (2)!
fwenv_set -8 equipment_id 5689
fwenv_set -8 hw_ver Fast5689Bell
fwenv_set -8 cp_hw_ver_sync 1
fwenv_set -8 sw_verA SGC8210154 # (3)!
fwenv_set -8 sw_verB SGC8210154
fwenv_set -8 mib_file /etc/mibs/prx300_1V_bell.ini
fwenv_set -8 fix_vlans 1
```

Prior to rebooting, verify that the 8311 environment variables are set correctly. If not, proceed to correct them with
the `fwenv_set` command as before.
1. :purple_circle: @MAC + 1, e.g. `40:65:A3:FF:A7:B0` becomes `40:65:A3:FF:A7:B1`
2. :blue_circle: ONT S/N
2. [Version listing]

``` sh
fw_printenv | grep ^8311
reboot
```
3. Verify the 8311 U-boot environment and reboot.

Once rebooted, the SC/APC cable can safely be plugged into the WAS-110 and immediately receive O5 operational status.
``` sh
fw_printenv | grep ^8311
reboot
```

For troubleshooting, please read:
After rebooting, the SC/APC cable can safely be plugged into the [WAS-110] and immediately receive O5
operational status. For troubleshooting, please read:

[Troubleshoot connectivity issues with the BFW Solutions WAS-110]

Expand Down
4 changes: 1 addition & 3 deletions ...masquerade-as-the-bouygues-sa-bbox-on-xgs-pon-with-the-bfw-solutions-was-110.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -206,8 +206,6 @@ outlined in the community firmware installation guide:

3. From the __8311 Configuration__ page, on the __ISP Fixes__ tab, disable __Fix VLANs__ from the drop-down.

!!! info "Tag the router's DHCP WAN interface and/or anything in-between the WAS-110 with VLAN 100"

4. __Save__ changes and reboot from the __System__ menu.

### from the shell
Expand Down Expand Up @@ -246,7 +244,7 @@ outlined in the community firmware installation guide:
reboot
```

After rebooting, the SC/APC cable can safely be plugged into the WAS-110 and immediately receive O5
After rebooting, the SC/APC cable can safely be plugged into the [WAS-110] and immediately receive O5
operational status. For troubleshooting, please read:

[Troubleshoot connectivity issues with the BFW Solutions WAS-110]
Expand Down
Loading

0 comments on commit 6d00023

Please sign in to comment.