Nexus 5548 reboots after config change

Hi all,
A customer configured his nexus 5000 with the basic configuration. This incudes also ssh (generate a certificate)
After that the switch reboots all the time.
I would like to test it tomorrow without the startup config. Is it possible to reboot the n5k without the startup config ? And is there also a ROM mode ? I don't found any docs on Cisco...
Thanks
Udo
Sent from Cisco Technical Support iPad App

Are you using the "ip arp synchronize", "peer-gateway" and "peer-switch" features? Those all help mitigate aspects of traffic flow that could be related to what you're seeing.

Similar Messages

%ONLINE-SP-6-REGN_TIMER: multiple line cards down after config change

Hi,
I was wondering if someone could help.
I recently changed the entire configuration on two 6509 switches, and the fibre modules on slot 7 and 8 have gone down on BOTH switches. It would be easy to say that its a hardware fault but I cannot understand how module 7 and 8 can go down on both switches. Initially I thought it maybe due to IOS bug 22-33.SXI2a.bin" so I upgraded it to s72033-advipservicesk9_wan-mz.122-18.SXF12a.bin but it still down.
These are the actions I have carrried out to try resolve the issue:
- Reverted back to orginal configs but no luck
- Tried to use "power enable" command but the status light on both modules seems to turn red and then go off again.
- I have also tried to put one of the fibre modules into a different slot but no joy
- Upgraded the IOS from 22-33.SXI2a. to 122-18.SXF12a
I am running out of ideas.. can anyone help ? I am sure that hardware fault cannot occur on BOTH modules 7 & 8 on BOTH switches after config change.
The error in the log shows that modules "failed to bring online because of registration timer event". I understand this means that it is unable to download the image within the allocated time.. maybe I could manually copy the image onto the line card if that is possible ?? any ideas ?
Daughterboard         WS-SUP720          SAL135063V2 4.0    Ok
7 Centralized Forwarding Card WS-F6700-CFC       SAL1419HKJK 4.1    PwrDown
8 Centralized Forwarding Card WS-F6700-CFC       SAL1419HAG0 4.1    PwrDown
Mod                                                      Hw    Fw           Sw           Status
7 5475.d016.075c to 5475.d016.075f   3.1   Unknown      Unknown      PwrDown
8 5475.d0bb.7404 to 5475.d0bb.7407   3.1   Unknown      Unknown      PwrDown
System image file is "disk0:s72033-advipservicesk9_wan-mz.122-18.SXF12a.bin"
BOOT variable = disk0:s72033-advipservicesk9_wan-mz.122-18.SXF12a.bin,12;sup-bootdisk,1;
CONFIG_FILE variable =
BOOTLDR variable =
Configuration register is 0x2102
Standby is not present.
May 28 17:25:10.352: %C6KPWR-SP-4-DISABLED: power to module in slot 7 set off (Module Failed SCP dnld)
May 28 17:25:10.452: %ONLINE-SP-6-REGN_TIMER: Module 8, Proc. 0. Failed to bring online because of registration timer event
sm(cygnus_oir_bay slot8), running yes, state wait_til_online
Last transition recorded: (disabled)-> disabled (disabled)-> disabled2 (restart)-> wait_til_disabled (timer)-> may_be_occupied (timer)-> occupied (known)-> can_power_on (yes_power)-> powered_on (real_power_on)-> check_power_on (timer)-> check_power_on (power_on_ok)-> wait_til_online
May 28 17:25:10.452: %C6KPWR-SP-4-DISABLED: power to module in slot 8 set off (Module Failed SCP dnld)
May 29 11:41:16.601: %SYS-5-CONFIG_I: Configured from console by console

