Introduction to IxNetwork NextGen Protocol Framework (NGPF)

hello and welcome to this IX Network video tutorial on the new feature called next-gen protocol framework introduced in IX network 7.0 also known as ng PF

this feature is a new framework for protocols at iyx network already supports and will support in the future as you can see in the screenshot here the new framework is very next-gen not

only visually but in the way that protocols will be built and used by our customers next-gen products and their customers next-gen networks here's the

agenda for the psychic network video tutorial this video tutorial will be broken up into five chapters each chapter going into different aspects of the next-generation protocol framework

chapter one is just a few slides on what is ng PF why did we decide to build a new framework and what are its benefits to our our customer base chapter two

goes into the new and gpf terminology there are some new terms that go along with ng PF and it's very important to understand them when you get into the GUI itself which is chapters three four

and five chapter three is where we start to configure protocols in the next-generation protocol framework using IX network how to add them how to modify

how to use the predefined resources scaling customizing etc chapter 4 is where we start the protocols and we look at the first session status the device

group status the color coding red green and yellow and basically what are the new statistics and in real time and how do we drill down into the protocols to

look at first session stats and finally in chapter 5 we'll be showing you how to build traffic using ng PF endpoints in the traffic wizard there's a new employee selection tool specifically for

in gpf endpoints and this chapter will show you how to use that feature in this chapter we're just going to cover a couple slides on what is and gpf why did

we build this new framework and what are its advantages to our customers so what is IX Network and GPS again ng PF is a new protocol framework they are not new

the calls there the existing protocols we already have an IX Network except we've migrated some of them at this point to the new protocol framework so definitely an upgrade to the framework

we have a lot more flexibility a lot more ease of use to scale a lot more granular control a lot more control at a range level what we call a device group this framework was definitely built to

meet and stay ahead of our customers requirements in terms of protocol stacking in terms of building real world networks with a visual representation of those networks

so we're moving into the next-gen protocols and technologies in this framework will will help help you get there definitely designed to provide

consistent workflow across all protocols what are you doing in broadband or are you doing routing or you're doing ipv4 ipv6 at the ACP it's a consistent

framework for all the protocols and they're all going to get the benefit of the features that the framework provides and again designed to work more closely simulate dynamic customer environments

so more stuff in real time dynamic changes and again a a lot quicker to to configure and get network to to that

next-gen scale okay the next question might be why a new framework for iyx network what was wrong with the old one or wire why did this need to be done

well the current iyx network protocol framework is not optimized for ultra high scale it does not scale well you can only have so many protocol

interfaces and the GUI starts become sluggish high port counts high scale the new framework is definitely more optimized for high much much higher

scale a small footprint environment as far as memory and CPU and again the scale is a definitely next-gen the

framework is not flexible or realistic currently today in iyx network with the existing protocol framework we can't stack protocols very well all the

protocols have to be configured in the silo OSPF by itself LDP by itself bgp by itself and we cannot emulate true dynamic behavior subscriber behavior

like in a broadband environment where you start the sessions and you start the traffic right away so this new framework takes care of all that where we have the

the stacking in a visual environment for true real world emulation real world subscription and it does a good job at that as you'll see the current framework

is about eight years old now so while it does do well as it works today we needed to do next-gen for next-gen protocol

stacking next-gen networks and as our application traffic over routes needs grow we needed a new framework for that so this framework will definitely take

care of that and then the current protocol has an inconsistent workflow the routing is configured and looks a whole lot different in the GUI than the access all the new framework what it

combines all the protocols into a single consistent workflow a consistent feature set and it's able to suit the complex test scenarios that the existing

previous workflow and framework could not okay and lastly what are what does this all mean what are the what are the key building blocks of ng PF and one of

the benefits well you definitely have the visual visual element which you're going to see in the next chapter where we get into the GUI you're going to see a visual representation of all your

