Router-stby#show tech
[Wed Jan 13 09:44:09.643 2016]
[Wed Jan 13 09:44:09.643 2016] ------------------ show clock ------------------
[Wed Jan 13 09:44:09.643 2016]
[Wed Jan 13 09:44:09.643 2016]
[Wed Jan 13 09:44:09.643 2016] *00:43:45.172 UTC Wed Jan 13 2016
[Wed Jan 13 09:44:09.703 2016]
[Wed Jan 13 09:44:09.703 2016] ------------------ show version ------------------
[Wed Jan 13 09:44:09.772 2016]
[Wed Jan 13 09:44:09.772 2016] Cisco IOS XE Software, Version 03.13.01.S - Extended Support Release
[Wed Jan 13 09:44:09.843 2016] Cisco IOS Software, ASR1000 Software (X86_64_LINUX_IOSD-ADVIPSERVICESK9-M), Version 15.4(3)S1, RELEASE SOFTWARE (fc3)
[Wed Jan 13 09:44:09.973 2016] Technical Support: http://www.cisco.com/techsupport
[Wed Jan 13 09:44:10.042 2016] Copyright (c) 1986-2014 by Cisco Systems, Inc.
[Wed Jan 13 09:44:10.042 2016] Compiled Fri 31-Oct-14 19:46 by mcpre
[Wed Jan 13 09:44:10.102 2016]
[Wed Jan 13 09:44:10.102 2016]
[Wed Jan 13 09:44:10.102 2016] Cisco IOS-XE software, Copyright (c) 2005-2014 by cisco Systems, Inc.
[Wed Jan 13 09:44:10.173 2016] All rights reserved. Certain components of Cisco IOS-XE software are
[Wed Jan 13 09:44:10.242 2016] licensed under the GNU General Public License ("GPL") Version 2.0. The
[Wed Jan 13 09:44:10.303 2016] software code licensed under GPL Version 2.0 is free software that comes
[Wed Jan 13 09:44:10.443 2016] with ABSOLUTELY NO WARRANTY. You can redistribute and/or modify such
[Wed Jan 13 09:44:10.503 2016] GPL code under the terms of GPL Version 2.0. For more details, see the
[Wed Jan 13 09:44:10.573 2016] documentation or "License Notice" file accompanying the IOS-XE software,
[Wed Jan 13 09:44:10.643 2016] or the applicable URL provided on the flyer accompanying the IOS-XE
[Wed Jan 13 09:44:10.703 2016] software.
[Wed Jan 13 09:44:10.703 2016]
[Wed Jan 13 09:44:10.703 2016]
[Wed Jan 13 09:44:10.703 2016] ROM: IOS-XE ROMMON
[Wed Jan 13 09:44:10.772 2016]
[Wed Jan 13 09:44:10.772 2016] Router uptime is 22 hours, 30 minutes
[Wed Jan 13 09:44:10.772 2016] Uptime for this control processor is 15 hours, 26 minutes
[Wed Jan 13 09:44:10.842 2016] System returned to ROM by reload at 07:11:59 UTC Tue Jan 12 2016
[Wed Jan 13 09:44:10.902 2016] System image file is "bootflash:/asr1000rp2-advipservicesk9.03.13.01.S.154-3.S1-ext.b"
[Wed Jan 13 09:44:11.042 2016] Last reload reason: redundancy force-switchover
[Wed Jan 13 09:44:11.042 2016]
[Wed Jan 13 09:44:11.042 2016]
[Wed Jan 13 09:44:11.042 2016]
[Wed Jan 13 09:44:11.042 2016] This product contains cryptographic features and is subject to United
[Wed Jan 13 09:44:11.173 2016] States and local country laws governing import, export, transfer and
[Wed Jan 13 09:44:11.242 2016] use. Delivery of Cisco cryptographic products does not imply
[Wed Jan 13 09:44:11.303 2016] third-party authority to import, export, distribute or use encryption.
[Wed Jan 13 09:44:11.372 2016] Importers, exporters, distributors and users are responsible for
[Wed Jan 13 09:44:11.443 2016] compliance with U.S. and local country laws. By using this product you
[Wed Jan 13 09:44:11.502 2016] agree to comply with applicable laws and regulations. If you are unable
[Wed Jan 13 09:44:11.573 2016] to comply with U.S. and local laws, return this product immediately.
[Wed Jan 13 09:44:11.643 2016]
[Wed Jan 13 09:44:11.643 2016] A summary of U.S. laws governing Cisco cryptographic products may be found at:
[Wed Jan 13 09:44:11.703 2016] http://www.cisco.com/wwl/export/crypto/tool/stqrg.html
[Wed Jan 13 09:44:11.772 2016]
[Wed Jan 13 09:44:11.772 2016] If you require further assistance please contact us by sending email to
[Wed Jan 13 09:44:11.842 2016] export@cisco.com.
[Wed Jan 13 09:44:11.902 2016]
[Wed Jan 13 09:44:11.902 2016] cisco ASR1006 (RP2) processor (revision RP2) with 4171307K/6147K bytes of memory.
[Wed Jan 13 09:44:11.973 2016] Processor board ID FOX1335G1CB
[Wed Jan 13 09:44:12.043 2016] 10 Gigabit Ethernet interfaces
[Wed Jan 13 09:44:12.043 2016] 32768K bytes of non-volatile configuration memory.
[Wed Jan 13 09:44:12.102 2016] 8388608K bytes of physical memory.
[Wed Jan 13 09:44:12.102 2016] 1873919K bytes of eUSB flash at bootflash:.
[Wed Jan 13 09:44:12.173 2016] 78085207K bytes of SATA hard disk at harddisk:.
[Wed Jan 13 09:44:12.242 2016]
[Wed Jan 13 09:44:12.242 2016] Configuration register is 0x2142
[Wed Jan 13 09:44:12.242 2016]
[Wed Jan 13 09:44:12.302 2016]
[Wed Jan 13 09:44:12.302 2016] ------------------ show running-config ------------------
[Wed Jan 13 09:44:12.302 2016]
[Wed Jan 13 09:44:12.302 2016]
[Wed Jan 13 09:44:12.372 2016] Building configuration...
[Wed Jan 13 09:44:12.372 2016]
[Wed Jan 13 09:44:12.372 2016] Current configuration : 1557 bytes
[Wed Jan 13 09:44:12.443 2016] !
[Wed Jan 13 09:44:12.443 2016] ! Last configuration change at 00:43:07 UTC Wed Jan 13 2016
[Wed Jan 13 09:44:12.502 2016] !
[Wed Jan 13 09:44:12.502 2016] version 15.4
[Wed Jan 13 09:44:12.502 2016] service timestamps debug datetime msec
[Wed Jan 13 09:44:12.502 2016] service timestamps log datetime msec
[Wed Jan 13 09:44:12.572 2016] no platform punt-keepalive disable-kernel-core
[Wed Jan 13 09:44:12.643 2016] !
[Wed Jan 13 09:44:12.643 2016] hostname Router
[Wed Jan 13 09:44:12.643 2016] !
[Wed Jan 13 09:44:12.643 2016] boot-start-marker
[Wed Jan 13 09:44:12.643 2016] boot-end-marker
[Wed Jan 13 09:44:12.703 2016] !
[Wed Jan 13 09:44:12.703 2016] !
[Wed Jan 13 09:44:12.703 2016] vrf definition Mgmt-intf
[Wed Jan 13 09:44:12.703 2016] !
[Wed Jan 13 09:44:12.703 2016] address-family ipv4
[Wed Jan 13 09:44:12.772 2016] exit-address-family
[Wed Jan 13 09:44:12.772 2016] !
[Wed Jan 13 09:44:12.772 2016] address-family ipv6
[Wed Jan 13 09:44:12.772 2016] exit-address-family
[Wed Jan 13 09:44:12.844 2016] !
[Wed Jan 13 09:44:12.844 2016] !
[Wed Jan 13 09:44:12.844 2016] no aaa new-model
[Wed Jan 13 09:44:12.844 2016] !
[Wed Jan 13 09:44:12.844 2016] !
[Wed Jan 13 09:44:12.844 2016] !
[Wed Jan 13 09:44:12.844 2016] !
[Wed Jan 13 09:44:12.844 2016] !
[Wed Jan 13 09:44:12.844 2016] !
[Wed Jan 13 09:44:12.844 2016] !
[Wed Jan 13 09:44:12.844 2016] !
[Wed Jan 13 09:44:12.844 2016] !
[Wed Jan 13 09:44:12.844 2016]
[Wed Jan 13 09:44:12.904 2016]
[Wed Jan 13 09:44:12.904 2016]
[Wed Jan 13 09:44:12.904 2016] !
[Wed Jan 13 09:44:12.904 2016] !
[Wed Jan 13 09:44:12.904 2016] !
[Wed Jan 13 09:44:12.904 2016] !
[Wed Jan 13 09:44:12.904 2016] !
[Wed Jan 13 09:44:12.904 2016] !
[Wed Jan 13 09:44:12.904 2016] !
[Wed Jan 13 09:44:12.904 2016] !
[Wed Jan 13 09:44:12.904 2016] !
[Wed Jan 13 09:44:12.904 2016] !
[Wed Jan 13 09:44:12.904 2016] subscriber templating
[Wed Jan 13 09:44:12.904 2016] !
[Wed Jan 13 09:44:12.904 2016] multilink bundle-name authenticated
[Wed Jan 13 09:44:12.972 2016] !
[Wed Jan 13 09:44:12.972 2016] !
[Wed Jan 13 09:44:12.972 2016] !
[Wed Jan 13 09:44:12.972 2016] !
[Wed Jan 13 09:44:12.972 2016] !
[Wed Jan 13 09:44:12.972 2016] !
[Wed Jan 13 09:44:12.972 2016] !
[Wed Jan 13 09:44:12.972 2016] !
[Wed Jan 13 09:44:12.972 2016] !
[Wed Jan 13 09:44:12.972 2016] !
[Wed Jan 13 09:44:12.972 2016] spanning-tree extend system-id
[Wed Jan 13 09:44:13.042 2016] !
[Wed Jan 13 09:44:13.042 2016] !
[Wed Jan 13 09:44:13.042 2016] redundancy
[Wed Jan 13 09:44:13.042 2016] mode sso
[Wed Jan 13 09:44:13.042 2016] !
[Wed Jan 13 09:44:13.042 2016] !
[Wed Jan 13 09:44:13.103 2016] !
[Wed Jan 13 09:44:13.103 2016] !
[Wed Jan 13 09:44:13.103 2016] !
[Wed Jan 13 09:44:13.103 2016] !
[Wed Jan 13 09:44:13.103 2016] !
[Wed Jan 13 09:44:13.103 2016] !
[Wed Jan 13 09:44:13.103 2016] !
[Wed Jan 13 09:44:13.103 2016] !
[Wed Jan 13 09:44:13.103 2016] !
[Wed Jan 13 09:44:13.103 2016] !
[Wed Jan 13 09:44:13.103 2016] !
[Wed Jan 13 09:44:13.103 2016] !
[Wed Jan 13 09:44:13.103 2016] !
[Wed Jan 13 09:44:13.103 2016] !
[Wed Jan 13 09:44:13.103 2016] !
[Wed Jan 13 09:44:13.103 2016] !
[Wed Jan 13 09:44:13.103 2016] !
[Wed Jan 13 09:44:13.103 2016] !
[Wed Jan 13 09:44:13.103 2016] !
[Wed Jan 13 09:44:13.103 2016] !
[Wed Jan 13 09:44:13.172 2016] !
[Wed Jan 13 09:44:13.172 2016] interface GigabitEthernet0/1/0
[Wed Jan 13 09:44:13.172 2016] no ip address
[Wed Jan 13 09:44:13.172 2016] negotiation auto
[Wed Jan 13 09:44:13.242 2016] !
[Wed Jan 13 09:44:13.242 2016] interface GigabitEthernet0/1/1
[Wed Jan 13 09:44:13.242 2016] no ip address
[Wed Jan 13 09:44:13.242 2016] negotiation auto
[Wed Jan 13 09:44:13.302 2016] !
[Wed Jan 13 09:44:13.302 2016] interface GigabitEthernet0/1/2
[Wed Jan 13 09:44:13.302 2016] no ip address
[Wed Jan 13 09:44:13.372 2016] negotiation auto
[Wed Jan 13 09:44:13.372 2016] !
[Wed Jan 13 09:44:13.372 2016] interface GigabitEthernet0/1/3
[Wed Jan 13 09:44:13.372 2016] no ip address
[Wed Jan 13 09:44:13.443 2016] negotiation auto
[Wed Jan 13 09:44:13.443 2016] !
[Wed Jan 13 09:44:13.443 2016] interface GigabitEthernet0/1/4
[Wed Jan 13 09:44:13.443 2016] no ip address
[Wed Jan 13 09:44:13.502 2016] negotiation auto
[Wed Jan 13 09:44:13.502 2016] !
[Wed Jan 13 09:44:13.502 2016] interface GigabitEthernet0/1/5
[Wed Jan 13 09:44:13.572 2016] no ip address
[Wed Jan 13 09:44:13.572 2016] negotiation auto
[Wed Jan 13 09:44:13.572 2016] !
[Wed Jan 13 09:44:13.572 2016] interface GigabitEthernet0/1/6
[Wed Jan 13 09:44:13.643 2016] no ip address
[Wed Jan 13 09:44:13.643 2016] negotiation auto
[Wed Jan 13 09:44:13.643 2016] !
[Wed Jan 13 09:44:13.643 2016] interface GigabitEthernet0/1/7
[Wed Jan 13 09:44:13.703 2016] no ip address
[Wed Jan 13 09:44:13.703 2016] negotiation auto
[Wed Jan 13 09:44:13.703 2016] !
[Wed Jan 13 09:44:13.703 2016] interface GigabitEthernet0/1/8
[Wed Jan 13 09:44:13.772 2016] no ip address
[Wed Jan 13 09:44:13.772 2016] negotiation auto
[Wed Jan 13 09:44:13.772 2016] !
[Wed Jan 13 09:44:13.772 2016] interface GigabitEthernet0/1/9
[Wed Jan 13 09:44:13.842 2016] no ip address
[Wed Jan 13 09:44:13.842 2016] negotiation auto
[Wed Jan 13 09:44:13.842 2016] !
[Wed Jan 13 09:44:13.902 2016] interface GigabitEthernet0
[Wed Jan 13 09:44:13.902 2016] vrf forwarding Mgmt-intf
[Wed Jan 13 09:44:13.902 2016] no ip address
[Wed Jan 13 09:44:13.972 2016] negotiation auto
[Wed Jan 13 09:44:13.972 2016] !
[Wed Jan 13 09:44:13.972 2016] ip forward-protocol nd
[Wed Jan 13 09:44:13.972 2016] !
[Wed Jan 13 09:44:13.972 2016] no ip http server
[Wed Jan 13 09:44:14.042 2016] no ip http secure-server
[Wed Jan 13 09:44:14.042 2016] !
[Wed Jan 13 09:44:14.042 2016] !
[Wed Jan 13 09:44:14.042 2016] !
[Wed Jan 13 09:44:14.042 2016] !
[Wed Jan 13 09:44:14.042 2016] control-plane
[Wed Jan 13 09:44:14.103 2016] !
[Wed Jan 13 09:44:14.103 2016] !
[Wed Jan 13 09:44:14.103 2016] !
[Wed Jan 13 09:44:14.103 2016] !
[Wed Jan 13 09:44:14.103 2016] !
[Wed Jan 13 09:44:14.103 2016] !
[Wed Jan 13 09:44:14.103 2016] !
[Wed Jan 13 09:44:14.103 2016] !
[Wed Jan 13 09:44:14.103 2016] !
[Wed Jan 13 09:44:14.103 2016] !
[Wed Jan 13 09:44:14.103 2016] line con 0
[Wed Jan 13 09:44:14.103 2016] stopbits 1
[Wed Jan 13 09:44:14.103 2016] line aux 0
[Wed Jan 13 09:44:14.172 2016] stopbits 1
[Wed Jan 13 09:44:14.172 2016] line vty 0 4
[Wed Jan 13 09:44:14.172 2016] login
[Wed Jan 13 09:44:14.172 2016] !
[Wed Jan 13 09:44:14.172 2016] !
[Wed Jan 13 09:44:14.172 2016] end
[Wed Jan 13 09:44:14.172 2016] https://cae-largefile-prod.cisco.com/web-ui?appId=CSOne&srId=637643773&fileName=r1_2nd.log&forceText=1
Saturday, March 30, 2019
Standby-RP Console
CISCO网络设备查看端口收发光功率
CRS-1#show controllers SONET 0/0/1/0
CRS-1#show hw-module subslot 0/10/0 status pluggable-optics 0
7609#show interfaces te1/1 transceiver
N7K#show interface e3/1 transceiver details
IOS-XE#show hw-module subslot 0/0 transceiver 4 status
CRS-1#show hw-module subslot 0/10/0 status pluggable-optics 0
7609#show interfaces te1/1 transceiver
N7K#show interface e3/1 transceiver details
IOS-XE#show hw-module subslot 0/0 transceiver 4 status
Thursday, March 14, 2019
可以在SFP+插槽中使用SFP电口光模块
我们常常对SFP和SFP+的兼容性感到困惑，困惑的是我们不知道是否可以使用SFP+插槽中的SFP光模块，这个问题对许多工程师来说非常头痛。本文将重点为大家讲解这个问题。
SFP光模块在大多数情况下可以插入SFP+端口。
根据经验来说，SFP光模块可以在SFP+插槽运行，但SFP+光模块不能在SFP插槽中运行。当您在SFP+端口插入SFP模块时，此端口的速度为1G，而不是10G。有时这个端口将锁定速度在1G，直到你重新加载交换机或做一些命令。此外，SFP+端口通常不能支持1G以下的速度。也就是说，我们不能在SFP+端口上插入100BASE SFP光模块。事实上，对于这个问题，它很大程度上取决于交换机型号，有时SFP在SFP+端口支持，有时不支持。例如，几乎思科交换机的所有SFP+端口都可以支持SFP光模块，Brocade交换机的许多SFP+端口仅支持SFP+。虽然它经常可行，但要求交换机供应商提供的信息更为安全。
SFP+端口中的SFP光模块
SFP+不能自动兼容到1G以支持SFP光模块
据我所知，与在10/100/1000自动兼容中可用的铜SFP不同，SFP和SFP+等光纤不支持自动兼容。事实上，大多数SFP和SFP+只会在额定速度下运行。
虽然很多情况下我们可以在SFP+端口使用SFP光模块，但是这并不意味着SFP+插入SFP+端口可以支持1G。在光纤链路中，如果我们在一侧的SFP+端口（1G）插入SFP光模块，然后在另一侧（10G）的SFP+端口上插入SFP+光模块，则可能无法正常工作！对于这个问题，如果你使用SFP+高速线缆，它也不能兼容到1G。
当网络中使用SFP和SFP+光模块时，请确保光纤链路两端的速度相同。10GSFP光模块可以在SFP+端口中使用，但SFP不能连接到SFP+光模块。对于不同的速度，传输距离和波长，10G SFP+光模块只能用于10G SFP+端口，永远不能自动兼容到1G。
Subscribe to:
Posts (Atom)