MDC requires a license to run on the device. If no license is installed or the license expires, you cannot create, start, or use non-default MDCs. For more information about licenses, see "Managing licenses."

Overview

The Multitenant Device Context (MDC) technology can partition a physical device or an IRF fabric into multiple logical devices called MDCs. Each MDC uses its own hardware and software resources, runs independently of other MDCs, and provides services for its own customer. Creating, starting, rebooting, or deleting an MDC does not affect any other MDCs. From the user's perspective, an MDC is a standalone physical device.

Each MDC is isolated from the other MDCs on the same physical device and cannot directly communicate with them.

To manage the MDCs on the same physical device, you only need to log in to the physical device.

MDC applications

The MDC technology can be widely used for such applications as device renting, service hosting, and student labs. Instead of purchasing new devices, you can configure more MDCs on existing network devices to expand the network.

As shown in Figure 1, LAN 1, LAN 2, and LAN 3 are three companies' LANs. To provide access service for the three companies, you can deploy a single physical device and configure an MDC for each company on the device. Then, the administrators of each company can log in only to their own MDC to maintain their own network, without affecting any other MDC or network. The effect equals deploying a separate gateway for each company.

Figure 1 Network diagram

Default MDC and non-default MDCs

A device supporting MDCs is called the default MDC (for example, Device in Figure 1). The default MDC always uses the name Admin and the ID 1. You cannot delete it or change its name or ID.

When you log in to the physical device, you are logged in to the default MDC. Configuring the physical device is the same as configuring the default MDC.

On the default MDC, you can perform the following tasks:

· Manage the entire physical device.

· Create and delete non-default MDCs, for example, Device A, Device B, and Device C in Figure 1.

· Assign resources to non-default MDCs. These resources include interfaces, CPU resources, and memory space.

No MDCs can be created on a non-default MDC. Administrators of non-default MDCs can only manage and maintain their respective MDCs.

A non-default MDC can use only the resources assigned to it. It cannot use the resources assigned to other MDCs or the remaining resources on the physical device. Resources that are not assigned to any non-default MDC belong to the default MDC.

Unless otherwise stated, the term "MDC" refers to a non-default MDC and all operations are performed on the default MDC in the following sections.

MDC configuration task list

IMPORTANT:

To configure MDCs for a device that you want to add to an IRF fabric, add the device to the IRF fabric before configuring MDCs. After a device joins an IRF fabric, it reboots and loads the master's configuration instead of its own.

Tasks at a glance
(Required.) Creating an MDC
Assigning hardware resources to MDCs: · (Required.) Assigning physical interfaces and LPUs to MDCs · (Optional.) Specifying a CPU weight for an MDC · (Optional.) Specifying a memory space percentage for an MDC
(Required.) Starting an MDC
(Required.) Accessing an MDC

You can assign hardware resources to MDCs before or after you start the MDCs. As a best practice, assign MDCs resources before starting them.

Creating an MDC

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Create an MDC.	mdc mdc-name [ id mdc-id ]	By default, there is a default MDC with the name Admin and ID 1. The default MDC is system defined. You cannot delete it. The MDC starts to work after you execute the mdc start command. The device supports a maximum of eight non-default MDCs.

Step

Command

Remarks

1. Enter system view.

system-view

N/A

2. Create an MDC.

mdc mdc-name [ id mdc-id ]

By default, there is a default MDC with the name Admin and ID 1.

The default MDC is system defined. You cannot delete it.

The MDC starts to work after you execute the mdc start command.

The device supports a maximum of eight non-default MDCs.

When you delete an MDC, you must use the following procedure so the resources in that MDC can be successfully reclaimed for reassignment:

1. Enter the view of the MDC.

2. Execute the display this command to view the running configuration for the MDC.

3. Use the undo mdc start command to stop the MDC.

4. Use the undo location command to reclaim the LPUs assigned to the MDC.

5. Use the undo allocate interface command to reclaim the physical interfaces assigned to the MDC.

6. Use the undo mdc command to delete the MDC.

Assigning hardware resources to MDCs

When you create an MDC, the system automatically assigns CPU and memory space resources to the MDC to ensure its operation. You can adjust the resource allocations as required.

An MDC needs interfaces to forward packets. However, the system does not automatically assign LPUs or interfaces to MDCs. You must assign interfaces and LPUs to MDCs.

Assigning physical interfaces and LPUs to MDCs