protocols and if they're up or down and stacking and all that stuff is in a nice visual environment consistent workflow we talked about of all the protocols a

new framework obviously we provide that topology based configurations to produce the application learning curve so you can see it and really feel your

different protocols all working together to to understand the topology scalability we can achieve up to a hundred percent improvement import scale and then at least 50 percent improvement

in protocol scale per test so a lot more performance for our protocols in this new framework and we also reduce the memory of the client

machine that runs the eyes Network goodbye 30% with the new protocol frameworks very flexible protocol stacking granular per session control as

well as a range concept so you get them both all at the same time assistant level stats you get dashboard again this framework will allow a truly converse

layer 2 to 7 environment for testing dynamic control plane of protocols and bringing them up and down in real-time

and provides the framework for more dynamic traffic control for real-world traffic ok in this chapter we're going

to cover ng PF terminology this is a very important chapter to understand for those that we will be using the ax network GUI and the new next generation

protocol framework because it really helps you with the building blocks of how the new terminology results in a visual representation of your network as

well as those same elements are used in the configuration so you're really going to need to get to know them to use the next-gen protocol framework the first

highest level of ng PF in the IX network GUI is the scenario view so in the new 7 starting in 7.0 you'll see the scenario

view on the left hand side of your screen and it basically represents the entire ng PF section of the GUI note that you'll still have the existing

framework in the IX network session we're not getting rid of that we've just labeled it classic protocol framework which is your existing OSPI bgp LBP and

everything else but we now have the new scenario node which will house the next-gen protocol framework that you can use for the protocols that are supported there if you like so you really have a

choice you can you can use the new next-gen protocol framework the classic framework or both the only caveat if you're going to use both is that you

cannot run the next-gen protocol framework and the classic framework on the same port at the same time but if you separate and via ports you can run both at the same time in the same IX

Network session you just have one scenario and in that scenario you'll have multiple topologies device groups etc and we'll get into those terms in a minute you can have one or more

topologies as shown here there are short apologies of different protocols in each and again you can only have one scenario per test the next three slides are the

three main components of protocols using ng PF they are topology device groups and devices the topology as shown here is the highest level and inside the

topology of the device groups and the devices a topology is basically a block of similarly configured ports the key word here is similarly all ports in

anthropology by default are all running the same protocols and the same number of devices per protocol the details of devices can be unique such as addressing

and protocol specifics but the number of the devices and the protocols running on each port are all the same the advantage here is quick easy and scalable

configuration for light ports examples are broadband subscribers CEO outers or IP / multicast hosts if any important

needs to be unique just put it in its own topology the example screenshot here there are four ports each with 20 routers for a total total of 80 devices

in this case the device group is a stack of OSPF routers so in this case it's 80 OSPF routers each of those 80 OSPF

routers has 10 device per router for a total of 800 routes or ipv4 prefixes so that's how a topology is built I can add

more device groups of the topology if I want I can change the multiplier we'll get into that later and I can also add and remove ports to

the topologies inside the topology you have device groups a device group represents a logical group of devices and a role for those devices such as hosts or routers each device group

consists of a protocol stack as you can see highlighted here we have our OSPF ak highlighted that could be a PvP stack or whatever you want it to be just have to have the right building blocks to

build whatever protocol you want and then of course within that device group is one or more devices or sessions in this case the multiplier here which

we'll get into later signifies there are twenty devices per port so in this device group eighty devices across four

ports and twenty devices per port and then as you can see if you click on in the GUI as we'll see later if you click on the device group itself you'll see

the configuration grid at the bottom and you'll see the device the Ethernet stack the ipv4 stack and then the OSPF router and its interface all in different tabs

you can also see how within the first port here in the screenshot at the bottom you can configure every device with unique parameters and characteristics via the configuration

grid and then within anthropology within the device groups are the devices themselves each device represents a per session within a device group as

mentioned earlier in the topology slide the devices are configured on all ports assigned to the topology and each session can be independently controlled as you can see in the screenshot below

