|
Home > Archive > Voice over IP Cisco > May 2007 > Re-enabled NIC on the Call Manager Has Prevented
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Re-enabled NIC on the Call Manager Has Prevented
|
|
| Miller, Steve 2007-05-19, 1:11 pm |
| 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!
Steve Miller
Telecom Engineer
Dickstein Shapiro LLP
1825 Eye Street NW | Washington, DC 20006
Tel (202) 420-3370 Fax (202)-330-5607
millers@dicksteinshapiro.com <mailto:millers@dicksteinshapiro.com>
--------------------------------------------------------
This e-mail message and any attached files are confidential and are intendedsolely for the use of the addressee(s) named above. This communication maycontain material protected by attorney-client, work product, or other privileges. If you are not the intended recipient or person responsible fordelivering 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 thise-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-mailmessage and permanently delete the original message.
To reply to our email administrator directly, send an email to postmaster@dicksteinshapiro.com
Dickstein Shapiro LLP
http://www.DicksteinShapiro.com
========================================
======================================
| |
| Miller, Steve 2007-05-19, 1:11 pm |
| When I look at the team properties, it says "Network Fault Tolerance
Only with Preference Order". What else do I need to check? Would
simply disabling the 2nd NIC again temporarily fix the problem? There
has been no adjustment of the cards (programming) at all at this point.
Steve Miller
Telecom Engineer
Dickstein Shapiro LLP
1825 Eye Street NW | Washington, DC 20006
Tel (202) 420-3370 Fax (202)-330-5607
millers@dicksteinshapiro.com <mailto:millers@dicksteinshapiro.com>
________________________________
From: Clouse, Chris [mailto:chris.clouse@berbee.com]
Sent: Saturday, May 19, 2007 1:40 PM
To: Miller, Steve
Subject: RE: [cisco-voip] Re-enabled NIC on the Call Manager Has
Prevented Access to the System - Please Help!
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.
Christopher Clouse, CCNP CCDP CCVP MCP Network+
From: cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] On Behalf Of Miller, Steve
Sent: Saturday, May 19, 2007 12:16 PM
To: cisco-voip@puck.nether.net
Subject: [cisco-voip] Re-enabled NIC on the Call Manager Has Prevented
Access to the System - Please Help!
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!
Steve Miller
Telecom Engineer
Dickstein Shapiro LLP
1825 Eye Street NW | Washington, DC 20006
Tel (202) 420-3370 Fax (202)-330-5607
millers@dicksteinshapiro.com <mailto:millers@dicksteinshapiro.com>
--------------------------------------------------------
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.
To reply to our email administrator directly, send an email to
postmaster@dicksteinshapiro.com
Dickstein Shapiro LLP
http://www.DicksteinShapiro.com
========================================
================================
======
--------------------------------------------------------
This e-mail message and any attached files are confidential and are intendedsolely for the use of the addressee(s) named above. This communication maycontain material protected by attorney-client, work product, or other privileges. If you are not the intended recipient or person responsible fordelivering 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 thise-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-mailmessage and permanently delete the original message.
To reply to our email administrator directly, send an email to postmaster@dicksteinshapiro.com
Dickstein Shapiro LLP
http://www.DicksteinShapiro.com
========================================
======================================
| |
| Jason Aarons \(US\) 2007-05-19, 7:11 pm |
| Using the cisco Media Convergence Server Network Teaming Driver with
Operating System Versions 2000.4.3 and 2000.4.3a
http://www.cisco.com/en/US/products...d_installation_
guide09186a00806a476f.html
The above document "strongly suggests NFT" in Step6, the default is
Auto.
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
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.
ftp://ftp.compaq.com/pub/products/s...g/TeamingWP.pdf
<java script:openExternal('ftp://ftp.compaq.com/pub/products/servers/netw
orking/TeamingWP.pdf')>
________________________________
From: Clouse, Chris [mailto:chris.clouse@berbee.com]
Sent: Saturday, May 19, 2007 1:40 PM
To: Miller, Steve
Subject: RE: [cisco-voip] Re-enabled NIC on the Call Manager Has
Prevented Access to the System - Please Help!
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.
Christopher Clouse, CCNP CCDP CCVP MCP Network+
From: cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] On Behalf Of Miller, Steve
Sent: Saturday, May 19, 2007 12:16 PM
To: cisco-voip@puck.nether.net
Subject: [cisco-voip] Re-enabled NIC on the Call Manager Has Prevented
Access to the System - Please Help!
We haveNICs in a Call Manager Subscriber in NY and one had been
disabled fora 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 werecorrect 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
Idon'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!
Steve Miller
Telecom Engineer
Dickstein Shapiro LLP
1825 Eye Street NW | Washington, DC 20006
Tel (202) 420-3370 Fax (202)-330-5607
millers@dicksteinshapiro.com <mailto:millers@dicksteinshapiro.com>
--------------------------------------------------------
This e-mail message and any attached files are confidential andare
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 filesis 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.
To reply to our email administrator directly, send an email to
postmaster@dicksteinshapiro.com
Dickstein Shapiro LLP
http://www.DicksteinShapiro.com
========================================
================================
======
--------------------------------------------------------
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 communicationin error, please notify
the sender immediately by reply e-mail message and permanently delete
the original message.
To replyto our email administrator directly, send an email to
postmaster@dicksteinshapiro.com
Dickstein Shapiro LLP
http://www.DicksteinShapiro.com
========================================
================================
======
-----------------------------------------
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 youhave 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.
| |
| Ryan Ratliff 2007-05-21, 1:12 pm |
| My recommendation has always been to use NFT only, never load balancing.
-Ryan
On May 19, 2007, at 3:36 PM, Jason Aarons ((US)) wrote:
Using the cisco Media Convergence Server Network Teaming Driver with =
Operating System Versions 2000.4.3 and 2000.4.3a
http://www.cisco.com/en/US/products/hw/voiceapp/ps378/ =
prod_installation_guide09186a00806a476f.html
The above document =93strongly suggests NFT=94 in Step6, the default is =
Auto.
I don=92t 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
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 =93Current Mode=94 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=92t supported with NIC teaming and does have =
problems.
ftp://ftp.compaq.com/pub/products/s...g/TeamingWP.pdf
From: Clouse, Chris [mailto:chris.clouse@berbee.com]
Sent: Saturday, May 19, 2007 1:40 PM
To: Miller, Steve
Subject: RE: [cisco-voip] Re-enabled NIC on the Call Manager Has =
Prevented Access to the System - Please Help!
The NIC=92s should not be teamed. The only method that is supported is =
Fault Tolerance Only. Enable this mode, connect both cables, and try =
again.
Christopher Clouse, CCNP CCDP CCVP MCP Network+
From: cisco-voip-bounces@puck.nether.net [mailto:cisco-voip- =
bounces@puck.nether.net] On Behalf Of Miller, Steve
Sent: Saturday, May 19, 2007 12:16 PM
To: cisco-voip@puck.nether.net
Subject: [cisco-voip] Re-enabled NIC on the Call Manager Has =
Prevented Access to the System - Please Help!
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!
Steve Miller
Telecom Engineer
Dickstein Shapiro LLP
1825 Eye Street NW | Washington, DC 20006
Tel (202) 420-3370 Fax (202)-330-5607
millers@dicksteinshapiro.com
--------------------------------------------------------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. To reply to our =
email administrator directly, send an email to =
postmaster@dicksteinshapiro.com Dickstein Shapiro LLPhttp:// =
www.DicksteinShapiro. com=3D=3D=3D=...3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D------------------------------------------ =
--------------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. To reply to our email administrator directly, send =
an email to postmaster@dicksteinshapiro.com Dickstein Shapiro =
LLPhttp:// =
www.DicksteinShapiro. com=3D=3D=3D=...3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D
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.
________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
|
|
|
|
|