Interface Management Configuration

ethernet interface configuration ethernet interface configuration introduction introduction ethernet interfaces are commonly used for carrying out business related tasks and data transmission they are often referred to as ports numbering scheme numbering scheme the numbering scheme for ethernet interfaces in this product series is as follows ethernetx here, x represents the interface number, starting from 1 and increasing incrementally it's important to note that the naming conventions for interfaces may vary based on the series for instance, in enterprise level products with 100g interfaces, the naming interval for 100g interfaces is 4 taking the example of cx206p 48s m h, the interface with the number 49 is the first 100g interface, and its name is ethernet49 the second 100g interface is named ethernet53, and so on default configuration of interfaces default configuration of interfaces true 435,304#4283c7 unhandled content type #4283c7 unhandled content type unhandled content type unhandled content type #d8e5f5 unhandled content type #d8e5f5 unhandled content type unhandled content type unhandled content type #d8e5f5 unhandled content type #d8e5f5 unhandled content type unhandled content type unhandled content type #d8e5f5 unhandled content type #d8e5f5 unhandled content type unhandled content type unhandled content type basic configuration of interfaces basic configuration of interfaces the product series supports interface speeds of 1g, 10g, 25g, and 100g for example, the cx204y 48gt, cx204y 24gt, and cx206y 48gt series default to interface speeds of 1g and 25g the cx204y 48s series defaults to 10g and 25g speeds the cx206p 48gt series defaults to 10g and 100g speeds true 295,237 5,667 5#4283c7 unhandled content type #4283c7 unhandled content type #4283c7 unhandled content type unhandled content type unhandled content type unhandled content type #d8e5f5 unhandled content type #d8e5f5 unhandled content type #d8e5f5 unhandled content type unhandled content type unhandled content type unhandled content type #d8e5f5 unhandled content type #d8e5f5 unhandled content type #d8e5f5 unhandled content type unhandled content type unhandled content type unhandled content type #d8e5f5 unhandled content type #d8e5f5 unhandled content type #d8e5f5 unhandled content type note in the cx206p 48s series, the 10g interfaces do not support configuration at 25g speed configuring layer 2/3 mode switching for ethernet interfaces configuring layer 2/3 mode switching for ethernet interfaces by default, the switch's interfaces do not belong to any vlan and have no ip address configured when an interface is configured with an ip address, vrf, or other layer 3 attributes, it automatically switches to layer 3 mode if you need to change the layer 2/3 mode of an interface, you should first remove the layer 3 attribute configurations from the interface afterward, execute the no router interface command true 377,242 5,167 5#4283c7 unhandled content type #4283c7 unhandled content type #4283c7 unhandled content type unhandled content type unhandled content type unhandled content type #d8e5f5 unhandled content type #d8e5f5 unhandled content type #d8e5f5 unhandled content type unhandled content type unhandled content type unhandled content type configuring interface splitting configuring interface splitting interface splitting refers to dividing a 100g bandwidth physical interface on the device into multiple independent lower bandwidth interfaces to meet the requirements of connecting to lower bandwidth interfaces the device supports splitting a 100g interface into four 1g/10g/25g interfaces after splitting, each interface is assigned an independent identifier for example, when a 100ge interface like ethernet17 is split into four 10ge interfaces, the resulting interfaces are numbered ethernet17 to ethernet20 true 314,265,150#4283c7 unhandled content type #4283c7 unhandled content type #4283c7 unhandled content type unhandled content type unhandled content type unhandled content type #d8e5f5 unhandled content type #d8e5f5 unhandled content type #d8e5f5 unhandled content type unhandled content type unhandled content type unhandled content type #d8e5f5 unhandled content type #d8e5f5 unhandled content type #d8e5f5 unhandled content type maintenance interface maintenance interface true 311,444 5,153 5#4283c7 unhandled content type #4283c7 unhandled content type #4283c7 unhandled content type unhandled content type unhandled content type unhandled content type #d8e5f5 unhandled content type #d8e5f5 unhandled content type #d8e5f5 unhandled content type unhandled content type unhandled content type unhandled content type #d8e5f5 unhandled content type #d8e5f5 unhandled content type #d8e5f5 unhandled content type unhandled content type unhandled content type unhandled content type #d8e5f5 unhandled content type #d8e5f5 unhandled content type #d8e5f5 unhandled content type port isolation configuration port isolation configuration introduction introduction port isolation allows the isolation of ports within the same vlan by adding ports to an isolation group, isolation between layer 2 data packets and multicast packets can be achieved for the ports within the isolation group traffic between ports within the isolation group and ports not added to the isolation group is not affected by the isolation group and can flow bidirectionally configuring port isolation groups configuring port isolation groups true 313,222 5,140 5#4283c7 unhandled content type #4283c7 unhandled content type #4283c7 unhandled content type unhandled content type unhandled content type unhandled content type #d8e5f5 unhandled content type #d8e5f5 unhandled content type #d8e5f5 unhandled content type unhandled content type unhandled content type unhandled content type #d8e5f5 unhandled content type #d8e5f5 unhandled content type #d8e5f5 unhandled content type configuration example configuration example network requirements network requirements a cell has multiple users, and now requires that the users cannot interoperate with each other's layer 2 messages, but all can access the external network procedure procedure create a vlan and add the interface to the vlan sonic(config)# vlan 100 sonic(config)# port group ethernet 1 4 sonic(config port group 1 4)# switchport access vlan 100 create port isolation group sonic(config)# port isolate group 1 sonic(config port isolate group 1)# interface 1,2,3 verify configuration verify configuration view the port ioslation group configuration sonic# show port isolate group + + + + \| group id | interface | mode | +============+=============+========+ \| 1 | ethernet1 | l2 | \| | ethernet2 | | \| | ethernet3 | | + + + + no interoperability between pcs, all pcs can access the external network interface bulk configuration interface bulk configuration introduction introduction when configuring a specific function (e g , port shutdown) across multiple interfaces, individually entering each interface's view and executing commands can become cumbersome to simplify this process, the interface bulk configuration feature can be utilized to configure interfaces in batches, thereby reducing the configuration workload there is no upper limit to the number of interfaces that can be included in a bulk configuration, only constrained by system resources however, if a significant number of interfaces are involved, executing commands within the bulk interface configuration view might take longer when performing bulk interface configuration, if the interfaces listed already possess existing configurations, attempting to enter the bulk configuration view will result in failure in such cases, the interface list needs to be reselected once inside the bulk interface configuration view, you can utilize the "?" command to explore the supported command lines for bulk configuration interface bulk configuration interface bulk configuration true 357,235 5,413 5#4283c7 unhandled content type #4283c7 unhandled content type #4283c7 unhandled content type unhandled content type unhandled content type unhandled content type #d8e5f5 unhandled content type #d8e5f5 unhandled content type #d8e5f5 unhandled content type loopback interface configuration loopback interface configuration introduction introduction the loopback interface is a type of virtual interface once created, the physical layer of the loopback interface remains in an "up" state unless manually disabled due to this characteristic, the loopback interface can be applied in the following scenarios source address for device generated ip packets because the loopback interface address is stable and a unicast address, it is often regarded as an identifier for the device by allowing or prohibiting packets carrying the loopback interface address to pass through authentication or security servers, it is possible to permit or restrict packets generated by specific devices this simplifies packet filtering rules however, it should be noted that when using the loopback interface address as the source address for ip packets, routing configurations are needed to ensure the reachability of the loopback interface to the destination route dynamic routing protocols in certain dynamic routing protocols, when a router id is not configured, the loopback interface's ip address is used as the router id by default in the context of the bgp protocol, to ensure that bgp sessions are not affected by physical interface failures, the source interface for transmitting bgp packets can be configured as the loopback interface in band device management the loopback interface can be utilized for device management within the network infrastructure loopback interface configuration loopback interface configuration true 400,216,360#4283c7 unhandled content type #4283c7 unhandled content type #4283c7 unhandled content type unhandled content type unhandled content type unhandled content type #d8e5f5 unhandled content type #d8e5f5 unhandled content type #d8e5f5 unhandled content type unhandled content type unhandled content type unhandled content type