iLO not assigning TestCenter ports efficiently
I am having a problem where iLO reserves TestCenter resources; it does not do it in an optimal way. As you may know, when you reserve one TestCenter port on a CM-1G-D12 card, you tie-up two ports, because of the hardware limitations. What I am seeing from iLO is somewhat of a random assignment that does reserve 4 ports, but ties up 8. Any hints on how to make iLO be more efficient with resources by reserving physical port pairs? This is what iLO looks like after my topology reserves 4 ports: ![alt text][1] ![alt text][2] [1]: /storage/temp/4268-ilo+assigned+1st+2+ports.png [2]: /storage/temp/4269-ilo+assigned+2nd+2+ports.png
![alt text][1]Can you please elaborate on how to create STC drivers from iTest? Basically, what I am looking for is a method to use an abstract topology but somehow making sure the port reservations are always mapped to physical port pairs. With the topology shown here, no more than 4 STC ports should be reserved. And because we must be able to switch test packages between l4l7 and stc, those packages can only be witched in port pairs. [1]: /storage/temp/4372-sample.jpg
As per the screen shots the "TestCenter" resource is connected to MRV and I believe that your logical topology contains FOUR connections. So after reserving the logical topology the MRV ports will be mapped based on the connections which we created. This is the reason we see all the ports(including unreserved/reserved ports) of that "TestCenter" resource. Lets say, We may have real MRV switch (added to iLO inventory) somewhere , and any devices which are just created in inventory, and then specify in physical topology that these devices are connected to MRV somehow. iLO doesn't check that devices are really connected to MRV, so it will just create corresponding mappings on the switch. Let me show with example: Suppose we have real MRV, and two fake devices "Testcenter1"(inherited with SpirentTest Center template) and "Testcenter2"(inherited with SpirentTest Center template). In physical topology we specified that Testcenter1 <-> MRV <-> Testcenter2 (MRV ports 1.1.1 and 1.1.2 for example are used here). In logical topology if we have Testcenter1 <-> Testcenter2, then iLO just will map 1.1.1 to 1.1.2 on MRV. It's NOT necessary to have real Testcenter1 and Testcenter2, and it doesn't matter what connected to 1.1.1 and 1.1.2 in reality. Here it will map the ports using the MRV divers. If we want to reserve the STC Chassis ports from ILO , then first we need to create STC drivers using iTest.
I just learned that you can change the *TestCenter* cards to have "1 port per group" via *Spirent TestCenter Application* menu: **Tools|Equipment Information...|Test Module|Resize Port Group**. Is there any known reason why this would not be a good idea?
18 People are following this question.
