04-15-2005 10:38 AM
Hello,
I just set up my CSS 11154 and I assigned the IP address to the Mgmt interface. I can ping it if I'm on the same subnet, but if I'm across a routed interface, I can not. I didn't see anywhere to put in a "default-gateway" parameter like on at regular switch. So, I just put in the
ip route 0.0.0.0 0.0.0.0 10.1.0.1
statement, thinking that would do the trick. It doesn't work. Any suggestions. Here's my config:
CSS11150# show run
!Generated on 01/01/1981 00:00:34
!Active version: ap0500033
configure
!*************************** GLOBAL ***************************
bridge spanning-tree disabled
ip route 0.0.0.0 0.0.0.0 10.1.0.1 1
!************************* INTERFACE *************************
interface e1
phy 100Mbits-FD
interface e2
phy 100Mbits-FD
interface e3
phy 100Mbits-FD
interface e4
phy 100Mbits-FD
interface e5
phy 100Mbits-FD
interface e6
phy 100Mbits-FD
interface e7
phy 100Mbits-FD
interface e8
phy 100Mbits-FD
interface e9
phy 100Mbits-FD
interface e10
phy 100Mbits-FD
interface e11
phy 100Mbits-FD
interface e12
phy 100Mbits-FD
!************************** CIRCUIT **************************
circuit VLAN1
ip address 20.33.33.33 255.255.255.0
CSS11150#
Solved! Go to Solution.
04-19-2005 11:13 AM
Dave,
glad to hear you found the command you needed in 6.10
Regarding ip addresses and vlans, switches nowadays separate the physical interface from the logical interface.
The circuit or vlan is the logical interface.
You assign it an ip address.
Physical interface can be grouped into logical interfaces.
For example, you could group e1 and e2 under vlan 100 and e3 under vlan 200.
The CSS will bridge traffic from e1 to e2 and will route traffic from e3 to e1 or e2.
Hoep this helps.
Gilles.
-please take a moment of your time to rate each answer sent to you by members of the forum.
04-16-2005 12:08 AM
you can configure 'ip management route ...' but no default gateway.
Also, be careful that you can't have the same route pointing to management interface and to a regular interface.
Also the command above comes only in recent versions.
Regards,
Gilles.
04-18-2005 04:07 AM
Hi Gilles,
It doesn't appear as though the "ip management route" is a valid command. Here's my version and what I have as options when issuing the "ip" command:
CSS11150(config)# version
Version: ap0500033 (5.00 Build 33)
Flash (Locked): 5.00 Build 33
Flash (Operational): 5.00 Build 33
Type: PRIMARY
Licensed Cmd Set(s): Standard Feature Set
CSS11150(config)# ip ?
ecmp Set the equal-cost multipath selection algorithm
firewall Configure firewall load-balancing route
no-implicit-service Do not start an implicit service for the next hop of
static routes
opportunistic Set the IP opportunistic layer-3 forwarding mode
record-route Enable processing of frames with a record-route option
redundancy Enable box-to-box redundancy
route Configure a static route
source-route Enable processing of source-routed frames
subnet-broadcast Enable forwarding of subnet broadcast addressed frames
uncond-bridging Do not allow routing lookup to override bridging decision
CSS11150(config)# ip
Any suggestions?
Also, your comment regarding "you can't have the same route pointing to a management interface and to a regula interface." What does that mean. I'm treating these things as basically the same as a regular 29xx/35xx switch, but there are definitely differences.
Thanks,
Dave
04-18-2005 04:22 AM
Dave,
from my last post
"Also the command above comes only in recent versions. "
Do you think that 5.0(0.33) is recent ?
.
no - this version is 2 years old.
You need the latest 6.10 for the command mentioned.
Using the search engine you could find the documentation for the command.
Also, the CSS is TOTALLY different from any other Cisco switch. The CSS was acquired from Arrowpoint and therefore is a different concept.
Gilles.
04-19-2005 11:02 AM
Hi Gilles,
This worked like a charm. Once I upgraded to 6.10x, I had the ability to route traffic to/from the Mgmt interface. It wouldn't let me put in a default route, but that doesn't matter. I just put in a static route and that did the trick.
Now I just have to get my head wrapped around Circuits and stuff. I'm a bit confused as to why VLANs (just another name for "circuits" I think) have IP address information associated to them. I don't understand why an L2 interface has an IP address assigned. But I'll see what I can find out about that.
Thanks,
Dave
04-19-2005 11:13 AM
Dave,
glad to hear you found the command you needed in 6.10
Regarding ip addresses and vlans, switches nowadays separate the physical interface from the logical interface.
The circuit or vlan is the logical interface.
You assign it an ip address.
Physical interface can be grouped into logical interfaces.
For example, you could group e1 and e2 under vlan 100 and e3 under vlan 200.
The CSS will bridge traffic from e1 to e2 and will route traffic from e3 to e1 or e2.
Hoep this helps.
Gilles.
-please take a moment of your time to rate each answer sent to you by members of the forum.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide