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
Similar Messages
-
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 AppAre 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.
-
CFS : how to disable application ? nexus 5000
1. Could you please help me out here. I am setting up syslog on Nexus switches and running into problems (error messages at bottom)
On Nexus 5000, I am trying to disable CFS distribution for application SYSLOGD, but do not find a command to do that.
Why I want to do that ?
With CFS enabled for syslogd, 'use-vrf' option is not allowed in the command 'logging server 167.54.254.23 6 ' and by default syslogd uses vrf management whereas I want it to use vrf default.
2. Also, any idea why this message pops up ?
CLIC-6-EXIT_CONFIG: Configured from 1 by systest
2010 Feb 12 10:40:13.308 ked1.dcacc.n01 LOG-3-SYSTEM_MSG: Syslog could not be send to serv
er(167.54.254.23) : No route to host
2010 Feb 12 10:40:46.162 ked1.dcacc.n01 %VSHD-5-VSHD_SYSLOG_CONFIG_I: Configured from vty ....
2010 Feb 12 10:40:46.170 ked1.dcacc.n01 LOG-3-SYSTEM_MSG: Syslog could not be send to serv..) : No route to host
2010 Feb 12 10:40:46.170 ked1.dcacc.n01 11244]: CLIC-6-EXIT_CONFIG: Configured from 1 by systest
2010 Feb 12 10:40:46.181 ked1.dcacc.n01 snmpd: snmpd: send_trap: Failure in sendto (No route to host)
2010 Feb 12 10:40:46.183 ked1.dcacc.n01 last message repeated 2 times
2010 Feb 12 10:40:46.183 ked1.dcacc.n01 snmpd: NETWORK- UNREACHABLELearned the command is:
no logging distribute -
Tacacs do not function in Nexus 5000
Dear Mister
By someone reason, the Tacas is not functioning in my Nexus 5000. I am using the next configuration :
tacacs-server key 7 "0310551D121F2D595D"
ip tacacs source-interface Vlan5
tacacs-server host 10.20.2.80
tacacs-server host 10.20.16.138
aaa group server tacacs+ TACSERVER
server 10.20.2.80
server 10.20.16.138
source-interface Vlan5
use-vrf default
aaa authentication login default group TACSERVER
no aaa user default-role
aaa authentication login error-enable
tacacs-server directed-request
I did a telnet to port 49, in address , and is functioning. That discard a Security problem (FW, ACL, etc).
When I do the test, nothing is showed in the Tacacs Logs Server.
The log messages are the next:
2012 Aug 22 15:54:45 NITE1 %TACACS-3-TACACS_ERROR_MESSAGE: received bad authentication packet from 10.20.2.80
2012 Aug 22 15:54:45 NITE1 %TACACS-3-TACACS_ERROR_MESSAGE: All servers failed to respond
2012 Aug 22 15:54:48 NITE1 %AUTHPRIV-3-SYSTEM_MSG: pam_aaa:Authentication failed for user GPALAVE from 10.20.2.80 - login[3087]
The problem is very strange.
I need help.
Best regardsYou config looks fine. Can you ping from VLAN5 to TACACS+? Also, did you add VLAN5's IP address to your TACACS+.
Regards,
jerry -
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 -
cannot send or receive yahoo mail or gmail from iPhone . installed ios 6 recently. tried rebooting the phone and deleting the email account and adding again but nothing works ! can someone suggest a solution?
Not sure about yahoo, but for gmail, I done the following:
Set up using Exchange on iPhone, it'll keep prompting for password. On PC use captcha option, log in to gmail account from PC after completingg captcha option, enter password on iPhone.
See how that goes for gmail, let us know.
Hopefully someone will have fix for yahoo. -
Nexus 5000 vpc and fabricpath considerations
Hello community,
I'm currently in the process of implementing a fabricpath environment which includes Nexus 5548UP as well Nexus 7009
NX OS on N5K is 6.0(2)N1(2)
Regarding the FP config on the N5K I wonder what is the best practice for the peer-link. Is it necessary to configure the Portchannel like below:
interface port-channel2
description VPC+ Peer Link
switchport mode fabricpath
spanning-tree port type network
vpc peer-link
There are several VLANs configured as FP.
As I understand we can remove the command:
spanning-tree port type network
Can anyone confirm this ?
Also I noticed a "cosmetic" problem. On two port 1/9 and 1/10 on both N5K it isn't possible to execute the command "speed"?!
When the command speed is executed I receive the following error:
ERROR: Ethernet1/9: Configuration does not match the port capability
Also please notice after the vPC and FP configuration we don't do a reload!
Thanks
UdoHi Simon -
Have done some testings in the lab on ISSU with FEXes either in Active/Active and Straight-through fashion, and it works.
Disabling BA on N5K(except the vPC peer link) is one of the requirements for ISSU .
In a lately lab testing with the following topo, BA is configured on the vpc 101 between the N5Ks and Cat6k. We have a repeated regular ping between the SVI interfaces of c3750 and Cat6K.
c3750
||
vPC
||
N5K =====vPC====== N5K
||
vpc 101
||
Cat6k
When we changed the network type to disable BA, we observed some ping drops, which around 20-30.
I am not sure what your network looks like, hopefully this will give you some ideas about the ISSU. As a general recommendation, schedule a change window for some changes or even ISSU.
regards,
Michael -
I have a new issue with all DPs.
When I pxe boot, it will boot into WinPE but then it will fail and reboot after the step: “Preparing network connections”
I have tried reinstalling the DP and MP. Also redistributing the boot image.
When I press F8 to go into debug mode, ipconfig show me an IP address and I am able to ping my Management point, my DHCP server and also my Distribution point.
I have attached the smsts.log file.
<![LOG[LOGGING: Finalize process ID set to 900]LOG]!><time="10:43:28.925+480" date="08-13-2014" component="TSBootShell" context="" type="1" thread="904" file="tslogging.cpp:1495">
<![LOG[==============================[ TSBootShell.exe ]==============================]LOG]!><time="10:43:28.925+480" date="08-13-2014" component="TSBootShell" context="" type="1" thread="904"
file="bootshell.cpp:1055">
<![LOG[Succeeded loading resource DLL 'X:\sms\bin\x64\1033\TSRES.DLL']LOG]!><time="10:43:28.925+480" date="08-13-2014" component="TSBootShell" context="" type="1" thread="904" file="util.cpp:964">
<![LOG[Debug shell is enabled]LOG]!><time="10:43:28.940+480" date="08-13-2014" component="TSBootShell" context="" type="1" thread="904" file="bootshell.cpp:1066">
<![LOG[Waiting for PNP initialization...]LOG]!><time="10:43:28.940+480" date="08-13-2014" component="TSBootShell" context="" type="1" thread="908" file="bootshell.cpp:60">
<![LOG[RAM Disk Boot Path: NET(0)\SMSIMAGES\EVN0002F\BOOT.EVN0002F.WIM]LOG]!><time="10:43:28.940+480" date="08-13-2014" component="TSBootShell" context="" type="1" thread="908" file="configpath.cpp:302">
<![LOG[Booted from network (PXE)]LOG]!><time="10:43:28.940+480" date="08-13-2014" component="TSBootShell" context="" type="1" thread="908" file="configpath.cpp:317">
<![LOG[Network(PXE) path: X:\sms\data\]LOG]!><time="10:43:28.940+480" date="08-13-2014" component="TSBootShell" context="" type="1" thread="908" file="configpath.cpp:319">
<![LOG[Found config path X:\sms\data\]LOG]!><time="10:43:28.940+480" date="08-13-2014" component="TSBootShell" context="" type="1" thread="908" file="bootshell.cpp:548">
<![LOG[Booting from removable media, not restoring bootloaders on hard drive]LOG]!><time="10:43:28.940+480" date="08-13-2014" component="TSBootShell" context="" type="1" thread="908" file="bootshell.cpp:582">
<![LOG[X:\sms\data\WinPE does not exist.]LOG]!><time="10:43:28.940+480" date="08-13-2014" component="TSBootShell" context="" type="1" thread="908" file="bootshell.cpp:599">
<![LOG[X:\_SmsTsWinPE\WinPE does not exist.]LOG]!><time="10:43:28.940+480" date="08-13-2014" component="TSBootShell" context="" type="1" thread="908" file="bootshell.cpp:613">
<![LOG[Executing command line: wpeinit.exe -winpe]LOG]!><time="10:43:28.956+480" date="08-13-2014" component="TSBootShell" context="" type="1" thread="908" file="bootshell.cpp:860">
<![LOG[The command completed successfully.]LOG]!><time="10:44:13.294+480" date="08-13-2014" component="TSBootShell" context="" type="1" thread="908" file="bootshell.cpp:942">
<![LOG[Starting DNS client service.]LOG]!><time="10:44:13.294+480" date="08-13-2014" component="TSBootShell" context="" type="1" thread="908" file="bootshell.cpp:666">
<![LOG[Executing command line: X:\sms\bin\x64\TsmBootstrap.exe /env:WinPE /configpath:X:\sms\data\]LOG]!><time="10:44:13.809+480" date="08-13-2014" component="TSBootShell" context="" type="1" thread="908"
file="bootshell.cpp:860">
<![LOG[The command completed successfully.]LOG]!><time="10:44:13.809+480" date="08-13-2014" component="TSBootShell" context="" type="1" thread="908" file="bootshell.cpp:942">
<![LOG[==============================[ TSMBootStrap.exe ]==============================]LOG]!><time="10:44:13.903+480" date="08-13-2014" component="TSMBootstrap" context="" type="1" thread="1116"
file="tsmbootstrap.cpp:1165">
<![LOG[Command line: X:\sms\bin\x64\TsmBootstrap.exe /env:WinPE /configpath:X:\sms\data\]LOG]!><time="10:44:13.903+480" date="08-13-2014" component="TSMBootstrap" context="" type="0" thread="1116"
file="tsmbootstrap.cpp:1166">
<![LOG[Succeeded loading resource DLL 'X:\sms\bin\x64\1033\TSRES.DLL']LOG]!><time="10:44:13.919+480" date="08-13-2014" component="TSMBootstrap" context="" type="1" thread="1116" file="util.cpp:964">
<![LOG[Succeeded loading resource DLL 'X:\sms\bin\x64\TSRESNLC.DLL']LOG]!><time="10:44:13.919+480" date="08-13-2014" component="TSMBootstrap" context="" type="1" thread="1116" file="resourceutils.cpp:169">
<![LOG[Current OS version is 6.2.9200.0]LOG]!><time="10:44:13.919+480" date="08-13-2014" component="TSMBootstrap" context="" type="1" thread="1116" file="util.cpp:3094">
<![LOG[Adding SMS bin folder "X:\sms\bin\x64" to the system environment PATH]LOG]!><time="10:44:13.934+480" date="08-13-2014" component="TSMBootstrap" context="" type="0" thread="1116"
file="tsmbootstrap.cpp:963">
<![LOG[PXE Boot with Root = X:\]LOG]!><time="10:44:13.934+480" date="08-13-2014" component="TSMBootstrap" context="" type="1" thread="1116" file="tsmbootstrap.cpp:1062">
<![LOG[Executing from PXE in WinPE]LOG]!><time="10:44:13.934+480" date="08-13-2014" component="TSMBootstrap" context="" type="1" thread="1116" file="tsmbootstrap.cpp:1077">
<![LOG[Loading TsPxe.dll from X:\sms\bin\x64\TsPxe.dll]LOG]!><time="10:44:13.934+480" date="08-13-2014" component="TSMBootstrap" context="" type="0" thread="1116" file="tsmbootstraputil.cpp:1363">
<![LOG[TsPxe.dll loaded]LOG]!><time="10:44:13.934+480" date="08-13-2014" component="TSPxe" context="" type="0" thread="1116" file="tsmbootstraputil.cpp:1373">
<![LOG[Device has PXE booted]LOG]!><time="10:44:13.934+480" date="08-13-2014" component="TSPxe" context="" type="0" thread="1116" file="tspxe.cpp:122">
<![LOG[Variable Path: \SMSTemp\2014.08.13.10.42.54.0001.{F722E5C6-13E4-4635-B674-7A56A68BCF03}.boot.var]LOG]!><time="10:44:13.934+480" date="08-13-2014" component="TSPxe" context="" type="0" thread="1116"
file="tspxe.cpp:134">
<![LOG[Variable Key Len: 69]LOG]!><time="10:44:13.934+480" date="08-13-2014" component="TSPxe" context="" type="0" thread="1116" file="tspxe.cpp:141">
<![LOG[Succesfully added firewall rule for Tftp]LOG]!><time="10:44:13.950+480" date="08-13-2014" component="TSPxe" context="" type="0" thread="1116" file="fwopen.cpp:123">
<![LOG[Executing: X:\sms\bin\x64\smstftp.exe -i 10.9.12.122 get \SMSTemp\2014.08.13.10.42.54.0001.{F722E5C6-13E4-4635-B674-7A56A68BCF03}.boot.var X:\sms\data\variables.dat]LOG]!><time="10:44:13.950+480" date="08-13-2014" component="TSPxe"
context="" type="0" thread="1116" file="tspxe.cpp:177">
<![LOG[Command line for extension .exe is "%1" %*]LOG]!><time="10:44:14.028+480" date="08-13-2014" component="TSPxe" context="" type="0" thread="1116" file="commandline.cpp:228">
<![LOG[Set command line: "X:\sms\bin\x64\smstftp.exe" -i 10.9.12.122 get \SMSTemp\2014.08.13.10.42.54.0001.{F722E5C6-13E4-4635-B674-7A56A68BCF03}.boot.var X:\sms\data\variables.dat]LOG]!><time="10:44:14.028+480" date="08-13-2014"
component="TSPxe" context="" type="0" thread="1116" file="commandline.cpp:731">
<![LOG[Executing command line: "X:\sms\bin\x64\smstftp.exe" -i 10.9.12.122 get \SMSTemp\2014.08.13.10.42.54.0001.{F722E5C6-13E4-4635-B674-7A56A68BCF03}.boot.var X:\sms\data\variables.dat]LOG]!><time="10:44:14.028+480" date="08-13-2014"
component="TSPxe" context="" type="1" thread="1116" file="commandline.cpp:827">
<![LOG[Process completed with exit code 0]LOG]!><time="10:44:14.106+480" date="08-13-2014" component="TSPxe" context="" type="1" thread="1116" file="commandline.cpp:1123">
<![LOG[Succesfully removed firewall rule for Tftp]LOG]!><time="10:44:14.122+480" date="08-13-2014" component="TSPxe" context="" type="0" thread="1116" file="fwopen.cpp:146">
<![LOG[Successfully downloaded pxe variable file.]LOG]!><time="10:44:14.122+480" date="08-13-2014" component="TSPxe" context="" type="1" thread="1116" file="tspxe.cpp:187">
<![LOG[we are booted using PXE]LOG]!><time="10:44:14.122+480" date="08-13-2014" component="TSPxe" context="" type="1" thread="1116" file="tsmediawizardcontrol.cpp:2673">
<![LOG[we are booted using PXE and we use a generated password]LOG]!><time="10:44:14.122+480" date="08-13-2014" component="TSPxe" context="" type="1" thread="1116" file="tsmediawizardcontrol.cpp:2678">
<![LOG[Loading Media Variables from "X:\sms\data\variables.dat"]LOG]!><time="10:44:14.122+480" date="08-13-2014" component="TSPxe" context="" type="1" thread="1116" file="tsremovablemedia.cpp:322">
<![LOG[CryptDecrypt (hKey, 0, 1, 0, pData, &dwDecryptedLen), HRESULT=80090005 (e:\nts_sccm_release\sms\framework\smscrypt\windes.cpp,165)]LOG]!><time="10:44:14.122+480" date="08-13-2014" component="TSPxe" context=""
type="0" thread="1116" file="windes.cpp:165">
<![LOG[SMS::Crypto::DES::DecryptBuffer( (BYTE*)pszPassword, (DWORD)(wcslen(pszPassword)*sizeof(WCHAR)), encryptedBuffer.getBuffer(), (DWORD)encryptedBuffer.size(), pbDecryptedBuffer, dwDecryptedBufferSize ), HRESULT=80090005 (e:\nts_sccm_release\sms\framework\tscore\tsremovablemedia.cpp,387)]LOG]!><time="10:44:14.122+480"
date="08-13-2014" component="TSPxe" context="" type="0" thread="1116" file="tsremovablemedia.cpp:387">
<![LOG[Verifying media password.]LOG]!><time="10:44:14.122+480" date="08-13-2014" component="TSPxe" context="" type="1" thread="1116" file="tsmediawizardcontrol.cpp:271">
<![LOG[Loading Media Variables from "X:\sms\data\variables.dat"]LOG]!><time="10:44:14.122+480" date="08-13-2014" component="TSPxe" context="" type="1" thread="1116" file="tsremovablemedia.cpp:322">
<![LOG[Found network adapter "Intel(R) 82577LM Gigabit Network Connection" with IP Address 10.9.2.50.]LOG]!><time="10:44:14.153+480" date="08-13-2014" component="TSPxe" context="" type="0"
thread="1116" file="tsmbootstraputil.cpp:517">
<![LOG[Loading Media Variables from "X:\sms\data\variables.dat"]LOG]!><time="10:44:14.153+480" date="08-13-2014" component="TSPxe" context="" type="1" thread="1116" file="tsremovablemedia.cpp:322">
<![LOG[CryptDecrypt (hKey, 0, 1, 0, pData, &dwDecryptedLen), HRESULT=80090005 (e:\nts_sccm_release\sms\framework\smscrypt\windes.cpp,165)]LOG]!><time="10:44:14.153+480" date="08-13-2014" component="TSPxe" context=""
type="0" thread="1116" file="windes.cpp:165">
<![LOG[SMS::Crypto::DES::DecryptBuffer( (BYTE*)pszPassword, (DWORD)(wcslen(pszPassword)*sizeof(WCHAR)), encryptedBuffer.getBuffer(), (DWORD)encryptedBuffer.size(), pbDecryptedBuffer, dwDecryptedBufferSize ), HRESULT=80090005 (e:\nts_sccm_release\sms\framework\tscore\tsremovablemedia.cpp,387)]LOG]!><time="10:44:14.153+480"
date="08-13-2014" component="TSPxe" context="" type="0" thread="1116" file="tsremovablemedia.cpp:387">
<![LOG[Entering TSMediaWizardControl::GetPolicy.]LOG]!><time="10:44:14.153+480" date="08-13-2014" component="TSPxe" context="" type="0" thread="1116" file="tsmediawizardcontrol.cpp:527">
<![LOG[Creating key 'Software\Microsoft\SMS\47006C006F00620061006C005C007B00350031004100300031003600420036002D0046003000440045002D0034003700350032002D0042003900370043002D003500340045003600460033003800360041003900310032007D00']LOG]!><time="10:44:14.153+480"
date="08-13-2014" component="TSPxe" context="" type="1" thread="1116" file="environmentscope.cpp:263">
<![LOG[Environment scope successfully created: Global\{51A016B6-F0DE-4752-B97C-54E6F386A912}]LOG]!><time="10:44:14.153+480" date="08-13-2014" component="TSPxe" context="" type="1" thread="1116"
file="environmentscope.cpp:623">
<![LOG[Creating key 'Software\Microsoft\SMS\47006C006F00620061006C005C007B00420041003300410033003900300030002D0043004100360044002D0034006100630031002D0038004300320038002D003500300037003300410046004300320032004200300033007D00']LOG]!><time="10:44:14.153+480"
date="08-13-2014" component="TSPxe" context="" type="1" thread="1116" file="environmentscope.cpp:263">
<![LOG[Environment scope successfully created: Global\{BA3A3900-CA6D-4ac1-8C28-5073AFC22B03}]LOG]!><time="10:44:14.153+480" date="08-13-2014" component="TSPxe" context="" type="1" thread="1116"
file="environmentscope.cpp:623">
<![LOG[Setting LogMaxSize to 1000000]LOG]!><time="10:44:14.153+480" date="08-13-2014" component="TSPxe" context="" type="1" thread="1116" file="tsmediawizardcontrol.cpp:555">
<![LOG[Setting LogMaxHistory to 1]LOG]!><time="10:44:14.153+480" date="08-13-2014" component="TSPxe" context="" type="1" thread="1116" file="tsmediawizardcontrol.cpp:556">
<![LOG[Setting LogLevel to 0]LOG]!><time="10:44:14.153+480" date="08-13-2014" component="TSPxe" context="" type="1" thread="1116" file="tsmediawizardcontrol.cpp:557">
<![LOG[Setting LogEnabled to 1]LOG]!><time="10:44:14.153+480" date="08-13-2014" component="TSPxe" context="" type="1" thread="1116" file="tsmediawizardcontrol.cpp:558">
<![LOG[Setting LogDebug to 1]LOG]!><time="10:44:14.153+480" date="08-13-2014" component="TSPxe" context="" type="1" thread="1116" file="tsmediawizardcontrol.cpp:559">
<![LOG[UEFI: false]LOG]!><time="10:44:14.153+480" date="08-13-2014" component="TSPxe" context="" type="1" thread="1116" file="tsmediawizardcontrol.cpp:569">
<![LOG[Loading variables from the Task Sequencing Removable Media.]LOG]!><time="10:44:14.153+480" date="08-13-2014" component="TSPxe" context="" type="1" thread="1116" file="tsmediawizardcontrol.cpp:584">
<![LOG[Loading Media Variables from "X:\sms\data\variables.dat"]LOG]!><time="10:44:14.153+480" date="08-13-2014" component="TSPxe" context="" type="1" thread="1116" file="tsremovablemedia.cpp:322">
<![LOG[Succeeded loading resource DLL 'X:\sms\bin\x64\1033\TSRES.DLL']LOG]!><time="10:44:14.153+480" date="08-13-2014" component="TSPxe" context="" type="1" thread="1116" file="util.cpp:964">
<![LOG[Setting SMSTSMP TS environment variable]LOG]!><time="10:44:14.153+480" date="08-13-2014" component="TSPxe" context="" type="1" thread="1116" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSMediaGuid TS environment variable]LOG]!><time="10:44:14.153+480" date="08-13-2014" component="TSPxe" context="" type="1" thread="1116" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSBootMediaPackageID TS environment variable]LOG]!><time="10:44:14.153+480" date="08-13-2014" component="TSPxe" context="" type="1" thread="1116" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSHTTPPort TS environment variable]LOG]!><time="10:44:14.153+480" date="08-13-2014" component="TSPxe" context="" type="1" thread="1116" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSHTTPSPort TS environment variable]LOG]!><time="10:44:14.153+480" date="08-13-2014" component="TSPxe" context="" type="1" thread="1116" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSIISSSLState TS environment variable]LOG]!><time="10:44:14.169+480" date="08-13-2014" component="TSPxe" context="" type="1" thread="1116" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSLaunchMode TS environment variable]LOG]!><time="10:44:14.169+480" date="08-13-2014" component="TSPxe" context="" type="1" thread="1116" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSMediaPFX TS environment variable]LOG]!><time="10:44:14.169+480" date="08-13-2014" component="TSPxe" context="" type="1" thread="1116" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSPublicRootKey TS environment variable]LOG]!><time="10:44:14.169+480" date="08-13-2014" component="TSPxe" context="" type="1" thread="1116" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSSiteCode TS environment variable]LOG]!><time="10:44:14.169+480" date="08-13-2014" component="TSPxe" context="" type="1" thread="1116" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSSiteSigningCertificate TS environment variable]LOG]!><time="10:44:14.169+480" date="08-13-2014" component="TSPxe" context="" type="1" thread="1116" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSUseFirstCert TS environment variable]LOG]!><time="10:44:14.169+480" date="08-13-2014" component="TSPxe" context="" type="1" thread="1116" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSx64UnknownMachineGUID TS environment variable]LOG]!><time="10:44:14.169+480" date="08-13-2014" component="TSPxe" context="" type="1" thread="1116" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSx86UnknownMachineGUID TS environment variable]LOG]!><time="10:44:14.169+480" date="08-13-2014" component="TSPxe" context="" type="1" thread="1116" file="tsmediawizardcontrol.cpp:604">
<![LOG[Root CA Public Certs=]LOG]!><time="10:44:14.169+480" date="08-13-2014" component="TSPxe" context="" type="1" thread="1116" file="tsmediawizardcontrol.cpp:615">
<![LOG[Missing root CA environment variable from variables file]LOG]!><time="10:44:14.169+480" date="08-13-2014" component="TSPxe" context="" type="1" thread="1116" file="tsmediawizardcontrol.cpp:621">
<![LOG[Support Unknown Machines: 0]LOG]!><time="10:44:14.169+480" date="08-13-2014" component="TSPxe" context="" type="1" thread="1116" file="tsmediawizardcontrol.cpp:632">
<![LOG[Custom hook from X:\\TSConfig.INI is ]LOG]!><time="10:44:14.169+480" date="08-13-2014" component="TSPxe" context="" type="1" thread="1116" file="tsmediawizardcontrol.cpp:675">
<![LOG[No hook is found to be executed before downloading policy]LOG]!><time="10:44:14.169+480" date="08-13-2014" component="TSPxe" context="" type="1" thread="1116" file="tsmediawizardcontrol.cpp:699">
<![LOG[Authenticator from the environment is empty.]LOG]!><time="10:44:14.169+480" date="08-13-2014" component="TSPxe" context="" type="1" thread="1116" file="tsmediawizardcontrol.cpp:838">
<![LOG[Need to create Authenticator Info using PFX]LOG]!><time="10:44:14.169+480" date="08-13-2014" component="TSPxe" context="" type="1" thread="1116" file="tsmediawizardcontrol.cpp:850">
<![LOG[Initialized CStringStream object with string: 6b7b5b1a-8a29-40a1-af6b-008746965168;2014-08-13T18:44:14Z.]LOG]!><time="10:44:14.200+480" date="08-13-2014" component="TSPxe" context="" type="0"
thread="1116" file="stringstream.cpp:101">
<![LOG[Set media certificate in transport]LOG]!><time="10:44:14.216+480" date="08-13-2014" component="TSPxe" context="" type="0" thread="1116" file="libsmsmessaging.cpp:9401">
<![LOG[Set authenticator in transport]LOG]!><time="10:44:14.216+480" date="08-13-2014" component="TSPxe" context="" type="0" thread="1116" file="libsmsmessaging.cpp:7734">
<![LOG[CLibSMSMessageWinHttpTransport::Send: URL: SS01.adskevents.local:80 GET /SMS_MP/.sms_aut?MPKEYINFORMATIONMEDIA]LOG]!><time="10:44:14.216+480" date="08-13-2014" component="TSPxe" context="" type="1"
thread="1116" file="libsmsmessaging.cpp:8604">
<![LOG[Executing command line: X:\WINDOWS\system32\cmd.exe /k]LOG]!><time="10:44:15.939+480" date="08-13-2014" component="TSBootShell" context="" type="1" thread="904" file="bootshell.cpp:860">
<![LOG[The command completed successfully.]LOG]!><time="10:44:15.939+480" date="08-13-2014" component="TSBootShell" context="" type="1" thread="904" file="bootshell.cpp:942">
<![LOG[Successfully launched command shell.]LOG]!><time="10:44:15.939+480" date="08-13-2014" component="TSBootShell" context="" type="1" thread="904" file="bootshell.cpp:432">
<![LOG[Error. Received 0x80072ee2 from WinHttpSendRequest.]LOG]!><time="10:44:35.281+480" date="08-13-2014" component="TSPxe" context="" type="1" thread="1116" file="libsmsmessaging.cpp:8870">
<![LOG[hr, HRESULT=80072ee2 (e:\nts_sccm_release\sms\framework\osdmessaging\libsmsmessaging.cpp,8919)]LOG]!><time="10:44:35.281+480" date="08-13-2014" component="TSPxe" context="" type="0" thread="1116"
file="libsmsmessaging.cpp:8919">
<![LOG[sending with winhttp failed; 80072ee2]LOG]!><time="10:44:35.281+480" date="08-13-2014" component="TSPxe" context="" type="3" thread="1116" file="libsmsmessaging.cpp:8919">
<![LOG[m_pHttpTransport->Send (0, 0, pServerReply, nReplySize), HRESULT=80072ee2 (e:\nts_sccm_release\sms\framework\osdmessaging\libsmsmessaging.cpp,5159)]LOG]!><time="10:44:35.281+480" date="08-13-2014" component="TSPxe"
context="" type="0" thread="1116" file="libsmsmessaging.cpp:5159">
<![LOG[MPKeyInformation.RequestMPKeyInformationForMedia(szTrustedRootKey), HRESULT=80072ee2 (e:\nts_sccm_release\sms\framework\osdmessaging\libsmsmessaging.cpp,9410)]LOG]!><time="10:44:35.281+480" date="08-13-2014" component="TSPxe"
context="" type="0" thread="1116" file="libsmsmessaging.cpp:9410">
<![LOG[Failed to get information for MP: http://SS01.adskevents.local. 80072ee2.]LOG]!><time="10:44:35.281+480" date="08-13-2014" component="TSPxe" context="" type="3" thread="1116" file="tsmbootstraputil.cpp:1518">
<![LOG[sMP.length() > 0, HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmbootstraputil.cpp,1526)]LOG]!><time="10:44:35.281+480" date="08-13-2014" component="TSPxe" context=""
type="0" thread="1116" file="tsmbootstraputil.cpp:1526">
<![LOG[TSMBootstrapUtil::SelectMP ( sSMSTSMP.c_str(), sMediaPfx.c_str(), sMediaGuid.c_str(), sAuthenticator.c_str(), sEnterpriseCert.c_str(), sServerCerts.c_str(), nHttpPort, nHttpsPort, bUseCRL, sSiteCode, sAssignedSiteCode, sMP, sCertificates, sX86UnknownMachineGUID,
sX64UnknownMachineGUID), HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,907)]LOG]!><time="10:44:35.281+480" date="08-13-2014" component="TSPxe" context=""
type="0" thread="1116" file="tsmediawizardcontrol.cpp:907">
<![LOG[Exiting TSMediaWizardControl::GetPolicy.]LOG]!><time="10:44:35.281+480" date="08-13-2014" component="TSPxe" context="" type="0" thread="1116" file="tsmediawizardcontrol.cpp:1419">
<![LOG[GetPolicy(), HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,2492)]LOG]!><time="10:44:35.281+480" date="08-13-2014" component="TSPxe" context=""
type="0" thread="1116" file="tsmediawizardcontrol.cpp:2492">
<![LOG[RunWizardForPXE(), HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,2834)]LOG]!><time="10:44:35.281+480" date="08-13-2014" component="TSPxe" context=""
type="0" thread="1116" file="tsmediawizardcontrol.cpp:2834">
<![LOG[oTSMediaWizardControl.Run( sMediaRoot, true, sTSLaunchMode ), HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmbootstrap.cpp,1078)]LOG]!><time="10:44:35.281+480" date="08-13-2014" component="TSPxe"
context="" type="0" thread="1116" file="tsmbootstrap.cpp:1078">
<![LOG[Execute( eExecutionEnv, sConfigPath, sTSXMLFile, uBootCount, &uExitCode ), HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmbootstrap.cpp,1226)]LOG]!><time="10:44:35.281+480" date="08-13-2014"
component="TSPxe" context="" type="0" thread="1116" file="tsmbootstrap.cpp:1226">
<![LOG[Exiting with return code 0x80004005]LOG]!><time="10:44:35.281+480" date="08-13-2014" component="TSPxe" context="" type="1" thread="1116" file="tsmbootstrap.cpp:1238">
<![LOG[Execution complete.]LOG]!><time="10:44:35.281+480" date="08-13-2014" component="TSBootShell" context="" type="1" thread="908" file="bootshell.cpp:693">
<![LOG[hMap != 0, HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentscope.cpp,493)]LOG]!><time="10:44:35.281+480" date="08-13-2014" component="TSBootShell" context="" type="0"
thread="908" file="environmentscope.cpp:493">
<![LOG[m_pGlobalScope->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,335)]LOG]!><time="10:44:35.281+480" date="08-13-2014" component="TSBootShell" context="" type="0"
thread="908" file="environmentlib.cpp:335">
<![LOG[this->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,553)]LOG]!><time="10:44:35.281+480" date="08-13-2014" component="TSBootShell" context="" type="0"
thread="908" file="environmentlib.cpp:553">
<![LOG[::RegOpenKeyExW (HKEY_LOCAL_MACHINE, sKey.c_str(), 0, KEY_READ, &hSubKey), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\utils.cpp,809)]LOG]!><time="10:44:35.281+480" date="08-13-2014" component="TSBootShell"
context="" type="0" thread="908" file="utils.cpp:809">
<![LOG[RegOpenKeyExW is unsuccessful for Software\Microsoft\SMS\Task Sequence]LOG]!><time="10:44:35.281+480" date="08-13-2014" component="TSBootShell" context="" type="2" thread="908"
file="utils.cpp:809">
<![LOG[GetTsRegValue() is unsuccessful. 0x80070002.]LOG]!><time="10:44:35.281+480" date="08-13-2014" component="TSBootShell" context="" type="2" thread="908" file="utils.cpp:842">
<![LOG[End program: ]LOG]!><time="10:44:35.281+480" date="08-13-2014" component="TSBootShell" context="" type="1" thread="908" file="bootshell.cpp:725">
<![LOG[Finalizing logging from process 900]LOG]!><time="10:44:35.281+480" date="08-13-2014" component="TSBootShell" context="" type="1" thread="908" file="tslogging.cpp:1741">
<![LOG[Finalizing logs to root of first available drive]LOG]!><time="10:44:35.281+480" date="08-13-2014" component="TSBootShell" context="" type="1" thread="908" file="tslogging.cpp:1583">
<![LOG[Successfully finalized logs to C:\SMSTSLog]LOG]!><time="10:44:35.687+480" date="08-13-2014" component="TSBootShell" context="" type="1" thread="908" file="tslogging.cpp:1640">
<![LOG[Cleaning up task sequencing logging configuration.]LOG]!><time="10:44:35.687+480" date="08-13-2014" component="TSBootShell" context="" type="0" thread="908" file="tslogging.cpp:584">Every time a query is sent to the MP, it receives 0x80072ee2 which translates to "The operation timed out". This has nothing to do with your MP or DP though so reinstalling them won't make any difference.
This error is indicative of network issues -- basically, the "client" is not getting a response back in a timely manner (and probably not at all). Assuming the MP is healthy though, then only other piece of the puzzle is the network.
You can try setting the SMSTSAssignmentsDownloadRetry and SMSTSAssignmentsDownloadInterval task sequence variables in the boot image to increase the client's tolerance for latency or other weirdness in the network. This has worked for many.
If that doesn't work, you'll have to break out a sniffer and watch the traffic to see what's going on at a network level.
Jason | http://blog.configmgrftw.com -
Hello to everyone!I have noticed that many times,my N78 reboots after I receive a missed call.On the top right of the screen appears something like a talk bubble containing a phone icon that turns from green to orange and back.After this happens,my phone reboots.I did restore factory setting but nothing changed..I notice that this problem stops when I get the microSD out of the phone.I thought that there is a file containing virus in it..but I replaced my microSD with an empty new one but reboot goes on...Please help I cant stand the 60mb phone memory!
Hello there, Abomosa.
The following Knowledge Base article offers up some practical steps to try for troubleshooting issues with an application not performing as expected:
iOS: Understanding multitasking
http://support.apple.com/kb/ht4211
When performing Step 2, I would recommend closing all applications that are running. If you perform Step 3 and the issue persists, you may want to try resetting as well:
If an app doesn't respond to your input, or doesn't perform as expected, do the following, testing after each step:
Check for app updates.
Force the app to close.
Restart your device.
Update your iOS device.
Learn more about troubleshooting apps.
Additionally this article offers some great information for Display issues as well:
iPhone: Hardware troubleshooting
http://support.apple.com/kb/ts2802
If you find the issue is still unresolved that same article offers the following:
My issue is still not resolved. What do I do next?
Contact Apple Support.
Thanks for reaching out to Apple Support Communities.
Cheers,
Pedro. -
PFC configuration on Nexus 5000
Hi,
I have a CNA in my server connected to cisco nexus 5000 interfcae. I Want to genearate pause frames for FCOE class of traffic using the default class class-fcoe and cos value 3, the firmware version running is 5.0(3) N1 (1b). Can anyone tell me how can i configure it ?
Thanks,
ManjuSorry for the delayed response, Here is what you asked
Cisco-5020# sh mod
Mod Ports Module-Type Model Status
1 40 40x10GE/Supervisor N5K-C5020P-BF-SUP active *
2 8 4x10GE + 4x1/2/4G FC Module N5K-M1404 ok
Mod Sw Hw World-Wide-Name(s) (WWN)
1 5.0(3)N1(1b) 1.2 --
2 5.0(3)N1(1b) 1.0 20:41:00:0d:ec:b2:15:40 to 20:44:00:0d:ec:b2:15:40
Mod MAC-Address(es) Serial-Num
1 000d.ecb2.1548 to 000d.ecb2.156f JAF1303ACES
2 000d.ecb2.1570 to 000d.ecb2.1577 JAF1245AJLF
Cisco-5020#
Cisco-5020#
Cisco-5020# sh run
!Command: show running-config
!Time: Fri Oct 28 17:40:02 2005
version 5.0(3)N1(1b)
feature fcoe
feature npiv
feature telnet
feature lldp
username admin password 5 $1$v9Tm8Y77$ZSdbOfBxe1.Z9Oz1V9V2B0 role network-admin
no password strength-check
ip domain-lookup
hostname Cisco-5020
logging event link-status default
service unsupported-transceiver
class-map type qos class-fcoe
class-map type queuing class-all-flood
match qos-group 2
class-map type queuing class-ip-multicast
match qos-group 2
class-map type network-qos class-all-flood
match qos-group 2
class-map type network-qos class-ip-multicast
match qos-group 2
policy-map type network-qos jumbo
class type network-qos class-fcoe
pause no-drop
mtu 2158
class type network-qos class-default
mtu 9216
system qos
service-policy type network-qos jumbo
snmp-server user admin network-admin auth md5 0x2694501fdfbe5abed9e85d51e4e31038 priv 0x2694501fdfbe5abed9e85d51e4e31038 localizedkey
snmp-server host 138.239.198.184 traps version 2c public udp-port 1163
snmp-server host 138.239.198.184 traps version 2c public udp-port 1164
snmp-server host 138.239.198.200 traps version 2c public udp-port 1163
snmp-server host 138.239.198.200 traps version 2c public udp-port 1164
snmp-server host 138.239.200.118 traps version 2c public udp-port 1163
snmp-server host 138.239.198.200 traps version 2c public udp-port 1163
snmp-server enable traps entity fru
snmp-server community snmpv3 group network-operator
vrf context management
ip route 0.0.0.0/0 10.192.207.254
vlan 1-2,8
vlan 10
fcoe vsan 10
vlan 20
fcoe vsan 20
vlan 30
vlan 35
fcoe vsan 35
vlan 40,50
vlan 52
fcoe vsan 52
vsan database
vsan 20
vsan 52
fcdomain fcid database
vsan 52 wwn 10:00:00:00:c9:b1:e5:3d fcid 0x180000 dynamic
vsan 52 wwn 10:00:00:00:c9:b1:e5:3b fcid 0x180001 dynamic
vsan 52 wwn 10:00:00:00:c9:5b:4d:e3 fcid 0x180002 dynamic
vsan 52 wwn 10:00:00:00:c9:5b:ab:ad fcid 0x180003 dynamic
vsan 52 wwn 10:00:00:00:c9:ad:ac:41 fcid 0x180004 dynamic
vsan 52 wwn 10:00:00:00:c9:ad:ac:b9 fcid 0x180005 dynamic
vsan 52 wwn 10:00:00:00:c9:ad:ac:b5 fcid 0x180006 dynamic
vsan 52 wwn 10:00:00:00:c9:f2:73:d1 fcid 0x180007 dynamic
vsan 52 wwn 10:00:00:00:c9:5b:4d:e1 fcid 0x180008 dynamic
vsan 52 wwn 10:00:00:00:c9:5b:ab:a9 fcid 0x180009 dynamic
vsan 52 wwn 10:00:00:00:c9:f2:73:d5 fcid 0x18000a dynamic
vsan 52 wwn 10:00:00:00:c9:b1:e5:5d fcid 0x18000b dynamic
vsan 52 wwn 10:00:00:00:c9:5b:ab:9b fcid 0x18000c dynamic
vsan 52 wwn 10:00:00:00:c9:5b:ab:99 fcid 0x18000d dynamic
vsan 52 wwn 10:00:00:00:c9:b1:e5:5b fcid 0x18000e dynamic
vsan 1 wwn 10:00:00:00:c9:f2:73:b3 fcid 0x050000 dynamic
vsan 52 wwn 10:00:00:00:c9:ad:ac:47 fcid 0x18000f dynamic
vsan 52 wwn 10:00:00:00:c9:5b:a7:93 fcid 0x180010 dynamic
vsan 52 wwn 10:00:00:00:c9:91:f8:19 fcid 0x180011 dynamic
vsan 52 wwn 10:00:00:00:c9:9c:e0:77 fcid 0x180012 dynamic
vsan 52 wwn 10:00:00:00:c9:5b:a7:d3 fcid 0x180013 dynamic
vsan 52 wwn 10:00:00:00:c9:5b:a3:bb fcid 0x180014 dynamic
vsan 52 wwn 10:00:00:00:c9:97:3b:c5 fcid 0x180015 dynamic
vsan 52 wwn 10:00:00:00:c9:f2:73:91 fcid 0x180016 dynamic
vsan 52 wwn 10:00:00:00:c9:a4:00:91 fcid 0x180017 dynamic
vsan 52 wwn 10:00:00:00:c9:f2:73:8d fcid 0x180018 dynamic
vsan 52 wwn 20:0f:00:11:0d:7f:a8:00 fcid 0x180019 dynamic
vsan 52 wwn 20:0f:00:11:0d:7f:a8:01 fcid 0x18001a dynamic
vsan 52 wwn 10:00:00:00:c9:5b:a3:b7 fcid 0x18001b dynamic
vsan 52 wwn 10:00:00:00:c9:5b:a5:27 fcid 0x18001c dynamic
vsan 52 wwn 10:00:00:00:c9:5b:a3:53 fcid 0x18001d dynamic
vsan 52 wwn 10:00:00:00:c9:bb:c8:37 fcid 0x18001e dynamic
vsan 52 wwn 10:00:00:00:c9:5b:76:e5 fcid 0x18001f dynamic
vsan 20 wwn 10:00:00:00:c9:5b:a3:83 fcid 0xd30000 dynamic
vsan 52 wwn 10:00:00:00:c9:91:00:00 fcid 0x180020 dynamic
vsan 52 wwn 10:00:00:00:00:91:f7:f1 fcid 0x180021 dynamic
vsan 1 wwn 10:00:00:00:c9:5b:4d:e3 fcid 0x050001 dynamic
vsan 52 wwn 10:00:00:00:c9:97:3b:0f fcid 0x180022 dynamic
vsan 52 wwn 10:00:00:00:c9:3c:8e:21 fcid 0x180023 dynamic
vsan 52 wwn 10:00:00:00:c9:97:3b:11 fcid 0x180024 dynamic
vsan 20 wwn 10:00:00:00:c9:b1:e6:b7 fcid 0xd30001 dynamic
vsan 52 wwn 10:00:f8:19:00:91:f8:19 fcid 0x180025 dynamic
vsan 52 wwn 10:00:00:00:c9:5b:a3:8b fcid 0x180026 dynamic
vsan 52 wwn 10:00:00:00:c9:b1:e4:ff fcid 0x180027 dynamic
vsan 52 wwn 10:00:00:00:c9:3c:8e:25 fcid 0x180028 dynamic
vsan 52 wwn 50:06:01:61:44:60:23:4f fcid 0x1800ef dynamic
vsan 52 wwn 10:00:00:00:c9:5b:d6:b9 fcid 0x180029 dynamic
vsan 52 wwn 10:00:00:00:c9:ad:ac:43 fcid 0x18002a dynamic
vsan 52 wwn 20:01:00:00:c9:5b:ab:99 fcid 0x18002b dynamic
vsan 52 wwn 20:02:00:00:c9:5b:ab:99 fcid 0x18002c dynamic
vsan 52 wwn 50:06:01:60:44:60:23:4f fcid 0x1801ef dynamic
vsan 52 wwn 10:00:00:00:c9:9d:1f:bf fcid 0x18002d dynamic
vsan 52 wwn 10:00:00:00:c9:9d:1f:c1 fcid 0x18002e dynamic
vsan 52 wwn 10:00:00:00:c9:f2:73:d3 fcid 0x18002f dynamic
vsan 20 wwn 10:00:00:00:c9:bb:c8:37 fcid 0xd30002 dynamic
vsan 52 wwn 10:00:00:00:c9:12:34:56 fcid 0x180030 dynamic
vsan 52 wwn 10:00:00:00:c9:12:34:57 fcid 0x180031 dynamic
vsan 52 wwn 10:00:00:00:c9:b1:ea:81 fcid 0x180032 dynamic
vsan 52 wwn 10:00:00:00:c9:b1:ea:7f fcid 0x180033 dynamic
vsan 20 wwn 10:00:00:00:c9:12:34:56 fcid 0xd30003 dynamic
vsan 52 wwn 10:00:00:00:c9:b1:e5:1b fcid 0x180034 dynamic
vsan 52 wwn 10:00:00:00:c9:b1:e5:1d fcid 0x180035 dynamic
vsan 52 wwn 10:00:00:00:c9:bb:c7:8f fcid 0x180036 dynamic
vsan 52 wwn 10:00:00:00:c9:bb:cb:8f fcid 0x180037 dynamic
vsan 52 wwn 10:00:00:00:c9:bb:cb:93 fcid 0x180038 dynamic
vsan 52 wwn 10:00:00:00:c9:bb:c7:93 fcid 0x180039 dynamic
vsan 20 wwn 10:00:00:00:c9:12:34:57 fcid 0xd30004 dynamic
vsan 52 wwn 10:00:00:00:c9:5b:ab:c4 fcid 0x18003a dynamic
vsan 52 wwn 10:00:00:00:c9:bb:17:b7 fcid 0x18003b dynamic
vsan 52 wwn 10:00:00:00:c9:a0:ce:2d fcid 0x18003c dynamic
vsan 52 wwn 10:00:00:00:c9:91:f7:f1 fcid 0x18003d dynamic
vsan 52 wwn 10:00:00:00:c9:5b:ab:c0 fcid 0x18003e dynamic
vsan 52 wwn 10:00:00:00:c9:b1:e5:5f fcid 0x18003f dynamic
vsan 52 wwn 10:00:00:00:c9:e3:06:89 fcid 0x180040 dynamic
vsan 52 wwn 50:06:01:68:44:60:23:4f fcid 0x1802ef dynamic
vsan 1 wwn 50:06:01:61:44:60:23:4f fcid 0x0500ef dynamic
vsan 52 wwn 10:00:00:00:c9:d1:16:24 fcid 0x180041 dynamic
vsan 52 wwn 10:00:00:00:c9:d1:16:25 fcid 0x180042 dynamic
vsan 52 wwn 10:00:00:00:c9:d1:0a:6d fcid 0x180043 dynamic
vsan 20 wwn 10:00:00:00:c9:d1:16:25 fcid 0xd30005 dynamic
vsan 20 wwn 10:00:00:00:c9:d1:16:24 fcid 0xd30006 dynamic
vsan 20 wwn ff:f2:00:00:c9:12:34:78 fcid 0xd30007 dynamic
vsan 20 wwn ff:f2:00:00:c9:d1:16:46 fcid 0xd30008 dynamic
vsan 52 wwn ff:f2:00:00:c9:d1:0a:8c fcid 0x180044 dynamic
vsan 20 wwn ff:f3:00:00:c9:d1:16:46 fcid 0xd30009 dynamic
vsan 52 wwn ff:f0:00:00:c9:d1:0a:8c fcid 0x180045 dynamic
vsan 52 wwn 10:00:00:00:c9:d1:0a:6c fcid 0x180046 dynamic
vsan 20 wwn ff:f2:00:00:c9:d1:0a:8c fcid 0xd3000a dynamic
vsan 20 wwn 10:00:00:00:c9:d1:0a:6d fcid 0xd3000b dynamic
vsan 52 wwn ff:f2:00:00:c9:d1:16:46 fcid 0x180047 dynamic
vsan 20 wwn ff:f3:00:00:c9:12:34:78 fcid 0xd3000c dynamic
vsan 52 wwn ff:f3:00:00:c9:12:34:78 fcid 0x180048 dynamic
vsan 52 wwn 50:06:01:69:44:60:23:4f fcid 0x1803ef dynamic
vsan 52 wwn ff:f3:00:00:c9:d1:16:46 fcid 0x180049 dynamic
vsan 52 wwn 10:00:00:00:c9:12:34:5b fcid 0x18004a dynamic
vsan 52 wwn 10:00:00:00:c9:12:34:5a fcid 0x18004b dynamic
vsan 52 wwn ff:f2:00:00:c9:12:34:78 fcid 0x18004c dynamic
vsan 52 wwn 10:00:00:00:c9:a5:ac:f3 fcid 0x18004d dynamic
vsan 52 wwn 10:00:00:00:c9:a5:ad:15 fcid 0x18004e dynamic
vsan 52 wwn 10:00:00:00:c9:a5:ac:f5 fcid 0x18004f dynamic
vsan 52 wwn 20:01:00:00:c9:a5:ac:f3 fcid 0x180050 dynamic
vsan 52 wwn 20:02:00:00:c9:a5:ac:f3 fcid 0x180051 dynamic
vsan 52 wwn ff:f3:00:00:c9:12:34:85 fcid 0x180052 dynamic
vsan 52 wwn 20:00:00:11:0d:77:9c:00 fcid 0x180053 dynamic
vsan 52 wwn 20:01:00:11:0d:77:9d:00 fcid 0x180054 dynamic
interface port-channel3
interface vfc1
no shutdown
interface vfc4
interface vfc9
bind interface Ethernet1/9
no shutdown
interface vfc10
interface vfc11
bind interface Ethernet1/11
no shutdown
interface vfc19
bind interface Ethernet1/19
no shutdown
interface vfc21
bind interface Ethernet1/21
no shutdown
interface vfc22
bind interface Ethernet1/22
switchport trunk allowed vsan 52
no shutdown
interface vfc24
bind interface Ethernet1/24
switchport trunk allowed vsan 52
no shutdown
interface vfc25
bind interface Ethernet1/25
switchport trunk allowed vsan 52
no shutdown
interface vfc26
bind interface Ethernet1/26
switchport trunk allowed vsan 52
no shutdown
interface vfc27
bind interface Ethernet1/27
no shutdown
interface vfc28
bind interface Ethernet1/28
no shutdown
interface vfc29
bind interface Ethernet1/29
no shutdown
interface vfc30
bind interface Ethernet1/30
switchport trunk allowed vsan 52
no shutdown
interface vfc31
bind interface Ethernet1/31
shutdown
interface vfc32
bind interface Ethernet1/32
no shutdown
interface vfc33
bind interface Ethernet1/33
no shutdown
interface vfc34
bind interface Ethernet1/34
no shutdown
interface vfc35
bind interface Ethernet1/35
no shutdown
interface vfc36
bind interface Ethernet1/36
no shutdown
interface vfc37
bind interface Ethernet1/37
no shutdown
interface vfc38
bind interface Ethernet1/38
no shutdown
interface vfc39
bind interface Ethernet1/39
no shutdown
interface vfc40
bind interface Ethernet1/40
no shutdown
vsan database
vsan 52 interface vfc1
vsan 52 interface vfc9
vsan 52 interface vfc11
vsan 52 interface vfc19
vsan 52 interface vfc21
vsan 52 interface vfc22
vsan 52 interface vfc24
vsan 52 interface vfc26
vsan 52 interface vfc27
vsan 52 interface vfc28
vsan 52 interface vfc29
vsan 52 interface vfc30
vsan 52 interface vfc31
vsan 52 interface vfc32
vsan 52 interface vfc33
vsan 52 interface vfc34
vsan 20 interface vfc35
vsan 52 interface vfc36
vsan 52 interface vfc37
vsan 52 interface vfc38
vsan 52 interface vfc39
vsan 52 interface vfc40
vsan 52 interface fc2/1
vsan 52 interface fc2/2
vsan 52 interface fc2/3
vsan 52 interface fc2/4
interface fc2/1
switchport trunk allowed vsan 1
switchport trunk allowed vsan add 52
switchport trunk mode auto
no shutdown
interface fc2/2
switchport trunk mode auto
no shutdown
interface fc2/3
no shutdown
interface fc2/4
no shutdown
interface Ethernet1/1
interface Ethernet1/2
speed 1000
interface Ethernet1/3
interface Ethernet1/4
interface Ethernet1/5
interface Ethernet1/6
interface Ethernet1/7
switchport mode trunk
interface Ethernet1/8
interface Ethernet1/9
switchport mode trunk
switchport trunk allowed vlan 1,10,20,52
flowcontrol receive on
flowcontrol send on
interface Ethernet1/10
interface Ethernet1/11
priority-flow-control mode on
switchport mode trunk
switchport trunk allowed vlan 1,52
flowcontrol receive on
flowcontrol send on
interface Ethernet1/12
switchport mode trunk
interface Ethernet1/13
switchport mode trunk
flowcontrol receive on
flowcontrol send on
interface Ethernet1/14
switchport mode trunk
flowcontrol receive on
flowcontrol send on
interface Ethernet1/15
switchport mode trunk
flowcontrol receive on
flowcontrol send on
interface Ethernet1/16
switchport mode trunk
flowcontrol receive on
flowcontrol send on
interface Ethernet1/17
interface Ethernet1/18
switchport mode trunk
switchport trunk allowed vlan 1,30
interface Ethernet1/19
switchport mode trunk
switchport access vlan 10
switchport trunk allowed vlan 1,52
flowcontrol receive on
flowcontrol send on
interface Ethernet1/20
switchport mode trunk
switchport access vlan 52
switchport trunk allowed vlan 1,52
flowcontrol receive on
flowcontrol send on
interface Ethernet1/21
switchport mode trunk
switchport trunk allowed vlan 1,52
flowcontrol receive on
flowcontrol send on
interface Ethernet1/22
interface Ethernet1/23
flowcontrol receive on
flowcontrol send on
interface Ethernet1/24
switchport mode trunk
switchport access vlan 52
switchport trunk allowed vlan 1,52
flowcontrol receive on
flowcontrol send on
interface Ethernet1/25
switchport mode trunk
switchport trunk allowed vlan 1,8,30,52
interface Ethernet1/26
switchport mode trunk
switchport access vlan 52
switchport trunk allowed vlan 1,8,30,52
interface Ethernet1/27
switchport mode trunk
flowcontrol receive on
flowcontrol send on
interface Ethernet1/28
switchport mode trunk
switchport trunk allowed vlan 1,8,30,52
flowcontrol receive on
flowcontrol send on
interface Ethernet1/29
switchport mode trunk
switchport trunk allowed vlan 1,52
flowcontrol receive on
flowcontrol send on
interface Ethernet1/30
description line
switchport mode trunk
switchport access vlan 52
switchport trunk allowed vlan 1,8,30,52
flowcontrol receive on
flowcontrol send on
interface Ethernet1/31
switchport mode trunk
switchport trunk allowed vlan 1,10,20,52
interface Ethernet1/32
switchport mode trunk
switchport trunk allowed vlan 1,10,52
flowcontrol receive on
flowcontrol send on
interface Ethernet1/33
switchport mode trunk
switchport trunk allowed vlan 1,52
flowcontrol receive on
flowcontrol send on
interface Ethernet1/34
switchport mode trunk
switchport trunk allowed vlan 1,52
flowcontrol receive on
flowcontrol send on
interface Ethernet1/35
switchport mode trunk
switchport access vlan 10
switchport trunk allowed vlan 1,10,52
flowcontrol receive on
flowcontrol send on
interface Ethernet1/36
switchport mode trunk
switchport trunk allowed vlan 1,30,52
flowcontrol receive on
flowcontrol send on
interface Ethernet1/37
switchport mode trunk
switchport trunk allowed vlan 1,30,52
flowcontrol receive on
flowcontrol send on
interface Ethernet1/38
switchport mode trunk
switchport trunk allowed vlan 1,10,52
flowcontrol receive on
flowcontrol send on
interface Ethernet1/39
shutdown
switchport mode trunk
switchport trunk allowed vlan 1,10,20,52
flowcontrol receive on
flowcontrol send on
interface Ethernet1/40
switchport mode trunk
switchport trunk allowed vlan 1,52
flowcontrol receive on
flowcontrol send on
interface Ethernet2/1
switchport mode trunk
flowcontrol receive on
flowcontrol send on
interface Ethernet2/2
switchport mode trunk
flowcontrol receive on
flowcontrol send on
interface Ethernet2/3
switchport mode trunk
flowcontrol receive on
flowcontrol send on
interface Ethernet2/4
switchport mode trunk
flowcontrol receive on
flowcontrol send on
interface mgmt0
ip address 10.192.194.111/20
system default zone default-zone permit
system default zone distribute full
line console
line vty
boot kickstart bootflash:/n5000-uk9-kickstart.5.0.3.N1.1b.bin
boot system bootflash:/n5000-uk9.5.0.3.N1.1b.bin
interface fc2/1
interface fc2/2
interface fc2/3
interface fc2/4
zone default-zone permit vsan 20
zone default-zone permit vsan 52
zoneset distribute full vsan 1
zoneset distribute full vsan 20
zoneset distribute full vsan 52
!Full Zone Database Section for vsan 1
zone name bg-qa vsan 1
member pwwn 10:00:00:00:c9:5b:ab:ca
member pwwn 21:00:00:0c:50:c3:70:23
member pwwn 21:00:00:0c:50:c3:70:22
member pwwn 21:00:00:0c:50:c3:70:16
member pwwn 21:00:00:0c:50:c3:70:1e
member pwwn 22:00:00:0c:50:c3:70:26
member pwwn 22:00:00:18:62:06:76:8a
member pwwn 22:00:00:11:c6:17:68:c3
member pwwn 22:00:00:0c:50:c3:70:1d
member pwwn 22:00:00:0c:50:c3:6f:c2
member pwwn 22:00:00:11:c6:17:68:dc
member pwwn 21:00:00:0c:50:c3:6a:d0
member pwwn 21:00:00:0c:50:79:92:90
member pwwn 21:00:00:11:c6:17:69:a0
member pwwn 21:00:00:0c:50:79:93:af
member pwwn 22:00:00:0c:50:48:10:80
member pwwn 22:00:00:11:c6:18:46:c6
member pwwn 22:00:00:0c:50:32:2e:0f
member pwwn 22:00:00:0c:50:48:10:74
member pwwn 22:00:00:11:c6:18:46:f2
member pwwn 21:00:00:00:87:13:cb:d1
member pwwn 21:00:00:0c:50:79:91:0f
member pwwn 10:00:00:00:c9:3c:8e:49
member pwwn 10:00:00:00:c9:5b:ab:c2
member pwwn 10:00:00:00:c9:5b:af:f3
zone name sf_RAM vsan 1
member pwwn 10:00:00:00:c9:5b:af:c9
member pwwn 21:00:00:0c:50:b4:8e:20
zone name anand vsan 1
member pwwn 10:00:00:00:c9:65:69:31
member pwwn 22:00:00:18:62:06:7f:f6
zone name syedzone vsan 1
member fwwn 20:11:00:0d:ec:56:7b:40
member pwwn 50:06:01:60:44:60:23:4f
zone name bg_qa vsan 1
zoneset name TOM vsan 1
member bg-qa
zoneset name bg_dvt vsan 1
member sf_RAM
zoneset name lancer vsan 1
member anand
zoneset name bg-qa vsan 1
zoneset name syed vsan 1
member syedzone
zoneset activate name lancer vsan 1
!Full Zone Database Section for vsan 20
zone name amrita_zone1 vsan 20
member pwwn 10:00:00:00:c9:5b:a3:83
member pwwn 22:00:00:04:cf:89:19:67
member pwwn 22:00:00:0c:50:48:10:80
member pwwn 22:00:00:11:c6:18:46:f2
member pwwn 22:00:00:0c:50:79:93:ae
zone name amr_zset vsan 20
zoneset name amr_zset vsan 20
member amrita_zone1
zoneset activate name amr_zset vsan 20
!Full Zone Database Section for vsan 52
zone name vinod vsan 52
member pwwn 50:06:01:69:44:60:23:4f
member pwwn ff:f3:00:00:c9:12:34:78
member pwwn 10:00:00:00:c9:12:34:5b
member pwwn 10:00:00:00:c9:12:34:57
zone name neha vsan 52
zone name siv1 vsan 52
member pwwn 10:00:00:00:c9:ad:ac:43
member pwwn 50:06:01:61:44:60:23:4f
member pwwn 10:00:00:00:c9:ad:ac:47
zone name neha1 vsan 52
member pwwn 10:00:00:00:c9:5b:ab:ad
member pwwn 50:06:01:60:44:60:23:4f
zone name neha2 vsan 52
member pwwn 50:06:01:60:44:60:23:4f
member pwwn 10:00:00:00:c9:5b:ab:a9
zone name neha3 vsan 52
member pwwn 10:00:00:00:c9:9d:1f:bf
member pwwn 50:06:01:60:44:60:23:4f
zone name neha4 vsan 52
member pwwn 50:06:01:60:44:60:23:4f
member pwwn 10:00:00:00:c9:9d:1f:c1
zone name chetan vsan 52
member pwwn 10:00:00:00:c9:f2:73:d3
member pwwn 50:06:01:60:44:60:23:4f
member pwwn 10:00:00:00:c9:ad:ac:47
zone name siv2 vsan 52
member pwwn 10:00:00:00:c9:d1:0a:6d
member pwwn ff:f2:00:00:c9:d1:0a:8c
member pwwn 22:00:00:0c:50:79:93:af
member pwwn 22:00:00:0c:50:79:92:90
member pwwn 22:00:00:0c:50:79:91:0f
member pwwn 20:01:00:11:0d:77:9d:00
zone name sroy vsan 52
member pwwn 10:00:00:00:c9:b1:ea:7f
member pwwn 50:06:01:60:44:60:23:4f
member pwwn 10:00:00:00:c9:5b:ab:99
member pwwn 10:00:00:00:c9:bb:cb:8f
member pwwn 10:00:00:00:c9:5b:ab:c4
member pwwn 10:00:00:00:c9:d1:16:25
member pwwn 50:06:01:61:44:60:23:4f
member pwwn 10:00:00:00:c9:a5:ac:f3
zone name manju vsan 52
member pwwn 10:00:00:00:c9:bb:c7:8f
member pwwn 50:06:01:61:44:60:23:4f
zone name ram vsan 52
member pwwn 50:06:01:60:44:60:23:4f
member pwwn 10:00:00:00:c9:a0:ce:2d
member pwwn 10:00:00:00:c9:bb:17:b7
member pwwn 10:00:00:00:c9:5b:a5:27
member pwwn 10:00:00:00:c9:91:f7:f1
member pwwn 10:00:00:00:c9:b1:e5:5f
zone name jana vsan 52
member pwwn 10:00:00:00:c9:91:f7:f1
member pwwn 50:06:01:60:44:60:23:4f
zone name priya vsan 52
member pwwn 10:00:00:00:c9:e3:06:89
member pwwn 50:06:01:60:44:60:23:4f
zoneset name IBMraptor vsan 52
member vinod
member siv1
member neha1
member neha2
member neha3
member neha4
member chetan
member siv2
member sroy
member manju
member ram
member priya
zoneset name ananda vsan 52
zoneset name vinod vsan 52
zoneset activate name IBMraptor vsan 52
no system default switchport shutdown san
Cisco-5020# sh system internal dcbx info interface ethernet 1/38
Interface info for if_index: 0x1a025000(Eth1/38)
tx_enabled: TRUE
rx_enabled: TRUE
dcbx_enabled: TRUE
DCX Protocol: CIN
Port MAC address: 00:0d:ec:b2:15:6d
DCX Control FSM Variables: seq_no: 0x1, ack_no: 0x0,my_ack_no: 0x0, peer_seq_no:
0x0 oper_version: 0x0, max_version: 0x0 fast_retries 0x0
Lock Status: UNLOCKED
PORT STATE: UP
LLDP Neighbors
No DCX tlvs from the remote peer
6 Features on this intf for Protocol CIN(0)
3 Features on this intf for Protocol CEE(1)
6 Features on this intf for Protocol CIN(0)
Feature type LLS (6)sub_type FCoE Logical Link Status (0)
feature type 6(LLS)sub_type 0
Feature State Variables: oper_version 0 error 0 local error 0 oper_mode 0
feature_seq_no 0 remote_feature_tlv_present 0 remote_tlv_aged_out 0
remote_tlv_not_present_notification_sent 0
Feature Register Params: max_version 0, enable 1, willing 0 advertise 1
disruptive_error 0 mts_addr_node 0x101 mts_addr_sap 0x1d9
Desired config cfg length: 1 data bytes:00
Operating config cfg length: 0 data bytes:
Peer config cfg length: 0 data bytes:
Feature type PFC (3)
feature type 3(PFC)sub_type 0
Feature State Variables: oper_version 0 error 0 local error 0 oper_mode 0
feature_seq_no 0 remote_feature_tlv_present 0 remote_tlv_aged_out 1
remote_tlv_not_present_notification_sent 0
Feature Register Params: max_version 0, enable 1, willing 0 advertise 1
disruptive_error 0 mts_addr_node 0x101 mts_addr_sap 0x179
Desired config cfg length: 1 data bytes:08
Operating config cfg length: 0 data bytes:
Peer config cfg length: 0 data bytes:
Feature type App(Fcoe) (5)sub_type FCoE (0)
feature type 5(App(Fcoe))sub_type 0
Feature State Variables: oper_version 0 error 0 local error 0 oper_mode 0
feature_seq_no 0 remote_feature_tlv_present 0 remote_tlv_aged_out 1
remote_tlv_not_present_notification_sent 0
Feature Register Params: max_version 0, enable 1, willing 0 advertise 1
disruptive_error 0 mts_addr_node 0x101 mts_addr_sap 0x179
Desired config cfg length: 1 data bytes:08
Operating config cfg length: 0 data bytes:
Peer config cfg length: 0 data bytes:
Feature type PriMtu (8)
feature type 8(PriMtu)sub_type 0
Feature State Variables: oper_version 0 error 0 local error 0 oper_mode 0
feature_seq_no 0 remote_feature_tlv_present 0 remote_tlv_aged_out 1
remote_tlv_not_present_notification_sent 0
Feature Register Params: max_version 0, enable 1, willing 0 advertise 1
disruptive_error 0 mts_addr_node 0x101 mts_addr_sap 0x179
Desired config cfg length: 16 data bytes:24 00 24 00 24 00 08 6e 24 00 24 00 24 00 24 00
Operating config cfg length: 0 data bytes:
Peer config cfg length: 0 data bytes:
Feature type PriGrp (2)
feature type 2(PriGrp)sub_type 0
Feature State Variables: oper_version 0 error 0 local error 0 oper_mode 0
feature_seq_no 0 remote_feature_tlv_present 0 remote_tlv_aged_out 1
remote_tlv_not_present_notification_sent 0
Feature Register Params: max_version 0, enable 1, willing 0 advertise 1
disruptive_error 0 mts_addr_node 0x101 mts_addr_sap 0x179
Desired config cfg length: 24 data bytes:32 32 00 00 00 00 00 00 00 0f 00 0f 00 0e 20 64 00 0e 00 0e
00 0e 00 0e
Operating config cfg length: 0 data bytes:
Peer config cfg length: 0 data bytes:
Feature type LLS (6)sub_type LAN Logical Link Status (1)
feature type 6(LLS)sub_type 1
Feature State Variables: oper_version 0 error 0 local error 0 oper_mode 0
feature_seq_no 0 remote_feature_tlv_present 0 remote_tlv_aged_out 1
remote_tlv_not_present_notification_sent 0
Feature Register Params: max_version 0, enable 1, willing 0 advertise 1
disruptive_error 0 mts_addr_node 0x101 mts_addr_sap 0xaf
Desired config cfg length: 1 data bytes:80
Operating config cfg length: 0 data bytes:
Peer config cfg length: 0 data bytes:
Traffic Counters
DCBX pkt stats:
Total frames out: 20296
Total Entries aged: 27
Total frames in: 0
DCBX frames in: 0
Total frames received in error: 0
Total frames discarded: 0
Total TLVs unrecognized: 0
Cisco-5020#
Cisco-5020#
Cisco-5020#
I am new to this PFC, and first time trying to configure so you can see nothing being configured. -
We run 6509 core routers as NTP servers to other IOS routers/switches & servers of several OS flavours.
All good.
Recently added some Nexus 5000s and cannot get them to lock.
No firewalls or ACLs in the path
6509 (1 of 4) state:
LNPSQ01CORR01>sh ntp ass
address ref clock st when poll reach delay offset disp
+ 10.0.1.2 131.188.3.220 2 223 1024 377 0.5 -6.23 0.7
+~130.149.17.21 .PPS. 1 885 1024 377 33.7 -0.26 0.8
*~138.96.64.10 .GPS. 1 680 1024 377 22.7 -2.15 1.0
+~129.6.15.29 .ACTS. 1 720 1024 377 84.9 -3.37 0.6
+~129.6.15.28 .ACTS. 1 855 1024 377 84.8 -3.30 2.3
* master (synced), # master (unsynced), + selected, - candidate, ~ configured
Nexus state:
BL01R01B10SRVS01# sh ntp peer-status
Total peers : 4
* - selected for sync, + - peer mode(active),
- - peer mode(passive), = - polled in client mode
remote local st poll reach delay
=10.0.1.1 10.0.201.11 16 64 0 0.00000
=10.0.1.2 10.0.201.11 16 64 0 0.00000
=10.0.1.3 10.0.201.11 16 64 0 0.00000
=10.0.1.4 10.0.201.11 16 64 0 0.00000
Nexus config:
ntp distribute
ntp server 10.0.1.1
ntp server 10.0.1.2
ntp server 10.0.1.3
ntp server 10.0.1.4
ntp source 10.0.201.11
ntp commit
interface mgmt0
ip address 10.0.201.11/24
vrf context management
ip route 0.0.0.0/0 10.0.201.254
Reachability to the NTP source...
BL01R01B10SRVS01# ping 10.0.1.1 vrf management source 10.0.201.11
PING 10.0.1.1 (10.0.1.1) from 10.0.201.11: 56 data bytes
64 bytes from 10.0.1.1: icmp_seq=0 ttl=253 time=3.487 ms
64 bytes from 10.0.1.1: icmp_seq=1 ttl=253 time=4.02 ms
64 bytes from 10.0.1.1: icmp_seq=2 ttl=253 time=3.959 ms
64 bytes from 10.0.1.1: icmp_seq=3 ttl=253 time=4.053 ms
64 bytes from 10.0.1.1: icmp_seq=4 ttl=253 time=4.093 ms
--- 10.0.1.1 ping statistics ---
5 packets transmitted, 5 packets received, 0.00% packet loss
round-trip min/avg/max = 3.487/3.922/4.093 ms
BL01R01B10SRVS01#
Are we missing some NTP or managment vrf setup in the Nexus 5Ks??
Thanks
Rob Spain
UKI have multiple 5020's, 5548's, and 5596's, and they all experience this same problem. Mind you I run strictly layer 2. I don't even have feature interface-vlan enabled. I tried: "ntp server X.X.X.X use-vrf management" as well as "clock protocol ntpt". These didn't help.
I was told by TAC that there is a bug (sorry I do not have the ID), but basically NTP will not work over the management VRF. The only way I got NTP to work, was by enabling the feature interface-vlan, and adding a vlan interface with an IP and retrieving NTP through this interface.
I upgraded to 5.2 (1) in hopes that this would fix the issue. but it did not. -
My 9230 keeps turning of after receiving a message on facebook HELP
After receiving an email on facebook which was a link to something i opened the message and ever since i have been having problems with my phone. it keeps turning of and when i take the battery out to reboot it still turns of when the reeboot is done, it does this numerous times a day, i have security wiped my phone and the problem still consists. please help
So, the device shuts off and stays off, not a reboot, it stays off? Does it do this at regular times or is it random? When you pull the battery and put it back, and the device boots up, how long does the device operate before it shuts off again?
If it isn't an app or the device auto-off setting causing the shut down, I would look at power issues. Make sure the battery is tight in the compartment. Make sure the battery is making good contact with the contact pins on the device. If you can borrow a battery, try it and see if it makes a difference.
I think the connection with clicking that link is coincidence.
If you dropped the device or got it wet, however, all bets are off.
- Ira -
Hi,
my imac reboot after a panic. I changed the HD with apple care and they removed defected memory card but i still have the same problem.
here is the last dump
Any help wil be appreciated
Eric.
Anonymous UUID: E665EA28-80CB-0D8B-DD0C-6CF961F20D8D
Sun Apr 13 12:11:20 2014
panic(cpu 0 caller 0xffffff8004f640a5): "hfs_swap_HFSPlusBTInternalNode: catalog key #24 invalid length (1060)\n"@/SourceCache/xnu/xnu-2422.90.20/bsd/hfs/hfs_endian.c:526
Backtrace (CPU 0), Frame : Return Address
0xffffff81282d3380 : 0xffffff8004c22fa9
0xffffff81282d3400 : 0xffffff8004f640a5
0xffffff81282d3440 : 0xffffff8004f6303f
0xffffff81282d3490 : 0xffffff8004f57a31
0xffffff81282d34d0 : 0xffffff8004e06e6e
0xffffff81282d35c0 : 0xffffff8004e03b17
0xffffff81282d3660 : 0xffffff8004e064ee
0xffffff81282d36b0 : 0xffffff8004f826ff
0xffffff81282d36e0 : 0xffffff8004f8697a
0xffffff81282d3750 : 0xffffff8004f6d1a6
0xffffff81282d37e0 : 0xffffff8004dfdc90
0xffffff81282d3860 : 0xffffff8004fbdfe6
0xffffff81282d3f50 : 0xffffff800503e363
0xffffff81282d3fb0 : 0xffffff8004cf3b26
BSD process name corresponding to current thread: PluginProcess
Mac OS version:
13C64
K
Model: iMac10,1, BootROM IM101.00CC.B00, 2 processors, Intel Core 2 Duo, 3.06 GHz, 10 GB, SMC 1.52f9
Graphics: NVIDIA GeForce 9400, NVIDIA GeForce 9400, PCI, 256 MB
Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1067 MHz, 0x029E, 0x434D5341344758334D314131303636433720
Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1067 MHz, 0x029E, 0x434D5341344758334D314131303636433720
Memory Module: BANK 0/DIMM1, 2 GB, DDR3, 1067 MHz, 0x802C, 0x31364A53463235363634485A2D3147314631
AirPort: spairport_wireless_card_type_airport_extreme (0x168C, 0x8F), Atheros 9280: 4.0.74.0-P2P
Bluetooth: Version 4.2.3f10 13477, 3 services, 23 devices, 1 incoming serial ports
Network Service: AirPort, AirPort, en1
Serial ATA Device: ST3500418AS, 500,11 GB
Serial ATA Device: HL-DT-ST DVDRW GA11N
USB Device: Photosmart C4600 series
USB Device: Built-in iSight
USB Device: Internal Memory Card Reader
USB Device: My Book 1140
USB Device: IR Receiver
USB Device: BRCM2046 Hub
USB Device: Bluetooth USB Host Controller
Thunderbolt Bus:There's a 90-day warranty on the repair. The panic may have been caused by bad memory, not the hard drive.
-
My iPhone 4 can not reboot after upgrading to iOS 6; keeps trying and cannot shut off either.
My iPhone 4 can not reboot after upgrading to iOS 6; keeps trying and cannot shut off either.
I FINALLY got it to work on BOTH iPhone 4 and iPpad 3. Here is what I had to do:
Had to DELETE all e-mail accounts including icloud.
Did a hard reset (hold down button on top right corner and round button on bottom center)
Then once it came back on, the iPhone had ALL of the accounts still on it and it was receivng e-mail.
The iPad receive e-mail until I did the steps above 5 times. Plus, I had to add back all of the e-mail accounts vs. on the iPhone 4 they were there when my phone came on.
Now I am receiving e-mail on both devices normally.
No clue why this happened, but Apple needs to find a fix ASAP. -
Hi,
I have a Nexus 5000 conected with a UCS C-200 with qlogic CNA in FCoE. The ethernet traffic is ok, but FC dont work fine, i thinks that i have configured all ok, by the show int vfc show the trunk vsan in initializating mode and i dont find what is the problem
switch(config-if)# sh int vfc 1
vfc1 is trunking
Bound interface is Ethernet1/9
Port description is Conexion FC con UCS1
Hardware is Virtual Fibre Channel
Port WWN is 20:00:00:0d:ec:e8:2c:7f
Admin port mode is F, trunk mode is on
snmp link state traps are enabled
Port mode is TF
Port vsan is 1
Trunk vsans (admin allowed and active) (1)
Trunk vsans (up) ()
Trunk vsans (isolated) ()
Trunk vsans (initializing) (1)
1 minute input rate 0 bits/sec, 0 bytes/sec, 0 frames/sec
1 minute output rate 0 bits/sec, 0 bytes/sec, 0 frames/sec
0 frames input, 0 bytes
0 discards, 0 errors
0 frames output, 0 bytes
0 discards, 0 errors
last clearing of "show interface" counters never
Interface last changed at Mon Dec 20 19:59:31 2010
switch(config-if)# show port internal info interface vfc 1
vfc1 - if_index: 0x1E000000, phy_port_index: 0x1000
local_index: 0xffff
Admin Config - state(up), mode(F), speed(auto), trunk(on)
beacon(off), snmp trap(on), tem(false)
description(Conexion FC con UCS1)
port owner()
Operational Info - state(trunking), mode(TF), speed(auto), trunk(on)
state reason(None)
phy port enable (1), phy layer (FC), port_osm_mode(OSM)
participating(1), fcid(0x000000), bb_scn(0)
config port vsan (1), oper port vsan (1)
rx bb_credit(0), rx bb_credit multiplier(0)
rx bb_credit performance buffers(0), tx bb_credit(0)
not first time port bringup is 0
Port WWN is 20:00:00:0d:ec:e8:2c:7f
current state [PI_FSM_ST_TXPORT_INIT_TRUNKING_ENABLED]
port_init_eval_flag(0x00000401), cfg wait for none
FC_PORT_INIT_DATA_VALID (0)
FC_PORT_INIT_ADMIN_ST_DOWN_TO_UP (10)
FC_PORT_INIT_PHY_PORT_UP (49)
Mts node id 0x0
Lock Info: resource [vfc1]
type[0] p_gwrap[(nil)]
FREE @ 259535 usecs after Mon Dec 20 19:59:31 2010
type[1] p_gwrap[(nil)]
FREE @ 260559 usecs after Mon Dec 20 19:59:31 2010
type[2] p_gwrap[(nil)]
FREE @ 266012 usecs after Mon Dec 20 19:59:31 2010
0x10000001e000000
eport_init_flag(0x00000000), elp_chk_flag(0x00000000)
elp_rcvd_fc2_handle(0x00000000), elp_sent_fc2_handle(0x00000000)
esc_chk_flag(0x00000000), esc_fc2_handle(0x00000000)
elp_flags(0x0000), classes_supported(F), tx bb_credit(0)
Peer ELP Revision: 0
Timer active for PI_FSM_EV_TE_2_E_TIMER_EXPIRED
cnt_link_failure(0), cnt_link_success(0), cnt_port_up(0)
cnt_cfg_wait_timeout(2), cnt_port_cfg_failure(2), cnt_init_retry(0)
nos link failures (0), debounce window (300 ms), elp wait tout (750 ms)
link fail reason (0x0) num_elps_before_up (0)
internal_reinit_counter (0) external_reinit_counter (0)
Trunk Info -
trunk vsans (allowed active) (1)
trunk vsans (operational allowed) (1)
trunk vsans (up) ()
trunk vsans (isolated) ()
TE port per vsan information
vfc1, Vsan 1 - state(down), state reason(waiting for flogi), fcid(0x000000)
port init flag(0x0),
Lock Info: resource [vfc1, vsan 1]
type[0] p_gwrap[(nil)]
FREE @ 270103 usecs after Mon Dec 20 19:59:31 2010
type[1] p_gwrap[(nil)]
FREE @ 270104 usecs after Mon Dec 20 19:59:31 2010
type[2] p_gwrap[(nil)]
FREE @ 270105 usecs after Mon Dec 20 19:59:31 2010
0x40000011e000000
current state [TE_FSM_ST_WAIT_FOR_FLOGI]
RNID info not found.
first time elp: 1
Peer ELP Revision: 0
Pacer Info -
Pacer state: released credits due to timer expiry
PQP: not in progress
My configuration
vlan 701
fcoe vsan 1
name FCoE-Vsan1
interface vfc1
bind interface Ethernet1/9
switchport description Conexion FC con UCS1
no shutdown
interface Ethernet1/9
description Conexion FCoE con UCS1
switchport mode trunk
spanning-tree port type edge trunk
I need configure anything in UCS?.
Regards.Under your ethernet 1/9 try adding:
switchport trunk allowed vlan 1, 701
Assuming vlan 1 as your native default vlan and 701 is FCoE vlan, this should bring up vlan 701 to your CNA.
Maybe you are looking for
-
Itunes update can't install or uninstall old version
I have tried several methods to uninstall old itunes, as it would not recognise my new ipod, or the cd configuration folder, which I have found but do not know where to put it! I have itunes on dell pc with wondows 7 . When I try to install the new
-
if i have a powerpoint file myfile.pps and i saved in a folder of any folder name in the f:// directory, how do i execute the file? Using this following codeRuntime.getRuntime().exec(new String[] {"cmd /c start", "f:/myfile.pps"});thanks
-
MERGE CONVERT TO UPDATE LOT OF ERROR OCCUR HOW TO CHANGE
in this statement change merge to update plz help me MERGE INTO CORM_QWD_QUOTE_WUTASK A USING (SELECT * FROM CORM_QMD_QUOTEMAT) B ON ( ( A.QWD_ORDER_OU = B.QMD_ORDER_OU AND A.QWD_ORDER_NO = B.QMD_ORDER_NO AND A.QWD_AMEND_NO = B.QMD_AMEND_NO AND A.QWD
-
How can recover database using only Full Export ?
Hi, I have one query , i have only Full export is given database , after full export sucessfully database Crash by mistacally, how can recover it, i have only export is given no backup is taken (RMAN,COLD or HOT) statergy is use , How can recover it.
-
Computer crashes when receiving or initiating a voice call - Windows 7, Skype version 7.6
Whenever I either initiate a voice call or click to answer one, the system freezes and does not respond to anything short of a hard reset. I've tried the following steps without solving the problem:Reinstalling Skype (was 7.5, now 7.6)Updating video