Physical Cores on a Server Sample Clauses

Physical Cores on a Server. You may license based on all of the physical cores on the server. If you choose this option, the number of licenses required equals the number of physical cores on the server subject to a minimum of four licenses per processor.
Physical Cores on a Server. For each server to which you have assigned the required number of licenses as provided in Section 2.2(a), you may run on the licensed server any number of instances of the server software in the physical OSE.

Related to Physical Cores on a Server

  • Physical Collocation (a) If space for Physical Collocation is immediately available at the time of Requesting Carrier’s Collo Order, Ameritech shall include in its Collo Response to Requesting Carrier notice of such immediate availability. (b) If Requesting Carrier’s requested Physical Collocation space is available, Ameritech and Requesting Carrier shall have an initial walk-through of such space within the interval specified in the Implementation Plan. Absent Ameritech’s written consent, Requesting Carrier must have at least one (1) authorized employee (i.e., in addition to any authorized vendor) at such walk- through. If during the initial walk-through, Requesting Carrier wishes to modify or change its Collo Request, Requesting Carrier must sign or initial any such modifications or changes and provide Ameritech a change order reflecting same within five (5) Business Days of such initial walk-through. If a change or modification is noted at the initial walk-through, Ameritech shall have no obligation to commence work on Requesting Carrier’s Collocation space until it receives a change order to amend the Collo Request or written confirmation that Requesting Carrier does not wish to pursue such change or modification. Failure to provide Ameritech the change order or written confirmation within the foregoing five (5) Business Day period shall be deemed a Requesting Carrier Delaying Event for the period between the expiration of such five (5) day period and the date of actual receipt by Ameritech. (c) Ameritech shall deliver to Requesting Carrier the requested space on or before the later of (i) one hundred twenty (120) days from Ameritech’s receipt of Requesting Carrier’s Collo Order, (ii) ninety (90) days from the date of the initial walk-through and (iii) such other reasonable date that the Parties may agree upon if it is not feasible for Ameritech to deliver to Requesting Carrier such space within the foregoing intervals (such date of delivery referred to as the “Delivery Date”). (d) Physical Collocation space ordered by Requesting Carrier will be made available to Requesting Carrier by Ameritech as more fully described in Section 1 of Schedule 12.12. (e) Ameritech may begin billing recurring charges for the Collocated space on the date such space is made available for occupancy (the “Occupancy Date”). Requesting Carrier shall vacate the Collocated space if either (i) Requesting Carrier (or one of its Resident Collocators, if applicable) fails to install within ninety (90) days of the Occupancy Date the equipment necessary for Interconnection with Ameritech and/or access to Ameritech’s unbundled Network Elements to be housed in such space or (ii) Requesting Carrier (or one of its Resident Collocators, if applicable) fails to Interconnect to the Ameritech network within one hundred fifty (150) days of the Occupancy Date. If Requesting Carrier is required to vacate the space pursuant to this Section 12.12.2(e), Requesting Carrier (and its Resident Collocators) shall vacate such space within ninety (90) Business Days of the earliest to occur of the foregoing events. If, after vacating a space, Requesting Carrier still requires Collocation in that Premises, Requesting Carrier shall be required to submit a new request for Collocation pursuant to the provisions of Section 12.12.1. (f) Physical Collocation will be subject to the additional rules and regulations set forth in Section 2.0 of Schedule 12.12. (g) At Requesting Carrier’s request Ameritech shall provide for APCS within three

  • Action by Written Consent or Telephone Conference Any action permitted or required by the Act, the Certificate or this Agreement to be taken at a meeting of the Members may be taken without a meeting if a consent in writing, setting forth the action to be taken, is signed by the Majority Members. Such consent shall have the same force and effect as a unanimous vote at a meeting and may be stated as such in any document or instrument filed with the Secretary of State of Delaware, and the execution of such consent shall constitute attendance or presence in person at a meeting of the Members. Subject to the requirements of the Act, the Certificate or this Agreement for notice of meetings, unless otherwise restricted by the Certificate, the Members may participate in and hold a meeting by means of a telephone conference or similar communications equipment by means of which all persons participating in the meeting can hear each other, and participation in such meeting shall constitute attendance and presence in person at such meeting.

  • Access to NID 2.7.3.1 NewPhone may access the customer’s premises wiring by any of the following means and NewPhone shall not disturb the existing form of electrical protection and shall maintain the physical integrity of the NID: 2.7.3.1.1 BellSouth shall allow NewPhone to connect its Loops directly to BellSouth’s multi-line residential NID enclosures that have additional space and are not used by BellSouth or any other telecommunications carriers to provide service to the premises; 2.7.3.1.2 Where an adequate length of the customer’s premises wiring is present and environmental conditions permit, either Party may remove the customer premises wiring from the other Party’s NID and connect such wiring to that Party’s own NID; 2.7.3.1.3 Either Party may enter the subscriber access chamber or dual chamber NID enclosures for the purpose of extending a cross-connect or spliced jumper wire from the customer premises wiring through a suitable “punch-out” hole of such NID enclosures; or 2.7.3.1.4 NewPhone may request BellSouth to make other rearrangements to the customer premises wiring terminations or terminal enclosure on a time and materials cost basis. 2.7.3.2 In no case shall either Party remove or disconnect the other Party’s loop facilities from either Party’s NIDs, enclosures, or protectors unless the applicable Commission has expressly permitted the same and the disconnecting Party provides prior notice to the other Party. In such cases, it shall be the responsibility of the Party disconnecting loop facilities to leave undisturbed the existing form of electrical protection and to maintain the physical integrity of the NID. It will be NewPhone’s responsibility to ensure there is no safety hazard, and NewPhone will hold BellSouth harmless for any liability associated with the removal of the BellSouth Loop from the BellSouth NID. Furthermore, it shall be the responsibility of the disconnecting Party, once the other Party’s loop has been disconnected from the NID, to reconnect the disconnected loop to a nationally recognized testing laboratory listed station protector, which has been grounded as per Article 800 of the National Electrical Code. If no spare station protector exists in the NID, the disconnected loop must be appropriately cleared, capped and stored. 2.7.3.3 NewPhone shall not remove or disconnect ground wires from BellSouth’s NIDs, enclosures, or protectors. 2.7.3.4 NewPhone shall not remove or disconnect NID modules, protectors, or terminals from BellSouth’s NID enclosures. 2.7.3.5 Due to the wide variety of NID enclosures and outside plant environments, BellSouth will work with NewPhone to develop specific procedures to establish the most effective means of implementing this section if the procedures set forth herein do not apply to the NID in question.

  • Outside Activities of Limited Partners Subject to any agreements entered into by a Limited Partner or its Affiliates with the General Partner, Partnership or a Subsidiary, any Limited Partner and any officer, director, employee, agent, trustee, Affiliate or stockholder of any Limited Partner shall be entitled to and may have business interests and engage in business activities in addition to those relating to the Partnership, including business interests and activities in direct competition with the Partnership or that are enhanced by the activities of the Partnership. Neither the Partnership nor any Partners shall have any rights by virtue of this Agreement in any business ventures of any Limited Partner or Assignee. Subject to such agreements, none of the Limited Partners nor any other Person shall have any rights by virtue of this Agreement or the partnership relationship established hereby in any business ventures of any other Person, other than the Limited Partners benefiting from the business conducted by the General Partner, and such Person shall have no obligation pursuant to this Agreement to offer any interest in any such business ventures to the Partnership, any Limited Partner or any such other Person, even if such opportunity is of a character which, if presented to the Partnership, any Limited Partner or such other Person, could be taken by such Person.

  • Access to List of Holders' Names and Addresses Each Holder and each Owner shall be deemed to have agreed not to hold the Depositor, the Property Trustee, the Delaware Trustee or the Administrative Trustees accountable by reason of the disclosure of its name and address, regardless of the source from which such information was derived.