Shulou(Shulou.com)06/01 Report--

La, heroes, meet again, after a long-winded episode of "752", today is the second experiment that takes you to play with DC-"meet N7K for the first time". What if life is just like when we first met? I Bah, isn't it impossible to play with N7K in the palm of your hand all your life? )

First of all, what is Nexus 7000 N7K is the abbreviation of N7K 7000. In Cisco's product structure, there are two 7 series products, Nexus 7000 and Nexus 7700. The main difference is in performance.

(in fact, Cisco is quite back, and the Nexus we are most familiar with should be Google's Nexus series of tablets and phones. In addition, for Cisco's IOS, the IOS we are most familiar with should be Apple's iPhone iPad system. In addition, Cisco's IP phone was just going to be called iPhone.)

The Nexus switch product line is parallel to the Catalyst switch product line, they are all switches, Nexus devices use NX-OS software, Catalyst devices use IOS software. For N7K, the main features that distinguish it from other devices are as follows:

1. Support for VDC (VirtualDevice Context)

VDC is a magical function. Through the efforts of R & D personnel (20, 000 words omitted here), the final result is: physically it is a N7K, but logically it is multiple different N7Ks. The maximum number of VDC that can be virtualized by a physical N7K is related to the model of the engine.

two。 Modular software structure, the use of most features (Feature), need to enable this function first

3. High availability (High Availability, HA)

As a core device in a data center, high availability is essential, and N7K has many features that can guarantee high availability.

Let's start with a positive photo:

Nexus7000 also has different models (7004 7009 7010 7018). Basically, different models can install different numbers of cards. 7004 in the picture can install 4 cards (2 engines and 2 boards), and other performance parameters are basically the same.

Okay, let's learn more about it mainly through experiments.

Experimental equipment: N7K with at least one engine and at least one M1XL module

Physical topology:

A lone N7K can logically become the following topology, which seems a little magical.

Logical topology:

Okay, before we do the VDC experiment, let's say a few more words. For VDC, their status is actually different, in terms of role and status:

1. DefaultVDC

2. Non-defaultVDC

3. AdminVDC

In fact, it is easy to understand that by default, there is only one VDC, that is, defaultVDC,default VDC cannot be deleted or created, and of course non-defaultVDC can be created or deleted.

Depending on the performance of the engine, what is the maximum number of VDC that can be 4 minutes 1 or 8 minutes 1?

In the case of not creating an Admin VDC, the maximum number of VDC is 4 or 8. Here, there are two types of non-defaultVDCc: Ethernet type and Storage type. There can only be one VDC of Storage type. We will introduce this experiment in the storage section. The VDC created and used in the following experiments all belong to the Ethernet type.

Try a tongue twister. If you do not create a separate Admin VDC, DefaultVDC will also serve as the management function. DefaultVDC must be of Ethernet type, and Non-default VDC can be created, either Ethernet or Storage. There can only be one VDC of Storage type.

Default VDC plays the role of Admin, and in this case, Default VDC is a VDC; that can work and manage, but some experts think that there is a hidden danger for a VDC to have two jobs, so Admin VDC is born out of thin air.

Admin VDC: a VDC; that is used only for administrative purposes. So what is administrative use? One word: create and delete VDC, configure basic information about VDC, such as interface partition, install License, enable Feature-set, etc.

To be continued...

Show time, start the experiment. (connect a computer to the Console port of the device with a console cable, omitting 1w words here)

By default, only one VDC,id is 1, and the name is N7K, which is naturally DefaultVDC.

What modules are there on this device?

On slot 1 is the engine, on slot 3 is the module of F2e, and slot 4 is the module of M1XL.

Initially, the interface on the device does not belong to any VDC. If you want to use the port in VDC, of course you have to divide it, just like eating cake. If you want to eat, you have to cut the cake.

Create a VDC called DC2-N7K-3 and divide the interface of E4ax 17-24 into this VDC

Similarly, we are creating a VDC called DC2-N7K-4 that divides the E4ax 25-32 interface into VDC

After dividing the interface, let's take a look at the ownership of the interface.

One problem worth noting is that an interface can be divided into a VDC, if:

This VDC is configured to support the corresponding module type

The consequence if VDC is configured to not support the corresponding module type is:

It is also easy to delete a VDC.

Remind me to say the important things three times:

Laboratory at will, production environment, please do not delete VDC at will, the consequences are very serious.

Laboratory at will, production environment, please do not delete VDC at will, the consequences are very serious.

Laboratory at will, production environment, please do not delete VDC at will, the consequences are very serious.

At this time, E4Compact 18-19 and E4Compact 26-27 have been assigned to two separate devices. If they want to communicate, they must be connected, just like Taiwan was separated from the mainland. Although it used to be a family, it now requires visas.

The default VDC N7K and the newly created DC2-N7K-3 and DC2-N7K-4 are three logically independent devices. To manage the specific configuration of DC2-N7K-3, you must do the following

The way to get back to Default VDC is

VDC is so easy to create and delete, so let's continue to see what Feature is. This must be the case for heroes who are used to using IOS. What functions do you need to configure? OK, let's see if the IOS version supports, yes, OK, pull up the sleeves and straighten up ~ but if you operate on the NX-OS platform, the result is...

You can't even get an order in? What happened? Hey, what's up? Is the function not supported? It's not that you don't support it, but you don't open Feature or Feature-set. The big feature set is Feature-set, and the small feature is Feature.

For example, to configure OSPF, open the feature of OSPF

As you can see, there are a lot of Feature, and almost every function you use needs to open the corresponding Feature. If the command cannot be used, check whether Feature is opened first.

If you want to use FabricPath, it is different. FabricPath belongs to a large feature set and belongs to Feature-set. For example, DC2-N7K-3 needs to use FabricPath function, as follows:

Under Default VDC, install feature-set, and then open FabricPath in the appropriate VDC

You can see that there are actually very few Feature-set, just the four shown in the figure.

Finally, let's take a look at HA. Of course, during the product design of N7K, many features are designed to achieve high availability, such as dual-engine design, redundant power supplies, redundant fans, online software upgrade ISSU (In-Service Software Upgrade), and so on. We will only discuss the HA features of the engine here.

What's the engine? Except that it does not look very similar, it is almost similar to the engine of an airplane. The N7K can be equipped with two engines, which is equivalent to that of an aircraft with two engines, which should be safer than a single-engine aircraft.

So what are the HA modes of the engine? This is going to be discussed in the case of single engine and twin engine.

What? Single engine, don't you mean twin engines? Although I can install twin engines, if I am poor and can only install a single engine, of course, a single-engine plane can also fly, it may not necessarily fall off.

Single engine HA mode: BringdownReload Restart

Dual-engine HA mode: BringdownRestart Switchover

A brief explanation:

Mode effect single engine Reload restarts, or single engine, just like when the plane is flying, the engine restarts. Think about it. Single engine Restart

Delete the VDC and shut down the interface, and then rebuild the VDC load configuration

The inaccurate statement is probably similar to the computer's LogOff and Login single-engine Bringdown.

Hang up, but if something goes wrong, don't do anything about it.

(the engine broke down while the plane was flying, so let's not deal with it, all right.)

Twin-engine Bringdown same single-engine Bringdown twin-engine Restart same single-engine Restart twin-engine Switchover keep all routing calculation, data forwarding and other control planes and forwarding planes in the network unaffected, the main engine transfers the work to the standby engine ~

More fun can come: http://bbs.yeslab.net

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.