I have not seen TRILL RAW configuration on Cisco Nexus as CISCO uses superset of TRILL called fabricpath. Please refer TRILL RAW configuration on HP switches http://www.manualslib.com/manual/579822/Hp-6125xlg.html?page=16     ... View more

  Hi Frank, Transparent Inter-Connection of Lots of Links (TRILL) is a technology that addresses the same requirements as the Cisco FabricPath and has almost the same benefits as FabricPath. Unlike FabricPath TRILL, is an IETF standard that was proposed to address the various STP challenges including inefficient utilizations of links, long convergence times, and MAC address table scaling in the Datacenter networks.   Like FabricPath, TRILL uses IS-IS as the control protocol with the idea of taking the advantages of a Layer 3 routing protocol and at the same time maintain the simplicity of a Layer 2 network.   To forward frames, TRILL uses a MAC-in-MAC encapsulation format. The ingress RBridge encapsulates the original Layer 2 frame with a new source and destination MAC (the MAC addresses of the source RBridge, and the next-hop RBridge, respectively), a TRILL Header, (which has the Ingress and Egress nicknames that identify the source and destination RBridge, respectively), and the original Layer 2 frame with a new CRC. The incoming 802.1q or q-in-q tag needs to be preserved in the inner header. Egress RBridge removes the headers added by the ingress RBridge and will forward them based on the inner frame.   Kindly refer the best book on TRILL as follows:   http://www.ciscopress.com/store/using-trill-fabricpath-and-vxlan-designing-massively-9780133393040 Using TRILL, FabricPath, and VXLAN: Designing Massively Scalable Data Centers (MSDC) with Overlays By Sanjay K. Hooda, Shyam Kapadia, Padmanabhan Krishnan Published Jan 31, 2014 by Cisco Press. Part of the Networking Technology series. Please email me at sachin.koenig@gmail.com , if you further need any assistance. Kindly rate !!   Best Regards   Sachin Garg     ... View more

  Hi Frank, Transparent Inter-Connection of Lots of Links (TRILL) is a technology that addresses the same requirements as the Cisco FabricPath and has almost the same benefits as FabricPath. Unlike FabricPath TRILL, is an IETF standard that was proposed to address the various STP challenges including inefficient utilizations of links, long convergence times, and MAC address table scaling in the Datacenter networks.   Like FabricPath, TRILL uses IS-IS as the control protocol with the idea of taking the advantages of a Layer 3 routing protocol and at the same time maintain the simplicity of a Layer 2 network.   To forward frames, TRILL uses a MAC-in-MAC encapsulation format. The ingress RBridge encapsulates the original Layer 2 frame with a new source and destination MAC (the MAC addresses of the source RBridge, and the next-hop RBridge, respectively), a TRILL Header, (which has the Ingress and Egress nicknames that identify the source and destination RBridge, respectively), and the original Layer 2 frame with a new CRC. The incoming 802.1q or q-in-q tag needs to be preserved in the inner header. Egress RBridge removes the headers added by the ingress RBridge and will forward them based on the inner frame.   Kindly refer the best book on TRILL as follows:   http://www.ciscopress.com/store/using-trill-fabricpath-and-vxlan-designing-massively-9780133393040 Using TRILL, FabricPath, and VXLAN: Designing Massively Scalable Data Centers (MSDC) with Overlays By Sanjay K. Hooda, Shyam Kapadia, Padmanabhan Krishnan Published Jan 31, 2014 by Cisco Press. Part of the Networking Technology series. Please email me at sachin.koenig@gmail.com , if you further need any assistance. Kindly rate !!   Best Regards   Sachin Garg       442 ... View more

  Hi Frank, Transparent Inter-Connection of Lots of Links (TRILL) is a technology that addresses the same requirements as the Cisco FabricPath and has almost the same benefits as FabricPath. Unlike FabricPath TRILL, is an IETF standard that was proposed to address the various STP challenges including inefficient utilizations of links, long convergence times, and MAC address table scaling in the Datacenter networks.   Like FabricPath, TRILL uses IS-IS as the control protocol with the idea of taking the advantages of a Layer 3 routing protocol and at the same time maintain the simplicity of a Layer 2 network.   To forward frames, TRILL uses a MAC-in-MAC encapsulation format. The ingress RBridge encapsulates the original Layer 2 frame with a new source and destination MAC (the MAC addresses of the source RBridge, and the next-hop RBridge, respectively), a TRILL Header, (which has the Ingress and Egress nicknames that identify the source and destination RBridge, respectively), and the original Layer 2 frame with a new CRC. The incoming 802.1q or q-in-q tag needs to be preserved in the inner header. Egress RBridge removes the headers added by the ingress RBridge and will forward them based on the inner frame.   Kindly refer the best book on TRILL as follows:   http://www.ciscopress.com/store/using-trill-fabricpath-and-vxlan-designing-massively-9780133393040 Using TRILL, FabricPath, and VXLAN: Designing Massively Scalable Data Centers (MSDC) with Overlays By Sanjay K. Hooda, Shyam Kapadia, Padmanabhan Krishnan Published Jan 31, 2014 by Cisco Press. Part of the Networking Technology series. Please email me at sachin.koenig@gmail.com , if you further need any assistance. Kindly rate !!   Best Regards   Sachin Garg     ... View more

  323 Hi Frank, Transparent Inter-Connection of Lots of Links (TRILL) is a technology that addresses the same requirements as the Cisco FabricPath and has almost the same benefits as FabricPath. Unlike FabricPath TRILL, is an IETF standard that was proposed to address the various STP challenges including inefficient utilizations of links, long convergence times, and MAC address table scaling in the Datacenter networks.   Like FabricPath, TRILL uses IS-IS as the control protocol with the idea of taking the advantages of a Layer 3 routing protocol and at the same time maintain the simplicity of a Layer 2 network.   To forward frames, TRILL uses a MAC-in-MAC encapsulation format. The ingress RBridge encapsulates the original Layer 2 frame with a new source and destination MAC (the MAC addresses of the source RBridge, and the next-hop RBridge, respectively), a TRILL Header, (which has the Ingress and Egress nicknames that identify the source and destination RBridge, respectively), and the original Layer 2 frame with a new CRC. The incoming 802.1q or q-in-q tag needs to be preserved in the inner header. Egress RBridge removes the headers added by the ingress RBridge and will forward them based on the inner frame.   Kindly refer the best book on TRILL as follows:   http://www.ciscopress.com/store/using-trill-fabricpath-and-vxlan-designing-massively-9780133393040 Using TRILL, FabricPath, and VXLAN: Designing Massively Scalable Data Centers (MSDC) with Overlays By Sanjay K. Hooda, Shyam Kapadia, Padmanabhan Krishnan Published Jan 31, 2014 by Cisco Press. Part of the Networking Technology series. Please email me at sachin.koenig@gmail.com , if you further need any assistance. Kindly rate !!   Best Regards   Sachin Garg     ... View more

