Cisco IE-3000-8TC switches and CNA

A colleague of mine has installed a set of 3 Cisco IE-3000-8TC switches which look like they have had a minimal amount of configuration applied to them, and I have now been asked to integrate them into a CNA community.
I can;
ping them and get replies
connect to them through telnet
connect to them with a web browser
I can create a community and the 3 switches are detected as shown in the attached file, CreateCommunity.png
However, when I try to connect to the newly created community CNA returns the error –1, as shown in the attached file, CommunityError.png
It then hangs at 83% Processing discovered devices…
Has anyone out there had experience of integrating these switches into CNA?
What do I need to do to them?

Similar Messages

Cisco IE-3000 8TC doesn't recogze 4SM fiber sfp module

Have a few Cisco IE-3000 8TC switches with the 4SM FIber SFP expansion modules. The switches do not discover these ports at all. I'm assuming that thhere is a fix or firmware upgrade, would appreciate any help.

Isgabrillo, Please see below.
I wasn't able to see a PID for the SFP's, but they are Cisco GLC-FE-100LX
THe switch doesn't seem to recognize the 4SM module that is currently attached. As I stated, I have a few already installed in the field that I am not able to contact right now, but have the same issue. I think I read in a blog somewhere that someone had the same issue and there was an IOS update that cured it.
Switch#sh inv
NAME: "1", DESCR: "IE-3000-8TC"
PID: IE-3000-8TC       , VID: V03 , SN: FOC1826Y36B
NAME: "IE-3000-8TC - Module in slot 1", DESCR: "IE-3000-8TC - Module in slot 1"
PID: IE-3000-8TC       , VID: V03 , SN: FOC1826Y36B
Switch#dir flash
%Error opening flash:/flash (No such file or directory)
Switch#sh version
Cisco IOS Software, IES Software (IES-LANBASEK9-M), Version 12.2(58)SE2, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2011 by Cisco Systems, Inc.
Compiled Thu 21-Jul-11 00:59 by prod_rel_team
ROM: Bootstrap program is Xmen2 boot loader
BOOTLDR: IES Boot Loader (IES-HBOOT-M) Version 12.2(44r)EX5, RELEASE SOFTWARE (fc1)
Switch uptime is 4 minutes
System returned to ROM by power-on
System image file is "flash:/ies-lanbasek9-mz.122-58.SE2/ies-lanbasek9-mz.122-58.SE2.bin"
This product contains cryptographic features and is subject to United
States and local country laws governing import, export, transfer and
use. Delivery of Cisco cryptographic products does not imply
third-party authority to import, export, distribute or use encryption.
Importers, exporters, distributors and users are responsible for
compliance with U.S. and local country laws. By using this product you
agree to comply with applicable laws and regulations. If you are unable
to comply with U.S. and local laws, return this product immediately.
A summary of U.S. laws governing Cisco cryptographic products may be found at:
http://www.cisco.com/wwl/export/crypto/tool/stqrg.html
If you require further assistance please contact us by sending email to
[email protected].
cisco IE-3000-8TC (PowerPC405) processor (revision S0) with 131072K bytes of memory.
Processor board ID FOC1826Y36B
Last reset from power-on
1 Virtual Ethernet interface
8 FastEthernet interfaces
2 Gigabit Ethernet interfaces
The password-recovery mechanism is enabled.
64K bytes of flash-simulated non-volatile configuration memory.
Base ethernet MAC Address       : 50:67:AE:72:AE:00
Motherboard assembly number     : 73-15595-01
Motherboard serial number       : FOC18258RWT
Model revision number           : S0
Motherboard revision number     : A0
Model number                    : IE-3000-8TC
System serial number            : FOC1826Y36B
Top Assembly Part Number        : 800-28538-03
Top Assembly Revision Number    : A0
Version ID                      : V03
CLEI Code Number                : CMMFE00ARB
Hardware Board Revision Number : 0x02
CIP Serial Number               : 0x8E72AE00
SKU Brand Name                  : Cisco
Switch Ports Model              SW Version            SW Image
*    1 10    IE-3000-8TC        12.2(58)SE2           IES-LANBASEK9-M
Configuration register is 0xF
Switch#exit
Switch#dir flash:
Directory of flash:/
736 -rwx        3096   Mar 1 1993 00:00:55 +00:00 multiple-fs
    2 drwx        1024   Mar 1 1993 00:06:38 +00:00 ies-lanbasek9-mz.122-58.SE2