Configuration restrictions and guidelines

You can assign multiple physical interfaces to a non-default MDC. A physical interface must meet the following requirements to be assigned to a non-default MDC:

· The interface is n ot the console port. The console port belongs to the default MDC. You cannot assign a console port to a non-default MDC.

· The interface is not the management Ethernet interface. The physical management Ethernet interface of the device belongs to the default MDC and cannot be assigned to a non-default MDC. When you create an MDC, the system automatically creates one virtual management Ethernet interface for each physical management Ethernet interface. A virtual management Ethernet interface uses the same interface number, physical port, and link as its corresponding physical management Ethernet interface. You can assign IP addresses to the virtual management Ethernet interfaces for access to the MDC. The IP addresses for the virtual management Ethernet interfaces can belong to different subnets.

· The interface belongs to the default MDC. To assign a physical interface that belongs to one non-default MDC to another non-default MDC, you must remove the existing assignment by using the undo allocate interface command.

· The LPU where the interface resides is not assigned to any MDC.

When you assign physical interfaces and LPUs to MDCs, follow these guidelines:

· For an MDC to use a physical interface, you must perform the following tasks:

a. Assign the physical interface to the MDC.

b. Authorize the MDC to use the LPU where the physical interface resides.

· Interfaces on LPUs are grouped. The interfaces in a group must be assigned to or removed from the same MDC at the same time. Different groups of interfaces on an LPU can be assigned to different MDCs. Table 1 shows the interface grouping information.

Table 1 Interface grouping on LPUs

LPU type	Interface grouping
FC and FX cards	Interfaces are grouped by interface number in ascending order, starting from 1. · 1G SFP, 10G SFP+, 10/100/1000Base-T, and 10GBase-T card—Each group has 24 interfaces. · 40G QSFP+ card—Each group has six interfaces. · 100G CXP and 100G CFP2 card—Each group has two interfaces.
FE cards	Each card has one interface group. All interfaces on the card belong to the group.

LPU type

Interface grouping

FC and FX cards

Interfaces are grouped by interface number in ascending order, starting from 1.

· 1G SFP, 10G SFP+, 10/100/1000Base-T, and 10GBase-T card—Each group has 24 interfaces.

· 40G QSFP+ card—Each group has six interfaces.

· 100G CXP and 100G CFP2 card—Each group has two interfaces.

FE cards

Each card has one interface group. All interfaces on the card belong to the group.

· A physical interface can be assigned to only one MDC.

· Assigning or reclaiming a physical interface restores the settings of the interface to the defaults. If the MDC administrator configures the interface during the assigning or reclaiming operation, settings made before the operation is completed are lost.

· To configure parameters for a physical interface that has been assigned to an MDC, you must log in to the MDC.

· To use the shutdown command to shut down the management Ethernet interface, you must be on the default MDC.

When you assign physical interfaces and LPUs to MDCs on an IRF fabric, also follow these guidelines:

· Each chassis must have a minimum of two LPUs that support IRF physical interfaces. As a best practice, set up a minimum of two IRF links on different LPUs. To avoid IRF split, make sure a minimum of one IRF link is operating correctly between IRF member devices while you are configuring MDCs.

· To remove an LPU that holds the IRF physical interface of a non-default MDC, first complete the following tasks:

a. Remove the IRF physical interface configuration for the LPU.

b. Use the save command to save the running configuration.

· IRF links can belong to the default MDC or non-default MDCs. As a best practice for link availability, establish a minimum of two IRF links by using different LPUs. An IRF link can belong to one or more MDCs. The two IRF physical interfaces of an IRF link can belong to the same MDC or different MDCs, as shown in Figure 2.

Figure 2 IRF links for MDCs

· To assign an IRF physical interface to an MDC or reclaim an IRF physical interface from an MDC, complete the following tasks:

a. Use the shutdown command to shut down the interface.

b. Use the undo port group interface command to remove the binding of the physical interface to the IRF port. For more information about the undo port group interface command, see Virtual Technologies Command Reference.

c. Assign or reclaim the IRF physical interface.

d. Use the save command to save the running configuration.

· Assigning an IRF physical interface to or reclaiming an IRF physical interface from an MDC causes the following problems:

? The IRF configuration on the interface is lost.

? The IRF link is closed.

To avoid IRF fabric split, make sure each member device always has a minimum of one IRF link in up state.

