One alternative would be to run each VPC in its own window. Now they double-click on VPC1 - when the window opens, the ping will still be running. Let's say someone has opened VPC2 and has issued the command to dos continuous ping, like: If the console window is already open, it should NOT open a new window, but simply make the existing window the focus window and issue a command to make the correct VPC the focus VPC. So what happens when I double click on say VPC2? Does a console window open? And then if I double-click on VPC1 next, what happens? What about if I double-click on VPC2 again?Īt the moment my thinking is this - but it has a problem:ĭouble-clicking on a VPCs icon should open the VPCs console window and issue a command to make the correct VPC the focus VPC. And this means that I can run scripts in this one window that involve multiple VPCs. But with VPCs, once console window gives you access to all 9 VPCs. With routers, each router gets its own console window. What happens when you double-click on a VPC icon? When you right-clicked on a VPC and chose Configure, the only options you would see would be:ģ. The next time you dragged a VPC on it would be VPC2 and get 30001/20001. In my vision, you would drag a VPCs icon on to the desktop and it would automatically be called VPC1 and allocated NIO-UDP ports 30000/20000. You and I might know that you COULD configure a cloud to be just like a vPCS host, but to make it easy for newcomers (and old hands) a quick, simple and predictable interface would be great. Make the VPCs host a little different to the generic Cloud. I can remember the first time I looked at that cloud and was so bewildered I closed it very quickly. I think that vPCS would work better if it had its own icon that simply automatically allocated the next NIO-UDP port pair, and the change port mechanism was more like changing the console port for a router, rather than the more complicated Cloud dialogue. It would be nice to use port numbers beginning with 30001/20001 for VPC1 etc It would be nice to have the NIO-UDP port numbers increment like the Console and AUX port numbers If I add multiple hosts at the same time, then default port numbers increment as I add them, but if I have already added C1 and C2, then later add C3, the default NIO-UDP port regresses to 30000/20000. For the first host, the port numbers are 30000/20000. When we add a Host node, we increment the names (C1, then C2 etc) but not the default NIO UDP ports. And at the same time, increment the Console and AUX port settings, 2001, then 2002 etc. When we add a Router Node, we are smart enough to give it an "incremental" name - R1 then R2 etc. Some thoughts on VPCs integration with GNS3 So I thought I'd better add my 2c worth with some random thoughts about how this ought to be done ) I hear of plans to integrate VPCs with GNS3.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |