- original message -
Subject: cisco-nsp Digest, Vol 66, Issue 114
From: [EMAIL PROTECTED]
Date: 05/31/2008 1:47 am
Send cisco-nsp mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://puck.nether.net/mailman/listinfo/cisco-nsp
or, via email, send a message with subject or body 'help' to
[EMAIL PROTECTED]
You can reach the person managing the list at
[EMAIL PROTECTED]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of cisco-nsp digest..."
Today's Topics:
1. Re: Memory requirements in Cisco Feature Navigator
(Steven Pfister)
2. Re: Memory requirements in Cisco Feature Navigator
(Church, Charles)
3. Re: Memory requirements in Cisco Feature Navigator
(Steven Pfister)
4. Re: High CPU load on Catalyst 3550 (Curtis Doty)
5. Re: Overlapping NAT subnets and PPTP (Andrew Gristina)
6. Re: Single strand SMF 10GbE (Andrew Gristina)
7. Re: Single strand SMF 10GbE (Richard A Steenbergen)
----------------------------------------------------------------------
Message: 1
Date: Fri, 30 May 2008 15:07:33 -0400
From: "Steven Pfister" <[EMAIL PROTECTED]>
Subject: Re: [c-nsp] Memory requirements in Cisco Feature Navigator
To: <[email protected]>
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=US-ASCII
It looks like without the command it defaults to 15%. Adding a 'memory-size
iomem 5' doesn't seem to do too much... I think it still defaults to 15%
Steve Pfister
Technical Coordinator,
The Office of Information Technology
Dayton Public Schools
115 S. Ludlow St.
Dayton, OH 45402
Office (937) 542-3149
Cell (937) 673-6779
Direct Connect: 137*131747*8
Email [EMAIL PROTECTED]
>>> "Church, Charles" <[EMAIL PROTECTED]> 5/30/2008 1:50 PM >>>
See if it works without the command. Bypassing the config via the
config register might do it too.
Chuck
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Steven Pfister
Sent: Friday, May 30, 2008 1:42 PM
To: [email protected]
Subject: Re: [c-nsp] Memory requirements in Cisco Feature Navigator
It's an IP plus image. It looks like there is a 'memory-size iomem 15'
in the config.
--Steve
Steve Pfister
Technical Coordinator,
The Office of Information Technology
Dayton Public Schools
115 S. Ludlow St.
Dayton, OH 45402
Office (937) 542-3149
Cell (937) 673-6779
Direct Connect: 137*131747*8
Email [EMAIL PROTECTED]
>>> "Church, Charles" <[EMAIL PROTECTED]> 5/30/2008 12:48 PM >>>
It's possible that FN is wrong. What feature set are you using? Do you
have 'memory-size iomem' configured on the router? Or something along
those lines, if memory serves me right (pun intended). I believe the
2600s and 3600s supported the command. Dedicating a large amount to
iomem might reduce the CPU memory to that which the router would find
insufficient.
Chuck Church
Principal Network Engineer, CCIE #8776
Harris Information Technology Services
EDS Contractor - Navy Marine Corps Intranet (NMCI)
1210 N. Parker Rd. | Greenville, SC 29609
Office: 864-335-9473 | Cell: 864-266-3978
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Steven Pfister
Sent: Friday, May 30, 2008 12:36 PM
To: [email protected]
Subject: [c-nsp] Memory requirements in Cisco Feature Navigator
I've got an IOS (12.3(14)T7) that I'm trying to load onto a 3640 router.
According to the feature navigator, it should require 96mb DRAM, 32mb
flash, which this router has. But, when I try to boot it, it gives me an
out-of-memory error and crashes during boot. Is the FN wrong, or is
there something I can do?
Thanks!
Steve Pfister
Technical Coordinator,
The Office of Information Technology
Dayton Public Schools
115 S. Ludlow St.
Dayton, OH 45402
Office (937) 542-3149
Cell (937) 673-6779
Direct Connect: 137*131747*8
Email [EMAIL PROTECTED]
_______________________________________________
cisco-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
_______________________________________________
cisco-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
_______________________________________________
cisco-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
------------------------------
Message: 2
Date: Fri, 30 May 2008 14:22:22 -0500
From: "Church, Charles" <[EMAIL PROTECTED]>
Subject: Re: [c-nsp] Memory requirements in Cisco Feature Navigator
To: "Steven Pfister" <[EMAIL PROTECTED]>,
<[email protected]>
Message-ID:
<[EMAIL PROTECTED]>
Content-Type: text/plain; charset="us-ascii"
Hmmm. Running out of ideas. What if you take out the NMs, and then try
to boot it? If you can get it to come up, get a 'sho mem', and see how
much is left. It could be an error on the FN.
Chuck
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Steven Pfister
Sent: Friday, May 30, 2008 3:08 PM
To: [email protected]
Subject: Re: [c-nsp] Memory requirements in Cisco Feature Navigator
It looks like without the command it defaults to 15%. Adding a
'memory-size iomem 5' doesn't seem to do too much... I think it still
defaults to 15%
Steve Pfister
Technical Coordinator,
The Office of Information Technology
Dayton Public Schools
115 S. Ludlow St.
Dayton, OH 45402
Office (937) 542-3149
Cell (937) 673-6779
Direct Connect: 137*131747*8
Email [EMAIL PROTECTED]
>>> "Church, Charles" <[EMAIL PROTECTED]> 5/30/2008 1:50 PM >>>
See if it works without the command. Bypassing the config via the
config register might do it too.
Chuck
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Steven Pfister
Sent: Friday, May 30, 2008 1:42 PM
To: [email protected]
Subject: Re: [c-nsp] Memory requirements in Cisco Feature Navigator
It's an IP plus image. It looks like there is a 'memory-size iomem 15'
in the config.
--Steve
Steve Pfister
Technical Coordinator,
The Office of Information Technology
Dayton Public Schools
115 S. Ludlow St.
Dayton, OH 45402
Office (937) 542-3149
Cell (937) 673-6779
Direct Connect: 137*131747*8
Email [EMAIL PROTECTED]
>>> "Church, Charles" <[EMAIL PROTECTED]> 5/30/2008 12:48 PM >>>
It's possible that FN is wrong. What feature set are you using? Do you
have 'memory-size iomem' configured on the router? Or something along
those lines, if memory serves me right (pun intended). I believe the
2600s and 3600s supported the command. Dedicating a large amount to
iomem might reduce the CPU memory to that which the router would find
insufficient.
Chuck Church
Principal Network Engineer, CCIE #8776
Harris Information Technology Services
EDS Contractor - Navy Marine Corps Intranet (NMCI)
1210 N. Parker Rd. | Greenville, SC 29609
Office: 864-335-9473 | Cell: 864-266-3978
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Steven Pfister
Sent: Friday, May 30, 2008 12:36 PM
To: [email protected]
Subject: [c-nsp] Memory requirements in Cisco Feature Navigator
I've got an IOS (12.3(14)T7) that I'm trying to load onto a 3640 router.
According to the feature navigator, it should require 96mb DRAM, 32mb
flash, which this router has. But, when I try to boot it, it gives me an
out-of-memory error and crashes during boot. Is the FN wrong, or is
there something I can do?
Thanks!
Steve Pfister
Technical Coordinator,
The Office of Information Technology
Dayton Public Schools
115 S. Ludlow St.
Dayton, OH 45402
Office (937) 542-3149
Cell (937) 673-6779
Direct Connect: 137*131747*8
Email [EMAIL PROTECTED]
_______________________________________________
cisco-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
_______________________________________________
cisco-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
_______________________________________________
cisco-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
_______________________________________________
cisco-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
------------------------------
Message: 3
Date: Fri, 30 May 2008 15:42:06 -0400
From: "Steven Pfister" <[EMAIL PROTECTED]>
Subject: Re: [c-nsp] Memory requirements in Cisco Feature Navigator
To: "Charles Church" <[EMAIL PROTECTED]>,
<[email protected]>
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=US-ASCII
Yes, it does come up without the NMs. What do I look at in 'sho mem'?
Steve Pfister
Technical Coordinator,
The Office of Information Technology
Dayton Public Schools
115 S. Ludlow St.
Dayton, OH 45402
Office (937) 542-3149
Cell (937) 673-6779
Direct Connect: 137*131747*8
Email [EMAIL PROTECTED]
>>> "Church, Charles" <[EMAIL PROTECTED]> 5/30/2008 3:22 PM >>>
Hmmm. Running out of ideas. What if you take out the NMs, and then try
to boot it? If you can get it to come up, get a 'sho mem', and see how
much is left. It could be an error on the FN.
Chuck
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Steven Pfister
Sent: Friday, May 30, 2008 3:08 PM
To: [email protected]
Subject: Re: [c-nsp] Memory requirements in Cisco Feature Navigator
It looks like without the command it defaults to 15%. Adding a
'memory-size iomem 5' doesn't seem to do too much... I think it still
defaults to 15%
Steve Pfister
Technical Coordinator,
The Office of Information Technology
Dayton Public Schools
115 S. Ludlow St.
Dayton, OH 45402
Office (937) 542-3149
Cell (937) 673-6779
Direct Connect: 137*131747*8
Email [EMAIL PROTECTED]
>>> "Church, Charles" <[EMAIL PROTECTED]> 5/30/2008 1:50 PM >>>
See if it works without the command. Bypassing the config via the
config register might do it too.
Chuck
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Steven Pfister
Sent: Friday, May 30, 2008 1:42 PM
To: [email protected]
Subject: Re: [c-nsp] Memory requirements in Cisco Feature Navigator
It's an IP plus image. It looks like there is a 'memory-size iomem 15'
in the config.
--Steve
Steve Pfister
Technical Coordinator,
The Office of Information Technology
Dayton Public Schools
115 S. Ludlow St.
Dayton, OH 45402
Office (937) 542-3149
Cell (937) 673-6779
Direct Connect: 137*131747*8
Email [EMAIL PROTECTED]
>>> "Church, Charles" <[EMAIL PROTECTED]> 5/30/2008 12:48 PM >>>
It's possible that FN is wrong. What feature set are you using? Do you
have 'memory-size iomem' configured on the router? Or something along
those lines, if memory serves me right (pun intended). I believe the
2600s and 3600s supported the command. Dedicating a large amount to
iomem might reduce the CPU memory to that which the router would find
insufficient.
Chuck Church
Principal Network Engineer, CCIE #8776
Harris Information Technology Services
EDS Contractor - Navy Marine Corps Intranet (NMCI)
1210 N. Parker Rd. | Greenville, SC 29609
Office: 864-335-9473 | Cell: 864-266-3978
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Steven Pfister
Sent: Friday, May 30, 2008 12:36 PM
To: [email protected]
Subject: [c-nsp] Memory requirements in Cisco Feature Navigator
I've got an IOS (12.3(14)T7) that I'm trying to load onto a 3640 router.
According to the feature navigator, it should require 96mb DRAM, 32mb
flash, which this router has. But, when I try to boot it, it gives me an
out-of-memory error and crashes during boot. Is the FN wrong, or is
there something I can do?
Thanks!
Steve Pfister
Technical Coordinator,
The Office of Information Technology
Dayton Public Schools
115 S. Ludlow St.
Dayton, OH 45402
Office (937) 542-3149
Cell (937) 673-6779
Direct Connect: 137*131747*8
Email [EMAIL PROTECTED]
_______________________________________________
cisco-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
_______________________________________________
cisco-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
_______________________________________________
cisco-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
_______________________________________________
cisco-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
_______________________________________________
cisco-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
------------------------------
Message: 4
Date: Fri, 30 May 2008 12:48:05 -0700 (PDT)
From: Curtis Doty <[EMAIL PROTECTED]>
Subject: Re: [c-nsp] High CPU load on Catalyst 3550
To: Cisco NSPs <[email protected]>
Message-ID: <[EMAIL PROTECTED]>
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
11:07am Andrew Degtiariov said:
>
> Unfortunately nor cisco.com nor Google can't give me answer what is a
> MRD process :-(
> Anybody known what it this?
WAG: Multicast Router Daemon?
# show run | incl gmp
.../C
------------------------------
Message: 5
Date: Fri, 30 May 2008 17:32:12 -0700
From: "Andrew Gristina" <[EMAIL PROTECTED]>
Subject: Re: [c-nsp] Overlapping NAT subnets and PPTP
To: [EMAIL PROTECTED]
Cc: [email protected]
Message-ID:
<[EMAIL PROTECTED]>
Content-Type: text/plain; charset=ISO-8859-1
One: most people use a real name on the list.
Two: PPTP and PAT don't really mix. Read up on the PPTP protocol. If
not just try a whole bunch of PPTP clients behind a PAT. I don't
really value the PPTP protocol very highly.
Three: IPSec can do double NAT or double PAT (disguise the same
network at both ends)
Four: VPN for B2B implementations are better off if everyone insists
on publics for the interesting traffic networks, then each network
owner can NAT at their "demarc".
These are all things that are probably in the list archive.
I hope you got more replies than this, and in a kinder gentler tone,
but I'm in a hurry and didn't see anyone reply to you.
On Thu, May 29, 2008 at 8:50 AM, <[EMAIL PROTECTED]> wrote:
>
> I have a customer that has a 2811 with a fairly complex NAT VPN
> configuration (an existing GRE tunnel, a bunch of static NAT mappings to it,
> etc).
>
> We just added a PPTP to it and ran into an overlapping subnet issue with it.
> They have over a hundred internal hosts on 192.168.1.0/24 and of course,
> many people who PPTP into it are using that same RFC1918 space on their LAN
> (it's hard coded into my Verizon router, for example). Since the incoming
> PPTP connections need to talk to those hosts, there is obviously a conflict.
>
> Cisco TAC's position was that they need to renumber to eliminate the
> conflict. That may be true, but we came up with an idea that seems like it
> should work as an alternative. That is to use something like:
>
> ip nat source static 192.168.1.20 10.3.3.20
> or
> ip nat outside source static 192.168.1.20 10.3.3.20
>
> to "fool" the incoming PPTP connected hosts. To some extent, it works. The
> incoming connections can now ping 10.3.3.20 and get responses (they could
> not ping 192.168.1.20). However, any attempt to connect to any TCP port on
> that host results in a "connection refused".
>
> Is this just a dead-end for this kludge, or is something else needed? Has
> anyone else succeeded with it? The customer just wants to avoid renumbering
> if possible (for now), so I just want to make sure that if this kludge
> doesn't work, I can explain why, or make it work if possible.
>
> Thanks in Advance!
>
> James Smallacombe PlantageNet, Inc. CEO and Janitor
> [EMAIL PROTECTED]
> http://3.am
> =========================================================================
> _______________________________________________
> cisco-nsp mailing list [email protected]
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>
------------------------------
Message: 6
Date: Fri, 30 May 2008 17:42:24 -0700
From: "Andrew Gristina" <[EMAIL PROTECTED]>
Subject: Re: [c-nsp] Single strand SMF 10GbE
To: [EMAIL PROTECTED]
Cc: MKS <[EMAIL PROTECTED]>, [email protected]
Message-ID:
<[EMAIL PROTECTED]>
Content-Type: text/plain; charset=ISO-8859-1
On Thu, May 29, 2008 at 9:13 AM, Mark Tinka <[EMAIL PROTECTED]> wrote:
> On Thursday 29 May 2008, MKS wrote:
>
>> Hello List
>>
>> Is some vendor out there that offers single strand SMF
>> 10GbE (X2/xenpak/whatever).
>> Does someone know if this is on cisco's roadmap?
>
> Cisco aren't doing 10Gbps yet - they are doing mux'ed 1Gbps
> links over CWDM (can use LACP to connect up to 4Gbps):
>
> http://www.cisco.com/en/US/prod/collateral/modules/ps5455/ps6575/product_data_sheet0900aecd8029d01b.html
>
> For 10Gbps, consider the following vendors:
>
> * MRV
> * Transition Networks
> * Ciena (acquired WWP)
>
> Cheers,
>
> Mark.
Wow. I must be imagining all this 10Gb Ethernet Cisco gear I'm looking
at. Nexus, 6500, etc. etc. DId you mean they aren't doing 10G CWDM
or DWDM?
The OP used 10GbE, but that could have been in error.
------------------------------
Message: 7
Date: Fri, 30 May 2008 22:09:12 -0500
From: Richard A Steenbergen <[EMAIL PROTECTED]>
Subject: Re: [c-nsp] Single strand SMF 10GbE
To: Andrew Gristina <[EMAIL PROTECTED]>
Cc: [email protected], MKS <[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=us-ascii
On Fri, May 30, 2008 at 05:42:24PM -0700, Andrew Gristina wrote:
> Wow. I must be imagining all this 10Gb Ethernet Cisco gear I'm looking
> at. Nexus, 6500, etc. etc. DId you mean they aren't doing 10G CWDM
> or DWDM?
>
> The OP used 10GbE, but that could have been in error.
The OP was asking about a single-strand 10GE product, not just "any" 10GE
product, or even ordinary 10G DWDM products. Basically they're looking for
a 10GE version of 1000BASE-BX, an integrated mux+transceiver in a standard
pluggable package with a sigle strand connector, as desribed here:
http://www.cisco.com/en/US/prod/collateral/modules/ps5455/ps6577/product_data_sheet0900aecd8033f885.html
Everyone and their mother sells 10G DWDM gear (no CWDM though, probably
because dealing with the dispersion of a wider band signal at 10G speeds
is far harder than transmitting a narrow and stable 100GHz signal), but
that has nothing to do with what they wanted.
Also note as always that Cisco doesn't actually make any of this gear, nor
do they do anything even vaguely "different" or "interesting" with it.
This is all just trivial tuned optics and passive filters that you can get
from anyone (at better densities, with more channels, and with better
optical characteristics too), all Cisco does is slap their logo on it and
mark it up 10x.
--
Richard A Steenbergen <[EMAIL PROTECTED]> http://www.e-gerbil.net/ras
GPG Key ID: 0xF8B12CBC (7535 7F59 8204 ED1F CC1C 53AF 4C41 5ECA F8B1 2CBC)
------------------------------
_______________________________________________
cisco-nsp mailing list
[email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
End of cisco-nsp Digest, Vol 66, Issue 114
******************************************
_______________________________________________
cisco-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
