Fabric of interconnection Port Mode

Similar Questions

• Fabric of interconnection in the care of the CF NPIV Switch mode? If anyone can confirm?

  Hello

  I'm working on a scenario where a client will make Direct Attach Storage for a pair of UCS fabric of interconnections. It will also need to connect a device of backup based on the CF to the FI. So let's run the s FI mode Switch CF.

  There apparently is a virtual machine on the blades which must have virtual HBA running in order to access their specific LUN.

  The question is whether the fabric interconnect (version 2.1(3b)) will support NPIV when running in the FC switch mode. Or the GUI or CLI Configuration guide mentions this, and I have not any FI to connect to check.

  Can anyone confirm this, either by pointing to a URL where it can be clarified or by connecting a FI Switch FC mode and by:

  connect nxos

  have SH

  or see the race |  feature Inc.

  and check if the npiv feature is enabled or not?

  Thanks a lot for your help

  Gustavo

  NPIV is by default active! See screenshot below

  Tanti saluti

  Walter.

• No link between IOM port 2/2/3 and fabric B interconnection

  Hello

  I am removing an uplink of the IOM to the fabric of interconnection in accordance with its not.  I tried to reset the module e/s and re - emphasize the chassis with no luck, it is still displayed in the GUI with the error message as in the subject.  We are running 2.0(1s).  The kit is not yet in production.

  Thanks for any help

  Hi barry,.

  The only way for you to clean up which will be de-Commission of the chassis in question and add it back again.

  Thank you!

  . / Afonso

• Fabric of interconnection to Bay iSCSI connection

  I need to connect my fabric for interconnection to a new array of iSCSI.  There are a number of blades UCS that need to connect to iSCSI LUNS. The FI is currently connected to the rest of the network through switches to Nexus 7000 K.   Should I I plugged directly from the FI to the iSCSI array or go through the 7000 K and then to the table?

  Hi, this is more a matter of design, you need to think about what will need access to the storage ISCCI matrix. For example, if a single UCS blaes will have access to this storage group, you can consider plug directly such as iscsi traffic must pass your N7Ks if the two fabrics are active. If you want another type of server such as HP or IBM to access storage, you should consider to connect the storage array to the N7Ks if your tissues are configured in end-host mode. Again, this will depend on your current implementation

• FAS3220 and FAS2240 directly set on fabric of interconnection 6296UP

  Hello everyone

  I have the following architecture

  1 cisco Catalyst 6509-E

  1 cisco Catalyst 3560-x

  2 fabric of interconnection 6296UP

  1 FAS 3220 (primary storage)

  1 FAS2240 (backup of the vault)

  1 chassis cisco UCS 5108

  5 servers blades Cisco UCS B200M3

  Firmware version: 2.2 (3 c)

  Interconnection of fabric are set directly on the fabric of interconnection 6296up and ports are configured as storage FC ports

  My question is this:

  Can I zoning fabric interconnect with FAS3220 and FAS2240?

  May I present LUNS of FAS2240 and FAS3220 at the same time on the same startup strategy, same strategy of startup san and the same organization?

  Thanks for your help

  You can make the zoning on UCS:

  http://www.Cisco.com/c/en/us/support/docs/servers-unified-computing/UCS-...

  If it's really a good practice...

  CF sees WWNNs and WWPN.

  What would be the purpose of pointing both starting the 3220 s 2 and the 2240?