you get the per session a row each session can be started and stopped it shows you a status information field interface state and LSP F neighbor state

so each session can be controlled individually or at the port level or at the device group level or at the topology level or at the test level so

there's plenty of control from the highest level to the lowest level as far as the protocols and devices using an GPS okay and the last slide here before

we get into the GUI in the next chapter is the terminology for multiplier and network groups the multiplier is a scale

ratio for devices within a device group so as you can see on the right hand side here the number of ports times the multiplier equals the number of the

vices within the device group so in this case there's two ports there's 50,000 devices per port for a total of 100,000

devices in this case their IP v4 devices because this is an IP v4 device group so as you can see it's very very quick and easy to scale just by clicking on this

box changing the multiplier and next thing you know you're you can scale from a few hundred to thousands and even hundreds of thousands as what's

supported the next term here is network groups Network groups is basically route pools ipv4 ipv6 route pools they can be

advertised through through the protocols like OSPF and of course the route pools can be used by multiple protocols as you can see here this is kind of like route

ranges behind the routers themselves and you can see at the bottom of the grid here where you configure the the route the starting address the routes and the

ending address okay in chapter 3 we're going to get into the GUI and learn how to configure protocols using the ng PF framework we'll show you how to add

protocols modify them we have some predefined resources that you can just drag and drop into the scenario view we have some new raid options with ng PF

and show you how to customize and scale your configuration using a new pattern tool and the multiplier okay here we are on the ieee eccentric GUI and starting

an IX Network 7.0 we now have the scenario button here for the next-gen protocol framework so you can go inside the next-gen protocol framework I've

already minimized the statistics so we don't have that window pane shown that way we can focus on the visual representation view up top as well as

the configuration elements on down below so the add ports and protocols into the scenario you can you can either go back to home and add ports the way you did

before or you can go in a new topology and add ports from here click on our chassis highlight the ports you want to use in

this case I'm just going to add two ports for now and I'm going to move them over into a topology and next I pick on

the what's protocol the one want in this topology for those ports so I'm just going to select ipv4 as a good example you'll see the list of current protocols that are supported in ng PF there are

much more coming from the existing framework into the new framework this is just a list as of right now so as soon as I click finish I'm going to see that

two ports are not one and two we're put in a topology called topology one it's important as soon as you add topologies and device groups that you

name them this will be useful for the configuration grid as well as when you get to the traffic wizard so I'm just going to call it my ipv4 topology one in

my ipv4 device group one so what's been created here is my two ports by default two multipliers ten as you can see here when I click on my device group I see I

have the devices itself and I can enable and disable per device I have the ethernet layer which I have shown me all both ports and unique MAC addresses per

port and I have the ipv4 layer with some default addresses in addition to clicking on the device group to navigate through the grid I can also click on the stacks themselves the Ethernet stack and

I can just see that the Ethernet stack or the ipv4 stack by itself but in this case I kind of like to see the device Ethernet I an ipv4 altogether on the

left hand side of the screen you can also see where we have that all the next-gen protocol stack so in this case I only have Ethernet and ipv4 configured in the scenario view so those

are the only two stacks I will see but if I also have DHCP device troops or OSPF device groups in topologies I'll see those stacks as well the difference is when I click over here on the left

hand side I'm not going to see the scenario visual picture at the top I'm just going to see that duration list for not just one topology a one device group but for all

topologies and all device groups for all stacks so here's my Ethernet stacks for all topologies and all device groups my ipv4 stacks are all topologies and all device groups and again I also have the

configuration options at the top to configure them this way for all ipv4 stacks in the test versus a scenario view or I can just configure the the one

stack in the one device group at a time another very nice way to add protocols and topologies into the scenario view is simply by dragging and dropping them on

the right hand side of the screen that comes with IX network are some resources you can just drag and drop we actually have one resource for all the protocols that are currently supported you can see

