Jump to content
Welcome to our new Citrix community!
  • 0

Bonding PIF Does NOT Unplug it From the Network


Eric Pretorious

Question

I've created a new network ('MGT'):

[root@xs0-pdx0 ~]# MGT_NET_UUID=$(xe network-create name-label=MGT)

[root@xs0-pdx0 ~]# echo -e "Management Network UUID: $MGT_NET_UUID\n"
Management Network UUID: 55a27cb0-b779-e462-5cde-f933c12305fe

...bonded the PIF's eth0 & eth3 and joined the bond to the new network:

[root@xs0-pdx0 ~]# PMI_PIF_UUID=$(xe pif-list host-uuid=$INSTALLATION_UUID management=true params=uuid | awk '{ print $5 }')
[root@xs0-pdx0 ~]# MGT_PIF0_UUID=$(xe pif-list host-uuid=$INSTALLATION_UUID device=eth0 params=uuid | awk '{ print $5 }')
[root@xs0-pdx0 ~]# MGT_PIF3_UUID=$(xe pif-list host-uuid=$INSTALLATION_UUID device=eth3 params=uuid | awk '{ print $5 }')
[root@xs0-pdx0 ~]# echo -e "Management PIF UUID's:\n PMI: $PMI_PIF_UUID\n PIF0: $MGT_PIF0_UUID\n PIF3: $MGT_PIF3_UUID\n"
Management PIF UUID's:
 PMI: 27a9c3d8-f069-1f15-9d9e-6d1f7df5d151
 PIF0: 27a9c3d8-f069-1f15-9d9e-6d1f7df5d151
 PIF3: ab5bf3f4-5d67-c324-5017-55e195864c39

[root@xs0-pdx0 ~]# MGT_BOND_UUID=$(xe bond-create network-uuid=$MGT_NET_UUID pif-uuids=$PMI_PIF_UUID,$MGT_PIF3_UUID mode=active-backup)
[root@xs0-pdx0 ~]# MGT_MSTR_UUID=$(xe pif-list host-uuid=$INSTALLATION_UUID network-uuid=$MGT_NET_UUID params=uuid | awk '{ print $5 }')
[root@xs0-pdx0 ~]# echo -e "Management Bond UUID's:\n BOND INTERFACE UUID: $MGT_BOND_UUID\n BOND MASTER UUID: $MGT_MSTR_UUID\n"
Management Bond UUID's:
 BOND INTERFACE UUID: 7daf866e-7a49-07bb-0570-c2cb9c44f9c6
 BOND MASTER UUID: f07c47a9-75db-23cc-3781-3caddb7badf6

But XAPI still believes that the two PIF's eth0 & eth3 are still plugged-in to their default networks:

[root@xs1-pdx0 ~]# xe network-list params=uuid,PIF-uuids,name-label | grep -A1 -B1 eth0
uuid ( RO)          : 790f648b-dd9c-40f4-1ed0-e236653e2fe7
    name-label ( RW): Pool-wide network associated with eth0
     PIF-uuids (SRO): 0e8feea7-1e46-9a79-1dad-6d6f6804b8c1; 84ff2117-1bba-8773-f264-6af7dcdf291b; 27a9c3d8-f069-1f15-9d9e-6d1f7df5d151

[root@xs1-pdx0 ~]# xe network-list params=uuid,PIF-uuids,name-label | grep -A1 -B1 eth3
uuid ( RO)          : 622d182f-d973-3225-06ef-ef85e9cca3b6
    name-label ( RW): Pool-wide network associated with eth3
     PIF-uuids (SRO): 8587cd88-2efd-f4b9-903a-fd4b17d0b5f0; eef4c3a9-cbfc-6e0d-0d70-7f0fb217d207; ab5bf3f4-5d67-c324-5017-55e195864c39

[root@xs1-pdx0 ~]# xe network-destroy uuid=622d182f-d973-3225-06ef-ef85e9cca3b6
The network contains active PIFs and cannot be deleted.
pifs: 8587cd88-2efd-f4b9-903a-fd4b17d0b5f0
<extra>: eef4c3a9-cbfc-6e0d-0d70-7f0fb217d207
<extra>: ab5bf3f4-5d67-c324-5017-55e195864c39