• ASR901: encapsulation xconnect vs xconnect default port mode

  Hi all,

  I have a doubt as to the potential difference between the xconnect with lack of encapsulation and the xconnect port mode, is the same thing? One is better than the other? which is the correct implementation and configuration of the port xconnect mode?

  Here is my configuration:

  

  ASR901-3 #sh run inter giga 0/5

  Building configuration...

  Current configuration: 236 bytes

  !

  interface GigabitEthernet0/5

  no ip address

  Loopback driver

  auto negotiation

  No keepalive

  service instance 1 ethernet

  lack of encapsulation

  XConnect 192.168.201.4 123 mpls encapsulation

  !

  end

  17:52:47.338 Jan 10: AToM LDP [192.168.201.4]: sending msg from the notif

  17:52:47.338 Jan 10: AToM LDP [192.168.201.4]: sending notif msg type vc 5, cbit 1,.

  17:52:47.338 Jan 10: AToM LDP [192.168.201.4]:, vc 123 ID.

  17:52:47.338 Jan 10: AToM LDP [192.168.201.4]: group id 0, 29 vc label,.

  17:52:47.338 Jan 10: AToM LDP [192.168.201.4]: status, 0 x 1 0 x 7/LDP/ADJ 0 0.

  17:52:47.338 Jan 10: AToM LDP [192.168.201.4]: mtu 9216, handful of vc 0xF2000007

  17:52:47.338 Jan 10: AToM LDP [192.168.201.4]: VCCV CC 0 x 2, HP 0 x 2

  ASR901-3 #sh mpls l2 retail CR 123

  Local interface: Gi0/5 place, line up, Ethernet protocol: 1

  Destination address: 192.168.201.4, VC ID: 123, status of VC: upward

  Output interface: Vl10, imposed label stack {20-25}

  Preferred path: not configured

  Default path: assets

  Next section: 192.168.201.242

  Create time: 00:05:20, last status change time: 00:00:32

  Last label State FSM change duration: 00:04:02

  Signaling protocol: LDP, peer 192.168.201.4:0 upwards

  Target Hello: Id 192.168.201.6 (LDP)-> 192.168.201.4, LDP is in PLACE

  Graceful restart: don't not configured and enabled not

  Non-stop routing: don't not configured and enabled not

  Support (local or remote) status TLV: enabled/supported

  Watch LDP route: enabled

  State/state machine of the label: Workbench, LruRru

  Last local dataplane of State received: flawless

  Last BFD dataplane received State: not sent

  Last BFD counterpart received status monitor: no fault

  Last received AC circuit State premises: no fault

  Latest local circuit AC status sent: no fault

  Last local PW I / f State received IARC: no fault

  Last local status of LDP TLV sent: no fault

  Last distance LDP TLV received State: no fault

  Last LDP ADJ remote of State received: flawless

  Labels MPLS VC: 29 local, remote 25

  Group ID: 0 local, remote 0

  MTU: 9216 local, remote 9216

  Description of the remote interface:

  Sequencing: persons with disabilities, send the disabled

  Control word: on (configured: automatic detection)

  Dataplane:

  SSM segment/switch ID: 12300/8203 (used), with: 4

  Statistics of the VC:

  transit package totals: receive 0, send 0

  the transit byte totals: receive 0, send 0

  transit packet drops: receive 0, seq 0 error, send 0

  ASR901-3 #.

  the other side:

  ASR901-1 #sh run inter giga 0/6

  Building configuration...

  Current configuration: 147 bytes

  !

  interface GigabitEthernet0/6

  no ip address

  Loopback driver

  auto negotiation

  No keepalive

  XConnect 192.168.201.6 123 mpls encapsulation

  end

  18:49:01.934 Jan 11: AToM LDP [192.168.201.6]: sending msg from the notif

  18:49:01.934 Jan 11: AToM LDP [192.168.201.6]: sending notif msg type vc 5, cbit 1,.

  18:49:01.934 Jan 11: AToM LDP [192.168.201.6]:, vc 123 ID.

  18:49:01.934 Jan 11: AToM LDP [192.168.201.6]: group id 0, label vc 25,.

  18:49:01.934 Jan 11: AToM LDP [192.168.201.6]: status, 0 x 1 0 x 7/LDP/ADJ 0 0.

  18:49:01.934 Jan 11: AToM LDP [192.168.201.6]: mtu 9216, handful of vc 0xAD000001

  18:49:01.934 Jan 11: AToM LDP [192.168.201.6]: VCCV CC 0 x 2, HP 0 x 2

  ASR901-1 #sh mpls l2 vc 123 det

  Local interface: Gi0/6 upward, line protocol up, Ethernet towards the top

  Destination address: 192.168.201.6, VC ID: 123, status of VC: upward

  Output interface: Vl10, imposed label stack {18 29}

  Preferred path: not configured

  Default path: assets

  Next section: 192.168.201.246

  Create time: 00:19:47, last status change time: 00:16:16

  Last label State FSM change duration: 00:19:46

  Signaling protocol: LDP, peer 192.168.201.6:0 upwards

  Target Hello: Id 192.168.201.4 (LDP)-> 192.168.201.6, LDP is in PLACE

  Graceful restart: don't not configured and enabled not

  Non-stop routing: don't not configured and enabled not

  Support (local or remote) status TLV: enabled/supported

  Watch LDP route: enabled

  State/state machine of the label: Workbench, LruRru

  Last local dataplane of State received: flawless

  Last BFD dataplane received State: not sent

  Last BFD counterpart received status monitor: no fault

  Last received AC circuit State premises: no fault

  Latest local circuit AC status sent: no fault

  Last local PW I / f State received IARC: no fault

  Last local status of LDP TLV sent: no fault

  Last distance LDP TLV received State: no fault

  Last LDP ADJ remote of State received: flawless

  Labels MPLS VC: local 25, 29 remote

  Group ID: 0 local, remote 0

  MTU: 9216 local, remote 9216

  Description of the remote interface:

  Sequencing: persons with disabilities, send the disabled

  Control word: on (configured: automatic detection)

  Dataplane:

  SSM segment/switch ID: 4097/4096 (used), with: 1

  Statistics of the VC:

  transit package totals: receive 0, send 0

  the transit byte totals: receive 0, send 0

  transit packet drops: receive 0, seq 0 error, send 0

  # ASR901-1

  In both cases, the loopback driver is set up because I do not have these ports connected to anything. But it's not important at this stage. The thing is that I have two ways to set up the same thing, but I don't know which is the right.

  Thank you very much

  Emiliano

  Hello Emiliano,

  In both cases, the encapsulation for xconnect is mpls only. the other encapsulation tht you defined as the service instance is to map an incoming tag to a service instance. If you receive an image without any tag it will be mapped to the instance of service 1.

  Say assume that instead of 'default of encapsulation' we confiure "encapsulation dot1q 10" then all the frames coming with 10 tag will be mapped to this service instance.

  Now a major difference between the two implementation is, one is the port-based EoMPLS is second evolutionary EoMPLS. In EoMPLS based on port, you can use this port only to L2 circuit service, while as part of the CVS, you can create several service instance and use them for different services.

  Probably the biggest advantage of the VCA framework is the ability to support several services by physical port. This means that under a single physical port, you have the following mixed together:

  -802. 1 q trunk

  -802. 1 q tunnel

  -Local connect

  -Scalable EoMPLS (EoMPLS xconnect)

  -Multipoint Bridging (L2 bypass)

  -Multipoint Bridging (VPLS, focused on the SVI EoMPLS)

  -L3 termination

  Kind regards

  Assani

