IHub Interface Guide - 3HH-11983-AAAA-TQZZA-06download.vianet.com.np/Others/Temp/Nokia/Nokia...

Nokia — Proprietary and confidentialUse pursuant to applicable agreements

7302 Intelligent Services Access Manager7330 Intelligent Services Access Manager FTTN7360 Intelligent Services Access Manager FXRelease 5.6

FD 100/320Gbps NT and FX NT IHub Interface Guide

3HH-11983-AAAA-TQZZA

Issue: 06

March 2017


2

FD 100/320Gbps NT and FX NT IHub InterfaceGuide

3HH-11983-AAAA-TQZZA Issue: 06

Nokia is a registered trademark of Nokia Corporation. Other products and company names mentioned herein may be trademarks or tradenames of their respective owners.The information presented is subject to change without notice. No responsibility is assumed for inaccuracies contained herein.© 2014-2017 Nokia. Contains proprietary/trade secret information which is the property of Nokia and must not be made available to, or copied or used by anyone outside Nokia without its written authorization. Not to be used or disclosed except in accordance with applicable agreements.


Issue: 06 3HH-11983-AAAA-TQZZA 3

Table of contents1 Preface...........................................................................................111.1 Scope ........................................................................................................111.2 Audience....................................................................................................111.3 Required knowledge..................................................................................111.4 Product naming .........................................................................................111.5 Documents ................................................................................................111.6 Acronyms and initialisms ...........................................................................111.7 Safety information......................................................................................121.8 Special information ....................................................................................121.9 Release notes............................................................................................12

2 Port Features.................................................................................132.1 Configuration Overview .............................................................................132.2 Ports ..........................................................................................................132.2.1 Port Type ...................................................................................................132.2.1.1 Access Ports..............................................................................................142.2.1.2 Network Ports ............................................................................................142.2.2 Hybrid Ports...............................................................................................142.2.3 Port Category ............................................................................................142.2.4 Port Rate limiting .......................................................................................142.2.5 Link Layer Discovery Protocol (LLDP).......................................................152.2.5.1 LLDP Protocol Features ............................................................................172.3 LAG ...........................................................................................................182.3.1 LAG Features ............................................................................................192.3.1.1 Configuring LAGs ......................................................................................212.3.1.2 LAG Hashing .............................................................................................222.3.1.3 Port Link Damping .....................................................................................222.3.2 Active / Standby Subgroup in Link Aggregation ........................................22

3 Configuring Physical Ports with CLI...........................................253.1 Pre-provisioning Guidelines.......................................................................253.2 Common Configuration Tasks ...................................................................253.2.1 Configuring Ethernet Port Parameters ......................................................263.2.1.1 Ethernet Access Ports ...............................................................................263.2.1.2 Ethernet Network Port ...............................................................................263.2.1.3 Ethernet Hybrid Port ..................................................................................273.2.2 Configuring LAG Parameters ....................................................................27

4 Port and LAG CLI Command Reference.....................................294.1 CLI Command Syntax Symbols.................................................................294.2 Command Hierarchies...............................................................................304.2.1 Port and LAG Configuration Commands ...................................................304.2.2 Port Configuration Command....................................................................314.2.3 Ethernet Command ...................................................................................314.2.4 LAG Command..........................................................................................324.2.5 Show Commands ......................................................................................334.2.6 Monitor Commands ...................................................................................33

4



4.2.7 Clear Commands.......................................................................................334.2.8 Debug Commands.....................................................................................344.3 Configuration Commands..........................................................................344.3.1 Generic Commands...................................................................................344.3.1.1 description .................................................................................................344.3.1.2 shutdown ...................................................................................................344.3.2 General Port Commands...........................................................................354.3.2.1 port ............................................................................................................354.3.2.2 local_nt_ports_only....................................................................................364.3.3 Ethernet Port Commands ..........................................................................364.3.3.1 ethernet .....................................................................................................364.3.3.2 autonegotiate.............................................................................................364.3.3.3 category.....................................................................................................374.3.3.4 dot1q-etype................................................................................................384.3.3.5 duplex ........................................................................................................394.3.3.6 use-vlan-dot1q-etype.................................................................................404.3.3.7 egress-rate ................................................................................................404.3.3.8 encap-type.................................................................................................414.3.3.9 hold-time....................................................................................................414.3.3.10 loopback ....................................................................................................424.3.3.11 mode..........................................................................................................434.3.3.12 speed.........................................................................................................444.3.3.13 lldp .............................................................................................................454.3.3.14 dest-mac....................................................................................................454.3.3.15 admin-status ..............................................................................................464.3.3.16 tx-mgmt-address........................................................................................464.3.3.17 tx-tlvs .........................................................................................................464.3.3.18 tca-interval .................................................................................................474.3.3.19 tca-threshold..............................................................................................484.3.3.20 inputbw ......................................................................................................484.3.3.21 outputbw....................................................................................................484.3.3.22 rxcrcalignerrors..........................................................................................494.3.3.23 txcrcalignerrors ..........................................................................................494.3.3.24 txcollisions .................................................................................................494.3.3.25 suppress-link-state-alarm ..........................................................................504.3.3.26 remark .......................................................................................................504.3.4 LAG Commands........................................................................................514.3.4.1 lag..............................................................................................................514.3.4.2 dynamic-cost .............................................................................................524.3.4.3 encap-type.................................................................................................524.3.4.4 hold-time....................................................................................................534.3.4.5 lacp............................................................................................................534.3.4.6 lacp-xmit-interval .......................................................................................544.3.4.7 lacp-xmit-stdby ..........................................................................................544.3.4.8 link-map-profile ..........................................................................................554.3.4.9 mode..........................................................................................................554.3.4.10 port ............................................................................................................564.3.4.11 sub-group ..................................................................................................574.3.4.12 sub-group-force .........................................................................................58



4.3.4.13 local_nt_ports_only....................................................................................584.3.4.14 sub-group-switch-detect-time ....................................................................584.3.4.15 port-threshold ............................................................................................594.4 Port Show Command ................................................................................594.4.1 port ............................................................................................................604.4.2 lldp .............................................................................................................674.4.3 curr-15min-stats | curr-day-stats | prev-15min-stats | prev-day-stats ........674.5 LAG Show Command................................................................................704.5.1 lag..............................................................................................................704.6 Port Monitor Command .............................................................................744.6.1 lag..............................................................................................................744.6.2 port ............................................................................................................754.7 Clear Commands.......................................................................................774.7.1 lag..............................................................................................................774.7.2 port ............................................................................................................774.7.3 historical-stats............................................................................................784.8 Debug Commands.....................................................................................784.8.1 lag..............................................................................................................78

6





List of figures2 Port Features.................................................................................13Figure 1 LLDP Internal Architecture ........................................................................16Figure 2 MPLS Network Example............................................................................17Figure 3 LAG Configuration .....................................................................................21Figure 4 Active/standby subgroups .........................................................................23

8





List of tables2 Port Features.................................................................................13Table 1 Hashing schemes ......................................................................................22