732 -rwx         676   Mar 1 1993 00:07:33 +00:00 vlan.dat
733 -rwx        1915   Mar 1 1993 00:00:58 +00:00 private-config.text
735 -rwx        1424   Mar 1 1993 00:00:58 +00:00 config.text
64094208 bytes total (45407744 bytes free)
Switch#exit

Cisco CSS 11150 Series switch and DNS Sticky

Hi,
I have currently have two internet independent facing CSS11154 switches with two web server farm environment across both of them.
I have a single URL that round robins between my internet facing links for these server farms.
The application is based on ssl connectivity to a web farm, because of the application and need to maintain session transactions, I have needed to use advanced-balance stick-srcip.
When using one leg (internet link) it works fine, no problem and visa versa.
However, when I turn both of them on my application fails.
Would I need to incorporate DNS Sticky to resolve my issue ?
This is one of the configs from one of the CSS Switches, the other has a similar config different servers.
!*************************** GLOBAL ***************************
acl enable
date european-date
dns-server
app
app session 10.1.1.1 14 authChallenge ebe encryptMd5hash
!************************** SERVICE **************************
service Server01
ip address 10.140.80.45
port 443
protocol tcp
active
service Server02
port 443
protocol tcp
ip address 10.140.80.47
active
service Server03
port 443
protocol tcp
ip address 10.140.80.53
active
service Server04
ip address 10.140.80.54
port 443
protocol tcp
active
!*************************** OWNER ***************************
owner HOME
dns both
content www-home.com
vip address 192.168.0.1
add dns www.home.com
add service Server01
add service Server02
add service Server03
add service Server04
advanced-balance sticky-srcip
active
Many Thanks !
Any view would be most helpful

looks like you will need dns sticky indeed.
To be 100% sure you should capture a sniffer trace of a failure.
But most probably this is a dns sticky problem.
Follow this link for sample configuration of dns sticky.
http://www.cisco.com/en/US/products/hw/contnetw/ps789/products_configuration_guide_chapter09186a0080176f6f.html
Regards,
Gilles.

SF302-08P small buisiness switch with CNA

