Differences

This shows you the differences between two versions of the page.

--- networking:fvcaccessngi [02/09/2025 22:11] – [Initial view of system] andrew
+++ networking:fvcaccessngi [03/09/2025 08:36] (current) – [AccessNGI Configuration] andrew
@@ Line 32: / Line 32: @@
 ADMIN FVCcoreATM>
+ADMIN FVCcoreATM>set telnet passwd yourpassword
+Telnet password changed to: yourpassword
 </code>
@@ Line 82: / Line 84: @@
 </code>
+==== Config of global ATM parameters ====
 Delete the previous config and return to factory defaults
   "set system delflashcfg".
@@ Line 94: / Line 101: @@
 ADMIN FVCcoreATM>show pnni addrtable
-ADMIN FVCcoreATM>
 ADDR: 39826f3148000000000001000a00000000000000 LEN:   104 SCOPE:   0
 ADDR: 39826f3148000000000001002000000000000000 LEN:   104 SCOPE:  96
 ADDR: 39826f3148000000000001002000a0b1007cc200 LEN:   104 SCOPE:   0
+ADMIN FVCcoreATM>
 </code>
@@ Line 110: / Line 117: @@
 This completes the basic global config.
+==== Interfaces ====
 Next start to configure some interfaces:-
@@ Line 120: / Line 129: @@
         "set e1 clocking 201 external"
-Scrambling is only required for e1 ports, not 155MB/s fibre ports.
+Scrambling is only required for e1 ports, not 155MB/s fibre ports. [[hdb3|HDB3 - High Density Bipolar Order 3 Encoding]]
 Please note, the scrambling is to ensure a zero dc average level, not for encryption, security etc....
 HDB3 is "High Density Bipolar 3zero substitution", an alternative to AMI etc. This has to match the line encoding being used by the circuit provider.
-Note also that the pnni implementation includes ilmi, so do NOT enable ilmi for the port. Pnni takes care of it.
+Note also that the PNNI implementation includes ILMI, so do NOT enable ILMI for the port. PNNI takes care of it.
 Next configure the ethernet port to use bridging and connect to ELAN name desired