the DHCP client server we have ipv4 ipv6 Auto config and OSPF and pppoe so the way to do that is just drag and drop now

for for the demo I'm actually going to pull up a new config and then drag it in to show you how that works okay so we have a new config so I'm just

going to come down here to the same ipv4 resource and just drag it and drop it the nice thing about these resources is once you once you have them and have saved them you can just do that via the

resource manager on the top here just to save and they'll be added over here into the right-hand window where you can just drag them and drop them in the future so once you have a topology you want to

save or group of topologies just save them off as a resource and pull them in anytime now in this case the one I pulled in has four ports offline ports

so let's just add online ports to these offline ports and we can get started you go back to Arielle you see the ports come up here

there's some color coding going on and now we have a device group with four ports forty MAC addresses and forty IP

addresses but now with those forty addresses we can see that they may not actually have the right IP addresses to actually work with the DD T so the next

feature I want to show you with the next-generation protocol framework is the incrementing tool the pattern tool at the top of every grid so you can see here in the device there's a blue row

here Ethernet there's a blue row ipv4 there's a blue row which is a is a pattern tool for it all of the devices in the device group so let's configure

our IP addresses using this new tool I click on the top row I see their seat the tool and I'm going to put in my

first IP address 51 4 2 1 a 2 now increment by 1 and my porch step is as soon so so what you're going to see here

is that with this tool I can increment all the devices in the device group across all the ports so it's a very nice tool for that and I'll show you some

other features in it in a second let's do the same thing for I don't want to increment at it all it's a gateway what

I do want to increment the port step and so I have that there so now I see all of my configuration is done and it should be very easy to see if we can ARP once

we start the protocols Ethernet looks good device looks good the other thing to notice here is that if I were to change the multiplier so my pattern tool is already there and I my pattern is

from 2 to 11 H port if I were to change the multiplier to a hundred for each port it's the multiplier the incrementing tool is automatically going

to give me a hundred addresses per port in order and everything is going to be configured for me so it's very easy to scale using the multiplier up and down and

one thing and secondly the the incrementing and the pattern tool is very useful and to go across all devices and all ports in the device group a

couple other quick grid functions here is if I make a change to the pattern let's say I make this a 8 it will show me here that this this particular value

is out of pattern and the very top row of the pattern will show the same thing so if I do have to make some customized

adjustments I can and it'll it'll show me a little value here that this is not part of the normal pattern if I made a bunch of those changes and I want to send them back I just clicking on that

again it sets them all back okay now let's move on to the next chapter where we will start the protocols and look at status and statistics okay in this

chapter we're going to look at the ngpa protocol status and statistics we're going to take our existing configuration we're going to start it and we're going to see all the visual color coding that

comes along with it how to start it at a very granular per session level as well as at the very high level and everywhere in between we're going to watch how you make changes on the fly

restart failed only sessions and basically all the new granular protocol options that are available for each and every session will also look more down in the statistics layer and look at the

real-time statistics the drill-down statistics aggregated and per session ok we're back in the GUI now and I've actually taken the four ports that we're

in the ipv4 topology 1 and I've taken two of those ports out and put them in their own topology now the reason I might need to do this is because of two things number one is I have a different

multiplier so for some reason I want these two ports to only have 5 IP hosts and I want these two ports to have 10 so therefore that they must be in separate topologies or the second reason I would

have to do that is because maybe topology 2 has a different protocol requirements so maybe this needs IP and DHCP in this topology either in two different device groups or in the same

device group so that's another reason I would have to have separate topologies but there isn't a reason I did this and I'll show that to you a little later but right now we want to show you the protocols on what

they look like when they're running so shown in the screen below here I've clicked on the I device group one and the ipv4 and show you how to start those at different levels

first of all in if I want to start it one at a time I just click on the button there I can start the entire stack either by clicking right here which will

