Hi all; quick question although I think I know the answer. creating a rep segment from ie5000-1 to an ie2000 with the segment ending on a second ie5000-2. at the moment, the "ring" back to the 2nd ie5000 is not terminated yet.   ie5000-1 g1/19 seg # primary ie2000     g1/1 seg # edge ie2000     g1/2 seg # edge (non-functional at this time) ie5000-1 g1/19 seg # preferred (non-functional at this time)   However, although the SFP is in ie2000 g1/2 port, there is no connectivity at this time (ring not complete yet)   in an effort to try and get the one part of the segment to function, it does not. Rep segment gets created but "sho rep top set # FAILED" although I can still ping and access the switch. So..just wonder if the fact there really isn't a third port to make this rep segment complete, of course it would fail? Does the segment expect to see a port when it is indeed in the same segment but not functional?   is there a way to allow this to communicate over just two ports? and once the fiber termination happens we will complete/extend the ring?   or...there is NO ring with only two ports?   tia   Howard     ... View more

Not ready for prime time. Try again. Does not load my "Community" Fail. When trying to do so, it gets to "processing discovered devices" and stays there. Program frozen. Created a "NEW" Community. Add device one at a time, by the time I try adding the third, crash and burn, frozen, discovering devices again...FAIL. Unusable product. Probably on purpose as well...after all it's FREE and what do you expect for FREE?? "insert operative F word here.....multiple times if needed" Try again maybe. This time.....don't put the same programer from Microsoft on this project. Plus its programmed using Java...another fucking mistake. I will now move on an use a product from HP to manage my Cisco.....Hahah what a joke. Cisco...your broken much like Microsoft is. FAIL ... View more

Hi all; Cisco newby, but I am managing pretty good so far. However, I do need a little direction on this one. I am implementing a Watchguard "FireCluster" in an Active/Active configuration. From the Watchguard doc's, they say the following: ""All switches and routers in an active/active FireCluster broadcast domain must meet these requirements. All switches and routers in the broadcast domain must not block ARP requests if the response contains a multicast MAC address. This is the default behavior for most layer 2 switches. For routers and layer 3 switches, the default behavior is to follow RFC 1812, which says that the router must not believe any ARP reply that claims that the Link Layer address of another host or router is a broadcast or multcast address. If possible, disable this behavior. If you are unable to block RFC 1812 support, you might need to configure static MAC and static ARP entries on your routing device."" One one side of this Watchguard is my Cisco switches (PLC network) and the other side is my HP switches (Corp Network). Cisco side has: (all Lan Base) 2 x 2960x (v15.0(2a)EX5-UniversalK9 - Stacked 2 x IE5000 (v15.2(2)EB1 (Cryto) Universal 23 x IE2000 (v15.0(2)EA-1-UniversalK9 HP side has: 20 or so more switches but the Core is: 4 x A5500-4SFP-HI (IRF) Would someone like to elaborate on how this can be accomplished? Do I have to create entries on each and every switch in the broadcast domain manually, once I get pointed in the right direction and know what I need to do? Any input or advice would be much appreciated. Thank you ... View more

I am running CNA 6.2 and all was good with the following switches. IE-2000 (x25) switches, 2960-x (x3) switches and IE-3000(x 3) switches all playing nice. Found out that Cisco mis-advertised/represented the capabilities of the IE3000 (No EDS File for creating tags) although this is an "Industrial Switch" Took about 4 weeks to convince them of this fact because of course all doc's say that it can/does support EDS, but this has been proven FALSE! Even had me upgrade/down grade software checking for the EDS file....Not there period. So, we are swapping out these IE3000 and going with IE5000. However, even tho all documents that I can find say that CNA can manage this switch, it cannot ("un-supported device"). So...more mis-direction from Cisco. Twice in as many months. Not a happy camper with Cisco. When will these switches IE-5000-16S12P be supported in CNA, considering the documentation states that it already DOES?? Link that also states this fact: http://www.cisco.com/c/en/us/td/docs/switches/lan/cisco_ie5000/software/release/15-2_2_eb/configuration/guide/scg-ie5000/swintro.pdf Thanks in advance. ... View more