channelized bandwidths for logical connections is a feature that's been introduced for Telecom Network inventory in the Washington DC release channelized bandwidths are used in a couple different scenarios the primary scenario would be for a Broadband fiber provider uh to model logical connections for their dwdm Network so you have network connections that have multiple wavelengths of fiber optic signals going over one circuit and logical connection channelization is used to allow each of those wavelengths its own logical connection as part of that parent logical connection so you could have one fiber circuit that has eight different wavelengths going over it and that's done through logical connection channelization let's see how we do that so if we go into our logical connection models we're going to create two different logical connection models the first we're going to call this Optical multiplexor section so this is a a logical connection model that's going to be used to represent the circuit uh that will carry the channelized bandwidths so you can see my model category is set to logical connection if I scroll down I can see that there is a behavior field here that is set to connection if I look at that you'll see that there's two choices the first is connection the second is channel we're going to use the channel connection uh the channel Behavior to Define our channelized uh logical Connections in just a second and then we also need a reference to our logical interface model and that's been done here that's our Optical Channel interface we'll take a look at that in a second so here's our Optical Channel model this is the model that's going to be used to represent the channelized individual wavelengths on that logical connection circuit so again our model category is logical connection and if we scroll down we can see that this time the behavior is set to channel and The Logical interface model referenced here is our Optical Channel interface and so let's go up and take a look at our Optical Channel interface so this is a network interface model different from The Logical connection models so this is going to be a model for our ports Associated where actually not the ports because these are virtual interfaces so it would be a virtual network interface and when we're setting this uh this Optical Channel interface anytime you're setting the channelization on the model you need to or on the interface model you need to set this flag to Virtual and then you can uh say the port bandwidth for this particular one is going to be one Lambda and so we've got the three models that are used used to create these logical connection channel channelized uh circuits the one thing that we're going to do to tie them together is we're going to create these Network model relationships so you can see that on my logical connection model for my circuit I've got two different relationships I've got one relationship that was created uh that's going to assign 48 child lambdas to the circuit and then I've got another relationship that was created for this circuit that it's only going to create eight lambdas um eight channels each for a Lambda or a wavelength so if we drill into the 8 Lambda relationship here you can see that my parent bandwidth is going to be eight lambdas my child bandwidth is one Lambda and it's referencing my Optical multiplexor section model and it's also referencing my child product model my channelized uh logical connection for my Optical Channel so if we go back and take a look at some of the circuits that were created using these models they were done using this uh template so I went and I created a 8 Lambda uh OMS template this is a template that's going to be used when we create a logical connection that has eight Lambda uh eight child channels one for each Lambda and I can see that the related templates associated with this are eight goes from 0 to seven and each of these represents a channel on this on the circuit so let's take a look at one of these logical connections that were created using these models and template so I can see I've got my logical connection and more importantly I can see that if I look at my infrastructure relationships here I've got 1 2 3 4 5 6 seven eight child channels and each of these channels is associated with a wavelength now the naming conventions for uh logical connection channels uh is pretty standard it's out of the box um but you can Implement Logic for your naming so that your channels have some indication as to the particular wavelength associated with that channel like we've done here so that's a quick review of logical connection channelization a new feature from TNI in the Washington DC release thank you