4 Port and LAG CLI Command Reference.....................................29Table 2 Command Syntax Symbols .......................................................................30Table 3 description command ................................................................................34Table 4 shutdown Command..................................................................................35Table 5 port Command...........................................................................................35Table 6 local_nt_ports_only Command..................................................................36Table 7 ethernet Command....................................................................................36Table 8 autonegotiate Command ...........................................................................37Table 9 category Command ...................................................................................37Table 10 dot1q-etype Command..............................................................................38Table 11 duplex Command ......................................................................................39Table 12 use-vlan-dot1q-etype Command ...............................................................40Table 13 egress-rate Command...............................................................................40Table 14 encap-type Command ...............................................................................41Table 15 hold-time Command ..................................................................................41Table 16 loopback Command...................................................................................42Table 17 mode Command........................................................................................43Table 18 speed Command .......................................................................................44Table 19 lldp Command ...........................................................................................45Table 20 dest-mac Command ..................................................................................45Table 21 admin-status Command ............................................................................46Table 22 tx-mgmt-address Command ......................................................................46Table 23 tx-tlvs Command........................................................................................47Table 24 tca-interval Command ...............................................................................47Table 25 tca-threshold Command ............................................................................48Table 26 inputbw Command.....................................................................................48Table 27 outputbw Command ..................................................................................48Table 28 rxcrcalignerrors Command ........................................................................49Table 29 txcrcalignerrors Command ........................................................................49Table 30 txcollisions Command................................................................................50Table 31 suppress-link-state-alarm Command.........................................................50Table 32 remark Command......................................................................................50Table 33 lag Command ............................................................................................51Table 34 dynamic-cost Command............................................................................52Table 35 encap-type Command ...............................................................................52Table 36 hold-time Command ..................................................................................53Table 37 lacp Command ..........................................................................................53Table 38 lacp-xmit-interval Command......................................................................54Table 39 lacp-xmit-stdby Command.........................................................................55Table 40 link-map-profile Command ........................................................................55Table 41 mode Command........................................................................................55Table 42 port Command...........................................................................................56Table 43 sub-group Command.................................................................................57

10



Table 44 sub-group-force Command........................................................................58Table 45 local_nt_ports_only Command..................................................................58Table 46 sub-group-switch-detect-time Command...................................................58Table 47 port-threshold Command...........................................................................59Table 48 port command............................................................................................60Table 49 General Port Output Fields........................................................................60Table 50 Specific Port Command Output Fields ......................................................61Table 51 Input/Output Command Fields...................................................................63Table 52 Detailed Port Output Fields .......................................................................64Table 53 Detailed port command input/output fields. ...............................................66Table 54 Port Associations Command Output Fields...............................................67Table 55 lldp command ............................................................................................67Table 56 curr-15min-stats | curr-day-stats | prev-15min-stats | prev-day-stats ........67Table 57 Command Output Fields............................................................................68Table 58 lag command.............................................................................................70Table 59 General LAG Command Output Fields......................................................70Table 60 Detailed LAG Command Output Fields .....................................................71Table 61 LAG Statistics Command Output Fields ....................................................72Table 62 LAG Associations Command Output Fields ..............................................73Table 63 LAG link-map-profile Command Output Fields..........................................73Table 64 LAG Associations link-map-profile Command Output Fields.....................74Table 65 lag command.............................................................................................74Table 66 port command............................................................................................75Table 67 lag command.............................................................................................77Table 68 port command............................................................................................77Table 69 historical-stats command...........................................................................78Table 70 lag command.............................................................................................79


Preface


1 PrefaceThis preface provides general information about the documentation set for the 7302 Intelligent Services Access Manager (7302 ISAM), the 7330 Intelligent Services Access Manager Fiber to the Node (7330 ISAM FTTN) and the 7360 Intelligent Services Access Manager FX (7360 ISAM FX).

1.1 Scope

This documentation set provides information about safety, features and functionality, ordering, hardware installation and maintenance, CLI and TL1 commands, and software upgrade and migration procedures for the current release.

1.2 Audience

This documentation set is intended for planners, administrators, operators, and maintenance personnel involved in installing, upgrading, or maintaining the 7302 ISAM, the 7330 ISAM FTTN or the 7360 ISAM FX.

1.3 Required knowledge

Readers must be familiar with general telecommunications principles.

1.4 Product naming

When the term “ISAM” is used alone, then the 7302 ISAM, the 7330 ISAM FTTN and the 7360 ISAM FX are meant. If a feature is valid for only one of the products, the applicability will be explicitly stated.

1.5 Documents

Refer to the Product Information document for your product to see a list of all relevant customer documents and their part numbers.

1.6 Acronyms and initialisms

The expansions and optional descriptions of most acronyms and initialisms appear in the glossary.

Preface

12



1.7 Safety information

For safety information, see the Safety Manual for your product.

1.8 Special information

The following are examples of how special information is presented in this document.

1.9 Release notes

Be sure to refer to the release notes (such as the Customer Release Notes or Emergency Fix Release Note) issued for software loads of your product before you install or use the product. The release notes provide important information about the software load.

Danger — Danger indicates that the described activity or situation may result in serious personal injury or death; for example, high voltage or electric shock hazards.

Warning — Warning indicates that the described activity or situation may, or will, cause equipment damage or serious performance problems.

Caution — Caution indicates that the described activity or situation may, or will, cause service interruption.

Note — A note provides information that is, or may be, of special interest.


Port Features


2 Port Features2.1 Configuration Overview

2.2 Ports

2.3 LAG

2.1 Configuration Overview

NOTE: This document uses the term preprovisioning in the context of preparing or preconfiguring entities such as ports, and interfaces, prior to initialization. These entities can be installed but not enabled. When the entity is in a no-shutdown state (administratively enabled), then the entity is considered to be provisioned.

2.2 Ports

Ports are pre-provisioned during initialization of the node. Besides the physical ports, the node auto-creates a single instance of a virtual port and a single instance of a multicast port. The intent of the virtual port is highlighted in the FD 100/320Gbps NT and FX NT IHub Services Guide. The intent of the multicast ports is highlighted in the FD 100/320Gbps NT and FX NT IHub Router Configuration and Protocols Guide (PIM section).

All ports have dot1q encapsulation type. No other encapsulation types are supported. Port default MTU size is 9212 (without FCS).

2.2.1 Port TypePorts are qualified as one of the following types:

• access• network• hybrid

Port Features

14



2.2.1.1 Access PortsThere are basically two flavors of access ports:

• Access ports are used for customer-facing traffic on which services are configured. If a Service Access Port (SAP) is to be configured on the port, it must be configured as an access port.

• In order to support VLAN services on network-facing ports, such ports will also be defined as “access ports”. The reason is that SAPs will be configured on these ports in order to provide for IP services on top of the VLAN service.

When a port is configured in access mode, one or more services can be configured on the port depending on the encapsulation value.

2.2.1.2 Network PortsNetwork ports participate in the service provider transport or infrastructure network. ISAM supports MPLS on network ports.

2.2.2 Hybrid PortsHybrid ports support the features of both access and network ports. They can't be used for customer facing traffic.

2.2.3 Port CategoryA port is defined to have a category residential or regular. The category determines the way in which MAC learning is dealt with and the rules for user-to-user communication. For more information, see the FD 100/320Gbps NT and FX NT IHub Services Guide.

An access port can have category residential or regular. For some ports, this category can be modified. Network-facing ports that are used as interface towards a subtending ISAM have to be configured with category residential.

In a public access network, residential access ports are connected to subtending ISAMs or LTs and are considered untrusted.

Network ports, hybrid ports, and the virtual port are always of category regular.

2.2.4 Port Rate limitingFor a physical port, the Egress Rate limiting can be configured on a per-port basis by specifying a rate and optionally a burst size.


Port Features


By default, there is no rate limiting.

