The corresponding products of this course are:OptiX 155/622/2500/2500+.

This course, as asubcourse of theECCSpecial Topics course, providesan overall introduction tonetwork elementIDand network elementIPinHuawei's SDHequipment, mainly describingthe definition, components, and applications ofnetwork elementIDand network elementIP.The main contents of this course are as follows:IDchapter,IPchapter, typical case study and other three parts.

After completing this course, you should be able to:

l Understandthe roles ofnetwork elementIDandIPinHuaweiSDHequipment

l Masterthe application configuration ofnetwork elementIDandIP

Each network element has an independent identifierIDthat is used to uniquely identify the network element.ECCcommunicationbetween network elementsisidentifiedby theIDof each network element; network managers also usethenetwork element ID when identifying different network elements in the interface and database, which is used as a keyword to retrieve to mark each network element in the network; and the network elementIDis used to log in to network elements in the command line.

InOptiX devices, we specify that the network elementIDis a24bitbinary number, i.e. three bytes. The dip switches on the main control board (16bitsin total,usually only8to10bitsare solderedinSS31SCC, butall of them are soldered in2500+ ) make upthe lower16bits ofthe network elementID(also known as the baseID), andthe upper8bitsof theIDare the extendedID(default is9), also known as the subnet number (subnet), because it can be used to identify different subnets. The complete ID is composed as follows:

The dip switches on the main control board are shown schematically in Figure 1-1, where dialing ON is 1 and dialing OFF is 0:

In the command line, the login network element or the command line command followed by "#" is the decimal network elementID, and the host software download uses the hexadecimal network elementID. e.g.:

#23:login:1, "nesoft";

Indicates that the loginIDis "23".

The return prompt message is:

#23:szhw>

In more complex networks, there are sometimessituations wheredifferent sites have the sameIDdialing codedue to various reasons.For example, in the network expansion or unified network management project, theIDdialing codeof the newly shipped equipmentand theIDdialing code ofthe equipment running on the networkare duplicated or theIDdialing code ofthe network elements between different subnetsis duplicated. The realization of unified network management requires that the network elementIDshould not be in conflict, and in the past, the maintenance personnel could only run to each site toreset the network elementIDby dialingthe IDdialing switch. if the rectification project is large, the corresponding workload will increase, and in the process of pulling out the main control board may bring about the instability of the network. The common solution now is to change the extendedID, which can be reset by the software on the network management.the default extendedIDofOptiX network elementis9, now only need tochange theextendedIDof one of the two network elements with duplicatedID, so that the network management can distinguish between these two network elements, and it is no longer necessary to dial theIDdip switcheson the main control board.

In the process of communication between the network management and network elements, the destination address (Address) and source addressof the packetare32bits, the lower24bitsof the addressfor the network elementID, the higher8bits for the extended address (note that different from the extendedID), also known as the port number (port), which can be used to identify the same gateway gateway element access to the same gateway when more than one network management (or network element) access point, the current port number has been assigned to the followingThe currently assigned port numbers are :

4: F port access to the networkadministrator/network element

8: Transparent channelfor access networkAV5

17~24: ECCchannelextendedviaLAN

25~100: Command line and other non-specified port number access

101~116: Access to specified port numbers such as network management

Other port numbers are used or reserved for internal use by the host software.

The network elementIDthat we usually dialis actually onlythe lower8bitsof thenetwork elementID.Identifying a network elementwith thelower8 bitsof theIDis limited to a maximum of255.When there is a large grouping (e.g., several hundred stations), itis no longer sufficient to identify the network elementswith only thelower8bits ofthe ID's toggle switch. There are two ways to solve this contradiction: one is toexpand therange of ID representationby setting thehigh 8 bits of thebaseID's dipswitchon theSCCboard; the other is to set the extendedIDwith softwareto categorize the network elements into different subnets.

For example, in Figure 1-2, the8-bitIDdialing code valueson theSCCboardsof stationsA,B,C, andDare bits1,2,3, and4, respectively,whiletheIDdialing codeson theSCCboardsof stationsE,F,G, andHare also1,2,3, and4. In method 1, theIDdialing switcheson the main control boards ofnetwork elementsE,F,G, andHneed to be re-toggled; and in method 2, in thecase where thedefault extendedIDsofA,B,C, andDare9, theJust set theextendedIDofE,F,GandHto"7", and thenE,F,GandHare categorized into another subnet, so that all8stations inthe whole networkhave differentIDs.

