The run show ipipv6-source-guard binding command shows the IP IPv6 source guard binding entries.
Command Syntax
run show ipipv6-source-guard binding [interface <interface-name>]
...
Parameter | Description |
interface <interface-name> | Optional. Specifies an interface name that enabled IP IPv6 source guard. The value could be a physical port. |
Example
View the IP IPv6 source guard binding entries.
| Code Block |
|---|
admin@PICOS# run show ipipv6-source-guard binding Total ipsgipsg6 host count: 5 Mac-Address Ip-Address Interface VLAN Type Filter-Type Status ----------------------------------------------------------------------------------------------------------- 22:22:22:22:22:22 1.1.1.12006::6 ge-1/1/3 20 static ip effective 33:33:33:33:33:33 1.1.1.12007::7 te-1/1/3 20 static ip ineffective 22:22:22:11:11:1120 10.1.1.10 ge-1/1/3 4094 static ip+mac ineffective 22:22:22:11:11:20 20.1.1.10100::10 ge-1/1/3 1 dhcpdhcp6-snooping ip+mac ineffective 22:22:22:22:22:22 2048::11 20.20.20.22 ge-1/1/3 6 static ip+mac ineffective |
...
The parameter “Type” indicates the type of the entry, the value could be static or dhcpdhcp6-snooping:
Ø static: indicates that the entry is manually configured.
Ø dhcpdhcp6-snooping: indicates that the entry is originated from the DHCP DHCPv6 snooping binding table.
The parameter “Filter-type” indicates the IP IPv6 source guard filtering item based on specific interface and VLAN. The value could be ip or ip+mac,
Ø ip: enables IP IPv6 Source Guard with interface + VLAN + Source IP filtering.
Ø ip+mac: enables IP IPv6 Source Guard with interface + VLAN + Source IP + Source MAC address filtering.
The parameter “Status” indicates whether the IP IPv6 source guard binding entry is effective or not. After configuring the IP IPv6 source guard binding entry, it needs to be deployed to the hardware by the system. If the entry is successfully deployed to the hardware, the "Status" will be shown as effective; however, if the deployment fails, it will be displayed as ineffective. Typically, the reason for deployment failure is due to the user configuring too many ACL rules, leading to insufficient hardware resources.