On May 15, 2007, at 10:00 PM, Brian McMahon wrote:
My personal theory (SWAG) is that, long ago in the Elder Days of
single-digit IOS version numbers, some clever programmer figured out
a way to save a couple of processor cycles per ACL by coding the
bitmask this way around -- an efficiency
Tony Li wrote:
On May 15, 2007, at 11:23 PM, Scott Granados wrote:
Well can't we don't care bit ourselves around to masking or something
consistent? It is confusing at times although it's interesting to
know
that's the origin.
If it were up to me (it's not ;-), the UI would be
On Sat, 12 May 2007 21:09 +0300, Tassos Chatzithomaoglou wrote:
Hi Peter,
Searching on cisco.com/go/fn for 802.1Q Tunneling returned many results.
3400,3550,3750 surely support it.
Usually 802.1Q Tunneling refers to L2 devices, while QinQ termination to
L3 ones.
I found it very strange
Selon Gert Doering [EMAIL PROTECTED]:
Hi,
On Tue, May 15, 2007 at 07:51:29PM +0200, Jerome Covini wrote:
Jared Mauch wrote:
if you have vlan1 on more than one interface (eg: gig1/1 and gig1/2)
they are actually the same vlan. This device is a switch, not an
independent router.
Hi All,
Does anyone have any experience with BFD on 12.2(33)SR?
We have troubles with BFD in a mixed 12.2(18)SXF7 and 12.2(33)SRB environment.
BFD will occasionally toggle our 10G interfaces when we do write mem or
shut/no shut, and I'd like to verify that the problem is caused by the
On Tue, May 15, 2007 7:57 pm, Gert Doering wrote:
The 8540 is more a router type device (well, routing bolted onto an
ATM switch or so) - the 6500/7600 is an ethernet switch device, with
some of the good sides of it (cheap fast can do nice tricks with
etherchannels etc.) and some of the
Hello Rubens,
We _certainly_ sure the proper vlan and ip and have been signed
both on router and the switch (disabling L2 mpls on other interface
will make IP routing back to work)
Also as i inform previously running EoMPLS and IP routing on the
different
On (2007-05-16 10:20 +0200), Geir Jensen wrote:
Does anyone have any experience with BFD on 12.2(33)SR?
We have troubles with BFD in a mixed 12.2(18)SXF7 and 12.2(33)SRB
environment.
BFD will occasionally toggle our 10G interfaces when we do write mem or
shut/no shut, and I'd like to
Hi,
On Wed, May 16, 2007 at 10:01:07AM +0100, Tim Franklin wrote:
On Tue, May 15, 2007 7:57 pm, Gert Doering wrote:
The 8540 is more a router type device (well, routing bolted onto an
ATM switch or so) - the 6500/7600 is an ethernet switch device, with
some of the good sides of it (cheap
Hi Geir,
Does anyone have any experience with BFD on 12.2(33)SR?
We have troubles with BFD in a mixed 12.2(18)SXF7 and 12.2(33)SRB
environment.
BFD will occasionally toggle our 10G interfaces when we do write
mem or shut/no shut, and I'd like to verify that the problem is
caused by the
hello,
did everybody use the same vlan id on both ends of the vlan based eompls
tunnel ? is anyone here that use different vlans, who can give me an answer
to my question ?
thanks,
liviu.
On Tuesday 15 May 2007 15:34, [EMAIL PROTECTED] wrote:
hello,
topology:
Host1 -- switches --PE
I'm not sure about the 4.0 but in the 3.3, RDBMS was the only option for
large imports (or other batch processing) apart from manually adding (or
modifying) each account one at a time. You can create the CSV file from
excel... bring everything into excel and save as csv... here's a good link
on
Thanks,
I wasn't aware of the CSCsc96524 bug..
We started out with 50ms, but we had to increase the timers to 200ms to
get rid of the flapping. But even at 200ms I see about one BFD false
negative a day.
We want to achieve SDH-like restoration times, so I would like to use
50ms*3 if it
On Wednesday 16 May 2007, [EMAIL PROTECTED] wrote:
Thanks you all folks for your detailed explanations. Now that Im hitting a
wall with the 6500/sup720 based platform, would you recommend another
platform that would allow to replicate a (bad) C8540 setup ? (i.e., allow
vlan-1 tagged L3
All:
I am thinking about using AToM to replace some older layer2 only devices that
are used to map PVCs from one circuit to another.
Circuits will be terminating on a 7200 (actually several). I would like to map
these circuits with AToM to some other 7200s. These other 7200s will be the
On Wed, May 16, 2007 at 07:18:35AM -0400, Richey wrote:
Typically, how long should it take to propagate a /24 across the net? This
isn't a new /24 from arin so it should not be filtered. It's supposedly
being announced but route-server.ip.att.net does not have the slightest clue
about this
don't think you can filter BPDUs on the PE if you're using this type of
setup (you might be able to do if you used SVI/Vlan-based eompls, i.e.
with an interface Vlan and bpdu filter/mac-acl), so you need to address
this PVID inconsistency issue on the CE, either by disabling STP for the
Vlan (as
Richey wrote:
Typically, how long should it take to propagate a /24 across the net? This
isn't a new /24 from arin so it should not be filtered. It's supposedly
being announced but route-server.ip.att.net does not have the slightest clue
about this /24 and we connect to ATT. I'm wondering
Hi,
On Wed, May 16, 2007 at 07:18:35AM -0400, Richey wrote:
Typically, how long should it take to propagate a /24 across the net? This
isn't a new /24 from arin so it should not be filtered. It's supposedly
being announced but route-server.ip.att.net does not have the slightest clue
about
I am curious if anyone is using the RSP720/SRB software in a
production network yet, or using SRB in production with a Sup720?
What issues or anomalies you have run into to date.
Thanks,
Phil
___
cisco-nsp mailing list
Hi,
We have DSL users who are migrating to a different provider and require
port 80 redirection until the migration is complete.
This subset of users are carried to several LNS's via L2TP from Telco
and as yet, are not distinguished from any other user via RADIUS
attributes etc. in our PoP.
Selon Lamar Owen [EMAIL PROTECTED]:
Just out of curiosity, why are you migrating from the 8540's in the first
place? What feature are you missing that the 12.1(26)E IOS can't do?
These C8540 are reaching EOS next year, and our hardware support contract is
ending this year.
On Wed, May 16, 2007 5:12 pm, Rick Kunkel wrote:
We've got a Sup2 with the two GigE ports and 48 port 6248 module. I've
assigned an IP address to one of the GigE ports, and plugged 3 AS5200's
into the 6248, and assigned those ports to VLAN 12.
The GigE port has (example) a 1.1.1.1 address.
Hi Rick,
I think it depends whether you want to have multiple ports in the same
subnet then you can configure a SVI (vlan interface) and assign the ports in
that vlan (12 in your case). If you wished to create routed ports then all
the AS52000 would have to be in their own subnet (2.2.2.8/30,
Dears
I have one problem with one new Ds3 link, it always shows CRC errors
and this show controller output
11017 Line Code Violations, 5613 P-bit Coding Violation
5360 C-bit Coding Violation
887 P-bit Err Secs, 0 P-bit Sev Err Secs
0 Sev Err Framing Secs, 0 Unavailable Secs
I have a 3845 running 12.4(9)T1 (advipservicesk9-mz if it matters) and
am trying to get ipv6 running on a bvi:
interface BVI2
ip address 10.250.2.254 255.255.255.0
ip access-group into-corp out
ip nat inside
ip inspect Inside in
ip virtual-reassembly
ipv6 address
I have one problem with one new Ds3 link, it always shows CRC errors
and this show controller output
How far is the router from the mux that the telco is pulling the DS3 from?
Also, have you tried changing or re-terminating the coax cables that plug
into your router?
Is this a
It happens only against the router, using Protocol Analyzers
Equipment I always shows OK.
Googling, I found a lot of forums writing about the issue and
advising to use one Cisco Ds3 Attenuator, but I can't find the Cisco
Ds3 Attenuator, so I'm thinking buy one * 75FP-XXX-2G BNC
On Wed, 16 May 2007, matthew zeier wrote:
I have a 3845 running 12.4(9)T1 (advipservicesk9-mz if it matters) and
am trying to get ipv6 running on a bvi:
I can't tell if my config's wrong or it's a bvi v6 support issue.
Anyone know?
I tried doing IPv6 on BVIs a while back and ran into the
Hi Peter,
A Loss of Signal alarm generally means physical cabling problem. Either your
2/0 port had nothing connected up when you issued the 'show controller e1'
command, or else you may be using an incorrect cable. E1 pinouts are
different from standard CAT5 cabling so be aware of that.
Good
I am looking for some input on how to determine a good time to move from
CFCs to DFCs. I am running SUP720-3BXL engines now on all of my 6509s
but only running my 6748 blades with the WS-F6700-CFC.
Is there some stats I should be looking at on the 6500 to let me know
when it would be a good idea
We're considering using ASA 5505's as a replacement for PIX 501's for customers
in our DC. I note on this page:
http://www.cisco.com/en/US/products/ps6120/products_data_sheet0900aecd802930c5.html
Rack-mountable Yes, with rack-mount kit (available in the future)
Does anyone know if this kit
show platform hardware capacity gives you some pretty good data
that may be useful in this situation. I think SXD was the first minor
rev to support it, but I could be wrong.
-C
On May 16, 2007, at 7:23 PM, Richard J. Sears wrote:
I am looking for some input on how to determine a good time
Usually, if things go well, minutes. Inside the US with
decent connectivity
you'll see changes at major routeservers very rapidly
(seconds at times).
But globally minutes, maybe 10 - 20 tops. If you're still
not announcing
make sure that you are infact announcing the route and if you
An entity claiming to be Juan C. Crespo R. ([EMAIL PROTECTED]) wrote:
: Dears
:
: I have one problem with one new Ds3 link, it always shows CRC errors
: and this show controller output
:
:11017 Line Code Violations, 5613 P-bit Coding Violation
Attenuation issues do not generally cause
At 10:07 PM 5/16/2007, Mark Rogaski wrote:
An entity claiming to be Juan C. Crespo R. ([EMAIL PROTECTED]) wrote:
: Dears
:
: I have one problem with one new Ds3 link, it always shows CRC errors
: and this show controller output
:
:11017 Line Code Violations, 5613 P-bit Coding Violation
36 matches
Mail list logo
