arta-feira, 18 de Novembro de 2009 7:40
To: Aaron
Cc: Antonio Soares; cisco-nsp@puck.nether.net
Subject: Re: [c-nsp] FABRIC-3-ERR_HANDLE
'Exec-on' commands are sent via IPC over the switch fabric and
'attach' sessions go over the mbus.
Eninja
On Nov 17, 2009, at 8:02 P
-nsp@puck.nether.net
Subject: Re: [c-nsp] FABRIC-3-ERR_HANDLE
'Exec-on' commands are sent via IPC over the switch fabric and 'attach'
sessions go over the mbus.
Eninja
On Nov 17, 2009, at 8:02 PM, Aaron wrote:
So, what is the difference in output from doing exec-on
'Exec-on' commands are sent via IPC over the switch fabric and
'attach' sessions go over the mbus.
Eninja
On Nov 17, 2009, at 8:02 PM, Aaron wrote:
So, what is the difference in output from doing exec-on vs attach?
You are still connecting via the same method.
On Mon, Nov 16, 2009 at 14:
So, what is the difference in output from doing exec-on vs attach?
You are still connecting via the same method.
On Mon, Nov 16, 2009 at 14:07, e ninja wrote:
> Antonio,
>
> You should *never* troubleshoot fabric errors with *any* exec-on commands.
> They run over the fabric that may or may not
Sent: segunda-feira, 16 de Novembro de 2009 19:07
To: Antonio Soares
Cc: cisco-nsp@puck.nether.net; eni...@gmail.com
Subject: Re: [c-nsp] FABRIC-3-ERR_HANDLE
Antonio,
You should never troubleshoot fabric errors with any exec-on
commands. They run over the fabric that may or may not be compromise
ira, 16 de Novembro de 2009 19:07
To: Antonio Soares
Cc: cisco-nsp@puck.nether.net; eni...@gmail.com
Subject: Re: [c-nsp] FABRIC-3-ERR_HANDLE
Antonio,
You should never troubleshoot fabric errors with any exec-on commands. They run
over the fabric that may or may not be compromised.
1. Are
Antonio,
You should *never* troubleshoot fabric errors with *any* exec-on commands.
They run over the fabric that may or may not be compromised.
1. Are any other LCs apart from slot 6 reporting CRC errors?
2. grab two "sh contr fia" from the RP and an attach to all the LCs and
send over.
udep...@gmail.com]
Sent: segunda-feira, 16 de Novembro de 2009 16:19
To: Antonio Soares
Cc: Leonardo Gama Souza; cisco-nsp@puck.nether.net
Subject: Re: [c-nsp] FABRIC-3-ERR_HANDLE
It is normal to have a CSC in standby mode. If something goes wrong with the
other CSC, it takes over.
Step 1 - Gather
It is normal to have a CSC in standby mode. If something goes wrong with the
other CSC, it takes over.
Step 1 - Gather data before making any changes
term length 0- so you don’t have to hit enter
show log
show tech
@netcabo.pt
-Original Message-
From: Leonardo Gama Souza [mailto:leonardo.so...@nec.com.br]
Sent: segunda-feira, 16 de Novembro de 2009 13:06
To: Antonio Soares; cisco-nsp@puck.nether.net
Subject: RES: [c-nsp] FABRIC-3-ERR_HANDLE
Hi,
Sounds weird.
You're right. It seems a problem with cs
Antonio Soares, CCIE #18473 (R&S)
amsoa...@netcabo.pt
-Original Message-
From: Leonardo Gama Souza [mailto:leonardo.so...@nec.com.br]
Sent: segunda-feira, 16 de Novembro de 2009 12:41
To: Antonio Soares; cisco-nsp@puck.nether.net
Subject: RES: [c-nsp] FABRIC-3-ERR_HANDLE
Hi,
Wha
Hello group,
I have a 12k reporting this:
%FABRIC-3-ERR_HANDLE: Reconfigure LC on fabric due to CRC error from slot 6
In one week, i have 4 of these messages.
Slot 6 is a SIP-601 containing 2 x SPA-10G.
What could be the problem ?
The "show controllers fia" do not show any problem.
The "exec
12 matches
Mail list logo