Re: [c-nsp] Looping up far end smartjack
Fiber fed ones aren't - but usually the copper loop fed ones are. -Original Message- From: cisco-nsp-boun...@puck.nether.net [mailto:cisco-nsp- boun...@puck.nether.net] On Behalf Of Adam Korab Sent: Monday, June 28, 2010 7:01 PM To: Richey Cc: cisco-nsp@puck.nether.net Subject: Re: [c-nsp] Looping up far end smartjack On Thu, Jun 24, 2010 at 9:17 AM, Richey myli...@battleop.com wrote: I was hoping to avoid having to go to the colo late at night. We did finally hear from the customer. A breaker had tripped and they person on duty had no idea where the breakers were in the building. T1 duty was long ago in a galaxy far away for me...but aren't NIUs all line-powered? That is, wouldn't you want to loop the remote CSU/DSU anyway to confirm power? --Adam ___ 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] Cisco ISP Essentials - Book Not For Sale
I was able to get a copy from Amazon as a used copy. 2 new from $59.99 8 used from $39.95 -Original Message- From: cisco-nsp-boun...@puck.nether.net [mailto:cisco-nsp- boun...@puck.nether.net] On Behalf Of Felix Nkansah Sent: Tuesday, May 04, 2010 7:42 PM To: cisco-nsp@puck.nether.net Subject: [c-nsp] Cisco ISP Essentials - Book Not For Sale Hi, The book may appear dated (2002) but most of us still find it useful. I just checked the Cisco Press website with the intention of buying a few hard copies. However, the site says of the book http://www.ciscopress.com/bookstore/product.asp?isbn=1587050412This publication is not for sale. Which other good books still in print would you recommend as an ISP operations practices guide? Thanks. Felix ___ 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] DC Inverters
You mean DC rectifiers for turning AC into DC? If you are going through the trouble, why not throw on a small chain of deep cycles to smooth things out and let you run a bit in a power outage? -Paul From: cisco-nsp-boun...@puck.nether.net [cisco-nsp-boun...@puck.nether.net] on behalf of Charles Mills [w3y...@gmail.com] Sent: Monday, March 29, 2010 3:36 PM To: cisco-nsp@puck.nether.net Subject: [c-nsp] DC Inverters Is anyone running DC for their Cisco 6509's and just using rack mount DC inverters in lieu of having a DC Power Plant? And..if so, what's everyone using for their inverters? Any to avoid or to recommend? Chuck ___ 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] Unified IOS (15.x) and feature based licensing model
I think it makes my choice to use Adtran CPE well placed. Except for their lack of IPv6 support *grumble* From: cisco-nsp-boun...@puck.nether.net [cisco-nsp-boun...@puck.nether.net] on behalf of Tim Franklin [...@pelican.org] Sent: Wednesday, March 24, 2010 7:43 AM To: cisco-nsp@puck.nether.net Subject: Re: [c-nsp] Unified IOS (15.x) and feature based licensing model What do others think of this new paradigm? I think the enforced licensing is going to give me a whole lot of operational pain. Installing CPE in volume (and not even *real* residential-type volumes, I'm only talking tens per week) seems like it's going to need a big manual addition to the process to generate license keys and get them installed on the *right* CPE. I haven't even looked into the ifs and hows of revoking them or transferring them to another box in the event of a hardware failure / swap-out. To me, it looks horribly similar to the entertainment industry. We're not making enough money leads to someone must be taking something without paying, or we'd make as much money as is in our business plan, leads to let's do X to ensure everyone pays. The user experience for *legitimate customers* gets worse, and the people who are prepared to resort to illegitimate means, or get their products from somewhere else still don't hand over the missing money. Regards, Tim. ___ 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] strange ipv6 problems on 3550 SVI
Feature Navigator is wrong - as usual. 3550 does not have hw support for IPv6, therefore no support for it. No plan, according to BU (have this info via our account manager), to support IPv6 on these switches. Go for 3560 or 3750 Best Regards, Janos Mohacsi What's worse is, the CLI supports IPv6 and it looks like it works, but it definitely does not. -Paul ___ 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] ipv6 cheat sheet
You can subnet ipv6 with your eyeballs, just add or subtract 4 from the prefix length for every character you move to the left or right. 1234:1234:1234:1234::/64 1234:1234:1234:123X::/60 1234:1234:1234:12XX::/56 1234:1234:1234:1XXX::/52 1234:1234:1234::/48 etc -Original Message- From: cisco-nsp-boun...@puck.nether.net [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Good One Sent: Wednesday, November 25, 2009 6:54 PM To: cisco-nsp@puck.nether.net Subject: [c-nsp] ipv6 cheat sheet Hello guys, Did you find any cheat sheet for IPv6 subnetting anywhere? _ Windows Live: Friends get your Flickr, Yelp, and Digg updates when they e-mail you. http://www.microsoft.com/middleeast/windows/windowslive/see-it-in-action /social-network-basics.aspx?ocid=PID23461::T:WLMTAGL:ON:WL:en-xm:SI_SB_3 :092010 ___ 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] IPV6 in general was Re: Large networks
We've got paying customers who came to us specifically because we support it. Our last decision for IP transport had IPv6 as a requirement. YMMV. -Original Message- From: cisco-nsp-boun...@puck.nether.net [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Scott Granados Sent: Wednesday, August 26, 2009 1:58 PM To: Ivan Pepelnjak; 'Gert Doering'; 'Mikael Abrahamsson' Cc: cisco-nsp@puck.nether.net Subject: [c-nsp] IPV6 in general was Re: Large networks I'm interested in general, how much IPV6 is actually out there? I'm very unfamiliar but at my present gig and my last few I never ran in to this once. Is it actually being used in production? Thank you Scott - Original Message - From: Ivan Pepelnjak i...@ioshints.info To: 'Gert Doering' g...@greenie.muc.de; 'Mikael Abrahamsson' swm...@swm.pp.se Cc: cisco-nsp@puck.nether.net Sent: Wednesday, August 26, 2009 10:33 AM Subject: Re: [c-nsp] Large networks Well, I think that it's reckless to spend 4 globally routable IP addresses instead of 1 per customer, when all you do is save a few minutes of time per installation. As I said: our customers usually use many more IP addresses than just one. And, of course, you're welcome to join us in IPv6 land where this sort of last century thinking does not need to worry us any longer :-) Some of us still have to live with reality where IPv6 deployment is negligible :) ... And don't forget some IBM mainframes are still forced to run operating systems emulating 80-column card reader :D ___ 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] BGP router-id - Chaos?
As far as I know, changing the router ID will take care of clearing the BGP tables for you. :) It should reset all sessions. -Original Message- From: cisco-nsp-boun...@puck.nether.net [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Jeff Cartier Sent: Wednesday, July 15, 2009 1:49 PM To: cisco-nsp@puck.nether.net Subject: [c-nsp] BGP router-id - Chaos? Just checking something that I haven't been able to verify online... Changing the bgp router-id manually will require you to clear the bgp sessions? Correct? Thanks!!! ___ 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] IPV6 to IPV4
Dual Stack. -Original Message- From: cisco-nsp-boun...@puck.nether.net [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Chintan Shah Sent: Wednesday, July 15, 2009 2:08 PM To: cisco-nsp@puck.nether.net Subject: [c-nsp] IPV6 to IPV4 Hi, The IPV6 host has to communicate to some IPV4 on Internet, I can use NAT-PT one but I see that it is now no more recommended. So, what is best translation mechanism achieve this when I being ISP provide IPV6 Internet service to my customer? Regards, CS ___ 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] Extended demarc
If you're asking about T1s, we've extended a demarc 23 stories over Category 0 building pair from the 70s or 80s and the circuit has run flawlessly. You have to test the cables when they're that old due to building sway causing shorts and things like that, but it works. T1s are designed to go several miles without repeaters on cable you'd barely want to run voice over. Ethernet IIRC can only go 300 meters or something like that, regardless of how fancy your cable is due to timing issues and the speed of light. But I don't extend Ethernet very often so I'm not an expert in that part. -Paul -Original Message- From: cisco-nsp-boun...@puck.nether.net [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of james edwards Sent: Wednesday, July 08, 2009 5:41 PM To: cisco-nsp@puck.nether.net Subject: [c-nsp] Extended demarc What is a real word limit on how far you can extend the demarc ? This is on Cat5e cable. I get wildly different figures from Google. Thanks, -- James H. Edwards Senior Network Systems Administrator Judicial Information Division jedwa...@nmcourts.gov ___ 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] PIX/ASA Change Control
We use subversion, and giving web access to the repository through the normal subversion frontend, no special additions, works for us, but our needs have been basically just to get a last known good configuration to blow onto a customer's replacement unit prior to dispatching a technician. Works pretty well, as you can just download the file from the repository, put it on the unit with xmodem over the serial port as the startup-config, reboot, and you've got an identical copy of what was there. We do this with Adtran Total Access 900 and Netvanta gear and our Cisco CPE using the same config in Rancid (using cisco as the type works just fine for Adtran AOS based gear) and it's a lifesaver. -Paul -Original Message- From: cisco-nsp-boun...@puck.nether.net [mailto:cisco-nsp- boun...@puck.nether.net] On Behalf Of Justin Shore Sent: Friday, June 26, 2009 10:25 AM To: Ryan West Cc: Cisco-nsp; rancid-disc...@shrubbery.net Subject: Re: [c-nsp] PIX/ASA Change Control Ryan West wrote: I'm curious to see what others are using for a frontend to RANCID. Besides the emailing of the diff's that take place, what are others using to browse the repository? I'm not a CVS buff so I'm sure someone that falls into that category would have a better solution. I currently just use the standard cvsweb CGI. It works well enough. I keep it in a password protected directory on my servers. Not overly elegant but it works well enough. Does anyone else have any other suggestions for a web GUI front-end to CVS for RANCID use? Justin ___ 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] Adding member to Multilink PPP during production
We do this all the time in carrier scenarios, carrying voip. I've never seen a problem with taking out members of ppp multilink groups at random, and re-adding them at random. It might cause a packet or two to drop when the link goes away unexpectedly. -Original Message- From: cisco-nsp-boun...@puck.nether.net [mailto:cisco-nsp- boun...@puck.nether.net] On Behalf Of Jeff Wojciechowski Sent: Friday, April 24, 2009 12:31 PM To: cisco-nsp@puck.nether.net Subject: [c-nsp] Adding member to Multilink PPP during production Hi all, We took down one of our 3 T1's in a PPP multilink group last night so that the LEC could replace a cable pair. Is it safe to add it back to the bundle during production hours? We've got mostly VoIP and Citrix traffic traversing that WAN link. Naturally it's the VoIP that I am mostly concerned about. Thanks, Jeff --- --- -- This electronic mail (including any attachments) may contain information that is privileged, confidential, or otherwise protected from disclosure to anyone other than its intended recipient(s). Any dissemination or use of this electronic mail or its contents (including any attachments) by persons other than the intended recipient(s) is strictly prohibited. If you have received this message in error, please delete the original message in its entirety (including any attachments) and notify us immediately by reply email so that we may correct our internal records. Midland Paper Company accepts no responsibility for any loss or damage from use of this electronic mail, including any damage resulting from a computer virus. ___ 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] Rancid and commercial config management tools
If I were you, I'd package up Rancid, call it JoeWare, and bill them a ton for it. :) -Original Message- From: cisco-nsp-boun...@puck.nether.net [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Joe Loiacono Sent: Thursday, February 05, 2009 4:57 PM To: Cisco-NSP Mailing List Subject: [c-nsp] Rancid and commercial config management tools I realize RANCID is a great tool for keeping track of IOS changes, etc., but if a client was looking for a commercial tool that does this, what would you recommend? Thanks, Joe Loiacono ___ 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] Backing up a 15454 over TL1 - Database Is Busy
I have a ONS that I am backing up over TL1. If I run the program I wrote to handle the TL1 manually, it works after a couple of tries. If I connect in directly and type the commands, it runs properly almost every time. Running from cron, I always get an error about the database being busy. Anyone here ever done this before? Have any pointers? -Original Message- WARNING Only authorized persons may use this system for legal and proper purposes as determined solely by Clear Rate. By using this system, you consent to monitoring. ACT-USER::monitoring:A286::*; X-CR-ONS1 2009-01-07 19:00:01 M A286 COMPLD monitoring:2009-01-07 17-00-02,0 ; X-CR-ONS1 2009-01-07 19:00:01 A 0 REPT EVT SESSION XX-CR-ONS1:NO, /* TL1 Agent Copyright (c) 1999-2007 Cisco Systems, Inc. WARNING Only authorized persons may use this system for legal and proper purposes as determined solely by Clear Rate. By using this system, you consent to monitoring. User monitoring logged in from x.x.x.x */ ; End of login COPY-RFILE::RFILE-DB:A998::TYPE=RFBU,DEST=FTP://redactedurlcontainingus ernameandpassword/ons1-backup.pkg; Config Downloaded CANC-USER::monitoring:A595; XX-CR-ONS1 2009-01-07 19:00:01 M A998 DENY SROF /* Database Is Busy */ ; Logged out ___ 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] OK, what is a cheap and dirty hack to test a port
Most modern sonet gear does not provide clocking to individual DS1s running it. The only reason clocking ever existed on point to point circuits was that the older gear couldn't avoid being an active participant in the circuit. It's possible the carrier you're using has upgraded the equipment, and where it was once providing the clocking (which it couldn't avoid previously), it's now on gear that can now act indistinguishably from a straight piece of wire (of course, it has to follow T1 line encoding and framing, but beyond that..). I've seen this plenty over the last 5 years as carriers upgrade, and roll DS3s onto newer gear. One night, the clocking gets funky, and you have to enable clock, which was causing problems before, but now works fine. (Of course, we don't feel it as much, because we are syncing our gear off the BITS in our CO, so we'd be in sync with the ILEC whether we provide clocking or not, so we just provide clocking on our end of all loops, and slave the customer sites.) It's also possible for two devices set to clock off line to work for a while, without anyone providing external clock. Since there's not really a clock signal per se, but just a directive that says whether your internal source is authorative, or whether you should be sending your own frames in sync with the frames you're getting off the line, both devices can feed off of each other (a device without line clock will fall back to internal clock, and start sending frames. The other device will see the clock signal on the line, and sync with it. Then the original device sees the framing on the line, and syncs with that. The devices then sync off whatever each other are sending. Because this isn't precise (but can be precise enough), it's possible for the line to work for a while like that, until power blips, line hits, or random cosmic noise cause the whole thing to fall apart). Anyway, the network has to actively participate in the circuit to provide clock, and the field has been running away from this for years. Set one side to line clock, and one to internal, and forget it. It's a single line of config. :) -Paul PS: I'm using the term providing clock because that's what we're calling it in this thread. The way you should actually think about it though, is using your own clock reference, or using the reference coming from the line. In the PSTN world, everyone provides clock (uses their own clock reference) and you don't trust the line clock from anywhere. Because your clock references are in sync with each other (because you're syncing off a cesium reference, using GPS, or CDMA, or you have a BITS T1 from the local LEC, or some combination of those) everything works flawlessly (insofar as that's possible in real life). CPE aren't expected to have their own stratum 1 reference clock, so they just trust the line signal. If you're connecting CPE to CPE, you're going to have to provide your own reference clock, and it doesn't have to be stratum 1 since you're not interfacing with anyone else (unless you're passing through some real old DACS or Mux gear that actively participates in the circuit, rather than just encapsulating it in a DS3 and sending it on its way through the network) it doesn't have to be in sync. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Luan Nguyen Sent: Wednesday, October 15, 2008 10:51 AM To: 'Roy' Cc: cisco-nsp@puck.nether.net Subject: Re: [c-nsp] OK, what is a cheap and dirty hack to test a port It's on fiber. I asked if we could get network timing from them, but they said no, not on this type of circuit. Also, this circuit has been working for years with the same setting :) Luan Nguyen Chesapeake NetCraftsmen, LLC. www.NetCraftsmen.net -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Roy Sent: Wednesday, October 15, 2008 10:36 AM Cc: cisco-nsp@puck.nether.net Subject: Re: [c-nsp] OK, what is a cheap and dirty hack to test a port Just because its a point to point circuit doesn't mean one side has to have internal clocking. This is only true if the circuit is copper all the way. There are lots of reasons that the telco would have its own equipment installed on the circuit and you would need network timing. Roy Luan Nguyen wrote: Is it a Verizon circuit? We have a T1 circuit with Verizon and have the same problem. We have a point to point circuit, so one side has clocking set to internal to provide the clocking and the other side feeds from the line. I wrote the problem up at http://ccie-security.blogspot.com/ But basically, it will be up for a some hours then down, then I call them to test and it's good again. Sometime it's good just by unplug the cable and plug it back. Like you, we changed everything and that didn't help. Finally, we talked to a knowledgeable Verizon tester and he mentioned the rate on the line is ~17 which is
Re: [c-nsp] PA-POS-1OC3 vs. PA-A3-OC3SMI
If you want to do 1:1 DS3, that'd work. If you want to rearrange individual DS1s, you need a TransMux card -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David Aldworth Sent: Thursday, September 18, 2008 5:18 PM To: David Prall Cc: cisco-nsp@puck.nether.net Subject: Re: [c-nsp] PA-POS-1OC3 vs. PA-A3-OC3SMI A vendor suggested the following configuration: 15454 Chassis and Fan Dual TCC+ cards Dual Cross Connect Cards 1 DS3 card (12 DS3s) 1 DS3 backplane (24 DS3 Backplane) 1 OC3 card (4 port OC3) 1310 fiber only Seems like it is a big mux and I would still need to punch into a pa- mc-t3 or some such in order manage things at the T1 level. David On Sep 18, 2008, at 1:06 PM, David Prall wrote: I'm pretty sure this is how it would be. You would need a frame- relay switch in front of the POS interface, it isn't a CHOC interface. The ATM would need an ATM switch in front of it to support ATM T1's. There is a PA- MC-2T3+ that is channelized for the 7200. With this you could put a MUX in front of it. David -- http://dcp.dcptech.com -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David Aldworth Sent: Thursday, September 18, 2008 2:43 PM To: cisco-nsp@puck.nether.net Subject: [c-nsp] PA-POS-1OC3 vs. PA-A3-OC3SMI We are looking for a fully channelized OC3 interface for a Cisco 7200 VXR. Something that we can break individual T1's off of. In researching this there are two routes: PA-POS-1OC3 or PA-A3-OC3SMI. The first is SONET and the second is ATM. Other than price what is the difference? Which is needed? Thanks for any and all advice. David ___ 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] CBWFQ question
I just tried it on a 7206 VXR running 12.4 on an NPE-400, on a frame relay t1 interface with a ping running, and there was no change in packet loss or delay on addition or removal. I don't seem to ever have had it cause any drops or resets on T1s or FastEthernet on the 7206 VXR platform. YMMV. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Shaun Sent: Tuesday, July 29, 2008 5:55 PM To: cisco-nsp@puck.nether.net Subject: [c-nsp] CBWFQ question Does removing or adding CBWFQ on an interface drop the link? Or does it depend on traffic levels? Type of interface? I have had opinions both ways. ___ 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] MacOS9, AS53xxx and L2TP
I'm having a similar issue where my portmasters authenticate the user, hand the L2TP session to our 7206VXR, and then that falls apart and states invalid username or password. Our VXR is at 12.4(16) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Pshem Kowalczyk Sent: Wednesday, June 25, 2008 8:54 PM To: cisco-nsp Subject: [c-nsp] MacOS9, AS53xxx and L2TP Hi All, We provide dialup services using Cisco AS5400 and AS5300 (in few remote and low-use places). The ASes initiate L2TP tunnels to our 7301s, that in turn terminate the sessions. Everything was fine until we upgraded the 7301 to a newer software version (from 12.3.18 to 12.4.10). After that all MacOS9 users can't get the PPP up any more if they happen to connect to a 5300. Debugging is quite difficult due to volume of the calls that we handle and the fact that local telco sends call down the E1s at random (i.e. there is no guarantee, that second call made to the same number will go down the same E1 and end up on the same NAS). It looks like the PPP negotiation stops at certain stage and then times out. None of the other types of customers/OSes seem to have that problem. Has any of you encounter anything similar? I know that 5300 is not supported any more, but due to dialup dying out it's difficult to justify any spendings on the platform. 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/ ___ 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/
