Re: [c-nsp] SRB4 (was RE: SRC2?)

hi, i'm running SRB4 on WS-SUP720-3BXL & WS-F6700-DFC3CXL linecards. i was running SRB2, hit some BUGs and had to option: 1. upgrade to SRB4 2. downgrade to SRA7 (change DFC3CXL linecards) i went for option 1. and everything is working fine now except my logs are full of these lines: Aug 29 09

Re: [c-nsp] multicast NOT in HW on 7600

hi Phil, because R2 is not part of the NEW TOPOLOGY, R1 and R2 are not PIM neighbors anymore. [...] R1#sh run | inc ^ip (pim|multi) ip multicast-routing ip multicast-routing vrf XXX ip pim ssm range multicast-mdt R1#sh run int Vlan10 interface Vlan10 description XXX mtu 9216 ip address XXX

[c-nsp] multicast NOT in HW on 7600

hi i have a multicast problem in the following topology; TOPOLOGY: Msource -> R1(SVI 10) ---trunk--- (SVI 10) R2 ---routed--- R3 ..Rn ... Receiver - R1(7613), R2(7609), R(7613) / IOS SRA3 / WS-SUP720-3BXL - 10G link between them in WS-X6704-10GE linecards with DFC - trunk between R1 and R2,

Re: [c-nsp] eompls with different vlans at the ends

hello, i wanted a confirmation that "bpdu filter" and "disabling STP" are the only choices for this setup. thanks, liviu. On Wednesday 16 May 2007 14:52, Oliver Boehmer (oboehmer) wrote: > 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

Re: [c-nsp] eompls with different vlans at the ends

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

[c-nsp] eompls with different vlans at the ends

hello, topology: Host1 --> switches -->PE --eompls--PE <-- switches <- Host2 config PE (7604 sup 720 / IOS SRA3): subinterface + encapulation dot1q vlan X + xconnect (MUX-UNI) problem: if vlan X for Host1 is different then vlan X for Host 2, on the first switch connected directly to PE we will

Re: [c-nsp] BGP and full traffic overload

hello, what type of L3 switches / routers do you use (paste here IOS too) ? what are the intervals that the BGP session goes up and down ? are you 100% sure the problem is generated because of the overloaded link ? paste here please the output of the command: "sh ip bgp nei " for both neighbors.

Re: [c-nsp] Cisco 2960 QOS issue

hello dimuthu, assure that "QoS ip packet dscp rewrite is enabled" (global config) and you'll see that your policy-map is marking your ftp traffic; you can see that with a port monitor configured with source uplink port (Gi0/24) TX or "sh mls qos interface Gi0/24 statistics" at "dscp: outgoing" f

Re: [c-nsp] multicast filter / one way - solved

hello, i've changed R2 from 3550 to 3560 and that solved the problem. R2 - 3560 - c3560-advipservicesk9-mz.122-25.SEE3.bin i'm pretty sure this is a bug. -- liviu. On Saturday 28 April 2007 22:44, Liviu Pislaru wrote: > hello, > > i have the topology: > R1 (SVI 460) --

[c-nsp] multicast filter / one way

hello, i have the topology: R1 (SVI 460) PE (SVI460/xconnect) EoMPLSPE (SVI460/xconnect) R2 (SVI 460) R1 - 7613 - s72033-advipservicesk9_wan-mz.122-33.SRA3.bin R2 - 3550 - c3550-ipservicesk9-mz.122-25.SEE.bin PE - 3750-ME (both) - c3750me-i5k91-mz.122-25.SEG1.bin i can't estab

Re: [c-nsp] BGP received-routes

hello, it seems like you are talking about eBGP; one possible scenario for your case is that you don't have an entry in RIB for next-hop AA.AA.AA.16 (for example because on neighbor router AA.AA.AA.1 the subnet used for your BGP connection is secondary on a SVI interface) and also have configure

Re: [c-nsp] Catalyst 6500 switchport input drops

hello, this document might help you: http://www.cisco.com/warp/public/63/queue_drops.html#topic2 -- liviu. - Original Message - From: "Matt Ryan" <[EMAIL PROTECTED]> To: Sent: Monday, April 23, 2007 8:21 PM Subject: [c-nsp] Catalyst 6500 switchport input drops > Seeing a large number

Re: [c-nsp] Traffic generator

hello, pktgen module included in the Linux kernel. ... Network Testing ---> Packet Generator -- liviu. - Original Message - From: <[EMAIL PROTECTED]> To: Sent: Friday, April 20, 2007 11:31 PM Subject: [c-nsp] Traffic generator Hi, I´d like to stress some our links. Does anyone know a

Re: [c-nsp] 6500: another eompls problem

hello, first of all, i think the error "INTERFACE_API-4-TBLERROR" doesn't have anything in common with "SPANTREE-2-RECV_PVID_ERR"; because you use different VLANs at the ends of the EoMPLS tunnel and the BPDUs with vlan id 812 are encapsulated through the EoMPLS tunnel and decapsulated in vlan 40

Re: [c-nsp] 6500: another eompls problem

hello, first of all, i think the error "INTERFACE_API-4-TBLERROR" doesn't have anything in common with "SPANTREE-2-RECV_PVID_ERR"; because you use different VLANs at the ends of the EoMPLS tunnel and the BPDUs with vlan id 812 are encapsulated through the EoMPLS tunnel and decapsulated in vlan 40

Re: [c-nsp] How to monitor BGP sessions

hello robert, you can try to obtain automatically (with the same monitoring script) neighbors ip adresses (ipv4 or ipv6); EXAMPLE (perl): - you have router X with the ip adress $iprouter: $comm=""; # put here your own password $oid="1.3.6.1.2.1.15.3.1.7"; ($session,$error) = Net::SNMP

Re: [c-nsp] access lists on vlan interfaces

hello, VACL are a little bit different. Standard and extended IOS ACLs are configured on the INPUT and OUTPUT of router interfaces and, as such, are applied to routed packets. The use of IOS ACLs requires both a PFCx and a MSFCx on the Catalyst 6500 Series for example. VLAN ACLs (VACLs) prov

Re: [c-nsp] access lists on vlan interfaces

hi, think of a router as a circle with you inside (center of that circle) :). inbound traffic is the traffic that come towards YOU through interface/SVI you want to configure ACL (SVI 100) an leaves the router through another interface. outbound traffic is the destined traffic for vlan 100 that

Re: [c-nsp] OSPF interoperability with ME6524 and RS15800

hello, OSPF must send acknowledgment of each newly received link-state advertisement (LSA). It does this by sending LSA packets. LSAs are retransmitted until they are acknowledged. The link-state retransmit interval defines the time between retransmissions. The default interval in 5 seconds.

Re: [c-nsp] Layer 3 Core

hello, if you already have all links routed beetwen core routers i think the best solution for L2 transport beetwen your servers would be EoMPLS (or VPLS). in my opinion that config represents best practice for an ISP with MPLS core network. -- liviu. - Original Message - From: "Stephen

Re: [c-nsp] 2960 for video & qos

---- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] On Behalf Of Liviu Pislaru > > Sent: Tuesday, April 03, 2007 12:23 AM > > To: cisco-nsp@puck.nether.net > > Subject: Re: [c-nsp] 2960 for video & qos > > > > hello, > > > > 2960 w

Re: [c-nsp] 2960 for video & qos

hello, 2960 works just fine for LAN QoS. you can mark, classifiy and police, you can adjust maping, buffers and output queues (1p3q3t). if you have voip on your network you can also use "auto-qos"; use 3560 only if you need la L3 device. -- liviu. - Original Message - From: "Dan" <[EMA