Hi Mario,   Could you please share your network diagram and configuration on these switches, so that I can help you further.   Best Reagrds Sachi Garg ... View more

Hi Ralacron, The current Cisco N7K OTV implementation requires separation between SVI routing and OTV encapsulation for a given VLAN. In addition, the Join interface can only be defined as a physical interface (or subinterface) or as a logical one (i.e. Layer 3 port channel or Layer 3 port channel subinterface). Note: Support for loopback interfaces as OTV Join interfaces is planned for a future NX-OS release. To meet these constraints, two VDCs will be deployed at the Delta N7Ks:     an OTV VDC dedicated to perform the OTV functionality     a Distr VDC used to provide SVI routing support. We could either configure the OTV VDC ‘on-a-stick’ with regards to the Distr VDC, or directly connect the OTV VDC to the transport WAN. We chose to use the ‘on-a-stick’ design. One clear advantage to the ‘on-a-stick’ design is that when the NX-OS no longer requires separation between SVI routing and OTV encapsulation for a given VLAN, Delta will easily be able to migrate to using just the Distr VDC for SVI routing and OTV encapsulation. The only migration steps needed will be to move the OTV configuration from the OTV VDC to the Distr VDC and deactivate the OTV VDC. This migration would be transparent to the rest of the data center network. Note: There is a small cost, the ‘on-a-stick’ design does use at least an extra pair of interfaces on each N7K. The N7K also requires that the routed SVI not be carried across the vPC peer link, so a separate Layer 3 link will be implemented between the vPC peers. This Layer 3 link can also be used for the vPC peer-keep alives.   The current OTV implementation on the Nexus 7000 enforces the separation between SVI routing and OTV encapsulation for a given VLAN. This separation can be achieved with the traditional workaround of having two separate network devices to perform these two functions. An alternative, cleaner and less intrusive solution is proposed here by introducing the use of Virtual Device Contexts (VDCs) available with Nexus 7000 platforms. Two VDCs would be deployed: an OTV VDC dedicated to perform the OTV functionality and a Routing VDC used to provide SVI routing support. Please refer the following doc from Cisco: http://www.cisco.com/c/en/us/td/docs/solutions/Enterprise/Data_Center/DCI/whitepaper/DCI3_OTV_Intro/DCI_1.html#wp1215970 ... View more

This is a very renowned case called FHRP isolation. You have configured HSRP for VLAN 200 in both Site-1 (between switch A and B) and Site-2 (between switch C and D). Because it is a contiguous subnet all hosts in VLAN-200 has their gateway set to A.B.C.D,  which is the same virtual gateway IP address in both sites. Now ideally traffic from Site-1 should exit via switch A and traffic from Site-2 should exit via switch C since both of these switches where setup with a same HSRP priority . But this is not what happens by default. On switch A, the active HSRP device for VLAN-200 is switch C. This would be the same on switch B and D. Why would this be? Since both switch A and C have their HSRP priorities set to same, the router with the higher interface IP address will be elected as the Active HSRP device. In this case switch C. This means that all traffic towards the gateway of A.B.C.D will be forward to Site-2. This is the problem that we will now correct. The next output shows the traffic from Site-1 is destined via the overlay. Not cool. Step 1 Could you please send me the output of show hsrp brief once you got the output you wil lfind out IP address of Active device. Step 2 Send me the out put of following after getting Active router IP show ip arp | i Active_Router_IP|Add Here you will get that MAC address Step 3 Send me the out put of following after getting MAC address show mac add add MAC_Address | b VLAN   FHRP isolation is the act of filtering HSRP, VRRP or GLBP traffic from going across the overlay, and thereby forcing localized FHRP elections. There are two parts to filter.     The election process should be contained within each site to elect a local active devices.     The virtual MAC addresses will still be advertised, which would cause constant MAC move moves. I.e., local site, remote site, local site, etc. Point number 1 is accomplished using a VLAN ACL on the OTV Edge Devices to filter the respective traffic depending on which FHRP protocol used. To prevent the virtual MAC addresses from causing MAC moves and allow for a cleaner design, an OTV route-map must be configured. This route-map must match the virtual MAC of the FHRP protocol used.   You have to make MAC ACL and IP ACL extended. On the Nexus, it appears that IP and MAC filtering cannot be done simultaneously on Layer 2 interfaces (cf. “mac packet-classify”). So the best bet appears to be using VACLs on Nexus, which is where most of us will likely be doing this sort of thing.   Once you can share your HSRP details I can help you out in making the ACLs. You can refer following link for further reading.   http://www.cisco.com/c/en/us/td/docs/solutions/Enterprise/Data_Center/DCI/whitepaper/DCI3_OTV_Intro/DCI_1.html#wp1186074   Best Regards   Sachin Garg ... View more

Hi Scott,   Could you please share the network diagram along with the configuration, so that I can help you further.     Best Regards   Sachin Garg ... View more

Hi ci-ralarcon,   Could you please send a more detail diagram  of your network setup mentioning the interface details.(in MS visio if you have and then zip it or else I will create one in case you dont have)   I am checking your configuration right now.   Best Regards   Sachin Garg ... View more

Hi jbeaulau,   Could you please confirm if yur issue has been resolved or not.   If resolved , kindly rate !!   Best Regards   Sachin Garg ... View more

I think UCS-MR-2X082RY-B= is not compatible with UCS C200: Check below:   http://www.cdw.com/shop/products/Cisco-DDR3-16-GB-2-x-8-GB-DIMM-240-pin/3470266.aspx   UCS-MR-2X082RY-B= is only  Compatible With:   Cisco UCS B250 M2 Extended Memory Blade Server Cisco UCS C250 M2 Extended-Memory Rack-Mount Server     Cisco - DDR3 - 16 GB : 2 x 8 GB - DIMM 240-pin Mfg. Part: UCS-MR-2X082RY-B= | CDW Part: 3470266 | UNSPSC: 43201402     DDR3 16 GB : 2 x 8 GB DIMM 240-pin 1600 MHz / PC3-12800 1.35 / 1.5 V registered ECC for UCS B250 M2 Extended Memory Blade Server C250 M2 Extended-Memory Rack-Mount Server Availability: 6-8 days Orders placed today will ship within 8 days $484.99 Advertised Price   This item is currently unavailable to purchase online. Please contact us to place this order. Sales Assistance 800.800.4239 Mon-Fri 7am-7:30pm CT Send E-Mail Answer within 24 hours. Lease Option ( $15.13 /month)   Product Overview     Product Overview Main Features DDR3 16 GB : 2 x 8 GB DIMM 240-pin 1600 MHz / PC3-12800 1.35 / 1.5 V registered ECC for UCS B250 M2 Extended Memory Blade Server C250 M2 Extended-Memory Rack-Mount Server       Technical Specifications Specifications are provided by the manufacturer. Refer to the manufacturer for an explanation of the print speed and other ratings.   Header               Brand:   Cisco       Compatibility:   PC       Manufacturer:   CISCO DS HARDWARE DIRECT       Packaged Quantity:   1       Product Line:   Cisco             Miscellaneous               OEM Manufacturer Equivalent Part Number:   Cisco UCS-MR-2X082RY-B             RAM               Chips Organization:   X4       Data Integrity Check:   ECC       Form Factor:   DIMM 240-pin       Memory Specification Compliance:   PC3-12800       Memory Speed:   1600 MHz       RAM Features:   Dual rank , Low Voltage       Registered or Buffered:   Registered       Storage Capacity:   16 GB       Supply Voltage:   1.35 / 1.5 V       Technology:   DDR3 SDRAM       Type:   DRAM       Upgrade Type:   System specific             Memory Module               Capacity of Module in Kit:   8 GB       Modules in Kit:   2             Miscellaneous (CDW)               Compatible With:   Cisco UCS B250 M2 Extended Memory Blade Server Cisco UCS C250 M2 Extended-Memory Rack-Mount Server   Please rate if you find this information useful to you.   Best Regards   Sachin Garg ... View more