<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
..shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
..MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Using the Cisco Media Convergence Server Network Teaming Driver
with Operating System Versions 2000.4.3 and 2000.4.3a<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><a
href="http://www.cisco.com/en/US/products/hw/voiceapp/ps378/prod_installation_guide09186a00806a476f.html">http://www.cisco.com/en/US/products/hw/voiceapp/ps378/prod_installation_guide09186a00806a476f.html</a><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>The above document “strongly suggests NFT” in Step6,
the default is Auto. <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>I don’t see anything that states Auto is unsupported by
Cisco. I would think being able to use two NICS @ 1000/Full would
be better than one @ 1000/Full -jason<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>In Auto mode connected to a Catalyst 3500/4500/6500 with default
settings Auto will select Transmit Load Balancing with Fault Tolerance (TLB) based
upon the HP Whitepaper below. If you go into Control Panel > Networks > Teaming
Interface > Properties> HP Network Configuration Utility > Select HP
Network Team > Properties > Information it will shows the actual “Current
Mode” that Auto selected. I went into a OS2000-4-4a-SR6 and found they
were Transmit Load Balancing with Fault Tolerance (TLB) and have been in
production for several years with no issues relating to the NIC teaming. IPCC
Express application isn’t supported with NIC teaming and does have
problems.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:9.5pt;font-family:"Arial","sans-serif"'><a
href="javascript:openExternal('ftp://ftp.compaq.com/pub/products/servers/networking/TeamingWP.pdf')">ftp://ftp.compaq.com/pub/products/servers/networking/TeamingWP.pdf
</a><o:p></o:p></span></p>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<div class=MsoNormal align=center style='text-align:center'>
<hr size=2 width="100%" align=center>
</div>
<p class=MsoNormal style='margin-bottom:12.0pt'><b><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'> Clouse, Chris
[mailto:chris.clouse@berbee.com] <br>
<b>Sent:</b> Saturday, May 19, 2007 1:40 PM<br>
<b>To:</b> Miller, Steve<br>
<b>Subject:</b> RE: [cisco-voip] Re-enabled NIC on the Call Manager Has
Prevented Access to the System - Please Help!</span><o:p></o:p></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>The NIC’s should not be teamed. The only method that
is supported is Fault Tolerance Only. Enable this mode, connect both
cables, and try again.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div>
<p class=MsoNormal><span style='font-size:10.5pt;font-family:Consolas;
color:#1F497D'>Christopher Clouse, CCNP CCDP CCVP MCP Network+<o:p></o:p></span></p>
</div>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
cisco-voip-bounces@puck.nether.net [mailto:cisco-voip-bounces@puck.nether.net] <b>On
Behalf Of </b>Miller, Steve<br>
<b>Sent:</b> Saturday, May 19, 2007 12:16 PM<br>
<b>To:</b> cisco-voip@puck.nether.net<br>
<b>Subject:</b> [cisco-voip] Re-enabled NIC on the Call Manager Has Prevented
Access to the System - Please Help!<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>We have NICs in a Call Manager Subscriber in NY and one had been
disabled for a long time. I was told by an expert engineer (who actually
was the architect or our system) that all of the settings for the cards were
correct and that there was probably a cable unplugged. When I got to the
site, there was a cable unplugged so I replaced the cable and then re-enabled
the card that corresponded to that port. At that point, we rec'd
errors in the event log that the system could not communicate with the NTP
server and now we cannot connect to the Call Manager via RDP or by
web interface programming. All calls are being processed and there
seems to be no current user issue, but I need to know if I should simply
disable the connection again and troubleshoot or if there is something in the
teaming NIC card setup that needs to be changed. I have never messed with
this before and I want to fix it, but I don't want to interfere with the phone
service. I'm sure that this is a simple issue, but I don't want a
misstep. Please let me know if you are familiar with this. Thank
you!</span><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
<p><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:blue'>Steve
Miller<br>
Telecom Engineer<br>
Dickstein Shapiro LLP<br>
1825 Eye Street NW | Washington, DC 20006<br>
Tel (202) 420-3370 Fax (202)-330-5607<br>
</span><a href="mailto:millers@dicksteinshapiro.com"><span style='font-size:
10.0pt;font-family:"Arial","sans-serif"'>millers@dicksteinshapiro.com</span></a><span
style='font-size:10.0pt;font-family:"Arial","sans-serif";color:blue'> </span><o:p></o:p></p>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
<pre>--------------------------------------------------------<o:p></o:p></pre><pre>This e-mail message and any attached files are confidential and are intended solely for the use of the addressee(s) named above. This communication may contain material protected by attorney-client, work product, or other privileges. If you are not the intended recipient or person responsible for delivering this confidential communication to the intended recipient, you have received this communication in error, and any review, use, dissemination, forwarding, printing, copying, or other distribution of this e-mail message and any attached files is strictly prohibited. Dickstein Shapiro reserves the right to monitor any communication that is created, received, or sent on its network. If you have received this confidential communication in error, please notify the sender immediately by reply e-mail message and permanently delete the original message. <o:p></o:p></pre><pre><o:p> </o:p></pre><pre>To reply to our email administrator directly, send an email to postmaster@dicksteinshapiro.com<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Dickstein Shapiro LLP<o:p></o:p></pre><pre>http://www.DicksteinShapiro.com<o:p></o:p></pre><pre>==============================================================================<o:p></o:p></pre><pre>--------------------------------------------------------<o:p></o:p></pre><pre>This e-mail message and any attached files are confidential and are intended solely for the use of the addressee(s) named above. This communication may contain material protected by attorney-client, work product, or other privileges. If you are not the intended recipient or person responsible for delivering this confidential communication to the intended recipient, you have received this communication in error, and any review, use, dissemination, forwarding, printing, copying, or other distribution of this e-mail message and any attached files is strictly prohibited. Dickstein Shapiro reserves the right to monitor any communication that is created, received, or sent on its network. If you have received this confidential communication in error, please notify the sender immediately by reply e-mail message and permanently delete the original message. <o:p></o:p></pre><pre><o:p> </o:p></pre><pre>To reply to our email administrator directly, send an email to postmaster@dicksteinshapiro.com<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Dickstein Shapiro LLP<o:p></o:p></pre><pre>http://www.DicksteinShapiro.com<o:p></o:p></pre><pre>==============================================================================<o:p></o:p></pre></div>
</body>
</html>
<HTML><BODY><P><hr size=1></P>
<P><STRONG>
Disclaimer:
This e-mail communication and any attachments may contain confidential and privileged information and is for use by the designated addressee(s) named above only. If you are not the intended addressee, you are hereby notified that you have received this communication in error and that any use or reproduction of this email or its contents is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by replying to this message and deleting it from your computer. Thank you.
</STRONG></P></BODY></HTML>