Ethernet User Traffic Sample Clauses

Ethernet User Traffic. Network to User In Figure tfrro! Use a guia Início para aplicar Heading 1 ao texto que xxxxxx aparecer aqui.-22 the rectangles illustrate the data flow for Ethernet user traffic from a network port to a user port. The rounded rectangles indicate the features that need to be configured, numbered according to the order of configuration. Table -11 shows the configuration steps corresponding to the numbers. Figure Erro! Use a guia Início para aplicar Heading 1 ao texto que xxxxxx aparecer aqui.-22. tfthernet User Traffic Data Flow – Network to User Table -11. tfthernet User Traffic Configuration – Network to User Sequence Step Commands Comments 1 Defining Classifier Profiles classifier-profile match The classifier profile defines the criteria for the network-to-user flow 2 Marking Profiles marking-profile mark Necessary only if a profile is needed for non-default mapping of p-bit, IP precedence, DSCP, or CoS classifications to egress priority tags for the network-to-user flow 3 Queue Mapping Profiles queue-map-profile map Necessary only if a profile is needed for non-default mapping of user priorities to queues for the network-to-user flow 4 Configuring Policer Profiles policer-profile bandwidth compensation Necessary only if you need to define non-default bandwidth limits or overhead compensation for the incoming traffic of the network-to-user flow Sequence Step Commands Comments 5 Configuring Queue Block Profile Parameters queue-block-profile queue scheduling depth Necessary only if you need to define non-default queue configuration for the network-to-user flow 6 WRtfD Profiles wred-profile color Necessary only if you need to define non-default WRED configuration for the queue blocks
Sample 1
AutoNDA by SimpleDocs

Related to Ethernet User Traffic

  • Internet Traffic Any traffic that is transmitted to or returned from the Internet at any point during the duration of the transmission.

  • Internet Use Customer assumes total responsibility for its and its users’ use of the Internet. Masergy specifically disclaims any warranties, endorsements or representations regarding any merchandise, information, software, products, data, files, or services provided through the Internet.

  • Transit Traffic 7.2.2.3.1 CenturyLink will accept traffic originated by CLEC’s network and/or its end user(s) for termination to other Telecommunications Carrier’s network and/or its end users that is connected to CenturyLink's Switch. CenturyLink will also terminate traffic from these other Telecommunications Carriers’ network and/or its end users to CLEC’s network and/or its end users. For purposes of the Agreement, transit traffic does not include traffic carried by Interexchange Carriers. That traffic is defined as Jointly Provided Switched Access. 7.2.2.3.2 The Parties involved in transporting transit traffic will deliver calls to each involved network with CCS/SS7 protocol and the appropriate ISUP/TCAP messages to facilitate full Interoperability and Billing functions. 7.2.2.3.3 The originating company is responsible for payment of appropriate rates to the transit company and to the terminating company. The Parties agree to enter into traffic exchange agreements with third party Telecommunications Carriers prior to delivering traffic to be transited to third party Telecommunications Carriers. In the event one Party originates traffic that transits the second Party’s network to reach a third party Telecommunications Carrier with whom the originating Party does not have a traffic exchange agreement, then the originating Party will indemnify, defend and hold harmless the second Party against any and all charges levied by such third party Telecommunications Carrier, including any termination charges related to such traffic and any attorneys fees and expenses. In the case of IntraLATA LEC Toll traffic where CenturyLink is the designated IntraLATA Toll provider for existing LECs, CenturyLink will be responsible for payment of appropriate usage rates. 7.2.2.3.4 When CenturyLink receives an unqueried call from CLEC to a telephone number that has been ported to another local services provider, the transit rate will apply in addition to any query rates. 7.2.2.3.5 In the case of a transit call that terminates in the Local Calling Area but in a different state than the call originated, and the CLEC does not have an agreement with CenturyLink in the state where the transit call terminated, CLEC must execute an agreement for that state if it is a state served by CenturyLink. In the absence of a second agreement, the transit rate in Exhibit A of this Agreement will be billed to the CLEC.

  • Network Access Control The VISION Web Site and the Distribution Support Services Web Site (the “DST Web Sites”) are protected through multiple levels of network controls. The first defense is a border router which exists at the boundary between the DST Web Sites and the Internet Service Provider. The border router provides basic protections including anti-spoofing controls. Next is a highly available pair of stateful firewalls that allow only HTTPS traffic destined to the DST Web Sites. The third network control is a highly available pair of load balancers that terminate the HTTPS connections and then forward the traffic on to one of several available web servers. In addition, a second highly available pair of stateful firewalls enforce network controls between the web servers and any back-end application servers. No Internet traffic is allowed directly to the back-end application servers. The DST Web Sites equipment is located and administered at DST’s Winchester data center. Changes to the systems residing on this computer are submitted through the DST change control process. All services and functions within the DST Web Sites are deactivated with the exception of services and functions which support the transfer of files. All ports on the DST Web Sites are disabled, except those ports required to transfer files. All “listeners,” other than listeners required for inbound connections from the load balancers, are deactivated. Directory structures are “hidden” from the user. Services which provide directory information are also deactivated.

  • Originating Switched Access Detail Usage Data A category 1101XX record as defined in the EMI Telcordia Practice BR-010-200- 010.

  • XXX Hosting 10.1 XXX Hosting is not required for resale in the BellSouth region.

  • Customer Content As part of the Services provided under this Agreement, Customer Data will be stored and processed in the data center region specified in the applicable Ordering Document. Axway shall not access Customer Content except in response to support or technical issues where Customer provides Axway with prior Customer’s written authorization required to access such Customer Content. Axway is not responsible for unauthorized access, alteration, theft or destruction of Customer Content arising from Customer’s own or its authorized users’ actions or omissions in contravention of the Documentation. Customer’s ability to recover any lost data resulting from Axway’s misconduct is limited to restoration by Axway from the most recent back-up.

  • Data Encryption Contractor must encrypt all State data at rest and in transit, in compliance with FIPS Publication 140-2 or applicable law, regulation or rule, whichever is a higher standard. All encryption keys must be unique to State data. Contractor will secure and protect all encryption keys to State data. Encryption keys to State data will only be accessed by Contractor as necessary for performance of this Contract.

  • Network Access TENANT may find it necessary to purchase a network interface card, wireless PC card or other hardware in order to connect to the internet service. LANDLORD is not responsible for the purchase of these items and LANDLORD cannot guarantee compatibility with any device TENANT may have. The computer and network card must have software installed that supports the Internet Protocol commonly referred to as TCP/IP. Any conflicts between the software compatibility of the network and the TENANT’S computer operating system or any other feature will be the responsibility of the TENANT to resolve. LANDLORD will not be responsible for software issues related to the user’s personal computer.

  • Programming Processor is not responsible for programming or reprogramming of fuel dispensers.

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