[root@xs1-pdx0 ~]# xe pif-unplug uuid=8587cd88-2efd-f4b9-903a-fd4b17d0b5f0
[root@xs1-pdx0 ~]# xe pif-unplug uuid=eef4c3a9-cbfc-6e0d-0d70-7f0fb217d207
[root@xs1-pdx0 ~]# xe pif-unplug uuid=ab5bf3f4-5d67-c324-5017-55e195864c39 

[root@xs1-pdx0 ~]# xe network-destroy uuid=622d182f-d973-3225-06ef-ef85e9cca3b6
The network contains active PIFs and cannot be deleted.
pifs: 8587cd88-2efd-f4b9-903a-fd4b17d0b5f0
<extra>: eef4c3a9-cbfc-6e0d-0d70-7f0fb217d207
<extra>: ab5bf3f4-5d67-c324-5017-55e195864c39

And what's really puzzling is the fact that XAPI knows that the PIF's are members of bonds:

[root@xs1-pdx0 ~]# xe network-list params=uuid,PIF-uuids,name-label | grep -A1 -B1 MGT
uuid ( RO)          : 55a27cb0-b779-e462-5cde-f933c12305fe
    name-label ( RW): MGT
     PIF-uuids (SRO): 6f7dd651-4447-f01d-9ce3-fe992d355d7b; 697fbb49-93e4-40e3-b36e-bd07d9b83ff5; f07c47a9-75db-23cc-3781-3caddb7badf6

[root@xs1-pdx0 ~]# xe bond-list params=uuid,master,slaves
uuid ( RO)      : 0090d1a8-8793-b78e-2bd7-6c0ed60d9e12
    master ( RO): 697fbb49-93e4-40e3-b36e-bd07d9b83ff5
    slaves ( RO): eef4c3a9-cbfc-6e0d-0d70-7f0fb217d207; 84ff2117-1bba-8773-f264-6af7dcdf291b

uuid ( RO)      : 7daf866e-7a49-07bb-0570-c2cb9c44f9c6
    master ( RO): f07c47a9-75db-23cc-3781-3caddb7badf6
    slaves ( RO): ab5bf3f4-5d67-c324-5017-55e195864c39; 27a9c3d8-f069-1f15-9d9e-6d1f7df5d151

uuid ( RO)      : f5455bc4-9e0a-b65f-b5a7-4e63cde71400
    master ( RO): 6f7dd651-4447-f01d-9ce3-fe992d355d7b
    slaves ( RO): 8587cd88-2efd-f4b9-903a-fd4b17d0b5f0; 0e8feea7-1e46-9a79-1dad-6d6f6804b8c1

 

How can I forcibly unplug the PIF's eth0 & eth3 from the default networks created during installation and then destroy the default networks created during installation?

 

TIA!

Link to comment

11 answers to this question

Recommended Posts

  • 0

Another way of displaying the same information:
 

[root@xs1-pdx0 ~]# xe network-list | grep -B1 -A2 eth3
uuid ( RO)                : 622d182f-d973-3225-06ef-ef85e9cca3b6
          name-label ( RW): Pool-wide network associated with eth3
    name-description ( RW):
              bridge ( RO): xenbr3

[root@xs1-pdx0 ~]# xe network-param-list uuid=622d182f-d973-3225-06ef-ef85e9cca3b6
uuid ( RO)                    : 622d182f-d973-3225-06ef-ef85e9cca3b6
              name-label ( RW): Pool-wide network associated with eth3
        name-description ( RW):
               VIF-uuids (SRO):
               PIF-uuids (SRO): 8587cd88-2efd-f4b9-903a-fd4b17d0b5f0; eef4c3a9-cbfc-6e0d-0d70-7f0fb217d207; ab5bf3f4-5d67-c324-5017-55e195864c39
                     MTU ( RW): 1500
                  bridge ( RO): xenbr3
                 managed ( RO): true
            other-config (MRW):
                   blobs ( RO):
                    tags (SRW):
    default-locking-mode ( RW): unlocked


[root@xs1-pdx0 ~]# xe network-destroy uuid=622d182f-d973-3225-06ef-ef85e9cca3b6
The network contains active PIFs and cannot be deleted.
pifs: 8587cd88-2efd-f4b9-903a-fd4b17d0b5f0
<extra>: eef4c3a9-cbfc-6e0d-0d70-7f0fb217d207
<extra>: ab5bf3f4-5d67-c324-5017-55e195864c39