2.2.5 Link Layer Discovery Protocol (LLDP)The IEEE 802.1ab Link Layer Discovery Protocol (LLDP) standard defines protocol and management elements that are suitable for advertising information to stations attached to the same IEEE 802 LAN (emulation) for the purpose of populating physical or logical topology and device discovery management information databases.

The protocol facilitates the identification of stations connected by IEEE 802 LANs/MANs, their points of interconnection, and access points for management protocols.

Note that LAN emulation and logical topology wording is applicable to customer bridge scenarios (enterprise/carrier of carrier) connected to a provider network offering a transparent LAN emulation service to their customers.

It helps the customer bridges to detect an erroneous connection by an intermediate provider by offering a view of the customer topology where the provider service is represented as a LAN interconnecting these customer bridges.

The IEEE 802.1ab standard defines a protocol that:

• Advertises connectivity and management information about the local station to adjacent stations on the same IEEE 802 LAN.

• Receives network management information from adjacent stations on the same IEEE 802 LAN.

• Operates with all IEEE 802 access protocols and network media.• Establishes a network management information schema and object definitions

that are suitable for storing connection information about adjacent stations.• Provides compatibility with a number of MIBs as shown in Figure 1.

Port Features

16



Figure 1 LLDP Internal Architecture

Network operators must be able to discover the topology information in order to detect and address network problems and inconsistencies in the configuration. Moreover, standard-based tools can address the complex network scenarios where multiple devices from different vendors are interconnected using Ethernet interfaces.

Organizationallydefined local deviceLLDP MIB Extension

(Optional)

Organizationallydefined remote deviceLLDP MIB Extensions

(Optional)

LLDP local systemMIB

LLDP remote systemsMIB

LLDP AgentLLDP Frames

LLDP/LSAP

Local device information Remote device information

PTOPO MIB(Optional)

Entity MIB(Optional)

Interface MIB(Optional)

Other MIBs(Optional)


Port Features


Figure 2 MPLS Network Example

The example in Figure 2 shows an MPLS network that uses Ethernet interfaces in the core or as an access/handoff interface to connect to different kinds of Ethernet-enabled devices such as service gateways/routers, Q-in-Q switches, DSLAMs or customer equipment.

IEEE 802.1ab LLDP running on each Ethernet interface between all the above network elements may be used to discover the topology information.

2.2.5.1 LLDP Protocol FeaturesLLDP is a unidirectional protocol that uses the MAC layer to transmit specific information related to the capabilities and status of the local device. Separately from the transmit direction, the LLDP agent can also receive the same kind of information for a remote device which is stored in the related MIB(s).

MPLS/Native EthCore

QinQSWs

DSLAMs

Ethernet Links - FE/GE/10GE

P P

SG/R

SG/R

LAG

PE PE

PE PE

PE PE

Port Features

18



LLDP itself does not contain a mechanism for soliciting specific information from other LLDP agents, nor does it provide a specific means for confirming the receipt of information. LLDP allows the transmitter and the receiver to be separately enabled, making it possible to configure an implementation so the local LLDP agent can either transmit only or receive only, or can transmit and receive LLDP information.

The information fields in each LLDP frame are contained in a LLDP Data Unit (LLDPDU) as a sequence of variable-length information elements. Each of these elements includes type, length, and value fields (known as TLVs), where:

• Type identifies what kind of information is being sent.• Length indicates the length of the information string in octets.• Value is the actual information that needs to be sent (for example, a binary bit map

or an alphanumeric string that can contain one or more fields).

Each LLDPDU contains four mandatory TLVs and can contain optional TLVs as selected by the network management:

• Chassis ID TLV• Port ID TLV• Time To Live TLV• Zero or more optional TLVs, as allowed by the maximum size of the LLDPDU• End Of LLDPDU TLV

The chassis ID and the port ID values are concatenated to form a logical identifier that is used by the recipient to identify the sending LLDP agent/port. Both the chassis ID and the port ID values can be defined in a number of convenient forms. Once selected however, the chassis ID/port ID value combination remains the same as long as the particular port remains operable.

A non-zero value in the TTL field of the Time To Live TLV tells the receiving LLDP agent how long all information pertaining to this LLDPDU's identifier will be valid. This allows the receiving LLDP agent to automatically discard all the associated information if the sender fails to update it in a timely manner. A zero value indicates that any information pertaining to this LLDPDU's identifier is to be discarded immediately.

2.3 LAG

Based on the IEEE 802.3ad standard, Link Aggregation Groups (LAGs) can be configured to increase the bandwidth available between two network devices, depending on the number of links installed (from 1 to 8). LAG also provides redundancy in the event that one or more links participating in the LAG fail. All physical links in a given LAG links combine to form one logical interface.

Packet sequencing must be maintained for any given session. The used hashing algorithm is based on the type of traffic transported to ensure that all traffic in a flow remains in sequence while providing effective load sharing across the links in the LAG.


Port Features


LAGs must be statically configured or formed dynamically with Link Aggregation Control Protocol (LACP). The optional marker protocol described in IEEE 802.3ad is not implemented.

LAGs can be configured on ports of mode access, hybrid, or network, with category regular or residential.

An LAG cannot be configured on ports connecting to LT boards, the virtual port or the multicast port.

2.3.1 LAG FeaturesIn addition to the mandated IEEE LAG implementation, Nokia’s solution has several improvements including dynamic costing and LAG port threshold features. The dynamic cost and LAG port threshold features can be enabled even if the second node is not an ISAM.

• Dynamic costDynamic cost can be enabled with the configure>lag dynamic-cost command or by the action specified in the configure>lag port-threshold command. If dynamic cost is enabled and the number of active links is greater than the port threshold value (0-7), then the path cost is dynamically calculated whenever there is a change in the number of active links regardless of the specified port threshold action. If the port-threshold is met and the action is set to dynamic cost, then the path cost is dynamically recalculated regardless of the global dynamic cost configuration.Enabling dynamic costing causes the physical link metrics used by OSPF to be applied based on the operational or aggregate link bandwidth in the LAG that is available at the time, providing the number of links that are up exceeds the configured LAG port threshold value. If the number of available links falls below the configured threshold, the configured threshold action determines if and at what cost this LAG will be advertised.For example, assume a single link in OSPF has an associated cost of 100 and the LAG consists of four physical links. The cost associated with the logical link is 25. If one link fails then the cost would automatically be adjusted to 33.If dynamic cost is not configured then costing is applied based on the total number of links configured. The cost would be calculated at 25. This will remain static provided the number of links that are up exceeds the configured LAG threshold.

Port Features

20



• LAG port thresholdThe LAG port threshold feature allows configuration of the behavior, once the number of available links in a LAG falls below or is equal to the specified threshold. Two options are available:

• If the number of links available (up) in a LAG is less than the configured threshold, then the LAG is regarded as operationally down. For example, assume a LAG consists of eight physical links. The threshold is set to four and dynamic costing is not configured. If the operational links is equal to or drops below four, the link is regarded as operationally down until the number of operational links is four or more.

• When the number of links available in a LAG is less than the configured threshold, the LAG starts using the dynamic-cost allowing other nodes to adjust their routing tables according to the revised costs. In this case, when the threshold is not crossed, a fixed metric (all links operational) is advertised.

• Link-map-profileLink-map-profile can be configured with the configure>lag>link-map-profile command. A lag member port can be added to the link-map-profile with the configure>lag>link-map-profile>link [port] [primary/secondary]. Link-map-profile failure-mode can be configured with configure>lag>link-map-profile>failure-mode {per-link-hash | discard}. The default failure-mode is per-link-hash. The link-map-profile configured lag can be only associated with v-vpls service. When the lag is associated with v-vpls service, the corresponding traffic can be pinned with the primary port of the corresponding link-map-profile. If the primary port is not configured or operation is down, traffic can be pinned with the secondary port, or else can take any other free port in the lag. For a lag, a maximum of 8 link-map-profile can be created, with profile ID ranging from 1 to 32. Only lag member ports can be added with link-map-profile.There are some restrictions for link-map-profile:

• the link-map-profile feature is not supported for the NANT-D board• each port/LAG-link can associate with only one link-map-profile• each V-VPLS can associate with only one link-map-profile SAP• SAPs in LAG with link-map-profile(s) can only associate with V-VPLS service• there is no per-link-hash fallback protection for pinned traffic when default-profile has

no ports• when the default-profile has no ports, it is expected that non-pinned traffic will drop• link-map-profile and sub-group configurations cannot coincide in a LAG• link-map-profile cannot exist in a LAG that is in network mode, and network mode

cannot be configured in a LAG that has link-map-profile• link-map-profile cannot exist in a LAG that is in hybrid mode, and hybrid mode cannot

be configured in a LAG that has link-map-profile• link-map-profile cannot exist in a LAG that has local_nt_ports configured, and

local_nt_ports cannot be configured in a LAG that has link-map-profile• link-map-profile is not permitted in a LAG that is configured as eth-ring SAP, and

eth-ring SAP cannot be configured in a LAG that has link-map-profile• link-map-profile does not support the combination of active and standby ports in a

LAG, for FNIO-A


Port Features


2.3.1.1 Configuring LAGsLAG configuration guidelines include:

• Ports can be added or removed from the LAG while the LAG and its ports (other than the port being removed) remain operational. When ports to and/or from the LAG are added or removed, the hashing algorithm is adjusted for the new port count.

• show commands display physical port statistics on a port-by-port basis or the entire LAG can be displayed.

• LAG is supported on Ethernet ports.• Ports of a particular LAG can be of different types but they must be the same

speed and duplex. To guarantee the same port speed is used for all ports in a LAG, auto-negotiation must be disabled or in limited mode to ensure only a specific speed is advertised.

The following restrictions apply when configuring LAGs:

• The physical port does not meet the criteria for duplex and speed of the other ports in the LAG. This includes egress-rate and egress-burst.

• The port being added does not have the same encapsulation type as the LAG.• The port being added has existing child dependencies configured on top of the

LAG (such as v-VPLS SAP). In this case the command is blocked and the operator is warned to remove the dependencies.

• The port mode does not match the LAG mode.• The port of type regular or residential does not match the LAG type.• The port being added is an LT port, a virtual port or a multicast port. This attempt

will be denied.• The port being added exceeds the number of supported ports in a LAG, the

attempt will be denied.• Port being added already exists in another LAG.

Figure 3 displays traffic routed between ALA-1 and ALA-2 as a LAG consisting of four ports.

Figure 3 LAG Configuration

ALA-1 ALA-4

ALA-2

LAG-1

LAG-2

ALA-3

Port Features

22



2.3.1.2 LAG HashingWhen a requirement exists to increase the available bandwidth for a logical link that exceeds the physical bandwidth or to add redundancy for a physical link, Link Aggregation (LAG) is applied. The ISAM supports up to eight ports per LAG.

To avoid out-of-sequence packets the algorithm for selecting the next hop in a LAG must be deterministic and at line rate.

Depending on the type of traffic that needs to be distributed into a LAG, different variables are used as input to the hashing algorithm that determines the next hop selection. Hashing modes are listed in Table 1.

Table 1 Hashing schemes

Legend:OuterVID: outer most VLAN ID of the packetIPSA: IP Source AddressIPDA: IP Destination AddressIPPROTO: IP Protocol field in the IP HeaderTCP/UDP-SRC: TCP or UDP Source Port numberTCP/UDP-DST: TCP or UDP Destination Port numberINPORT: physical port the packet arrived onMACDA: MAC Destination AddressMACSA: MAC Source AddressETYPE: Ethertype field

2.3.1.3 Port Link DampingHold time controls enable port link damping timers that reduce the number of link transitions reported to upper layer protocols.

The port link damping feature guards against excessive port transitions. Any initial port transition is immediately advertised to upper layer protocols, but any subsequent port transitions are not advertised to upper layer protocols until a configured timer has expired.

A “down” timer controls the dampening timer for link down transitions.

2.3.2 Active / Standby Subgroup in Link AggregationActive and standby subgroups can be configured in LAG. See Figure 4.

Packet type Hash based on:

If the packet is an IP packet OuterVID+IPSA+IPDA+IPPROTO+TCP/UDP-SRC+TCP/UDP-DST+INPORT

If the packet is not an IP packet

MACDA+MACSA+OuterVID+ETYPE+INPORT


Port Features


Figure 4 Active/standby subgroups

The following must be configured for the LAG subgroups:

• A preference for each subgroup:the subgroup with the lowest preference is the most preferred subgroup

• A threshold for each subgroup:when the number of active links in the subgroup is equal to or lower than this threshold, a switchover to another subgroup is initiated. The selection of this subgroup is based on the preference

• A switchover detection time:this switchover detection time is based on the hold-time configured for the ports in the LAG

• If required, a “force-active” of a subgroup:this “force-active” overrides the preference-based subgroup selection.

The following restrictions apply when configuring subgroups:

• Ports can only be added to a subgroup when the preference for a subgroup has been configured to a non-zero value

• A subgroup with available ports cannot have a preference value of zero• Two subgroups cannot have the same non-zero preference value• The value of a subgroup threshold is expected to be greater than the LAG port

threshold (this is not enforced).

ISAM

LAGStandbysubgroup

Activesubgroup

UpstreamNE1

UpstreamNE2

Port Features

24



The following applies for subgroup selection:

• The selection of subgroups in static LAG is non-revertive. Switchover from a subgroup will not occur unless the threshold is hit or a forced switchover is initiated

• If the number of active links in the subgroup to which switchover has occurred is lower than the configured threshold for this subgroup, that subgroup will remain active despite having a number of active links that is lower then the configured threshold

• If the number of active links in the subgroup to which switchover has occurred is zero, then a switchover to the next subgroup will be initiated. This switchover is based on the configured preference

• When the number of active links in all subgroups is zero, then the subgroup which was last carrying traffic will be chosen as the active subgroup

• The two upstream NEs should have the same IP address and the same MAC address.

The following applies to LAG subgroups in which LACP is enabled:

• Subgroup selection is always revertive, that is, revertive to the most preferred sub-group

• Whenever the number of active links in the most preferred sub-group is higher than the sub-group's configured threshold, it will be selected as the active sub-group.

• When the number of active links in all the sub-groups is lower than their respective thresholds, the sub-group with the most number of active links will be chosen as the active sub-group.


Configuring Physical Ports with CLI


3 Configuring Physical Ports with CLI3.1 Pre-provisioning Guidelines

3.2 Common Configuration Tasks

3.1 Pre-provisioning Guidelines

Ports are pre-provisioned during initialization of the node, based on the equipment practice and the planned boards. All the ports are of type Ethernet. Supported Ethernet port types include Fast Ethernet (10/100BASE-T), Gigabit Ethernet (1000BASE-T) and 10Gigabit Ethernet (10GBASE-X).

Besides the physical ports, the node auto-creates a single instance of a virtual port. The intent of the virtual port is highlighted in the FD 100/320Gbps NT and FX NT IHub Services Guide.

