Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Philmel: Finish Maintenance #97

Open
19 of 32 tasks
FFHener opened this issue Jul 26, 2024 · 5 comments
Open
19 of 32 tasks

Philmel: Finish Maintenance #97

FFHener opened this issue Jul 26, 2024 · 5 comments
Assignees
@FFHener
Labels
Maintenance A ff-location needs some maintenance Priority Mark tasks that should be proactivly dealt with when someone has capacities

Comments

@FFHener
Copy link
Contributor

FFHener commented Jul 26, 2024 •
edited
Loading

Open TODO's bbb-configs:

  • Update bbb-configs to current state
  • comment sxtsqs out if not running in bbb-config
  • flash hardware with new images
  • close PR to have current state in bbb-configs

Open TODO's Hardware:

  • aquire new sxtsqs for nearfield with shields and mount
  • add and patch to new cables with plugs
    • westwindow
    • northwindow
  • mount new sxtsqs for nearfield on tower

Open TODO's Alignement:

  • Align philmel <-> Klunker 60GHz

Software

  • Update bbb-configs single location file config
  • Create image
    • Core-Router
    • Sxtsq

Hardware

  • Prepare Switch
    • ports to cardinal!
    • keep hierarchy
    • vlan
    • poe
  • Prepare Rocket
  • Prepare isobeam 300
  • Exchange mikrotik 60ghz with sector sgfrd-core <-> philmel

Alignment

  • align 60GHz towards klunker philmel <-> klunker
  • align 5GHz towards ak36 philmel <-> ak36

Assembly Mounts etc.

Eastwindow

  • remove LiteAP in Eastwindow
  • Exchange SxtSQ5AC to the left side of window
  • Cut the right side of the SXTSQ Mount
  • Mount Pole in Eastwindow
  • Mount RocketLiteAC and TitaniumSector in right half of Eastwindow
  • Align devices SXT to Kranoldplatz and Rocket slightly to south with 120 degree angle

Network

  • change subnets and ips in config
  • Change subnets and ips on hardware
@FFHener FFHener added the Maintenance A ff-location needs some maintenance label Jul 26, 2024
@FFHener FFHener self-assigned this Jul 26, 2024
@booo
Copy link
Member

booo commented Jul 26, 2024

Please keep me posted about the progress and planed work. Thanks.

I can invest a very limited amount of work as well if you need help.

@Petrella
Copy link

Petrella commented Sep 24, 2024 •
edited by FFHener
Loading

EDIT: Moved TODOs to top comment

Open TODO's bbb-configs:

  • Update bbb-configs to current state
  • comment sxtsqs out if not running in bbb-config
  • flash hardware with new images
  • close PR to have current state in bbb-configs

Open TODO's Hardware:

  • aquire new sxtsqs for nearfield with shields and mount
  • add and patch to new cables with plugs
    • westwindow
    • northwindow
  • mount new sxtsqs for nearfield on tower

Open TODO's Alignement:

  • Align philmel <-> Klunker 60GHz

Software

  • Update bbb-configs single location file config
  • Create image
    • Core-Router
    • Sxtsq

Hardware

  • Prepare Switch
    • ports to cardinal!
    • keep hierarchy
    • vlan
    • poe
  • Prepare Rocket
  • Prepare isobeam 300
  • Exchange mikrotik 60ghz with sector sgfrd-core <-> philmel

Alignment

  • align 60GHz towards klunker philmel <-> klunker
  • align 5GHz towards ak36 philmel <-> ak36

Assembly Mounts etc.

Eastwindow

  • remove LiteAP in Eastwindow
  • Exchange SxtSQ5AC to the left side of window
  • Cut the right side of the SXTSQ Mount
  • Mount Pole in Eastwindow
  • Mount RocketLiteAC and TitaniumSector in right half of Eastwindow
  • Align devices SXT to Kranoldplatz and Rocket slightly to south with 120 degree angle

Network

  • change subnets and ips in config
  • Change subnets and ips on hardware

@FFHener FFHener added the Priority Mark tasks that should be proactivly dealt with when someone has capacities label Oct 8, 2024
@FFHener
Copy link
Contributor Author

FFHener commented Oct 21, 2024

There might be another appointment next friday to finish the TODOs

@booo
Copy link
Member

booo commented Oct 22, 2024

Not sure if that is on the agenda but it would make sense to check the channel assignment for each link and make sure we do not have overlapping channels in use. Double checking the tx power would be wise too. Most of the time we tend to use high tx power without very significant change in throughput.

@FFHener
Copy link
Contributor Author

FFHener commented Oct 22, 2024

As this could be done remotly very easily I wouldnt put it into the scope of this on-site appointment. But in general im in favour of it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@FFHener FFHener

Labels
Maintenance A ff-location needs some maintenance Priority Mark tasks that should be proactivly dealt with when someone has capacities
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@booo @Petrella @FFHener