For feedback and comments: |
documentation.feedback@alcatel-lucent.com |
•
• The sap-id can be configured in one of the following formats:
port-id: 1/1/3lag-id: lag-63 port-id:qtag1: 1/1/3:100lag-id:qtag1:lag-63:102 port-id:qtag1.qtag2: 1/1/3:100.10 bundle-id: bundle-ima-1/1.1bpgrp-id: bpgrp-ima-1 port-id: 1/1/1:100aps-id: aps-1dlci: 16 port-id: 1/1/3.1
Values: sap-id: null [port-id | bundle-id | bpgrp-id | lag-id | aps-id]
dot1q [port-id | bundle-id | bpgrp-id | lag-id | aps-id]:qtag1
qinq [port-id | bundle-id | bpgrp-id | lag-id]:qtag1.qtag2
atm [port-id | aps-id][:vpi/vci|vpi| vpi1.vpi2]
frame [port-id | aps-id]:dlci
cisco-hdlc slot/mda/port.channel
cem slot/mda/port.channel
ima-grp [bundle-id[:vpi/vci|vpi|vpi1.vpi2]
port-id slot/mda/port[.channel]
bundle-id bundle-type-slot/mda.bundle-num
bundle keyword
type ima, fr, ppp
bundle-num 1 — 256
bpgrp-id bpgrp-type-bpgrp-num
bpgrp keyword
type ima, ppp
bpgrp-num 1 — 1280
aps-id aps-group-id[.channel]
aps keyword
group-id 1 — 64
ccag-id ccag-id.path-id[cc-type]:cc-id
ccag keyword
id 1 — 8
path-id a, b
cc-type .sap-net, .net-sap
cc-id 0 — 4094
eth-tunnel eth-tunnel-tunnel-id
tunnel-id 1 — 1024
eth-tunnel-sap-id 0 — 4094
lag-id lag-id
lag keyword
id 1 — 800
qtag1 0 — 4094
qtag2 *, 0 — 4094
vpi NNI: 0 — 4095
UNI: 0 — 255
vci 1, 2, 5 — 65535
dlci 16 — 1022
ipsec-id ipsec-id.private | public:tag
ipsec keyword
id 1 — 4
tag 0 — 4094
tunnel-id tunnel-id.private|public:tag
tunnel keyword
id 1..16
tag 0..4094Specifies the multilink bundle to be associated with this IP interface. The bundle keyword must be entered at the beginning of the parameter.
The command syntax must be configured as follows:*A:ALA-12>config# port bundle-ppp-5/1.1
*A:ALA-12>config>port# multilink-bundleSpecifies the bundle protection group ID to be associated with this IP interface. The bpgrp keyword must be entered at the beginning of the parameter.*A:ALA-12>config# port bpgrp-ima-1
*A:ALA-12>config>service>vpls$ sap bpgrp-ima-1
Values qtag1: 0 — 4094
qtag2 : * | 0 — 4094
The SAP is identified by the 802.1Q tag on the port. Note that a 0 qtag1 value also accepts untagged packets on the dot1q port. SONET/SDH
TDM SONET/SDH
TDM This parameter associates an IPSec group SAP with this interface. This is the public side for an IPSec tunnel. Tunnels referencing this IPSec group in the private side may be created if their local IP is in the subnet of the interface subnet and the routing context specified matches with the one of the interface.This context will provide a SAP to the tunnel. The operator may associate an ingress and egress QoS policies as well as filters and virtual scheduling contexts. Internally this creates an Ethernet SAP that will be used to send and receive encrypted traffic to and from the MDA. Multiple tunnels can be associated with this SAP. The “tag” will be a dot1q value. The operator may see it as an identifier. The range is limited to 1 — 4095.port port-idThe port-id can be configured in one of the following formats:
Values port-id slot/mda/port[.channel]
bundle-id bundle-type-slot/mda.bundle-num
bundle keyword
type ima|ppp
bundle-num 1 — 256
bpgrp-id bpgrp-type-bpgrp-num
bpgrp keyword
type ima, ppp
bpgrp-num 1 — 256
aps-id aps-group-id[.channel]
aps keyword
group-id 1 — 64
ccag-id ccag-id.<path-id>[cc-type]
ccag keyword
id 1 — 8
path-id a, b
cc-type [.sap-net|.net-sap]
eth-tunnel-id - eth-tunnel-id
eth-tunnel keyword
id 1 — 1024
lag-id lag-id
lag keyword
id 1— 800