When the ports are initialized, the following applies for all the ports:

• all the ports have encapsulation type dot1q. No other encapsulation types are supported.

• all the ports are of mode access. This is the default. Only through operator configuration can a port become a network or hybrid port.

3.2 Common Configuration Tasks

The following sections are basic system tasks that must be performed:

• Configuring Ethernet Port Parameters• Ethernet Access Ports• Ethernet Network Port• Ethernet Hybrid Port

• Configuring LAG Parameters


26



3.2.1 Configuring Ethernet Port Parameters

3.2.1.1 Ethernet Access PortsA access port is a port where SAPs will be created.

The following example displays an access port configuration for port nt-a:sfp:1 having category regular:

A:ALA-B>config>port# info----------------------------------------------

description "Ethernet access port"ethernetexitno shutdown

----------------------------------------------A:ALA-B>config>port# info

When the access port is reconfigured to be used as subscriber-facing port, the category of the port is to be changed to residential using the following syntax:

A:ALA-B>config>port# ethernet category residential

This results in the following configuration:


description "Ethernet access port"ethernet

category residentialexitno shutdown


3.2.1.2 Ethernet Network PortA network port participates in the service provider transport or infrastructure network processes.

The following example displays a network port configuration:


description "Ethernet network port"ethernet

mode networkexitno shutdown





If an access port is to be turned into a network port, use the following syntax:

A:ALA-B>config>port# shutdown

A:ALA-B>config>port# ethernet mode network

3.2.1.3 Ethernet Hybrid PortA hybrid port participates in the service provider transport or infrastructure network processes. On a hybrid port, SAPs can be created to get the access port behavior.

The following example displays a hybrid port configuration:


description "Ethernet hybrid port"ethernet

mode hybridexitno shutdown


If an access or network port is to be turned into a hybrid port, use the following syntax:

A:ALA-B>config>port# shutdown

A:ALA-B>config>port# ethernet mode hybrid

3.2.2 Configuring LAG ParametersThe following constraints apply for creating an LAG:

• A maximum of eight ports can be included in a LAG. All ports in the LAG must share the same characteristics (speed, duplex, hold-timer, and so on). The port characteristics are inherited from the primary port.

• Auto-negotiation must be disabled or set limited mode for ports that are part of a LAG to guarantee a specific port speed.

• Ports in a LAG must be configured as full duplex.

The following example displays LAG configuration output:

A:ALA-A>configure>lag# info detail----------------------------------------------

description “LAG2”mac 04:68:ff:00:00:01port lt:1/1/1port lt:11/3/1port lt:1/5/1port lt:1/7/1


28



port lt:1/9/1dynamic-costport-threshold 4 action down

----------------------------------------------A:ALA-A>configure>lag#


Port and LAG CLI Command Reference


4 Port and LAG CLI Command Reference4.1 CLI Command Syntax Symbols

4.2 Command Hierarchies

4.3 Configuration Commands

4.4 Port Show Command

4.5 LAG Show Command

4.6 Port Monitor Command

4.7 Clear Commands

4.8 Debug Commands

4.1 CLI Command Syntax Symbols

This section explains the symbols used throughout this manual within a CLI command syntax, see Table 2.


30



Table 2 Command Syntax Symbols

4.2 Command Hierarchies

4.2.1 Port and LAG Configuration Commands• Port Configuration Command• Ethernet Command• LAG Command• Show Commands• Monitor Commands• Clear Commands• Debug Commands

Symbol Description

| A vertical line indicates that one of the parameters within the brackets or braces is required.Example: tcp-ack {true|false}

[ ] Brackets indicate optional parameters.Example: redirects [number seconds]

< > Angle brackets indicate that you must enter text based on the parameter inside the brackets.Example: interface

{ } Braces indicate that one of the parameters must be selected.Example: default-action {drop | forward}

[{ }] Braces within square brackets indicates that you must choose one of the optional parameters.Example: sdp sdp-id [{gre | mpls}]

Bold Commands in bold indicate commands and keywords.

Italic Commands in italics indicate command options.

Note — For more information on CLI commands in general, see the CLI Command Guide for FD 100/320Gbps NT and FX NT.




4.2.2 Port Configuration Commandconfigure

— port {port-id}— no port {port-id}

— description description-string— no description— [no] local_nt_ports_only— [no] shutdown

4.2.3 Ethernet Commandconfigure

— [no] port {port-id}— ethernet

— autonegotiate [limited]— [no] autonegotiate— category {regular | residential}— no category— dot1q-etype — no dot1q-etype— duplex {full | half}— use-vlan-dot1q-etype — no use-vlan-dot1q-etype— egress-rate sub-rate [burst burst-size]— no egress-rate— encap-type {dot1q}— no encap-type— hold-time {[up hold-time-up] [down

hold-time-down]}— no hold-time— loopback tunnel vlan-id— no loopback— mode {access | network | hybrid}— no mode— speed {10 | 100 | 1000 | 2500 | 10000}— lldp

— dest-mac {nearest-bridge | nearest-non-tpmr | nearest-customer}— admin-status {rx | tx | tx-rx | disabled}— tx-mgmt-address [system]— no tx-mgmt-address— tx-tlvs [port-desc] [sys-name] [sys-desc]

— suppress-link-state-alarm— no suppress-link-state-alarm— no remark

[sys-cap]— no tx-tlvs

— tca-interval interval-number— tca-threshold

— inputbw


32



— no inputbw— outputbw— no outputbw— rxcrcalignerrors— no rxcrcalignerrors— txcrcalignerrors— no txcrcalignerrors— txcollisions— no txcollisions

4.2.4 LAG Commandconfigure

— [no] lag [lag-id]— description description-string— no description— [no] dynamic-cost— encap-type {dot1q}— no encap-type— hold-time down hold-down-time— no hold-time— lacp [mode] [administrative-key admin-key]— no lacp — lacp-xmit-interval {slow | fast}— no lacp-xmit-interval— [no] lacp-xmit-stdby— [no] link-map-profile

— description description-string— [no] failure-mode {per-link-hash | discard}— [no] link port-id {primary | secondary}

— mode {access | network | hybrid}— no mode— port port-id [port-id …up to 8 total] [priority priority]

[sub-group sub-group-id]— no port port-id [port-id …up to 8 total] — sub-group sub-group-id [preference preference

threshold threshold]— sub-group-force sub-group-id— no sub-group-force— sub-group-switch-detect-time seconds— no sub-group-switch-detect-time— port-threshold value [action {dynamic-cost | down}]— no port-threshold— [no] shutdown

— lag [lag-id]— [no] local_nt_ports_only




4.2.5 Show Commandsshow

— lag [lag-id] [detail] [statistics] — lag lag-id associations— lag lag-id link-map-profile [link-map-profile-id]— lag lag-id associations link-map-profile [link-map-profile-id] sap— port port-id [count] [detail] — port port-id description — port port-id associations— port port-id ethernet

— lldp [nearest-bridge | nearest-non-tpmr| nearest-customer] [remote-info] [detail]

— curr-15min-stats | curr-day-stats | prev-15min-stats | prev-day-stats[interval-number interval-number]

4.2.6 Monitor CommandsFor more information about monitor commands, refer to the FD 100/320Gbps NT and FX NT IHub System Basics, Management and OAM Guide for command usage and CLI syntax.

monitor— lag lag-id [lag-id...(up to 5 max)] [interval seconds]

[repeat repeat] [absolute | rate]— port port-id [port-id...(up to 5 max)] [interval seconds]