Would anyone know if the line cards are maybe failing due to Embedded Event Manager configuration ? The person who configured this lab has left the company so I am not sure what the EEM configurations actually mean.
The reason i am suspecting the EEM configuration is because the error in the log seems to suggest the module failed due to registration timer event.
May 30 14:47:00.366: %ONLINE-SP-6-REGN_TIMER: Module 8, Proc. 0. Failed to bring online because of registration timer event
Just trying to check all the possibilities as I have tried everything else,
event manager directory user policy "disk0:/fcp_eem"
event manager directory user repository tftp://10.11.x.x/xxx/
event manager scheduler script thread class default number 10
no event manager policy Mandatory.go_switchbus.tcl type system
event manager policy rp_test.tcl type user
event manager detector rpc ssh acl 60 event manager directory user policy "disk0:/fcp_eem"
event manager directory user repository tftp://10.11.216.145/FCPD/
event manager scheduler script thread class default number 10
no event manager policy Mandatory.go_switchbus.tcl type system
event manager policy rp_test.tcl type user
event manager detector rpc ssh acl 60

%OSPF-4-FLOOD_WAR messages after config change

I recently changed some configs on two L3 switches running OSPF. After this change I'm now getting the below log message about ever 2 minutes or so on one of the switches (172.22.0.53):
%OSPF-4-FLOOD_WAR: Process 1 re-originates LSA ID 172.18.24.3 type-2 adv-rtr 172.22.0.53 in area 0
The two switches are using loopbacks 172.22.0.53 and 172.22.0.89, and are connected via a radio link. Previously both switches were using Layer 3 vlan interfaces with their OSPF configs applied to those vlan interfaces, then the physical interfaces were added in this VLAN as a L2 interface. The radio AP's were also within this vlan and not participating in OSPF. Under this setup I was not getting these Flood War messages, but was having a spanning-tree issue which is why I removed the L3 vlan interfaces.
I changed the physical ports to routed ports and copied the L3 vlan interfaces over and removed the L3 vlans. This is working, but now I'm getting these OSPF Flood war messages. I didn't change any router ID's, and the IP's set on the L3 vlans were moved to the L3 routed ports so I'm not sure where the duplicate is coming from. I've attached the configs of both switches.
Any ideas?

Hi
from url:-
http://www.cisco.com/c/en/us/support/docs/ip/open-shortest-path-first-ospf/9237-9.html
Q. What does the error message %OSPF-4-FLOOD_WAR: Process process-id re-originates LSA ID ip address type-2 adv-rtr ip address in area area id means?
A. The error message is due to the some router that is flushing the network LSA because the network LSA received by the router whose LSA ID conflicts with the IP address of one of the router's interfaces and flushes the LSA out of the network. For OSPF to function correctly the IP addresses of transit networks must be unique. If it is not unique the conflicting routers reports this error message. In the error message the router with the OSPF router ID reported as adv-rtr reports this message.
Also on your 53 config
You have a paasive int on vlan 153 but that SVI does not exist , 133 does though
Regards
Alex

Adding failover ASA back after config changes on "primary" ASA?

I had a working active/passive pair of ASA5510's, and then I had to do a rush firmware upgrade, but didn't have time to do it on the secondary at the same time. Now I have made config changes and upgraded the secondary firmware to be the same, and wish to know if I plug it back in if it will think the secondary has the "correct" config or if it will know that the primary is newer. I disconnected the failover cable because it was complaining about version mismatches constantly.
Is it safe to add the secondary back in or is it possible it will be declared newer and overwrite the config?

Hi,
There should be no problem adding another ASA back to the network.
Here is what I just did (and what happened) on a rather big customer
A power fault broke Secondary ASA and it never booted up
A replacement device was aquired
The replacement device was
Updated to matching hardware setup (mainly memory)
Updated to same software (OS and ASDM)
Configured with its physical interface up with "no shutdown"
Configured with ONLY "failover" configurations (exact configuration ofcourse depends on your setup)
It was attached to the rack and powered up.
After boot every interface BUT "failover" was attached to the network (Dont necesarily have to do it in this order) and I checked that every single one was up.
After everything above was done I connected the failover interface and watched as the devices "noticed" eachother and the Active firewall copied its configuration to the new Secondary unit.
This was done in a factory environment and all went fine.
There should be no problems doing this though I personally still prefer doing the replacement by attaching a "blank" ASA with only Failover configurations.
EDIT: Beeing that I am always paranoid when doing anything like this, I had ofcourse saved the configurations to flash on a separate file for worst case scenario and was ready to boot the original primary unit incase it took in something it wasnt supposed to.
EDIT 2: In the case where you think the Secondary unit doesnt have the exact configuration of the Primary unit, you can issue the command write standby on the Primary unit to save/copy the COMPLETE configuration of the Primary unit to the Secondary. Think the "write mem" on the Primary unit only updates some changes you have made to the Secondary unit
- Jouni