start everything in the ipv4 device group and you can see right away that the Ethernet went to green the ipv4 went to green all the sessions went to up and

the the gateway actually shows right there in the in the grid the MAC address of the Gateway I could also start one stack at a time for example if I just

stop this two stack I can just hover over the Ethernet and start that now since this is a basically a layer 3 stack it doesn't really do anything meaning I don't send out any frames but

I can go back up to the ipv4 stack and start that and that will also start the ipv4 stack also note that if I want to just start the ipv4 stack or whatever

the highest stack in the device group it'll automatically start the lower stack at the same time or right before it before it starts to stack that I've chosen to start I just go over here to

my topology - I can start at that device group level or I could go to the whole topology where you might have multiple device groups and start there so let's let's just try that one click on the device group there go over to IP and

we'll see that the 10 IP addresses in that topology have started and lastly the other ways to start it as at the up here on the ribbon bar I can start the

started device groups that I selected or I can just start all the protocols with this drop down and if you click on the white space here you'll see I can start the topologies of advice groups from

here to see kind of the aggregated status obviously if everything's green that means everything is up but if you want to see aggregated status you could always click on the

I screw maybe on one of the stacks and if you collapse it to just show the port level you'll see that first of all each port will tell you how many of how many are up and also at the highest level

will tell you how many of helmand your ups just to show you how the color coding works obviously green is fairly obvious if all sessions are started and up then they're all green if for some

reason you made a mistake maybe when you first started it let's just make a let's just change it to 1 and hit OK first thing I want to show you is while the protocols are running if you make a

change in the grid the the bulbs thing here shows that it hasn't been applied yet so when you see the bulb you this green apply button will come on and this

is how you make changes on the fly so the sessions are up I'm going to apply the changes to have a incorrect gateway and what you're going to see is that

they're all going to go down so basically now you can see the status of the ipv4 went to red the green is still there but the for the ethernet but all

the sessions are down if you want to get partial sessions up I could fix this go back to 51 here so they're all correct

and maybe change one of them to an incorrect hit apply and now we see that all but one are up so you can see

obviously which one is which ones are up and which one are down if I collapse them I can see that this one actually has the down session so I can drill into that it gives me the the reason it

failed and I also see the ipv4 stack is yellow meaning there's at least one session that has a has a problem the other thing to note is if I stop a

device group the grey color coding just means that the sessions are not started ok I forgot to show you one thing earlier which is protocol stacking

protocol stacking is very easy in the NC bf framework I can go to this ipv4 stack and add add another layer here's my layer thing actually I can go to any

stack and add a layer if I were able to Ethernet stack and add later it will show me the available stacks I might say ipv6 and now I have dual-stack hosts with one

eat one MAC address and two IP VoIP stacks Justin I bleep that one very simply and easily and what I want to show you here is how to add a stack on

top of ipv4 if I hit the add stack button it will show me the available stacks right now it's just OSPF and dhcp server I want to add oh s PF stack it

automatically adds it for me it gives me the default router configuration the default interface configuration and it's all done for me I know my IP layer

already works I can even start that if I want to just to make sure that my IP layer started it did before and it still does but if if I

want to add routes to that OSPF routers now I have five OSPF routers I can just click the add routes I want to add ipv4 prefixes which is which are routes and

now I have my network group with a certain number of routes I'll say I want ten routes per router so now I have two

ports each with five routers in this case I changed from ipv4 host to OSPF routers and then each of those for a total of 10 routers and then the 10

routers with the 10 route each gives me a hundred total routes I can see my route range here if I want to change something like prefix length I can and I

can see how they were how the route ranges were distributed across the routers and I can see my first address my last address and the count right there

now just as usually I can click on the device group hit start protocols and see if my OSPF routers come up I knew that

my ipv4 stacks would come up because I saw that earlier but let's go down to the OSPF routers which are not up the interfaces are not up but I can see status here right in the configuration