[repeat repeat] [absolute | rate]

4.2.7 Clear Commandsclear

— lag lag-id statistics— port port-id statistics— port port-id statistics— port ethernet

— historical-stats all


34



4.2.8 Debug Commandsdebug

— lag [lag-id lag-id port port-id] [all]— lag [lag-id lag-id port port-id] [sm] [pkt] [cfg] [red]

[port-state] [timers]— no lag [lag-id lag-id]

4.3 Configuration Commands

4.3.1 Generic Commands

4.3.1.1 description

Table 3 description command

4.3.1.2 shutdown

Item Description

Syntax description description-stringno description

Context configure>portconfigure>lag

Description This command creates a text description for a configuration context to help identify the content in the configuration file.The no form of this command removes any description string from the context.

Default No description is associated with the configuration context.

Parameters description-string — The description character string. Strings can be up to 160 characters long composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, etc.), the entire string must be enclosed within double quotes.




Table 4 shutdown Command

4.3.2 General Port Commands

4.3.2.1 port

Table 5 port Command

Item Description

Syntax [no] shutdown

Context configure>portconfigure>lag

Description This command administratively disables an entity. When disabled, an entity does not change, reset, or remove any configuration settings or statistics. The operational state of the entity is disabled as well as the operational state of any entities contained within. The no form of this command administratively enables an entity.

Special cases lag — The default state for a Link Aggregation Group (LAG) is shutdown.port — The default state for a port is shutdown.

Item Description

Syntax port {port-id}no port

Context configure

Description This command enables access to the context to configure ports. All ports are pre-provisioned.

Parameters port-id — Specifies the physical port ID. This can be either a network port (nwport-id) or an LT port (ltport-id). The syntax is:• For nwport-id: ::

where:• slot-address — nt, nt-a, nt-b or ntio-1• port-type — sfp, xfp, cfp, vp, eth, ieee1588 or AI• port-num — the port-number

• For ltport-id: lt:// where:• lt — keyword• rack — number identifying the rack• shelf — number identifying the shelf• slot — number identifying the slot


36



4.3.2.2 local_nt_ports_only

Table 6 local_nt_ports_only Command

4.3.3 Ethernet Port Commands

4.3.3.1 ethernet

Table 7 ethernet Command

4.3.3.2 autonegotiate

Item Description

Syntax [no] local_nt_ports_only

Context configure > port

Description This command allows the operator to enable/disable LAG hashing to only local unit ports.

Default No local_nt_ports_only

Exception This command is applicable only for back plane load shared LT ports

Item Description

Syntax ethernet

Context configure>port

Description This command enables access to the context to configure Ethernet port attributes.This context can only be used when configuring Fast Ethernet, Gigabit, or 10Gigabit Ethernet LAN ports on an appropriate MDA.




Table 8 autonegotiate Command

4.3.3.3 category

Table 9 category Command

Item Description

Syntax autonegotiate [limited][no] autonegotiate

Context configure>port>ethernet

Description This command enables speed and duplex autonegotiation on Fast Ethernet ports and enables far-end fault indicator support on Gigabit ports.There are three possible settings for autonegotiation:• “on” or enabled with full port capabilities advertised• “off” or disabled where there are no autonegotiation advertisements• “limited” where a single speed/duplex is advertised.When autonegotiation is enabled on a port, the link attempts to automatically negotiate the link speed and duplex parameters. If autonegotiation is enabled, the configured duplex and speed parameters are ignored. When autonegotiation is disabled on a port, the port does not attempt to autonegotiate and will only operate at the speed and duplex settings configured for the port. Note that disabling autonegotiation on gigabit ports is not allowed as the IEEE 802.3 specification for gigabit Ethernet requires autonegotiation be enabled for far end fault indication.If the autonegotiate limited keyword option is specified the port will autonegotiate but will only advertise a specific speed and duplex. The speed and duplex advertised are the speed and duplex settings configured for the port. One use for limited mode is for multispeed gigabit ports to force gigabit operation while keeping autonegotiation enabled for compliance with IEEE 801.3.Note: The limited keyword is not supported when the Ethernet port is equipped with an electrical SFP. Ports equipped with an electrical SFP will always negotiate up to the highest commonly available speed.7302 ISAM OS requires that auto-negotiation be disabled or limited for ports in a Link Aggregation Group to guarantee a specific port speed.The no form of this command disables autonegotiation on this port.

Default autonegotiate

Parameters limited — The Ethernet interface will automatically negotiate link parameters with the far end, but will only advertise the speed and duplex mode specified by the Ethernet speed and duplex commands.

Item Description

Syntax category {regular | residential}no category


(1 of 2)


38



4.3.3.4 dot1q-etype

Table 10 dot1q-etype Command

Description The port category determines the rules for MAC address learning and for user-to-user communication. This is specified in the FD 100/320Gbps NT and FX NT IHub Services Guide, chapter “Virtual Private LAN Service”, section “ISAM VPLS Implementation”.The port category for an access port is either residential or regular. The port category for access ports can be modified. For ports of mode network and hybrid, the category is fixed to regular, it cannot be modified.The following holds for an access port:A network-facing port will be configured as regular port, a customer-facing port will be configured as residential port.When the system starts up:• LT ports are auto- created with category residential; their mode cannot be modified• Virtual ports are created with category regular• Network-facing ports (including subtending ISAM ports) are created with category regular.In case you want to reconfigure a network-facing port with the intent to connect to a subtended ISAM, you must modify the port category to residential.The no form of this command reverts the port to its default category.

Default For an access port: the default depends on the usage of the port:• for LT ports: residential• for virtual ports: regular• for network-facing ports (including subtending ISAM ports): regular.For network and hybrid ports, the default is regular.

Parameters regular — Configures the mode of the port as regularresidential — Configures the mode of the port as residential

Item Description

(2 of 2)

Item Description

Syntax dot1q-etype 0x0600..0xffffno dot1q-etype


(1 of 2)




4.3.3.5 duplexTable 11 duplex Command

Description This command specifies the Ethertype expected when the port's encapsulation type is dot1q. Dot1q encapsulation is supported only on Ethernet interfaces.When a non-default Ethertype "dot1q-etype" (that is, with value different from 0x8100), is configured on a port, some control plane packets get dropped in the OBC and are never processed:• ARP Request and Response• OSPF Protocol packets• PIM Protocol packets• LDP-UDP packets • LDP-TCP packets • ISIS protocol packets • IP Packets having exact Source IP match with one of L3 interface addresses. • DHCP snooped packets • LSP PING packets • VCCV PING packets • VPLS IPHOST packets • DHCP6 packets• ICMP6 packets • IGMP packets • BFD packets Workaround:In case you need to receive and process the above list of packets on your port with different Ethertype from 0x8100, you can do one of the following:• configure “use-vlan-etype” on that particular port and configure the required ether type on

the corresponding v-VPLS services where SAPs are present over this port (command: configure service vpls vlan-dot1q-etype; for more information, see the IHub services guide).

• configure “use-vlan-etype” on that particular port and configure system-wide ether type as the required ether type which applies for all v-VPLS services (command: configure system vlan-dot1q-etype; for more information, see the IHub system guide)

The no form of this command reverts the dot1q-etype value to the default.

Parameters 0x0600..0xffff — Specifies the Ethertype to expect.

Item Description

(2 of 2)

Item Description

Syntax duplex {full|half}


(1 of 2)


40



4.3.3.6 use-vlan-dot1q-etype

Table 12 use-vlan-dot1q-etype Command