• How to check the use of the channels of port on fabric of interconnection?

  Hi all

  Is there a mechanism to view and export the use of ports or port channel fabric Interconnect 6248.

  I need to export for the last 15 days. Is there a command or options in the GUI I can export it

  Greetings.

  Native statistics are unlikely to give you a historical trend for the period you're looking for.  See the monitoring/stats for the UCSM system section for more information on the rules of collection of statistics.  The default value for the period appears to be 2 hrs to watch statistics table.

  You can look something like manage performance UCSr, which can do a trend and will retain much historical perspective of production like detailed.

  For a short term in UCSM view, click the LAN tab, then a given port channel, in the right pane statistics, chart and "configure chart" to add in the box counters as "total number of bytes.

  Thank you

  Kirk...

• Adding redundant fabric to interconnect with the existing FI

  For UCS, we have a fabric interconnect version 2.1, customer bought a FI more to add to the cluster configuration.

  The FI is delivered with the latest firmware, please let me know can downgrade us the new FI and forms a cluster or the upgrade of FI existing to the latest firmware.

  Please review best practices for cluster FI configuration.

  First change the old standalone cluster mode FI! Not sure if it is without service interruption. In any case, you must plan a maintenance window!

  Then, if your old FI minimum 2.1.3, you can add the other FI who, in the boot menu, see the FI counterpart and ask if it should cooperatively as a cluster member, synchronization first firmware (Assembly FI will have same firmware release like the old FI).

  Hope that's clear?

