Hello, I have a N7k with 40G ports that needs to be connected with 10G mainly to ASR920 and ASR9001. Using the breakout cable QSFP-4X10G-AOC results in interface down (ASR9k reports LOS). The cable is not listed as compatible for ASR9001 nor AR920 (as the SFP+ module) in SFP+ compatibility matrix and "service unsupported-transceiver" doesn't do it's magic. Have you managed to use this cable outside of Nexus ecosystem? Thanks, kind regards, Eduard RP/0/RSP0/CPU0:R9-ASR9k1#show control tenGigE 0/0/2/0 phy Mon May 9 06:45:46.866 UTC PHY data for interface: TenGigE0/0/2/0 SFP EEPROM port: 0 Xcvr Type: SFP Xcvr Code: SFP-H10GB-ACU7M Encoding: not specified Bit Rate: 10300 Mbps Vendor Name: CISCO-AVAGO Vendor OUI: 00.17.6a Vendor Part Number: AFBR-7IER07Z-CS1 (rev.: 01 ) Laser wavelength: 3072 nm (fraction: 0.00 nm) Optional SFP Signal: Tx_Disable, LOS Vendor Serial Number: AVE1948XXXX-CH2 Date Code (yy/mm/dd): 15/11/24 lot code: Diagnostic Monitoring: Enhanced Options: None ... View more

Hello experts, I have a testbed configuration with Nexus 7700 - F3 (NxOS 6.4 and latest 7.2, too) and try to configure a simple xconnect. The AC and MPLS interface are on the same F3 card. Everything seems OK control-plane-wise but the PW doesn’t come up. The 7K is connected directly to an ASR1k. The configuration is done in a simple not-mixed VDC. The question is - is this a supported topology (if so, what am I am missing in config)?  Thanks, kind regards, Eduard MPLS Interface CORE-INTER_DC# show mpls int detail Interface Ethernet1/43: ldp enabled MPLS operational Label space id 0x10000001 MPLS sub-layer Ethernet1/43-mpls layer(0x26000001) CORE-INTER_DC# show mpls l2transport binding Destination Address: 2.2.2.2,VC ID: 201 Local Label: 18 Cbit: 1, VC Type: Ethernet, GroupID: 0 MTU: 1500, Interface Desc: Vlan201 VCCV: CC Type: RA [2], TTL [3] CV Type: LSPV [2] Remote Label: 23 Cbit: 1, VC Type: Ethernet, GroupID: 12 MTU: 1500, Interface Desc: Vlan201 VCCV: CC Type: CW [1], RA [2], TTL [3] CV Type: LSPV [2] CORE-INTER_DC# show int ethernet 1/42.21 Ethernet1/42.21 is up admin state is up, Dedicated Interface, [parent interface is Ethernet1/42] Hardware: 1000/10000 Ethernet, address: 8c60.aaaa.aaaa (bia 188b.aaaa.aaaa) Description: Vlan201 MTU 1500 bytes, BW 10000000 Kbit, DLY 10 usec reliability 255/255, txload 1/255, rxload 1/255 Encapsulation 802.1Q Virtual LAN, Vlan ID 201, medium is broadcast Port mode is routed Auto-mdix is turned off EtherType is 0x8100 L3 in Switched: ucast: 0 pkts, 0 bytes - mcast: 0 pkts, 0 bytes L3 out Switched: ucast: 0 pkts, 0 bytes - mcast: 0 pkts, 0 bytes l2vpn xconnect context TEST member Ethernet1/42.21 member pseudowire201 2.2.2.2 201 encapsulation mpls ! CORE-INTER_DC# show l2vpn service xconnect all detail Legend: St=State XC St=State in the L2VPN Service Prio=Priority UP=Up DN=Down AD=Admin Down IA=Inactive SB=Standby HS=Hot Standby RV=Recovering NH=No Hardware m=manually selected Interface Group Encapsulation Prio St XC St --------- ----- ------------- ---- -- ----- VPWS name: TEST, State: DN Eth1/42.21 Eth1/42.21:201(Eth VLAN) 0 UP DN Interworking: none pw201 2.2.2.2:201(MPLS) 0 DN DN Local VC label 18 Remote VC label 23 port-profile: CORE-INTER_DC# show l2vpn atom vc pseudowire 201 detail pseudowire201 is down, VC status is down PW type: Ethernet Create time: 00:09:10, last status change time: 00:08:59 Last label FSM state change time: 00:08:58 Destination address: 2.2.2.2 VC ID: 201 Output interface: Ethernet1/43, imposed label stack {23} Preferred path: not configured Default path: active Next hop: 192.168.10.2 Member of xconnect service TEST Associated member Eth1/42.21 is up, status is up Interworking type is Like2Like Signaling protocol: LDP, peer 2.2.2.2:0 up Targeted Hello: 1.1.1.1(LDP Id) -> 2.2.2.2, LDP is UP Graceful restart: configured and not enabled Non stop routing: not configured and not enabled PWid FEC (128), VC ID: 201 Status TLV support (local/remote) : enabled/supported LDP route watch : enabled Label/status state machine : activating, LruRruD Local dataplane status received : DOWN(pw-tx-fault) BFD dataplane status received : Not sent BFD peer monitor status received : No fault Status received from access circuit : No fault Status sent to access circuit : DOWN(pw-rx-fault) Status received from pseudowire i/f : No fault Status sent to network peer : DOWN(pw-tx-fault) Status received from network peer : No fault Adjacency status of remote peer : No fault Sequencing: receive disabled, send disabled Bindings Parameter Local Remote ------------ ------------------------------ ------------------------------ Label 18 23 Group ID 0 12 Interface Vlan201 Vlan201 MTU 1500 1500 Control word on (configured: autosense) on PW type Ethernet Ethernet VCCV CV type 0x02 0x02 LSPV [2] LSPV [2] VCCV CC type 0x06 0x07 RA [2], TTL [3] CW [1], RA [2], TTL [3] Status TLV enabled supported Rx Counters 0 input transit packets, 0 bytes 0 drops, 0 seq err Tx Counters 0 output transit packets, 0 bytes 0 drops CORE-INTER_DC(config-if)# CORE-INTER_DC(config-if)# show mpls l2transport vc detail Local interface: Eth1/42.21 up, Eth VLAN up Destination address: 2.2.2.2, VC ID: 201, VC status: down Last error: MPLS dataplane reported a fault to the nexthop Output interface: Ethernet1/43, imposed label stack {23} Preferred path: not configured Default path: active Next hop: 192.168.10.2 Create time: 00:04:22, last status change time: 00:00:16 Last label FSM state change time: 00:00:16 Signaling protocol: LDP, peer 2.2.2.2:0 up Targeted Hello: 1.1.1.1(LDP Id) -> 2.2.2.2, LDP is UP Graceful restart: configured and not enabled Non stop routing: not configured and not enabled Status TLV support (local/remote) : enabled/supported LDP route watch : enabled Label/status state machine : activating, LruRruD Last local dataplane status rcvd: DOWN(pw-tx-fault) Last BFD dataplane status rcvd: Not sent Last BFD peer monitor status rcvd: No fault Last local AC circuit status rcvd: No fault Last local AC circuit status sent: DOWN(pw-rx-fault) Last local PW i/f circ status rcvd: No fault Last local LDP TLV status sent: DOWN(pw-tx-fault) Last remote LDP TLV status rcvd: No fault Last remote LDP ADJ status rcvd: No fault MPLS VC labels: local 18, remote 23 Group ID: local 0, remote 12 MTU: local 1500, remote 1500 Remote interface description: Vlan201 Sequencing: receive disabled, send disabled Control Word: On (configured: autosense) VC statistics: transit packet totals: receive 0, send 0 transit byte totals: receive 0, send 0 transit packet drops: receive 0, seq error 0, send 0 CORE-INTER_DC# show mpls ldp neighbor detail Peer LDP Ident: 2.2.2.2:0; Local LDP Ident 1.1.1.1:0 TCP connection: 2.2.2.2.17610 - 1.1.1.1.646 Password: not required, none, in use State: Oper; Msgs sent/rcvd: 34/37; Downstream; Last TIB rev sent 14 Up time: 00:19:51; UID: 2; Peer Id 1 LDP discovery sources: Ethernet1/43; Src IP addr: 192.168.10.2 holdtime: 15000 ms, hello interval: 5000 ms Targeted Hello 1.1.1.1 -> 2.2.2.2, active, passive; holdtime: infinite, hello interval: 10000 ms Addresses bound to peer LDP Ident: 192.168.4.100 172.20.0.103 2.2.2.2 192.168.2.200 192.168.10.2 Peer holdtime: 180000 ms; KA interval: 60000 ms; Peer state: estab Clients: Dir Adj Client Capabilities Sent: [Dynamic Announcement (0x0506)] [Typed Wildcard (0x050b)] Capabilities Received: [Dynamic Announcement (0x0506)] [Typed Wildcard (0x050b)]" ... View more