Configuration considerations

Before assigning physical interfaces and LPUs to MDCs, determine the following items:

· Number of MDCs.

· Number of physical interfaces that each MDC needs.

· Interface numbers of the physical interfaces to be assigned to MDCs.

· Location of each LPU that holds the physical interfaces to be assigned.

Configuration procedure

To assign physical interfaces to an MDC, you must reclaim the LPUs where the physical interfaces reside from all MDCs, including the default MDC.

To assign physical interfaces and LPUs to an MDC:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter the MDC view of the default MDC.	mdc Admin	N/A
3. Identify the LPUs that the default MDC is authorized to use.	display this	Search the command output for undo location commands. If the undo location command is not displayed for an LPU, the default MDC has been authorized to use the LPU.
4. Reclaim the LPUs.	· In standalone mode: undo location slot slot-number · In IRF mode: undo location chassis chassis-number slot slot-number	To reclaim multiple LPUs from the default MDC, execute this command multiple times.
5. Return to system view.	quit	N/A
6. Enter the MDC view for the MDC to which you want to assign physical interfaces.	mdc mdc-name [ id mdc-id ]	N/A
7. Identify the LPUs that the MDC is authorized to use.	display this	Search the command output for location commands. If the location command is displayed for an LPU, the MDC has been authorized to use the LPU.
8. Reclaim the LPUs.	· In standalone mode: undo location slot slot-number · In IRF mode: undo location chassis chassis-number slot slot-number	To reclaim multiple LPUs from the MDC, execute this command multiple times.
9. Assign physical interfaces to the MDC.	allocate interface interface-list	By default, all physical interfaces belong to the default MDC. A non-default MDC cannot use any physical interfaces. To assign multiple physical interfaces to an MDC, execute this command multiple times.
10. Authorize the MDC to use an LPU.	· In standalone mode: location slot slot-number · In IRF mode: location chassis chassis-number slot slot-number	By default, all LPUs belong to the default MDC. A non-default MDC cannot use any LPUs. Authorize an MDC to use an LPU only if interfaces on the LPU have been assigned to the MDC. If you have assigned interfaces on multiple LPUs to the MDC, execute this command for each of the LPUs.

Specifying a CPU weight for an MDC

To ensure correct operation of all MDCs, assign the MDCs CPU weights. All MDCs share and compete for the CPU resources on the MPUs in the system. All MDCs that are authorized to use the same LPU share and compete for the CPU resources on the LPU. If one MDC occupies too many of the CPU resources, the other MDCs might not be able to operate.

The amount of CPU resources an MDC can use depends on the percentage of its CPU weight among the CPU weights of all MDCs that share the same CPU. For example, if three MDCs share the same CPU, setting their weights to 10, 10, and 5 is equivalent to setting their weights to 2, 2, and 1.

· The two MDCs with the same weight can use the CPU for approximately the same period of time.

· The third MDC can use the CPU for approximately half of the time for each of the other two MDCs.

The CPU weight specified for an MDC takes effect on all MPUs and all LPUs that the MDC can use.

To specify a CPU weight for an MDC:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter MDC view.	mdc mdc-name [ id mdc-id ]	N/A
3. Specify a CPU weight for the MDC.	limit-resource cpu weight weight-value	By default, each MDC has a CPU weight of 10. You can use this command to change the CPU weight for a non-default MDC. The CPU weight for the default MDC cannot be changed.

Specifying a memory space percentage for an MDC

All MDCs share and compete for the memory space of the MPUs in the system. If an MDC occupies too much memory space, the other MDCs might not be able to operate correctly. To avoid this problem, specify a memory space percentage for each MDC.

Before you specify a memory space percentage for an MDC, use the display mdc resource command to view how much memory space the MDC is using. Make sure the memory space you assign to an MDC is sufficient for the MDC to operate correctly.

To specify a memory space percentage for an MDC:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter MDC view.	mdc mdc-name [ id mdc-id ]	N/A
3. Specify a memory space percentage for the MDC.	· In standalone mode: limit-resource memory slot slot-number [ cpu cpu-number ] ratio limit-ratio · In IRF mode: limit-resource memory chassis chassis-number slot slot-number [ cpu cpu-number ] ratio limit-ratio	By default, all MDCs share the memory space on the MPUs in the system, and an MDC can use all the free memory space.

Starting an MDC

For an MDC to operate, you must start the MDC. Starting an MDC is the same as powering on a device.

After you start an MDC, the MDC first starts the automatic configuration process. To verify whether the process is completed, use the switchto mdc command to log in to the MDC. If the servers for automatic configuration are not available, stop the automatic configuration process as prompted. For more information about automatic configuration, see "Using automatic configuration."

To start an MDC:

Step	Command
1. Enter system view.	system-view
2. Enter MDC view.	mdc mdc-name [ id mdc-id ]
3. Start the MDC.	mdc start

Accessing an MDC

A non-default MDC operates in the same way as a standalone device. From the system view of the default MDC, you can log in to a non-default MDC and enter MDC system view. To allow administrators to log in to a non-default MDC by using Telnet or SSH, you must complete one of the following tasks in MDC system view:

· Assign an IP address to the management Ethernet interface.

· Create a VLAN interface on the MDC and assign an IP address to the interface.

To return from an MDC to the default MDC, use the switchback or quit command.

To log in to a non-default MDC from the system view of the default MDC:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Log in to an MDC.	switchto mdc mdc-name	You use this command to log in to only an MDC that is in active state.

Displaying and maintaining MDCs

Execute the following display commands in any view on the default MDC:

Task	Command
Display MDCs and their status.	display mdc [ name mdc-name ]
Display the interfaces of MDCs.	display mdc [ name mdc-name ] interface
Display the CPU and memory space usage of MDCs in standalone mode.	display mdc [ name mdc-name ] resource [ cpu \| memory ] [ slot slot-number [ cpu cpu-number ] ]
Display the CPU and memory space usage of MDCs in IRF mode.	display mdc [ name mdc-name ] resource [ cpu \| memory ] [ chassis chassis-number slot slot-number [ cpu cpu-number ] ]

Execute the following display commands in any view on a non-default MDC:

Task	Command
Display the ID, name, and status of the MDC.	display mdc
Display the interfaces of the MDC.	display mdc interface
Display the CPU and memory space usage of the MDC in standalone mode.	display mdc resource [ cpu \| memory ] [ slot slot-number [ cpu cpu-number ] ]
Display the CPU and memory space usage of the MDC in IRF mode.	display mdc resource [ cpu \| memory ] [ chassis chassis-number slot slot-number [ cpu cpu-number ] ]

MDC configuration examples

MDC configuration example in standalone mode

Network requirements

As shown in Figure 3, two departments need to use the device to access the Internet.

Configure two MDCs on the device to meet the Internet access requirements of two departments. Use the default allocation settings for memory space and CPU resources.

Figure 3 Network diagram

Configuration procedure

1. Create and configure MDCs:

# Create MDCA for Department A.

<Device> system-view

[Device] mdc MDCA

It will take some time to create MDC...

MDC created successfully.

[Device-mdc-2-MDCA] quit

# Create MDCB for Department B.

[Device] mdc MDCB

It will take some time to create MDC...

MDC created successfully.

[Device-mdc-3-MDCB] quit

# Reclaim the LPU in slot 2 from the default MDC.

[Device] mdc Admin

[Device-mdc-1-Admin] undo location slot 2

The configuration associated with the specified slot of MDC will be lost. Continue? [Y/N]:y

[Device-mdc-1-Admin] quit

# Assign interfaces Ten-GigabitEthernet 2/0/1 through Ten-GigabitEthernet 2/0/24 to MDCA.

[Device] mdc MDCA

[Device-mdc-2-MDCA] allocate interface ten-gigabitethernet 2/0/1 to ten-gigabitethernet 2/0/24

Configuration of the interfaces will be lost. Continue? [Y/N]:y

Execute the location slot command in this view to make the configuration take effect.

[Device-mdc-2-MDCA] quit

# Authorize MDCA to use the LPU in slot 2.

[Device-mdc-2-MDCA] location slot 2

# Set the CPU weight to 5 for MDCA.

[Device-mdc-2-MDCA] limit-resource cpu weight 5

# Start MDCA.

[Device-mdc-2-MDCA] mdc start

It will take some time to start MDC...

MDC started successfully.

[Device-mdc-2-MDCA] quit

# Assign interfaces Ten-GigabitEthernet 2/0/25 through Ten-GigabitEthernet 2/0/48 to MDCB.

[Device] mdc MDCB