• Fabric of interconnections can be re - RPI?

  We decided to use another IP range and I was wondering if I need to do some sort of clear the config or do I go through the installation of transitional upward through the console and change IP addresses?  The original range of subnet 'management' that we were going to use is not available, so I never had with the VIP address.

  Certainlu you can change the IP without having to clear the system.  Remember that it is only a change of plan, not data management, you can do this without disrupting the traffic from your server.

  Here's how I suggest you do:

  1. connect to the Console of each FI with the admin account.

  2. find what FI's secondary by issuing:

  view the status of the cluster

  3. the issue of session from console secondary FI:

  fabric-interconnection of scope [a / b].

  4. set the new IP settings with:

  the value of subnet mask ip out-of-band [address-IP-New] [New-Netmak] gw [New-Bridge]

  buffer validation

  * Note: If the subnet mask and the gateway are not change, you can omit them in the above command.

  * At this point, you should be able to ping the new IP addresses assuming management upstream interface are configured correctly and assigned to the VLAN correct

  5. Repeat for the main fabric connect to the console session.

  6. set the new VIP by launching:

  staff system

  game virtual-ip x.x.x.x

  buffer validation

  7. test the connectivity with each IP & VIP address.

  8. If you have any questions, you should be able to use the console session to correct all errors with no disruption to service other than access UCSM.

  Kind regards

  Robert

• Media Port Mode on a MSE 8510

  Hello

  I would like a confirmation, currently we have a blade in our MSE 8510 and the Media Port is set to HD.

  • This means that we have 20 HD video Ports available (up to 20 endpoints will be able to connect)
  • We have also 20 dedicated ports for streaming.
  • Finally, we have 20 additional voice Ports.

  The problem is that we have a meeting that it will take 26 video Ports, if I put it in the SD, we have about 40 SD video Ports. But no content or audio ports.

  Will be what this means if 26 end points to connect I have 14 left ports and ports audio and content will begin to use my video ports?

  I'd connect 26 people on my MSE 8510, with about 10 people connecting via audio and all end points will receive the content.

  Please see attached picture.

  Yes, if you share your content, will consume you a port video, same thing for one participant audio that connects to the Conference.

• Connection no UCS server to the fabric of interconnection 6248

  We are migrating our VMS of Dell PowerEdge servers to Cisco UCS environment 620\710. The question has been ask if we can connect our Dell servers directly to the IF SFP ports + and/or the connection of TP will 10 GB. Is this possible? How does the FIs treat non - UCS servers?

  This is not supported! I guess you want to do vmotion and transfer your Dell to UCS Server VM. Just configure the appropriate network connectivity (vlan UCS to Northbound Dell server) and it should work.

• FC Port-Channel does not

  Hello

  I need help, I'm setup CF port-channel between 9148 MDS and Cisco fabric Interconnect 6248 and the port-channel does not work. He said no operational members.

  For the MDS, see configuration below:

  NPIV #feature SW (config)

  SW (config) #feature fport-channel-trunk

  SW (config) #interface fc1/17-18

  SW(config-f) force Group-channel mode # 63

  SW(Config-if) F #switchport mode

  SW(Config-if) #switchport trunk-allowed vsan 1-2 (I have only vsan 1 and 2)

  SW (config) #no close

  SW (config) #interface 63 port channel

  SW(Config-if) F #switchport mode

  SW(config-f) #switchport trunk-allowed vsan 1-2

  SW (config) - #no close

  Note: the ports are assigned to vsan 2

  See the attached screenshots for interconnection fabric config

  On the fabric of interconnections switchport mode are defined E. What I have to change to F. If yes where can I change since the option is not there in the UCS Manager?

  have you added the VSANS on the UCSM as well?

  What Code are you runnig on the San Norhbound selector?

  You can be hitting

  https://Tools.Cisco.com/bugsearch/bug/ CSCty04686