Cat6509 hangs after config change

I have two 6509 Sup720 Boxes running IOS 12.2.(18)SXD4. If I do a show run command after making any config change my telnet session will hang. If I open another session I can run other show commands but, If I do show run it will hang again. The boxes will continue to work fine, just the console hangs. After about 10 - 15 min it will reset and it's ok???????

Not sure what that would be , we have the same setup with SXD4 running on probably 20 6509's and haven't had a problem . Are you talking console or vty session hanging ???

Nexus 5000 rebooted after receiving %VSHD-5-VSHD_SYSLOG_CONFIG_I: Configured from vty by on ppm.3523

Hi,
We have two Nexus 5000 in HA configuration that use a switch port profile to share configuration changes.
Earlier this morning the secondary switch rebooted (this has happened before).
Just prior to the reboot the syslog server received the following command.
Dec 18 07:08:32 10.91.254.62 : 2013 Dec 18 07:08:32 AEST: %ASCII-CFG-6-INFORMATION: Reading ACFG Runtime information
Dec 18 07:08:33 10.91.254.62 : 2013 Dec 18 07:08:33 AEST: %VSHD-5-VSHD_SYSLOG_CONFIG_I: Configured from vty by on ppm.3523
Dec 18 07:08:33 10.91.254.62 : 2013 Dec 18 07:08:33 AEST: %ASCII-CFG-6-INFORMATION: Reading ACFG Runtime information
Any help with diagnosing this issue will be appreciated
Version information below.
Software
BIOS:      version 3.5.0
loader:    version N/A
kickstart: version 5.1(3)N2(1)
system:    version 5.1(3)N2(1)
power-seq: Module 1: version v1.0
             Module 3: version v2.0
uC:        version v1.2.0.1
SFP uC:    Module 1: v1.0.0.0
BIOS compile time:       02/03/2011
kickstart image file is: bootflash:///n5000-uk9-kickstart.5.1.3.N2.1.bin
kickstart compile time: 3/20/2012 0:00:00 [03/20/2012 18:51:29]
system image file is:    bootflash:///n5000-uk9.5.1.3.N2.1.bin
system compile time:     3/20/2012 0:00:00 [03/20/2012 20:00:58]
Hardware
cisco Nexus5548 Chassis ("O2 32X10GE/Modular Universal Platform Supervisor")
Intel(R) Xeon(R) CPU         with 8263864 kB of memory.
Processor Board ID FOC15504PN3
Device name: AALN5KPDC03
bootflash:    2007040 kB
Kernel uptime is 0 day(s), 3 hour(s), 1 minute(s), 48 second(s)
Last reset at 429902 usecs after Wed Dec 18 07:03:10 2013
Reason: Kernel Panic
System version: 5.1(3)N2(1)
Service:
plugin
Core Plugin, Ethernet Plugin

Hello,
In case a unexpected reboot with a kernel panic reason I recommend to you to open a case with Cisco TAC team.
Probably is related a bug CSCua53582.
Richard

WCL Tracking Scenario (Search List) not updated after config change

Dear Users,
Initially I assigned 3 User profiles and Web Interface Transaction to my user ID under the transaction : Event Management -> Event Messages, Status Queries and Web Interface -> Web Interface -> Assign User profile and Web Interface transactions to Users
When I login to WCL using my user ID, I was able to see these three tracking scenarios in my Search page drop down.
Now I go back to config and add new user profiles and web interface transactions to the same user id.
But when I login to WCL, the search page still remains the same( the three old tracking scenarios are there, new ones not reflected) !!!
Can this be any setting in the internet explorer which is not allowing to refresh? I have tried deleting cookies etc. But no change!!
Please HELP with your expert advise.
Thanks in advance.
Regards,
Rimjhim

Can you share the solution.

Nexus 5548 acl in config sync