grid the neighbors are not on the full state actually I see my problem now my area is actually 4 so I'm going to change that to 4 it goes bold me

you have to hit the apply button for on-the-fly changes and after I change them to four I'll wait to see at the OSPF sessions come up and sure enough

they do so I get what's nice is I get all the status and state information right here in the configuration grid we haven't even gone to the statistics

grids yet this is just full status D our other state and any information typically if it went down if it's down is where you get the information here

but I can see now that my OSPF routers are up and obviously my routes have been advertised as well the ng PF framework

also allows for a lot more per session granular protocol operations for example for these OSPF sessions that I'm showing now I can right mouse click and do

something like stop hello messages resume hello abort the session get learned info just for that specific session so for example if I stop hello

here we should see in about 40 seconds which is the dead timer for the protocol the session go down so I'm going to stop that and then we'll wait 40 seconds to

see what happens and sure enough this session did go down the neighbor is not in full state the neighbor state is initialized and we can

now resume and it will come back up and there we go another operation here is as I mentioned earlier getting the learned

info I've already turned on allowing learned info on session 1 so if I come back to session 1 right mouse click and say get learned info it'll show me the

learned info for that router I can even refresh the state right here so it's a new view to look at all the different learned information from that router

from the D UT these operations are also under actions here at the top so you have those available on the ribbon bar

and the final thing the ng PF framework gives you is protocol options so now under the protocol options you can see that for Ethernet and IP and OSPF we

have all the rate controls for every protocol and the report so we see the start and stop rate of the protocol sessions for ipv4 you can also have the

ARB rate the start rate and stop rates so each protocol will also have those options as well the last thing I want to show you in this chapter is the actual

statistics for the ng PF we have new statistics for ng PF protocols and to get them I'm going to re-enable the statistics pane I'm going to actually

minimize collapse the configuration grid with this button so I have some more real estate pull this up here to see my

statistics so right away let's just look at all the ng PF views which are actually already turned on you can see I have next-gen protocol views

specifically for ng PF protocols I have the protocol summary so I can see all my ipv4 sessions that are total up and running I think this one I just configured the gateway and that's fine

and then how many routers I have running I can also look at the port summary and I can see how many total sessions are up are down so I get my aggregated use from

a protocol summary I can also drill down much like in traffic traffic statistics I can also drill down with an GPS now these are all real-time views so well up

they'll go up and down let's see if I stop the stack here we should see this go down to a just lost 20 sessions that

are not started 10 or up in a total of 30 and then if I click that and start it again I can see the real-time go back up to 29 sessions with one down for OSPF

routers I can just right mouse click just like I do in traffic statistics and I can say let's look at the per session stats for my OSPF routers there was also

some other options there the first thing to notice is the refresh so all of the per session stats are refreshed only

statistics so but when I drill down I can get full status on each of my OSPF routers how many hellos were sent receive what's the current status

databases sent received and all the rest of the statistics that you might need especially when you're troubleshooting as you saw on the configure it's a few minutes ago I get a lot of my status

there there may not be a need to go into the full statistics for the number of packets sent received for each OSPF our session but if I need that they're there

and I can just drill down I can hit the Refresh statistics button it'll just automatically update all the stats on the bottom left here shows the last time since I refreshed and again I can hit

the refresh button down here or the refresh button at the top of the window and the ribbon bar to refresh and the refreshes are very fast it's hard to even notice them happening but you can

see a little bar at the bottom as I as I click here the last chapter in this iyx network video tutorial is building traffic using ng PF endpoints in the

traffic wizard there's a new endpoint selection tool when you want to select devices and sessions within the device group or within the stack if you want to select the entire stack that's still a

single checkbox but there's a new tool if you want to drill down into endpoints within that stack we're going to cover how do you send traffic from sources and

destinations using the next-gen protocol framework endpoints so in this case we have a 100 OSPF routes and 20 ipv4 addresses on two ports over here and two