Hello experts, The topic is OTV on Nexus 7k peered with ASR1k in unicast mode. I've configured it considering this useful document: http://www.cisco.com/c/en/us/support/docs/switches/nexus-7000-series-switches/118917-configure-nx7k-00.html There are however two more requirements: 1. Using multiple join interfaces on ASR 1000. Is it possible? 2. Allowing for fragmentation on WAN. Is it possible on Nexus 7000 F3? For the first question, in ASR1000 documentation on the Restrictions chapter there is one listed. Only one join interface can be configured on a router for all overlays. I've tested on ASR1001-X with two Overlay interfaces using two different join interfaces and it works. It looks like the restriction is not valid maybe because of newer software version or because unicast mode is used. interface Overlay2 otv join-interface GigabitEthernet0/0/0 interface Overlay3 otv join-interface GigabitEthernet0/0/1 ASR1K#show otv route Codes: BD - Bridge-Domain, AD - Admin-Distance, SI - Service Instance, * - Backup Route OTV Unicast MAC Routing Table for Overlay2 Inst VLAN BD MAC Address AD Owner Next Hops(s) ---------------------------------------------------------- 0 201 201 xxxx.xxcc.8301 40 BD Eng Gi0/0/3:SI201 0 201 201 xxxx.xx94.8fbf 50 ISIS CORE_A-INTER_DC 2 unicast routes displayed in Overlay2 OTV Unicast MAC Routing Table for Overlay3 Inst VLAN BD MAC Address AD Owner Next Hops(s) ---------------------------------------------------------- 0 301 301 xxxx.xxcc.8301 40 BD Eng Gi0/0/3:SI301 0 301 301 xxxx.xx94.8fbf 50 ISIS CORE_A-INTER_DC 2 unicast routes displayed in Overlay3 For the second question, the WAN links cannot provide 1542 bytes MTU so we need to fragment. There is a similar subject here: https://supportforums.cisco.com/discussion/11396566/otv-asr-1k On ASR1k the otv fragmentation command is available but I cannot find a similar command for Nexus OS. Thanks, kinds regards, Eduard Gheorghiu ... View more

Hello, I plan to use Enhanced PAgP for dual-active detection for a VSS consisting of 6880-X.   Has anybody tested it? What about the 6800IA switch - does it have a similar feature that can help the active switch in the VSS to find out if the former standby has become also active?   Thanks, kind regards, Eduard Gheorghiu ... View more