From: Michael J. Doherty (Z0rand3r@hotmail.com)
Date: Wed Jan 15 2003 - 11:47:28 GMT-3
Based on these comments, "The servers in Table 5 contain two network
interface cards (NIC), but Cisco CallManager supports only one NIC. When you
connect the server to the network, use the NIC connector listed in the table
because the other NIC is disabled during the installation.", from this page
(
http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_installation_guide
09186a00800f934d.html ) and a recent conference with Cisco engineers, using
both NICs (even with Compaq's Teaming Utility) is not supported by TAC. If
TAC logs into your box remotely, and finds a non-supported configuration,
they will require you to rebuild the CCM from scratch before providing any
assistance. We specifically asked them about redundant NICs, among other
changes, when we received that answer.
Just thought I should pass that on.
Mike
----- Original Message -----
From: "Yigit Zorlu" <yzorlu@tepum.com.tr>
To: "Armand D" <ciscoworks2001@yahoo.com>; "Michael J. Doherty"
<Z0rand3r@hotmail.com>; <ccielab@groupstudy.com>
Sent: Wednesday, January 15, 2003 01:38
Subject: RE: Call Manager redundancy
> Callmanager NIC redundancy is possible. Team utility of Compaq server
solves the problem. It creates a new card and you give IP address to that
card. In practice this new one is a virtual NIC that teams both physical
NICs. If you connect NICs to different switches you will have a redundant
Callmanager in case of a NIC failure or switch failure. I'm sure IBM servers
have this feature as well.
>
>
> HTH
>
> Yigit
>
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
> Armand D
> Sent: Monday, January 13, 2003 9:22 PM
> To: Michael J. Doherty; ccielab@groupstudy.com
> Subject: Re: Call Manager redundancy
>
>
> This helps alot.Thank you all for your help.
>
> Regards,
>
> Armand
>
> --- "Michael J. Doherty" <Z0rand3r@hotmail.com>
> wrote: > CallManager, during the software load, will
> disable
> > any NIC it finds, beyond
> > NIC 1.
> >
> > As for Unity...
> >
> > Unity 3.1 does not permit multiple NICs (
> >
>
http://www.cisco.com/warp/public/788/AVVID/unity31-inst-guide-win2k-bl.html
> >
> > )
> > Unity 4.0 permits Multiple NICs in a failover format
> > (
> >
>
http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/relnote/cu401r
> > n.htm#xtocid69 ).
> >
> > HTH
> >
> > Sincerely,
> >
> > Michael J. Doherty
> >
> > ----- Original Message -----
> > From: "Armand D" <ciscoworks2001@yahoo.com>
> > To: <ccielab@groupstudy.com>
> > Sent: Monday, January 13, 2003 12:05
> > Subject: Call Manager redundancy
> >
> >
> > > Hi,
> > >
> > > Does anyone know if I can use two NICs on a call
> > > manager server or unity server to ensure
> > redundancy?
> > > Is this configuration supported in the event that
> > a
> > > switch fails or a NIC fails? How can I do this?
> > Any
> > > info would be appreciated.
> > >
> > > Armand
> > >
> > > http://movies.yahoo.com.au - Yahoo! Movies
> > > - What's on at your local cinema?
> > > .
> > .
> >
> __________________________________________________________________
> > To unsubscribe from the CCIELAB list, send a message
> > to
> > majordomo@groupstudy.com with the body containing:
> > unsubscribe ccielab
>
> http://movies.yahoo.com.au - Yahoo! Movies
> - What's on at your local cinema?
> .
> .
.
This archive was generated by hypermail 2.1.4 : Sat Feb 01 2003 - 07:33:49 GMT-3