Hello, I have a following problem. When configuring ip acl in config-sync mode I get following message: "Error: Cannot configure acl rule without seq no." Is this a bug or a feature? I'm running 5.1(3)N1(1)

sounds more like a bug. i see a bug being filed on it internally (not customer viewable yet). CSCtz27923. I will make it customer viewable shortly.
thanks, vinayak

SNMPv3 config changing after reboot

Whenever one of my C2960's reboot, our Solarwinds monitoring stops working. I found that this is due to one line of SNMPv3 config changing by itself. This used to be in the config:
     snmp-server group XXX v3 priv access permit-snmp
(permit-snmp being the access-list defining ip addresses allowed to query) After the reboot, snmpv3 stops working and this line shows up in the config instead of the one above:
     snmp-server group XXX v3 priv notify *tv.FFFFFFFF.FFFFFFFF.FFFFFFFF.FFFFFFFF7F
Is this a bug? (I did check the bug database, without success.) I have upgraded the IOS to 12.2(53) SE2 without any success. The switch is a C2960-24TC-L.

I had the same problem and believe the issue is that you probably have a trap server configured and are using the same snmp-server group for the trap server and your queries. I created another group for SNMPv3 queries and the configuration no longer seems to get overwritten. Here's what I did.
Go into config mode and create a group just for the trap server - let's call it TRAPS. I used priv and it looks like that's what you use. Don't worry about defining any MIB views as this group will automatically populate the notifyview once the trap servers below are added to the config. (...and will remove the readview and writeview entries after reboot - that's why a second group is needed). Remove your old trap server entries and set up the new trap server using the new group called TRAPS.
snmp-server group TRAPS v3 priv
snmp-server host version 3 priv TRAPS
Now create another group for queries only - (let's call it QUERIES but you could just use your current group XXX since it's already set up) - I like the v1default MIB view for both reads and writes but you can limit the MIBs with the snmp-server view command. I am using md5 and des56 here - your case may be different - and set up the user (or keep the one you already have configured)
snmp-server group QUERIES v3 priv read v1default write v1default access
snmp-server user QUERIES v3 auth md5 priv des56
Exit and check the config.
The group TRAPS should have the notifyview set. The group QUERIES should have the readview and writeview set to v1default (or whatever view you chose to enter here). The two SNMPv3 groups should look like this:
#sh snmp group
groupname: TRAPS                            security model:v3 priv
readview :           writeview:
notifyview: *tv.FFFFFFFF.FFFFFFFF.FFFFFFFF.F
row status: active
groupname: QUERIES                          security model:v3 priv
readview : v1default                        writeview: v1default
notifyview:
row status: active      access-list: 4
The old trap server entry using the old group XXX should have been removed already. Verify that the user: entry says TRAPS
#sh snmp host
Notification host: xxx.xxx.xxx.xxx      udp-port: 162   type: trap
user: TRAPS     security model: v3 priv
Finally make sure the user is in the correct group (QUERIES):
#sh snmp user
User name:
Engine ID: xxxxxxxxxxxxxxxxxxxxxxxxxx
storage-type: nonvolatile        active
Authentication Protocol: MD5
Privacy Protocol: DES
Group-name: QUERIES
If all is well - write the config. You should now be able to perform a coldstart without losing your SNMPv3 config.
Please, let me know if this worked for you.

Fix for continuous reboot after installing Service Pack 3 in Windows XP