• FEX-Uplink Failover, loadbalancing

  I would like to understand more of the technology within a vblock
  I have a few questions gradually

  So I'm out. pls be patient and thank you in advance...

  VBlock 720 with the following generic configuration

  Switch 2 x Cisco 5000 Series
  2 x FI 6248
  6 x chassis 5108
  FEX 2204
  VIC 1240 (no Mezzanine Card)
  8 x M3 blade, 2 CPU

  uplinks of 4 x 10 G of each FEX to FI (port channel)
  uplink of 8 x 10 G of each FI for Ciso 5000 series swith (vpc)

  Assumptions:

  All chassis are completely fill

  Each blade has consistient thoroughput of bandwidth, but 6 GB

  1. When the blades connect to FEX A and B FEX, are active active connections?
  2. For exampleIs blades 1 and 5 has made the fallen on the same ports on the same FEX FEX?
  3. What is the method that load balances blade ping?
  4. Assume 1 Uplink fails between FEX and FI, is the uplink 1 on FEX B overexploited.
  5. How the virtual machine decides which ANC port to send traffic?

  She now...

  See online

  When the blades connect to FEX A and B FEX, are active active connections?

  I assume you mean of FEX = IOM in the chassis;

  Yes the two fabrics are active; all VIC are double hosted the fabric a and b

  For exampleIs blades 1 and 5 has made the fallen on the same ports on the same FEX FEX?

  You have the choice between static pinning (made by UCS Manager) blade slot to an Uplink of IOM, or set a port between IOM and fabric channel interconnection; port channel is the preferred mode.

  Static pinning depends on model of IOM, 2204 / 2208 and the number of uplinks, for example

  2204-4 uplinks

  slot 1 and 5--> uplink 1 chassis

  2 and 6-> uplink 2 chassis slot

  ......

  2208-8 uplinks

  Chassis slot 1-> uplink 1

  Chassis slot 2-> uplink 2

  ......

  Pinning static if a rising fails, the fabric slots correspondent has or b, are declining. There is no repinning for remaining uplinks; grouping and multipathing will take the appropriate action.

  If you have a port-channel, and you lose a link, no problem, as long as there is at least a link to the top; your bandwidth will decrease, but th vnic/vhba are still in place

  What is the method that load balances blade ping?

  Don't understand; To be more specific

  Assume 1 Uplink fails between FEX and FI, is the uplink 1 on FEX B overexploited.

  Yes, in principle. but you will have to design oversubscription from end to end in any case!

  How the virtual machine decides which ANC port to send traffic?

  It depends on the hypervisor; Take, for example, VMware ESXi and vswitch: load balancing can be configured by switch and / or port-group; important caveat: do not hash IP as interconnection of fabric does not support the Protocol LACP; by default, the original virtual¨port code.

• Adding ports to a vlan on interconnection of fabric (end-host Mode)

  Hi all

  I have a problem, I have created vlan 99 and added the ports and port channels to the vlan on the fabric of the ucs interconnections and saved the configs.

  To my surprise, that nothing has changed, they are still on the vlan 1 (the default).

  See my setup below.

  UCS - A eth-link # rising scope
  UCS - Has/eth-uplink # create vlan EMM_NET 99
  UCS - Has/eth-storage / vlan * # create member-port has 15 1
  UCS - Has/eth-storage / vlan * # create member-port a 16 1
  UCS - Has/eth-storage / vlan * # create portchannel members a 61
  UCS - Has/eth-uplink / vlan * # set no sharing
  UCS - Has/eth-uplink / vlan * # commit buffer
  UCS - Has / eth-uplink/vlan #.

  Or should I just create vlan 99 on the switch to the North (Nexus5548UP) because the fabric of interconnection is in fine host mode?

  Kind regards

  OK, now you must give us more detailed information?

  What is your OS? ESXi?

  And maybe, depending on how your host is configured, you should make 99 Vlan as vlan native!

• Conversion of Standalone put in Cluster Mode of interconnection fabric UCS

  Dear all,

  I have an environment, where the configuration is done on the stand-alone version FI. Now the customer has purchased another FI.

  Ask that let me know the best practice to convert the stand-alone version FI in cluster mode.

  If someone can share the document that would be great...

  Looking forward to hear as soon as POSSIBLE.

  Kind regards

  Gopi G

  Very simple. Connect to your existing fabric of interconnection of the field running. Type 'local-mgmt connection '.  In this next command, the IP address is the virtual IP address of the cluster. You will use this from now on to use UCSM. Type 'cluster enable IPAddress '. Answer Yes to the prompt. Cable now your second interconnect with the ports of L1 and L2 as a normal cluster configuration.

  You will need to rework your service profiles since you now have a side B available.

  http://www.Cisco.com/c/en/us/TD/docs/unified_computing/UCS/SW/GUI/config...