Library items tagged: network set-up

Anonymous
B1. JANET QoS Development Project Documentation [KentP2]  JANET QoS Project Phase 2, ‘Kent and Manchester University Deliverable’, http://www.webarchive.ja.net/development/qos/documents/KMLQoSreportfinal.pdf. [LANCP2]  JANET QoS Project Phase 2, ‘Lancaster University / CLEO Trials’, http://www.ja.net/documents/development/QoSReport-LancasterPhase2v2.0.pdf.
Anonymous
A1. CISCO IP-SLA Monitoring Probe Configuration Example Cisco® IP-SLA Probe Command Line Configuration used on JANET Monitoring probes at sites are configured with the Cisco® IOS command: ! tr responder ! This enables the IP-SLA process, allowing the router to receive, process, and return probes back to the CMP. For IOS version 12.4 this command became ‘ip sla monitor responder’ and the related commands changed also.
Anonymous
General information on the use of QoS with networks belonging to the UK JANET community can be found on the JANET(UK) web site (www.ja.net). More specific information concerning QoS on JANET is located at [JANETSTAT].
Anonymous
6.1 Operating System Support for Quality of Service When considering application support for QoS, a key underlying issue will be the level of QoS support in the operating system for packet marking. Earlier sections of this guide have stated that it is preferential to move the packet marking process as close to the source as possible. As such, the ability to do this within the host itself would be the ultimate outcome here. This section will present an overview of QoS support in the major end user operating systems including Microsoft Windows, Linux and UNIX based systems.
Anonymous
In this section we discuss the issues facing a site that is considering the deployment of QoS in its network. We first run through some of the general considerations for a site before looking at some of the specifics of certain technologies that may impact QoS deployment, along with the user and application viewpoint for QoS. Finally we discuss how these issues may vary for large (university campus and satellite) and small (single site college) networks.
Anonymous
In this section we address the deployment of QoS in the Regional Network based on the experience gained by QoS operation and trailing in the project. Due to the range and scope of network infrastructures that operate in this area, it is difficult to present a single case for QoS that fits all cases. Instead, this section will present a discussion of the issues that may be encountered when considering QoS in the Regional Networks and how this can interact with the JANET QoS Policy presented above.
Anonymous
JANET Policy Framework This section describes the initial JANET QoS Policy Framework, which is based on the DiffServ architecture being implemented at the edge of the network. It is intentionally simple, and may be revised over time as experience is gained in the production deployment of elements of DiffServ.
Anonymous
2.1 Introduction to QoS This section provides a brief description of the main techniques concerned with engineering support for QoS in packet networks. A more detailed description of QoS can be found in a companion document [QoSBasics].
Anonymous
This appendix contains ideas and examples of good practice in Grid support gathered from various conferences and meetings with organisations that are making effective use of Grid technologies. It is hoped to expand this collection in future editions: please send any suggestions for ideas to include to Andrew.Cormack@ja.net. Where possible, references to the source of the idea are included, though some of the case studies were given by personal communication or on condition of anonymity.
Anonymous
Service Definitions Grid Service Providers ensure that technical and support services offered are defined and available to users, along with any service level definitions define who may use the Grid service, and document the process for gaining authorisation (and authentication credentials if required) define technical and network requirements to use the Grid service define acceptable use and other policies for the Grid and make these available, as far as possible, to all authorised users