Nexus 5000 - Odd Ethernet interface behavior (link down inactive)
Hi Guys,
This would sound really trivial but it is very odd behavior.
- We have a server connected to a 2, Nexus 5000s (for resiliancy)
- When there is no config on the ethernet interfaces whatsoever, the ethernet interface is UP / UP, there is minimal amount of traffic on the link etc. E.g.
Ethernet1/16 is up
Hardware: 1000/10000 Ethernet, address: 000d.ece7.85d7 (bia 000d.ece7.85d7)
Description: shipley-p1.its RK14/A13
MTU 1500 bytes, BW 10000000 Kbit, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA
Port mode is access
full-duplex, 10 Gb/s, media type is 1/10g
Beacon is turned off
Input flow-control is off, output flow-control is off
Rate mode is dedicated
Switchport monitor is off
Last link flapped 00:00:07
Last clearing of "show interface" counters 05:42:32
30 seconds input rate 0 bits/sec, 0 packets/sec
30 seconds output rate 96 bits/sec, 0 packets/sec
Load-Interval #2: 5 minute (300 seconds)
input rate 0 bps, 0 pps; output rate 8 bps, 0 pps
RX
0 unicast packets 0 multicast packets 0 broadcast packets
0 input packets 0 bytes
0 jumbo packets 0 storm suppression packets
0 runts 0 giants 0 CRC 0 no buffer
0 input error 0 short frame 0 overrun 0 underrun 0 ignored
0 watchdog 0 bad etype drop 0 bad proto drop 0 if down drop
0 input with dribble 0 input discard
0 Rx pause
TX
0 unicast packets 163 multicast packets 0 broadcast packets
163 output packets 15883 bytes
0 jumbo packets
0 output errors 0 collision 0 deferred 0 late collision
0 lost carrier 0 no carrier 0 babble
0 Tx pause
1 interface resets
- As soon as I configure the link to be an access port, the link goes down, flagging "inactivity" E.g.
sh int e1/16
Ethernet1/16 is down (inactive)
Hardware: 1000/10000 Ethernet, address: 000d.ece7.85d7 (bia 000d.ece7.85d7)
Description: shipley-p1.its RK14/A13
MTU 1500 bytes, BW 10000000 Kbit, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA
Port mode is access
auto-duplex, 10 Gb/s, media type is 1/10g
Beacon is turned off
Input flow-control is off, output flow-control is off
Rate mode is dedicated
Switchport monitor is off
Last link flapped 05:38:03
Last clearing of "show interface" counters 05:41:33
30 seconds input rate 0 bits/sec, 0 packets/sec
30 seconds output rate 0 bits/sec, 0 packets/sec
Load-Interval #2: 5 minute (300 seconds)
input rate 0 bps, 0 pps; output rate 0 bps, 0 pps
RX
0 unicast packets 0 multicast packets 0 broadcast packets
0 input packets 0 bytes
0 jumbo packets 0 storm suppression packets
0 runts 0 giants 0 CRC 0 no buffer
0 input error 0 short frame 0 overrun 0 underrun 0 ignored
0 watchdog 0 bad etype drop 0 bad proto drop 0 if down drop
0 input with dribble 0 input discard
0 Rx pause
TX
0 unicast packets 146 multicast packets 0 broadcast packets
146 output packets 13083 bytes
0 jumbo packets
0 output errors 0 collision 0 deferred 0 late collision
0 lost carrier 0 no carrier 0 babble
0 Tx pause
0 interface resets
- This behavior is seen on both 5Ks
- I've tried using a different set of ports, changed SFPs, and fibre cabling to no avail
- I can't seem to understand this behavior?! In that, why would configuring the port cause the link to go down?
- If anyone has experience this before, or could shed some light on this behavior, it would be appreciated.
sh ver
Cisco Nexus Operating System (NX-OS) Software
TAC support: http://www.cisco.com/tac
Copyright (c) 2002-2010, Cisco Systems, Inc. All rights reserved.
The copyrights to certain works contained herein are owned by
other third parties and are used and distributed under license.
Some parts of this software are covered under the GNU Public
License. A copy of the license is available at
http://www.gnu.org/licenses/gpl.html.
Software
BIOS: version 1.2.0
loader: version N/A
kickstart: version 4.2(1)N1(1)
system: version 4.2(1)N1(1)
power-seq: version v1.2
BIOS compile time: 06/19/08
kickstart image file is: bootflash:/n5000-uk9-kickstart.4.2.1.N1.1.bin
kickstart compile time: 4/29/2010 19:00:00 [04/30/2010 02:38:04]
system image file is: bootflash:/n5000-uk9.4.2.1.N1.1.bin
system compile time: 4/29/2010 19:00:00 [04/30/2010 03:51:47]
thanks
Sheldon
I had identical issue
Two interfaces on two different FEXes were INACTIVE. I have two Nexus 5596 in vPC and A/A FEXes.
I also use config-sync feature.
Very same configuration was applied to other ports on other FEXes and they were working with no problems.
interface Ethernet119/1/1
inherit port-profile PP-Exchange2003
I checked VLAN status associated with this profile and it was active (of course it was, other ports were ok).
I solved it by removing port profile from this port and re-applied it... voila, port changed state to up!
Very very strange.
Similar Messages
-
Odd Tunnel Interface behavior - one end requires "no keepalive"
Where's the quick version. Tunnel between sites A & B. This is GRE o IPSEC, but I don't think that's the issue. Tunnel comes up and works great when: site A has no keepalives and site B has no keepalives, and it works when Site A has keepalives turned on and Site B does not. The moment I turn on keepalives on site B, the tunnel goes down.
This isn't a simple config. Site A is an MPLS PE, meaning the Tunnel interface is configured with an fVRF and iVRF. Site B has no VRF's - it is the CE.
Any ideas on how to fix? I need Site B's Tunnel interface to go down when connectivity fails. My current workaround is to use EIGRP to update the routing tables. I need to be able to support redundant paths with static and floating routes.Like this;
Core1-r1#sh access-list ironport2
Extended IP access list ironport2
10 deny tcp host 10.247.254.174 any
20 deny tcp any 192.168.0.0 0.0.255.255
30 deny tcp any 10.0.0.0 0.255.255.255
40 deny tcp host 10.230.3.250 any
50 permit tcp 10.139.60.0 0.0.0.255 any (119568304 matches)
60 permit tcp 10.230.32.0 0.0.0.255 any (9290669 matches)
70 permit tcp host 10.230.48.12 any (141403 matches)
80 permit tcp host 10.230.36.62 any (1456 matches)
90 permit tcp host 10.150.18.7 any (741 matches)
Core1-r1#
10= P1 interface
20= network we don't want to be sent to ironport
30= " "
40= M1 interface
50->90=All testing subnets to go to ironport
Thanks for the feedback! jc -
Vfc interface down until "shut/no shut" on Ethernet interface(s)
Hello, I'm hoping someone out there has had this problem and knows the solution, or can provide some insight as to whether the problem is with the CNA, Host OS, or Nexus. I've not yet posted anything to the Brocade discussion forums about this issue.
I have vfc interfaces that are not coming up naturally; the log states that it fails "waiting for flogi" (see 'google'). The only solution that I've found posted for that problem is to apply the QoS settings for FCoE. Those settings were already applied during the initial configuration of the switch, and I've since double and triple checked them. I've also gone through the Cisco Nexus 5000 Troubleshooting Guide, Troubleshooting FCoE Issues, and everything checks out except a couple of things:
1) The interfaces don't get past the FIP Solicitation stage: They show Triggered Event: [FCOE_MGR_VFC_EV_FIP_SOLICITATION] over and over again.
2) While the troubleshooting guide states that the FCoE vLAN should be STP forwarding on the underlying Ethernet interfaces, it is not. However, I have a working configuration elsewhere (with different make/model CNA hardware and Nexus software revisions) and the FCoE vLAN is not STP forwarding on those underlying Ethernet interfaces either.
The interesting part is that if I do a "shut" then "no shut" on the underlying Ethernet interfaces, after the hosts have completely booted, the vfc interfaces come up and successfully register in the flogi database. At that point everything is functional. If the hosts then reboot, the vfc interfaces fail to come up until I perform the "shut/no shut" on the underlying Ethernet interfaces.
One other noteworthy symptom is that during POST, when the CNA initializes, it displays the error message "Link initialization failed. Disabling BIOS."
Here is a configuration synopsis:
Cisco Nexus 5548UP [Ver. 5.1(3)N2(1)]
Brocade 1020 CNA [Rev. 3.2.1.0]
ESXi vSphere [Ver 5.1], [CNA Driver Rev. 3.2.1.0]
There are two vSANs; A-side and B-side. Each is bound to a unique and dedicated vLAN.
Po1 is the vPC peer-link. The FCoE vLANs are *not* allowed on it.
Po1011 is DB1's vPC port-channel. It is an 802.1q Trunk; the native vLAN (1) and the FCoE vLANs are allowed, among other Ethernet data vLANs.
Po1021 is DB1's vPC port-channel. It is an 802.1q Trunk; the native vLAN (1) and the FCoE vLANs are allowed, among other Ethernet data vLANs.
vfc1011 is DB1's Virtual FC interface. It is a Trunk (mode TF), allowing the A-side vSAN only. It is in the vSAN membership database.
vfc1021 is DB2's Virtual FC interface. It is a Trunk (mode TF), allowing the B-side vSAN only. It is in the vSAN membership database.
EDIT: The Port-Channels are LACP.
Thanks for your time.
Message was edited by: Michael HertrickI agree that the more distance you can put between the fabrics ever converging into one, the better off you are. You don't want faults on one SAN to interrupt and cause faults on your redundant SAN.
Nevertheless, the aforementioned configuration does not converge the two vSANs.
The host does not bridge between the two adapters, nor do the switches bridge between the two. Remember, even though you bind the vfc to the port-channel in the configuration, the vfc is really bound only to the Ethernet interface on the local switch and is not participating in the port-channel at all. There is no way, with that configuration as-is, for SAN A traffic to land on SAN B. A series of a few mis-configurations would be required for the SAN segmentation to be eroded.
http://www.cisco.com/en/US/prod/collateral/switches/ps9441/ps9670/configuration_guide_c07-543563.html
See sections "Configuration Parameters That Must Be Identical" and "Configuration Parameters That Should Be Identical"
Under "must" there is:
Enable or disable state per VLAN"
Under "should" there is:
Spanning Tree Protocol interface settings:
VLANs (Rapid Per-VLAN Spanning Tree Plus [PVST+])
Would you mind pointing out in the document you linked where Cisco recommends that the allowed vLANs on each side of the vPC should be different? I didn't exactly find that. What I did see was that they have vlan 101 and 102 allowed on both port-channel11 and port-channel12 in their example. vsan 101 is bound to vlan 101, vsan 102 is bound to vlan 102.
Kind Regards. -
Leave plugged in Ethernet interface disabled (down) [solved]
Is it possible to keep a plugged in Ethernet interface down by default at boot? I have a USB Ethernet adapter I'd like to keep down until needed. Despite not having an IP, it is automatically activated and up at boot up (it is a spanned port).
The ipv6 stack is in the kernel but not used for interfaces, udev renames the device, and nothing is configured for it in NetworkManager (although have tried to manage it this way to avail). dhcp shouldn't be a problem, unless I'm missing something that is pre-configured by default?
The only solution I can think of is to blacklist the module, which would allow me to probe it when needed to bring it up (there is also the physical side of doing this as well). The only drawback is these aren't the most efficient ways to manage an interface.
Any suggestions are appreciated.
Last edited by jskier (2014-03-27 19:49:44)Standard NICs are kept down unless configured (eg. with netctl, etc). My net2 is plugged into a switch:
$ ip a s
3: net2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 00:00:5a:73:94:a2 brd ff:ff:ff:ff:ff:ff -
Ethernet interface down when make entry in autopush file
Hi,
my kernel STREAMS module is working fine when i push it just above ethernet interface through ifconfig cmd, but when i make its entry in autopush file as: iprbo -1 0 simod
then during boot ethernet interface iprb0 is not getting up & even system is getting crashed?
how i can sort out this prob ?Hi Prakash
Chech if the host name entry in maintained on DNS server. DNS server is responsible to resolve your host-name to IP setting.
refer this link - http://forums.techarena.in/server-dns/905529.htm
Regards
Mitesh Parekh -
Ethernet/networking link down // AppleYukon2 - en0 link down
*Massive writing into a Volume located on a NAS // Ethernet/networking link down // AppleYukon2 - en0 link down*
Scenario
Writing a massive data into a volume (sparsebundle) on a NAS (network attached store).
*Problem / Error*
Always during this process the Ethernet link down.
Then the MAC OS X (10.5.6) freeze – no reset, no shutdown and no volume eject – after trying some clicks the spinning wheel comes and only soft reset or hard reset shutdown.
*Technical Info*
Wireless Device: Linksys - WRT54G firmware updated
NAS/External Hard Drive: Iomega - Home Network HD firmware updated
MacBook Pro // Mac OS X (10.5.6) // 2.2 GHz Intel Core 2 Duo // 2 GB
Logs
+LOG 1+
Apr 8 18:56:30 wslyMac /System/Library/CoreServices/backupd[207]: Backup requested by user
Apr 8 18:56:30 wslyMac /System/Library/CoreServices/backupd[207]: Starting standard backup
Apr 8 18:56:36 wslyMac /System/Library/CoreServices/backupd[207]: Mounted network destination using URL: smb://admin@STORAGE-7AB4/TimeMachine
Apr 8 18:56:36 wslyMac /System/Library/CoreServices/backupd[207]: Backup destination mounted at path: /Volumes/TimeMachine-1
Apr 8 18:56:58 wslyMac kernel[0]: AppleYukon2: 00000000,00000001 sk98osx sky2 - - sk98osx_sky2::replaceOrCopyPacket tried N times
Apr 8 18:57:07 wslyMac hdiejectd[231]: running
Apr 8 18:57:08 wslyMac kernel[0]: jnl: disk1s2: replay_journal: from: 8088064 to: 15072256 (joffset 0x7d0000)
Apr 8 18:57:25 wslyMac kernel[0]: jnl: disk1s2: journal replay done.
Apr 8 18:57:25 wslyMac fseventsd[37]: event logs in /Volumes/TimeMachine_Backup/.fseventsd out of sync with volume. destroying old logs. (1989 18 2969)
Apr 8 18:57:25 wslyMac /System/Library/CoreServices/backupd[207]: Disk image /Volumes/TimeMachine-1/wslyMac_001b63b30d6b.sparsebundle mounted at: /Volumes/TimeMachine_Backup
Apr 8 18:57:25 wslyMac /System/Library/CoreServices/backupd[207]: Backing up to: /Volumes/TimeMachine_Backup/Backups.backupdb
Apr 8 18:57:29 wslyMac fseventsd[37]: log dir: /Volumes/TimeMachine_Backup/.fseventsd getting new uuid: CBE196F1-1008-4BFB-8D4A-AD9504E68ACF
Apr 8 18:57:59 wslyMac /System/Library/CoreServices/backupd[207]: Event store UUIDs don't match for volume: Macintosh HD
Apr 8 18:58:00 wslyMac /System/Library/CoreServices/backupd[207]: No pre-backup thinning needed: 29.79 GB requested (including padding), 245.17 GB available
Apr 8 19:20:31 wslyMac kernel[0]: AppleYukon2: 00000000,00000017 sk98osx sky2 - - sk98osx_sky2::replaceOrCopyPacket tried N times
Apr 8 19:21:35 wslyMac kernel[0]: AppleYukon2: 00000000,0000001b sk98osx sky2 - - sk98osx_sky2::replaceOrCopyPacket tried N times
Apr 8 19:21:53 wslyMac kernel[0]: AppleYukon2: 00000000,0000001e sk98osx sky2 - - sk98osx_sky2::replaceOrCopyPacket tried N times
Apr 8 19:23:32 wslyMac kernel[0]: AppleYukon2: 00000000,00000004 sk98osx sky2 - - sk98osx_sky2::replaceOrCopyPacket tried N times
Apr 8 19:23:37 wslyMac kernel[0]: AppleYukon2: 00000000,00000001 sk98osx sky2 - - sk98osx_sky2::replaceOrCopyPacket tried N times
Apr 8 19:23:41 wslyMac kernel[0]: AppleYukon2: 00000000,00000011 sk98osx sky2 - - sk98osx_sky2::replaceOrCopyPacket tried N times
Apr 8 19:25:32 wslyMac kernel[0]: smbiodsendall: Timed out waiting on the response for 0x32
Apr 8 19:25:38 wslyMac kernel[0]: AppleYukon2: 00000000,000003e8 sk98osx sky2 - - sk98osx_sky2::replaceOrCopyPacket timedout
Apr 8 19:32:07 localhost kernel[0]: npvhash=4095
+LOG 2+
Apr 8 22:03:19 wslyMac /System/Library/CoreServices/backupd[356]: Backup requested by user
Apr 8 22:03:19 wslyMac /System/Library/CoreServices/backupd[356]: Starting standard backup
Apr 8 22:03:19 wslyMac /System/Library/CoreServices/backupd[356]: Mounted network destination using URL: smb://admin@STORAGE-7AB4/TimeMachine
Apr 8 22:03:19 wslyMac /System/Library/CoreServices/backupd[356]: Backup destination mounted at path: /Volumes/TimeMachine-1
Apr 8 22:03:26 wslyMac /System/Library/CoreServices/backupd[356]: Disk image /Volumes/TimeMachine-1/wslyMac_001b63b30d6b.sparsebundle mounted at: /Volumes/TimeMachine_Backup
Apr 8 22:03:26 wslyMac /System/Library/CoreServices/backupd[356]: Backing up to: /Volumes/TimeMachine_Backup/Backups.backupdb
Apr 8 22:03:26 wslyMac /System/Library/CoreServices/backupd[356]: Ownership is disabled on the backup destination volume. Enabling.
Apr 8 22:03:26 wslyMac KernelEventAgent[35]: tid 00000000 received unknown event (256)
Apr 8 22:03:27 wslyMac /System/Library/CoreServices/backupd[356]: Event store UUIDs don't match for volume: Macintosh HD
Apr 8 22:08:22 wslyMac /System/Library/CoreServices/backupd[356]: Backup content size: 66.6 GB excluded items size: 44.6 GB for volume Macintosh HD
Apr 8 22:08:22 wslyMac /System/Library/CoreServices/backupd[356]: No pre-backup thinning needed: 26.46 GB requested (including padding), 249.57 GB available
Apr 8 22:08:22 wslyMac /System/Library/CoreServices/backupd[356]: Waiting for index to be ready (909 > 0)
Apr 8 22:40:50 wslyMac kernel[0]: AppleYukon2: 00000000,0000009c sk98osx sky2 - - sk98osx_sky2::replaceOrCopyPacket tried N times
Apr 8 22:40:50 wslyMac kernel[0]: AppleYukon2: 00000000,00000008 sk98osx sky2 - - sk98osx_sky2::replaceOrCopyPacket tried N times
Apr 8 22:40:50 wslyMac kernel[0]: AppleYukon2: 00000000,00000004 sk98osx sky2 - - sk98osx_sky2::replaceOrCopyPacket tried N times
Apr 8 22:41:20 wslyMac kernel[0]: smbiodreconnect: Reconnected to STORAGE-7AB4
Apr 8 22:41:49: --- last message repeated 1 time ---
Apr 8 22:41:49 wslyMac kernel[0]: disk1s2: 0x48 (UNDEFINED).
Apr 8 22:41:50 wslyMac kernel[0]:
Apr 8 22:41:50: --- last message repeated 1 time ---
Apr 8 22:41:50 wslyMac kernel[0]: jnl: disk1s2: dojnlio: strategy err 0x5
Apr 8 22:41:50 wslyMac kernel[0]: jnl: disk1s2: end_transaction: only wrote 0 of 463360 bytes to the journal!
Apr 8 22:41:50 wslyMac kernel[0]: smbiodreconnect: Reconnected to STORAGE-7AB4
Apr 8 22:41:50 wslyMac fseventsd[39]: disk logger: failed to open output file /Volumes/TimeMachine_Backup/.fseventsd/00000000005a57d8 (Invalid argument). mount point /Volumes/TimeMachine_Backup/.fseventsd
Apr 8 22:41:50 wslyMac kernel[0]: smbfssmb_reopenfile: Reopen 1a with open deny modes failed because the modify time has changed was 1239244850s 0ns now 1239244910s 0ns!
Apr 8 22:41:50 wslyMac kernel[0]: smbfssmb_reopenfile: Warning: pid 360(diskimages-helpe) reopening of 1a failed with error 5
Apr 8 22:41:50 wslyMac mds[33]: (/Volumes/TimeMachine_Backup/.Spotlight-V100/Store-V1/Stores/DE7D5030-E962-480A -AE37-350EFD1764B1)(Error) IndexCI in ci_ftruncate:ftruncate(53 /Volumes/TimeMachine_Backup/.Spotlight-V100/Store-V1/Stores/DE7D5030-E962-480A- AE37-350EFD1764B1/live.0.indexPostings, 131072) error:22
Apr 8 22:41:50 wslyMac mds[33]: (/Volumes/TimeMachine_Backup/.Spotlight-V100/Store-V1/Stores/DE7D5030-E962-480A -AE37-350EFD1764B1)(Error) IndexCI in initPayload:ftruncate err: 22
Apr 8 22:41:50 wslyMac mds[33]: (/Volumes/TimeMachine_Backup/.Spotlight-V100/Store-V1/Stores/DE7D5030-E962-480A -AE37-350EFD1764B1)(Error) IndexGeneral in notify_lowspace:low space for device 234881029 (/Volumes/TimeMachine_Backup/.Spotlight-V100/Store-V1/Stores/DE7D5030-E962-480A -AE37-350EFD1764B1)
Apr 8 22:41:50 wslyMac mds[33]: (Error) Volume: LOW DISK SPACE device:234881029
Apr 8 22:41:50 wslyMac mds[33]: (/Volumes/TimeMachine_Backup/.Spotlight-V100/Store-V1/Stores/DE7D5030-E962-480A -AE37-350EFD1764B1)(Error) IndexCI in ci_ftruncate:ftruncate(54 /Volumes/TimeMachine_Backup/.Spotlight-V100/Store-V1/Stores/DE7D5030-E962-480A- AE37-350EFD1764B1/live.0.indexPostings, 131072) error:22
Apr 8 22:41:50 wslyMac mds[33]: (/Volumes/TimeMachine_Backup/.Spotlight-V100/Store-V1/Stores/DE7D5030-E962-480A -AE37-350EFD1764B1)(Error) IndexCI in initPayload:ftruncate err: 22
Apr 8 22:41:50 wslyMac mds[33]: (/Volumes/TimeMachine_Backup/.Spotlight-V100/Store-V1/Stores/B8028080-DC7D-4A98 -813F-46DA8DCFF8AF)(Error) IndexCI in ci_ftruncate:ftruncate(48 /Volumes/TimeMachine_Backup/.Spotlight-V100/Store-V1/Stores/B8028080-DC7D-4A98- 813F-46DA8DCFF8AF/live.0.indexPostings, 4096) error:22
Apr 8 22:41:50 wslyMac mds[33]: (/Volumes/TimeMachine_Backup/.Spotlight-V100/Store-V1/Stores/B8028080-DC7D-4A98 -813F-46DA8DCFF8AF)(Error) IndexCI in initPayload:ftruncate err: 22
Apr 8 22:41:50 wslyMac mds[33]: (/Volumes/TimeMachine_Backup/.Spotlight-V100/Store-V1/Stores/DE7D5030-E962-480A -AE37-350EFD1764B1)(Error) IndexCI in copyFileOrFd:error (22) opening 0.indexGroups
Apr 8 22:41:50 wslyMac mds[33]: (/Volumes/TimeMachine_Backup/.Spotlight-V100/Store-V1/Stores/DE7D5030-E962-480A -AE37-350EFD1764B1)(Error) IndexCI in recoverIndex:Unrecoverable error: could not recover groups file (0.)
Apr 8 22:41:50 wslyMac mds[33]: (/Volumes/TimeMachine_Backup/.Spotlight-V100/Store-V1/Stores/DE7D5030-E962-480A -AE37-350EFD1764B1)(Error) IndexCI in CIMetaInfoCreate:Tried to create index when index already existed /Volumes/TimeMachine_Backup/.Spotlight-V100/Store-V1/Stores/DE7D5030-E962-480A- AE37-350EFD1764B1
Apr 8 22:41:50 wslyMac /System/Library/CoreServices/backupd[356]: Error: (-50) SrcErr:NO Copying /Applications/Utilities/System Profiler.app/Contents/version.plist to /Volumes/TimeMachine_Backup/Backups.backupdb/wslyMac/2009-04-08-220327.inProgre ss/0788B97B-3F1C-4331-90E0-7FAE0EDDC3D1/Macintosh HD/Applications/Utilities/System Profiler.app/Contents
Apr 8 22:41:50 wslyMac /System/Library/CoreServices/backupd[356]: Error: (-50) SrcErr:NO Copying /Applications/Utilities/System Profiler.app/Contents to /Volumes/TimeMachine_Backup/Backups.backupdb/wslyMac/2009-04-08-220327.inProgre ss/0788B97B-3F1C-4331-90E0-7FAE0EDDC3D1/Macintosh HD/Applications/Utilities/System Profiler.app
Apr 8 22:41:50 wslyMac /System/Library/CoreServices/backupd[356]: Indexing a file failed. Returned -1132 for: /Applications/Utilities/System Profiler.app, /Volumes/TimeMachine_Backup/Backups.backupdb/wslyMac/2009-04-08-220327.inProgre ss/0788B97B-3F1C-4331-90E0-7FAE0EDDC3D1/Macintosh HD/Applications/Utilities/System Profiler.app
Apr 8 22:41:50 wslyMac /System/Library/CoreServices/backupd[356]: Aborting backup because indexing of file failed.
Apr 8 22:41:50 wslyMac /System/Library/CoreServices/backupd[356]: Stopping backup.
Apr 8 22:41:50 wslyMac /System/Library/CoreServices/backupd[356]: Error: (-50) SrcErr:NO Copying /Applications/Utilities/System Profiler.app to /Volumes/TimeMachine_Backup/Backups.backupdb/wslyMac/2009-04-08-220327.inProgre ss/0788B97B-3F1C-4331-90E0-7FAE0EDDC3D1/Macintosh HD/Applications/Utilities
Apr 8 22:41:50 wslyMac /System/Library/CoreServices/backupd[356]: Copied 1738 files (4.0 GB) from volume Macintosh HD.
Apr 8 22:41:55 wslyMac /System/Library/CoreServices/backupd[356]: Backup canceled.
Apr 8 22:41:56 wslyMac /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder[117]: StatusMonitor::volumesChangedCallBack returned -47
Apr 8 22:42:06: --- last message repeated 1 time ---
Apr 8 22:42:06 wslyMac /System/Library/CoreServices/backupd[356]: Failed to eject volume /Volumes/TimeMachine_Backup (FSVolumeRefNum: -113; status: -47; dissenting pid: 0)
Apr 8 22:42:06 wslyMac /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder[117]: StatusMonitor::volumesChangedCallBack returned -47
Apr 8 22:42:56 wslyMac mds[33]: (/Volumes/TimeMachine_Backup/.Spotlight-V100/Store-V1/Stores/B8028080-DC7D-4A98 -813F-46DA8DCFF8AF)(Error) IndexCI in ci_ftruncate:ftruncate(43 /Volumes/TimeMachine_Backup/.Spotlight-V100/Store-V1/Stores/B8028080-DC7D-4A98- 813F-46DA8DCFF8AF/live.0.indexIds, 32768) error:22
Apr 8 22:42:56 wslyMac mds[33]: (/Volumes/TimeMachine_Backup/.Spotlight-V100/Store-V1/Stores/B8028080-DC7D-4A98 -813F-46DA8DCFF8AF)(Error) IndexCI in openindexfile:ftruncate error: 22, size: 32768, live.0.indexIds
Apr 8 22:42:56 wslyMac mds[33]: (/Volumes/TimeMachine_Backup/.Spotlight-V100/Store-V1/Stores/B8028080-DC7D-4A98 -813F-46DA8DCFF8AF)(Error) IndexCI in ContentIndexOpenBulk:Could not open /Volumes/TimeMachine_Backup/.Spotlight-V100/Store-V1/Stores/B8028080-DC7D-4A98- 813F-46DA8DCFF8AF/live.0.; needs recovery
Apr 8 22:42:56 wslyMac mds[33]: (/Volumes/TimeMachine_Backup/.Spotlight-V100/Store-V1/Stores/B8028080-DC7D-4A98 -813F-46DA8DCFF8AF)(Error) IndexCI in copyFileOrFd:error (22) opening 0.indexGroups
Apr 8 22:42:56 wslyMac mds[33]: (/Volumes/TimeMachine_Backup/.Spotlight-V100/Store-V1/Stores/B8028080-DC7D-4A98 -813F-46DA8DCFF8AF)(Error) IndexCI in recoverIndex:Unrecoverable error: could not recover groups file (0.)
Apr 8 22:42:56 wslyMac mds[33]: (/Volumes/TimeMachine_Backup/.Spotlight-V100/Store-V1/Stores/B8028080-DC7D-4A98 -813F-46DA8DCFF8AF)(Error) IndexCI in CIMetaInfoCreate:Tried to create index when index already existed /Volumes/TimeMachine_Backup/.Spotlight-V100/Store-V1/Stores/B8028080-DC7D-4A98- 813F-46DA8DCFF8AF
Apr 8 22:42:56 wslyMac mds[33]: (/Volumes/TimeMachine_Backup/.Spotlight-V100/Store-V1/Stores/DE7D5030-E962-480A -AE37-350EFD1764B1)(Error) IndexCI in copyFileOrFd:error (22) opening 0.indexGroups
Apr 8 22:42:56 wslyMac mds[33]: (/Volumes/TimeMachine_Backup/.Spotlight-V100/Store-V1/Stores/DE7D5030-E962-480A -AE37-350EFD1764B1)(Error) IndexCI in recoverIndex:Unrecoverable error: could not recover groups file (0.)
Apr 8 22:42:56 wslyMac mds[33]: (/Volumes/TimeMachine_Backup/.Spotlight-V100/Store-V1/Stores/DE7D5030-E962-480A -AE37-350EFD1764B1)(Error) IndexCI in CIMetaInfoCreate:Tried to create index when index already existed /Volumes/TimeMachine_Backup/.Spotlight-V100/Store-V1/Stores/DE7D5030-E962-480A- AE37-350EFD1764B1
Apr 8 22:50:21 localhost kernel[0]: npvhash=4095
Apr 8 22:50:17 localhost com.apple.launchctl.System[2]: fsck_hfs: Volume is journaled. No checking performed.
Apr 8 22:50:17 localhost com.apple.launchctl.System[2]: fsck_hfs: Use the -f option to force checking.
Apr 8 22:50:21 localhost com.apple.launchctl.System[2]: launchctl: Please convert the following to launchd: /etc/mach_init.d/dashboardadvisoryd.plist
Apr 8 22:50:21 localhost com.apple.launchd[1] (com.apple.blued): Unknown key for boolean: EnableTransactions
Apr 8 22:50:21 localhost com.apple.launchd[1] (org.cups.cupsd): Unknown key: SHAuthorizationRight
Apr 8 22:50:21 localhost com.apple.launchd[1] (org.ntp.ntpd): Unknown key: SHAuthorizationRight
Apr 8 22:50:21 localhost DirectoryService[11]: Launched version 5.6 (v514.24)
Apr 8 22:50:27 localhost kernel[0]: hi mem tramps at 0xffe00000
Apr 8 22:50:22 localhost DirectoryService[11]: Improper shutdown detected
Apr 8 22:50:27 localhost kernel[0]: PAE enabled
Apr 8 22:50:27 localhost kernel[0]: 64 bit mode enabled
Apr 8 22:50:27 localhost kernel[0]: Darwin Kernel Version 9.6.0: Mon Nov 24 17:37:00 PST 2008; root:xnu-1228.9.59~1/RELEASE_I386
Apr 8 22:50:27 localhost kernel[0]: standard timeslicing quantum is 10000 us
Apr 8 22:50:27 localhost kernel[0]: vmpagebootstrap: 511374 free pages and 12914 wired pages
Apr 8 22:50:27 localhost kernel[0]: migtable_maxdispl = 79
Apr 8 22:50:22 localhost kextd[10]: 417 cached, 0 uncached personalities to catalog
Apr 8 22:50:27 localhost kernel[0]: 101 prelinked modules
Apr 8 22:50:27 localhost kernel[0]: AppleACPICPU: ProcessorApicId=0 LocalApicId=0 Enabled
Apr 8 22:50:27 localhost kernel[0]: AppleACPICPU: ProcessorApicId=1 LocalApicId=1 Enabled
Apr 8 22:50:27 localhost kernel[0]: Loading security extension com.apple.security.TMSafetyNet
Apr 8 22:50:27 localhost kernel[0]: calling mpopolicyinit for TMSafetyNet
Apr 8 22:50:27 localhost kernel[0]: Security policy loaded: Safety net for Time Machine (TMSafetyNet)
Apr 8 22:50:27 localhost kernel[0]: Loading security extension com.apple.nke.applicationfirewall
Apr 8 22:50:27 localhost kernel[0]: Loading security extension com.apple.security.seatbelt
Apr 8 22:50:27 localhost kernel[0]: calling mpopolicyinit for mb
Apr 8 22:50:27 localhost kernel[0]: Seatbelt MACF policy initialized
Apr 8 22:50:27 localhost kernel[0]: Security policy loaded: Seatbelt Policy (mb)
Apr 8 22:50:27 localhost kernel[0]: Copyright (c) 1982, 1986, 1989, 1991, 1993
Apr 8 22:50:27 localhost kernel[0]: The Regents of the University of California. All rights reserved.
Apr 8 22:50:27 localhost kernel[0]: MAC Framework successfully initialized
Apr 8 22:50:27 localhost kernel[0]: using 10485 buffer headers and 4096 cluster IO buffer headers
Apr 8 22:50:27 localhost kernel[0]: IOAPIC: Version 0x20 Vectors 64:87
Apr 8 22:50:27 localhost kernel[0]: ACPI: System State [S0 S3 S4 S5] (S3)
Apr 8 22:50:27 localhost kernel[0]: mbinit: done
Apr 8 22:50:27 localhost kernel[0]: Security auditing service present
Apr 8 22:50:27 localhost kernel[0]: BSM auditing present
Apr 8 22:50:27 localhost kernel[0]: rooting via boot-uuid from /chosen: 402D8D77-0836-3192-8A63-554D726141DC
Apr 8 22:50:27 localhost kernel[0]: Waiting on <dict ID="0"><key>IOProviderClass</key><string ID="1">IOResources</string><key>IOResourceMatch</key><string ID="2">boot-uuid-media</string></dict>
Apr 8 22:50:27 localhost kernel[0]: FireWire (OHCI) TI ID 8025 built-in now active, GUID 001e52fffe3817fa; max speed s800.
Apr 8 22:50:27 localhost kernel[0]: Got boot device = IOService:/AppleACPIPlatformExpert/PCI0/AppleACPIPCI/SATA@1F,2/AppleICH8AHCI/PR T0@0/IOAHCIDevice@0/AppleAHCIDiskDriver/IOAHCIBlockStorageDevice/IOBlockStorageD river/FUJITSU MHY2120BH Media/IOGUIDPartitionScheme/Customer@2
Apr 8 22:50:27 localhost kernel[0]: BSD root: disk0s2, major 14, minor 2
Apr 8 22:50:27 localhost kernel[0]: jnl: unknown-dev: replay_journal: from: 15129600 to: 2979328 (joffset 0x7d01000)
Apr 8 22:50:27 localhost kernel[0]: [Bluetooth::CSRHIDTransition] switchToHCIMode (legacy)
Apr 8 22:50:27 localhost kernel[0]: [Bluetooth::CSRHIDTransition] transition complete.
Apr 8 22:50:27 localhost kernel[0]: [HCIController][configurePM] power parent ready after 1 tries
Apr 8 22:50:27 localhost kernel[0]: AppleIntelCPUPowerManagement: initialization complete
Apr 8 22:50:27 localhost kernel[0]: jnl: unknown-dev: journal replay done.
Apr 8 22:50:27 localhost kernel[0]: HFS: Removed 4 orphaned unlinked files or directories
Apr 8 22:50:27 localhost kernel[0]: Jettisoning kernel linker.
Apr 8 22:50:27 localhost kernel[0]: Resetting IOCatalogue.
Apr 8 22:50:27 localhost kernel[0]: GFX0: family specific matching fails
Apr 8 22:50:27 localhost kernel[0]: Matching service count = 1
Apr 8 22:50:27 localhost kernel[0]: Matching service count = 2
Apr 8 22:50:27: --- last message repeated 4 times ---
Apr 8 22:50:27 localhost kernel[0]: Previous Shutdown Cause: 5
Apr 8 22:50:27 localhost kernel[0]: NVDANV50HAL loaded and registered.
Apr 8 22:50:27 localhost kernel[0]: GFX0: family specific matching fails
Apr 8 22:50:27 localhost kernel[0]: ath_attach: devid 0x24
Apr 8 22:50:27 localhost kernel[0]: Override HT40 CTL Powers. EEPROM Version is 14.4, Device Type 5
Apr 8 22:50:27 localhost kernel[0]: mac 12.10 phy 8.1 radio 12.0
Apr 8 22:50:27 localhost kernel[0]: GFX0: family specific matching fails
Apr 8 22:50:27: --- last message repeated 1 time ---
Apr 8 22:50:27 localhost kernel[0]: Matching service count = 0
Apr 8 22:50:27 localhost kernel[0]: yukon: Ethernet address 00:1b:63:b3:0d:6b
Apr 8 22:50:27 localhost kernel[0]: AirPort_Athr5424ab: Ethernet address 00:1e:52:71:2c:52
Apr 8 22:50:30 localhost mDNSResponder mDNSResponder-176.3 (Sep 30 2008 16:59:38)[16]: starting
Apr 8 22:50:30 localhost fseventsd[38]: event logs in /.fseventsd out of sync with volume. destroying old logs. (3603 22 3778)
Apr 8 22:50:30 localhost rpc.statd[30]: statd.notify - no notifications needed
Apr 8 22:50:31 localhost kernel[0]: AirPort: Link Down on en1
Apr 8 22:50:30 localhost /System/Library/CoreServices/loginwindow.app/Contents/MacOS/loginwindow[33]: Login Window Application Started -- Threaded auth
Apr 8 22:50:30 localhost fseventsd[38]: log dir: /.fseventsd getting new uuid: B621E1D8-11D5-49D5-90F5-6E32BEDC8615
Apr 8 22:50:30 localhost bootlog[45]: BOOT_TIME: 1239241808 0
Apr 8 22:50:30 localhost blued[46]: Apple Bluetooth daemon started.
Apr 8 22:50:31 wslyMac configd[14]: setting hostname to "wslyMac.local"
Apr 8 22:50:33 wslyMac kernel[0]: AppleYukon2 - en0 link active, 100-Mbit, full duplex, symmetric flow control enabled port 0
Apr 8 22:50:35 wslyMac org.ntp.ntpd[26]: Error : nodename nor servname provided, or not known
Apr 8 22:50:35 wslyMac ntpdate[60]: can't find host time.apple.com
Apr 8 22:50:35 wslyMac ntpdate[60]: no servers can be used, exiting
Apr 8 22:50:39 wslyMac kernel[0]: IOHIDSystem: Seize of IOHIDPointing failed.
Apr 8 22:50:39 wslyMac kernel[0]: IOHIDSystem: Seize of IOHIDEventDriver failed.
Apr 8 22:50:39 wslyMac kextd[10]: writing kernel link data to /var/run/mach.sym
Apr 8 22:50:43 wslyMac /usr/sbin/ocspd[75]: starting
Apr 8 22:50:43 wslyMac com.apple.SystemStarter[28]: Starting HP IO Monitor
Apr 8 22:50:43 wslyMac com.apple.SystemStarter[28]: Starting HP Trap Monitor
Apr 8 22:50:43 wslyMac com.apple.SystemStarter[28]: /Library/StartupItems/HP Trap Monitor/HP Trap Monitor: line 15: /Library/Printers/hp/hpio/HPIO Trap Monitor.app/Contents/MacOS/HPIO Trap Monitor: No such file or directory
Apr 8 22:50:46 wslyMac loginwindow[33]: Login Window Started Security Agent
Apr 8 22:52:36 wslyMac authorizationhost[95]: MechanismInvoke 0x125de0 retainCount 2
Apr 8 22:52:36 wslyMac SecurityAgent[96]: MechanismInvoke 0x101660 retainCount 1
Apr 8 22:52:37 wslyMac SecurityAgent[96]: NSSecureTextFieldCell detected a field editor ((null)) that is not a NSTextView subclass designed to work with the cell. Ignoring...
Apr 8 22:52:37 wslyMac loginwindow[33]: Login Window - Returned from Security Agent
Apr 8 22:52:37 wslyMac SecurityAgent[96]: MechanismDestroy 0x101660 retainCount 1
Apr 8 22:52:37 wslyMac authorizationhost[95]: MechanismDestroy 0x125de0 retainCount 2
Apr 8 22:52:37 wslyMac loginwindow[33]: USER_PROCESS: 33 console
Apr 8 22:52:37 wslyMac com.apple.launchd[1] (com.apple.UserEventAgent-LoginWindow[91]): Exited: Terminated
Apr 8 22:52:37 wslyMac com.apple.launchd[108] (com.apple.AirPortBaseStationAgent): Unknown key for boolean: EnableTransactions
Apr 8 22:52:42 wslyMac Dock[118]: _DESCRegisterDockExtraClient failed 268435459
Apr 8 22:52:44 wslyMac /System/Library/CoreServices/coreservicesd[56]: SFLSharePointsEntry::CreateDSRecord: dsCreateRecordAndOpen(wsly Hiroyuki Mompean Ueda's Public Folder) returned -14135
Apr 8 22:53:02 wslyMac /System/Library/CoreServices/SystemUIServer.app/Contents/MacOS/SystemUIServer[1 24]: CPSGetProcessInfo(): This call is deprecated and should not be called anymore.
Apr 8 22:53:02 wslyMac /System/Library/CoreServices/SystemUIServer.app/Contents/MacOS/SystemUIServer[1 24]: CPSPBGetProcessInfo(): This call is deprecated and should not be called anymore.
Apr 8 22:54:42 wslyMac kernel[0]: AppleYukon2 - en0 link down
Apr 8 22:54:46 wslyMac kernel[0]: AppleYukon2 - en0 link active, 100-Mbit, full duplex, symmetric flow control enabled port 0
Apr 8 22:54:52 wslyMac kernel[0]: AppleYukon2 - en0 link down
Apr 8 22:54:53 wslyMac kernel[0]: AppleYukon2 - en0 link active, 100-Mbit, full duplex, symmetric flow control enabled port 0I've had this problem with this computer as soon as I remember starting to use it.
You should have taken it back to apple immediately.
You need to try a clean install of the OS.. yosemite has known bugs especially with the wireless and if you upgrade installed the OS it can just get worse.
You should do a clone of the hard disk and a Time Machine backup etc.. to make sure you don't lose files.. but a clean install will at least show if it is driver issue or actual faulty hardware. Is the laptop still in warranty / Applecare.. if so return it to apple for checking. -
The meaning of Interface Ethernet250/1 under the Nexus 2000 is connected to Nexus 5000 switch
Dear all,
Recently, I prepared and deploy a network monitoring system to monitor the new generation Nexus connected network. With using snmpwalk to query the interfacs information from the Nexus 5000 switch (one Nexus 2000 is connected to it via FlexLink), I found that other than normal Nexus 5000 and 2000 ports(ifName to be Ethernet1/1, Ethernet1/2, ... Ethernet190/1/1, Ethernet190/1/2...), a series of interface with ifName Ethernet250/1, Ethernet250/2, .... to be appeared in the interface SNMP tree. With logged into the Nexus 5000 and issue display interface command, I can only found the information on the normal interfaces but not the abnormal interface Ethernet250/1, ...
Would someone know what is it (do E250/1 is a logical interface like port channel or VLAN) and how to monitor it ? Thanks in advances.
HC WongI've not seen that myself. Could it perhaps be a VPC (Virtual Portchannel)?
-
Config ethernet interface on Nexus 7010
Hi all,
Please help to config the ethernet interface port 1 on slot 7. The old 6500 command "interface 7/1" does not work, got message "invalid range". Thank you.
Also I have the 1/10 Gbps Ethernet module (N7K-F248XP-25E), please educate me how to choose between 1 or 10 Gbps for the end devices ? Thanks.Wouldnt it be interface ethernet7/1 ?
interface Ethernet3/5 is a interface configured on my switch. It is a 7009 -
VPC on Nexus 5000 with Catalyst 6500 (no VSS)
Hi, I'm pretty new on the Nexus and UCS world so I have some many questions I hope you can help on getting some answers.
The diagram below is the configuration we are looking to deploy, that way because we do not have VSS on the 6500 switches so we can not create only one Etherchannel to the 6500s.
Our blades inserted on the UCS chassis have INTEL dual port cards, so they do not support full failover.
Questions I have are.
- Is this my best deployment choice?
- vPC highly depend on the management interface on the Nexus 5000 for the keep alive peer monitoring, so what is going to happen if the vPC brakes due to:
- one of the 6500 goes down
- STP?
- What is going to happend with the Etherchannels on the remaining 6500?
- the Management interface goes down for any other reason
- which one is going to be the primary NEXUS?
Below is the list of devices involved and the configuration for the Nexus 5000 and 65000.
Any help is appreciated.
Devices
· 2 Cisco Catalyst with two WS-SUP720-3B each (no VSS)
· 2 Cisco Nexus 5010
· 2 Cisco UCS 6120xp
· 2 UCS Chassis
- 4 Cisco B200-M1 blades (2 each chassis)
- Dual 10Gb Intel card (1 per blade)
vPC Configuration on Nexus 5000
TACSWN01
TACSWN02
feature vpc
vpc domain 5
reload restore
reload restore delay 300
Peer-keepalive destination 10.11.3.10
role priority 10
!--- Enables vPC, define vPC domain and peer for keep alive
int ethernet 1/9-10
channel-group 50 mode active
!--- Put Interfaces on Po50
int port-channel 50
switchport mode trunk
spanning-tree port type network
vpc peer-link
!--- Po50 configured as Peer-Link for vPC
inter ethernet 1/17-18
description UCS6120-A
switchport mode trunk
channel-group 51 mode active
!--- Associates interfaces to Po51 connected to UCS6120xp-A
int port-channel 51
swithport mode trunk
vpc 51
spannig-tree port type edge trunk
!--- Associates vPC 51 to Po51
inter ethernet 1/19-20
description UCS6120-B
switchport mode trunk
channel-group 52 mode active
!--- Associates interfaces to Po51 connected to UCS6120xp-B
int port-channel 52
swithport mode trunk
vpc 52
spannig-tree port type edge trunk
!--- Associates vPC 52 to Po52
!----- CONFIGURATION for Connection to Catalyst 6506
Int ethernet 1/1-3
description Cat6506-01
switchport mode trunk
channel-group 61 mode active
!--- Associate interfaces to Po61 connected to Cat6506-01
Int port-channel 61
switchport mode trunk
vpc 61
!--- Associates vPC 61 to Po61
Int ethernet 1/4-6
description Cat6506-02
switchport mode trunk
channel-group 62 mode active
!--- Associate interfaces to Po62 connected to Cat6506-02
Int port-channel 62
switchport mode trunk
vpc 62
!--- Associates vPC 62 to Po62
feature vpc
vpc domain 5
reload restore
reload restore delay 300
Peer-keepalive destination 10.11.3.9
role priority 20
!--- Enables vPC, define vPC domain and peer for keep alive
int ethernet 1/9-10
channel-group 50 mode active
!--- Put Interfaces on Po50
int port-channel 50
switchport mode trunk
spanning-tree port type network
vpc peer-link
!--- Po50 configured as Peer-Link for vPC
inter ethernet 1/17-18
description UCS6120-A
switchport mode trunk
channel-group 51 mode active
!--- Associates interfaces to Po51 connected to UCS6120xp-A
int port-channel 51
swithport mode trunk
vpc 51
spannig-tree port type edge trunk
!--- Associates vPC 51 to Po51
inter ethernet 1/19-20
description UCS6120-B
switchport mode trunk
channel-group 52 mode active
!--- Associates interfaces to Po51 connected to UCS6120xp-B
int port-channel 52
swithport mode trunk
vpc 52
spannig-tree port type edge trunk
!--- Associates vPC 52 to Po52
!----- CONFIGURATION for Connection to Catalyst 6506
Int ethernet 1/1-3
description Cat6506-01
switchport mode trunk
channel-group 61 mode active
!--- Associate interfaces to Po61 connected to Cat6506-01
Int port-channel 61
switchport mode trunk
vpc 61
!--- Associates vPC 61 to Po61
Int ethernet 1/4-6
description Cat6506-02
switchport mode trunk
channel-group 62 mode active
!--- Associate interfaces to Po62 connected to Cat6506-02
Int port-channel 62
switchport mode trunk
vpc 62
!--- Associates vPC 62 to Po62
vPC Verification
show vpc consistency-parameters
!--- show compatibility parameters
Show feature
!--- Use it to verify that vpc and lacp features are enabled.
show vpc brief
!--- Displays information about vPC Domain
Etherchannel configuration on TAC 6500s
TACSWC01
TACSWC02
interface range GigabitEthernet2/38 - 43
description TACSWN01 (Po61 vPC61)
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
no ip address
channel-group 61 mode active
interface range GigabitEthernet2/38 - 43
description TACSWN02 (Po62 vPC62)
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
no ip address
channel-group 62 mode activeihernandez81,
Between the c1-r1 & c1-r2 there are no L2 links, ditto with d6-s1 & d6-s2. We did have a routed link just to allow orphan traffic.
All the c1r1 & c1-r2 HSRP communications ( we use GLBP as well ) go from c1-r1 to c1-r2 via the hosp-n5k-s1 & hosp-n5k-s2. Port channels 203 & 204 carry the exact same vlans.
The same is the case on the d6-s1 & d6-s2 sides except we converted them to a VSS cluster so we only have po203 with 4 *10 Gb links going to the 5Ks ( 2 from each VSS member to each 5K).
As you can tell what we were doing was extending VM vlans between 2 data centers prior to arrivals of 7010s and UCS chassis - which worked quite well.
If you got on any 5K you would see 2 port channels - 203 & 204 - going to each 6500, again when one pair went to VSS po204 went away.
I know, I know they are not the same things .... but if you view the 5Ks like a 3750 stack .... how would you hook up a 3750 stack from 2 6500s and if you did why would you run an L2 link between the 6500s ?
For us using 4 10G ports between 6509s took ports that were too expensive - we had 6704s - so use the 5Ks.
Our blocking link was on one of the links between site1 & site2. If we did not have wan connectivty there would have been no blocking or loops.
Caution .... if you go with 7Ks beware of the inability to do L2/L3 via VPCs.
better ?
one of the nice things about working with some of this stuff is as long as you maintain l2 connectivity if you are migrating things they tend to work, unless they really break -
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. -
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.A network diagram would be quite useful ? is it multihop FCoE, Storage connectivity with FCoE,......
-
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 -
UCS C-Series VIC-1225 to Nexus 5000 setup
Hello,
I have two nexus 5000 setup with a vpc peer link. I also have an cisco c240 m3 server with a vic-1225 card that will be running esx 5.1. I also have some 4 2248 fabric extenders. I have been searching for some best practice information on how to best setup this equipment. The nexus equipment is already running, so its more about connecting the c240 and the vic-1225 to the nexus switches. I guess this is better to do rather than to connect to the fabric extenders in order to minmize hops?
All documention I have found involves setup/configuration etc with fabric interconnects which I dont have, and have been told that I do not need. Does anyone have any info on this? and can point me in the right direction to setup this correctly?
More specifically, how should I setup the vic-1225 card to the nexus? just create a regular vpc/port-channel to the nexuses? use lacp and set it to active?
Do I need to make any configuration changes on the vic card via the cimc on the c240 server to make this work?Hello again, Im stuck
This is what I have done. I have created the vPC between my esx host and my two nexus 5000 switches, but it doesnt seem to come up:
S02# sh port-channel summary
Flags: D - Down P - Up in port-channel (members)
I - Individual H - Hot-standby (LACP only)
s - Suspended r - Module-removed
S - Switched R - Routed
U - Up (port-channel)
M - Not in use. Min-links not met
Group Port- Type Protocol Member Ports
Channel
4 Po4(SD) Eth LACP Eth1/9(D)
vPC info:
S02# sh vpc 4
vPC status
id Port Status Consistency Reason Active vlans
4 Po4 down* success success -
vPC config:
interface port-channel4
switchport mode trunk
switchport trunk allowed vlan 20,27,30,50,100,500-501
spanning-tree port type edge trunk
vpc 4
interface Ethernet1/9
switchport mode trunk
switchport trunk allowed vlan 20,27,30,50,100,500-501
spanning-tree port type edge trunk
channel-group 4 mode active
Im unsure what I must configure on the cisco 240M3(esx host) side to make this work. I only have the two default interfaces(eth0 and eth1) on the vic-1225 installed in the esx host, and both have the vlan mode is set to TRUNK.
Any ideas on what I am missing?
Message was edited by: HDA -
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. -
Nexus 5548 and vfc Interfaces - WHY?
What is a vfc and why do we need to configure it? I find this extremely tedious.
I have a Dell blade CNA connected to a Dell M8024-k FCoE transit module, which is then connected to a Cisco Nexus 5K. The Cisco 5K's FC port is in NPIV mode and is connected to a Brocade 300 switch. An FC target is connected to the B300.
So, in configuring this set up, I see that, in the Cisco 5K, one has to map the CNA's Ethernet MAC-address to a vfc!
Why do I have to do this mapping? You dont have to do this with Brocade. For example, in another lab setup, I have a Dell M8428-k FCF (FCoE) switch, which is a Brocade ODM, and there is no such mapping necessary. You bring up a CNA at will, the CNA executees a FIP FLOGI, gets an FPMA from the FC fabric switch, and a construct is seamlessly built between that CNA (or perhaps more correctly stated, the N-Port component of that CNA) and a LUN. NO MANUAL MAPPING is necessary.
Can someone explain this Cisco vfc construct and why one has to engage in this laborious task of mapping every CNA to a vfc? Just trying to understand....perhaps I am missing something.
Thank youHello,
Virtual Fiber Channel ( vfc ) interfaces are used to apply FC features in FCoE link.
Check out the section " Cisco Nexus 5000 Series Virtual Fibre Channel Interfaces " in following link
http://www.cisco.com/en/US/prod/collateral/switches/ps9441/ps9670/white_paper_c11-560403.html
Additional guidelines on vfc configuration are documented here
http://www.cisco.com/en/US/partner/docs/switches/datacenter/nexus5000/sw/fcoe/513_n1_1/b_Cisco_n5k_fcoe_config_gd_re_513_n1_1_chapter_0100.html#con_1288652
Padma
Maybe you are looking for
-
How long does it take for a book in iBooks Author to be published to the iBooks store.
Dear Apple, I have recently submited a book to be published to the iBooks store. I have been waiting for a week for it to be uploaded. I would appreciate if you could give me the longest wait time. Sincerely, John Graham
-
Performance problems with use SCOPE instruction?
Hi All! We have application work with cube bases on SSAS 2008 R2. Also we use writeback function for change data in cube. Now I'm looking bottleneck in our queries. We have following MDX query(for example): select non empty{ ([Date].[Date].[All].chil
-
hello all, for my application,i am storing birthday dates of all of my customers.i want to tell "happy birthday" to them on respective dates.for that i have to see the change of date everyday and i have to cross check each and every day, then i have
-
BlackBerry Handheld Software v6.0.0.3155 (All Languages) Will install to any carrier's 9800 model Package Version: 6.0.0.3155 Consisting of: Applications: 6.0.0.747 Software Platform: 6.6.0.249 File name: 9800AllLang_PBr6.0.0_rel3155_PL6.6.0.249_A6.0
-
Hi All, I've just downloaded iTunes 10, I checked the spec req on the download page and it states that 10.4.11 is supported (with limitations). The installer won't work, it says it requires 10.5! Just checking that there's no way I can get it onto my