4.3.3.7 egress-rate

Table 13 egress-rate Command

Description This command specifies the Ethernet port duplex modeFull duplex mode configuration:• is possible on all RJ45/SFP/XFP/CFP Ethernet interface ports that support 10, 100, 1

Gbps, 10 Gbps, or 100 Gbps.• is not possible on XFP interface ports that support only 10Gbps.Half-duplex mode configuration:• is only possible if the configured speed on the Ethernet port is 10 or 100 Mbps.• is not possible on an Ethernet port that is part of a link aggregation group.

Parameters full — Full duplex mode must be used.

half — Half-duplex mode must be used.

Item Description

(2 of 2)

Item Description

Syntax use-vlan-dot1q-etype[no] use-vlan-dot1q-etype


Description This command enables/disables the use of the service level dot1q-etype on SAPs (on v-VPLS service) on this port.

Item Description

Syntax egress-rate sub-rate [burst burst-size]no egress-rate


Description This command configures the rate of traffic leaving the network. The no form of this command reverts the value to the default.

(1 of 2)




4.3.3.8 encap-type

Table 14 encap-type Command

4.3.3.9 hold-time

Table 15 hold-time Command

Default no egress-rate

Parameters sub-rate — The egress rate in KbpsValue: 1 — 100000000 Kbps

burst burst-size — The burst size in KbytesValue: 1— 262144 | default

Item Description

(2 of 2)

Item Description

Syntax encap-type {dot1q}no encap-type


Description This command configures the encapsulation method used to distinguish customer traffic on an Ethernet access port or hybrid port, or different VLANs on a network port.The no form of this command reverts the value to the default.

Default dot1q

Parameters dot1q — Ingress frames carry 802.1Q tags where each tag signifies a different service.

Item Description

Syntax hold-time {[up hold-time-up] [down hold-time-down]}no hold-time


(1 of 2)


42



4.3.3.10 loopback

Table 16 loopback Command

Description This command configures port link dampening timers which reduce the number of link transitions reported to upper layer protocols.The hold-time value is used to dampen interface transitions. When an interface transitions from an up state to a down state, it is immediately advertised to the rest of the system if the hold-time-down interval is zero, but if the hold-time-down interval is greater than zero, interface down transitions are not advertised to upper layers until the hold-time-down interval has expired. Likewise, an interface is immediately advertised as up to the rest of the system if the hold-time-up interval is zero, but if the hold-time-up interval is greater than zero, up transitions are not advertised until the hold-time-up interval has expired.The no form of this command reverts to the default values.

Default down 0 — No port link down dampening is enabled; link down transitions are immediately reported to upper layer protocols.up 0 — No port link up dampening is enabled; link up transitions are immediately reported to upper layer protocols.

Parameters up hold-time-up — The delay, in seconds, to notify the upper layers after an interface transitions from a down state to an up state.Values: 0 — 900 seconds | 0— 90000 centisecondsNote: hold-time-up can only be configured in centiseconds for 10GE ports

down hold-time-down — The delay, in seconds, to notify the upper layers after an interface transitions from an up state to a down state.Values: 0 — 900 seconds | 0— 90000 centisecondsNote: hold-time-down can only be configured in centiseconds for 10GE ports

Item Description

(2 of 2)

Item Description

Syntax loopback tunnel vlan-idno loopback


(1 of 2)




4.3.3.11 mode

Table 17 mode Command

Description This command allow to place an access port in MAC loopback. That is, packets egressing the port will be looped back, so they ingress the port. For untagged packets and single tagged packets egressing the port with a VLAN different than the configured tunnel VLAN, an extra VLAN tag (= tunnel VLAN) will be added to the packet before looping the packet. For tagged packets egressing the port with a VLAN equal to the configured tunnel VLAN, the tunnel VLAN will be removed before looping the packet. The following restrictions apply:• To configure a port in loopback, the following conditions must be fulfilled:

• the port must be an access port • no SAP should be configured on the port • the port should not be part of a LAG • the port should not be used by the Lawful Intercept feature

• A tunnel VLAN can only be modified after the loopback has been removed • The loopback can only be removed from a port when no SAP has been defined on this port • LAG membership:

• A port in loopback can be made member of an LAG• Either all the ports or no ports of the LAG must be placed in loopback

Parameters tunnel — keyword, creates a loopback port in tunnel mode.

vlan-id — The VLAN ID (mandatory for tunnel mode).Values: 1 — 4093

Item Description

(2 of 2)

Item Description

Syntax mode {access | network | hybrid}no mode


(1 of 2)


44



4.3.3.12 speed

Table 18 speed Command

Description This command configures an Ethernet port for access mode, hybrid mode, or network mode operation. An access port or channel is used for customer facing traffic on which services are configured. A Service Access Point (SAP) can only be configured on an access port or channel. When a port is configured for access mode, the appropriate encap-type must be specified to distinguish the services on the port. Once an Ethernet port has been configured for access mode, multiple services can be configured on the Ethernet port. Note that ATM and Frame Relay parameters can only be configured in the access mode. The access port can be “regular” or “residential”.A subset of the links that are connected to the NT I/O board can be used as either customer links or network links. Such a link must be configured as uplink when intended to be used as a network-facing port, alternatively the link must be configured as downlink when intended to be used as a user-facing port.A customer-facing port (an LT port or a downlink) can only be of mode access.A virtual port can only be of mode access.Network ports participate in the service provider transport or infrastructure network. Network ports support MPLS. A network port is always of type “regular”.Hybrid ports provide the features of both network ports and access regular ports. The mode of a port cannot be modified if either an SAP, an LAG or an IP interface is configured on the port or if the port is not in shutdown state.The no form of this command restores the default.

Default access — Default channel/port mode for channelized, ASAP, and ATM MDAs.

Parameters access — Configures the Ethernet port to allow creation of SAPs on the port, the port can be either network-facing or customer-facing.network — Configures the Ethernet port to be a network port.hybrid — Configures the Ethernet port to be a hybrid port.

Item Description

(2 of 2)

Item Description

Syntax speed {10|100|1000|2500|10000}


Description This command configures the port speed of a Fast Ethernet port when auto-negotiation is disabled.If the port is configured to autonegotiate this parameter is ignored. Speed cannot be configured for ports that are part of a Link Aggregation Group (LAG).

(1 of 2)




4.3.3.13 lldp

Table 19 lldp Command

4.3.3.14 dest-mac

Table 20 dest-mac Command

Parameters 10 — Sets the link to 10 mbps speed.

100 — Sets the link to 100 mbps speed.




Item Description

(2 of 2)

Item Description

Syntax lldp


Description This command enables the context to configure Link Layer Discovery Protocol (LLDP) parameters on the specified port.

Item Description

Syntax dest-mac { nearest-bridge | nearest-non-tpmr | nearest-customer}

Context configure>port>ethernet>lldp

Description This command configures destination MAC address parameters.

Parameters nearest-bridge — The nearest bridge must be used.

nearest-non-tpmr — The nearest non-Two Port MAC Relay (TPMR) must be used.

nearest-customer — The nearest customer must be used.


46



4.3.3.15 admin-status

Table 21 admin-status Command

4.3.3.16 tx-mgmt-address

Table 22 tx-mgmt-address Command

4.3.3.17 tx-tlvs

Item Description

Syntax admin-status {rx | tx | tx-rx | disabled}

Context configure>port>ethernet>lldp>dest-mac

Description This command configures destination MAC address parameters.

Parameters rx — The LLDP agent will receive, but will not transmit LLDP frames on this port.

