06-22-2004 07:18 PM
Hi,
My CSS 11501 is connected to 2 Server using port 1 and port 2, the 3 port connected to the firewall.
I've keep getting as below on my log:
JUN 12 01:38:24 1/1 130 NETMAN-2: Enterprise:Service Transition:Server2-80 -> down
JUN 12 01:47:59 1/1 131 NETMAN-2: Enterprise:Service Transition:Server2-80 -> down
JUN 12 01:48:29 1/1 132 NETMAN-2: Enterprise:Service Transition:Server1-80 -> down
JUN 16 00:21:50 1/1 133 NETMAN-2: Enterprise:Service Transition:Server2-80 -> down
JUN 16 00:27:10 1/1 134 NETMAN-2: Enterprise:Service Transition:Server2-80 -> down
JUN 17 17:55:57 1/1 135 NETMAN-2: Enterprise:Service Transition:Server2-80 -> down
JUN 18 07:39:07 1/1 136 NETMAN-2: Enterprise:Service Transition:Server2-80 -> down
JUN 18 07:39:39 1/1 137 NETMAN-2: Enterprise:Service Transition:Server1-80 -> down
JUN 20 03:11:32 1/1 138 NETMAN-2: Enterprise:Service Transition:Server2-80 -> down
JUN 21 03:03:43 1/1 139 NETMAN-2: Enterprise:Service Transition:Server1-80 -> down
JUN 21 03:11:34 1/1 140 NETMAN-2: Enterprise:Service Transition:Server2-80 -> down
JUN 22 03:03:45 1/1 141 NETMAN-2: Enterprise:Service Transition:Server1-80 -> down
JUN 22 03:11:41 1/1 142 NETMAN-2: Enterprise:Service Transition:Server2-80 -> down
I'm curious
1) why the transition is only detected on 1/1?
2) how can port 1/1 detect the services for port 80 Server2 is also down.
Can this be a server issue or the CSS port issue?
my sample config:
!************************** SERVICE **************************
service Server1-80
ip address 172.1.1.20
port 80
keepalive type tcp
keepalive frequency 60
active
service Server2-80
ip address 172.1.1.21
port 80
keepalive type tcp
keepalive frequency 60
active
owner L3-Owner
content L3_Rule-80
protocol tcp
add service Server1-80
add service Server2-80
vip address 172.1.1.22
port 80
balance aca
advanced-balance sticky-srcip
active
regards,
ganesh
06-23-2004 01:51 AM
1/1 is not the port but the module reporting the problem. This is the SCM in slot 1 subslot 1.
This problem is most likely a layer 2 issue.
Do a 'show phy' and check the speed/duplex settings.
Try to hardcode the value you want - do not use auto negotiation.
if this is ok, try an icmp keepalive and see if it makes any difference.
Regards,
Gilles.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide