That 3K and 9K platforms don't really have a notion of software switching. If it can't be programmed in the forwarding ASIC then it's not forwarded. There are a couple of minor exceptions but for standard unicast/multicast forwarding it's going to either go in hardware or not at all.
This, incidentally, is why the number of ACL's supported on these ...
For your first question, enable 'peer-gateway' under the VPC domain settings. This allows for directed ping forwarding over the VPC peer-link.
With core Nexus VPC peers, it is also recommended to set 'peer-switch' under the VPC domain settings and set their STP priorities for VPC vlans to the same values.
For your second question, HSRP is configured ...
The default-class uses (by default) 50 percent of the available bandwidth. You can reduce that value as part of your policy-map. For example:
policy-map type queuing TA-queuing
class-type queuing class-default
While most devices probably have a single physical control plane, others may have two or both layers may be differentiated in software with two logical control planes. I guess there's no single answer...
The Nexus 7000 series has a physically distributed control plane assembled into one logical unit, see https://www.cisco.com/c/en/us/support/docs/switches/...
Here is a generic example:
ip prefix-list TO-A seq 10 permit 22.214.171.124/23 le 32
ip prefix-list TO-B seq 10 permit 126.96.36.199/23 le 32 ! the 'le 32' allows smaller subnets of that block
router bgp 200
ip prefix-list TO-A out
ip prefix-list TO-B out
After reboot switch it fixed my issue, Now its showing SFP Type 10Gbase-SR
n3k# show int e1/49 capabilities
Type (SFP capable): 10Gbase-SR
Trunk encap. type: 802.1Q
Look like you need to set ...
It appears that the Nexus 3172 can only do QoS MTU, not per port MTU.
Configure and Verify Maximum Transmission Unit on Cisco Nexus Platforms
Layer 2 MTU Configurations
Layer 2 MTU is set either through a network Quality of Service (QoS)
policy or by configuring the port itself (on switches that support
per-port MTU). Only the Nexus 7K, 9K, and ...
In the Cisco Nexus 3048 Switch Data Sheet in table 3 you can see this:
(sorry for the image I cannot get the formatting right with a text paste)
So without specific license you get basic features with the system default. That is layer 2 features.
The switch may have been shipped with a base license, required for layer 3 (routing) features but you should ...
I think I set the path to this answer in the other thread, it took me some time to follow it through.
... when a non-portfast port (regardless if individual or port-channel) goes "FWD", a spanning-tree topology change notification runs through the pertaining spanning tree(s).
See this part of the document: Understanding Spanning-Tree Protocol ...
I don't think that peer-gateway is needed on SW-3 at all, as it serves somewhat of a corner case (see below), only useful if the the given nexus has SVIs (interface vlan XXX) and acts as default gateway for the said VLANs and there are special devices in that VLAN. As I understand your diagram and text, this not the case for SW-3.
While I suggest turning ...
Do I need to add update-source loopback0 in BGPconfig and why?
Yes, otherwise the router will use the closest interface, which would be either f0/0 or f0/1. The BGP process is expecting the BGP packet's source address to be the one listed in the neighbor statement, so the peering will never form. You also need to have IGP routing so that your loopbacks ...
(Quote from documentation)
Atomic ACL Updates
By default, when a ...
Yes. Looks like your ping syntax is wrong. To verify, exit the TCL shell and trying running the same ping command from your script substituting in an appropriate value: ping vrf XYZ 10.xx.xx.1
You will likely receive the exact same error message. Rather your command should look more like: ping 10.xx.xx.1 vrf XYZ.
You can also try something like ...
It is always recommended in BGP best practices to peer with loopback addresses for iBGP peers as we no longer have to rely on a single physical interface (or in your case a VLAN SVI) to be up/up. As Ron mentioned, using a loopback address should always be used for device services (SNMP, NTP, Remote access etc) and to assist with identifying the device when ...
The only circumstances under which you'd have the same address on two different boxes are various flavors of anycast and HSRP/VRRP. This definitely does not include routing protocols. In your scenario the customer router would need to have sessions to both 3K's and, of course, the 3K's would need to have distinct address. This would likely push you to ...
It actually depends on the NX-OS version running on the switch (and hence the switch model). Starting with version 6.0(2)N2(1), the default interface command has been added to the nexus world. Compare the release notes of this version.
As far as I know, previous versions do not support this or any similar command.
However you won't be able to run NX-OS 6 ...
The thing is the Nexus 2000s aren't autonomous switches. They are essentially line cards for the 5ks (or 7ks) and have no independent existence, so you can't run the normal protocols across those fex-fabric links.
To my knowledge, you simply can't run UDLD across a fex-fabric port (there's even a bug, CSCub14112, related to the fact that the UDLD config ...
The 5600-series can switch 40G at line rate (...as in full 40Gbit/s flows) but won't ever be able to switch full 100G interfaces (nb - fabric is limited to 40G flows). The 5500 can only support 40G in a 4x10G mode (...no flow over 10Gbit/s). The 50x0 is strictly 10G only.
Unless you actively need certain features (specifically native FC termination or ...
It depends on whether you have a vPC between the aggregation and core layers.
If the connection between (A1, A2) and (C1, C2) is a vPC, then the switch always prefers "local forwarding". That is, any packet that is received on A1 will be sent to C1, and any packet that is received on A2 will be send to C2. The idea is to have the packet pass through only ...
I was able to Goole the answer in less time than it took for you to write the question:
Configure the FTP username and password.
CE_2(config)#ip ftp username cisco
CE_2(config)#ip ftp password cisco123
From Back up and Restore Configuration Files
This command was missing in e1/27 interface.
spanning-tree port type edge trunk
Full interface output look like following.
description Connected to server
switchport mode trunk
switchport trunk allowed vlan 10,20,30,100
spanning-tree port type edge trunk
spanning-tree bpduguard enable
I don't think there are any 10G linecards/modules for the CAT6500 that directly support SFP+ modules.
WS-X6700 Series: https://www.cisco.com/c/en/us/products/collateral/switches/catalyst-6500-series-switches/product_data_sheet09186a00801dce34.html
Usually Nexus have this config section:
policy-map type network-qos jumbo
class type network-qos class-default
service-policy type network-qos jumbo
While this works and enables a Nexus for jumbo frames at L2, I personally consider it a bad example of config item naming, as the term "jumbo" is misleading as to what it is ...
In my case, I was able to solve the problem by turning on these debugs on Nexus9000_2:
debug spanning-tree rstp interface eth1/54
debug spanning-tree event interface eth1/54
debug spanning-tree bpdu_rx interface eth1/54
The next time a BPDU triggered a calculation, the debug gave me detailed information on what was happening on the switchport.
The output ...
SW3 is a switch. By first principle, portfast [trunk] or port type edge [trunk] should not be enabled on ports that connect to switches, lest you risk loops if that other switch connects to some other upstream switch.
There are exceptions to this rule, but they require solid knowledge and understanding by the network admin.
Usually, deployment of edge ...