testing in my lab now -- simple back to back copper over glc-t between
n5020 running 4.2(1)n2(1) and asr1002 running 3.1.0s
=========================================================================================
asr1002-1#sh run int gig 0/0/3
Building configuration...
Current configuration : 74 bytes
!
interface GigabitEthernet0/0/3
no ip address
no negotiation auto
end
asr1002-1#sh int gig 0/0/3
GigabitEthernet0/0/3 is up, line protocol is up
Hardware is 4XGE-BUILT-IN, address is 588d.09ef.5103 (bia 588d.09ef.5103)
MTU 1500 bytes, BW 1000000 Kbit/sec, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive not supported
Full Duplex, 1000Mbps, link type is force-up, media type is T
output flow-control is on, input flow-control is on
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:00, output never, output hang never
Last clearing of "show interface" counters never
Input queue: 0/375/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
37 packets input, 5077 bytes, 0 no buffer
Received 0 broadcasts (0 IP multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 37 multicast, 0 pause input
0 packets output, 0 bytes, 0 underruns
0 output errors, 0 collisions, 4 interface resets
0 unknown protocol drops
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier, 0 pause output
0 output buffer failures, 0 output buffers swapped out
----------------------------------------------------------------------------------------
n5020-1# sh run int e1/1
!Command: show running-config interface Ethernet1/1
!Time: Fri Apr 15 20:46:47 2011
version 4.2(1)N2(1)
interface Ethernet1/1
speed 1000
n5020-1# sh int e1/1
Ethernet1/1 is up
Hardware: 1000/10000 Ethernet, address: 0005.73a1.6508 (bia
0005.73a1.6508)
MTU 1500 bytes, BW 1000000 Kbit, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA
Port mode is access
full-duplex, 1000 Mb/s, media type is 1/10g
Beacon is turned off
Input flow-control is off, output flow-control is off
Rate mode is dedicated
Switchport monitor is off
Last link flapped 00:01:54
Last clearing of "show interface" counters 00:03:58
30 seconds input rate 0 bits/sec, 0 packets/sec
30 seconds output rate 232 bits/sec, 0 packets/sec
Load-Interval #2: 5 minute (300 seconds)
input rate 0 bps, 0 pps; output rate 32 bps, 0 pps
RX
0 unicast packets 0 multicast packets 0 broadcast packets
0 input packets 0 bytes
0 jumbo packets 0 storm suppression packets
0 runts 0 giants 0 CRC 0 no buffer
0 input error 0 short frame 0 overrun 0 underrun 0 ignored
0 watchdog 0 bad etype drop 0 bad proto drop 0 if down drop
0 input with dribble 0 input discard
0 Rx pause
TX
0 unicast packets 46 multicast packets 0 broadcast packets
46 output packets 6528 bytes
0 jumbo packets
0 output errors 0 collision 0 deferred 0 late collision
0 lost carrier 0 no carrier 0 babble
0 Tx pause
1 interface resets
=========================================================================================
the asr is as "carrier" as i get -- and i don't have a 5548 to dink
with, so take this for what its worth, but i think that tony is spot on.
q.
==
() ascii ribbon campaign - against html e-mail
/\ www.asciiribbon.org - against proprietary attachments
On 04/15/2011 12:28 PM, Tony Varriale wrote:
On 4/15/2011 1:07 PM, Gert Doering wrote:
Hi,
yesterday, one of our customers tried to move two GigE-on-fiber circuits
from a Catalyst 4507 to a new Nexus 5548.
The other end terminates on some carrier gear (and is then multiplexed
in whatever ways across the city).
After moving the circuit, the link didn't come up on the Nexus, but
the carrier gear *did* show link. I wasn't on-site, so I couldn't
investigate myself, but it smells very much like "GigE link negotiation
being disabled on the carrier gear" - carriers love that.
Of course we do not have access to either the Catalyst nor the Nexus,
but it's "our duty" to "make it work" (after all, we provide the fiber
patches!). So I'd like him to test disabling link negotiation on the
Nexus, but don't know how to do that - no access to any NX-OS gear yet.
On CatOS, this is "set port negotiation x/y disable".
On IOS, it's "int giga x/y / speed nonegotiate".
--> How to do it on NX-OS?
http://www.cisco.com/en/US/docs/switches/datacenter/nexus5000/sw/configuration/guide/cli_rel_4_0_1a/BasicEthernet.html
refers to "Layer 1 autonegotiation", but no word on turning it off...
gert
_______________________________________________
cisco-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
Hmmm interesting. Force it? speed 1000.
_______________________________________________
cisco-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
_______________________________________________
cisco-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
