Why is a configuration error message prompted when an S series or E series switches use the network command in RIP to advertise network segment routes

1

Q: Why is a configuration error message prompted when the network command in RIP is used to advertise network segment routes?
A: RIP is based on natural network segments. Though RIP version 2 supports other subnet masks, natural network segments must be used for configuration. For example, if the IP address of VLANIF100 is set to 1.1.1.1/24, the network 1.0.0.0 command must be used for configuration.

Other related questions:
Method to configure DHCP on different network segments on S series switches
S series switches excluding the S1700 support DHCP configuration on the same network segment or different network segments. A DHCP relay agent is required to forward DHCP messages when the DHCP server and DHCP client are located on different network segments or in different VLANs.

Why does the NMS display an error message when it uses SNMPv2c to connect to an S series switch
When an NMS uses SNMPv2c to connect to an S series switch (except the S1700), error message "another nms was polling the switch with wrong community" is displayed. The reason is that the community name configured on the NMS is different from that configured on the switch. Run the display snmp-agent community command on the switch to check the configured community name.

The method of S-series switches configure multiple network segments on an interface
S series switches (except S1700) can be configured by configuring the slave address to configure the address of multiple network segments on a Layer 3 interface.

Can public network routes be iterated to tunnels on S series switches
Q: Can public network routes be iterated to tunnels? A: For S series switches, by default, an unlabeled public network route can only be iterated to the outbound interface and next hop, but not a tunnel. If the route recursive-lookup tunnel command is executed, an unlabeled public network route can inherit the tunnel ID of an IGP or static route, allowing packets to be forwarded through MPLS routes. The route recursive-lookup tunnel command enables the switch to iterate unlabeled public network routes to tunnels. This command is valid only to unlabeled public network routes that require tunnel iteration. To control tunnel iteration more precisely, you can filter unlabeled public network routes by specifying an optional IP prefix list. The undo route recursive-lookup tunnel command disables tunnel iteration.

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top