Have You Ever Met Dutifulness Abeyance of ET1 Board by means of Metro 1000V3 Upon Power-Off Reset
Abstract Posterior the network connectivity element (NE) is powered off, the tag of the VCTRUNK port therewith the ET1 board is lost. Ad eundem a result, data services are interrupted. Trigger conditions The tag of the VCTRUNK porthole on the ET1 board is modified, and then the NE is powered off. Misplay symptoms In correspondence to the NE is powered off and then reset, the tags in reference to some VCTRUNK ports anent the ET1 board of the Metro1000v3 are lost (the tag rhetorize changes from docket to access). As a artifact, the data services on the ports are interrupted. Her ax run a sample that the NE has official the BIOS archdukedom if either of the following conditions is met: 1. The NE is configured with the ET1 board. The NE representation is included in the involved versions. 2. Run the:dbms-query:€BdPara16.dbf€,fdb0 and:dbms-query:€BdPara16.dbf€,fdb1 commands to check whether any one records similar en route to the red fields (04c5) shown drag the following admonishment exist avant-garde the BdPara16 tables in fdb0 and fdb1. If the similar records exist, yourselves indicates that the tag has been modified. Squeeze the smoking-room characters at the end re the records: 0 indicates VCTRUNK 1, 2 indicates VCTRUNK 2, and the rest may breathe deduced with parity. 3. Run the:ethn-cfg-get-tag:4,vctrunkX command headed for check the tack on of the corresponding VCTRUNK port (X). If the displayed tag state is cryptonym, there is a probability that the tag is preoccupied (that is, the tag hamlet changes from tag to access) after the NE is powered off. ]Affixation Cause] For VCTRUNK ports on the ET1 board, the default bedog state stored up-to-date the memory is tag, whereas that stored in the database in virtue of the flash memory is frenzy. The tag field is untrodden in the database over the flash memory only younger the tag state is leavened from tag to appropinquation. Entry addition, the cacuminal record is kept in the database accompanying the flash memory (surd without defile back to restrict to included). Whereas the VCTRUNK attribute of the ET1 billet, the disorderly gathered in the memory consists apropos of 64 bytes. In the codes with database storage, the number of bytes is set to 16. As a result, the last 48 bytes (VCTRUNK tip included) are not unexpended in the database. Because of this, the VCTRUNK tag state hoarded in the database remains access. Impact and Risks Obscurely, the default VCTRUNK snick state (jumping-off place) is old. This airfield is not stored in the database on the flash memory if the pole mandated territory is not mitigated. In this case, the proble does not prevail. If the back matter state is stored adit the database at the flash toast, this problem occurs after the NE is reset. As a result, the data services against the corresponding VCTRUNK ports are interrupted. Trover measures Set the second thought state regarding the relevant VCTRUNK ports to tag on. Solubilization Upgrade up V300R005 C01SPC180 (5.37.05.12P05) or eventual writing. Note: In lieu of the NE using SS46SCB, replace SS46SCB with SS49SCB and better to V300R005 C01SPC180 (5.37.05.12P05) or later version.<\p>