Re: [c-nsp] Anybody here is running IPv6
You also might try out Hurricane's free IPv6 certification/training service at http://ipv6.he.net/certification Mike. Renelson Panosky wrote: Thank you all for the responses on IPv6 i've learned a lot from you guys and i feel a lot more comfortable Renelson On Wed, Apr 29, 2009 at 11:03 AM, Renelson Panosky panocisc...@gmail.comwrote: Hello fellow Engineers We are getting ready to start testing IPv6 at my job, if you are running IPv6 right now please let me how is it working fo you? I would like to know the good, the bad and the ugly Renelson ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ -- + H U R R I C A N E - E L E C T R I C + | Mike LeberWholesale IPv4 and IPv6 Transit 510 580 4100 | | Hurricane Electric AS6939 | | mle...@he.net Internet Backbone Colocation http://he.net | +-+ ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] QoS Strategy for Cisco 877
Hi Gary, Configuring QoS on Cisco 877 routers is actually at the heart of one of our products. Can I ask what queuing method you are using, are you using CBWFQ or Priority queuing? Steven Steven McCrory Senior Network Engineer Netservices PLC Waters Edge Business Park Modwen Road Manchester, M5 3EZ www.netservicesplc.com -Original Message- From: cisco-nsp-boun...@puck.nether.net [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Gary T. Giesen Sent: 30 April 2009 21:17 To: cisco-nsp@puck.nether.net Subject: [c-nsp] QoS Strategy for Cisco 877 Guys, I've been trying a bunch of different methods, but nothing seems to achieve what I want. Ideally I'd like to use Priority Queueing (or something that operates the same) on the ATM0 interface of a Cisco 877. I have 3 classes of traffic: Telnet/SSH/ICMP/Management - High Priority General Data - Default Priority IP Video Camers - Low Priority Normally I would just use a priority-list/priority-group, but I can't seem to apply it to either the ATM0 interface or the ATM0.33 interface (and I have also tried applying it on the PVC under the subinterface). I would like all packets in the high priority queue to be serviced first, then all packets in the default priority, and if there's any bandwidth leftover, service the low priority queue. I would prefer not to have to define minimum and maximum bandwidth for each queue (I don't want any hard queues/bandwidth limits, I would like all available bandwidth to be used by any particular queue as long as the queues above it are serviced). Can anyone recommend a QoS strategy/configuration for this that will work on the ATM0/DSL interface (no PPPoE) on a Cisco 877? Thanks, GG ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ NetServices plc, Company No. 4178393, Registered Office: NetServices House, 31 Modwen Road, Waters Edge Business Park, SALFORD, M5 3EZ ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] Cisco MPLS interoperability with Mikrotik (or Linux) MPLS
On Thu, Apr 30, 2009 at 5:35 AM, Rubens Kuhl rube...@gmail.com wrote: Have anynone done any testing interoperating Cisco MPLS (Cat 6k or 7600 families) with Mikrotik (which is just packaging of MPLS Linux) ? I'm specially curious about EoMPLS and H-VPLS interoperating, but basic LDP/RSVP/MPLS-TE/MPLS-FRR also needs to be addressed, of course. I can't comment to the Mikrotik aspect but I've played around with MPLS linux (mpls-linux.sourceforge.net/) a bit recently. The kernel label forwarding aspect (including EoMPLS) seems well maintained and I've managed to get a Linux instance participating with off the shelf routers in MPLS forwarding. Label distribution protocols don't seem to be as well maintained, LDP being the most mature although you'll need to compile from the latest sources downloaded from the projects' Subversion server. There are code trees for Quagga for MP-BGP support although I would consider this alpha at best. afaik there is no RSVP or VPLS support yet. Rubens ___ cisco-nsp mailing list cisco-...@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] Optical module transmit power
Michael -- Michael Robson | Tel: +44 (0) 161 275 6113 Senior Network Engineer | Fax: +44 (0) 161 275 6120 Net North West | Email: michael.rob...@manchester.ac.uk On 30 Apr 2009, at 16:08, Dale W. Carder wrote: On Apr 30, 2009, at 9:37 AM, Michael Robson wrote: We have a selection of ZR modules (XENPAK-10GB-ZR) For these modules, none of them are transmitting at anything like their maximum of +4.0dBm (Cisco's figures for the maximum transmit power), they are in fact transmitting between +1.9dBm and +2.3dBm. This is to be expected. Vendors just publish a tolerable range somewhere in which the optics will operate. What determines what they will transmit at i.e. is it simply that better manufactured ones achieve a transmit value closer to the +4.0dBm power level Maybe it's luck. As I suspected, ah well. Anyway, how long are your fiber spans? If they are really long, and you're living on the edge now, you may end up in a sticky situation as these optics degrade over time. They are very long distances; however these links are just stop gaps until we procure our DWDM equipment. If they are not extremely long, you may have some horrible jumpers or splices that are eating some dB. Do you have an OTDR? Dale The circuit supplier quoted dB values for the links on handover which should have meant that most of the links would have been within acceptable values: perhaps the 6500-quoted values aren't very accurate? p.s. My fiance did her postgraduate work at Manchester. Quite a nice place! Manchester is a great place! Thanks, Michael. ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
[c-nsp] VSS1440 to ASR1002 - MEC issues
Hello, I'm currently deploying two Cisco 6509-E chassis with VS-Sup720-10GE (in a VSS 1440 cluster/configuration) with dual ASR 1002 routers to provide aggregation of multiple upstream links (running multiple BGP and EIGRP sessions). I wanted to utilize MEC between each ASR and each 6509 chassis to build in as much resilience as possible. However this configuration seems to be playing up and so I thought I'd ask the experts! Physical Topology: ASR Gi0/0/0 into 6509 Chassis 1 Module 1 Port 1 ASR Gi0/1/0 into 6509 Chassis 2 Module 1 Port 1 The ASR is running IOS-XE 2.3.0 (IOS 12.2(33)XNC) AISK9 with dual IOS processes. The VSS chassis are running IOS 12.2(33)SXI1 ISK9 with a 4x 10GE VSL (2 supervisor 10GE interfaces, 2 10GE interfaces on a 6708-10GE line card). I'm just using CAT6 between the ASR and the 6748-GE-TX line cards in the VSS boxes. ASR configuration: interface Port-Channel1 ip address x.x.x.5 255.255.255.252 ip hello-interval eigrp 100 2 ip hold-time eigrp 100 6 ip authentication mode eigrp 100 md5 ip authentication key-chian eigrp 100 vcoresw1-chain ip summary-address eigrp 100 0.0.0.0 0.0.0.0 255 no ip redirects no ip unreachables no ip proxy-arp no shut ! interface Gi0/0/0 channel-group 1 no shut interface Gi0/1/0 channel-group 1 no shut Cisco VSS configuration: int Gi1/1/1 no switchport channel-group 3 mode on int Gi2/1/1 no switchport channel-group 3 mode on int Po3 desc *** MEC to br1-po1 *** no ip redirects no ip unreachables no ip proxy-arp ip vrf forwarding edge-vrf ip address x.x.x.6 255.255.255.252 ip hello-interval eigrp 100 2 ip hold-time eigrp 100 6 ip authentication mode eigrp 100 md5 ip authentication key-chain eigrp 100 br1-chain no shut ! The problem I am experiencing seems to be one way traffic between the VSS cluster and the Border Router. Pinging across this /30 subnet does not work in either direction. EIGRP relationships build when the Po interfaces first come online and then immediately time out moments later. The VSS cluster then does not see any further EIGRP traffic from the ASR. However the ASR seems to think it's successfully building an adjacency to the VSS. However this times out due to 'retry limit exceeded' every minute or so, but seems to think it re- establishes again. This problem persists if we drop the PortChannel to just one Gigabit Ethernet interface. The second interface can be shut down or actually removed from the Po config (eg. no channel-group 1). The really interesting thing is, with one link, if we remove the channel-group comand from the one remaining ASR interface, all of a sudden the link springs to life. Pings between the ASR Gi0/0/0 interface and the Po3 VSS interface are successful. EIGRP relationship comes up immediately and is stable, and routes are exchanged as you'd expect. How does this work? With the ASR thinking it's a non-etherchannel interface, but the VSS thinking it IS an EtherChannel (with 1 member), surely it should just fail? Am I doing something wrong or could this be a bug in either VSS or the ASR? It's not earth shattering, we could just configure 2 EIGRP sessions between the VSS and the ASR (4 in total with 2 ASRs) but don't think this is as clean an implementation as MEC across fully redundant chassis and line cards (one of the big selling points of the VSS !!) Any help would be much appreciated! Thanks Alasdair ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] Optical module transmit power
On Fri, 1 May 2009 15:05:35 +0100, Michael Robson wrote The circuit supplier quoted dB values for the links on handover which should have meant that most of the links would have been within acceptable values: perhaps the 6500-quoted values aren't very accurate? Values reported by ZR XENPAKs are quite precise, so if they report RX level which is much worse than expected, you have to look for dirty connectors, faulty patchcord or the like problems. Our installation team tried to blame XENPAKs for inacurrate measurements several times, but after closer investigation it always turned out that the fault was somewhere else. It's nothing uncommon to see 3 dB extra loss on just one dirty connector. M. ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] QoS Strategy for Cisco 877
Hi Gary, I've read through your email again and answered my own question. My next question would be, have you given thought to the upstream sync-speed? Our testing highlighted that when QoS was applied to the pvc, it didn't seem to function properly unless we applied a vbr-nrt bitrate configuration which matched the upstream sync-speed e.g. interface ATM0 pvc 0/38 vbr-nrt 832 832 tx-ring-limit 3 encapsulation aal5mux ppp dialer dialer pool-member 2 service-policy output dsl-out max-reserved-bandwidth 100 Steven Steven McCrory Senior Network Engineer Netservices PLC Waters Edge Business Park Modwen Road Manchester, M5 3EZ www.netservicesplc.com -Original Message- From: cisco-nsp-boun...@puck.nether.net [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Steve McCrory Sent: 01 May 2009 12:21 To: gie...@snickers.org; cisco-nsp@puck.nether.net Subject: Re: [c-nsp] QoS Strategy for Cisco 877 Hi Gary, Configuring QoS on Cisco 877 routers is actually at the heart of one of our products. Can I ask what queuing method you are using, are you using CBWFQ or Priority queuing? Steven Steven McCrory Senior Network Engineer Netservices PLC Waters Edge Business Park Modwen Road Manchester, M5 3EZ www.netservicesplc.com -Original Message- From: cisco-nsp-boun...@puck.nether.net [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Gary T. Giesen Sent: 30 April 2009 21:17 To: cisco-nsp@puck.nether.net Subject: [c-nsp] QoS Strategy for Cisco 877 Guys, I've been trying a bunch of different methods, but nothing seems to achieve what I want. Ideally I'd like to use Priority Queueing (or something that operates the same) on the ATM0 interface of a Cisco 877. I have 3 classes of traffic: Telnet/SSH/ICMP/Management - High Priority General Data - Default Priority IP Video Camers - Low Priority Normally I would just use a priority-list/priority-group, but I can't seem to apply it to either the ATM0 interface or the ATM0.33 interface (and I have also tried applying it on the PVC under the subinterface). I would like all packets in the high priority queue to be serviced first, then all packets in the default priority, and if there's any bandwidth leftover, service the low priority queue. I would prefer not to have to define minimum and maximum bandwidth for each queue (I don't want any hard queues/bandwidth limits, I would like all available bandwidth to be used by any particular queue as long as the queues above it are serviced). Can anyone recommend a QoS strategy/configuration for this that will work on the ATM0/DSL interface (no PPPoE) on a Cisco 877? Thanks, GG ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ NetServices plc, Company No. 4178393, Registered Office: NetServices House, 31 Modwen Road, Waters Edge Business Park, SALFORD, M5 3EZ ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ NetServices plc, Company No. 4178393, Registered Office: NetServices House, 31 Modwen Road, Waters Edge Business Park, SALFORD, M5 3EZ ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] VSS1440 to ASR1002 - MEC issues
ASR1000 doesn't -yet- support the well-known EtherChannel/LACP. If i remember right, RLS5 will have it. There is a feature called VLAN Mapping to Gigabit EtherChannel (GEC) Member Links, but i don't think it would help you much, since you have L3 portchannels on both sides. http://www.cisco.com/en/US/docs/ios/lanswitch/configuration/guide/lsw_cfg_gecvlan.html -- Tassos Alasdair McWilliam wrote on 01/05/2009 18:29: Hello, I'm currently deploying two Cisco 6509-E chassis with VS-Sup720-10GE (in a VSS 1440 cluster/configuration) with dual ASR 1002 routers to provide aggregation of multiple upstream links (running multiple BGP and EIGRP sessions). I wanted to utilize MEC between each ASR and each 6509 chassis to build in as much resilience as possible. However this configuration seems to be playing up and so I thought I'd ask the experts! Physical Topology: ASR Gi0/0/0 into 6509 Chassis 1 Module 1 Port 1 ASR Gi0/1/0 into 6509 Chassis 2 Module 1 Port 1 The ASR is running IOS-XE 2.3.0 (IOS 12.2(33)XNC) AISK9 with dual IOS processes. The VSS chassis are running IOS 12.2(33)SXI1 ISK9 with a 4x 10GE VSL (2 supervisor 10GE interfaces, 2 10GE interfaces on a 6708-10GE line card). I'm just using CAT6 between the ASR and the 6748-GE-TX line cards in the VSS boxes. ASR configuration: interface Port-Channel1 ip address x.x.x.5 255.255.255.252 ip hello-interval eigrp 100 2 ip hold-time eigrp 100 6 ip authentication mode eigrp 100 md5 ip authentication key-chian eigrp 100 vcoresw1-chain ip summary-address eigrp 100 0.0.0.0 0.0.0.0 255 no ip redirects no ip unreachables no ip proxy-arp no shut ! interface Gi0/0/0 channel-group 1 no shut interface Gi0/1/0 channel-group 1 no shut Cisco VSS configuration: int Gi1/1/1 no switchport channel-group 3 mode on int Gi2/1/1 no switchport channel-group 3 mode on int Po3 desc *** MEC to br1-po1 *** no ip redirects no ip unreachables no ip proxy-arp ip vrf forwarding edge-vrf ip address x.x.x.6 255.255.255.252 ip hello-interval eigrp 100 2 ip hold-time eigrp 100 6 ip authentication mode eigrp 100 md5 ip authentication key-chain eigrp 100 br1-chain no shut ! The problem I am experiencing seems to be one way traffic between the VSS cluster and the Border Router. Pinging across this /30 subnet does not work in either direction. EIGRP relationships build when the Po interfaces first come online and then immediately time out moments later. The VSS cluster then does not see any further EIGRP traffic from the ASR. However the ASR seems to think it's successfully building an adjacency to the VSS. However this times out due to 'retry limit exceeded' every minute or so, but seems to think it re-establishes again. This problem persists if we drop the PortChannel to just one Gigabit Ethernet interface. The second interface can be shut down or actually removed from the Po config (eg. no channel-group 1). The really interesting thing is, with one link, if we remove the channel-group comand from the one remaining ASR interface, all of a sudden the link springs to life. Pings between the ASR Gi0/0/0 interface and the Po3 VSS interface are successful. EIGRP relationship comes up immediately and is stable, and routes are exchanged as you'd expect. How does this work? With the ASR thinking it's a non-etherchannel interface, but the VSS thinking it IS an EtherChannel (with 1 member), surely it should just fail? Am I doing something wrong or could this be a bug in either VSS or the ASR? It's not earth shattering, we could just configure 2 EIGRP sessions between the VSS and the ASR (4 in total with 2 ASRs) but don't think this is as clean an implementation as MEC across fully redundant chassis and line cards (one of the big selling points of the VSS !!) Any help would be much appreciated! Thanks Alasdair ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] QoS Strategy for Cisco 877
I was hoping to use priority queueing, since it does exactly what I want (service all packets in highest queue, then default queue, then low queue) but it doesn't seem to work with a DSL/ATM interface... GG On Fri, May 1, 2009 at 7:20 AM, Steve McCrory stev...@netservicesplc.com wrote: Hi Gary, Configuring QoS on Cisco 877 routers is actually at the heart of one of our products. Can I ask what queuing method you are using, are you using CBWFQ or Priority queuing? Steven Steven McCrory Senior Network Engineer Netservices PLC Waters Edge Business Park Modwen Road Manchester, M5 3EZ www.netservicesplc.com -Original Message- From: cisco-nsp-boun...@puck.nether.net [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Gary T. Giesen Sent: 30 April 2009 21:17 To: cisco-nsp@puck.nether.net Subject: [c-nsp] QoS Strategy for Cisco 877 Guys, I've been trying a bunch of different methods, but nothing seems to achieve what I want. Ideally I'd like to use Priority Queueing (or something that operates the same) on the ATM0 interface of a Cisco 877. I have 3 classes of traffic: Telnet/SSH/ICMP/Management - High Priority General Data - Default Priority IP Video Camers - Low Priority Normally I would just use a priority-list/priority-group, but I can't seem to apply it to either the ATM0 interface or the ATM0.33 interface (and I have also tried applying it on the PVC under the subinterface). I would like all packets in the high priority queue to be serviced first, then all packets in the default priority, and if there's any bandwidth leftover, service the low priority queue. I would prefer not to have to define minimum and maximum bandwidth for each queue (I don't want any hard queues/bandwidth limits, I would like all available bandwidth to be used by any particular queue as long as the queues above it are serviced). Can anyone recommend a QoS strategy/configuration for this that will work on the ATM0/DSL interface (no PPPoE) on a Cisco 877? Thanks, GG ___ cisco-nsp mailing list cisco-...@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ NetServices plc, Company No. 4178393, Registered Office: NetServices House, 31 Modwen Road, Waters Edge Business Park, SALFORD, M5 3EZ ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
[c-nsp] IPv6 ND over PPP
Hi - 1) does anyone know if Cisco (IOS) is using IPv6CP for neighbor discovery on a PPP link or they run neighbor discovery on top of PPP link? 2) same question for HDLC over PPP - how do they do neighbor discovery there - ND, or statically provisioned neighbors or Inverse ND? Thanks, Marlon ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
[c-nsp] Channelized DS3 over SM fiber handoff
Hello, We will need to terminate channelized DS3 circuit in 7200VXR router. The problem is that DS3 is given to us by telco (Verizon) as a single-mode fiber. I have no experience with this kind of setup and actually limited experience with DS3 circuits. Has anybody done this before? How it's usually done? Is there a DS3 PA with fiber interface for 7200 routers (I don't see any) or I should use a media converter with PA-MC-T3? If so, can you recommend one? It seems that many media converters use proprietary DS3 encoding scheme and must be used in pairs (or at least I've been told so), but telco is unable to give us any recommendation on how we should terminate it on our end. If anyone could share the experience on terminating DS3 over fiber handoff from Verizon, East Coast, I'd greatly appreciate it. Any pointers to appropriate documentation/tutorials/howtos/etc are also very welcome. Thanks a lot, Michael ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] Channelized DS3 over SM fiber handoff
Michael Ulitskiy wrote: Hello, We will need to terminate channelized DS3 circuit in 7200VXR router. The problem is that DS3 is given to us by telco (Verizon) as a single-mode fiber. I have no experience with this kind of setup and actually limited experience with DS3 circuits. Has anybody done this before? How it's usually done? Is there a DS3 PA with fiber interface for 7200 routers (I don't see any) or I should use a media converter with PA-MC-T3? If so, can you recommend one? It seems that many media converters use proprietary DS3 encoding scheme and must be used in pairs (or at least I've been told so), but telco is unable to give us any recommendation on how we should terminate it on our end. If anyone could share the experience on terminating DS3 over fiber handoff from Verizon, East Coast, I'd greatly appreciate it. Any pointers to appropriate documentation/tutorials/howtos/etc are also very welcome. Thanks a lot, I've never seen a telco hand off a DS-3 as fiber. Always a pair of 75-ohm coaxial cables on BNC connectors. Typically it comes in to the customer premise as a SONET fiber connection and a carrier-owned MUX and NID is installed with the customer handoff as co-ax. You would need to know the exact make and model of the hardware at the other end of the link to procure a compatible media converter if they are really terminating a DS-3 this way. And good luck when you have a case of trouble, the blame game on this one will not be fun. Are you sure they're finished with the provisioning and that there isn't another group scheduled to install equipment? -- Jay Hennigan - CCIE #7880 - Network Engineering - j...@impulse.net Impulse Internet Service - http://www.impulse.net/ Your local telephone and internet company - 805 884-6323 - WB6RDV ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] VSS1440 to ASR1002 - MEC issues
That's correct, ASR1000 GEC only support static VLAN LB at the moment and not LACP. So this can only work if you are ok on just using GEC with VLANs on both sides as Tassos mentioned. Since you are deploying GEC for redundancy, this VLAN static LB should be able to give you what you need. Also you need to have the VSS on GEC mode on. HTH - Daniel de la Rosa CCIE # 4622 Technical Marketing Engineer ERBU, Cisco Systems ASR1000 doesn't -yet- support the well-known EtherChannel/LACP. If i remember right, RLS5 will have it. There is a feature called VLAN Mapping to Gigabit EtherChannel (GEC) Member Links, but i don't think it would help you much, since you have L3 portchannels on both sides. http://www.cisco.com/en/US/docs/ios/lanswitch/configuration/guide/lsw_c fg_gecvlan.html -- Tassos Alasdair McWilliam wrote on 01/05/2009 18:29: Hello, I'm currently deploying two Cisco 6509-E chassis with VS-Sup720-10GE (in a VSS 1440 cluster/configuration) with dual ASR 1002 routers to provide aggregation of multiple upstream links (running multiple BGP and EIGRP sessions). I wanted to utilize MEC between each ASR and each 6509 chassis to build in as much resilience as possible. However this configuration seems to be playing up and so I thought I'd ask the experts! Physical Topology: ASR Gi0/0/0 into 6509 Chassis 1 Module 1 Port 1 ASR Gi0/1/0 into 6509 Chassis 2 Module 1 Port 1 The ASR is running IOS-XE 2.3.0 (IOS 12.2(33)XNC) AISK9 with dual IOS processes. The VSS chassis are running IOS 12.2(33)SXI1 ISK9 with a 4x 10GE VSL (2 supervisor 10GE interfaces, 2 10GE interfaces on a 6708-10GE line card). I'm just using CAT6 between the ASR and the 6748-GE-TX line cards in the VSS boxes. ASR configuration: interface Port-Channel1 ip address x.x.x.5 255.255.255.252 ip hello-interval eigrp 100 2 ip hold-time eigrp 100 6 ip authentication mode eigrp 100 md5 ip authentication key-chian eigrp 100 vcoresw1-chain ip summary-address eigrp 100 0.0.0.0 0.0.0.0 255 no ip redirects no ip unreachables no ip proxy-arp no shut ! interface Gi0/0/0 channel-group 1 no shut interface Gi0/1/0 channel-group 1 no shut Cisco VSS configuration: int Gi1/1/1 no switchport channel-group 3 mode on int Gi2/1/1 no switchport channel-group 3 mode on int Po3 desc *** MEC to br1-po1 *** no ip redirects no ip unreachables no ip proxy-arp ip vrf forwarding edge-vrf ip address x.x.x.6 255.255.255.252 ip hello-interval eigrp 100 2 ip hold-time eigrp 100 6 ip authentication mode eigrp 100 md5 ip authentication key-chain eigrp 100 br1-chain no shut ! The problem I am experiencing seems to be one way traffic between the VSS cluster and the Border Router. Pinging across this /30 subnet does not work in either direction. EIGRP relationships build when the Po interfaces first come online and then immediately time out moments later. The VSS cluster then does not see any further EIGRP traffic from the ASR. However the ASR seems to think it's successfully building an adjacency to the VSS. However this times out due to 'retry limit exceeded' every minute or so, but seems to think it re-establishes again. This problem persists if we drop the PortChannel to just one Gigabit Ethernet interface. The second interface can be shut down or actually removed from the Po config (eg. no channel-group 1). The really interesting thing is, with one link, if we remove the channel-group comand from the one remaining ASR interface, all of a sudden the link springs to life. Pings between the ASR Gi0/0/0 interface and the Po3 VSS interface are successful. EIGRP relationship comes up immediately and is stable, and routes are exchanged as you'd expect. How does this work? With the ASR thinking it's a non-etherchannel interface, but the VSS thinking it IS an EtherChannel (with 1 member), surely it should just fail? Am I doing something wrong or could this be a bug in either VSS or the ASR? It's not earth shattering, we could just configure 2 EIGRP sessions between the VSS and the ASR (4 in total with 2 ASRs) but don't think this is as clean an implementation as MEC across fully redundant chassis and line cards (one of the big selling points of the VSS !!) Any help would be much appreciated! Thanks Alasdair ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ ___ cisco-nsp mailing list cisco-nsp@puck.nether.net
Re: [c-nsp] Channelized DS3 over SM fiber handoff
Michael Ulitskiy wrote: Hello, We will need to terminate channelized DS3 circuit in 7200VXR router. The problem is that DS3 is given to us by telco (Verizon) as a single-mode fiber. I have no experience with this kind of setup and actually limited experience with DS3 circuits. Has anybody done this before? How it's usually done? Is there a DS3 PA with fiber interface for 7200 routers (I don't see any) or I should use a media converter with PA-MC-T3? If so, can you recommend one? It seems that many media converters use proprietary DS3 encoding scheme and must be used in pairs (or at least I've been told so), but telco is unable to give us any recommendation on how we should terminate it on our end. If anyone could share the experience on terminating DS3 over fiber handoff from Verizon, East Coast, I'd greatly appreciate it. Any pointers to appropriate documentation/tutorials/howtos/etc are also very welcome. Thanks a lot, I've never seen anyone do that before with a DS3. Maybe they gave you Ethernet? ~Seth ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] Channelized DS3 over SM fiber handoff
Maybe they delivered a channelized OC3? I know that is an actual product, but have never seen a DS3 as fiber handoff. Troy Beisigl Sent from my iPhone On May 1, 2009, at 6:05 PM, Seth Mattinen se...@rollernet.us wrote: Michael Ulitskiy wrote: Hello, We will need to terminate channelized DS3 circuit in 7200VXR router. The problem is that DS3 is given to us by telco (Verizon) as a single-mode fiber. I have no experience with this kind of setup and actually limited experience with DS3 circuits. Has anybody done this before? How it's usually done? Is there a DS3 PA with fiber interface for 7200 routers (I don't see any) or I should use a media converter with PA-MC-T3? If so, can you recommend one? It seems that many media converters use proprietary DS3 encoding scheme and must be used in pairs (or at least I've been told so), but telco is unable to give us any recommendation on how we should terminate it on our end. If anyone could share the experience on terminating DS3 over fiber handoff from Verizon, East Coast, I'd greatly appreciate it. Any pointers to appropriate documentation/tutorials/howtos/etc are also very welcome. Thanks a lot, I've never seen anyone do that before with a DS3. Maybe they gave you Ethernet? ~Seth ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] Channelized DS3 over SM fiber handoff
Troy Beisigl wrote: Maybe they delivered a channelized OC3? I know that is an actual product, but have never seen a DS3 as fiber handoff. Maybe; odd though if one asked for a DS3. If that's the case you can just get an OC3 port adapter. ~Seth ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] BGP Med and outbound metric
Hi,
2009/5/1 Matthew Huff mh...@ox.com:
Since we use BGP as peering to our ISPs, and don't use BGP internally in our
core, I haven't used MED or local_pref much. However, we have two routers
connected to another ASN (not via the internet) and I'm trying to influence
their return path since we are getting asynchronous routing. I'm trying to
use MED to advertise a lower preference out our second router but it doesn't
seem to be working. Any suggestions?
{cut}
Another option that you can try is as-prepending - instead of setting
higher metric.
Try this:
route-map setMED-LOW permit 10
match ip address routemap_ecn
set metric 200
set as-path prepend 14607
Even if they reset the metric this should work (unless they influence
the decision with weight or local_pref).
kind regards
Pshem
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] Channelized DS3 over SM fiber handoff
Allstream at 151 front street in Toronto does this. They run a single strand SMF and they terminate it into a form of a media converter, which passes off 2x BNC as expected for a DS3. They do this for both clear channel and channelized DS3. Interestingly enough, our channelized OC12s come in on a pair of SMF from them. I would imagine you would need a similar media converter - I'm sorry I don't have the model number of the equipment Allstream uses. All I know it is some sort of WDM equipment (obviously) on the fiber side. Ryan Werber Sr. Network Engineer Epik Networks AS21513 -Original Message- From: cisco-nsp-boun...@puck.nether.net [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Seth Mattinen Sent: Friday, May 01, 2009 6:42 PM To: cisco-nsp@puck.nether.net Subject: Re: [c-nsp] Channelized DS3 over SM fiber handoff Troy Beisigl wrote: Maybe they delivered a channelized OC3? I know that is an actual product, but have never seen a DS3 as fiber handoff. Maybe; odd though if one asked for a DS3. If that's the case you can just get an OC3 port adapter. ~Seth ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] Channelized DS3 over SM fiber handoff
Very interesting. Here is just one of many different media converters found while doing a google search. http://www.transition.com/TransitionNetworks/Products2/Product.aspx?ID=15429CategoryName=SCSCF30xx-10x Troy Beisigl Allstream at 151 front street in Toronto does this. They run a single strand SMF and they terminate it into a form of a media converter, which passes off 2x BNC as expected for a DS3. They do this for both clear channel and channelized DS3. Interestingly enough, our channelized OC12s come in on a pair of SMF from them. I would imagine you would need a similar media converter - I'm sorry I don't have the model number of the equipment Allstream uses. All I know it is some sort of WDM equipment (obviously) on the fiber side. Ryan Werber Sr. Network Engineer Epik Networks AS21513 -Original Message- From: cisco-nsp-boun...@puck.nether.net [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Seth Mattinen Sent: Friday, May 01, 2009 6:42 PM To: cisco-nsp@puck.nether.net Subject: Re: [c-nsp] Channelized DS3 over SM fiber handoff Troy Beisigl wrote: Maybe they delivered a channelized OC3? I know that is an actual product, but have never seen a DS3 as fiber handoff. Maybe; odd though if one asked for a DS3. If that's the case you can just get an OC3 port adapter. ~Seth ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
