Tools for Lookup Service Testing Sample Clauses

Tools for Lookup Service Testing. ‌ To ensure flawless operation of the complex distributed system comprising gLS, hLS and perfSONAR services, tools to test its most important functionalities are needed. The multi-step nature of querying perfSONAR services (Discovery query, LS query, MA or MP query) complicates testing by requiring query sequences to retrieve information for every single metric and interface. Since PerfsonarUI has already been used to query and test different perfSONAR services, an additional new module for testing the LS was suggested in Gn3. The existing PerfsonarUI Playground module was occasionally used for testing LS services, but required too much knowledge of the specific gLS and hLS queries, as well as the LS infrastructure. The additional Lookup Service Playground module that was proposed for testing the LS therefore includes the following functionalities: • Simple testing functionality of home LS and Discovery protocol (involves global Lookup Services, listed in a predefined top root.hints file): ○ Ability to change LS federation, by specifying selected root.hints or just selecting specific global LS. ○ Send/receive echo requests/responses. ○ Given a user-selected network element, event types and service type, retrieve and display the following information: — global Lookup service(s) involved. — home LS(s) involved. — MA or MP that serve the specified network element and event types — Verify if MA/MP does indeed provide information about the specified network element and event types (troubleshooting summarisation errors). ○ The user should be able to inspect the LS hierarchy relevant to the query network element and identify/report if a problem exists. ○ Report timings of LS interactions. • More complex scenario (to be considered in further development): Providing different views of the LS infrastructure. ○ Top down view: An LS hierarchy (as in [i2]) with the ability to inspect which network elements are served by the hLS. ○ Bottom up view: Starting with (multiple) user-selected network elements and event types, retrieve and display a map of the involved MA/MP, home and global LS troubleshooting. ○ Observing multiple LS services simultaneously to keep an eye on summarisation and LS data exchange in a multi-domain environment (speed, amount of data being exchanged, etc.).
Sample 1
AutoNDA by SimpleDocs

Related to Tools for Lookup Service Testing

  • Repair Testing At the time of repair of a LIS trunk group, at no additional charge, tests will be performed to ensure that the service is operational and meets the applicable technical parameters.

  • Meter Testing Company shall provide at least twenty-four (24) hours' notice to Seller prior to any test it may perform on the revenue meters or metering equipment. Seller shall have the right to have a representative present during each such test. Seller may request, and Company shall perform, if requested, tests in addition to the every fifth-year test and Seller shall pay the cost of such tests. Company may, in its sole discretion, perform tests in addition to the fifth year test and Company shall pay the cost of such tests. If any of the revenue meters or metering equipment is found to be inaccurate at any time, as determined by testing in accordance with this Section 10.2 (Meter Testing), Company shall promptly cause such equipment to be made accurate, and the period of inaccuracy, as well as an estimate for correct meter readings, shall be determined in accordance with Section 10.3 (Corrections).

  • Performance Testing 7.2.1 The Design-Builder shall direct and supervise the tests and, if necessary, the retests of the Plant using Design-Builder’s supervisory personnel and the Air Emissions Tester shall conduct the air emissions test, in each case, in accordance with the testing procedures set forth in Exhibit A (the “Performance Tests”), to demonstrate, at a minimum, compliance with the Performance Guarantee Criteria. Owner is responsible for obtaining Air Emissions Tester and for ensuring Air Emissions Tester’s timely performance. Design-Builder shall cooperate with the Air Emissions Tester to facilitate performance of all air emissions tests. Design-Builder shall not be held responsible for the actions of Owner’s employees and third parties involved in the Performance Testing, including but not limited to Air Emissions Tester.

  • ODUF Testing 6.6.1 Upon request from TWTC, AT&T shall send ODUF test files to TWTC. The Parties agree to review and discuss the ODUF file content and/or format. For testing of usage results, AT&T shall request that TWTC set up a production (live) file. The live test may consist of TWTC’s employees making test calls for the types of services TWTC requests on ODUF. These test calls are logged by TWTC, and the logs are provided to AT&T. These logs will be used to verify the files. Testing will be completed within thirty (30) days from the date on which the initial test file was sent.

  • Loop Provisioning Involving Integrated Digital Loop Carriers 2.6.1 Where InterGlobe has requested an Unbundled Loop and BellSouth uses IDLC systems to provide the local service to the End User and BellSouth has a suitable alternate facility available, BellSouth will make such alternative facilities available to InterGlobe. If a suitable alternative facility is not available, then to the extent it is technically feasible, BellSouth will implement one of the following alternative arrangements for InterGlobe (e.g. hairpinning):

  • Drug Testing (A) The state and the PBA agree to drug testing of employees in accordance with section 112.0455, F.S., the Drug-Free Workplace Act.

  • Random Testing Notwithstanding any provisions of the Collective Agreement or any special agreements appended thereto, section 4.6 of the Canadian Model will not be applied by agreement. If applied to a worker dispatched by the Union, it will be applied or deemed to be applied unilaterally by the Employer. The Union retains the right to grieve the legality of any imposition of random testing in accordance with the Grievance Procedure set out in this Collective Agreement.

  • AIN Selective Carrier Routing for Operator Services, Directory Assistance and Repair Centers 4.3.1 BellSouth will provide AIN Selective Carrier Routing at the request of <<customer_name>>. AIN Selective Carrier Routing will provide <<customer_name>> with the capability of routing operator calls, 0+ and 0- and 0+ NPA (LNPA) 555-1212 directory assistance, 1+411 directory assistance and 611 repair center calls to pre-selected destinations.

  • Selection of Subcontractors, Procurement of Materials and Leasing of Equipment The contractor shall not discriminate on the grounds of race, color, religion, sex, national origin, age or disability in the selection and retention of subcontractors, including procurement of materials and leases of equipment. The contractor shall take all necessary and reasonable steps to ensure nondiscrimination in the administration of this contract.

  • Loop Testing/Trouble Reporting 2.1.6.1 Think 12 will be responsible for testing and isolating troubles on the Loops. Think 12 must test and isolate trouble to the BellSouth portion of a designed/non- designed unbundled Loop (e.g., UVL-SL2, UCL-D, UVL-SL1, UCL-ND, etc.) before reporting repair to the UNE Customer Wholesale Interconnection Network Services (CWINS) Center. Upon request from BellSouth at the time of the trouble report, Think 12 will be required to provide the results of the Think 12 test which indicate a problem on the BellSouth provided Loop.

Time is Money Join Law Insider Premium to draft better contracts faster.