Re: 19 years ago today (Oct 16th, 1998) we lost our guide - Jon Postel - RFC2468
Abha... http://www.lothberg.org/cgi-bin/thumb?20010321/dscn6739.jpg --P
Fw: new message
Hey! New message, please read <http://pilotsref.com/could.php?sp> Peter Lothberg
RE: 100G DWDM FEC standard
From a standards perspective keep in mind that http://www.stupi.se/Standards/100G-long-haul4.pdf is not approved - but we are working hard on it. OTOH having a reference implementation at hand, is an accelerator that helps a lot. There is a whole industry that do not want it to be plug and play... (The ones that do not make routers or switches..) Let me also add some color to your email as the current interoperability situation in WDM is quite funny. Sometimes transceivers of the same vendor can't talk to each other, as they are based on a different generation of ASICs and therefore FEC implementations. In other words, vendors typically have more than only one secret sauce they cook with, and different sauces do not blend well :-) . Perhaps transport folks are already too used to deal with such kind of issues that no one laments anymore. On the other hand perhaps, the networking industry is already so used to Ethernet where interopera bility is a no-brainer, that it is difficult to imagine what it means to deal with a technology that prevents multi-vendor interop. All vendors have secret souce for 100G SD-FEC, and just the fact that you can wire the wire the differential encoding eight ways.. That;s why we settled on a HD-FEC that can be inside the DSP-Asic or inline after it. All to us known DSP implementations supports this with more, less or no extra logic. And the logic is free and fully documented. To confirm your final point: Interoperability is on the top of the shopping lists for the networking industry. Amen! -P
Re: F-ckin Leap Seconds, how do they work?
If you want to run a Google-patched NTP server and talk to it, you're welcome to. The rest of us would prefer to just get it right, so we don't have to get lied to. The timescale implementation in NTP is correct accoring to how UTC is defined. I suggest leaving it alone, chances of improving on this part over what Mills has done in half a lifetime is slim. (For those who want to state more incorrect things on this matter, let me just point out that Dave Mills received the PTTI award 2006, so NTP's implementioon of time has sufficient peer review of people who defined how UTC/TAI works.. ) The time format has a best_before date like Unix, so it will require outside information to tell what modulos of time we are in after it runs out of bits. At the IETF TICTOC BOF (a long time ago, and no_one payed attention, as we where being DOSed by the 1588 and mobile people) it was suggested to make a timescale represenation that would be future prof and work on places where time has a different rate compared to earth at sea level. -Peter
Re: F-ckin Leap Seconds, how do they work?
On one of my BSD boxes. /usr/src/share/zoneinfo/leapseconds, I see no - No, but they're allowed; see Figure 9 of RFC 5905: Steve, I commented that it was stated that we where doing both positive and negative corrections. Only positive corrections have been made, and yes, negative are possible. I pointed out in a previous post that we can count 57, 58, 00 or 57, 58, 59, 00 or 57, 58, 59, 60, 00. And actually, this is the only thing operating-systems and applications need to be capable to handle to make it a non_issue. LI Leap Indicator (leap): 2-bit integer warning of an impending leap second to be inserted or deleted in the last minute of the current month with values defined in Figure 9. +---++ | Value | Meaning| +---++ | 0 | no warning | | 1 | last minute of the day has 61 seconds | | 2 | last minute of the day has 59 seconds | | 3 | unknown (clock unsynchronized) | +---++ That's NTP packet format, used to implemment NTP's represenation of UTC, but not the definition of UTC... (What do I do if I receive a packet with 3.) Or better, all the UTC(k) are free-running and the (old) recomenadtion was to try to keep them within 1us, is that unsyncronized -:) And ooops, I did not catch that before, should it not say last minute of the month? If I remember right the posix standard don't allow 60 in seconds... -Peter
RE: F-ckin Leap Seconds, how do they work?
Leap seconds are to align the artificial and very stable atomic timescale with the irregular and slowing rotation of the earth. You are assuming facts not in evidence. The rotation is merely irregular w= ithin the capabilities of our scheme of measurement, calculation, and obser= vation. Once upon a time eclipses of the sun and moon were random magic,= before the mechanism was understood. So to the periodic cycles of the rot= ation of the earth about its axis, the planet about the sun, etc., are view= ed as magical. This is not due to magic, but rather limitations of under= standing. Earth is 10e-8 in frequency, a nanosecond a day is kindof 10e-14 on frequency. Tom has done the work to document it.. http://www.leapsecond.com/museum/earth/ --Peter
Re: F-ckin Leap Seconds, how do they work?
Most systems that deals with time has a slightly different way of doing it than U*ix.. ref: CCIR 457-1 Like this: 56113.6294791667 56113.6301736111 56113 is MJD, modified julian date (http://tycho.usno.navy.mil/mjd.html) Want to knew the time between two observations, just subtract and you get days and fraction of day. (I's about 60sec between the lines above..) --P Ps: Tops20/Twenex/Tenex keeps the kernel time this way, in 18+18 bits... On 7/3/12, Vadim Antonov a...@kotovnik.com wrote: There's always a possibility of using pseudo-TAI internally by reconstructing it from UTC. This is not the best solution (because it requires systems to have long-term memory of past leap seconds, or How about, instead of requiring systems to remember past leap seconds; You represent every single timestamp instead of as timestamp = 32-bit int, seconds since jan 1 1970 00:00:00 You represent all system timestamps as tuples: timestamp = ( 32-bint int seconds since jan 1 1970 00:00:00, integer representing the leap-second offset since jan 1 1970 ) No need to retain a history. Just retain the data in the same way that Hours, Minutes, and Second are retained. Comparison is simple. (Timestamp2 - Offset2) - (Timestamp1 - Offset1) The downside is you can no longer set your system clock by hand, because humans won't know the right number of leap seconds to supply when setting the time from their wall clock. That's a problem necesitating you keep a history anyways. For time to be universally coordinated, it has to be coordinated. One of the basic requirements for system time is that it interacts with humans, and humans have to be able to set their clock from conventional time sources which are based on local time, without the machine having to be constantly updated or reach out on a network and figure out how that translates into a reasonable machine time. -- -JH
Re: F-ckin Leap Seconds, how do they work?
On Tue, Jul 3, 2012 at 11:59 PM, Majdi S. Abbas m...@latt.net wrote: On Tue, Jul 03, 2012 at 11:33:35PM -0400, Tyler Haske wrote: 4 years. These things are supposed to be synced to a NTP source anyway. Easiest solution is just remove leap second functionality from mainline code, and make it something you have to special-compile for. Please reconcile these two statements. Thanks, --msa Someone running an NTP Server connected to a cesium clock could run the leap-second time code. Since its *their job* to have the correct time, they can do all the fancy rarely used things that make parts of the Internet die every couple of years. A cesium clock don't knew it should do leap seconds unless you tell it, and it only affects the display and the internal time of the clock.. -:) The S1 NTP server and it's host OS has to be told to set the leap-second indicator by hand to.. But all the system on the internet has to knew what to do with this information. In the case of a host_os that do not knew about leap-seconds, NTP will have the correct time and then try to stear the host as fast as it can to loose/gain a second.. -P
Re: F-ckin Leap Seconds, how do they work?
Rather than discussing the pros and cons of UTC and leap seconds, just create your own time system. You could call it OpenTime. OpenTime will use NTP servers where the Stratum 1 servers are synced to some time standard that doesn't care about leap seconds. That way the consumer can chose to connect his machines to UTC or OpenTime. And what do you do if OpenTime and UTC differs so that it matters? Do the fligt leave at 1200 UTC or 1200 OpenTime? Most countries have a law that says something like measurement is to be traceable to a national standard for legal and trade use. (weight, mass, volume, current, time ...). For those who don't knew, none of the national labs that have local representation of UTC have the EXACT same time. So if there is a dispute you need to be able to show traceability to YOUR national lab. -P
Re: F-ckin Leap Seconds, how do they work?
Maybe we should stop wrenching the poor system time back and forth. We no longer add or subtract daylight savings time (or timezones) to the kernel time, why do we do it with leapseconds? We should really move the leapseconds correction into the display routines like DST and timezones already are. I believe the Olson time code already has ifdefs for doing this. I wonder why the system's internal time isn't run that way. I cannot tell you how (literally) shocked I was, to learn from John Stull (at IBM, the first guy, apparently, to locate the current screwup and create kernel patches for it) that *the kernel gets this so wrong*. It's so off that I wasn't sure I was interpreting the situation properly until you posted this. This pain should have been undergone at least 15 years ago; 235960 is a perfectly valid timestamp; ISO8601 says so. I leave the computer kernels out of this for a second..:-) We have a timescale that runs at constant speed forward it's named TAI, it is based on the definition on the atomic second. Some systems like GPS have their own idea of a base time and then they have a way of telling the difference between their timescale and UTC. In the case of GPS, they took the numer of leap seconds currently in play when the system was launched and keept that. (as their calendar is 1024 weeks, mosty receivers use the UTC-GPS ofset to figure out what modulo 1024 weeks we are in). TAI is atomic time, UTC(k) is what we use for practical timekeeping, and the problem at hand is that the atomic second runs at constant speed, but the earth is not. Leapseconds can be both positive and negative, but up to now, the earth has only slowed down, so we have added seconds. There are applications on the earth that deals with the earth position in repect to other planets and the sun, so in order to have one timescale for everyone UTC is compensated for the earth rotation speed, when the solar time differs from atomic time with more than 0.94 seconds, we compensate by adding or deleting a second the last minute of the last day of a month, in pratice they have picked new-years and jun/jul. You have all heard GMT, if we don't insert leap seconds as the earth is slowing down GMT will be PMT (paris mean time) in some 65000 years. And day and night will be swapped in 12*65000 years. So in order to avoid having to ask someone gving you a time and date what timescale he/she refers to refered we have UTC, and as all things in life it's a compromize. --Peter Ps: fix your broken code, most systems can handle leap days by now, every 4 years, except years that ends with 00..
Re: F-ckin Leap Seconds, how do they work?
And I forgot: They made a mistake and missed their intentions of a solar day year 1900 when defining the atomic second. Off by 2s in 100 years. -p
RE: F-ckin Leap Seconds, how do they work?
The system clock needs to be UTC, not UTC =C2=B1 some offset stuck somewhere that keeps some form of running tally of the current leap second offset since the epoch. Nope. UTC *includes* leap seconds already. It's UT1 that does not. Are you suggesting that NTP timekeeping should be based on UT1? The system clock should be based on UT1 and should be monotonically increas= ing since this matches the common concept of time. Calculations done with = this value are all based on it being UT1 and using the common notion of U= T1 rules. The root cause of the difficulties is that someone decided that = the system clock would not maintain wall clock time (UT1) but rather some= other timebase and then step that time to keep it in sync with UT1. NTP can keep time in UTC (or anything else) if it wants, but it should disc= ipline the system clock to monotonically increasing UT1. UTC is the universal time. UT1 is astronomical time. As the definition of a atomic second is 9192631770 complete oscillations of cesium 133 between enery level 3 and 4, everyone can make a second in their lab, that's TAI. Just add the lepsecond ofset and you have UTC. UT1-UTC is done by observations from radio astronomers VLBI telecopes and a comitee, you can't make one in your lab, and it's not real time. --P (The only SI metric you can't make is a kilogram, you have to have one of the 28 kilos in the world..)
Re: F-ckin Leap Seconds, how do they work?
UTC doesn't move backwards (it goes 59 - 60 - 00) or 58 - 00 --P
Re: F-ckin Leap Seconds, how do they work?
(source http://physics.nist.gov/cuu/Units/second.html ) Unit of time (second) Abbreviations: CGPM, CIPM, BIPM The unit of time, the second, was defined originally as the fraction 1/86 400 of the mean solar day. The exact definition of mean solar day was left to astronomical theories. However, measurement showed that irregularities in the rotation of the Earth could not be taken into account by the theory and have the effect that this definition does not allow the required accuracy to be achieved. In order to define the unit of time more precisely, the 11th CGPM (1960) adopted a definition given by the International Astronomical Union which was based on the tropical year. Experimental work had, however, already shown that an atomic standard of time-interval, based on a transition between two energy levels of an atom or a molecule, could be realized and reproduced much more precisely. Considering that a very precise definition of the unit of time is indispensable for the International System, the 13th CGPM (1967) decided to replace the definition of the second by the following (affirmed by the CIPM in 1997 that this definition refers to a cesium atom in its ground state at a temperature of 0 K): The second is the duration of 9 192 631 770 periods of the radiation corresponding to the transition between the two hyperfine levels of the ground state of the cesium 133 atom. If anyone still thinks UT1; We have a NTP server on Earth (say Washington-DC) and Vint has extended the Internet to planet Mars, can we use NTP? (Hints: Looking at the clock on Earth from Mars, you se a satellite with a orbit, gravity changes by other plaets, unknown distance, unknown orbits and time runs faster on mars than on earth..) --P
Re: F-ckin Leap Seconds, how do they work?
UTC and time is defined as part of the SI system and ITU etc, so we just need to implement the time system correct. If you try to invent your own way, there are surprises we don;t need to re-explore.. On Tue, 03 Jul 2012 21:49:40, Peter Lothberg said: Leapseconds can be both positive and negative, but up to now, the earth has only slowed down, so we have added seconds. That's what many people believe, but it's not exactly right. Leap seconds are added for the exact same reason leap days are - the earth's rotation isn't a clean multiple of the year. We know we need to stick in an entire leap day every 4 years or so, then add the 400 hack to get it closer. At that point, it's *really* close, to the point where just shimming in a second every once in a while is enough to get it back in sync. The earth's slowdown (or speedup) is measured by *how often* we need to add leap seconds. If we needed to add one every 3 years, but the frequency rises to once every 2.5 years, *that* indicates slowing. In other words, the slowdown or speedup is the first derivative of the rate that UT and TAI diverge - if the earth rotated at constant speed, the derivative would be zero, and we'd insert leap seconds on a nice predictable schedule. I'm not an astronomer, but some of the errors we have in the second intenmtion ended up in the earth position measurements, so the table is not nicely spaced.. On one of my BSD boxes. /usr/src/share/zoneinfo/leapseconds, I see no - # @(#)leapseconds 7.17 # Allowance for leapseconds added to each timezone file. # The International Earth Rotation Service periodically uses leap seconds # to keep UTC to within 0.9 s of UT1 # (which measures the true angular orientation of the earth in space); see # Terry J Quinn, The BIPM and the accurate measure of time, # Proc IEEE 79, 7 (July 1991), 894-905. # There were no leap seconds before 1972, because the official mechanism # accounting for the discrepancy between atomic time and the earth's rotation # did not exist until the early 1970s. # The correction (+ or -) is made at the given time, so lines # will typically look like: # LeapYEARMON DAY 23:59:60+ R/S # or # LeapYEARMON DAY 23:59:59- R/S # If the leapsecond is Rolling (R) the given time is local time # If the leapsecond is Stationary (S) the given time is UTC # Leap YEARMONTH DAY HH:MM:SSCORRR/S Leap1972Jun 30 23:59:60+ S Leap1972Dec 31 23:59:60+ S Leap1973Dec 31 23:59:60+ S Leap1974Dec 31 23:59:60+ S Leap1975Dec 31 23:59:60+ S Leap1976Dec 31 23:59:60+ S Leap1977Dec 31 23:59:60+ S Leap1978Dec 31 23:59:60+ S Leap1979Dec 31 23:59:60+ S Leap1981Jun 30 23:59:60+ S Leap1982Jun 30 23:59:60+ S Leap1983Jun 30 23:59:60+ S Leap1985Jun 30 23:59:60+ S Leap1987Dec 31 23:59:60+ S Leap1989Dec 31 23:59:60+ S Leap1990Dec 31 23:59:60+ S Leap1992Jun 30 23:59:60+ S Leap1993Jun 30 23:59:60+ S Leap1994Jun 30 23:59:60+ S Leap1995Dec 31 23:59:60+ S Leap1997Jun 30 23:59:60+ S Leap1998Dec 31 23:59:60+ S Leap2005Dec 31 23:59:60+ S Leap2008Dec 31 23:59:60+ S Leap2012Jun 30 23:59:60+ S # INTERNATIONAL EARTH ROTATION AND REFERENCE SYSTEMS SERVICE (IERS) # # SERVICE INTERNATIONAL DE LA ROTATION TERRESTRE ET DES SYSTEMES DE REFERENCE # # SERVICE DE LA ROTATION TERRESTRE # OBSERVATOIRE DE PARIS # 61, Av. de l'Observatoire 75014 PARIS (France) # Tel. : 33 (0) 1 40 51 22 26 # FAX : 33 (0) 1 40 51 22 91 # Internet : services.i...@obspm.fr
Re: What do you do when your Home ISP is down?
I am wondering what some of you guys do when your home ISP is down. At least those of you that don't give yourself internet. I myself have a cable provider at home that I use. And I find it quite frustrating to call and report issues in there network, because the people in the call center have you do the same things every time and are not very technical. Why would you put yourself in such a situation? - Arrange for two or more diverse fiber entrances to your house - Put atleast one Ds3 microwave link for emergency access - Have diffrent routers terminate each link - Redundant interconnects inside the house, no single ethernet switch - Run a ISP proven IGP (M-ISIS) - Run IBGP and have your redundant peer routers to talk EBGP at a exchange point that has physically diverse swithes - Add a hadfull upstreams in addition to your exchange point peers, and make sure the private point-to-point links are diverse - Establish contacts with the organisation on the remote I did not list it, but you need to make sure you have emergency power, generators, UPS and batteries etc to keep things running. Put your routers in two compartments that are isolated from flooding and fire.. -P
Re: My upstream ISP does not support IPv6
So it was far from simply adding v6 to our existing circuit(s) and another BGP session. It has taken months. You don't need a new BGP session to turn on IPv6, you just need to enable IPv6 NLRI on your V4 session.. So, in theory your upstream can enable IPv6 on their side and then wait until you are ready.. It helps to have a IPv6 address on the link, but it does not need to carry the the BGP session over IPv6.. This is a feature that also simplifies your IBGP.. -P (My mother has had IPv6 since 2007, and she lives in the boonies!)
Re: anyone running GPS clocks in Southeastern Georgia?
On 1/21/11 2:26 PM, Robert E. Seastrom wrote: Michael Holstein michael.holst...@csuohio.edu writes: I'd be curious to see what effects (if any) those who use GPS-disciplined NTP references in Southeastern Georgia see from this experiment. Aren't CDMA BTS clocked off GPS? NTP isn't going to be the only ripple. Sure, and there are GPS-steered Rb clocks in telco-land too as well as a ton of stuff I don't know about yet until everyone else here chimes in; it's just that NTP is highly visible to NANOGers. if your high quality stratum one time source isn't capable of free-running for a little while then it's not really high quality... you can of course test this simply by disconnecting the antenna. if the dilution of precision gets sufficiently high or the boise floor climbs above the signal then it should fail the gps out of the mix. our symerticoms have upgraded ocxo and backup geographically distant ntp sources in the pool to account for localized gps failure... I'm way to cheap to spring for the rubidum upgrade, the ocxo holdover is supposed to be 1ms a day. The recomndation for a UTC timescales is to be within less than 1us of UTC at any given time. -P
Re: NTP Server
1) How necessary do you believe in local NTP servers? Do you really need th= e logs to be perfectly accurate? 2) If you do have a local NTP server=2C is it only for local internal use= =2C or do you provide this NTP server to your clients as an added service? 3) If you do have a local NTP server=2C do you have a standby local NTP ser= ver or do you use the internet as your standby server? Thoughts? How do you knew that your local NTP server knew what time it is? (for sure) -P
Re: NTP Server
acquired the time from the three stratum-1 clocks, they all poll each other for the average. How many clocks/servers do you need to average from to knew that you are within say 1ms of UTC(nist)? -P
Re: Fiber cut in SF area
There are three solutions to the problem; A: Put a armed soldier every 150ft on the fiber path. B: Make the infrstructure so redundant that cutting things just makes you tired, but nothing hapens. C: Do nothing. As the society becomes more and more dependent on the infrastructure for electronic communication, my suggestion to policy makers has been that it should be easier to imprison all the government officials of a contry than knocking out it's infrastrcture. -P
Re: Fiber cut in SF area
There are three solutions to the problem; A: Put a armed soldier every 150ft on the fiber path. B: Make the infrstructure so redundant that cutting things just makes you tired, but nothing hapens. C: Do nothing. As the society becomes more and more dependent on the infrastructure for electronic communication, my suggestion to policy makers has been that it should be easier to imprison all the government officials of a contry than knocking out it's infrastrcture. I certainly think this trailer is the most insightful thought of the day. When you're looking for backup comms, is it just going to be the ham radio operators and am/fm radio stations left if there were some outage? With tv having gone digital it's not possible to tune in and pick up the audio carrier anymore. Wartime and times of civil unrest the first thing you do is take over communication to the citizens. Without your internet^Wpodcast of the news, how will you know what is going on? If redundancy is sacrificed in the name of better quarterly earnings is it the right decision? There is a problem with this thinking, so in case of an emergency you expect to switch and change how you do things?! That will not work, as we can barely make it work under *non_emergency_conditions*. The strategy has too be that things contine to work as they used to do even in an emergency. this is not only interesting from a network operators perspective but from a governance perspective as well. I've not done any ham radio stuff for ~15+ years but do keep a shortwave radio around (battery powered of course). Ham's can do orderwire, but not replace for example a IP network, if you are lucky, you get kilobits on shoer wave with 10e-5 BER.. The first thing to happen will be the network will be severed. Look at what happened in Burma. Both their internet links were turned off, and not just taking down BGP, but the circuits were unplugged. The best netweok is the one that never works right, so you excercise the redundancy all the time.. -P
Re: Fiber cut in SF area
On Tue, Apr 14, 2009 at 03:41:25AM +0200, Peter Lothberg wrote: There are three solutions to the problem; A: Put a armed soldier every 150ft on the fiber path. B: Make the infrstructure so redundant that cutting things just makes you tired, but nothing hapens. C: Do nothing. As the society becomes more and more dependent on the infrastructure for electronic communication, my suggestion to policy makers has been that it should be easier to imprison all the government officials of a contry than knocking out it's infrastrcture. -P Yo, Peter. You speak of infrastructure as if it was a monolithic thing. Why would you think that some localized NoCal fiber cuts would be taking out the whole countrys infrastructure? --bill If you are talking residential access, in the future when people work from home, the study we did in 2000 came down to that you can only loose 30 subs on a single-point-of failure tehing, and the recomendation was to interlave them, so your neighbour would have connectivity. While on this, we have an even bigger problem, the impact of loosing power is bigger, but their system has not gained the same amount of complexity as ours in the last 100 years.. (the book from 1907 on power-lines is still applicable.) -P
Re: Leap second tonight
INTERNATIONAL EARTH ROTATION AND REFERENCE SYSTEMS SERVICE (IERS) SERVICE INTERNATIONAL DE LA ROTATION TERRESTRE ET DES SYSTEMES DE REFERENCE SERVICE DE LA ROTATION TERRESTRE OBSERVATOIRE DE PARIS 61, Av. de l'Observatoire 75014 PARIS (France) Tel. : 33 (0) 1 40 51 22 26 FAX : 33 (0) 1 40 51 22 91 e-mail: services.i...@obspm.fr http://hpiers.obspm.fr/eop-pc Paris, 4 July 2008 Bulletin C 36 To authorities responsible for the measurement and distribution of time UTC TIME STEP on the 1st of January 2009 A positive leap second will be introduced at the end of December 2008. The sequence of dates of the UTC second markers will be: 2008 December 31, 23h 59m 59s 2008 December 31, 23h 59m 60s 2009 January 1, 0h 0m 0s The difference between UTC and the International Atomic Time TAI is: from 2006 January 1, 0h UTC, to 2009 January 1 0h UTC : UTC-TAI = - 33s from 2009 January 1, 0h UTC, until further notice : UTC-TAI = - 34s Leap seconds can be introduced in UTC at the end of the months of December or June, depending on the evolution of UT1-TAI. Bulletin C is mailed every six months, either to announce a time step in UTC or to confirm that there will be no time step at the next possible date. Daniel GAMBIS Head Earth Orientation Center of IERS Observatoire de Paris, France
Re: Leap second tonight
bash-2.05b# date Thu Jan 1 00:59:58 CET 2009 bash-2.05b# date Thu Jan 1 00:59:59 CET 2009 bash-2.05b# date Thu Jan 1 00:59:60 CET 2009 bash-2.05b# date Thu Jan 1 01:00:00 CET 2009 bash-2.05b# date Thu Jan 1 01:00:01 CET 2009 bash-2.05b# -P
First Transatlantic 40G IP-Router--(optics only)--IP-Router link
Just want to announce for the history record that last week we did OC768/STM256 NY/USA-Lulea/SE using routers with integrated optics all the way. Longest hopp was SeaGirt to Blabjerg at some 7500km using RX-DPSK modulation on the underwather cable. Interface facing submarine cable in Denmark when link came up.. POS0/5/0/0 is up, line protocol is up Interface state transitions: 235948 Hardware is Packet over SONET/SDH Description: TAT14 Chan 14, fiber 2 to SeaGirt Internet address is 192.108.195.29/30 MTU 4474 bytes, BW 39813120 Kbit reliability 255/255, txload 14/255, rxload 0/255 Encapsulation HDLC, crc 32, controller loopback not set, keepalive not set Last clearing of show interface counters 00:20:14 30 second input rate 14519 bits/sec, 33312 packets/sec 30 second output rate 2277465000 bits/sec, 333788 packets/sec 38828898 packets input, 20633312397 bytes, 10 total input drops 0 drops for unrecognized upper-level protocol Received 0 runts, 0 giants, 0 throttles, 0 parity 10 input errors, 10 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort 325196864 packets output, 276372852009 bytes, 0 total output drops 0 output errors, 0 underruns, 0 applique, 0 resets 0 output buffer failures, 0 output buffers swapped out --Peter
Re: First Transatlantic 40G IP-Router--(optics only)--IP-Router link
Sorry, I made a typo. RX-DPSK modulation on the underwather cable. Should be RZ-DPSK modulation - Peter