I've been using the CNA for our 3560X type switches and really like it.
I saw the lastest version would support the Sx300 switches.
I tried it on some of our SF302-08P switches and it worked great!
But then I tried it on a new one, with newer firmware (1.3.7.18) I got a connection error (said something about not specifying a host name with DNS, but I didn't copy it all down).
Anyone know if that version of firmware has an issue with the latest CNA? (6.1)
I also couldn't update the firmware on the switch to the 1.4.x firmware on the cisco site. Said a mismatch.
Mark

Hi,
Thanks for the response.
the firmware is for the SF302-08P switches.
I use the latest CNA to connect with other 302 switches (older firmware) but not this one with the newer firmware.
That was what I was trying to find out. Is there an issue with the 1.3.7.18 firmware on the 302 switches AND CNA.
Or if possibly I'm doing something else wrong (certainly probable)
thanks
mark

CiscoWorks user options "device type groups|switch and Hubs"

Hi,
We are using CiscoWorks software to deploy new configuration to our network devices. Because our environnement is mixed about version of network devices we have to create a new netconfig job for each device model, because in some plate-forme configuration option, syntax maybe different of each other.
When I create a new netconfig job with my username under "device type groups|switch and Hubs" I have a list there of all plate-forme we have in our production environnement managed by CiscoWorks software. I know thoses group was'nt define by on of us and thoses are define by default in CiscoWorks software, but they are hiden by default per user basic.
We have a new one in our team, I had created his user name and password, but I can find the option where I can asked to make visible to him plate-form device type group as I have in my user configuration.
Also, is it possible to copy private define group to an other user without to make thoses as public ?
Thanks a lot !

Here,
is a view of what I have with my user
but in his profile he is only see
Device type Groups
     + Routers
     + Switches and Hubs
     + Wireless
if he clic on the plus sing to develop group "Switches and Hubs" he see all switches and hub managed by CiscoWorks software. I know He did not create Cisco Catalyst 2912 XL Switch and Cisco Catalyst 2924 XL Switch group in my profile. I know we have to modify an option in CiscoWorks per user basic to view those group, the person who where that option should be modifiy is currently in vacation, but he will need that option enable before our specialist will be back !
Thanks a lot !

Connecting two cisco ESW 500 series switches.

Hi Experts,
I have a basic knowledge of network and need some help.
I have two cisco ESW 500 series switches and i want to connect them together.
Q1 # Which type of cable i should use to connect these two switches CrossOver or fiber...What is the advantage of using Fiber over CrossOver. ?
Q2 # What are the marked ports in the image used for...???

tech spec,
Traditionally you would use crossover to connect switches. Most modern network devices have Auto-MDIX which allows the device to connect using either crossover or straight through.
The ports on the right can be used for uplink or as regular network ports. On the 10/100 versions the ports on the right are usually Gigabit, thus making them more suitable for uplink to another switch, etc.
Please mark this thread as answered or reply if you have any additional questions.
- Marty

Ask the Expert: Different Flavors and Design with vPC on Cisco Nexus 5000 Series Switches

Welcome to the Cisco® Support Community Ask the Expert conversation. This is an opportunity to learn and ask questions about Cisco® NX-OS.
The biggest limitation to a classic port channel communication is that the port channel operates only between two devices. To overcome this limitation, Cisco NX-OS has a technology called virtual port channel (vPC). A pair of switches acting as a vPC peer endpoint looks like a single logical entity to port channel attached devices. The two devices that act as the logical port channel endpoint are actually two separate devices. This setup has the benefits of hardware redundancy combined with the benefits offered by a port channel, for example, loop management.
vPC technology is the main factor for success of Cisco Nexus® data center switches such as the Cisco Nexus 5000 Series, Nexus 7000 Series, and Nexus 2000 Series Switches.
This event is focused on discussing all possible types of vPC along-with best practices, failure scenarios, Cisco Technical Assistance Center (TAC) recommendations and troubleshooting
Vishal Mehta is a customer support engineer for the Cisco Data Center Server Virtualization Technical Assistance Center (TAC) team based in San Jose, California. He has been working in TAC for the past 3 years with a primary focus on data center technologies, such as the Cisco Nexus 5000 Series Switches, Cisco Unified Computing System™ (Cisco UCS®), Cisco Nexus 1000V Switch, and virtualization. He presented at Cisco Live in Orlando 2013 and will present at Cisco Live Milan 2014 (BRKCOM-3003, BRKDCT-3444, and LABDCT-2333). He holds a master’s degree from Rutgers University in electrical and computer engineering and has CCIE® certification (number 37139) in routing and switching, and service provider.
Nimit Pathak is a customer support engineer for the Cisco Data Center Server Virtualization TAC team based in San Jose, California, with primary focus on data center technologies, such as Cisco UCS, the Cisco Nexus 1000v Switch, and virtualization. Nimit holds a master's degree in electrical engineering from Bridgeport University, has CCNA® and CCNP® Nimit is also working on a Cisco data center CCIE® certification While also pursuing an MBA degree from Santa Clara University.
Remember to use the rating system to let Vishal and Nimit know if you have received an adequate response.
Because of the volume expected during this event, Vishal and Nimit might not be able to answer every question. Remember that you can continue the conversation in the Network Infrastructure Community, under the subcommunity LAN, Switching & Routing, shortly after the event. This event lasts through August 29, 2014. Visit this forum often to view responses to your questions and the questions of other Cisco Support Community members.

Hello Gustavo
Please see my responses to your questions:
Yes almost all routing protocols use Multicast to establish adjacencies. We are dealing with two different type of traffic –Control Plane and Data Plane.
Control Plane: To establish Routing adjacency, the first packet (hello) is punted to CPU. So in the case of triangle routed VPC topology as specified on the Operations Guide Link, multicast for routing adjacencies will work. The hellos packets will be exchanged across all 3 routers and adjacency will be formed over VPC links
http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus5000/sw/operations/n5k_L3_w_vpc_5500platform.html#wp999181
Now for Data Plane we have two types of traffic – Unicast and Multicast.
The Unicast traffic will not have any forwarding issues, but because the Layer 3 ECMP and port channel run independent hash calculations there is a possibility that when the Layer 3 ECMP chooses N5k-1 as the Layer 3 next hop for a destination address while the port channel hashing chooses the physical link toward N5k-2. In this scenario,N5k-2 receives packets from R with the N5k-1 MAC as the destination MAC.
Sending traffic over the peer-link to the correct gateway is acceptable for data forwarding, but it is suboptimal because it makes traffic cross the peer link when the traffic could be routed directly.
For that topology, Multicast Traffic might have complete traffic loss due to the fact that when a PIM router is connected to Cisco Nexus 5500 Platform switches in a vPC topology, the PIM join messages are received only by one switch. The multicast data might be received by the other switch.
The Loop avoidance works little different across Nexus 5000 and Nexus 7000.
Similarity: For both products, loop avoidance is possible due to VSL bit
The VSL bit is set in the DBUS header internal to the Nexus.
It is not something that is set in the ethernet packet that can be identified. The VSL bit is set on the port asic for the port used for the vPC peer link, so if you have Nexus A and Nexus B configured for vPC and a packet leaves Nexus A towards Nexus B, Nexus B will set the VSL bit on the ingress port ASIC. This is not something that would traverse the peer link.
This mechanism is used for loop prevention within the chassis.
The idea being that if the port came in the peer link from the vPC peer, the system makes the assumption that the vPC peer would have forwarded this packet out the vPC-enabled port-channels towards the end device, so the egress vpc interface's port-asic will filter the packet on egress.
Differences: In Nexus 5000 when it has to do L3-to-L2 lookup for forwarding traffic, the VSL bit is cleared and so the traffic is not dropped as compared to Nexus 7000 and Nexus 3000.
It still does loop prevention but the L3-to-L2 lookup is different in Nexus 5000 and Nexus 7000.
For more details please see below presentation:
https://supportforums.cisco.com/sites/default/files/session_14-_nexus.pdf
DCI Scenario: If 2 pairs are of Nexus 5000 then separation of L3/L2 links is not needed.
But in most scenarios I have seen pair of Nexus 5000 with pair of Nexus 7000 over DCI or 2 pairs of Nexus 7000 over DCI. If Nexus 7000 are used then L3 and L2 links are required for sure as mentioned on above presentation link.
Let us know if you have further questions.
Thanks,
Vishal

Cisco switches and virtual ip address(load balancing address) on xenapp portals

Hi I am quite new in configuring cisco switches and stumble across an issue after installing xenapp7.6 with load balanced portal to the ddc`s
It seems i only can ping or get access to portal if using real ip address behind cisco switch from other subnets in my network.
I can ping ddc01 and ddc02 and connect to the portal with http without problem. However when i triy to access the load balancing address of the ddc`s
it wont answer to ping or http
In same subnett it is no problem connecting to the load balancing address of the ddc`s, but in loactions on other subnets i only can access real server ip
eks
dd01 192.168.1.4 ok ping and access behind cisco switch from subnets
ddc02 192.168.1.5 ok to ping access behind cisco switch from subnets
load balancing for both ddc 192.168.1.6 not able to get answer og access from subnets, only in same subnett
Is there any way to configure switch to access the load balancing address of the ddc`s ?
Regards
Pål Arne Røberg

Wrong forum. This forum is dedicated to feedback related to CSC framework itself. You should not wish for response here.
Moved by moderator, no longer apply.

How to view the login log in window NPS after login cisco switch and without SQL server database

how to view the login log in window NPS after login cisco switch and without SQL server database
in summary
there is only log with event id 4400
A LDAP connection with domain controller XCPAWS20.cyberport.noc for domain NOC2 is established.

Hi adil,
For your issue, you can create a custom security token service (STS) and then set up a trust relationship between a SharePoint 2010 farm and the custom STS.
For more information, you can refer to the articles:
http://forums.asp.net/t/1335229.aspx?Sharing+Authentication+Ticket+Between+ASP+NET+and+Sharepoint
https://msdn.microsoft.com/en-us/library/office/ff955607(v=office.14).aspx
http://www.paraesthesia.com/archive/2011/02/01/working-with-windows-identity-foundation-in-asp-net-mvc.aspx/
Best Regards,
Eric
Eric Tao
TechNet Community Support

Cisco Switches and Dell EqualLogic PS series integration

Scanrio: In head office there is Dell EqualLogic PS series and in branch also same for replicaiotn from head office to branch i want to know the ios feature set of Switch and Router.

If the Dell EqualLogic systems are using iSCSI to communicate there is no specific feature required on the Cisco gear. The Cisco gear will pass iSCSI traffic just like any other IP traffic.
Make sense?
Cheers,
Brad

Cisco switches and 802.1.x

Hi, there !
I have a question for you.
Cisco all switches, is it impossible to present for 802.1x ?
I try to put a network access server in our network to authenticate.
Thanks.
I will wait your answer.
Regards.

Most Cisco switches will handle 802.1x, but it depends on the switch and the OS. Which specific ones are you considering?
Wes

Cisco Architectures for 2950/2960 Switches and 2800 Routers

Hello,
I have a question regarding the architectures of these three series, i.e. the type of switch fabric they use and the general architecture (first, second, or third generation regarding the sharing of the bus, memory and the type of switch fabric). We have so far learned these three generation and our assumption is that the only generation being produced now is the third (crossbar) generation, but so far we have to information to back up this claim. We are doing a study on buffer sizing in edge routers/switches so knowing the exact architecture of each model is our priority.
Thank you for reading and thanks in advance for the answers.

Disclaimer
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
Liability Disclaimer
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
Posting
Exact details on Cisco switch and/or router architecture can be hard to come by, as much of the information, Cisco appears to consider proprietary.
Most switches have some kind of cross bar architecture. Overall bandwidth tends to be higher in later variants (to support higher port densities and/or higher bandwidth ports). Later switch architectures are less likely to block at ports. However, there are often other architecture changes which may improve or worsen performance. For example, 2960 tends to have more fabric bandwidth than the 2950, but the 2960 has different port buffer management (I believe) from the 2950, often resulting in more port drops with bursty traffic.
True routers, like the 2800 series, I believe use a PCI bus, with additional bandwidth restrictions to the modules. They will well support the WAN bandwidths they are recommended for, but they do not well support LAN port bandwidths. Again, specific architecture details can be hard to come by.

Connecting Cisco 2821 Router, Switch, and Cable Modem

Hey everyone,
I am currently in the Cisco Network Academy at my school and just finished CCNA 1. I have a few questions though.
I am purchasing new equipment and that equipment includes:
1-Cisco 2821 2-port Gigabit Router
1-Linksys SE3016 16-Port Gigabit Switch (unmanaged)
1-Cisco WAP4410n Wireless Access Point
1-Motorla SurfBoard Gigabit Cable Modem (no router built in-Just standalone Modem used with Comcast Xfinity High Speed Internet)
1-12U Network Rack (not enclosed)
I am confused on how I will connect the cable modem to the router and the router to the switch and the WAP so that I still have WiFi. Since the router only has 2 Ge Ports, how would I cable this up?
If my assumptions are correct, would I do the following set up?
Take the Cable Modem and run a Straight Thru to Port 1 of the Router.
Connect the Switch Port 1 to Port 2 of the Router using a Straight Thru cable (I believe I will most likely have to Subnet a network, won't I?).
Connect Switch Port 2 to WAP using Straight Thru Cable (so I still have WiFi in my home).
Connect all my computers and other devices to the Switch (this includes several PC's/Laptops, two printers that are ethernet, two TV's that are ethernet, an AppleTV and a Blue Ray Player that are both ethernet, and some Cisco Powerline Network Adapters).
Will that set up work?
Also, how would I configure the router to work with my cable modem AND act as a DHCP Server so that all of my devices get IP Addresses? I have the Cisco Command Guide Book, but it is confusing to me as of now.
Thanks!
Chris

A good start but a few points I would make.
If you set the clock manually, you may find it resets itself after a router reboot. I would look at pointing it at an NTP server:
#ntp server x.x.x.x
#clock timezone GMT (Assuming you are UK based)
Although not required, I would put a description on each of the interfaces as it may help identify them later if you are not physically in front of the Router.
#interface gi0/0
#description WAN
Same for LAN
You have set up your LAN subnet with a /16 subnet mask which is effectively 10.0.0.1 - 10.0.255.254. This is a large subnet allowing over 65k hosts which is not best practice on enterprise networks. It probably won't cause you any issues but I doubt you will have any more than 254 hosts so personally I would use a /24 subnet (255.255.255.0)
The only major thing missing is NAT which needs to be configured on the router to translate the LAN IP addresses from their 10.* private range to the Public IP address on the Gi0/0 WAN Interface.
Firstly you need to define the 'inside' and 'outside' NAT interfaces which is fairly self explanatory:
#interface gi0/0
#ip nat outside
#interface gi0/1
#ip nat inside
Gi0/0 is your outside interface because its facing the Outside world (i.e the internet) and Gi0/1 is your inside interface because its facing Inside your LAN.
Then you need to tell the router which addresses to translate against by first creating an access list:
#ip access-list standard LAN-Addresses
#permit 10.0.0.0 0.0.255.255
Finally you need to tell the router to start translating:
#ip nat inside source list LAN-Addresses interface gi0/0 overload
Oh, I have just noticed that you do not have a 'default route' configured. A router forwards packets by first looking up the destination IP address of the packet (i.e where its going) in it's own routing table. Obviously home routers are not going to have an entry for every Public IP subnet on the internet so they use something called a default route which effectively says 'If I cannot find an entry for this packet in my routing table, use the default route'.
As you are on DHCP and your IP address (and even default gateway) could change on your WAN interface, I would not bother with the next hop address in the default route but rather use the outgoing interface as below:
#ip route 0.0.0.0 0.0.0.0 gi0/0
Hope this helps!

Cisco Prime 2.1.2 auto sync config for switches and Routers

hello Support,
how to configure auto sync config in CPI? when the customer make a changes in the switches and Routers, the customer expect a new version of the configuration in CPI immediately. but we are getting the new version after 10 minutes. if we not configure in the switches and Routers to send syslog we are not getting anything.
where we have to configure in CPI to get the new versions immediately?
thanks!

Make sure you have completed the recommended preparation steps given in Before You Begin Installing the Patch.
If you are not using the Prime Infrastructure High Availability (HA) feature, follow the steps in Installing the Patch instead of the steps below.
If your current Prime Infrastructure implementation has High Availability enabled, follow the steps below to install the patch. You must start the patch installation with the primary server in “Primary Active” state and the secondary server in “Secondary Syncing” state.
Patching of the primary and secondary servers takes approximately one hour. During that period, both servers will be down. If you have trouble at any point, see Troubleshooting Patch Installs in HA Implementations.
Step 1 Ensure that your HA implementation is enabled and ready for update:
a. Log in to the primary server using an ID with Administrator privileges.
b. Select Administration > System Settings > High Availability , The primary server state displayed on the HA Status page should be “Primary Active”.
c. Select HA Configuration . The current Configuration Mode should show “HA Enabled”.
d. The Failover Type must be set to “Manual” throughout the patch installation. If Failover Type is currently set to “Automatic”, select “Manual” and then click Save .
e. Access the secondary server’s Health Monitor (HM) web page by pointing your browser to the following URL:
https:// <ServerIP> :8082
where ServerIP is the IP address or host name of the secondary server.
f. You will be prompted for the authentication key entered when HA was enabled. Enter it and click Login .
g. Verify that the secondary server state displayed on the HM web page is “Secondary Syncing”.
Step 2 Download the patch:
a. Point your browser to the software patches listing for Cisco Prime Infrastructure 2.1.
b. Click the Download button for the Release 2.1.2 patch file (pi212_20141118_01.ubf), and save the file locally.
Step 3 Install the patch on the secondary server:
a. Access the secondary server’s HM web page by pointing your browser to the following URL:
https:// <ServerIP> :8082
where ServerIP is the IP address or host name of the secondary server.
b. You will be prompted for the authentication key entered when HA was enabled. Enter it and click Login .
c. Choose the HM web page’s Software Update link. You will be prompted for the authentication key a second time. Enter it and click Login again.
d. Click Upload Update File and browse to the location where you saved the patch file.
e. Click OK to upload the patch file.
f. When the upload is complete: On the Software Upload page, verify that the Name, Published Date and Description of the patch file are correct.
g. Select the patch file and click Install . When the installation is complete, you will see a popup message confirming this.
h. After the installation is complete on the secondary server, verify that the Software Updates page shows:
– In the “Installed” column: A “Yes” opposite the listing for this patch.
– In the “Pending Restart” column: A “Yes” for the secondary server. Do not restart the secondary server at this point.
Step 4 Install the patch on the primary server:
a. Log in to the primary server using an ID with administrator privileges and choose Administration > Software Update .
b. Click Upload Update File and browse to the location where you saved the patch file.
c. Click OK to upload the patch file.
d. When the upload is complete: On the Software Upload page, verify that the Name, Published Date and Description of the patch file are correct.
e. Select the patch file and click Install . When the installation is complete, you will see a popup message confirming this.
f. After the installation is complete on the primary server, verify that the Software Update page shows:
– In the “Installed” column: A “Yes” opposite the listing for this patch.
– In the “Pending Restart” column: A “Yes” for the primary server. Do not restart the primary server at this point.
Step 5 Stop the servers in the following sequence, using the commands explained in Running Commands:
a. On the secondary server, run the ncs stop command.
b. On the primary server, run the ncs stop command.
Step 6 Re-start and monitor the servers in the following sequence, using the commands explained in Running Commands:
a. On the secondary server, run:
– The ncs start command to restart the secondary server. Wait for the processes on the secondary to restart.
– The ncs status command to verify that the processes on the secondary have re-started.
– The ncs ha status command to verify that the secondary state is “Secondary Lost Primary”.
b. Once the secondary server is in “Secondary Lost Primary” state: On the primary server, run:
– The ncs start command to restart the primary server. Wait for the processes on the primary to restart.
– The ncs status command to verify that the primary’s Health Monitor and other processes have re-started.
Once all the processes on the primary are up and running, automatic HA registration will be triggered. This normally completes after a few minutes.
Step 7 Once registration completes, verify the patch installation as follows:
a. Run the ncs ha status command on both the primary and secondary servers. You should see the primary server state change from “HA Initializing” to “Primary Active”. You should see the secondary server state change from “Secondary Lost Primary” to “Secondary Syncing”.
b. Log in to the primary server and access its Software Update page as you did earlier. The “Installed” column should show “Yes” and the “Pending Restart” column should show “No” for the installed patch.
c. Access the secondary server’s Health Monitor page as you did earlier. The “Installed” column should show “Yes” and the “Pending Restart” column should show “No” for the installed patch.

Cisco Switches and HP Interoperability with Spanning-Tree (RSTP)

Hello All.
I read a lot of information from this forum about Spaning-Tree interoperability between HP Switches and Cisco Switches.
Rather than having questions I would like to post that I manage to configure successfully HP and Cisco using RSTP (802.1w).
SWPADRAO]display stp root
MSTID Root Bridge ID        ExtPathCost IntPathCost Root Port
  0    32768.cc3e-5f3a-2939 0           0
[SWPADRAO]display stp brief
MSTID      Port                         Role STP State     Protection
  0        GigabitEthernet1/0/47        DESI FORWARDING    NONE
  0        GigabitEthernet1/0/48        DESI FORWARDING    NONE
[SWPADRAO]display stp instance 0
-------[CIST Global Info][Mode RSTP]-------
CIST Bridge         :32768.cc3e-5f3a-2939
Bridge Times        :Hello 2s MaxAge 20s FwDly 15s MaxHop 20
CIST Root/ERPC      :32768.cc3e-5f3a-2939 / 0
CIST RegRoot/IRPC   :32768.cc3e-5f3a-2939 / 0
CIST RootPortId     :0.0
BPDU-Protection     :enabled
Bridge Config-
Digest-Snooping     :disabled
TC or TCN received :17
Time since last TC :0 days 0h:1m:52s
SWNHAM17#show spanning-tree VLAN0001
Spanning tree enabled protocol rstp
Root ID    Priority    32768
            Address     cc3e.5f3a.2939
            Cost        4
            Port        26 (GigabitEthernet0/2)
            Hello Time   2 sec Max Age 20 sec Forward Delay 15 sec  Bridge ID Priority    61441 (priority 61440 sys-id-ext 1)
            Address     001b.54db.7200
            Hello Time   2 sec Max Age 20 sec Forward Delay 15 sec
            Aging Time 300 Interface        Role Sts Cost      Prio.Nbr Type
Gi0/1            Altn BLK 4         128.25   P2p
Gi0/2            Root FWD 4         128.26   P2p
SWNHAM18#show spanning-tree VLAN0001
Spanning tree enabled protocol rstp
Root ID    Priority    32768
            Address     cc3e.5f3a.2939
            Cost        4
            Port        26 (GigabitEthernet0/2)
            Hello Time   2 sec Max Age 20 sec Forward Delay 15 sec  Bridge ID Priority    61441 (priority 61440 sys-id-ext 1)
            Address     001b.0cbc.4300
            Hello Time   2 sec Max Age 20 sec Forward Delay 15 sec
            Aging Time 300 Interface        Role Sts Cost      Prio.Nbr Type
Gi0/1            Desg FWD 4         128.25   P2p
Gi0/2            Root FWD 4         128.26   P2p

Hello, David.
Your command doesn't work because it's made only for tha ports that has command "spanning-tree portfast" in them. Try change spanning tree mode at the HP switch to MSTP if this is possible.

Cisco IE-3000-8TC switches and CNA

Similar Messages

Maybe you are looking for