2 units of N2K-C2348UPQ running for months and today one of unit failed. On chasis "STAT" LED it is solid amber color and  all the ports  LED solid amber on. I had rebooted , by power cycle but no help.   How to tell was it booting / hang or it is overtemperature ?? Any other troubleshooting guide to confirm this N2K is still working or need RMA? Note: power supply confirm in working condition.   https://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus2000/hw/installation/guide/nexus_2000_hig/LEDs.html STAT: On (amber) The module is booting or running diagnostics. An overtemperature condition has occurred. The temperature threshold has been exceeded by a small value during environmental monitoring.   Port: Solid on (amber) The module or port is disabled through the CLI command or the module is initializing. ... View more

Common setup of vPC is setup peer-link and heartbeat link between 2 unit of N5K switches. FEX switch will have uplink to N5K-1 and N5K-2 , with vPC configure.   I have very unusual question.   Can we setup vPC with only single N5K? and N2K FEX only connect to N5K-1. reason is the secondary N5K-2 is not availalble now, but will add in N5K-2 in future. But I want to do pre-configuration on N5K-1, the vPC configuration. So when N5K-2 is available , I can just connect (heartbeat & peer link) N5K-2 to N5K-1 , then configure vPC on N5K-2. N2K then add anohter uplink to N5K-2. When hearbeat & peerling is up then N5K-2 will resume as secondary vPC. Without have to change/add  the vPC configuration on N5K-1    Today I tried configure N5K-1 with vPC to N2K FEX. But the vPC won't come  up.   fex 100 pinning max-links 1 description "fex100-1"   vpc domain 100 role priority 100 peer-keepalive destination 172.24.97.11 source 172.24.97.10 peer-config-check-bypass delay restore 15 auto-recovery   interface port-channel1 description vPC peer-link switchport mode fabricpath spanning-tree port type network vpc peer-link   interface port-channel100 switchport mode fex-fabric fex associate 100 vpc 100   interface Ethernet1/9 description fex100-1 switchport mode fex-fabric fex associate 100 channel-group 100 ... View more

While pre-provision the N2K switch on new N5K, the exact model number N2K-C2248TP-1GE I had is not available. The closer model I can configure are N2K-C2248TP-E-1GE and N2K-C2248TP   Will it give us any issue when the exact model of hardware is not configure.   slot 100 provision model N2K-C2248TP-E-1GE slot 101 provision model N2K-C2248TP-E-1GE     Thanks. ... View more

refer to following url for the configuration sample. http://www.cisco.com/en/US/docs/routers/crs/software/crs_r4.3/lxvpn/configuration/guide/vc43vpls.html#wp1323265 I would like to understand what is the purpose or explanation of the use of the generic-interface-list It is a must to define generic-interface-list on interface pw-ether ? generic-interface-list il1   interface gig0/1/0/0   interface gig0/2/0/0 generic-interface-list il2   interface gig0/1/0/1   interface gig0/2/0/1 interface pw-ether1   ipv4 address 10.1.1.2/24   attach generic-interface-list il1 interface pw-ether2   ipv4 address 10.1.2.2/24   attach generic-interface-list il2 l2vpn   xconnect group pwhe    p2p pwhe1     interface pw-ether1     neighbor 100.100.100.100 pw-id 1    p2p pwhe2     interface pw-ether2    neighbor 100.100.100.100 pw-id 2 ... View more

Hi, In IOS 12000 router, interface can configure to increase the hold-queue. Once upgrade to IOX , the command is no longer available. I am facing the interface input drops, in IOS I can increased the input hold-queue to solve the problem. But in IOX, no such command available. How can increased the interface hold-queue ? In IOS: interface GigabitEthernet2/0/7      hold-queue 1500 in      hold-queue 1500 out ... View more

Reason to do so is because the IP is running out, need to additional subnet. All the ISP is eBGP peering with each other in one VLAN, but due to growing number of ISPs the IP is running out and new subnet is added as secondary IP in VLAN. But the peering cannot up because the BGP local IP is alway bind to primary IP, not secondary IP. Is there way to force it to use secondary IP as source address during BGP peering R1 === interface GigabitEthernet2/0 ip address 100.1.1.1 255.255.255.252 secondary ip address 10.1.1.1 255.255.255.252 negotiation auto ! router bgp 10081 no synchronization bgp log-neighbor-changes neighbor 100.1.1.2 remote-as 4818 neighbor 100.1.1.2 update-source GigabitEthernet2/0 no auto-summary R2 === interface GigabitEthernet2/0 ip address 100.1.1.2 255.255.255.252 secondary ip address 10.1.1.2 255.255.255.252 negotiation auto ! router bgp 4818 no synchronization bgp log-neighbor-changes neighbor 100.1.1.1 remote-as 10081 neighbor 100.1.1.1 update-source GigabitEthernet2/0 no auto-summary *Aug 12 22:06:21.331: BGP: 100.1.1.2 open active, local address 10.1.1.1 *Aug 12 22:06:21.423: BGP: 100.1.1.2 read request no-op *Aug 12 22:06:21.431: BGP: 100.1.1.2 open failed: Connection refused by remote host, open active delayed 23553ms (35000ms max, 60% jitter) ... View more

Hi, I try to match the route learned with RD 10081:84 , and then set the weight to 100. I can't find the keyword RD at ip extcommunity-list, only SOO and RT. Can guide is there other way to perform it ? What I try to achive is to manipulate the  weight of route learn from PE with RD 10081:84 ip extcommunity-list 10 permit soo 10081:84 route-map gngp permit 10 match extcommunity 10 set weight 100 router bgp 10081 o synchronization bgp router-id 172.18.255.16 bgp log-neighbor-changes neighbor 172.18.255.250 remote-as 10081 neighbor 172.18.255.250 update-source Loopback0 no auto-summary ! address-family vpnv4   neighbor 172.18.255.250 activate   neighbor 172.18.255.250 send-community both   neighbor 172.18.255.250 route-map gngp in exit-address-family KKBPE2#sh bgp vpnv4 unicast rd 10081:84 BGP table version is 104, local router ID is 172.18.255.16 Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,               r RIB-failure, S Stale Origin codes: i - IGP, e - EGP, ? - incomplete    Network          Next Hop            Metric LocPrf Weight Path Route Distinguisher: 10081:84 *>i172.18.188.0/24  172.18.255.202           0    100      0 ? ... View more

I have some issue with IOX Tacacs+ client at public domain, pointing to ACS at internal network, both ACS ia NAT by firewall. Please refer to attached diagram. When user login into the IOX device, it sucessful login but was not assgined with any usergroup. Therefore the user suppose to get let say usergroup root-system, it not assigned with any usergroup at all. So the user cannot even show run ( show run do not show any vonfig) This problem do not appear at Internal IOX device, where it does not go thru firewall.Only IOX client in front of firewall pointing to ACS public NATted IP. What can it goes wrong here ? Firewall need to open additional other application port ? So far tcp/49 is allow from public. Regards ... View more