Common use of Dynamic Routing Clause in Contracts

Dynamic Routing. LightEdge will design a network topology based on a dynamic routing protocol. The routing protocol for such a design will be Border Gateway Protocol or BGP. Customer will be responsible for the support or design of any portion of network not running BGP. If Customer network design does not fit into pre-defined LightEdge templates then Customer will be responsible for any Engineering time required to design, implement or support Customer. Customer will be billed at standard LightEdge hourly rates for such time. LightEdge shall be the sole party responsible for determining that Customer network does not fit into a pre-defined LightEdge template. Customer will be responsible for providing network gear recommended by LightEdge. This network gear may include but is not limited to routers, memory, flash memory, software code, switches and router modules. If LightEdge manages Customer equipment then LightEdge shall be responsible for configuring equipment to support dynamic routing. If LightEdge does not manage customer equipment then Customer will be responsible for configuring equipment to support dynamic routing within the guidelines recommended by LightEdge. Customer acknowledges that a network based on a dynamic routing protocol may place certain constraints on the troubleshooting and support of the network. If a customer with a network based on a dynamic routing protocol experiences issues that are deemed to originate outside of LightEdge’s control then Customer may be held responsible for troubleshooting activities relating to issues. LightEdge responsibility is limited to the routing between LightEdge’s network and Customer equipment directly attached to LightEdge network. Customer is responsible for any equipment directly attached to the LightEdge network.

Appears in 3 contracts

Samples: Access Business Internet Service Agreement, Access Business Internet Service Agreement, Access Business Internet Service Agreement

AutoNDA by SimpleDocs

Dynamic Routing. LightEdge will design a network topology based on a dynamic routing protocol. The routing protocol for such a design will be Border Gateway Protocol or BGP. Customer will be responsible for the support or design of any portion of network not running BGP. If Customer network design does not fit into pre-defined LightEdge templates then than Customer will be responsible for any Engineering time required to design, implement or support Customer. Customer will be billed at standard LightEdge hourly rates for such time. LightEdge shall be the sole party responsible for determining that Customer network does not fit into a pre-defined LightEdge template. Customer will be responsible for providing network gear recommended by LightEdge. This network gear may include but is not limited to routers, memory, flash memory, software code, switches and router modules. If LightEdge manages Customer equipment then LightEdge shall be responsible for configuring equipment to support dynamic routing. If LightEdge does not manage customer equipment then Customer will be responsible for configuring equipment to support dynamic routing within the guidelines recommended by LightEdge. Customer acknowledges that a network based on a dynamic routing protocol may place certain constraints on the troubleshooting and support of the network. If a customer with a network based on a dynamic routing protocol experiences issues that are deemed to originate outside of LightEdge’s control then than Customer may be held responsible for troubleshooting activities relating to issues. LightEdge responsibility is limited to the routing between LightEdge’s network and Customer equipment directly attached to LightEdge network. Customer is responsible for any equipment directly attached to the LightEdge network.

Appears in 2 contracts

Samples: Access Meshed Ip Wan Service Agreement, Access Meshed Ip Wan Service Agreement

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