After contacting HP Technical Support and speaking to a supervisor we were able to solve the problem of Windows continuously rebooting after installing SP3. Here are the steps that fixed the problem with my HP Pavilion running on an AMD processor. The steps are actually fairly straight forward and easy....
Issue: The computer reboots continuously after installing Windows XP service pack 3
Computer reboots continuously after installing Windows XP service pack 3 on AMD systems. The problem is that with some configurations, SP3 causes the computer to crash during boot, and Windows XP, by default, is set up to automatically reboot when it crashes. That is why you end up in the endless rebooting scenario.
Cause:
On HP computers, the same Windows installation disc image for Intel processor based PC's is deployed for the AMD processor based computers as well. Because the original installation image for both Intel and AMD is the same, all have the intelppm.sys driver installed and running. That driver provides power management on Intel-based computers. On an AMD-based computer, amdk8.sys provides the same functionality for power management.
Symptoms:
Ordinarily, having intelppm.sys running on an AMD-based computer appears to cause no problems. However, on the first reboot after a Service Pack 3 installation, it causes a big problem. The computer either fails to boot, or crashes with a STOP error code of 0x0000007e.
You may not see the error code because the computer reboots too fast. In order to get the error message, you need to set an option during startup. To do so, open the windows advanced menu by tapping the f8 key on startup. Then select the "Disable automatic restart on system failure" option.
Solution:
If you have an AMD-based computer, however, you do not need the intelppm.sys driver and can disable it. There are three methods in order to do this.
Step 1: Please try to log on the system in safe mode.
1. While using Safe mode open the command prompt.... Start, All Programs, Accessories, Command Prompt
Run the following command in the command prompt just like it's typed: sc config intelppm start= disabled
Step 2:
If the issue persists, please try to log on or boot the system in recovery console (refer to the web document)
2. Using recovery console:
If you booted into the recovery console, from a command prompt, type: disable intelppm
Step 3: Please check in registry.
3. Using windows registry:
1. Run regedit
2. Click on HKEY_LOCAL_MACHINE
3. From the File menu, select "Load hive"
4. Navigate to %systemdriver%\Windows\System32\Config on the dead system and select the file name System
5. Name it something you can remember, such as "horked"
6. Navigate to horked\ControlSet001\Services\IntelPPM
7. Double click the Start value and set it to 4
8. If you did what I did and completely messed things up by running a disk check previously, navigate to ControlSet001\Control\SessionManager. Open the BootExecute value and clear out the autochk entries.
9. Repeat steps 6-8 for the other control sets.
10. Reboot
Reference:
http://support.microsoft.com/kb/888372
Additional information:
Computer Restarts after Displaying Stop Error 0x0000007E (After Updating with Service Pack 3 for Windows XP):
http://h10025.www1.hp.com/ewfrf/wc/genericDocument?docname=c01457284&cc=us&dlc=en&lc=en&jumpid=reg_R1002_USEN
For future reference: Service pack 3 Installation steps:
Before installing the service pack 3 update, please follow the steps listed above and save yourself much time and effort.
To uninstall service pack 3, I suggest that you uninstall it from add/remove programs.
Step 1:
Uninstall service pack 3 from add/remove programs:
1. Click Start.
2. Select Run.
3. Type appwiz.cpl in the run field.
4. Click OK.
5. Click change or remove programs.
6. Select the program -service pack 3 that you want to uninstall or remove.
7. Click Remove button.
8. It will pop up the message stating that "Are you sure you want to remove the programs".
9. Click Yes. It will help you to remove or uninstall the installed programs from add and remove programs.
Step 2: If the issue persists, I suggest you to perform system restore and then try to install the service pack 3 after performing the steps mentioned above in regards to removing the intelppm.sys Driver.
Using Microsoft System Restore in Windows Me and XP:
http://h10025.www1.hp.com/ewfrf/wc/genericDocument?docname=bph07103&cc=us&dlc=en&lc=en&jumpid=reg_R1002_USEN
Step 3:
How to obtain the latest Windows XP service pack :
http://support.microsoft.com/kb/322389/
Steps to take before you install Windows XP Service Pack 3:
http://support.microsoft.com/kb/950717/en-us
I hope this helps someone who is having this problem. It sure took me a minute to get it all figured out. :0)

Still useful as of 12/30/11. Have ten Lenovo 5042 computers with downgrade licenses to run XP and have a ghosted image from another Lenovo 5042 having and Intel cpu. My target computers all have AMD cpus in them and the image would continuously reboot on
the AMD computers.
Used method 1 and it cleared the problem instantly, many thanks for the post and the time and effort it took to dig up the answer..

Active/Standby Failover Config change

Hi everyone,
This weekend we are doing some change on ASA in Active/Standby mode.
We will power off standby ASA.
Do some changes on Active ASA save the changes and reboot it.
Power up the Active ASA and will test the connectivity if it is working or not .
In case Active ASA is not working as expected after the change i will power it off.
Power up Standby ASA then it will become active as expected.
Now if i Power up other ASA where changes were made will it synchnorize to old config from Standby ASA or not?
Last week we did some changes on Active ASA and it did not work as expected so we have to undo our change.
Need to make sure our backup plan is working?
Regards
Mahesh

