Correct, they will wrap when you have moved more than about 4 billion bytes
(2^32) in a single 5 minute polling cycle. That works out to just over
114.5Mb/s
It's usually easiest these days to just use 64 bit counters for everything,
but with anything over essentially a 100M interface it's
We just run q-in-q from a relatively inexpensive CPE switch back to our
nearest node. The advantage to this is that it's simple, and we can run
either over our own fiber or tunnel through other carrier's networks if
needed for type-2 circuits. If you're tunneling you need to make sure your
carrier
...@gvtc.com]
Sent: Thursday, May 21, 2015 3:02 PM
To: 'Bill Wichers'; cisco-nsp@puck.nether.net
Subject: RE: [c-nsp] Virtual CPE as a service on Metro-E last mile -
Suggestions/inputs required
You mentioned ... I'm thinking q-in-q is what you mean when you say MAC
in MAC.
I've read
The problem data strings are usually either strings that match control
codes or long sequences of either all ones or all zeroes. If too many
bits go by without any transitions it is possible for the receiver to
loose sync with the network. You might want to just try a packet of all
zeroes or ones
I've found that some carriers consider Ethernet something of a toy
whereas TDM and SONET circuits are considered more mission critical.
Basically our local engineering gusy say that the Ethernet links are
just a bunch of jumpers in COs, and by that they mean a single link
patched through to where
RS-232 has more limitations than just cable capacitance. RS-232 is a
single-ended communication protocol (on the physical level), so it's
noise immunity is not very good. This is especially a problem if you're
running the cable in an electrically noisy environment (like a cable
tray or wiring
[snip]
I typically set both ends (router and switch) of these links to
100/full
since I've seen weird autonegotiation problems before. This works
just
fine for individual FE links, but as soon as I bring up the
Etherchannel
group both member links on the router end drop back to unknown
[snip]
... and the context of *this* discussion is likely involving
PA-FE-TX's,
which are quite old hardware, and cannot do any sort of autoneg.
True, so the ports should probably be nailed to full at both sides.
Correct, they are PA-FE-TX's. There are two such PAs in a VIP2-50, and
those
I have a strange problem getting an Etherchannel link betweek a 7507 and
a Cat 4006. Basically everything works, but the two FE interfaces on the
7507 (both in the same VIP) keep dropping their full-duplex config and
reporting unknown duplex instead. Traffic works across the link, load
is about
I'm seeing a strange problem with an OC3 link that should be really
simple. The link runs from a 4-port OC3 card in a 12012 to an old
POSIP-OC3-50 in a 7507. Earlier in the day one of the two POSIP cards in
the 7507 started running a *lot* of receive errors, all CRC, so we
thought maybe the optic
One quick question: is this your own dark fiber, or through a SONET
ADM,
or
through a service provider? Interestingly enough, the recommendation
for
dark
fiber is internal clocking on both ends.
Also note that the quad OC3 line cards in the 12000 have some
limitations
as
to clocking
We've seen some customers order 2 x 120 volt, 30 amp power circuits
which is about 5.8kW, and it's not uncommon. With the new blade server
people coming in we see 208 volt, 30 amp circuits being ordered and
those are approx 5kW each and it's not uncommon to have people order
multiple circuits
If there is anyone out there with some experience setting up HSRP on a
small datacenter-type core network with a few BGP peers please contact
me off list. We are looking for someone to do some quicky contract work.
All the equipment will be accessible through the Internet.
-Bill
13 matches
Mail list logo
