Triggering ANCP OAM to Simulate ANCP Port Down and Port Up Messages
You can trigger ANCP OAM to simulate the sending of an ANCP Port-Down or Port-Up message. Typically you use this feature only when troubleshooting an ANCP issue or to mitigate an error condition when ANCP is not operating normally.
When you issue either the request ancp oam port-down command or the request ancp oam port-up command from
operational mode, you must specify either an IP address for an ANCP
neighbor or the physical interface used for subscriber access. You
must also specify all of the following; all three are required together
to identify the access node:
circuit-id aci—ANCP Access-Loop-Circuit-ID TLV
remote-id ari—ANCP Access-Loop-Remote-ID TLV
outer-vlan-id vlan-id—ANCP Access-Aggregation-Circuit-ID-Binary TLV
You can use the request ancp oam port-up command
to trigger reauthorization and re-creation of the dynamic VLAN session
and logical interface that is supporting Layer 2 wholesale after they
have been removed by any of the following:
Issuance of the
clear network-access aaa subscribercommand.Receipt of a RADIUS disconnect message that does not include the RADIUS Acct-Terminate-Cause attribute (49).
Action by the ANCP agent.
The previous instance of the VLAN can be either ANCP-triggered (a wholesaled VLAN) or a conventionally autosensed dynamic VLAN (an access-provider-owned VLAN).
If no access line parameters are available from ANCP for a given
access line, you can use the request ancp oam port-up command
as a test mechanism to trigger authorization of a dynamic VLAN session
and logical interface. The session and interface are created when
a RADIUS Access-Accept message is subsequently received.
These commands have no effect on conventionally autosensed dynamic VLANs (for the access provider’s own subscriber sessions) that have matching access loop attributes.
Genuine ANCP Port-Down and Port-Up messages take precedence
over these simulated messages. This means that when a Port-Down message
has already been received, you cannot use the request ancp oam
port-up command to initiate the Port-Up condition. When a Port-Up
message has already been received, you cannot use the request
ancp oam port-down command to initiate the Port-Down condition.
You can use the request ancp oam port-down command
to trigger removal of the ANCP-triggered, autosensed, dynamic VLAN
that corresponds to the specified attributes. The typical use for
this command is to remove the VLAN created by sending a request
ancp oam port-up command.
To simulate an ANCP Port Up message:
Identify the loop by the neighbor’s IP address or the access-facing physical interface, and the ACI, ARI, and outer VLAN ID.
user@host> request ancp oam port-up neighbor 192.168.32.5 circuit-id line-aci-1 remote-id line-ari-1 outer-vlan-id 126 user@host> request ancp oam port-up subscriber-interface ge-1/0/1 circuit-id line-aci-1 remote-id line-ari-1 outer-vlan-id 126
To simulate an ANCP Port Down message:
Identify the loop by the neighbor’s IP address or the access-facing physical interface, and the ACI, ARI, and outer VLAN ID.
user@host> request ancp oam port-down neighbor 192.168.32.5 circuit-id line-aci-1 remote-id line-ari-1 outer-vlan-id 126 user@host> request ancp oam port-down subscriber-interface ge-1/0/1 circuit-id line-aci-1 remote-id line-ari-1 outer-vlan-id 126
To verify the operation of either request, you can enter the following commands before and after initiating the Port Down or Port Up message:
show subscribers client-type vlan-oob detail—Subscriber information is displayed for the VLAN on Port UP, or disappears on Port Down.show subscribers summary—The VLAN-OOB counter reflects the creation or removal of the VLAN-OOB session by incrementing (Port Up) or decrementing (Port Down).show l2-routing-instance routing-instance-name—The VLAN counters reflect to reflect the creation or removal of the VLAN-OOB session by incrementing (Port Up) or decrementing (Port Down).