In your fall back scenario you would have to tell what was the secondary ASA that it is now the primary
change
failover lan unit secondary
to
failover lan unit primary
and vice-versa on the now primary ASA.
change
failover lan unit primary
to
failover lan unit secondary
Hope it helps

Nexus 5548 L3 daughter card flapping

Hi guys,
Anyone of you here that experienced the logs below on their Nexus box:
2011 Dec 12 06:24:45 GDCNXS5K01 %BTCM-2-BTCM_LOG_ROUTER_ERR: router card in slot 3 has internal link(s) flapped: router ports down: 0x1a108000 0x1a109000 0x1a10a000 0x1a10b000 0x1a10c000 0x1a10d000 0x1a10e000 0x1a10f000
I am getting this log at least once a day. Seems like it is shutting down the SVI of the box after the said log occured. Good thing I have enable vPC and I am able to access the NXS5K through the vCP keepalive link (mgmt).
I have two Nexus 5548, but only one is experiencing the said error.
Any inputs, suggestions would be greatly appreciated.
Thanks,
Edzel

We had this same problem this past weekend, only in module 2 on a 5596.
In our case, we had rebooted our primary Nexus and found the following message immediately preceeded the BTCM error you noted:
%$ VDC-1 %$ %NOHMS-2-NOHMS_DIAG_ERROR: Module 2: Bootup diag detected major event: Forwarding ASIC failure: Ethernet2/9 Ethernet2/10 Ethernet2/11 Ethernet2/12 Ethernet2/13 Ethernet2/14 Ethernet2/15 Ethernet2/16
We replaced the module. A "show diag results module 3" would probably show you the same thing. However, I don't think the error message will show up until you reboot.
If your flapping Nexus is secondary, you probably won't notice anything major, but if it is your primary, it would probably affect your routing.

Urgent help: L3 daughter card for Nexus 5548

Hi
We have 2 Nexus 5548 which is in one vPC doamin. All the servers are teamed to these switches
Requirement
We have to install New L3 daughter card.(N55-D160L3-V2(=))
I have gone through the Cisco websites and found that we have to do the following things
1. software version:
i Nexus 5548P Daughter Card (N55-D160L3)
Before installing a Layer 3 daughter card (N55-D160L3) into a Cisco Nexus 5548P switch, you must upgrade to Cisco NX-OS Release 5.0(3)N1(1b) or NX-OS Release 5.0(3)N1(1c) and then install the card into the chassis.
http://www.cisco.com/en/US/docs/switches/datacenter/nexus5000/sw/release/notes/Rel_5_0_3_N2_1/Nexus5000_Release_Notes_5_0_3_N2.html
2. license:
Also in order to enable this module following license should present on N5k device:
LAN_BASE_SERVICES_PKG - it's free and lifetime.
https://supportforums.cisco.com/thread/2121574
I have 2 questions
1- In cisco documentation its says that these cards will be installed in the front where I/O module is and after NX OS 5.X they are hot swappable
Does that mean that no reboot will be required after installing this module (keeping in mind its the first time) so i am confused about the wording ???
Does license installation requires reboot??? in short if you are installing for the first time do we require a reboot ???? that is my main question
2- I have heard there is a known bug which keep rebooting the switch after installation of L3 card
http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCtl45495
has that been address in any version of license or NS-OS yet???
Thanks heaps guys
If the module is still offline when the requirements are met above, it could be a bug.(CSCtl45495) Try reloading the switch.

1- In cisco documentation its says that these cards will be installed in the front where I/O module is and after NX OS 5.X they are hot swappable
Does that mean that no reboot will be required after installing this module (keeping in mind its the first time) so i am confused about the wording ???
Answer: -- Yes no reboot is required.
Does license installation requires reboot??? in short if you are installing for the first time do we require a reboot ???? that is my main question
Answer: As you are installing the license for the first time reboot of the box is not required.
2- I have heard there is a known bug which keep rebooting the switch after installation of L3 card
http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCtl45495
has that been address in any version of license or NS-OS yet???
Answer;--No this is not fixed yet.
HTH
Regards
Inayath
********Please do not forget to rate the post if this info is helpfull.