ports over here so we're going to figure out how to send traffic to these using the traffic wizard the traffic wizard is basically the same as before there's only one difference which is in the

endpoint selection page which is the first page all the other pages are exactly the same so first thing we're going to see is when we go into the traffic wizard we're going to see our

topology and our names this is why it's important to name the topologies and device groups with a certain name so that you can know what - what you're looking at when you get into the traffic

wizard so let's expand those and in this case let's go from the OSPF route ranges so if you remember we had 200 I'm sorry

100 route ranges are as the source as a destination let's go to the twenty ipv4 addresses on those two ports so from two

ports to two ports and go down to tracking let's just select source destination value pair which means source destination IP pair it finish and

start and what we're going to see in the traffic the traffic item first of course is the first place you want to go to see if there's any high-level loss and

there's not so no loss latency is about eight microseconds and let's look in the flow stats and this is what we expect

right from port threes going to port one because we had one-to-one mapping in the traffic wizard and from the routes on port three to the IP addresses on port

one so that's exactly what we're getting a hundred rows of 50 routes to the ten IP addresses on port 1 from 3 to 1 and

from 4 to 2 so that's pretty straightforward on sending traffic but now what I really want to show you is how to send traffic to a subset from 3 to 1 and a subset

four to two so not the entire range but a subset of that let's stop traffic go back into the

traffic item double click let's just go ahead and delete that endpoint set so we can start again and this time I only go

from only the first ten routes in each of the port so instead of all 50 and 52 10 and 10 on the other side let's go just ten routes and ten routes on ports

three and four to the ten IP addresses and ten IP addresses on port one two so to do that you still go into down to the ipv4 prefixes which is all 100 routes

here and if you want to select them all that's what we just did if you want to select a subset you got to go into here so this is the new endpoint selection

tool by default it since we selected the check box before we actually went into it it's actually showing you all 100 addresses will be selected if you want

to select a subset you can use the drop down here and say what's my first port but I want to start with I'm going to go three I am on both ports to do that one

I do want to start at the first address as my my source from port 3 but I only want to do the first 10 addresses on each port so when I do that it

automatically selects my last address on on that port 3 and it also selects the first 10 on port 4 so the bottom portion

of your screen is really just a graphical representation of what part of the endpoint did you select so I've only selected really I guess the first 10 out

of 50 so that's one fifth of the addresses on port 3 which is the top row and one fifth of the addresses on port 4 which is the bottom row and that's just a representation of where I selected

another way to do this if you wanted to you can certainly add more and this would be a just a different way to do it just let's just do the first one is port

3 and the second one is port for you put 10 on each and that basically accomplishes the same thing the reason that we had to do it in this

particular format it's because in ng PF framework we're all able to do tens and hundreds and thousands and hundreds of thousands and millions of rows in the GUI it's a very scalable GUI but the

traffic wizard itself is it's just not it's just not easy to scale to a million rows so it's a much easier way actually to select ranges of endpoints with this

tool then it will be to scroll up and down in the traffic wizard so it's actually a better way to do it you just have to get used to it so you just select okay so as you can

see I've only selected 20 addresses it does give me a readout there and then I go over here at ipv4 and I could just select them all because I don't there's only 20 there so I'm going to go 20 to

20 if I wanted to go a subset I could just again click here and then do the same thing as I already did for my destination but I don't need to do that

so I just add that as before my flow tracking is still there if I want to see my preview I can see I should see and I do only the first 10 addresses the first

10 routes going to the 10 addresses on from this would be port 3 2 1 and then on 4 4 2 2 you have the first 10 raus to

the the 10 ipv4 addresses finish and start and there you go there's my 20 rows 10 of them from 4 3 2 1 10 of them

for 4 2 - there's my source destination IPS and I'm getting no loss so that concludes the video tutorial on the next generation protocol framework introduce

a nice network 7.0 thank you