Re: [c-nsp] Solutions Details Requested
I'd rather suggest him to ask himself What am I trying to ask? -Original Message- From: cisco-nsp-boun...@puck.nether.net [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Nick Hilliard Sent: Monday, January 17, 2011 8:37 PM To: jack daniels Cc: cisco-nsp@puck.nether.net Subject: Re: [c-nsp] Solutions Details Requested On 17/01/2011 17:44, jack daniels wrote: Regrets for posting this querry but I'm thinking Day-in -day out to position some of Routers/Switches in Service Providers.Can you please guide me any link which talks about diffrent solutions where Routers/Switches have been Positioned in past in diffrent Service Providers. JD, I'll answer your question if you tell me how long is a piece of string, ok? Advice: sit down, get yourself a nice warm drink, then ask yourself the following question: what am I trying to achieve? Nick ___ 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/ This footnote confirms that this email message has been scanned by PineApp Mail-SeCure for the presence of malicious code, vandals computer viruses. The information contained in this e-mail message and its attachments is confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the sender, and then delete the message from your computer. Thank you! This mail was sent via Mail-SeCure System. This footnote confirms that this email message has been scanned by PineApp Mail-SeCure for the presence of malicious code, vandals computer viruses. ___ 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] 12.2.33.SRE Train and Dynamips
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Shahid Shafi wrote: Is anyone able to run 12.2.33 SRE train with Dynamips? I am trying to run it on NPE-G2 and NPE-400 with no luck. My routers keep crashing without any rhyme or reason. I also tried to decompress the image and bumped up the memory to 1 Gig but still no success. Please let me know if you are able to make it work and share your Dynamips settings. Go read this and you will understand why... http://www.dynagen.org/tutorial.htm - -- = bep -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk01ayAACgkQE1XcgMgrtyZGyACdGTNHjjUu9hEsaUTJEAvyE2IN plUAmwebZcBFT7wiS2IxABev8QpBx0Ey =ppza -END PGP SIGNATURE- ___ 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] 12.2.33.SRE Train and Dynamips
Shahid Shafi wrote: Hello, Is anyone able to run 12.2.33 SRE train with Dynamips? I am trying to run it on NPE-G2 and NPE-400 with no luck. My routers keep crashing without any rhyme or reason. I also tried to decompress the image and bumped up the memory to 1 Gig but still no success. Please let me know if you are able to make it work and share your Dynamips settings. I've just tried with 12.2(33)SRE2 on an NPE-400, it seems to work fine. Make sure that you are not trying to run a PowerPC image (c7200p) on a MIPS platform or vice-versa. BTW, 256 Mb of RAM is enough to run this image, and NPE-400 will not accept more than 512 Mb anyway. Hope this helps. thanks in advance, Shahid ___ 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] 12.2.33.SRE Train and Dynamips
I was able to start it this way: autostart=false ## # Instance 0 # ## [localhost:7200] [[7200]] image = c7200-adventerprisek9.122-33.SRE2.bin ram = 256 npe = npe-400 idlepc = 0x624fa21c mmap = false [[Router R1]] model = 7200 console = 2001 Regards, Antonio Soares, CCIE #18473 (RS/SP) amsoa...@netcabo.pt -Original Message- From: cisco-nsp-boun...@puck.nether.net [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Shahid Shafi Sent: terça-feira, 18 de Janeiro de 2011 00:47 To: Cisco certification; GroupstudyCCIE R/S; Cisco-nsp Subject: [c-nsp] 12.2.33.SRE Train and Dynamips Is anyone able to run 12.2.33 SRE train with Dynamips? I am trying to run it on NPE-G2 and NPE-400 with no luck. My routers keep crashing without any rhyme or reason. I also tried to decompress the image and bumped up the memory to 1 Gig but still no success. Please let me know if you are able to make it work and share your Dynamips settings. thanks in advance, Shahid ___ 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/
[c-nsp] SLA route tracking
Hi Team! We have following config on the 3750 switch. track 10 rtr 10 reachibility ! ip route 1.1.1.2 255.255.255.255 vlan10 1.1.1.2 track 10 ! ip sla 10 tcp-connect 1.1.1.2 3 source-ip 1.1.1.1 source-port 433 ! The main disadvantage of such config is that route removed from routing table in case of ONE TCP timeout. In this case false alarm occurs. Is it possible using 3750 platfirm remove route fo THREE CONSEQUINTIVE TCP timout? ___ 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] Upgrading VSS from Modular SXH to Monolitich SXH Monolithic SXI
This is a bit late, but check out the documentation for the FSU and eFSU procedures. I just did a VSS upgrade using the eFSU procedure and it went well. We were not using a modular IOS, but there may be a process detailed for that. - Chris On Wed, Jan 12, 2011 at 5:26 AM, David Crane david.cr...@webfusion.com wrote: Thanks Kevin, I feared that we'd hit some roadblocks with this. I think the plan is going to be to change bootvar on the devices, and just do a full outage/re-boot of both chassis, rather than look at any failover options. ___ 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/
[c-nsp] Strange T3 failure on 7206
We got an alarm that a T3 to a customer was down. PE router showed interface up, line protocol down. CE router showed down/down. Provider side goes to an Adtran Opti-mux out OC-12 to Verizon, customer end is a Verizon mux on premise. Called Vz and they claimed it was CPE, they saw idle loop towards our 7206 CE router. We shut/no-shut the interface and rebooted the 7206, no joy. I'm not familiar with the term idle loop, we were showing receive LOS and sending RAI. Customer IT guy came on site and saw CLOS on Verizon mux, alarm light on 7206. He disconnected the cable and put a coax loop towards the 7206. Interface came up-looped right away. Reconnected to Verizon mux and everything came back up nice and happy. That's what is bugging me. Circuit has been running fine for months. -- -- 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] Strange T3 failure on 7206
On 1/18/2011 09:52, Jay Hennigan wrote: We got an alarm that a T3 to a customer was down. PE router showed interface up, line protocol down. CE router showed down/down. Provider side goes to an Adtran Opti-mux out OC-12 to Verizon, customer end is a Verizon mux on premise. Called Vz and they claimed it was CPE, they saw idle loop towards our 7206 CE router. We shut/no-shut the interface and rebooted the 7206, no joy. I'm not familiar with the term idle loop, we were showing receive LOS and sending RAI. Customer IT guy came on site and saw CLOS on Verizon mux, alarm light on 7206. He disconnected the cable and put a coax loop towards the 7206. Interface came up-looped right away. Reconnected to Verizon mux and everything came back up nice and happy. That's what is bugging me. Circuit has been running fine for months. I had a T3 card get randomly confused a few months ago and wouldn't responding to commands properly. Ended up doing an OIR on it to reset it and called the whole thing weirdness happens. Mine was off a Verizon OC-12 to Adtran OPTI-6100 mux (with OC-3, DS3, and DS1 cards). ~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] SLA route tracking
On Tue, 2011-01-18 at 20:26 +0300, Sergey Voropaev wrote: We have following config on the 3750 switch. track 10 rtr 10 reachibility ! ip route 1.1.1.2 255.255.255.255 vlan10 1.1.1.2 track 10 ! ip sla 10 tcp-connect 1.1.1.2 3 source-ip 1.1.1.1 source-port 433 ! The main disadvantage of such config is that route removed from routing table in case of ONE TCP timeout. In this case false alarm occurs. Is it possible using 3750 platfirm remove route fo THREE CONSEQUINTIVE TCP timout? You could use the delay down command on the track object, like this: ip sla 10 tcp-connect 10.20.30.40 22 control disable timeout 5000 frequency 10 ! ip sla schedule 10 life forever start-time now ! track 10 ip sla 10 delay down 25 ! The SLA object probes every 10 seconds, but the track object only goes down 25 seconds later (2,5 timers SLA frequency here). So if the SLA object misses one or two probes and then regains connectivity, the track will never go down. I tried this on 12.2(55)SE IP Base; since you didn't specify your IOS version I can't say if it's supported there. This was also on a C3560G, but I can't imagine they're different in that aspect. -- Peter ___ 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] Ignore counters on 2950 switch
hi I am troubleshooting increasing ignore counts on 2950 to 2950 switch to switch interface. This counter is increasing at same rate as no-buffer under show interface. When I did show interface fast 0/2 counter errors The counter rcv-error also increasing at same rate. There are 4 2950 switches connected in ring topology and all switch to switch ports has ignore errors with no-buffer and rcv-error. 2950#sho run int f0/2 Building configuration... Current configuration : 57 bytes ! interface FastEthernet0/2 speed 100 duplex full end 2950#sho int f0/2 counters error PortAlign-ErrFCS-Err Xmit-ErrRcv-Err UnderSize Fa0/2 0 0 0 1759 0 Port Single-Col Multi-Col Late-Col Excess-Col Carri-Sen Runts Giants Fa0/2 0 0 0 0 0 0 0 2950#sho int f0/2 FastEthernet0/2 is up, line protocol is up (connected) Hardware is Fast Ethernet, address is 0009.7c58.9482 (bia 0009.7c58.9482) MTU 1500 bytes, BW 10 Kbit, DLY 100 usec, reliability 255/255, txload 1/255, rxload 1/255 Encapsulation ARPA, loopback not set Keepalive set (10 sec) Full-duplex, 100Mb/s, media type is 100BaseTX input flow-control is unsupported output flow-control is unsupported ARP type: ARPA, ARP Timeout 04:00:00 Last input 00:00:03, output 00:00:01, output hang never Last clearing of show interface counters 2d01h Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0 Queueing strategy: fifo Output queue: 0/40 (size/max) 5 minute input rate 34000 bits/sec, 4 packets/sec 5 minute output rate 39000 bits/sec, 5 packets/sec 3721996 packets input, 2706010843 bytes,* 1759 no buffer* Received 26164 broadcasts (18616 multicast) 0 runts, 0 giants, 0 throttles 0 input errors, 0 CRC, 0 frame, 0 overrun, *1759 ignored* 0 watchdog, 18616 multicast, 0 pause input 0 input packets with dribble condition detected 2977227 packets output, 1049227263 bytes, 0 underruns 0 output errors, 0 collisions, 0 interface resets 0 babbles, 0 late collision, 0 deferred 0 lost carrier, 0 no carrier, 0 PAUSE output 0 output buffer failures, 0 output buffers swapped out 2950#sho int tru PortMode Encapsulation StatusNative vlan Fa0/1 desirable802.1q trunking 1 Port Vlans allowed on trunk Fa0/1 1-4094 PortVlans allowed and active in management domain Fa0/1 1 PortVlans in spanning tree forwarding state and not pruned Fa0/1 1 From my research I have been able to find out following. Ignored:- Shows the number of received packets ignored by the interface because the interface hardware ran low on internal buffers. These buffers are different from the system buffers mentioned previously in the buffer description. Broadcast storms and bursts of noise can cause the ignored count to be increased. No buffers:- Gives the number of received packets discarded because there was no buffer space in the main system. Compare this with the ignored count. Broadcast storms on Ethernet networks are often responsible for no input buffer events. Rcv-err in show interface fast 0/1 counter error Receive error are seen on port Fa0/1.This indicates that the receive buffers are full and could lead to packet loss. This counter also increments when there is excessive traffic through the switch. All above 3 counters are increasing with exactly same rate. When I looked at the interface traffic its very low and in some kbps. There are no VLANs on any of the switch and all users connected to the switch are in same broadcast domain. Can anyone help in finding out reason for this counters and how to reduce it?? Krunal ___ 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] Bug Scrub
What's the easiest way to find all bugs related to a particular platform? It's simple enough to look through the release notes and the like for specific version of IOS, but what about bugs related to specific box? ___ 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] STP and customer ports
Is there any good reason to turn on STP on a switch port to a customer? It seems like it could cause more trouble than preventing a loop. What's your common practice? What if you hand off two connection for redundancy? I am in the middle of converting to MSTP from a network that didn't really have any STP design or goals. ___ 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] Strange T3 failure on 7206
Hi, On Tue, Jan 18, 2011 at 09:52:16AM -0800, Jay Hennigan wrote: Reconnected to Verizon mux and everything came back up nice and happy. That's what is bugging me. Circuit has been running fine for months. We've seen that on E3s and T3s as well - seems sometimes the stuff just de-syncs, and physically unplugging the cables helps getting it to re-sync. Highly annoying. (Especially if Telco techs show up, look at your cabling, and claim these cables are no good quality!, and go on to demonstrate their wisdom by unplugging/replugging the bad cable - and voila! the link is back, confirming their wisdom...) And no, I have not found a proper technical explanation yet - but it doesn't bother us very much as it happens quite infrequently, and we're using less and less E3/T3 lines. 100M Ethernet links can be had for roughly the same price, the gear is MCH cheaper, and the weird effects are gone as well... (Now, STM-1/OC-3 and up are a different thing - proper data links, proper syncing and fault monitoring, etc. - but still the gear is way expensive...) gert -- USENET is *not* the non-clickable part of WWW! //www.muc.de/~gert/ Gert Doering - Munich, Germany g...@greenie.muc.de fax: +49-89-35655025g...@net.informatik.tu-muenchen.de pgpswoDoprzRu.pgp Description: PGP signature ___ 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] Bug Scrub
Release Notes, Bug Toolkit, Account Team. On Tue, Jan 18, 2011 at 9:08 PM, Keegan Holley keegan.hol...@sungard.com wrote: What's the easiest way to find all bugs related to a particular platform? It's simple enough to look through the release notes and the like for specific version of IOS, but what about bugs related to specific box? ___ 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] STP and customer ports
Really bad idea.. if you had 2 connection through a single switch, makes sure it your switch or managed by you. Or else, use L3 solutions. Thanks, Insan - Original Message From: Jay Nakamura zeusda...@gmail.com To: cisco-nsp cisco-nsp@puck.nether.net Sent: Wed, January 19, 2011 3:07:17 AM Subject: [c-nsp] STP and customer ports Is there any good reason to turn on STP on a switch port to a customer? It seems like it could cause more trouble than preventing a loop. What's your common practice? What if you hand off two connection for redundancy? I am in the middle of converting to MSTP from a network that didn't really have any STP design or goals. ___ 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] Constant output drops on etherchannel
Cisco Catalyst 3750 QoS Configuration Examples is also a decent documentation, can be found on the following link. http://www.cisco.com/en/US/products/hw/switches/ps5023/products_tech_note09186a0080883f9e.shtml On Mon, Jan 17, 2011 at 12:27 AM, Dan Letkeman danletke...@gmail.com wrote: Nick, Thanks for the detailed explanation. The problem is I also see this on our gig switches as well. And only on ether channel's, not on a single interconnects. The traffic can be a such a minimum and I still see drops. I would like to tune the output buffers, but I'm not sure where to start. I know that I need to learn some more about qos, because we do have a voice network that is growing very fast. Do you know of some good documentation or books that I can start with? Dan. On Sun, Jan 16, 2011 at 9:14 AM, Nick Hilliard n...@foobar.org wrote: On 16/01/2011 02:30, Dan Letkeman wrote: Drops are happening even when its not under load. Has nothing to do with bandwidth. Dan, hypothetically on a 100Mb port, if you burst your output to 200 megs for 1 second, then drop to zero traffic for 4 minutes 59 seconds, you will see: - 50% packet loss on the link - a 5 minute throughput rate of 333000 bits per sec This is called a microburst. I.e. a burst of traffic which goes beyond the capacity of the link, but which is too short to be measured accurately by your 5 minute rolling average. Typically you'll see this on slower speed lan links with bursty traffic, and it's why you're seeing relatively low levels of traffic, but output drops on the interface. If you want to fix this problem, you have several potential workarounds: - increase your port speeds - get a switch with bigger buffers - tune the output buffers on your existing switch - in your particular case, you could try fiddling with the etherchannel hashing algorithm to see if it helps (it's unlikely to make the problem disappear completely). Going back to your port channel Port-channel2 is up, line protocol is up (connected) Hardware is EtherChannel, address is 001b.d59d.7199 (bia 001b.d59d.7199) MTU 1500 bytes, BW 20 Kbit, DLY 100 usec, reliability 255/255, txload 24/255, rxload 2/255 Encapsulation ARPA, loopback not set Keepalive set (10 sec) Full-duplex, 100Mb/s, link type is auto, media type is unknown input flow-control is off, output flow-control is unsupported Members in this channel: Fa0/23 Fa0/24 Your problem is here -- ^ You need to upgrade your switch to a gig capable device. You've outgrown your existing equipment. Nick ___ 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] STP and customer ports
Im not sure you have a choice. If there are redundant links in the design then spanning tree is the only way to prevent loops (unless you're running TRILL or something like that). If you don't have any redundant links then spanning tree can't cause much damage, although I would still leave it enabled. On Tue, Jan 18, 2011 at 3:07 PM, Jay Nakamura zeusda...@gmail.com wrote: Is there any good reason to turn on STP on a switch port to a customer? It seems like it could cause more trouble than preventing a loop. What's your common practice? What if you hand off two connection for redundancy? I am in the middle of converting to MSTP from a network that didn't really have any STP design or goals. ___ 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] Constant output drops on etherchannel
What load-balance method do you use? If you see an uneven distribution of output drops across the 2 L2 interface, consider changing the etherchannel load-balance method to have a more even traffic distribution (src-dst-ip for example). I understand that you have 5 switches in the stack. You might consider spreading the etherchannel member interfaces across the stack members, in a way that the 2 ports should connect to different member switches (you can have the members on different members as cross-stack etherchannel is supported). This will ensure that you don't oversubscribe buffers on one port-asic (buffers are allocated per port-asic on 3750 switches). You might try to create a SPAN monitor session with the etherchannel member interfaces being the source ports to see if you find a burst of packets in a short interval which could lead to output drops due to buffer starvation. This will help you identify what's the source of the bursts. You might also look for unexpected or flooded traffic and consider pruning unnecessary vlans (if it's a trunk) to prevent flooding of broadcast and unknown unicast traffic on the etherchannel. Ultimately, you can increase the bandwidth by adding more links to the port-channel or using 10G links instead of GigabitEthernet. Best regards, Andras On Fri, Jan 14, 2011 at 10:08 PM, Robert VanOrmer vanor...@gmail.com wrote: I am experiencing a very similar issue on the C3750E platform w/ 12.2(52)SE. We have 5 switches in a cluster, port-channeled with (2) Gig interfaces L2 to distro (6500's) with excessive output drops even at low utilization. No QoS enabled. I am using the Cisco TwinGig Converter Modules for uplinks.. We have a TAC case open, but no progress yet. I'd be interested in knowing if you find a cause. I am going to try swapping GBICs over the weekend. Thanks, Rob Date: Fri, 14 Jan 2011 12:28:03 -0600 From: Dan Letkeman danletke...@gmail.com To: Phil Mayers p.may...@imperial.ac.uk Cc: cisco-nsp@puck.nether.net Subject: Re: [c-nsp] Constant output drops on etherchannel Message-ID: AANLkTiktxHw2Za3yWjU4rmPaa3q_-EU7N_dKtxUgMaz=@mail.gmail.com Content-Type: text/plain; charset=ISO-8859-1 3560 or 3560G. (C3560-IPSERVICESK9-M), Version 12.2(53)SE2 Interface config: interface Port-channel2 switchport trunk encapsulation dot1q switchport trunk native vlan 3009 switchport trunk allowed vlan 8,10,1008,1101,3009 switchport mode trunk end I see more output drops during higher traffic, but I still see drops during low traffic rates. Always more on one interface. I do have auto qos enabled for some of the phones I have connected to the switches, but I don't have any qos on the etherchannel trunks. I'm just using the default etherchannel load balancing algorithm. Thanks, Dan. ___ 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] STP and customer ports
There are only good reasons for enabling it on L2 links. STP is required to avoid bridging loops on L2 networks. The bad idea is to disable it, especially if you're planning to hand out redundant links. If you want to avoid incidents like creative customer attaching a switch to the network or advertising a superior root ID, enable RootGuard and BPDUGuard on the customer facing ports. This will disable the offending ports which has much less impact than having a L2 loop or continous STP instability in your network. Best regards, Andras On Tue, Jan 18, 2011 at 9:07 PM, Jay Nakamura zeusda...@gmail.com wrote: Is there any good reason to turn on STP on a switch port to a customer? It seems like it could cause more trouble than preventing a loop. What's your common practice? What if you hand off two connection for redundancy? I am in the middle of converting to MSTP from a network that didn't really have any STP design or goals. ___ 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] Bug Scrub
I'd say the 'best' way is to go through your account team. Cisco doesn't post all the bugs to their website. They only show the bugs which other customers have reported, and not ones found internally. Your account team will have access to ALL the bugs for a particular platform/code train. Ken Matlock Network Analyst Exempla Healthcare (303) 467-4671 matlo...@exempla.org -Original Message- From: cisco-nsp-boun...@puck.nether.net [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Tóth András Sent: Tuesday, January 18, 2011 1:48 PM To: Keegan Holley Cc: Cisco NSPs Subject: Re: [c-nsp] Bug Scrub Release Notes, Bug Toolkit, Account Team. On Tue, Jan 18, 2011 at 9:08 PM, Keegan Holley keegan.hol...@sungard.com wrote: What's the easiest way to find all bugs related to a particular platform? It's simple enough to look through the release notes and the like for specific version of IOS, but what about bugs related to specific box? ___ 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/
Re: [c-nsp] Catalyst 4500-E ROMMON Upgrade Caveat
Did you set the config-register to 0x0102 as well? It has been mentioned in the guide that it's mandatory in order for the system to autoboot with the IOS after the ROMMON upgrade. Best regards, Andras On Mon, Jan 17, 2011 at 2:18 PM, Sebastian Wiesinger cisco-...@ml.karotte.org wrote: Just a quick warning for people trying to upgrade a Cat4500-E with SUP6-E to 12.2(54)SG. The release notes for Cat4500 http://www.cisco.com/en/US/docs/switches/lan/catalyst4500/release/note/OL_5184.html state that you need a new ROMMON (12.2(44r)SG5) when installing the new IOS on a SUP6-E. There is a section Upgrading the Supervisor Engine ROMMON Remotely Using Telnet: http://www.cisco.com/en/US/docs/switches/lan/catalyst4500/release/note/OL_5184.html#wp466212 This section says that you should do a: boot system flash bootflash:cat4500-e-ios-promupgrade-122_44r_SG5 boot system flash bootflash:cat4500e-ipbasek9-mz.122-54.SG.bin (remove all other boot entries) After that the system should upgrade the rommon and then boot the IOS. Quote: Use the boot system flash bootflash:file_name command to set the BOOT variable. You will use two BOOT commands: one to upgrade the ROMMON and a second to load the Cisco IOS software image after the ROMMON upgrade is complete. Notice the order of the BOOT variables in the example below. At bootup the first BOOT variable command upgrades the ROMMON. When the upgrade is complete the supervisor engine will autoboot, and the second BOOT variable command will load the Cisco IOS software image specified by the second BOOT command. This is NOT the case! The system is endlessy upgrading the ROMMON, looping until stopped with CTRL-C via console. You can then manually boot the new IOS. So DO NOT upgrade the system unless you have console access! Kind Regards Sebastian -- New GPG Key: 0x93A0B9CE (F4F6 B1A3 866B 26E9 450A 9D82 58A2 D94A 93A0 B9CE) Old GPG Key-ID: 0x76B79F20 (0x1B6034F476B79F20) 'Are you Death?' ... IT'S THE SCYTHE, ISN'T IT? PEOPLE ALWAYS NOTICE THE SCYTHE. -- Terry Pratchett, The Fifth Elephant ___ 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] Bug Scrub
On 2011-01-18 22:36, Matlock, Kenneth L wrote: I'd say the 'best' way is to go through your account team. Cisco doesn't post all the bugs to their website. They only show the bugs which other customers have reported, and not ones found internally. Your account team will have access to ALL the bugs for a particular platform/code train. Account team job is not in any way to provide bug scrub information. The only source of Cisco-backed-up of bug information and software recommendation (which may, or may not depend on the other services) is to ask Cisco Services (and pay for it) to do it. There's a lot going on, and checking bug toolkit is just scratching the surface. -- There's no sense in being precise when | Łukasz Bromirski don't know what you're talking about. | jid:lbromir...@jabber.org John von Neumann |http://lukasz.bromirski.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] Strange T3 failure on 7206
Any attenuators involved?? I've actually experienced the same thing before and traced it back to what we believed to be a bad attenuator. Replaced it and LOS cleared right up. I only mention it because the Adtran MUX that was in use at that facility didn't have a way to dial down the DB's. On Tue, Jan 18, 2011 at 11:52 AM, Jay Hennigan j...@west.net wrote: We got an alarm that a T3 to a customer was down. PE router showed interface up, line protocol down. CE router showed down/down. Provider side goes to an Adtran Opti-mux out OC-12 to Verizon, customer end is a Verizon mux on premise. Called Vz and they claimed it was CPE, they saw idle loop towards our 7206 CE router. We shut/no-shut the interface and rebooted the 7206, no joy. I'm not familiar with the term idle loop, we were showing receive LOS and sending RAI. Customer IT guy came on site and saw CLOS on Verizon mux, alarm light on 7206. He disconnected the cable and put a coax loop towards the 7206. Interface came up-looped right away. Reconnected to Verizon mux and everything came back up nice and happy. That's what is bugging me. Circuit has been running fine for months. -- -- 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/ ___ 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] GE Servers in data center with teaming interfaces
Do any of you support / host servers from GE ? Anyone have any of them in LACP port channels ? thank you, chris ___ 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] Bug Scrub
Agreed, and just asking for all the bugs on the platform(if you got it) would likely give a deluge of mostly useless / incomprehensible info. What you want to do is frame it something like this. I will be deploying this box, to this place in my network, to offer these services, with this code train. What are the currently known / outstanding issues for this box in this scenario? -Ben On Jan 18, 2011, at 5:16 PM, Łukasz Bromirski wrote: On 2011-01-18 22:36, Matlock, Kenneth L wrote: I'd say the 'best' way is to go through your account team. Cisco doesn't post all the bugs to their website. They only show the bugs which other customers have reported, and not ones found internally. Your account team will have access to ALL the bugs for a particular platform/code train. Account team job is not in any way to provide bug scrub information. The only source of Cisco-backed-up of bug information and software recommendation (which may, or may not depend on the other services) is to ask Cisco Services (and pay for it) to do it. There's a lot going on, and checking bug toolkit is just scratching the surface. -- There's no sense in being precise when | Łukasz Bromirski don't know what you're talking about. | jid:lbromir...@jabber.org John von Neumann |http:// lukasz.bromirski.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/ ___ 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] ATM over a Serial Interface question
Hello, We have a number of channelized DS3's that are terminating on to a 7206VXR with the standard old PA-MC-T3 cards. We have a need to deliver ATM based DS1's out to Adtran DSLAMs in the field. Customers will connect to the Adtran units via ADSL and their local telco loop and their data is then aggregated by the Adtran and on to the ATM based T1 coming back to us. SO, my question is if we can deliver these circuits to the Adtran units using the encapsulation atm-dxi on each serial interface. I know this encapsulation is for delivering ATM through an ATM ADSU, but in this application, does the far end Adtran function as the ADSU or are we missing something on our end? Thanks very much for the help. -Nick Voth ___ 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] GE Servers in data center with teaming interfaces
On 18/01/2011 22:27, chris stand wrote: Do any of you support / host servers from GE ? Anyone have any of them in LACP port channels ? Yes. Be very careful with your switch uplinks if you do this, because applications can be badly behaved and can cause serious problems due to microbursting. Nick ___ 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] ATM over a Serial Interface question
Nick Voth nv...@estreet.com wrote: We have a number of channelized DS3's that are terminating on to a 7206VXR with the standard old PA-MC-T3 cards. We have a need to deliver ATM based DS1's out to Adtran DSLAMs in the field. Customers will connect to the Adtran units via ADSL and their local telco loop and their data is then aggregated by the Adtran and on to the ATM based T1 coming back to us. Let me see if I've understood you correctly: you are planning on feeding a whole DSLAM with a single T1? In other words, the aggregated bandwidth usage of all subscribers you are going to serve is going to fit into a single 1.5 Mbps T1? I thought today's spoiled ADSL users demand a heck of a lot more than that... (The latter thought is based on my personal experience of the level of ridicule I get for promoting my beloved SDSL which also maxes out at 1.5 Mbps.) SO, my question is if we can deliver these circuits to the Adtran units using the encapsulation atm-dxi on each serial interface. I know this encapsulation is for delivering ATM through an ATM ADSU, but in this application, does the far end Adtran function as the ADSU or are we missing something on our end? I invite someone from Cisco to prove me wrong, but my understanding is that encapsulation atm-dxi is another term for what's also known as ATM FUNI: http://ifctfvax.Harhan.ORG/OpenWAN/l2conv.html With ATM FUNI aka DXI the line carries HDLC frames which have the AAL5 packets encapsulated in them, so the hardware is still HDLC. True ATM over DS1, OTOH, would mean running actual 53-octet ATM cells over the DS1 bits, which calls for significantly different hardware. I would expect that a DS1 feeding a DSLAM would need to be true ATM, but I'm not familiar with Adtran DSLAMs specifically. (The DSLAMs which I do know want to be fed with DS3 or higher, not DS1, and they do want ATM cells over that DS3, not FUNI or DXI.) HTH, MS ___ 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] Catalyst 4500-E ROMMON Upgrade Caveat
Neither setting confreg to 0x102 doesn't help here. Also, in release notes directly focused to ROMMON for Sup6E, there's only serial console method (with boot break) mentioned for upgrading. Daniel On 01/18/2011 10:36 PM, Tóth András wrote: Did you set the config-register to 0x0102 as well? It has been mentioned in the guide that it's mandatory in order for the system to autoboot with the IOS after the ROMMON upgrade. Best regards, Andras On Mon, Jan 17, 2011 at 2:18 PM, Sebastian Wiesinger cisco-...@ml.karotte.org wrote: Just a quick warning for people trying to upgrade a Cat4500-E with SUP6-E to 12.2(54)SG. The release notes for Cat4500 http://www.cisco.com/en/US/docs/switches/lan/catalyst4500/release/note/OL_5184.html state that you need a new ROMMON (12.2(44r)SG5) when installing the new IOS on a SUP6-E. There is a section Upgrading the Supervisor Engine ROMMON Remotely Using Telnet: http://www.cisco.com/en/US/docs/switches/lan/catalyst4500/release/note/OL_5184.html#wp466212 This section says that you should do a: boot system flash bootflash:cat4500-e-ios-promupgrade-122_44r_SG5 boot system flash bootflash:cat4500e-ipbasek9-mz.122-54.SG.bin (remove all other boot entries) After that the system should upgrade the rommon and then boot the IOS. Quote: Use the boot system flash bootflash:file_name command to set the BOOT variable. You will use two BOOT commands: one to upgrade the ROMMON and a second to load the Cisco IOS software image after the ROMMON upgrade is complete. Notice the order of the BOOT variables in the example below. At bootup the first BOOT variable command upgrades the ROMMON. When the upgrade is complete the supervisor engine will autoboot, and the second BOOT variable command will load the Cisco IOS software image specified by the second BOOT command. This is NOT the case! The system is endlessy upgrading the ROMMON, looping until stopped with CTRL-C via console. You can then manually boot the new IOS. So DO NOT upgrade the system unless you have console access! ___ 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] ATM over a Serial Interface question
There are many cases when terminating a DSLAM with a single T1 makes sense. You assumed that these were ADSL end users, they may not be. We used this exact model in a previous gig to terminate a bunch of management interfaces on hardware or console servers. There's lots of telemetry type applications where this setup is more than enough to meet the need. Also, the DSLAMs I am familiar with (samsung, redback and nokia) can terminate DS3 or DS1. On Jan 18, 2011, at 4:29 PM, Michael Sokolov wrote: Nick Voth nv...@estreet.com wrote: We have a number of channelized DS3's that are terminating on to a 7206VXR with the standard old PA-MC-T3 cards. We have a need to deliver ATM based DS1's out to Adtran DSLAMs in the field. Customers will connect to the Adtran units via ADSL and their local telco loop and their data is then aggregated by the Adtran and on to the ATM based T1 coming back to us. Let me see if I've understood you correctly: you are planning on feeding a whole DSLAM with a single T1? In other words, the aggregated bandwidth usage of all subscribers you are going to serve is going to fit into a single 1.5 Mbps T1? I thought today's spoiled ADSL users demand a heck of a lot more than that... (The latter thought is based on my personal experience of the level of ridicule I get for promoting my beloved SDSL which also maxes out at 1.5 Mbps.) SO, my question is if we can deliver these circuits to the Adtran units using the encapsulation atm-dxi on each serial interface. I know this encapsulation is for delivering ATM through an ATM ADSU, but in this application, does the far end Adtran function as the ADSU or are we missing something on our end? I invite someone from Cisco to prove me wrong, but my understanding is that encapsulation atm-dxi is another term for what's also known as ATM FUNI: http://ifctfvax.Harhan.ORG/OpenWAN/l2conv.html With ATM FUNI aka DXI the line carries HDLC frames which have the AAL5 packets encapsulated in them, so the hardware is still HDLC. True ATM over DS1, OTOH, would mean running actual 53-octet ATM cells over the DS1 bits, which calls for significantly different hardware. I would expect that a DS1 feeding a DSLAM would need to be true ATM, but I'm not familiar with Adtran DSLAMs specifically. (The DSLAMs which I do know want to be fed with DS3 or higher, not DS1, and they do want ATM cells over that DS3, not FUNI or DXI.) HTH, MS ___ 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] ATM over a Serial Interface question
Scott Granados sc...@granados-llc.net wrote: Also, the DSLAMs I am familiar with (samsung, redback and nokia) can = terminate DS3 or DS1. Nokia D50 is the one I'm familiar with: http://ifctfvax.Harhan.ORG/OpenWAN/DSLAMs/Nokia/ Its uplink options are DS3/ATM or OC3/ATM, no DS1/ATM. It can *serve out* DS1s (I assume that's how Covad serves their T1 customers), and it can use 4xDS1 for its internal proprietary MCS-LCS link, but no DS1 uplink. Or did you mean a different Nokia? MS ___ 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] Strange T3 failure on 7206
Jay-- I have had similar experience with some T3s from Vz. I like to unplug and replug as you and Gert noted. Plus I like to keep some spare coax and adapters hanging around my routers. When I invariably receive the it's the CPE I loop the cables and ask them if they see a loop. That shuts them up fast. ;-) - Jay writes: Date: Tue, 18 Jan 2011 09:52:16 -0800 From: Jay Hennigan j...@west.net To: Cisco Mailing list cisco-nsp@puck.nether.net Subject: [c-nsp] Strange T3 failure on 7206 Message-ID: 4d35d350.4000...@west.net Content-Type: text/plain; charset=ISO-8859-1 We got an alarm that a T3 to a customer was down. PE router showed interface up, line protocol down. CE router showed down/down. Provider side goes to an Adtran Opti-mux out OC-12 to Verizon, customer end is a Verizon mux on premise. Called Vz and they claimed it was CPE, they saw idle loop towards our 7206 CE router. We shut/no-shut the interface and rebooted the 7206, no joy. I'm not familiar with the term idle loop, we were showing receive LOS and sending RAI. Customer IT guy came on site and saw CLOS on Verizon mux, alarm light on 7206. He disconnected the cable and put a coax loop towards the 7206. Interface came up-looped right away. Reconnected to Verizon mux and everything came back up nice and happy. That's what is bugging me. Circuit has been running fine for months. -- -- 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 cjw ___ 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] Ping test with DF bit and MTU / IP MTU value
Hi, I have very basic question related to MTU / IP MTU value and ping test with DF bit *Scenario: * I have one router connected to HUB router with Link leasing from SP ** 1. On spoke side, we have GigaEthernet Interface with MTU value set to 1520 2. On HUB side, that link is terminated on layer-2 switch and from there to router sub-interface with IP MTU value set to 1520. 3. Configurations on both router * a. SPOKE Side* * *interface GigabitEthernet0/1 mtu 1520 bandwidth 1 ip address 192.168.0.1 255.255.255.252 ip ospf network point-to-point ip ospf cost 1000 ip ospf hello-interval 1 ip ospf dead-interval 3 ip ospf mtu-ignore duplex auto speed auto mpls ip *b. HUB Side* * interface GigabitEthernet0/1.100 bandwidth 1 encapsulation dot1Q 100 ip address 192.168.0.2 255.255.255.252 ip mtu 1520 ip ospf network point-to-point ip ospf cost 1000 ip ospf hello-interval 1 ip ospf dead-interval 3 ip ospf mtu-ignore mpls ip * *Issue:* I am testing the link and face issue. 1. while performing ping test without df bit, I am able to ping with size upto 18024 2. while performing ping test with df bit, I am able to ping with size 1520 3. while performing ping test with df bit, I am able to ping with size more than 1520 *Kindly let me know, why I am not able to ping with DF bit with size more than 1520 (MTU value). How can I troubleshoot the issue. * * * *Any comment please* -- Regards, Muhammad Atif Jauhar (+60-10-2155076) ___ 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] ATM over a Serial Interface question
Yes these end users are ADSL users and in many cases these are very rural connections where a single T1 will suffice. Often we bond several of them with IMA to get better capacity, but higher bandwidth links are unavailable. Thanks, -Nick Voth From: Scott Granados sc...@granados-llc.net Date: Tue, 18 Jan 2011 16:45:44 -0800 To: Michael Sokolov msoko...@ivan.harhan.org Cc: cisco-nsp@puck.nether.net cisco-nsp@puck.nether.net, nv...@estreet.com nv...@estreet.com Subject: Re: [c-nsp] ATM over a Serial Interface question There are many cases when terminating a DSLAM with a single T1 makes sense. You assumed that these were ADSL end users, they may not be. We used this exact model in a previous gig to terminate a bunch of management interfaces on hardware or console servers. There's lots of telemetry type applications where this setup is more than enough to meet the need. Also, the DSLAMs I am familiar with (samsung, redback and nokia) can terminate DS3 or DS1. On Jan 18, 2011, at 4:29 PM, Michael Sokolov wrote: Nick Voth nv...@estreet.com wrote: We have a number of channelized DS3's that are terminating on to a 7206VXR with the standard old PA-MC-T3 cards. We have a need to deliver ATM based DS1's out to Adtran DSLAMs in the field. Customers will connect to the Adtran units via ADSL and their local telco loop and their data is then aggregated by the Adtran and on to the ATM based T1 coming back to us. Let me see if I've understood you correctly: you are planning on feeding a whole DSLAM with a single T1? In other words, the aggregated bandwidth usage of all subscribers you are going to serve is going to fit into a single 1.5 Mbps T1? I thought today's spoiled ADSL users demand a heck of a lot more than that... (The latter thought is based on my personal experience of the level of ridicule I get for promoting my beloved SDSL which also maxes out at 1.5 Mbps.) SO, my question is if we can deliver these circuits to the Adtran units using the encapsulation atm-dxi on each serial interface. I know this encapsulation is for delivering ATM through an ATM ADSU, but in this application, does the far end Adtran function as the ADSU or are we missing something on our end? I invite someone from Cisco to prove me wrong, but my understanding is that encapsulation atm-dxi is another term for what's also known as ATM FUNI: http://ifctfvax.Harhan.ORG/OpenWAN/l2conv.html With ATM FUNI aka DXI the line carries HDLC frames which have the AAL5 packets encapsulated in them, so the hardware is still HDLC. True ATM over DS1, OTOH, would mean running actual 53-octet ATM cells over the DS1 bits, which calls for significantly different hardware. I would expect that a DS1 feeding a DSLAM would need to be true ATM, but I'm not familiar with Adtran DSLAMs specifically. (The DSLAMs which I do know want to be fed with DS3 or higher, not DS1, and they do want ATM cells over that DS3, not FUNI or DXI.) HTH, MS ___ 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] ATM over a Serial Interface question
Nick Voth nv...@estreet.com wrote: Often we bond several of them with IMA to get better capacity, but higher bandwidth links are unavailable. Well, if these DS1/ATM connections can be bonded with IMA, that certainly indicates they are true ATM, not FUNI/DXI, so encapsulation atm-dxi won't help, sorry. I don't know of any single piece of hardware that can take a CT3, internally break it up into T1s and handle each T1 as an ATM (not HDLC) interface. But you should be able to use standard TDM gear to pull T1s out of the CT3, and then find some gear that will do DS1/ATM given a single physical T1 interface. But wait a minute... the quoted sentence is in present tense. Do you already have a working setup? Your original message seemed to indicate that this was something you are *planning* to implement, and you were wondering if your PA-MC-T3 can handle it, weren't you? A bit confused, MS ___ 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] Ping test with DF bit and MTU / IP MTU value
Hi, On 19 January 2011 15:20, Muhammad Atif Jauhar atif.jau...@gmail.com wrote: Hi, I am testing the link and face issue. 1. while performing ping test without df bit, I am able to ping with size upto 18024 2. while performing ping test with df bit, I am able to ping with size 1520 3. while performing ping test with df bit, I am able to ping with size more than 1520 *Kindly let me know, why I am not able to ping with DF bit with size more than 1520 (MTU value). How can I troubleshoot the issue. * Points 2 and 3 seem to be contradictory. Assuming that you actually meant that you can not ping with packets bigger then 1520 with the DF bit set - this is expected behaviour. The DF bit tells the routers that they can not fragment that packet (which they do if the DF is not set). As your MTU is 1520 the biggest packet with DF bit set can only be 1520. Anything bigger won't be forwarded. 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] Ping test with DF bit and MTU / IP MTU value
Yes... there is typo error in 3rd point I am not able to ping more then size 1520 with DF bit Means there is no issue in link and I will not able to ping with DF bit more then size 1520. On Wed, Jan 19, 2011 at 10:49 AM, Pshem Kowalczyk pshe...@gmail.com wrote: Hi, On 19 January 2011 15:20, Muhammad Atif Jauhar atif.jau...@gmail.com wrote: Hi, I am testing the link and face issue. 1. while performing ping test without df bit, I am able to ping with size upto 18024 2. while performing ping test with df bit, I am able to ping with size 1520 3. while performing ping test with df bit, I am able to ping with size more than 1520 *Kindly let me know, why I am not able to ping with DF bit with size more than 1520 (MTU value). How can I troubleshoot the issue. * Points 2 and 3 seem to be contradictory. Assuming that you actually meant that you can not ping with packets bigger then 1520 with the DF bit set - this is expected behaviour. The DF bit tells the routers that they can not fragment that packet (which they do if the DF is not set). As your MTU is 1520 the biggest packet with DF bit set can only be 1520. Anything bigger won't be forwarded. kind regards Pshem -- Regards, Muhammad Atif Jauhar (+60-10-2155076) ___ 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] Ping test with DF bit and MTU / IP MTU value
Hi, On 19 January 2011 15:54, Muhammad Atif Jauhar atif.jau...@gmail.com wrote: Yes... there is typo error in 3rd point I am not able to ping more then size 1520 with DF bit Means there is no issue in link and I will not able to ping with DF bit more then size 1520. That's correct. 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] Ping test with DF bit and MTU / IP MTU value
Hey Muhammad, If you set the MTU size to 1520 and set the DF (do not fragment bit) then it will tell all device to never fragment the packets... So if a single hope in the chain can not support the max size of the packet you are sending it will drop the packet. Sorry not certain if I missed something here but that seems like a simple enough question and answer?!?! Cheers, Simon -Original Message- From: cisco-nsp-boun...@puck.nether.net [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Muhammad Atif Jauhar Sent: Wednesday, 19 January 2011 12:21 PM To: cisco-nsp@puck.nether.net Subject: [c-nsp] Ping test with DF bit and MTU / IP MTU value Hi, I have very basic question related to MTU / IP MTU value and ping test with DF bit *Scenario: * I have one router connected to HUB router with Link leasing from SP ** 1. On spoke side, we have GigaEthernet Interface with MTU value set to 1520 2. On HUB side, that link is terminated on layer-2 switch and from there to router sub-interface with IP MTU value set to 1520. 3. Configurations on both router * a. SPOKE Side* * *interface GigabitEthernet0/1 mtu 1520 bandwidth 1 ip address 192.168.0.1 255.255.255.252 ip ospf network point-to-point ip ospf cost 1000 ip ospf hello-interval 1 ip ospf dead-interval 3 ip ospf mtu-ignore duplex auto speed auto mpls ip *b. HUB Side* * interface GigabitEthernet0/1.100 bandwidth 1 encapsulation dot1Q 100 ip address 192.168.0.2 255.255.255.252 ip mtu 1520 ip ospf network point-to-point ip ospf cost 1000 ip ospf hello-interval 1 ip ospf dead-interval 3 ip ospf mtu-ignore mpls ip * *Issue:* I am testing the link and face issue. 1. while performing ping test without df bit, I am able to ping with size upto 18024 2. while performing ping test with df bit, I am able to ping with size 1520 3. while performing ping test with df bit, I am able to ping with size more than 1520 *Kindly let me know, why I am not able to ping with DF bit with size more than 1520 (MTU value). How can I troubleshoot the issue. * * * *Any comment please* -- Regards, Muhammad Atif Jauhar (+60-10-2155076) ___ 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/ Buy your loved one the gift of peace of mind with an RACQ gift membership. Join the Club today at www.racq.com/membership, 13 1905, 24 hours every day or in store Please Note: If you are not the intended recipient, please delete this email as its use is prohibited. RACQ does not warrant or represent that this email is free from viruses or defects. If you do not wish to receive any further commercial electronic messages from RACQ please e-mail unsubscr...@racq.com.au or contact RACQ on 13 19 05. ___ 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/
