Importance of Channelized Bandwidth
Channelize bandwidth enables the division of available bandwidth into discrete channels. Having the capability to channelize bandwidth enables the efficient allocation of resources which allow different applications or services to occupy different channels without causing interference which in turn enhances overall network performance.
With ServiceNow Network Inventory Washington release, achieving complete automation just got one step closer. The channelized bandwidth feature enables the following capability:
- Create Channel models
- Create model relationship between Connection and Channel models
- Capability to create Logical Connection template enabling the creation of auto creates channel templates
Channelized bandwidth capability within Network Inventory enables the scalability and network customization to ensure optimum network efficiency by maximizing bandwidth usage.
Channel Representation
ServiceNow network inventory channel representation will be represented within the CMDB data model as logical connections. The below diagram is a sample channel representation where there is a logical connection ( Eq1/Eq2/DS1) which has a bandwidth of size DS1representing the logical connection of the channel and the logical connection Eq1/Eq2/DS3 has a larger bandwidth that supports 28 channels. Furthermore, you can create a DS1 circuit that can be represent individual channels that are contained::contained by Eq1/Eq2/DS3.
ServiceNow has out of the box templates that can be applied to automatically create all these 28 logical channels and the relationships represented in the diagram below which will be used as an example implementation in the following sections.
ServiceNow Channel Implementation
- Navigate to the Network Inventory Workspace
- From the List Menu, under Inventory Models> Logical Connection Models
Within the optical channel form, there is a behavior characteristic
-
There are two types of behaviors (connection and channel) and in this scenario channel is selected
-
Logical Interface Model also needs to be added in this example.
-
- From the List Menu, under Inventory Models> Logical Connection Models >Optical Multiplexer Section
- Click on More > Network Model Relationship in the Optical Multiplexer Section form.
- Click on the 8 Lambda OTS Channel
- Within the 8 Lambda OTS Channel, the compatibility can be configured
- Parent Product Model and Child product model can be seen below.
- Moving back to the Optical Multiplexer form, click on New to define additional relationships by completing the form as shown below:
- Name: 48 Lambda
- Relationship type: Logical connection to channel
- Parent Bandwidth: 48 Lamda
- Parent Product Model: Optical Multiplexer Section
- Child Product Model: Optical Channel
- Child Bandwidth: 1 Lambda
- Sequence: 2
- Click on Save
- The additional relationship 48 Lambda has been added to the Optical Multiplexer Section
- Return to the network inventory templates and create a new Inventory template there.
- List > Network Inventory Templates > Inventory Templates.
- Select New
- The following template can be completed:
- Name: 48 Lambda OMS Template
- Inventory model: Optical Multiplexer Section
- Parent Bandwidth: 48 Lambda
- Child Bandwidth: 1 Lambda
- Click on Save
- By creating a template, it will automatically create the 48 Channels seen below.
Instantiating a Logical Connection to Establish Bandwidth Channelization
Defining a new logical connection is available by a simple out of the box template.
From lists navigate to > Changes > All and select NEW
There is a new out of the box template “Create Logical Connection” available and can now be selected
- Select SAVE when the template appears
- Once the template is Saved, the tab Change Task appears
- Click on the Change Task tab and then click on the Task Number to go to the topology Design and Assign form.
- The following can be completed as an example:
- Logical Connection Model: Optical Multiplexer Section
- Bandwidth AtoZ: 48 Lambda
- A end Site: Frankfurt Pop
- A end Equipment: FRNFTELC1/7360 FX-4/3
- Parent Port A: Gig-1
- Logical Connection Template: 48 Lambda OMS Template
- Bandwidth ZtoA: Frankfurt POP
- Z end Equipment: FRNFTELC1/7360 FX-4/3
- Parent Port Z: Gig-2
- Click on Submit
- Once submitted, the logical connection is created along with creating the channels as per the related templates.
- Return to the Change Task initially opened to see the Configuration Item that has been created.
- Click on the “i” to open the record
- Within the record, all the 48 channels have been created as logical connections
- Return to the previous form and click on a channel
- Click on Network Diagram to see the visualization and the click on Connection Element to see the relationship
