Manageable Switch Sample Clauses

Manageable Switch. Gigabit Ethernet Manageable Switch A) 16 Port Gigabit Ethernet Manageable Switch: Min. Technical Specificat ion Minimum 16 No’s of 10/100/1000 Base-Tx XxX ports (full Duplex) and 2 x 1GE Uplink port. All ports should have features of auto- negotiate, flow control (802.3x), port- based network access control (802.1x), port security, MAC filtering etc. Minimum Switching capacity of 30 Gbps or more MAC address table of minimum of 8k per switch Should be IPv4 and IPv6 ready from day one Should have IEEE 802.1.d STP, 802.1w RSTP ,802.1s MSTP, IEEE 802.1Q VLAN Features of DHCP, NTP/SNTP or equivalent, SNMPv1, v2 and v3, TELNET/ SSH, TFTP, Web/SSL IGMP versions 1 and 2 snooping: supports 1K multicast groups Should have console port for administration and management, CLI/ webbased GUI Support for IEEE 802.3ad Link Aggregation Control Protocol (LACP), Up to 8 groups, Up to 8 ports per group All necessary SFP's, interfaces, connectors, patch cords (if any) and licenses must be delivered along with the switch from day one. The Switch should be Rack mountable and the switch should be supplied with Indian standard AC power cord. Relay of DHCP traffic to DHCP server in different VLAN. Works with DHCP Option 82 ping, traceroute, RADIUS/LDAP, TACACS+, syslog, DNS xxxxxx X) 24 Port Gigabit Ethernet Manageable Switch: Min. Technical Specificat ion Minimum 24 No’s of 10/100/1000 Base-Tx XxX ports (full Duplex) and 2 x 1GE Uplink port. All ports should have features of auto- negotiate, flow control (802.3x), port-based network access control (802.1x), port security, MAC filtering etc. Minimum Switching capacity of 50 Gbps or more MAC address table of minimum of 8k per switch Should be IPv4 and IPv6 ready from day one Should have IEEE 802.1.d STP, 802.1w RSTP ,802.1s MSTP, IEEE 802.1Q VLAN, Features of DHCP, NTP/SNTP or equivalent, SNMPv1, v2 and v3, TELNET/ SSH, TFTP, Web/SSL IGMP versions 1 and 2 snooping: supports 1K multicast groups Should have console port for administration and management, CLI/web-based GUI Support for IEEE 802.3ad Link Aggregation Control Protocol (LACP), Up to 8 groups, Up to 8 ports per group All necessary SFP's, interfaces, connectors, patch cords (if any) and licenses must be Page 34 of 48 delivered along with the switch from day one. The Switch should be Rack mountable and the switch should be supplied with Indian standard AC power cord. Relay of DHCP traffic to DHCP server in different VLAN. Works with DHCP Option 82 ping, traceroute, RADIUS/LDAP,...
AutoNDA by SimpleDocs