Notice that the first PIF listed as a slave of each bond appears above in the list of PIF's connected to the "Pool-wide network associated with eth3":

[root@xs1-pdx0 ~]# xe network-list name-label=MGT
uuid ( RO)                : 55a27cb0-b779-e462-5cde-f933c12305fe
          name-label ( RW): MGT
    name-description ( RW):
              bridge ( RO): xapi0


[root@xs1-pdx0 ~]# xe network-param-list uuid=55a27cb0-b779-e462-5cde-f933c12305fe
uuid ( RO)                    : 55a27cb0-b779-e462-5cde-f933c12305fe
              name-label ( RW): MGT
        name-description ( RW):
               VIF-uuids (SRO):
               PIF-uuids (SRO): 6f7dd651-4447-f01d-9ce3-fe992d355d7b; 697fbb49-93e4-40e3-b36e-bd07d9b83ff5; f07c47a9-75db-23cc-3781-3caddb7badf6
                     MTU ( RW): 1500
                  bridge ( RO): xapi0
                 managed ( RO): true
            other-config (MRW):
                   blobs ( RO):
                    tags (SRW):
    default-locking-mode ( RW): unlocked


[root@xs1-pdx0 ~]# xe bond-list master=f07c47a9-75db-23cc-3781-3caddb7badf6
uuid ( RO)      : 7daf866e-7a49-07bb-0570-c2cb9c44f9c6
    master ( RO): f07c47a9-75db-23cc-3781-3caddb7badf6
    slaves ( RO): ab5bf3f4-5d67-c324-5017-55e195864c39; 27a9c3d8-f069-1f15-9d9e-6d1f7df5d151


[root@xs1-pdx0 ~]# xe bond-list master=697fbb49-93e4-40e3-b36e-bd07d9b83ff5
uuid ( RO)      : 0090d1a8-8793-b78e-2bd7-6c0ed60d9e12
    master ( RO): 697fbb49-93e4-40e3-b36e-bd07d9b83ff5
    slaves ( RO): eef4c3a9-cbfc-6e0d-0d70-7f0fb217d207; 84ff2117-1bba-8773-f264-6af7dcdf291b


[root@xs1-pdx0 ~]# xe bond-list master=6f7dd651-4447-f01d-9ce3-fe992d355d7b
uuid ( RO)      : f5455bc4-9e0a-b65f-b5a7-4e63cde71400
    master ( RO): 6f7dd651-4447-f01d-9ce3-fe992d355d7b
    slaves ( RO): 8587cd88-2efd-f4b9-903a-fd4b17d0b5f0; 0e8feea7-1e46-9a79-1dad-6d6f6804b8c1

And one more data point regarding the PIF eth3:

[root@xs1-pdx0 ~]# ovs-appctl bond/list
bond    type    recircID    slaves
bond0    active-backup    0    eth3, eth0

 

Link to comment
  • 0

The pifs are not actually attached to that network though,

 

currently-attached ( RO)    : true
    network-name-label ( RO): MGT

 

currently-attached ( RO)    : false
    network-name-label ( RO): Pool-wide network associated with eth1


currently-attached ( RO)    : false
    network-name-label ( RO): Pool-wide network associated with eth2

 

I will have to do some reading as to why the pool networks cannot be released but im going to theorise that this is for pool join operations as these networks will exist before the bond object does.
 

 

 

Link to comment
  • 0
On 1/22/2018 at 9:04 AM, Marc ONeill said:

The pifs are not actually attached to that network though,

 

currently-attached ( RO)    : true
    network-name-label ( RO): MGT

 

currently-attached ( RO)    : false
    network-name-label ( RO): Pool-wide network associated with eth1


currently-attached ( RO)    : false
    network-name-label ( RO): Pool-wide network associated with eth2

 

I will have to do some reading as to why the pool networks cannot be released but im going to theorise that this is for pool join operations as these networks will exist before the bond object does.

 

Thanks, Marc: But without knowing the commands that you used to produce this information (i.e., Without the context) I'm hesitant to contemplate your feedback (because that output that you cited did not come from the CLI that I provided). e.g., Are these the commands that you used?

 

[root@xs0-pdx0 ~]# xe pif-list host-name-label=xs0-pdx0 device=eth0 physical=true params=device,uuid,currently-attached,network-name-label,bond-slave-of
uuid ( RO)                  : 27a9c3d8-f069-1f15-9d9e-6d1f7df5d151
                device ( RO): eth0
    currently-attached ( RO): false
         bond-slave-of ( RO): 7daf866e-7a49-07bb-0570-c2cb9c44f9c6
    network-name-label ( RO): Pool-wide network associated with eth0