[Device-mdc-3-MDCB] allocate interface ten-gigabitethernet 2/0/25 to ten-gigabitethernet 2/0/48

Configuration of the interfaces will be lost. Continue? [Y/N]:y

Execute the location slot command in this view to make the configuration take effect.

# Authorize MDCB to use the LPU in slot 2.

[Device-mdc-3-MDCB] location slot 2

# Set the CPU weight to 5 for MDCB.

[Device-mdc-3-MDCB] limit-resource cpu weight 5

# Start MDCB.

[Device-mdc-3-MDCB] mdc start

It will take some time to start MDC...

MDC started successfully.

[Device-mdc-3-MDCB] quit

2. Configure the management Ethernet interface for MDCA:

# Log in to MDCA from the default MDC. Press Ctrl+D as prompted to access the CLI of MDCA.

[Device] switchto mdc MDCA

******************************************************************************

* Without the owner's prior written consent, *

* no decompiling or reverse-engineering shall be allowed. *

******************************************************************************

Automatic configuration is running, press CTRL_D to break or press CTRL_B to

switch back to the default MDC.

<Device> system-view

# Change the device name to MDCA for easy identification of the MDC.

[Device] sysname MDCA

# To enable the MDC administrator to remotely manage the MDC, assign an IP address to the management Ethernet interface and enable the Telnet service.

[MDCA] interface m-gigabitethernet 0/0/0

[MDCA-M-GigabitEthernet0/0/0] ip address 192.168.1.251 24

[MDCA-M-GigabitEthernet0/0/0] quit

[MDCA] telnet server enable

[MDCA] user-interface vty 0 63

[MDCA-line-vty0-63] authentication-mode none

[MDCA-line-vty0-63] user-role mdc-admin

# Return to the default MDC.

[MDCA-line-vty0-63] return

<MDCA> switchback

[Device]

3. Configure the management Ethernet interface for MDCA:

# Log in to MDCB from the default MDC. Press Ctrl+D as prompted to access the CLI of MDCB.

[Device] switchto mdc MDCB

******************************************************************************

* Without the owner's prior written consent, *

* no decompiling or reverse-engineering shall be allowed. *

******************************************************************************

Automatic configuration is running, press CTRL_D to break or press CTRL_B to

switch back to the default MDC.

<Device> system-view

# Change the device name to MDCB for easy identification of the MDC.

[Device] sysname MDCB

# To enable the MDC administrator to remotely manage the MDC, assign an IP address to the management Ethernet interface and enable the Telnet service.

[MDCB] interface m-gigabitethernet 0/0/0

[MDCB-M-GigabitEthernet0/0/0] ip address 192.168.2.252 24

[MDCB-M-GigabitEthernet0/0/0] quit

[MDCB] telnet server enable

[MDCB] user-interface vty 0 63

[MDCB-line-vty0-63] authentication-mode none

[MDCB-line-vty0-63] user-role mdc-admin

# Return to the default MDC.

[MDCB-line-vty0-63] return

<MDCB> switchback

[Device]

Verifying the configuration

1. Verify that the MDCs exist and are operating correctly.

<Device> display mdc

ID Name Status

1 Admin active

2 MDCA active

3 MDCB active

The output shows that the MDCs have been created and are operating correctly.

2. Log in to MDCA as an administrator of Department A and then view the current configuration of the MDC.

C:\> telnet 192.168.1.251

******************************************************************************

* Without the owner's prior written consent, *

* no decompiling or reverse-engineering shall be allowed. *

******************************************************************************

<MDCA> display current-configuration

...

MDC configuration example in IRF mode

Network requirements

As shown in Figure 4, two departments need to use the IRF fabric to access the Internet. In the IRF fabric, each member device has two LPUs. Each LPU has 48 Ten-GigabitEthernet interfaces.

The two member devices are connected with two IRF links. The IRF port on the master is IRF port 1. The IRF port on the subordinate member is IRF port 2. IRF port 1 is bound with Ten-GigabitEthernet 1/2/0/1 and Ten-GigabitEthernet 1/3/0/1. IRF port 2 is bound with Ten-GigabitEthernet 2/2/0/1 and Ten-GigabitEthernet 2/3/0/1.