Related to Manageable Switch

  • Shared Transport The Shared Transport Network Element (“Shared Transport”) provides the collective interoffice transmission facilities shared by various Carriers (including Qwest) between end-office switches and between end-office switches and local tandem switches within the Local Calling Area. Shared Transport uses the existing routing tables resident in Qwest switches to carry the End User Customer’s originating and terminating local/extended area service interoffice Local traffic on the Qwest interoffice message trunk network. CLEC traffic will be carried on the same transmission facilities between end- office switches, between end-office switches and tandem switches and between tandem switches on the same network facilities that Qwest uses for its own traffic. Shared Transport does not include use of tandem switches or transport between tandem switches and end-office switches for Local Calls that originate from end users served by non- Qwest Telecommunications Carriers (“Carrier(s)”) which terminate to QLSP End Users.

  • Tandem Switching 4.5.1 The Tandem Switching capability Network Element is defined as: (i) trunk-connect facilities, which include, but are not limited to, the connection between trunk termination at a cross-connect panel and switch trunk card; (ii) the basic switch trunk function of connecting trunks to trunks; and (iii) the functions that are centralized in the Tandem Switches (as distinguished from separate end office switches), including but not limited to call recording, the routing of calls to operator services and signaling conversion features. 4.5.2 Where <<customer_short_name>> utilizes portions of the BellSouth network in originating or terminating traffic, the Tandem Switching rates are applied in call scenarios where the Tandem Switching Network Element has been utilized. Because switch recordings cannot accurately indicate on a per call basis when the Tandem Switching Network Element has been utilized for an interoffice call originating from a UNE port and terminating to a BellSouth, Independent Company or Facility-Based CLEC office, BellSouth has developed, based upon call studies, a melded rate that takes into account the average percentage of calls that utilize Tandem Switching in these scenarios. BellSouth shall apply the melded Tandem Switching rate for every call in these scenarios. BellSouth shall utilize the melded Tandem Switching Rate until BellSouth has the capability to measure actual Tandem Switch usage in each call scenario specifically mentioned above, at which point the rate for the actual Tandem Switch usage shall apply. The UNE Local Call Flows set forth on BellSouth's website, as amended from time to time and incorporated herein by this reference, illustrate when the full or melded Tandem Switching rates apply for specific scenarios.

  • One-Way Interconnection Trunks 2.3.1 Where the Parties use One-Way Interconnection Trunks for the delivery of traffic from Onvoy to Frontier, Onvoy, at Onvoy’s own expense, shall: 2.3.1.1 provide its own facilities for delivery of the traffic to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA; and/or 2.3.1.2 obtain transport for delivery of the traffic to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA (a) from a third party, or, (b) if Frontier offers such transport pursuant to a Frontier access Tariff, from Frontier. 2.3.2 For each Tandem or End Office One-Way Interconnection Trunk group for delivery of traffic from Onvoy to Frontier with a utilization level of less than sixty percent (60%) for final trunk groups and eighty-five percent (85%) for high usage trunk groups, unless the Parties agree otherwise, Onvoy will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for all final trunk groups and eighty-five percent (85%) for all high usage trunk groups. In the event Onvoy fails to submit an ASR to disconnect One-Way Interconnection Trunks as required by this Section, Frontier may disconnect the excess Interconnection Trunks or bill (and Onvoy shall pay) for the excess Interconnection Trunks at the rates set forth in the Pricing Attachment. 2.3.3 Where the Parties use One-Way Interconnection Trunks for the delivery of traffic from Frontier to Onvoy, Frontier, at Frontier’s own expense, shall provide its own facilities for delivery of the traffic to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA.

  • Two-Way Interconnection Trunks 2.4.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and Ymax, Ymax, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA (a) from a third party, or, (b) if Verizon offers such transport pursuant to this Agreement or an applicable Verizon Tariff, from Verizon. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and Ymax, Verizon, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Ymax shall meet with Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centium Call Seconds (Hundred Call Seconds) information, and the Parties shall mutually agree on the appropriate initial number of End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA at which the Parties interconnect for the exchange of traffic. Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One- Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.4 On a semi-annual basis, Ymax shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Interconnection Trunks that Ymax anticipates Verizon will need to provide during the ensuing two (2) year period for the exchange of traffic between Ymax and Verizon. Ymax’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centium Call Seconds (Hundred Call Seconds) equal to five (5). Either Party may disconnect End Office Two-Way Interconnection Trunks that, based on reasonable engineering criteria and capacity constraints, are not warranted by the actual traffic volume experienced. 2.4.8 Two-Way Interconnection Trunk groups that connect to a Verizon access Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx B.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of Xxxx- Xxxxxxxxx B.01 during the average time consistent busy hour. Verizon and Xxxx shall engineer Two-Way Interconnection Trunks using BOC Notes on the LEC Networks SR-TSV-002275. 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months. 2.4.10 Ymax shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. Ymax shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Ymax shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and Ymax has not notified Verizon that it has corrected such blocking, Verizon may submit to Ymax a Trunk Group Service Request directing Ymax to remedy the blocking. Upon receipt of a Trunk Group Service Request, Ymax will complete an ASR to establish or augment the End Office Two-Way Interconnection Trunk group(s), or, if mutually agreed, to augment the Tandem Two-Way Interconnection Trunk group with excessive blocking and submit the ASR to Verizon within five (5) Business Days. 2.4.12 The Parties will review all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Ymax will promptly augment all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two-Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, Ymax will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event Ymax fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Verizon may disconnect the excess Interconnection Trunks or bill (and Ymax shall pay) for the excess Interconnection Trunks at the applicable Verizon rates. 2.4.13 Because Verizon will not be in control of when and how many Two- Way Interconnection Trunks are established between its network and Ymax’s network, Verizon’s performance in connection with these Two- Way Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan. 2.4.14 Ymax will route its traffic to Verizon over the End Office and Tandem Two-Way Interconnection Trunks in accordance with SR-TAP-000191, including but not limited to those standards requiring that a call from Ymax to a Verizon End Office will first be routed to the End Office Interconnection Trunk group between Ymax and the Verizon End Office.

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If ECI chooses to subtend a Verizon access Tandem, ECI’s NPA/NXX must be assigned by ECI to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG. 9.2.2 ECI shall establish Access Toll Connecting Trunks pursuant to applicable access Tariffs by which it will provide Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic to and from ECI’s Customers. 9.2.3 The Access Toll Connecting Trunks shall be two-way trunks. Such trunks shall connect the End Office ECI utilizes to provide Telephone Exchange Service and Switched Exchange Access to its Customers in a given LATA to the access Tandem(s) Verizon utilizes to provide Exchange Access in such LATA. 9.2.4 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access to allow ECI’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier which is connected to a Verizon access Tandem.

  • Television Equipment Recycling Program If this Contract is for the purchase or lease of covered television equipment, then Contractor certifies that it is compliance with Subchapter Z, Chapter 361 of the Texas Health and Safety Code related to the Television Equipment Recycling Program.

  • Local Switching 4.1.1 BellSouth shall provide non-discriminatory access to local circuit switching capability, and local tandem switching capability, on an unbundled basis, except as set forth below in Section 4.1.

  • Initiating Interconnection ‌ 4.1 If Emergency determines to offer Telephone Exchange Services and to interconnect with Verizon in any LATA in which Verizon also offers Telephone Exchange Services, and in which the Parties are not already interconnected pursuant to this Agreement, Emergency shall provide written notice to Verizon of the need to establish Interconnection in such LATA pursuant to this Agreement.‌ 4.2 The notice provided in Section 4.1 of this Attachment shall include (a) the initial Routing Point(s); (b) the applicable technically feasible Point(s) of Interconnection on Verizon's network to be established in the relevant LATA, in accordance with this Agreement; (c) Emergency’s intended Interconnection activation date; and (d) a forecast of Emergency’s trunking requirements conforming to Section 14.2 of this Attachment; and (e) such other information as Verizon shall reasonably request in order to facilitate Interconnection. 4.3 The Interconnection activation date in the new LATA shall be mutually agreed to by the Parties after receipt by Verizon of all necessary information as indicated above. Within ten (10) Business Days of Verizon’s receipt of the Emergency’s notice provided for in Section 4.1 of this Attachment, Verizon and Emergency shall confirm the technically feasible Point of Interconnection on Verizon's network in the new LATA and the mutually agreed upon Interconnection activation date for the new LATA.

  • Loop Provisioning Involving Integrated Digital Loop Carriers 2.6.1 Where Freedom 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 Freedom. 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 Freedom (e.g. hairpinning): 1. Roll the circuit(s) from the IDLC to any spare copper that exists to the customer premises. 2. Roll the circuit(s) from the IDLC to an existing DLC that is not integrated. 3. If capacity exists, provide "side-door" porting through the switch. 4. If capacity exists, provide "Digital Access Cross Connect System (DACS)- door" porting (if the IDLC routes through a DACS prior to integration into the switch). 2.6.2 Arrangements 3 and 4 above require the use of a designed circuit. Therefore, non- designed Loops such as the SL1 voice grade and UCL-ND may not be ordered in these cases. 2.6.3 If no alternate facility is available, and upon request from Freedom, and if agreed to by both Parties, BellSouth may utilize its Special Construction (SC) process to determine the additional costs required to provision facilities. Freedom will then have the option of paying the one-time SC rates to place the Loop.

  • Signaling Link Transport 9.2.1 Signaling Link Transport is a set of two or four dedicated 56 kbps transmission paths between Global Connection-designated Signaling Points of Interconnection that provide appropriate physical diversity.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!