[root@xs0-pdx0 ~]# xe pif-list host-name-label=xs0-pdx0 device=eth3 physical=true params=device,uuid,currently-attached,network-name-label,bond-slave-of
uuid ( RO)                  : ab5bf3f4-5d67-c324-5017-55e195864c39
                device ( RO): eth3
    currently-attached ( RO): false
         bond-slave-of ( RO): 7daf866e-7a49-07bb-0570-c2cb9c44f9c6
    network-name-label ( RO): Pool-wide network associated with eth3

 

BTW: By adding the parameter "bond-slave-of", we can also see that XAPI is aware that the PIF's are connected to the bond! (As displayed above)

 

And another way of arriving at the same conclusion:

 

[root@xs0-pdx0 ~]# xe bond-list params=all slaves=ab5bf3f4-5d67-c324-5017-55e195864c39\;\ 27a9c3d8-f069-1f15-9d9e-6d1f7df5d151
uuid ( RO)             : 7daf866e-7a49-07bb-0570-c2cb9c44f9c6
           master ( RO): f07c47a9-75db-23cc-3781-3caddb7badf6
           slaves ( RO): ab5bf3f4-5d67-c324-5017-55e195864c39; 27a9c3d8-f069-1f15-9d9e-6d1f7df5d151
             mode ( RO): active-backup
       properties (MRO):
    primary-slave ( RO): 27a9c3d8-f069-1f15-9d9e-6d1f7df5d151
         links-up ( RO): 1

 

At this point, without some reasonable explanation of why the PIF's are still considered attached to the Default Networks [that were created during installation], I'm inclined to conclude that this is a bug in XAPI. Especially when you consider the output of these commands:

 

[root@xs0-pdx0 ~]# xe network-list | grep -B1 -A2 eth0
uuid ( RO)                : 790f648b-dd9c-40f4-1ed0-e236653e2fe7
          name-label ( RW): Pool-wide network associated with eth0
    name-description ( RW):
              bridge ( RO): xenbr0

[root@xs0-pdx0 ~]# xe network-param-list uuid=790f648b-dd9c-40f4-1ed0-e236653e2fe7 params=all
uuid ( RO)                    : 790f648b-dd9c-40f4-1ed0-e236653e2fe7
              name-label ( RW): Pool-wide network associated with eth0
                        ...<snip>...
               PIF-uuids (SRO): 0e8feea7-1e46-9a79-1dad-6d6f6804b8c1; 84ff2117-1bba-8773-f264-6af7dcdf291b; 27a9c3d8-f069-1f15-9d9e-6d1f7df5d151
                     MTU ( RW): 1500
                  bridge ( RO): xenbr0
                        ...<snip>...

[root@xs0-pdx0 ~]# xe network-list | grep -B1 -A2 eth3
uuid ( RO)                : 622d182f-d973-3225-06ef-ef85e9cca3b6
          name-label ( RW): Pool-wide network associated with eth3
    name-description ( RW):
              bridge ( RO): xenbr3

[root@xs0-pdx0 ~]# xe network-param-list uuid=622d182f-d973-3225-06ef-ef85e9cca3b6 params=all
uuid ( RO)                    : 622d182f-d973-3225-06ef-ef85e9cca3b6
              name-label ( RW): Pool-wide network associated with eth3
                        ...<snip>...
               PIF-uuids (SRO): 8587cd88-2efd-f4b9-903a-fd4b17d0b5f0; eef4c3a9-cbfc-6e0d-0d70-7f0fb217d207; ab5bf3f4-5d67-c324-5017-55e195864c39
                     MTU ( RW): 1500
                  bridge ( RO): xenbr3
                        ...<snip>...
    default-locking-mode ( RW): unlocked

[root@xs0-pdx0 ~]# ovs-appctl bond/list
bond	type	recircID	slaves
bond0	active-backup	0	eth3, eth0

[root@xs0-pdx0 ~]# ip add | grep xenbr
9: xenbr1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN qlen 1
11: xenbr5: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN qlen 1
12: xenbr4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN qlen 1
14: xenbr2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN qlen 1

 