:cm-set-subnet:subnet number.

E.g., originalID = 0x090001,:cm-set-subnet:7; thenID = 0x070001;

The master board willautomatically resetafter the subnet number (i.e., extendedIDnumber) setting command takes effect and use the new subnet number. After modifying the subnet number, you can use the command

:cm-get-subnet. to query the modified value.

If a network element is set with a subnet number that is different from the subnet number of the gateway element,you must add the subnet number when youenterthe ID ofthe network element in the command line, andtheIDfollowed by "#"when you log inis in decimal (the current version ofNavigatoronly supports the decimal method, and the hexadecimal one will be provided in the future version ); if you want to log in , you can use the command :cm-get-subnet; to find out the modified value. (the current version of Navigator only supports decimal mode, the hexadecimal mode will be provided in future versions); if the subnet number of the network element you want to log in is the same as that of the gateway element, you do not need to add the subnet number.

For example, to log in tostationAin the grouping above, use:

#1:login:1, "nesoft".

To log in tostationCin the diagram above, sincestationChas the same subnet numberas the gateway network elementstationA(which is the default value of9), then you can log in with the following command:

#3:login:1, "nesoft";

Logging in tostationEin the above figure, sincestationEand gateway network elementstationAhave different subnet numbers (7as default value ), then you need to use the following command to log in:

#458753:login:1, "nesoft"; (458753isthe decimal value of070001)

Note: TheIDused for the host software downloadis still in hexadecimal.

The network elementIDcan also be obtained locally using the command line (i.e., by connecting to the network element to be queried with a direct line). For example, if youtype ":"in the command line window for stationEin the above figure, it will show:

Inversion 4.01.13and later, you can also query the system information database"sys_info.dbf"to get theIDof the network element:

:dbms-query: "sys_info.dbf",drdb;One of the items is the network elementID.

First, make sure that the NICIPaddress ofthe network management computeris129.9.0.Xand the subnet mask is255.255.0.0.

As in the above figure, in the network management, first create the gateway network element A,ID = 1, extendedIDis9, do not change, network element name is set to "A", and set as a gateway (note thatthe IPaddress is129.9.0.1).stationAcan be logged in normally. Then createstationsB,CandDin turn, with extensionIDsof9, and use A as the gateway.

Next, createstationEin the network management,ID=1,set theextendedIDto "7", and select "A" forthe gateway element.In this way,after thesubnet number of stationEhas been setto "7" onthe side of the network element,stationEin the network managementcan log in normally and carry out various configurations, and stationEandstationAare not conflicting with each other in the network management (becausethe 24-digitIDis not the same). Similarly, you can createstationsF,GandHin the network management.

If the network management computer is connected tostationE(assuming thatthe IP ofstationEhas not been modified and is129.9.0.1), then first create the gateway network element "E" inthe network management,ID = 1, extendedID = 7, and set it as the gateway. Then note that the gatewayIPaddressdisplayedis129.7.0.1, which must be changed to "129.9.0.1" (consider why?). Change it to "129.9.0.1" (think about why?). This willallow stationEto log in normally. Then createstationsF,G, andH,allwith extensionIDsof "7" and gateway "E". Next, createstationsA,B,C, andDwith extension"9" and gateway "E".

Afterthe host software and network management support extendedID, it brings great convenience to our work. However, theIDsettingsof network elementsare standardized and cannot be set arbitrarily. In general, the extendedIDof the network elementshould not be changed arbitrarily, please use the default value of "9". Unless in the unified network management or network expansion, due to theworkload ofresetting the dialingIDis too large, or the actual number of network elements has exceeded the range of the dialing switch, then you can use the extendedID. in addition, it is better not to have different subnet numbers for the network elements in the same subnet. For example, in Figure 1-2, network elementsA,B,C, andDshould have the same subnet number.

In practice,the relationship betweenthe network elementIPandIDand its scope of use should have a clearer concept of when it is anIPaddress and when it is a network elementID, so as not to be confused.

