diff --git a/docs/source/guides/admin-guides/manage_clusters/common/deployment/network/cfg_second_adapter.rst b/docs/source/guides/admin-guides/manage_clusters/common/deployment/network/cfg_second_adapter.rst
index ded30393c..ce6f9b801 100644
--- a/docs/source/guides/admin-guides/manage_clusters/common/deployment/network/cfg_second_adapter.rst
+++ b/docs/source/guides/admin-guides/manage_clusters/common/deployment/network/cfg_second_adapter.rst
@@ -1,6 +1,8 @@
 Configure Additional Network Interfaces old version - confignics - (deprecated)
 ===============================================================================
 
+**"confignics" is deprecated, recommend using new version "confignetwork" instead.**
+
 The **nics** table and the **confignics** postscript can be used to automatically configure additional network interfaces (multiple ethernets adapters, InfiniBand, etc) on the nodes as they are being deployed.
 
 The way the confignics postscript decides what IP address to give the secondary adapter is by checking the nics table, in which the nic configuration information is stored.
@@ -74,12 +76,15 @@ Use command below to add confignics into the node's postscripts list ::
 
     chdef cn1 -p postscripts=confignics
 
+**NOTE**: ``confignics`` is deprecated, you can also use ``chdef cn1 -p postscripts=confignetwork`` instead above ``chdef`` command.
+
 By default, confignics does not configure the install nic. if need, using flag "-s" to allow the install nic to be configured.  ::
 
     chdef cn1 -p prostscripts="confignics -s"
 
 Option "-s" writes the install nic's information into configuration file for persistence. All install nic's data defined in nics table will be written also.
 
+**NOTE**: ``confignics`` is deprecated, you can also use ``chdef cn1 -p postscripts="confignetwork -s"`` instead above ``chdef`` command.
 
 Add network object into the networks table
 ------------------------------------------