i.e., Notice that, though xenbr0 & xenbr3 are described in the output of the `xs network-param-list` command as the underlying bridge/switch/network/ (above), Dom0 reports that no such bridge/switch/network exists!

Link to comment
  • 0

Eric,

I'm wondering if the network isn't being "understood" over the whole pool, hwnce confusion. Have you tried doing an "xe pool-sync-database" t make sure all parameters of the pool are known in an updated form to all hosts? Also, any change there is a hung VM that's not releasing a network because of an incorrect powerstate or the like? Are there any suspended or hung tasks (check with "xe task-list")?

 

-=Tobias

Link to comment
  • 0
11 hours ago, Tobias Kreidl said:

I'm wondering if the network isn't being "understodd" over the whole pool, hwnce confusion. Have you tried doing an "xe pool-sync-database" t make sure all parameters of the pool are known in an updated form to all hosts? Also, any change there is a hung VM that's not releasing a network because of an incorrect powerstate or the like? Are there any suspended or hung tasks (check with "xe task-list")?

 

 

On 1/21/2018 at 6:36 PM, Eric Pretorious said:

And what's really puzzling is the fact that XAPI knows that the PIF's are members of bonds:


[root@xs1-pdx0 ~]# xe network-list params=uuid,PIF-uuids,name-label | grep -A1 -B1 MGT
uuid ( RO)          : 55a27cb0-b779-e462-5cde-f933c12305fe
    name-label ( RW): MGT
     PIF-uuids (SRO): 6f7dd651-4447-f01d-9ce3-fe992d355d7b; 697fbb49-93e4-40e3-b36e-bd07d9b83ff5; f07c47a9-75db-23cc-3781-3caddb7badf6

[root@xs1-pdx0 ~]# xe bond-list params=uuid,master,slaves
uuid ( RO)      : 0090d1a8-8793-b78e-2bd7-6c0ed60d9e12
    master ( RO): 697fbb49-93e4-40e3-b36e-bd07d9b83ff5
    slaves ( RO): eef4c3a9-cbfc-6e0d-0d70-7f0fb217d207; 84ff2117-1bba-8773-f264-6af7dcdf291b

uuid ( RO)      : 7daf866e-7a49-07bb-0570-c2cb9c44f9c6
    master ( RO): f07c47a9-75db-23cc-3781-3caddb7badf6
    slaves ( RO): ab5bf3f4-5d67-c324-5017-55e195864c39; 27a9c3d8-f069-1f15-9d9e-6d1f7df5d151

uuid ( RO)      : f5455bc4-9e0a-b65f-b5a7-4e63cde71400
    master ( RO): 6f7dd651-4447-f01d-9ce3-fe992d355d7b
    slaves ( RO): 8587cd88-2efd-f4b9-903a-fd4b17d0b5f0; 0e8feea7-1e46-9a79-1dad-6d6f6804b8c1

 

 

Yes - All three hosts are aware of the MGT network. And all three hosts  believe that the [local] eth0 & eth3 PIF's are bonded and that the bond is connected to that network:

 

[root@xs0-pdx0 ~]# xe pif-list physical=false params=uuid,device,host-name-label,network-name-label,bond-master-of
uuid ( RO)                  : 6f7dd651-4447-f01d-9ce3-fe992d355d7b
                device ( RO): bond0
        bond-master-of ( RO): f5455bc4-9e0a-b65f-b5a7-4e63cde71400
    network-name-label ( RO): MGT
       host-name-label ( RO): xs2-pdx0


uuid ( RO)                  : 697fbb49-93e4-40e3-b36e-bd07d9b83ff5
                device ( RO): bond0
        bond-master-of ( RO): 0090d1a8-8793-b78e-2bd7-6c0ed60d9e12
    network-name-label ( RO): MGT
       host-name-label ( RO): xs1-pdx0


uuid ( RO)                  : f07c47a9-75db-23cc-3781-3caddb7badf6
                device ( RO): bond0
        bond-master-of ( RO): 7daf866e-7a49-07bb-0570-c2cb9c44f9c6
    network-name-label ( RO): MGT
       host-name-label ( RO): xs0-pdx0


[root@xs0-pdx0 ~]# xe bond-list params=
all             links-up        master          mode            primary-slave   properties      slaves          uuid            
[root@xs0-pdx0 ~]# xe bond-list params=slaves uuid=f5455bc4-9e0a-b65f-b5a7-4e63cde71400 
slaves ( RO)    : 8587cd88-2efd-f4b9-903a-fd4b17d0b5f0; 0e8feea7-1e46-9a79-1dad-6d6f6804b8c1


