User Tools
support:small_customer_offering_sco
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| support:small_customer_offering_sco [2023/04/28 10:22] – 10.91.110.100 | support:small_customer_offering_sco [2025/05/09 10:24] (current) – [2. Verification and Configuration] 10.91.120.100 | ||
|---|---|---|---|
| Line 14: | Line 14: | ||
| ** | ** | ||
| * - ECD DAS - Chris Nolte - chris@ecd-das.com | * - ECD DAS - Chris Nolte - chris@ecd-das.com | ||
| - | * - KLA Labs (Nom-Ford) - sfoust@klalabs.com | + | * - KLA Labs - Mark Woloszyn |
| - | * - NGEN - Chris Langley langley@ngen.com | + | * - NGEN - Moises Pulido - pulido@ngen.com |
| - | * - Concise - Brian Johnson | + | * - Concise - David Johnson |
| - | * - Shared Access - Phil Eldredge phil.eldredge@machineandtechnologyuk.co.uk | + | * - Shared Access - Allen De Jonge - Allen@machineandtechnologyuk.co.uk |
| + | * - Amazon - Jason Robinett - jrrobne@amazon.com | ||
| + | * - HetNet - Brandon Maderos - Brandon.maderos@hetnet.com | ||
| Line 77: | Line 79: | ||
| ====== Onboarding a Customer - Steps required as of 27th April 2023 ====== | ====== Onboarding a Customer - Steps required as of 27th April 2023 ====== | ||
| - | |||
| - | Get yourself a cup of tea, this is unfortunately quite a drawn out process. | ||
| * Add new cluster to snmp_manager database with name of customer (requires sub-steps below) | * Add new cluster to snmp_manager database with name of customer (requires sub-steps below) | ||
| * Add a new errigal_customer_company to ticketer database | * Add a new errigal_customer_company to ticketer database | ||
| * Add a new region to ticketer database | * Add a new region to ticketer database | ||
| - | * Add a new visibility to ticketer database | + | |
| + | | ||
| * Add a new errigal_customer_company to snmp_manager database | * Add a new errigal_customer_company to snmp_manager database | ||
| + | * (You can now add the cluster in the snmp_manager DB) | ||
| * Add new carrier to snmp_manager database with name of customer | * Add new carrier to snmp_manager database with name of customer | ||
| * Go to userprofile, | * Go to userprofile, | ||
| - | * Again in userprofile, | + | * Again in userprofile, |
| - | * Add a new network element to the database, with the customer name as its name, and "CUSTOMER-NETWORK" | + | |
| * Load a network element into this cluster via excel file loader, go to snmp manager homepage, the one with all the links and alphabetic filtering options and click excel file loader in the toolbar (ask a colleague for a template) | * Load a network element into this cluster via excel file loader, go to snmp manager homepage, the one with all the links and alphabetic filtering options and click excel file loader in the toolbar (ask a colleague for a template) | ||
| - | | + | * Create visibility in userprofile with carrier and cluster created above selected |
| - | | + | |
| * Clear the cache for device trees in snmp manager, at the homepage, click " | * Clear the cache for device trees in snmp manager, at the homepage, click " | ||
| * You may need to wait for a while for the elements to appear in the device tree, move to another task and check back later in the day. | * You may need to wait for a while for the elements to appear in the device tree, move to another task and check back later in the day. | ||
| Line 97: | Line 97: | ||
| * If they still are not in the list, try clearing your browser cache. | * If they still are not in the list, try clearing your browser cache. | ||
| * Do a topology rediscovery on the device you added via loadsheet, be sure to check " | * Do a topology rediscovery on the device you added via loadsheet, be sure to check " | ||
| - | * Add new devices if the customer has more than one by clicking on the cluster | + | * Add new devices if the customer has more than one by clicking on their cluster |
| - | * Sync the network elements to nova by running the elastic replictor bulk import http:// | + | * Sync the network elements to nova by running the elastic replictor bulk import |
| Line 186: | Line 186: | ||
| ====== Adding elements to existing customers | ====== Adding elements to existing customers | ||
| - | Similar Process | + | This section provides a guide on how to add a new network element for an existing SCO customer. |
| + | |||
| + | ==== 1. Topology Discovery: ==== | ||
| + | |||
| + | * Navigate to the appropriate site or cluster within the EMS. | ||
| + | * Run a Topology Discovery using the new network element' | ||
| + | |||
| + | ==== 2. Verification and Configuration ==== | ||
| + | |||
| + | * **Technology and Software Version** | ||
| + | * Verify that the network element' | ||
| + | * If incorrect, update the ' | ||
| + | |||
| + | * **Link Polling** | ||
| + | * Compare similar devices to determine the appropriate 'Link Pollable' | ||
| + | * Apply these settings via the UI or directly in the database. | ||
| + | |||
| + | * **SNMP Settings** | ||
| + | * Ensure the new device is configured to send SNMP traps to Errigal and that the correct SNMP port is assigned. | ||
| + | * __Note:__ SNMP port changes may experience a delay in reflecting in MDC. This can be done manually by running the following command: | ||
| + | |||
| + | insert into snmp_manager.network_element_change_sync | ||
| + | |||
| + | |||
| + | * **Billing** | ||
| + | * Determine the correct ' | ||
| - | If loading using topology discovery, make sure that topology scripts are associating | + | * **MDC Schedules** |
| + | * If required, add MDC schedules directly through | ||
| + | ==== 3. Additional Steps ==== | ||
| + | * Complete the element' | ||
| + | * Add contact details using the SNMP Manager' | ||
| ====== Customer Support ====== | ====== Customer Support ====== | ||
support/small_customer_offering_sco.1682673758.txt.gz · Last modified: 2023/04/28 10:22 by 10.91.110.100
Page Tools