Upgrading Nexus 5548

Hi,
We want to upgrade our pair of Nexus 5548 to the new NX-OS 5.1(3)N2(1a) from the 5.0(3)N1(1c) version. We would like to use the ISSU procedure. But when we execute the command "show spannig-tree issu-impact" we get the following output:
No Active Topology change Found!
Criteria 1 PASSED !!
No Ports with BA Enabled Found!
Criteria 2 PASSED!!
List of all the Non-Edge Ports
Port VLAN Role Sts Tree Type Instance
Ethernet2/8 1803 Desg FWD PVRST 1803
The 1803 vlan is only used for the peer-keepalive link and it only exists on these two Nexus. So one of the two Nexus needs to be the STP root. That makes the ports on that vlan to be in designated-forwarding state, which is not supported for the ISSU:
sh run int e2/8
!Command: show running-config interface Ethernet2/8
!Time: Fri Jun 8 17:04:33 2012
version 5.0(3)N1(1c)
interface Ethernet2/8
switchport access vlan 1803
speed 1000
That is the only port that belongs to that VLAN and it is directly connected to the other Nexus 5548. So the only way we see to avoid this port of being in designated-forwarding state is to apply the "no spanning-tree vlan 1803" command. Would it be a problem?
We can imagine that introducing the "spanning-tree port type edge" should not be a good idea, shouldn´t it?
Thank you very much for your help!
Josu

Hi,
Reviewing all the prerequisites for the ISSU, we have seen the following:
SSU and Layer 3
Cisco Nexus 5500 Platform switches support Layer 3 functionality. However, the system cannot be upgraded with the ISSU process (non disruptive upgrade) when Layer 3 is enabled. It is required to unconfigure all Layer 3 features to be able to upgrade in a non disruptive way with an ISSU.
We have the interface-vlan feature enabled. But it is only used for two interfaces:
- interface-vlan 510 --> It is only used in order connect to the switch
- interface-vlan 1803 --> The one used for the keepalive
We could administratevely shutdown the interface-vlan 510. But we could not do so with the interface-vlan 1803, since it is used for the keepalive. If we execute "no feature interface-vlan", would the keepalive stop working?
When we execute "sh install all impact ..." command the Nexus does not tell anything about this feature. Is really recommended to disable it? Is it needed for the ISSU procedure?
Thank you very much in advance!!
JOSU

FCoE using Brocade cards CNA1020 and Cisco Nexus 5548 switches

All,
I have the following configuration and problem that I am not sure how to fix:
I have three Dell R910 servers with 1TB of memory and each has two brocade 1020 CNA cards dual port. I am using distributed switches for the VM network and a second distributed switch for VMotion. I have two of the 10G ports configured in each distributed switch using IP Hash. The management network is configured using a standard switch with two 1G ports.
The Nexus configuration is we have two nexus 5548 switch connected together with a trunk. We have two VPC's configured to each ESX hosts consisting of two 10gig ports in each VPC with one port going to each switch. The VPC is configured for static LAG.
What I am seeing is that after a few hours the virtual machines will not be accessible via network anymore. So if you ping the VM it will not work and if you get on the console of the VM then ping the gateway then nothing as well but if you try to ping another virtual machine on the same host on the same VLAN then it will work so traffic is going through the ESX backplane. If I reboot the ESX host then things will work again for another few hours or so then the problem repeats.
The version of vSphere I am using is ESXi4.1
Please assist I am stuck.
Thanks...

Here is the link for Nexus and Brocade interoperability Matrix
http://www.cisco.com/en/US/docs/switches/datacenter/mds9000/interoperability/matrix/Matrix7.html#wp313498
usually this table would show those models those have been tested and verified
However I do not see Brocade 5300 listed in the table . It could be, interoperability may have not been tested by both vendors perticularly to 5300 type Model.

Nexus 5548 reboots after config change

Similar Messages

Maybe you are looking for