[root@xs0-pdx0 ~]# xe bond-list params=slaves uuid=0090d1a8-8793-b78e-2bd7-6c0ed60d9e12 
slaves ( RO)    : eef4c3a9-cbfc-6e0d-0d70-7f0fb217d207; 84ff2117-1bba-8773-f264-6af7dcdf291b


[root@xs0-pdx0 ~]# xe bond-list params=slaves uuid=7daf866e-7a49-07bb-0570-c2cb9c44f9c6 
slaves ( RO)    : ab5bf3f4-5d67-c324-5017-55e195864c39; 27a9c3d8-f069-1f15-9d9e-6d1f7df5d151

 

I seem to recall something about changing a PIF parameter somehow to remove the association with the default network... 

 

e.g.,

[root@xs0-pdx0 ~]# xe pif-param-list uuid=ab5bf3f4-5d67-c324-5017-55e195864c39
uuid ( RO)                       : ab5bf3f4-5d67-c324-5017-55e195864c39
                     device ( RO): eth3
                        MAC ( RO): 00:26:55:d2:ef:cb
                   physical ( RO): true
                    managed ( RO): true
         currently-attached ( RO): false
                        MTU ( RO): 1500
                       VLAN ( RO): -1
             bond-master-of ( RO):
              bond-slave-of ( RO): 7daf866e-7a49-07bb-0570-c2cb9c44f9c6
...<snip>...
                 management ( RO): false
               network-uuid ( RO): 622d182f-d973-3225-06ef-ef85e9cca3b6
         network-name-label ( RO): Pool-wide network associated with eth3
                  host-uuid ( RO): 72dc05fe-1dc9-4541-9267-4880bc8a5b2a
            host-name-label ( RO): xs0-pdx0
      IP-configuration-mode ( RO): None
                         IP ( RO):
                    netmask ( RO):
                    gateway ( RO):
...<snip>...

 

I'll do some poking around.

Link to comment
  • 0

To provide some context to what I posted,

 

I have a XenServer with two bonded NICs in a network called "MGT" as you do.

 

The output I provided is from - xe pif-list params=network-name-label,currently-attached

 

From this output you can see that the PIFs are not currently plugged to the poolwide networks. Is there a reason you want to remove them?

Link to comment
  • 0
6 hours ago, Marc ONeill said:

To provide some context to what I posted,

 

I have a XenServer with two bonded NICs in a network called "MGT" as you do.

 

The output I provided is from - xe pif-list params=network-name-label,currently-attached

 

From this output you can see that the PIFs are not currently plugged to the poolwide networks. Is there a reason you want to remove them?

 

Thanks, Marc - That's an ironic coincidence!

 

I'd just like to remove the default networks that were created during installation as a matter of hygiene - CLI is so much easier to parse when there's less irrelevant information! (And I prefer to work entirely from the CLI.) Hence my frequent use of grep with the -B and the -A flags to just show the information that's relevant to the situation!

Link to comment
  • 0

http://www.virtues.it/2011/05/cxs56fp1-config-nic-settingsYou need to unplug and plug the interface in order to activate the new settings. If for some reason you cannot perform these actions, the new settings will not be activated untill the XenServer is rebooted. Modifying speed and duplux-mode can also be performed with ethtool, which changes the settings on the fly. The changes made with ethtool are however not persistent and will be discarded after a reboot.

https://showbox.onl/

https://vidmate.win/

https://mobdro.one/

Link to comment
  • 0
On 3/8/2018 at 9:20 PM, nazim zmirli said:

http://www.virtues.it/2011/05/cxs56fp1-config-nic-settingsYou need to unplug and plug the interface in order to activate the new settings. If for some reason you cannot perform these actions, the new settings will not be activated untill the XenServer is rebooted. Modifying speed and duplux-mode can also be performed with ethtool, which changes the settings on the fly. The changes made with ethtool are however not persistent and will be discarded after a reboot.

 

Before attempting to enable multipathing, verify that multiple targets are available on your storage server. For example, an iSCSI storage backend queried for sendtargets on a given portal should return multiple targets

https://get-9apps.comhttps://get-cartoonhd.com https://get-shareit.com 

Link to comment

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...