Configure two MDCs on the IRF fabric to meet the Internet access requirements of two departments. Use the default allocation settings for memory space and CPU resources. Assign Ten-GigabitEthernet 1/2/0/1 through Ten-GigabitEthernet 1/2/0/24 and Ten-GigabitEthernet 2/2/0/1 through Ten-GigabitEthernet 2/2/0/24 to MDCA. Assign Ten-GigabitEthernet 1/3/0/25 through Ten-GigabitEthernet 1/3/0/48 and Ten-GigabitEthernet 2/3/0/25 through Ten-GigabitEthernet 2/3/0/48 to MDCB.

Figure 4 Network diagram

Configuration procedure

The IRF fabric has been established in this example.

1. Remove IRF port bindings:

# Shut down Ten-GigabitEthernet 1/2/0/1 and Ten-GigabitEthernet 2/2/0/1.

<IRF> system-view

[IRF] interface range ten-gigabitethernet 1/2/0/1 ten-gigabitethernet 2/2/0/1

[IRF-if-range] shutdown

[IRF-if-range] quit

# Remove the binding for IRF port 1/1.

[IRF] irf-port 1/1

[IRF-irf-port1/1] undo port group interface Ten-GigabitEthernet1/2/0/1

[IRF-irf-port1/1] quit

# Remove the binding for IRF port 2/2.

[IRF] irf-port 2/2

[IRF-irf-port2/2] undo port group interface Ten-GigabitEthernet2/2/0/1

[IRF-irf-port2/2] quit

2. Create and configure MDCA:

# Create MDCA for Department A.

[IRF] mdc MDCA

It will take some time to create MDC...

MDC created successfully.

[IRF-mdc-2-MDCA] quit

# Reclaim the LPU in slot 2 of each member device from the default MDC.

[IRF] mdc Admin

[IRF-mdc-1-Admin] undo location chassis 1 slot 2

The configuration associated with the specified slot of MDC will be lost. Continue? [Y/N]:y

[IRF-mdc-1-Admin] undo location chassis 2 slot 2

The configuration associated with the specified slot of MDC will be lost. Continue? [Y/N]:y

[IRF-mdc-1-Admin] quit

# Assign Ten-GigabitEthernet 1/2/0/1 through Ten-GigabitEthernet 1/2/0/24 and Ten-GigabitEthernet 2/2/0/1 through Ten-GigabitEthernet 2/2/0/24 to MDCA.

[IRF] mdc MDCA

[IRF-mdc-2-MDCA] allocate interface ten-gigabitethernet 1/2/0/1 to ten-gigabitethernet 1/2/0/24

Configuration of the interfaces will be lost. Continue? [Y/N]:y

Execute the location slot command in this view to make the configuration take effect.

[IRF-mdc-2-MDCA] allocate interface ten-gigabitethernet 2/2/0/1 to ten-gigabitethernet 2/2/0/24

Configuration of the interfaces will be lost. Continue? [Y/N]:y

Execute the location slot command in this view to make the configuration take effect.

[IRF-mdc-2-MDCA] quit

# Authorize MDCA to use the two LPUs.

[IRF-mdc-2-MDCA] location chassis 1 slot 2

[IRF-mdc-2-MDCA] location chassis 2 slot 2

# Set the CPU weight to 5 for MDCA.

[IRF-mdc-2-MDCA] limit-resource cpu weight 5

# Start MDCA.

[IRF-mdc-2-MDCA] mdc start

It will take some time to start MDC...

MDC started successfully.

[IRF-mdc-2-MDCA] quit

3. Configure Ten-GigabitEthernet 1/2/0/1 and Ten-GigabitEthernet 2/2/0/1 as the IRF physical interface on MDCA:

# Log in to MDCA from the default MDC. Press Ctrl+D as prompted to stop automatic MDC configuration and access the CLI of MDCA.

[IRF] switchto mdc MDCA

******************************************************************************

* Without the owner's prior written consent, *

* no decompiling or reverse-engineering shall be allowed. *

******************************************************************************

Automatic configuration is running, press CTRL_D to break or press CTRL_B to

switch back to the default MDC.

<IRF> system-view

# Change the device name to MDCA for easy identification of the MDC.

[IRF] sysname MDCA

# Shut down Ten-GigabitEthernet 1/2/0/1 and Ten-GigabitEthernet 2/2/0/1.

[MDCA] interface range ten-gigabitethernet 1/2/0/1 ten-gigabitethernet 2/2/0/1

[MDCA-if-range] shutdown

[MDCA-if-range] quit

[MDCA] quit

# Return to the default MDC.