The IPaddress isthe packet address used when communicatingbetween the network administrator and the gateway network element through theTCP/IPprotocol, sotheIPaddress is validonly when participating inTCP/IPcommunication, that is, generally only the gateway network element needs to set theIPaddress.the IPaddress cannot be used to uniquely identify the network element (what can uniquely identify the network element is the network elementID).Network elementson differentTCP/IPnetworks can have the sameIPaddress, and a network element can have more than oneIPaddress ( e.g., theIP of a dial-up network, theIP ofan Ethernetport, etc.). For gateway network elements, the followingIPaddresses are used: network elementIP, gatewayIP, subnet mask, and so on.

In essence,IDhas nothing to dowithIP, andbothIDandIPcan be set independently. However,the IPaddress is set by default to beconsistentwiththe ID, i.e.IP = 0x81000000+ID, i.e. ifthe IDis0x090001, theIPdefaults to129.9.0.1. If theIPaddressis set manually,the change of ID will no longer affect theIPaddress. If the manually setIPaddressis canceled,the IPwill follow theIDchange.Theset/query commandsforIPare:cm-set-ip/cm-get-ip. Examples are as follows:

:cm-get-ip.

:cm-set-ip:129.8.0.1;

Aftersetting theIPaddress ofthe network element, the master software will automatically reset and use the newIPaddress. If the parameter is0, it means the setting is cleared andthe IPwill be changed to the default value (Note: some hosts do not supportIPsettingof 0).

Only gateway network elements need to set the "IP" address, it is not recommended toset the"IP"for non-gateway network elements.Aftermanually setting the "IP"of the gateway element, it is recommended to record it in a document so that you do not forget it. If the manually setIPaddress is forgotten, you can only log in tothe network element with the forgottenIP addressthrough a non-gateway network elementand querythe IPaddress fromthe command line.

ForTCP/IPcommunicationthrough a router, the gateway network element should also settheIPof thegateway (gateway)to enable the network element to access the remote networkmanager/network element. The gatewayIPof thegatewaynetwork elementmust beset to the same network segmentas theIPof the network element. If theIPaddress of thegateway to be setis not the same network segmentas theIPaddress ofthe network element, the command line will return an error. The command line commands are:cm-set-gateway/cm-get-gateway. examples are as follows:

:cm-get-gateway.

:cm-set-gateway:129.8.1.1;

where129.8.1.1is theIPaddressof portE0of the router connected to the gateway network element, you need to make sure that theIPaddress ofthe gatewayis in the same network segmentas theIPaddressof the network element.

After the setup command is issued, the master control software uses the new gateway address without automatic reset. If the parameter is0 , it means that the setting is cleared and thegatewayis no longer used.

ForTCP/IPcommunicationthrough the router,thehost software also providesthe function toset theTCP/IPsubnet mask, whichis a four-byte value, expressed in binary asxxxxxxxxxx.xxxxxxxxxx.xxxxxxxxxx.xxxxxxxxxx, where the first portion is the subnet address, and the second portion is the host address, i.e.,HOST. The subnet mask can be used to identify which is the subnet address and which is the host address. For example, a computerIPaddress "132.37.1.17" (converted to binary10000100.00100101.00000001.00010001), subnet mask "255.255.255.240"(converted to binary11111111.11111111.11111111.11110000), then the subnet mask and thecorresponding bits of theIPaddress for the "and" operation, resulting in the subnet address "132.37. 1.16"(converted to binary10000100.00100101.00000001.00010000), andthe IPaddress of the remaining four binary code is the host address "0001". Communication between nodes in the same subnet does not need to be forwarded through the gateway, directly from theARPanalysis to obtain theMACaddressof the opposite end stationcan be, while not in the same subnet communication between nodes need to be forwarded by the gateway.

The command to set the subnet mask is:cm-set-submask/cm-get-submask. examples are as follows:

:cm-get-submask.

:cm-set-submask:255.255.255.0;

The master will automatically reset and make the settings take effect. If the parameter is0, it means that the settings are cleared out and the default value of255.255.0.0is used.

The commandscm-set-subnet/cm-get-subnet,cm-set-gateway/cm-get-gateway, and cm-set-submask/cm-get-submaskare all available only in4.02.03,4.01.15,4.08.01.02,4.05.xand subsequentversions, butcm-set-ip/cm-get-ipareprovidedin all versions. Thecommandsprovided above aboutIDandIPmust be used carefully, and after setting them, they must be recorded and archived for future reference. Moreover, these setting data are saved in the database, if the database is erased, you need to reconfigure these parameters.

There are mainly the following two items:

