 |
Note: For the FPC slot number, specify the actual hardware slot number (numbered 0 through 7) as labeled on the T640 routing node chassis. Do not use the corresponding software FPC number shown in the TX Matrix Platform Chassis and Interface Names. |
A routing matrix supports the same chassis configuration statements as a standalone routing platform (except ce1, ct3, mlfr-uni-nni-bundles, sparse-dlcis, and vtmapping). By including the lcc statement at the [edit chassis] hierarchy level, you configure PIC-specific features, such as framing, on specific T640 routing nodes. In addition, a routing matrix has two more chassis configuration statements, online-expected and offline.
To configure a T640 routing node that is connected to a TX Matrix platform, include the lcc statement at the [edit chassis] hierarchy level:
- [edit chassis]
- lcc number;
number can be 0 through 3.
To configure a T640 routing node within a routing matrix, include the following statements at the [edit chassis lcc number] hierarchy level:
- [edit chassis lcc number]
- fpc slot-number { # Use the hardware FPC slot number
- pic pic-number {
- atm-cell-relay-accumulation;
- atm-l2circuit-mode (cell | aal5 | trunk trunk);
- framing (sdh |
sonet);
-
- idle-cell-format {
- itu-t;
- payload-pattern payload-pattern-byte;
- }
- max-queues-per-interface (8 | 4);
- no-concatenate;
- }
- offline;
- online-expected;
|
Note: For the FPC slot number, specify the actual hardware slot number (numbered 0 through 7) as labeled on the T640 routing node chassis. Do not use the corresponding software FPC number shown in the TX Matrix Platform Chassis and Interface Names. |
For information about how to configure the online-expected and offline configuration statements, see Configuring the JUNOS Software to Enable the TX Matrix Platform to Generate an Alarm if a T640 Routing Node Stays Offline.
