{"id":5141,"date":"2015-02-27T15:12:40","date_gmt":"2015-02-27T15:12:40","guid":{"rendered":"http:\/\/32478000127144839.blog.com.gr\/?page_id=5141"},"modified":"2025-10-09T09:42:19","modified_gmt":"2025-10-09T09:42:19","slug":"technical-specifications","status":"publish","type":"page","link":"https:\/\/www.gr-ix.gr\/el\/technical-specifications\/","title":{"rendered":"Technical Specifications"},"content":{"rendered":"<div id=\"landing\">\n<div class=\"container\">\n<div class=\"row\">\n<div class=\"span12\">\n<h2>Physical Interface Specifications<\/h2>\n<p>The following types\/speeds of Ethernet interfaces are available:<\/p>\n<table class=\"table\">\n<thead>\n<tr>\n<th class=\"name\" valign=\"top\">If\/ce<\/th>\n<th class=\"name\" valign=\"top\">\n<p style=\"text-align: left;\">Cable\/Fibre Type<\/p>\n<\/th>\n<th class=\"name\" valign=\"top\">WaveLength<\/th>\n<th class=\"name\" valign=\"top\">Distance<\/th>\n<th class=\"name\" valign=\"top\">Input<br \/>\n(dbm)<\/th>\n<th class=\"name\" valign=\"top\">Output<br \/>\n(dbm)<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"text-align: center;\" colspan=\"6\" valign=\"top\"><span style=\"font-size: 14px;\"><strong>1 Gbps<\/strong><\/span><\/td>\n<\/tr>\n<tr>\n<td valign=\"top\"><strong>TX<\/strong><\/td>\n<td valign=\"top\">UTP cat5e<\/td>\n<td style=\"text-align: center;\" valign=\"top\">N\/A<\/td>\n<td style=\"text-align: center;\" valign=\"top\">100m<\/td>\n<td style=\"text-align: center;\" valign=\"top\">N\/A<\/td>\n<td style=\"text-align: center;\" valign=\"top\">N\/A<\/td>\n<\/tr>\n<tr>\n<td valign=\"top\"><strong>SX*<\/strong><\/td>\n<td valign=\"top\">MultiMode fibre 62.5\/125\u03bcm OM1<\/td>\n<td style=\"text-align: center;\" valign=\"top\">850 nm<\/td>\n<td style=\"text-align: center;\" valign=\"top\">275m<\/td>\n<td style=\"text-align: center;\" valign=\"top\">0 \u2026 -21<\/td>\n<td style=\"text-align: center;\" valign=\"top\">~-3<\/td>\n<\/tr>\n<tr>\n<td valign=\"top\"><strong>LX<\/strong><\/td>\n<td valign=\"top\">SingleMode fibre<\/td>\n<td style=\"text-align: center;\" valign=\"top\">1310 nm<\/td>\n<td style=\"text-align: center;\" valign=\"top\">10km<\/td>\n<td style=\"text-align: center;\" valign=\"top\">-3 \u2026 -25<\/td>\n<td style=\"text-align: center;\" valign=\"top\">-3<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: center;\" colspan=\"6\" valign=\"top\"><span style=\"font-size: 14px;\"><strong>10 Gbps<\/strong><\/span><\/td>\n<\/tr>\n<tr>\n<td valign=\"top\"><strong>SR*<\/strong><\/td>\n<td valign=\"top\">MultiMode fibre 62.5\/125\u03bcm OM1<\/td>\n<td style=\"text-align: center;\" valign=\"top\">850 nm<\/td>\n<td style=\"text-align: center;\" valign=\"top\">33m<\/td>\n<td style=\"text-align: center;\" valign=\"top\">-1 \u2026 -9.9<\/td>\n<td style=\"text-align: center;\" valign=\"top\">~ -1<\/td>\n<\/tr>\n<tr>\n<td valign=\"top\"><strong>LR<\/strong><\/td>\n<td valign=\"top\">SingleMode fibre 9\/125<\/td>\n<td style=\"text-align: center;\" valign=\"top\">1310 nm<\/td>\n<td style=\"text-align: center;\" valign=\"top\">10km<\/td>\n<td style=\"text-align: center;\" valign=\"top\">0.5 \u2026 -18<\/td>\n<td style=\"text-align: center;\" valign=\"top\">~0.5<\/td>\n<\/tr>\n<tr>\n<td valign=\"top\"><strong>ER<\/strong><\/td>\n<td valign=\"top\">SingleMode fibre<\/td>\n<td style=\"text-align: center;\" valign=\"top\">1550 nm<\/td>\n<td style=\"text-align: center;\" valign=\"top\">40km<\/td>\n<td style=\"text-align: center;\" valign=\"top\">-1 \u2026 -15.8<\/td>\n<td style=\"text-align: center;\" valign=\"top\">~4<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: center;\" colspan=\"6\" valign=\"top\"><span style=\"font-size: 14px;\"><strong>100 Gbps<\/strong><\/span><\/td>\n<\/tr>\n<tr>\n<td valign=\"top\"><strong>LR4*<\/strong><\/td>\n<td valign=\"top\">SingleMode fibre 9\/125<\/td>\n<td style=\"text-align: center;\" valign=\"top\">1310 nm<\/td>\n<td style=\"text-align: center;\" valign=\"top\">10km<\/td>\n<td style=\"text-align: center;\" valign=\"top\">-10.6 \u2026 4.5 each lane<\/td>\n<td style=\"text-align: center;\" valign=\"top\">-4.3 \u2026 4.5 each lane<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>*only available in ATH01 POP.<\/p>\n<p>&nbsp;<\/p>\n<h2>Ethernet Specifications<\/h2>\n<h3>Framing &amp; Ethertypes<\/h3>\n<p>The GR-IX infrastructure offers ports that implement the Ethernet standard (IEEE 802.3-2012 \/ Ethernet II).<\/p>\n<p>The members\u2019 ports are, by default, in \u201caccess\u201d mode, which means that only untagged Ethernet Frames are allowed. 802.1q-tagged frames can be supported, if necessary (e.g., for private peerings).<\/p>\n<p>Allowed ethertypes are: <em><strong>IPv4 (0x0800), IPv6 (0x06dd), ARP (0x0806) and 802.3ad \u2013 LACP (0x8809)<\/strong><\/em>. Traffic with any other ethertype may be dropped without notice.<\/p>\n<h3>Maximum Transmission Unit (MTU)<\/h3>\n<p>The allowed L2 payload (L3 MTU) for GR-IX is 9000 bytes. Frames exceeding this payload may be dropped without further notice.<\/p>\n<h3>Link Aggregation (a.k.a link-bundling, ether-channel, port-channel)<\/h3>\n<p>Links of the same speed, on the same device, can be bundled into a single logical interface. Bundling can be configured statically or dynamically through LACP (802.3ad).<\/p>\n<p>In both cases,\u00a0<strong>per-flow<\/strong> load-balancing is implemented\u00a0 (source\/destination IP addresses &amp; ports).<\/p>\n<h3>Port Speed\/Duplex<\/h3>\n<p><span style=\"color: #000000;\"><span style=\"color: #000000;\"><span style=\"text-decoration: underline;\">For copper ports<\/span>, GR-IX explicitly configures speed and full-duplex on its side; and auto-negotiation is enabled (so that these settings are advertised to the members). Members can explicitly configure speed\/full-duplex, or rely on a<\/span><span style=\"color: #000000;\">uto-negotiation, or do both (explicitly configure speed\/full-duplex and keep auto-negotiation active) &#8212; the latter is the safest option, thus suggested.<br \/>\n<\/span><\/span><\/p>\n<h2>Public Peering LAN Specifications<\/h2>\n<h3>Addressing<\/h3>\n<div id=\"list-prefixes\">\n<div class=\"row sub\">\n<div class=\"col-xs-8 col-sm-8 col-md-8\">The public peering LAN address space is:<\/div>\n<ul>\n<li class=\"col-xs-8 col-sm-8 col-md-8\">GR-IX::Athens:\n<ul>\n<li class=\"col-xs-8 col-sm-8 col-md-8\">IPv4: <strong>176.126.38.0\/25<\/strong><\/li>\n<li class=\"col-xs-8 col-sm-8 col-md-8\">IPv6: <strong>2001:7f8:6e::\/64<\/strong><\/li>\n<\/ul>\n<\/li>\n<li class=\"col-xs-8 col-sm-8 col-md-8\">GR-IX::Thessaloniki:\n<ul>\n<li class=\"col-xs-8 col-sm-8 col-md-8\">IPv4: <strong>185.1.123.0\/25<\/strong><\/li>\n<li class=\"col-xs-8 col-sm-8 col-md-8\">IPv6: <strong>2001:7f8:ce::\/64<\/strong><\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/div>\n<\/div>\n<p>&nbsp;<\/p>\n<p>Members are assigned one IPv4 and one IPv6 address per physical port or bundle in order to connect their router on the public peering LAN. Under certain circumstances, a second IPv4 and a second IPv6 address can be assigned for redundancy.<\/p>\n<p>Members are not allowed to use IPs other that the ones assigned to them on the ports connecting to GR-IX. Proxy-ARP is not allowed on the GR-IX ports; and NAT is not allowed on the GR-IX IPs.<\/p>\n<p>Members are not allowed to redistribute the peering LAN address space into their eBGP and announce it to other AS.<\/p>\n<h3>MAC addresses<\/h3>\n<h4>MAC address policy and MAC address change<\/h4>\n<p>For each assigned GR-IX IP address, members need to specify a single corresponding MAC address. Based in this correlation, GR-IX statically configures the provided MAC addresses on the relevant ports (static mac learning and layer2 access lists that drop traffic sourced from other MAC addresses).<\/p>\n<\/div>\n<div class=\"span12\">In case of hardware replacement (router, port, card etc), the member need to contact GR-IX personnel in order to explicitly allow the new MAC. To facilitate the transition, both old and new MAC can be permitted for a limited period of time.<\/div>\n<div class=\"span12\"><\/div>\n<div class=\"span12\">\n<p>Please note that, after a MAC change, the other members&#8217; ARP tables need to be updated. This process relies on appropriate ARP\/gARP messages between the replaced equipment and the equipment of each of the member&#8217;s peers. If, for any reason, this process fails for a peer, significant downtime might occur. In order to resolve such a problem, the member will need to communicate directly with the affected peer(s) &#8212; GR-IX is unable to trigger such an ARP update.<\/p>\n<h4>Static MAC allocation<\/h4>\n<p>Instead of using their hardware MAC addresses, GR-IX members may use MAC addresses statically assigned to them by GR-IX. These MAC addresses belong to the Locally Administered Address Range and are of the form:<\/p>\n<ul>\n<li>GR-IX::Athens:<strong> ee:01:26:38:0X:XX<\/strong><\/li>\n<li>GR-IX::Thessaloniki:<strong> ee:01:26:38:1X:XX<\/strong><\/li>\n<\/ul>\n<p>(where X:XX = the decimal digits of the last byte of the corresponding IP address)<\/p>\n<p><strong>Examples<\/strong><\/p>\n<p>IP: 176.126.38.<strong>1<\/strong>, MAC: ee:01:26:38:00:0<strong>1<\/strong><br \/>\nIP: 176.126.38.<strong>123<\/strong>, MAC: ee:01:26:38:0<strong>1<\/strong>:<strong>23<\/strong><\/p>\n<\/div>\n<div class=\"span12\">Although the use of statically assigned MAC addresses is <strong>optional<\/strong>, it is highly <strong>recommended<\/strong>: Hardware can be replaced without affecting the MAC address in use. Hence, no communication, scheduling or coordination with GR-IX or other members is required. Apart from that, the use of such MAC addresses makes debugging and troubleshooting is easier, as MAC&lt;-&gt;IP correlation is evident.<\/div>\n<div class=\"span12\">\n<h3>Port Limitations<\/h3>\n<ul>\n<li><strong>Spanning tree &amp; BPDUs:<\/strong> Incoming BPDUs are ignored (and dropped). The GR-IX infrastructure will not send or forward BPDUs towards its members.<\/li>\n<li><strong>Broadcast traffic (destination MAC FF:FF:FF:FF:FF):<\/strong> Broadcast traffic, with the exception of ARP broadcasts, is dropped<\/li>\n<li><strong>Storm Control:<\/strong> No more than 50Mbps of the incoming traffic of each port can be unknown unicast, multicast or broadcast. Traffic above this level is dropped.<\/li>\n<li><strong>ICMP redirects: <\/strong>ICMP redirects are not allowed and dropped.<\/li>\n<\/ul>\n<h3>Traffic Limitations<\/h3>\n<ul>\n<li>Internal Traffic: The members are allowed to exchange a limited amount of internal traffic (i.e between a member&#8217;s own ports) over the GR-IX infrastructure. See &#8220;<a href=\"\/terms\/\">terms of use<\/a>&#8221; for more details.<\/li>\n<li>Members are not allowed to advertise spoofed or private address space and AS numbers.<\/li>\n<li>Multicast is not allowed on the public peering LAN<\/li>\n<\/ul>\n<p>&nbsp;<\/p>\n<h2>Private Interconnects<\/h2>\n<ul>\n<li><strong>Point-or-point or Multipoint private interconnects<\/strong> can be provided between two or more members, on a single or on several POPs. The same specifications and restrictions with the public peering LAN apply.<\/li>\n<li>Especially for <strong>point-to-point private interconnects <\/strong> between two ports <strong>on the same POP<\/strong>, the above restrictions can be removed, if requested; in that case all traffic received at each endpoint will be transparently forwarded to the other one.<\/li>\n<li>Private interconnects require an 802.1q trunk port between GR-IX and the member; VLAN tags on that port separate this traffic from the public peering lan or other private interconnects on the same port.<\/li>\n<\/ul>\n<p>&nbsp;<\/p>\n<h2>Implementation Directives<\/h2>\n<p>The members are encouraged to implement the following directives:<\/p>\n<ul>\n<li>Disable spanning tree on the GR-IX port. Disable outgoing BPDUs and ignore incoming BPDUs (although no BPDUs should be received from a GRIX port).<\/li>\n<li>Disable all unnecessary protocols. Take extra care with link-local protocols, esp. discovery protocols such as LLDP or CDP and VLAN propagation protocols such as VTP or GVRP\/MRP.<\/li>\n<li>If possible, terminate the GR-IX connection on a L3 port rather than using a switchport and a SVI\/IRB interface, and avoid using L2 switches between GR-IX infrastructure and your L3 device.<\/li>\n<li>Terminating LACP and L3 on different devices is not recommended.<\/li>\n<\/ul>\n<p>&nbsp;<\/p>\n<h2>Other Good Practice<\/h2>\n<ul>\n<li>Keep your IRR records updated (eg, on RIPE whois database). Create <em>route objects<\/em> for all prefixes that may be advertised to your peers<\/li>\n<li>If other AS&#8217;s are advertised by you, create an appropriate AS-SET object and share it with your peers. Ask your downlink customers to keep their own IRR records updated.<\/li>\n<li>Register GR-IX as an exchange point in your <a href=\"https:\/\/www.peeringdb.com\">peeringdb<\/a> entry. If your network is not registered, please do.<\/li>\n<li>If possible, create and maintain <a href=\"https:\/\/en.wikipedia.org\/wiki\/Resource_Public_Key_Infrastructure#Route_Origination_Authorizations\">ROAs<\/a>. Even if you do not implement <a href=\"https:\/\/en.wikipedia.org\/wiki\/Resource_Public_Key_Infrastructure\">RPKI<\/a> on your network, the existence of ROAs may protect your prefixes from hijacking. (for RIPE members, this can be done easily through the <a href=\"https:\/\/lirportal.gr-ix.grripe.net\/\">LIR portal<\/a>)<\/li>\n<li>Several GR-IX members (including GR-IX route servers) implement automation that relies on the accuracy of IRR and\/or peeringdb data. Failing to keep this data updated may result into dropped bgp prefixes or even peering requests getting rejected.<\/li>\n<\/ul>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"<p>Physical Interface Specifications The following types\/speeds of Ethernet interfaces are available: If\/ce Cable\/Fibre Type WaveLength Distance Input (dbm) Output (dbm) 1 Gbps TX UTP cat5e N\/A 100m N\/A N\/A SX* MultiMode fibre 62.5\/125\u03bcm OM1 850 nm 275m 0 \u2026 -21 ~-3 LX SingleMode fibre 1310 nm 10km -3 \u2026 -25 -3 10 Gbps SR* MultiMode [&hellip;]<\/p>\n","protected":false},"author":2,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_uag_custom_page_level_css":"","footnotes":""},"class_list":["post-5141","page","type-page","status-publish","hentry"],"uagb_featured_image_src":{"full":false,"thumbnail":false,"medium":false,"medium_large":false,"large":false,"1536x1536":false,"2048x2048":false,"small":false,"thumb":false,"metro-small":false,"metro-horizontal":false,"metro-large":false,"relatedposts":false},"uagb_author_info":{"display_name":"admin","author_link":"https:\/\/www.gr-ix.gr\/el\/author\/stratis\/"},"uagb_comment_info":0,"uagb_excerpt":"Physical Interface Specifications The following types\/speeds of Ethernet interfaces are available: If\/ce Cable\/Fibre Type WaveLength Distance Input (dbm) Output (dbm) 1 Gbps TX UTP cat5e N\/A 100m N\/A N\/A SX* MultiMode fibre 62.5\/125\u03bcm OM1 850 nm 275m 0 \u2026 -21 ~-3 LX SingleMode fibre 1310 nm 10km -3 \u2026 -25 -3 10 Gbps SR* MultiMode&hellip;","_links":{"self":[{"href":"https:\/\/www.gr-ix.gr\/el\/wp-json\/wp\/v2\/pages\/5141","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.gr-ix.gr\/el\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/www.gr-ix.gr\/el\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/www.gr-ix.gr\/el\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.gr-ix.gr\/el\/wp-json\/wp\/v2\/comments?post=5141"}],"version-history":[{"count":9,"href":"https:\/\/www.gr-ix.gr\/el\/wp-json\/wp\/v2\/pages\/5141\/revisions"}],"predecessor-version":[{"id":6355,"href":"https:\/\/www.gr-ix.gr\/el\/wp-json\/wp\/v2\/pages\/5141\/revisions\/6355"}],"wp:attachment":[{"href":"https:\/\/www.gr-ix.gr\/el\/wp-json\/wp\/v2\/media?parent=5141"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}