①,IPaddress and mask "and" after theHOSThost address can not be "0", nor can it be "all1";

②, some of the special address is theTCP / IPprotocol reserved address, can not be used. For example, the network segment255.255.255.224is reserved forTCP/IP;theIPaddressstarting with"127"cannot be used.

For example, the followingIPaddress settings are illegal:

The correct setting ofthe network elementIDandIPis closely related to the normal login of the network element.Althoughincorrectly setting the network elementIDorIPdoes not directly affect the communication service, it may result in misoperation of the network element after switching the network element by mistake, which indirectly affects the normal transmission of the communication service. Moreover, network elementIDandIPfailures are often manifested as abnormal login of network elements, which makes it impossible to maintain and manage abnormal login network elements and monitor the services carried on the network elements.

In daily maintenance, it is necessary to pay attention to checkingwhetherthe IDand extendedIDof the network element,IPaddress, subnet mask and gateway addressof the gateway network elementare correctly set, and if they are set abnormally, they need to be restored immediately so as not to affect the normal management of the network element.

Sincethe IDandIPsettings ofnetwork elementsare saved on the main control board, when the main control board is replaced, it is also necessary to pay attention to the following: correctly set up the dialingID, correctly set up the extensionID; correctly set up theIPaddress, subnet mask, gatewayIP, etc.for the gateway network elements.

The following are sometypical cases ofnetwork elementIDandIPfailures, through which we mainly learn the ideas and methods of handling such failures.

Phenomenon Description:

A capacity expansion project has some newly added network elements, the original network elementIPaddress range is from10.16.2.66 ~ 10.16.2.71, subnet mask is255.255.255.224, the gateway is10.16.2.68. There is a newly added network element, the defaultIPaddress is129.9.1.160.After setting theIP, the subnet mask can never be set successfully.

Troubleshooting:

Modifythe IPof the network administrator computerto10.16.2.72, then re-modifythe IPaddressof the newly created network elementto10.16.2.73, and then modify its subnet mask to255.255.255.224, and the subnet mask is set successfully.

Cause analysis:

The unified subnet mask of the project network element is255.255.255.224, and the subnet segment indicated by the mask can only have²⁵host numbers (because224is converted to binary as11100000), which means that theIPaddressof the new network elementmust be within the32valid addressesadjacent to theoriginalIPaddress ofthe network element, and the range can not be too large or else it exceeds the hosts indicated by the subnet mask. range. The originalIPaddress (10.16.2.160) is outside the host range indicated by the subnet mask. Also note that theIPaddressof the network management computermust be within the32valid addresses.

Phenomenon Description:

When a bureau opens, it is found that a certainSCCboard has anIPaddress of129.9.0.1no matterhow many ID dip switchesaredialed to it.the address that isautomaticallyRETRIEVEDwhen connectingwithnavigatoris129.9.0.1, and after logging in, the title bar showsthe IPaddress as129.9.0.1. when operating on this network element, use the#number of theIDnumber to connect to the network element. For example, ifthe IDis6, use#6to connect to the local network element with theIPaddress129.9.0.1.

Troubleshooting:

1. First try the command::cm-set-ip:0.0.0.0;, after the host reset if unsuccessful, proceed to the next step.

2、 Use:dbms-delete:drdb, "sys_info.dbf";command todeletesys_info.dbflibrary recordindrdb.Becausethe format ofsys_info.dbfinfdb0andfdb1librariesis different, it can not be deleted directly, so you can use:dbms-backup-all:fdb0/fdb1; todelete it in disguise. Reset the master board again, so that it returns tothe state ofdefaultIP, that is,the IPaddresschangeswith theIDsetting.

Cause Analysis:

Afterthe IPaddresshas been setwith the:cm-set-ip: "ipaddress";command, the setIPaddress will be fixed and will notchangewith theID.

1. For155/622hosts support the command:cm-set-ip:followed by a zero parameter, by which the device can be changed to the default value.

2,2500+ devices4.5.2.8and above hosts do not support the above two commands followed by zero parameters.ipand subnet mask values are recorded on the host in thesystem information librarysys_info.dbfindrdb(andfdb0,fdb1after backup).This libraryis not allowed to be modifiedinversion4.5.2.8and above, so it is impossible to modify theIPand subnet mask valuesin this library by the above command, and the only way to change the device to the default values is to delete the library.