tx — The LLDP agent will transmit LLDP frames on this port and will not store any information about the remote systems connected.

tx-rx — The LLDP agent will transmit and receive LLDP frames on this port.

disabled — The LLDP agent will not transmit or receive LLDP frames on this port. If remote systems information is received on this port and it is stored in other tables before the port's administrative status becomes disabled, then the information will naturally age out.

Item Description

Syntax tx-mgmt-address [system]no tx-mgmt-address


Description This command specifies which management address to transmit.The no form of the command resets value to the default.

Parameters system — Specifies to use the system IP address. Note that the system address will only be transmitted once it has been configured if this parameter is specified.




Table 23 tx-tlvs Command

4.3.3.18 tca-interval

Table 24 tca-interval Command

Item Description

Syntax tx-tlvs [port-desc] [sys-name] [sys-desc] [sys-cap]no tx-tlvs


Description This command specifies which LLDP TLVs must be transmitted. The TX TLVS, defined as a bitmap, includes the basic set of LLDP TLVs whose transmission is allowed on the local LLDP agent by the network management. Each bit in the bitmap corresponds to a TLV type associated with a specific optional TLV. Organizationally-specific TLVs are excluded from this bitmap.There is no bit reserved for the management address TLV type since the transmission of management address TLVs is controlled by another object.The no form of the command resets the value to the default.

Default no tx-tlvs

Parameters port-desc — The LLDP agent should transmit port description TLVs.

sys-name — The LLDP agent should transmit system name TLVs.

sys-desc — The LLDP agent should transmit system description TLVs.

sys-cap — The LLDP agent should transmit system capabilities TLVs.

Item Description

Syntax tca-intervalno tca-interval


Description Count of 15 min intervals based on which the TCA alarm raise/clear condition is decided. TCA Alarm Raise: From the 32 previous 15 min valid intervals, if the configured TCA threshold is crossed for 'TcaInterval' times then an alarm is raised. TCA Alarm Clear: From the 32 previous 15 min valid intervals, if the configured TCA threshold hasn't crossed for 'TcaInterval' times and an alarm is already raised for this TCA then the alarm is cleared. On system startup, it will take a minimum of 32 intervals for clearing an already raised alarm.

Default 32


48



4.3.3.19 tca-threshold

Table 25 tca-threshold Command

4.3.3.20 inputbw

Table 26 inputbw Command

4.3.3.21 outputbw

Table 27 outputbw Command

Item Description

Syntax tca-threshold


Description This command enables the context to configure TCA threshold parameters on the specified port.

Item Description

Syntax inputbwno inputbw

Context configure>port>ethernet>tca-threshold

Description Bandwidth input configures the used input bandwidth threshold as percentage of available port bandwidth

Default no inputbw

Item Description

Syntax outputbwno outputbw


Description Bandwidth output configures the used output bandwidth threshold as percentage of available port bandwidth

(1 of 2)




4.3.3.22 rxcrcalignerrors

Table 28 rxcrcalignerrors Command

4.3.3.23 txcrcalignerrors

Table 29 txcrcalignerrors Command

4.3.3.24 txcollisions

Default no outputbw

Item Description

(2 of 2)

Item Description

Syntax rxcrcalignerrorsno rxcrcalignerrors


Description CrcAlignErrors Input configures the Receive CRC Errors threshold as percentage of total number of Crc error packets received on the port

Default no rxcrcalignerrors

Item Description

Syntax txcrcalignerrorsno txcrcalignerrors


Description CrcAlignErrors Output configures the Transmit CRC Errors threshold in percentage of total number of Crc error packets transmitted on the port

Default no txcrcalignerrors


50



Table 30 txcollisions Command

4.3.3.25 suppress-link-state-alarmTable 31 suppress-link-state-alarm Command

4.3.3.26 remarkTable 32 remark Command

Item Description

Syntax txcollisionsno txcollisions


Description txCollisions Output configures the Transmit Collision threshold as percent of the total count of Transmit Collisions Error on the port

Default no txcollisions

Item Description

Syntax suppress-link-state-alarm[no] suppress-link-state-alarm

Context configure > port > Ethernet

Description This command enables/disables the link status change (Link Down) alarm reporting. • “suppress-link-state-alarm” when set would disable the link state change alarm reporting

to management.• "no suppress-link-state-alarm" when set would enable the link state change alarm

reporting.

Default no suppress-link-state-alarm

Item Description

Syntax remark[no] remark

Context configure > port > Ethernet > remark enable

Description This command enables/disables remarking on ports.

Default no remark




4.3.4 LAG Commands

4.3.4.1 lag

Table 33 lag Command

Item Description

Syntax [no] lag [lag-id]

Context configure

Description This command creates the context for configuring Link Aggregation Group (LAG) attributes.A LAG can be used to group up to eight ports into one logical link. The aggregation of multiple physical links allows for load sharing and offers seamless redundancy. If one of the links fails, traffic will be redistributed over the remaining links. Up to 8 links can be supported in a single LAG, up to 200 LAGs can be configured on a node. NOTE: All ports in a LAG group must have autonegotiation set to Limited or Disabled.There are three possible settings for autonegotiation:• “on” or enabled with full port capabilities advertised• “off” or disabled where there is no autonegotiation advertisements• “limited” where a single speed/duplex is advertised. When autonegotiation is enabled on a port, the link attempts to automatically negotiate the link speed and duplex parameters. If autonegotiation is enabled, the configured duplex and speed parameters are ignored. When autonegotiation is disabled on a port, the port does not attempt to autonegotiate and will only operate at the speed and duplex settings configured for the port. Note that disabling autonegotiation on gigabit ports is not allowed as the IEEE 802.3 specification for gigabit Ethernet requires autonegotiation be enabled for far end fault indication.If the autonegotiate limited keyword option is specified the port will auto-negotiate but will only advertise a specific speed and duplex. The speed and duplex advertised are the speed and duplex settings configured for the port. One use for limited mode is for multispeed gigabit ports to force gigabit operation while keeping autonegotiation is enabled for compliance with IEEE 801.3.7302 ISAM requires that auto-negotiation be disabled or limited for ports in a Link Aggregation Group to guarantee a specific port speed.The no form of this command deletes the LAG from the configuration. Deleting a LAG can only be performed while the LAG is administratively shut down. Any dependencies such as IP-Interfaces configurations must be removed from the configuration before issuing the no lag command.

Default No LAGs are defined.

Parameters lag-id — The LAG identifier, expressed as a decimal integer.Values: 1 — 64


52



4.3.4.2 dynamic-cost

Table 34 dynamic-cost Command

4.3.4.3 encap-type

Table 35 encap-type Command

Item Description

Syntax [no] dynamic-cost

Context configure>lag lag-id

Description This command enables OSPF costing of a Link Aggregation Group (LAG) based on the available aggregated, operational bandwidth.The path cost is dynamically calculated based on the interface bandwidth. OSPF path cost can be changed through the interface metric or the reference bandwidth. If dynamic cost is configured, then costing is applied based on the total number of links configured and the cost advertised is inversely proportional to the number of links available at the time. This is provided that the number of links that are up exceeds the configured LAG threshold value at which time the configured thre

IHub Interface Guide - 3HH-11983-AAAA-TQZZA-06download.vianet.com.np/Others/Temp/Nokia/Nokia...

Documents

Transcript of IHub Interface Guide - 3HH-11983-AAAA-TQZZA-06download.vianet.com.np/Others/Temp/Nokia/Nokia...