<MDCA> switchback

[IRF]

# View the ID of MDCA.

[IRF] display mdc

ID Name Status

1 Admin active

2 MDCA active

# Bind Ten-GigabitEthernet 1/2/0/1 to IRF port 1/1. This setting takes effect immediately because the IRF fabric has been established. If the IRF fabric has not been established, you must activate this setting.

[IRF] irf-port 1/1

[IRF-irf-port1/1] port group mdc 2 interface ten-gigabitethernet 1/2/0/1

You must perform the following tasks for a successful IRF setup:

Save the configuration after completing IRF configuration.

Execute the "irf-port-configuration active" command to activate the IRF ports.

[IRF-irf-port1/1] quit

# Bind Ten-GigabitEthernet 2/2/0/1 to IRF port 2/2. This setting takes effect immediately because the IRF fabric has been established.

[IRF] irf-port 2/2

[IRF-irf-port2/2] port group mdc 2 interface ten-gigabitethernet 2/2/0/1

You must perform the following tasks for a successful IRF setup:

Save the configuration after completing IRF configuration.

Execute the "irf-port-configuration active" command to activate the IRF ports.

[IRF-irf-port2/2] quit

# Log in to MDCA from the default MDC.

[IRF] switchto mdc MDCA

******************************************************************************

* Without the owner's prior written consent, *

* no decompiling or reverse-engineering shall be allowed. *

******************************************************************************

<MDCA> system-view

# Bring up Ten-GigabitEthernet 1/2/0/1 and Ten-GigabitEthernet 2/2/0/1.

[MDCA] interface range ten-gigabitethernet 1/2/0/1 ten-gigabitethernet 2/2/0/1

[MDCA-if-range] undo shutdown

[MDCA-if-range] quit

# To enable the administrator of MDCA to remotely manage MDCA, assign an IP address to the management Ethernet interface and enable the Telnet service.

[MDCA] display interface M-GigabitEthernet brief

Brief information on interfaces in route mode:

Link: ADM - administratively down; Stby - standby

Protocol: (s) - spoofing

Interface Link Protocol Primary IP Description

M-GE1/0/0/0 DOWN DOWN --

M-GE1/0/0/1 DOWN DOWN --

M-GE1/0/0/2 UP UP --

M-GE1/0/0/3 DOWN DOWN --

[MDCA] interface m-gigabitethernet 1/0/0/2

[MDCA-M-GigabitEthernet1/0/0/2] ip address 192.168.1.251 24

[MDCA-M-GigabitEthernet1/0/0/2] quit

[MDCA] telnet server enable

[MDCA] user-interface vty 0 63

[MDCA-line-vty0-63] authentication-mode none

[MDCA-line-vty0-63] user-role mdc-admin

[MDCA-line-vty0-63] return

# Return to the default MDC.

<MDCA> switchback

[IRF]

# Display IRF link information. The two IRF links are both in up state.

<IRF> display irf link

Member 1

IRF Port Interface Status

1 Ten-GigabitEthernet1/2/0/1(MDC2) UP

Ten-GigabitEthernet1/3/0/1 UP

2 disable --

Member 2

IRF Port Interface Status

1 disable --

2 Ten-GigabitEthernet2/2/0/1(MDC2) UP

Ten-GigabitEthernet2/3/0/1 UP

NOTE:

To assign an IRF physical interface to a non-default MDC or establish a new IRF link on a non-default MDC, follow the configuration procedure for MDCA. In the following steps, only interfaces that are not IRF physical interfaces are assigned to MDCB. This configuration method is simpler than assigning IRF physical interfaces, because it does not require you to change the IRF port configuration.

4. Create and configure MDCB:

# Create MDCB for Department B.

[IRF] mdc MDCB

It will take some time to create MDC...

MDC created successfully.

[IRF-mdc-3-MDCB] quit

# Reclaim the LPU in slot 3 of each member device from the default MDC.

[IRF] mdc Admin

[IRF-mdc-1-Admin] undo location chassis 1 slot 3

The configuration associated with the specified slot of MDC will be lost. Continue? [Y/N]:y

[IRF-mdc-1-Admin] undo location chassis 2 slot 3

The configuration associated with the specified slot of MDC will be lost. Continue? [Y/N]:y

[IRF-mdc-1-Admin] quit

