<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2900.3395" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2>CCIE is still referring to 6608s? wow.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Configuration is simple. When it works. I've had to
devise some interesting troublshooting steps in order to make them properly
register. And the TAC will come back and say we won't help you unless ALL your
6608 ports are registered. Which I think is a load of crock. <FONT face=Arial
size=2>I've had to disable the port first, after, change the vlan before, after,
etc. </FONT></FONT><FONT face=Arial size=2>Basically, the config statement looks
something like this:</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>set port voice interface
<mod>/<port> dhcp disable <ipaddr> <mask>
vlan <vlan#> tftp <tftpipaddr> gateway
<gatewayipaddr></FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>The config statement is the same regardless of
gateway, transcoding or conferencing. It downloads the appropriate software and
config from the TFTP server.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>The important thing to note is that the device
resets itself twice and to not do anything until that second reset has come
by.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2> </DIV>
<DIV><BR></DIV></FONT>
<DIV><FONT face=Arial
size=2>Lelio<BR>--------------------------------------------------------------------------------<BR>Lelio
Fulgenzi, B.A.<BR>Senior Analyst (CCS) * University of Guelph * Guelph, Ontario
N1G 2W1<BR>(519) 824-4120 x56354 (519) 767-1060 FAX
(JNHN)<BR>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
<BR>...seen on a Geek Squad patch cord: "While it is the same length, this 7'
crossover cable<BR>is not regulation issue for most competitive Manhattan double
dutch leagues.</FONT></DIV>
<BLOCKQUOTE dir=ltr
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV
style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B>
<A title=jeff@cia.net href="mailto:jeff@cia.net">Jeff Garvas</A> </DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A title=lelio@uoguelph.ca
href="mailto:lelio@uoguelph.ca">Lelio Fulgenzi</A> </DIV>
<DIV style="FONT: 10pt arial"><B>Cc:</B> <A title=cisco-voip@puck.nether.net
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A> </DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Monday, September 08, 2008 10:50
AM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> Re: [cisco-voip] VoIP Lab
WS-6608X blade</DIV>
<DIV><BR></DIV>
<DIV dir=ltr><BR>Sorry I should have been more clear. I'm building
out a CCIE lab and trying to follow that blueprint for a handful of people
here to use the equipment to prepare to take the lab exam. This
isn't for production use at all.<BR><BR>There are some labs that use the 6608X
for a conference bridge, a gateway, and to register its DSP resources with
Call Manager. They seem simple but I'm doing my best to build the lab
out entirely. I guess based on what I originally thought and what
your'e saying about the CMM blades I'm better off trying to find a 6608X
someone might not be using and willing to trade/swap or
sell.<BR><BR>-Jeff<BR><BR><BR>
<DIV class=gmail_quote>On Mon, Sep 8, 2008 at 9:35 AM, Lelio Fulgenzi <SPAN
dir=ltr><<A
href="mailto:lelio@uoguelph.ca">lelio@uoguelph.ca</A>></SPAN> wrote:<BR>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid">
<DIV bgcolor="#ffffff">
<DIV><FONT face=Arial size=2>The 6608 blades are EOL. If you are looking at
learning new stuff, I'd stick with ISRs. You could probably get a CMM but
I'm not sure they're any more long term than the 6608s. I don't think
they've been EOL'd but I wouldn't be surprised with the limited memory etc.
If you look at the cost of outfitting a Catalyst switch with CMM blades it's
much more expensive than a bunch of VG224s and an ISR. And that's not
including the chasis either.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>The only thing the 6608s blades were great for
was that you could configure each individually for a seperate cluster. The
only way you can do that with ISRs or CMMs as far as I know is to use H323
gateways. Then again, people are moving towards H323 gateways and away from
MGCP for a number of reasons too. Which is another reason they 6608 blade
might not serve you well.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial
size=2>Lelio<BR>--------------------------------------------------------------------------------<BR>Lelio
Fulgenzi, B.A.<BR>Senior Analyst (CCS) * University of Guelph * Guelph,
Ontario N1G 2W1<BR>(519) 824-4120 x56354 (519) 767-1060 FAX
(JNHN)<BR>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
<BR>...seen on a Geek Squad patch cord: "While it is the same length, this
7' crossover cable<BR>is not regulation issue for most competitive Manhattan
double dutch leagues.</FONT></DIV>
<BLOCKQUOTE
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: rgb(0,0,0) 2px solid; MARGIN-RIGHT: 0px">
<DIV>
<DIV></DIV>
<DIV class=Wj3C7c>
<DIV
style="FONT: 10pt arial; font-size-adjust: none; font-stretch: normal">-----
Original Message ----- </DIV>
<DIV
style="BACKGROUND: rgb(228,228,228); FONT: 10pt arial; font-size-adjust: none; font-stretch: normal; moz-background-clip: -moz-initial; moz-background-origin: -moz-initial; moz-background-inline-policy: -moz-initial"><B>From:</B>
<A title=jeff@cia.net href="mailto:jeff@cia.net" target=_blank>Jeff
Garvas</A> </DIV>
<DIV
style="FONT: 10pt arial; font-size-adjust: none; font-stretch: normal"><B>To:</B>
<A title=cisco-voip@puck.nether.net
href="mailto:cisco-voip@puck.nether.net"
target=_blank>cisco-voip@puck.nether.net</A> </DIV>
<DIV
style="FONT: 10pt arial; font-size-adjust: none; font-stretch: normal"><B>Sent:</B>
Monday, September 08, 2008 9:04 AM</DIV>
<DIV
style="FONT: 10pt arial; font-size-adjust: none; font-stretch: normal"><B>Subject:</B>
[cisco-voip] VoIP Lab WS-6608X blade</DIV>
<DIV><BR></DIV>
<DIV dir=ltr><BR>I've been working on building out a VoIP lab and I have
about 95% of the hardware. The blueprint calls for a 6608X blade
which is no longer available unless you can find one used.<BR><BR>I'm
looking for opinions from those of you who may have begun studying the
lab. Would it make sense to hunt one of these down used or to use
the recommended replacement cards? I'm thinking
finding a used card might be more economical.<BR><BR>In fact, if anyone
has a 6608X blade available that they'd like to trade I have a other
blades available I could swap in a trade. All I ask is that it
works. If you're interested in a swap contact me off
list.<BR><BR>-Jeff <BR><BR><BR><BR><BR></DIV></DIV></DIV>
<P></P>
<HR>
<P></P>_______________________________________________<BR>cisco-voip
mailing list<BR><A href="mailto:cisco-voip@puck.nether.net"
target=_blank>cisco-voip@puck.nether.net</A><BR><A
href="https://puck.nether.net/mailman/listinfo/cisco-voip"
target=_blank>https://puck.nether.net/mailman/listinfo/cisco-voip</A><BR></BLOCKQUOTE></DIV></BLOCKQUOTE></DIV><BR></DIV></BLOCKQUOTE></BODY></HTML>