Developer & Integrations
Routes under: dev
- dev > netdev > addbysubnet
- dev > netdev > all
- dev > netdiscdev > all
- dev > settings > firm > all
- dev > settings > mg > add
- dev > settings > mg > all
- dev > settings > model > add
- dev > settings > model > all
- dev > settings > profile > all
- dev > settings > rule > all
- dev > site > add
- dev > site > all
dev > netdev > addbysubnet
dev > netdev > addbysubnet
Route: dev/netdev/addbysubnet
URL: https://admin.myslbb.com/#/dev/netdev/addbysubnet
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: Device Type, Device Profile, Device Model, Device Group, Status, IP with Subnet mask
- Actions detected: Auto, Close, Network, Device, Cancel, Submit
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/#/dev/netdev/addbysubnet
dev > netdev > all
dev > netdev > all
Route: dev/netdev/all
URL: https://admin.myslbb.com/#/dev/netdev/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)
- Fields detected: Search Field, Search Type
- Actions detected: Auto, Close, Network, Device, Add Servers Subnet, New Server, Clear, DBCG1DC4704D, DBCG1DC47055, DBCG1DC4705D, DBCG1DC47035, DBCG1DC4703D, DBCG1DC47065, DBCG1DC46ECD, DBCG1DC47025, DBCG1DC4701D, DBCG1DC46EC5, DBCG1DC46E8D, DBCG1DC46EA5, DBCG1DC46ED5
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/#/dev/netdev/all
ui_tab_1
Captured URL: https://admin.myslbb.com/#/dev/netdev/all
common_tab_1
Captured URL: https://admin.myslbb.com/#/dev/netdev/all
common_tab_2
Captured URL: https://admin.myslbb.com/#/dev/netdev/all
drilldown_one_item
Captured URL: https://admin.myslbb.com/#/dev/netdev/all
dev > netdiscdev > all
dev > netdiscdev > all
Route: dev/netdiscdev/all
URL: https://admin.myslbb.com/#/dev/netdiscdev/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, Network, Discovered Device, Clear, 12345989DB29C3259, Auto Registration Failed, 12345989DB29C1169, 12345989DB29D0A99, 12345989DB29C1889, 12345989DB29D02C9, 12345989DB299D7E9, 12345989DB29A5029, 12345989DB299C549, 12345989DB29A47A9, 12345989DB29A4459, 12345989DB299C4F9, 12345989DB29A4FA9, 12345989DB299C2A9, DBCG1DC3A3B4
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/#/dev/netdiscdev/all
drilldown_one_item
Captured URL: https://admin.myslbb.com/#/dev/netdiscdev/all
dev > settings > firm > all
dev > settings > firm > all
Route: dev/settings/firm/all
URL: https://admin.myslbb.com/#/dev/settings/firm/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, Network, Settings, Device Firmware, Add Firmware
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/#/dev/settings/firm/all
create_new
Captured URL: https://admin.myslbb.com/#/dev/settings/firm/all
drilldown_one_item
Captured URL: https://admin.myslbb.com/#/dev/settings/firm/all
dev > settings > mg > add
dev > settings > mg > add
Route: dev/settings/mg/add
URL: https://admin.myslbb.com/#/dev/settings/mg/add
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: Name, Description, Device Type, Activity Type, Activity, Execution Interval
- Actions detected: Auto, Close, Network, Settings, Monitoring Group, Add Device, Cancel, Submit
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/#/dev/settings/mg/add
dev > settings > mg > all
dev > settings > mg > all
Route: dev/settings/mg/all
URL: https://admin.myslbb.com/#/dev/settings/mg/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, Network, Settings, Monitoring Group, New Monitoring Group, TR069 Power Monitoring
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/#/dev/settings/mg/all
drilldown_one_item
Captured URL: https://admin.myslbb.com/#/dev/settings/mg/all
dev > settings > model > add
dev > settings > model > add
Route: dev/settings/model/add
URL: https://admin.myslbb.com/#/dev/settings/model/add
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: Name *, Description, Model Number *, Model Vendor *, Device Type *, Status *, Select Device Model Image
- Actions detected: Auto, Close, Network, Settings, Model, Submit
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/#/dev/settings/model/add
create_new
Captured URL: https://admin.myslbb.com/#/dev/settings/model/add
dev > settings > model > all
dev > settings > model > all
Route: dev/settings/model/all
URL: https://admin.myslbb.com/#/dev/settings/model/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, Network, Settings, Model, New Model, BDCM GP1705-2GV 0055B1 ONT Model, HWTC Router_123 40BB56 ONT Model, HWTC Router_789 00053B ONT Model, HWTC Snet-128s A68F06 ONT Model, PPCT PPCT 64FB92 ONT Model, Realtek HGU-V210-4AC 4CAE1C ONT Model, TP-Link IGD E0D362 ONT Model, TP-Link XC220-G3v DC6279 ONT Model, XPON SM009 XPON ONT Model
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/#/dev/settings/model/all
default
Captured URL: https://admin.myslbb.com/#/dev/settings/model/all
drilldown_one_item
Captured URL: https://admin.myslbb.com/#/dev/settings/model/all
drilldown_one_item
Captured URL: https://admin.myslbb.com/#/dev/settings/model/all
dev > settings > profile > all
dev > settings > profile > all
Route: dev/settings/profile/all
URL: https://admin.myslbb.com/#/dev/settings/profile/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, Network, Settings, Profile, BDCM-GP1705-2GV-0055B1 Profile, Internet Gateway Device v1.0, HWTC-Router_123-40BB56 Profile, HWTC-Router_789-00053B Profile, HWTC-Snet-128s-A68F06 Profile, PPCT-PPCT-64FB92 Profile, Realtek-HGU-V210-4AC-4CAE1C Profile, TP-Link-IGD-E0D362 Profile, TP-Link-XC220-G3v-DC6279 Profile, XPON-SM009-XPON Profile
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/#/dev/settings/profile/all
drilldown_one_item
Captured URL: https://admin.myslbb.com/#/dev/settings/profile/all
dev > settings > rule > all
dev > settings > rule > all
Route: dev/settings/rule/all
URL: https://admin.myslbb.com/#/dev/settings/rule/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, Network, Settings, Device Association Rule
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/#/dev/settings/rule/all
drilldown_one_item
Captured URL: https://admin.myslbb.com/#/dev/settings/rule/all
dev > site > add
dev > site > add
Route: dev/site/add
URL: https://admin.myslbb.com/#/dev/site/add
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: Site Level *, Site Name *, Site Code, Status *, Physical Location *, Address Line 1 *, Address Line 2, Pincode, State, City, Latitude, Longitude
- Actions detected: Auto, Close, Network, Site, Cancel, Create
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/#/dev/site/add
dev > site > all
dev > site > all
Route: dev/site/all
URL: https://admin.myslbb.com/#/dev/site/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, Network, Site, Add Site, Clear
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/#/dev/site/all
ui_tab_1
Captured URL: https://admin.myslbb.com/#/dev/site/all
common_tab_1
Captured URL: https://admin.myslbb.com/#/dev/site/all
common_tab_2
Captured URL: https://admin.myslbb.com/#/dev/site/all
drilldown_one_item
Captured URL: https://admin.myslbb.com/#/dev/site/all