# Assign Ten-GigabitEthernet 1/3/0/25 through Ten-GigabitEthernet1/3/0/48 and Ten-GigabitEthernet 2/3/0/25 through Ten-GigabitEthernet 2/3/0/48 to MDCB.

[IRF] mdc MDCB

[IRF-mdc-3-MDCB] allocate interface ten-gigabitethernet 1/3/0/25 to ten-gigabitethernet 1/3/0/48

Configuration of the interfaces will be lost. Continue? [Y/N]:y

Execute the location slot command in this view to make the configuration take effect.

[IRF-mdc-3-MDCB] allocate interface ten-gigabitethernet 2/3/0/25 to ten-gigabitethernet 2/3/0/48

Configuration of the interfaces will be lost. Continue? [Y/N]:y

Execute the location slot command in this view to make the configuration take effect.

# Authorize MDCB to use the two LPUs.

[IRF-mdc-3-MDCB] location chassis 1 slot 3

[IRF-mdc-3-MDCB] location chassis 2 slot 3

# Set the CPU weight to 5 for MDCB.

[IRF-mdc-3-MDCB] limit-resource cpu weight 5

# Start MDCB.

[IRF-mdc-3-MDCB] mdc start

It will take some time to start MDC...

MDC started successfully.

[IRF-mdc-3-MDCB] quit

# Restore the authorization of the two LPUs for the default MDC.

[IRF] mdc Admin

[IRF-mdc-2-Admin] location chassis 1 slot 3

[IRF-mdc-2-Admin] location chassis 2 slot 3

[IRF-mdc-2-Admin] quit

# Log in to MDCB from the default MDC. Press Ctrl+D as prompted to stop automatic MDC configuration and access the CLI of MDCB.

[IRF] switchto mdc MDCB

******************************************************************************

* Without the owner's prior written consent, *

* no decompiling or reverse-engineering shall be allowed. *

******************************************************************************

Automatic configuration is running, press CTRL_D to break or press CTRL_B to

switch back to the default MDC.

<IRF> system-view

# Change the device name to MDCB for easy identification of the MDC.

[IRF] sysname MDCB

# To enable the administrator of MDCB to remotely manage MDCB, assign an IP address to the management Ethernet interface and enable the Telnet service.

[MDCB] display interface M-GigabitEthernet brief

Brief information on interfaces in route mode:

Link: ADM - administratively down; Stby - standby

Protocol: (s) - spoofing

Interface Link Protocol Primary IP Description

M-GE1/0/0/0 DOWN DOWN --

M-GE1/0/0/1 DOWN DOWN --

M-GE1/0/0/2 UP UP --

M-GE1/0/0/3 DOWN DOWN --

[MDCB] interface m-gigabitethernet 1/0/0/2

[MDCB-M-GigabitEthernet1/0/0/2] ip address 192.168.2.252 24

[MDCB-M-GigabitEthernet1/0/0/2] quit

[MDCB] telnet server enable

[MDCB] user-interface vty 0 63

[MDCB-line-vty0-63] authentication-mode none

[MDCB-line-vty0-63] user-role mdc-admin

# Return to the default MDC.

[MDCB-line-vty0-63] return

<MDCB> switchback

[IRF]

Verifying the configuration

1. Verify that the MDCs exist and are operating correctly.

<IRF> display mdc

ID Name Status

1 Admin active

2 MDCA active

3 MDCB active

The output shows that the MDCs have been created and are operating correctly.

2. Log in to MDCA as an administrator of Department A. View the running configuration of the MDC.

C:\> telnet 192.168.1.251

******************************************************************************

* Without the owner's prior written consent, *

* no decompiling or reverse-engineering shall be allowed. *

******************************************************************************

<MDCA> display current-configuration

...

02-Virtual Technologies Configuration Guide

Configuring MDCs

MDC applications

Default MDC and non-default MDCs

Creating an MDC

Configuration restrictions and guidelines

Configuration considerations

Configuration procedure

Specifying a CPU weight for an MDC

Specifying a memory space percentage for an MDC

Displaying and maintaining MDCs

Network requirements

Configuration procedure

Verifying the configuration

Network requirements

Configuration procedure

Verifying the configuration

Cloud & AI

InterConnect

Intelligent Terminal Products

Product Support Services

Technical Service Solutions

Resource Center

Policy

Online Help

Become a Partner

Partner Resources

Partner Business Management

Company Information

News & Events

Contact Us