AAA & Authentication
Routes under: aaa
- aaa > radius > clientg > all
- aaa > radius > clients > addclient
- aaa > radius > clients > l
- aaa > radius > node > l
- aaa > radius > sesdis > all
- aaa > radius > set
aaa > radius > clientg > all
aaa > radius > clientg > all
Route: aaa/radius/clientg/all
URL: https://admin.myslbb.com/#/aaa/radius/clientg/all
Overview
This page is a draft SOP reference for the above screen in i2i Core OSS/BSS. It is auto-generated from UI exports and should be reviewed for operational correctness before customer release.
When to Use
- Use this screen for the workflow represented by this route.
- Do not make billing/AAA/provisioning-impacting changes without required authorization.
Typical Workflow
- Verify you are working on the correct entity (Customer/Account/Service).
- Review the current lifecycle state before making changes.
- Apply changes and validate system response.
- Confirm downstream impact (AAA/Provisioning/Billing) where applicable.
Field & Action Hints (Auto-detected)
- Actions detected: Auto, Close, AAA, Radius, Radius Client Group, New Client Group, Default Rad Group, SmartLink Dandy BNG Group, SmartLink Mikrotik Group, Sunrise WiFi Mikrotik Group
Validation & Safety Checks
- Confirm identifiers before saving.
- Confirm lifecycle state allows the change.
- Confirm rollback/support path exists for production actions.
Escalation Guidance
- L1: Verify input, permissions, and entity state.
- L2: Validate dependencies and downstream state.
- L3/Admin: Policy/config changes or suspected defect.
Screenshots
default
Captured URL: https://admin.myslbb.com/#/aaa/radius/clientg/all
default
Captured URL: https://admin.myslbb.com/#/aaa/radius/clientg/all
create_new
Captured URL: https://admin.myslbb.com/#/aaa/radius/clientg/all
create_new
Captured URL: https://admin.myslbb.com/#/aaa/radius/clientg/all
drilldown_one_item
Captured URL: https://admin.myslbb.com/#/aaa/radius/clientg/all
drilldown_one_item
Captured URL: https://admin.myslbb.com/#/aaa/radius/clientg/all
aaa > radius > clients > addclient
aaa > radius > clients > addclient
Route: aaa/radius/clients/addclient
URL: https://admin.myslbb.com/#/aaa/radius/clients/addclient
Overview
This page is a draft SOP reference for the above screen in i2i Core OSS/BSS. It is auto-generated from UI exports and should be reviewed for operational correctness before customer release.
When to Use
- Use this screen for the workflow represented by this route.
- Do not make billing/AAA/provisioning-impacting changes without required authorization.
Typical Workflow
- Verify you are working on the correct entity (Customer/Account/Service).
- Review the current lifecycle state before making changes.
- Apply changes and validate system response.
- Confirm downstream impact (AAA/Provisioning/Billing) where applicable.
Field & Action Hints (Auto-detected)
- Fields detected: identity, IP Address For Client, MAC Address For Client, Client Group, Client Profile, Shared Secret, CoA/DM Shared Secret, Request Timeout (ms), CoA Port, CoA Timeout (ms), Accounting Interval (s), Share Across Organization, Description, Mac Id attribute of the client, NAS Port Id Attribute, Option 82 Attribute, API Type
- Actions detected: Auto, Close, AAA, Radius, Trusted Client, Cancel, Create Radius Client
Validation & Safety Checks
- Confirm identifiers before saving.
- Confirm lifecycle state allows the change.
- Confirm rollback/support path exists for production actions.
Escalation Guidance
- L1: Verify input, permissions, and entity state.
- L2: Validate dependencies and downstream state.
- L3/Admin: Policy/config changes or suspected defect.
Screenshots
create_new
Captured URL: https://admin.myslbb.com/#/aaa/radius/clients/addclient
create_new
Captured URL: https://admin.myslbb.com/#/aaa/radius/clients/addclient
aaa > radius > clients > l
aaa > radius > clients > l
Route: aaa/radius/clients/l
URL: https://admin.myslbb.com/#/aaa/radius/clients/l
Overview
This page is a draft SOP reference for the above screen in i2i Core OSS/BSS. It is auto-generated from UI exports and should be reviewed for operational correctness before customer release.
When to Use
- Use this screen for the workflow represented by this route.
- Do not make billing/AAA/provisioning-impacting changes without required authorization.
Typical Workflow
- Verify you are working on the correct entity (Customer/Account/Service).
- Review the current lifecycle state before making changes.
- Apply changes and validate system response.
- Confirm downstream impact (AAA/Provisioning/Billing) where applicable.
Field & Action Hints (Auto-detected)
- Actions detected: Auto, Close, AAA, Radius, Trusted Client, New Radius Client, Relaod Cache, 103.5.187.18, 49.143.252.226, 49.143.252.59, 49.143.252.60, 49.143.255.172, 49.143.255.173, 49.143.255.226
Validation & Safety Checks
- Confirm identifiers before saving.
- Confirm lifecycle state allows the change.
- Confirm rollback/support path exists for production actions.
Escalation Guidance
- L1: Verify input, permissions, and entity state.
- L2: Validate dependencies and downstream state.
- L3/Admin: Policy/config changes or suspected defect.
Screenshots
default
Captured URL: https://admin.myslbb.com/#/aaa/radius/clients/l
default
Captured URL: https://admin.myslbb.com/#/aaa/radius/clients/l
drilldown_one_item
Captured URL: https://admin.myslbb.com/#/aaa/radius/clients/l
drilldown_one_item
Captured URL: https://admin.myslbb.com/#/aaa/radius/clients/l
aaa > radius > node > l
aaa > radius > node > l
Route: aaa/radius/node/l
URL: https://admin.myslbb.com/#/aaa/radius/node/l
Overview
This page is a draft SOP reference for the above screen in i2i Core OSS/BSS. It is auto-generated from UI exports and should be reviewed for operational correctness before customer release.
When to Use
- Use this screen for the workflow represented by this route.
- Do not make billing/AAA/provisioning-impacting changes without required authorization.
Typical Workflow
- Verify you are working on the correct entity (Customer/Account/Service).
- Review the current lifecycle state before making changes.
- Apply changes and validate system response.
- Confirm downstream impact (AAA/Provisioning/Billing) where applicable.
Field & Action Hints (Auto-detected)
- Actions detected: Auto, Close, AAA, Radius, Node (Interface), New Radius Server
Validation & Safety Checks
- Confirm identifiers before saving.
- Confirm lifecycle state allows the change.
- Confirm rollback/support path exists for production actions.
Escalation Guidance
- L1: Verify input, permissions, and entity state.
- L2: Validate dependencies and downstream state.
- L3/Admin: Policy/config changes or suspected defect.
Screenshots
default
Captured URL: https://admin.myslbb.com/#/aaa/radius/node/l
create_new
Captured URL: https://admin.myslbb.com/#/aaa/radius/node/l
drilldown_one_item
Captured URL: https://admin.myslbb.com/#/aaa/radius/node/l
aaa > radius > sesdis > all
aaa > radius > sesdis > all
Route: aaa/radius/sesdis/all
URL: https://admin.myslbb.com/#/aaa/radius/sesdis/all
Overview
This page is a draft SOP reference for the above screen in i2i Core OSS/BSS. It is auto-generated from UI exports and should be reviewed for operational correctness before customer release.
When to Use
- Use this screen for the workflow represented by this route.
- Do not make billing/AAA/provisioning-impacting changes without required authorization.
Typical Workflow
- Verify you are working on the correct entity (Customer/Account/Service).
- Review the current lifecycle state before making changes.
- Apply changes and validate system response.
- Confirm downstream impact (AAA/Provisioning/Billing) where applicable.
Field & Action Hints (Auto-detected)
- Actions detected: Auto, Close, AAA, Radius, Session Disconnection, Session Disconnect, New Batch, 3/2/2026, Username, 2/2/2026, 1/2/2026, 31/1/2026, 30/1/2026, 29/1/2026, 28/1/2026, 27/1/2026, 26/1/2026, 25/1/2026, 24/1/2026, 23/1/2026
Validation & Safety Checks
- Confirm identifiers before saving.
- Confirm lifecycle state allows the change.
- Confirm rollback/support path exists for production actions.
Escalation Guidance
- L1: Verify input, permissions, and entity state.
- L2: Validate dependencies and downstream state.
- L3/Admin: Policy/config changes or suspected defect.
Screenshots
default
Captured URL: https://admin.myslbb.com/#/aaa/radius/sesdis/all
create_new
Captured URL: https://admin.myslbb.com/#/aaa/radius/sesdis/all
drilldown_one_item
Captured URL: https://admin.myslbb.com/#/aaa/radius/sesdis/all
aaa > radius > set
aaa > radius > set
Route: aaa/radius/set
URL: https://admin.myslbb.com/#/aaa/radius/set
Overview
This page is a draft SOP reference for the above screen in i2i Core OSS/BSS. It is auto-generated from UI exports and should be reviewed for operational correctness before customer release.
When to Use
- Use this screen for the workflow represented by this route.
- Do not make billing/AAA/provisioning-impacting changes without required authorization.
Typical Workflow
- Verify you are working on the correct entity (Customer/Account/Service).
- Review the current lifecycle state before making changes.
- Apply changes and validate system response.
- Confirm downstream impact (AAA/Provisioning/Billing) where applicable.
Field & Action Hints (Auto-detected)
- Actions detected: Auto, Close, AAA, Radius, Settings
Validation & Safety Checks
- Confirm identifiers before saving.
- Confirm lifecycle state allows the change.
- Confirm rollback/support path exists for production actions.
Escalation Guidance
- L1: Verify input, permissions, and entity state.
- L2: Validate dependencies and downstream state.
- L3/Admin: Policy/config changes or suspected defect.
Screenshots
default
Captured URL: https://admin.myslbb.com/#/aaa/radius/set
