[cisco-voip] CUCM 8.0.3.20000-2 - Network Failover DOWN!
Bill Riley
bill at hitechconnection.net
Tue Oct 18 13:27:36 EDT 2011
They are not teamed, they are active/passive. Yes they just access ports,
one is active and if you disconnect it the other becomes active but it does
not failback when the first cable comes back online.
From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Michel L. M. B.
Perez
Sent: Tuesday, October 18, 2011 12:12 PM
To: Matthew Saskin
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] CUCM 8.0.3.20000-2 - Network Failover DOWN!
So are you saying to me is that on GB interface speed and duplex i need to
set on auto, and LACP is not necessary to make connection redudant with my
LAN? It´s confused because we know that CUCM is based on RHEL, and I saw
lot´s of configuration on internet with LACP with xenservers and linux
machine to make Bond0 redundant connection with Cisco switches.
If I don´t have LACP from switch side to cucm server i have a little stop of
communications when one of my cables be disconnected.
So LACP is not used with CUCM servers to make a redundant connection? Is
impossible to do that?
--
Michel Perez
Skype: michelmbperez
michelmbperez at gmail.com
http://br.linkedin.com/in/michelmbperez
2011/10/15 Matthew Saskin <msaskin at gmail.com>
You don't need the ether-channel configuration. For CUCM NIC teaming the
switch ports should just be plain old access ports, no LACP.
-matthew
On Sat, Oct 15, 2011 at 11:11 AM, dschulz <dschulz at skyline-ats.com> wrote:
Gig interface should be set to auto
Dave
On Oct 15, 2011, at 10:59 AM, "Buchanan, James" <jbuchanan at presidio.com>
wrote:
For starters, your Ethernet interfaces on the server are set to auto
negotiate, but on the switch are hard-coded. Big no-no. Change the switch
side first.
James Buchanan| UC Technology Manager | Presidio South | Presidio Networked
Solutions
12 Cadillac Dr Ste 130 Brentwood, TN 37027 |
<mailto:jbuchanan at presidio.com> jbuchanan at presidio.com
D: 615-866-5729 | F:615-866-5781 <http://www.presidio.com/>
www.presidio.com
From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Michel L. M. B.
Perez
Sent: Saturday, October 15, 2011 9:41 AM
To: cisco-voip at puck.nether.net
Subject: [cisco-voip] CUCM 8.0.3.20000-2 - Network Failover DOWN!
Hello Peolple,
I have TWO DC, my publisher is connected to a Cisco 6504 Switch and de
Subscriber is connected to 6509, my problem is that i´ve enabled bond0
interface (nic teaming at this two MCS7835 servers), but the port-channel is
not coming up neither from the server side and from the switch side, anyone
here has this working? Here are some outputs from my 6509.
Server Config
admin:show network failover
Bond 0
DHCP : disabled Status : up
IP Address : 10.5.3.216 IP Mask : 255.255.000.000
Link Detected: no Mode : Auto disabled, N/A, N/A
Ethernet 0
DHCP : disabled Status : up
IP Address : IP Mask :
Link Detected: yes Mode : Auto enabled, Full, 1000MB/s
Ethernet 1
DHCP : disabled Status : up
IP Address : IP Mask :
Link Detected: yes Mode : Auto enabled, Full, 1000MB/s
DNS
Primary : 10.5.3.3 Secondary : 10.5.3.102
Options : timeout:5 attempts:2
Domain : xxx.xxx.xx
Gateway : 10.5.2.1 on Ethernet bond0
Switch Config
interface Port-channel11
description description #### LACP - SRV-CUCM-FLN02 ####
switchport
switchport mode access
spanning-tree portfast edge
spanning-tree bpduguard enable
interface GigabitEthernet1/41
description #### CUCM - ETH1 ####
switchport
switchport mode access
speed 1000
duplex full
no cdp enable
channel-group 11 mode active
spanning-tree portfast edge
spanning-tree bpduguard enable
interface GigabitEthernet1/42
description #### CUCM - ETH2 ####
switchport
switchport mode access
speed 1000
duplex full
no cdp enable
channel-group 11 mode active
spanning-tree portfast edge
spanning-tree bpduguard enable
SW_6509E(config-if-range)#do sh etherc 11 summ
Flags: D - down P - bundled in port-channel
I - stand-alone s - suspended
H - Hot-standby (LACP only)
R - Layer3 S - Layer2
U - in use N - not in use, no aggregation
f - failed to allocate aggregator
M - not in use, no aggregation due to minimum links not met
m - not in use, port not aggregated due to minimum links not met
u - unsuitable for bundling
d - default port
w - waiting to be aggregated
Number of channel-groups in use: 11
Number of aggregators: 12
Group Port-channel Protocol Ports
------+-------------+-----------+-------------------------------------------
----
11 Po11(SD) LACP Gi1/41(I) Gi1/42(I)
Last applied Hash Distribution Algorithm: -
SW_6509E(config-if-range)#
--
Michel Perez
Skype: michelmbperez
michelmbperez at gmail.com
http://br.linkedin.com/in/michelmbperez
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20111018/b7a2ba4c/attachment.html>
More information about the cisco-voip
mailing list