Hello all, just trying to use the labs to learn more about connecting to the API and when trying to connect to our own APIC API, I get the following: This is an APIC running 1.1(3f). thanks, James ... View more

All, I am wanting/needing to connect to the blade server CIMC through an inband IP connection, and have created a pool for that, and a VLAN group and made all the necessary changes, and can KVM to the server, so everything is working right, but what is happening is that when I associate the SP to the blade, the blade is coming up with two IP's assigned both for inband and for outband. My SP specifically states to use the pool for inband and 'none' for outband. Does anyone know why the blade is getting two IP's assigned for both inband and outband?   Any help would be appreciated...thanks. ... View more

All,   I'm looking for a bit of clarity on the resource limitation for policy-maps on the Nexus 1000v. From the docs (http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus1000/sw/4_2_1_s_v_2_2_1_a/release/notes/n1000v_rn.html#pgfId-64826) it seems pretty clear, however, when I look at my modules on the 1k, there are differing numbers of 'instances' where the same policy map is applied to our management uplinks.   As an example, we have a policy-map attached to our management uplinks (consisting of two Eth uplinks bundled into a PC), and we can see this output below: atl2-vsm-01# sh resource-availability qos-queuing Maximum number of instances per DVS is 4096 The number of instances created is 1116 The number of instances available is 2980 Maximum number of instances per module is 300 Following table shows the per module instance usage ---------------------------------------------------------------- Module  Used  Available ----------------------------------------------------------------      3    16   284      4    25   275      5    20   280      6    19   281   The same policy-map is applied to each one of those modules, and is attached to the same number of management uplinks for each module, however the 'used' column is what's throwing me a curve.   1. When the output references 'instances' do those instances correlate with the 'used' column in the table that references the 'per module' (I know this seems obvious from the output). 2. If the same policy-map is applied to each of these modules, and is applied to the same two Eth uplinks, howcome the 'used' column varies per host?   We are a Service Provider and have a large customer footprint, and I'm attempting to find a solution where we can to rate-limiting for customers in our environment based on the customers purchased CIR, however there seems to be scalability issues regarding using policing on the 1k, so I'm looking for any insight into how to solve this problem.   Thanks in advance for any help provided.   James ... View more

All, We've set a custom loging prompt under System Administration > Configuration > Global System Options > TACACS+ Settings On our IOS switches/routers, we are getting our custom login prompt sent, but the NXOS devices are not receiving this same prompt. I've tried with telnet, and ssh, but the result is the same. Does anyone know what may be causing this? ... View more

All, In troubleshooting an issue with output drops on one of our switches attached to a customer, one of our engineers used the information in the 'show interface gix/x' as a guide for the queue size. The section that i'm describing is this: GigabitEthernet1/30 is up, line protocol is up (connected) <output omitted>   Queueing strategy: fifo   Output queue: 0/40 (size/max) The customer asked our engineer if he could increase that value of 40. I came across the ticket, and lent a hand and explained that the 4948 uses hardware queues, and we can see these here: clt3-access-13#sh platform hardware interface g1/30 tx-queue Switch Phyport Gi1/30 Tx-Queue Hardware State Phyport TxQ   High     Shape      Share     Shape        Share          Curr             Priority Mant. Exp. Mant. Exp. NextTime     NextTime        Time ------------------------------------------------------------------------------- Gi1/30  0   Disabled  0    0     45   16  0x11B1D00D4   0x11B1D00D4   0xAB97B6383 Gi1/30  1      -      0    0     45   16  0xAA3506F73   0xAA3507324   0xAB97BAAB8 Gi1/30  2      -      0    0     45   16  0x11B1F99F3   0x11B1F99F3   0xAB97BEF88 Gi1/30  3      -      0    0     45   16  0xAB97B7DCD   0xAB97B8B12   0xAB97C3327 Phyport TxQ  Head    Tail   Full   Not   Num    BaseAddr   Size                                   Empty Packets --------------------------------------------------------------- Gi1/30  0   0x0000  0x0000  False False   0      0x20800   2080 Gi1/30  1   0x03C5  0x03C5  False False   0      0x21020   2080 Gi1/30  2   0x0000  0x0000  False False   0      0x21840   2080 Gi1/30  3   0x0070  0x0070  False False   0      0x22060   2080 My question is two part really. First off, why does the output in the show interface have the output queue as 40 when it's obviously not being used(if I remember correctly, this had to do with router interfaces)? My other question, is that the QoS documentation for the 4948 is here (apparently the 4500 docs are what is supposed to be used): http://www.cisco.com/en/US/docs/switches/lan/catalyst4500/12.2/15.02SG/configuration/guide/qos.html#wp1463316 But I can find no refereence to the timeframe that these queues get serviced. This is important to me because when I look at the queue's for the interface: clt3-access-13#sh qos interface g1/30 QoS is enabled globally Port QoS is enabled Administrative Port Trust State: 'untrusted' Operational Port Trust State: 'untrusted' Trust device: none Default DSCP: 0 Default CoS: 0 Appliance trust: none Tx-Queue   Bandwidth   ShapeRate   Priority   QueueSize              (bps)       (bps)                (packets)   1        250000000   disabled    N/A        2080       2        250000000   disabled    N/A        2080       3        250000000   disabled    normal     2080       4        250000000   disabled    N/A        2080 I'm thinking that that packet count can easily get overrun. If we do the math real quick, and say we use a 1500 byte packet, and use the formula (1500*2080)8, we end up getting 24960000, which is much lower than 250000000. So I'm a bit confused on the correlation between the queue size regarding packets, and the bandwidth. This is why I was asking about the timeframe that the above rates are referencing, because it would seem to me that you would have to have quite a bit more than 2080 (standard size packets) to accumulate 250 Mbps of traffic, not to mention that a queue limit of 2080 packets may seem like alot, but we have customer links that are showing pps well in excess of 4000 with no output drops, which again leads me to believe that the packet count shown above is for a timeframe that is shorter than a second. Does this make sense? Any help is appreciated, James ... View more

All, We are experiencing an issue with some virtual Kemp LB's in our environment where they are not functioning properly with regard to multicast, and their HA. We came across a doc that seems to point to a possible solution: https://supportforums.cisco.com/thread/2013429 I'm no multicast wizard, but one thing that's throwing me is this whole concept of specifying a querier within the VLAN. I am assuming that there has to be a layer 3 device in that VLAN (specified by the IP address of the querier) to perform this function? Can someone explain the nuances regarding the querier?, or if anyone has had any similar issues in the UCS environment when dealing with muticast, I'd appreciate any information you could provide. ... View more