Reference configuration data for telecommunications and internet networks

QME Communications maintains a reviewed, openly readable catalogue of device configuration references for the routers, switches and transport equipment that carry telecommunications and internet traffic. Every entry is published as plain, annotated text so that network engineers can read it in a browser before adapting it to their own service provider or enterprise WAN topology.

What this site publishes

Telecommunications networks are built from a small number of repeating patterns: an external BGP session to a transit provider, an OSPF or IS-IS underlay between core routers, an MPLS label-switched path carrying Layer 3 VPN customer traffic, a Carrier Ethernet handoff with a policed committed information rate, an aggregation switch presenting tagged VLANs to a broadband access network. Those patterns are well documented in standards but rarely written down as complete, working device configuration with the reasoning attached.

This catalogue fills that gap. Each reference page states the network role, the equipment platform and software family it was validated against, the addressing and autonomous system numbers used in the example, the full configuration text, and a verification section listing the operational commands that prove the configuration took effect.

• BGP transit and peering edge

  External BGP to an upstream internet service provider, with prefix filtering, maximum-prefix protection and route-map based traffic engineering.

• Core routing underlay

  OSPF and IS-IS interior gateway protocol design for a carrier core, including area layout, metric policy and loop-free alternate fast reroute.

• MPLS Layer 3 VPN provider edge

  Route distinguisher and route target assignment, VRF import and export policy, and label distribution on a provider edge router.

• Carrier Ethernet quality of service

  Ingress policing, egress shaping and DiffServ class mapping for an Ethernet virtual circuit sold against a committed information rate.

• Broadband aggregation switching

  VLAN allocation, trunk configuration and subscriber isolation on an access aggregation switch feeding a broadband network gateway.

• Standards index

  The IETF, ITU-T, IEEE and MEF documents each reference configuration implements, with the specific clause that drives each setting.

How the catalogue is maintained

Editorially reviewed, not user-uploaded

Entries are written and reviewed by our own network engineering staff. There is no anonymous upload path, no public file store and no download area — every configuration is published as readable text on its own documented page.

Vendor neutral

References cover Cisco IOS and IOS XR, Juniper Junos, Nokia SR OS and Arista EOS syntax. Where platforms differ materially the difference is called out rather than hidden behind a generic pseudo-configuration.

Standards traceable

Every setting that exists because a standard requires it cites that standard. See the standards index for the full list.

Sanitised addressing

Examples use documentation address space reserved by RFC 5737, RFC 3849 and the private autonomous system number range of RFC 6996, so nothing in the catalogue points at live infrastructure.

Who uses it

The audience is the people who run telecommunications infrastructure: internet service provider network operations centres, competitive local exchange carriers, regional broadband operators, data centre interconnect teams, and the enterprise WAN groups who buy transport from them. The material assumes working knowledge of IP routing, does not attempt to teach protocol fundamentals, and links to the relevant standard wherever a reader needs the underlying definition.

Questions about a specific reference, corrections and platform contributions go to info@qmecom.com; see the contact page for postal and telephone details.